Pubsub tag missing on subscription result

SND: <iq id="1" type="set" to="pubsub.example.com">
       <pubsub xmlns="http://jabber.org/protocol/pubsub">
         <subscribe
             node="/home/example.com/romeo/1"
             jid="romeo@example.com/here" />
       </pubsub>
     </iq>

RCV: <iq from="pubsub.example.com"
         to="romeo@example.com/here"
         id="1" type="result">
       <subscription
           node="/home/example/romeo/1"
           jid="noc@example.com/here"
           subscription="subscribed" subid="4B5E6F6E9B848" />
     </iq>

The inner subscription tag should be wrapped:

  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
      <subscription ... />
  </pubsub>

It might be missing in other areas as well; I haven't done enough testing there.

Node deletion is missing too?

From XEP-0060: 8.4 Delete a Node

If a service supports node creation, it MUST support node deletion. If an implementation persists items, it MUST remove all items from persistent storage before the node itself is deleted.

--

SND: <iq id="42" type="set" to="pubsub.example.com">
       <pubsub xmlns="http://jabber.org/protocol/pubsub">
         <delete node="/home/example.com/romeo/node" />
       </pubsub>
RCV: <iq from="pubsub.example.com"
         to="romeo@example.com/here"
         type="error" id="42">
       <pubsub xmlns="http://jabber.org/protocol/pubsub">
         <delete node="/home/example.com/romeo/node" />
       </pubsub>
       <error code="501" type="cancel">
         <feature-not-implemented
             xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" />
       </error>
     </iq>

Will pubsub be completed in 2.0.1?

8.4 Delete a Node is an

8.4 Delete a Node is an owner use case

xmlns must be http://jabber.org/protocol/pubsub#owner

see example 140

ejabberd's 2.0.0 pubsub is

ejabberd's 2.0.0 pubsub is v1.10 compliant
this wrapping should have been added in pubsub v1.11 i guess
bug is tracked here: pubsub subscription result is not wrapped in pubsub tag

this is indeed a bug, it's

this is indeed a bug, it's even not 1.10 compliant.
it will be corrected in 2.0.1

Syndicate content