If a stanza is sent by the managing entity on a managed namespace, the server MUST NOT forward it. This way, the managing entity can use privileged entity to do specific treatments, a kind of universal plugin (i.e. working with all servers implementing &xep0355; and &xep0356;).

In the following examples, juliet@capulet.lit has its "jabber:iq:roster" namespace delegated to filter.capulet.lit. filter.capulet.lit is a server agnostic component which filters allowed entities (which can be added to a roster), and sort them in enforced groups.

filter.capulet.lit accepts to add Romeo, but all JIDs with a montaigu.lit must be in a "Rivals" group, so it first returns a success result (Romeo is accepted).

At this stade, the entity is accepted, but not added to the roster. filter.capulet.lit is also a privileged entity which can manage "jabber:iq:roster", so it uses this ability to add Romeo in the enforced group:

The namespace is delegated, but as the stanza is from the managing entity, the server manages it normally. The entity is also privileged, so it can change the stanza of Juliet, the server accepts:

The server will then send the roster pushes (with the enforced group) normally.

When a server delegates a namespace to a managing entity, the later can have particular features which must be advertised by the former with disco protocol.

This is done by using a disco node, which is built in the following way: if pubsub.capulet.int manages pubsub namespace, it MUST report that fact in discovery feature, and have a 'urn:xmpp:delegation:2::http://jabber.org/protocol/pubsub' node which reports the managed features.

The node name is obtained by concatenating this XEP namespace (urn:xmpp:delegation:2), a '::' separator, and the delegated namespace (here http://jabber.org/protocol/pubsub).
The server MUST advertise the result in its own discovery answer, and MUST ignore features of its internal component (here internal PubSub service).

In the following example, the capulet.int server delegates its internal PEP component to pubsub.capulet.int. capulet.int only supports REQUIRED PubSub features and auto-create, while pubsub.capulet.int supports REQUIRED PubSub features and publish-options, but not auto-create.
juliet@capulet.int asks its server what it is capable of, she is specially interested in PubSub capabilities.

Server delegates its PubSub namespace to pubsub.capulet.lit, so it asks its available features for this namespace like this:

Note that in real situation, server has probably this information already in cache (see Implementation Notes).
pubsub.capulet.lit returns its available features:

Server include the results in its own discovery info results:

Note that 'http://jabber.org/protocol/pubsub#auto-create' is not available.

N.B.: In the special case of attribute filtering, the server still display managing entity's features for the whole delegated namespace instead of its own internal ones.

As an entity may ask for discovery information on bare JID, which the server would answer, the managing entity must be able to send this kind of information.

To do so, the mechanism is the same as for server features, but the separator is ':bare:' instead of '::':

Server delegate its PubSub namespace to pubsub.capulet.lit, so it ask its available features for this namespace like this:

As for general case, server has probably this information already in cache.
pubsub.capulet.lit returns its available features:

Then the server returns the answer to Juliet, as in general case, with requested bare JID in 'from' field.

Extensions of Service Discovery as specified in &xep0128; follow the same rules: for the delegated namespace, internal extensions MUST be removed and extensions of managing entity MUST be included instead.

It may be necessary for a managing entity to advertise feature on a node which is unknown at the time of configuration. This is notably the case for a PEP component: features must be advertisable on disco nodes mapping pubsub nodes.

To allows that, the special namespace 'urn:xmpp:delegation:2:bare:disco#info:*' is used, and means "delegate information discovery requests made on bare jids for any discovery node which is not already managed by the server".

The node 'urn:xmpp:microblog:0' is not managed by the server. Normally, this would result as an <item-not-found> &IQ; error, but the namespace 'urn:xmpp:delegation:2:bare:disco#info:*' is delegated to pubsub.capulet.lit, thus the server delegate the stanza to the managing entity:

The managing entity answers with its own disco features for the requested node:

Then the server decapsulate the &IQ; result, validate it as explained in Server Forwards Delegated &IQ; Stanza, and send the result to Juliet:

A managing entity must be able to answer items discovery requests on bare jids. For PEP components, this is used to show available nodes on the service. Furthermore, An information discovery request or an items discovery requests on a node corresponding to an item advertised by the managing entity must be forwarded to the managing entity too.

This is done by using the special namespace 'urn:xmpp:delegation:2:bare:disco#items:*' which means "delegate items discovery made on bare jids with no node specified and all items discovery requests made on bare jids with a node which is not already managed by the server".

Note: When no node is used, and unlike the disco#info case, the server SHOULD NOT nest its internal items with the ones from managing entity. The reason is that bare jids disco items are usually used for PEP nodes, and the server would then mix internal PEP nodes with the managing entity nodes, which would be confusing for XMPP clients and end-users. The server implementation MAY choose to nest items anyway, in which case the mechanism is the same as for disco#info.

A server SHOULD NOT cache result of forwarded disco#items requests, as this is highly dynamic.

The namespace 'urn:xmpp:delegation:2:bare:disco#items:*' is delegated to pubsub.capulet.lit, thus the server delegate the stanza to the managing entity:

The managing entity answers with its own disco items for Juliet's JID:

Then the server decapsulate the &IQ; result, validate it as explained in Server Forwards Delegated &IQ; Stanza, and send the result to Juliet:

Juliet now wants to know the IDs of blog items which has been published on her blog, to do so she does an items discovery request on her own bare jid with the 'urn:xmpp:microblog:0' node:

Because the special namespace 'urn:xmpp:delegation:2:bare:disco#items:*' is delegated to pubsub.capulet.lit, the server forward the request to this managing entity:

The managing entity answers with its own disco items for the requested entity and node (pubsub.capulet.lit being a PEP service, the items are actually Juliet's blog items IDs):

The server decapsulates the &IQ; result, validate it as explained in Server Forwards Delegated &IQ; Stanza, and send the result to Juliet: