mirror of https://github.com/moparisthebest/xeps
0.2
This commit is contained in:
stpeter
parent
dca2f95df6
commit
4a150d9452
100
xep-0267.xml
100
xep-0267.xml
|
|
@ -6,11 +6,11 @@
|
|||
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
|
||||
<xep>
|
||||
<header>
|
||||
<title>Server Rosters</title>
|
||||
<abstract>This specification defines a convention for trust between XMPP server deployments.</abstract>
|
||||
<title>Server Buddies</title>
|
||||
<abstract>This specification defines a convention for presence subscriptions between XMPP servers.</abstract>
|
||||
&LEGALNOTICE;
|
||||
<number>0267</number>
|
||||
<status>Deferred</status>
|
||||
<status>Experimental</status>
|
||||
<type>Standards Track</type>
|
||||
<sig>Standards</sig>
|
||||
<approver>Council</approver>
|
||||
|
|
@ -45,6 +45,12 @@
|
|||
<email>mwild1@gmail.com</email>
|
||||
<jid>mwild1@jaim.at</jid>
|
||||
</author>
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2011-12-09</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Defined ad-hoc command for admin generation of outbound presence subscription; added security considerations.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.1</version>
|
||||
<date>2009-04-30</date>
|
||||
|
|
@ -60,16 +66,16 @@
|
|||
</header>
|
||||
|
||||
<section1 topic='Description' anchor='description'>
|
||||
<p>In XMPP, rosters and presence subscriptions have been used to date only among IM users (see &xmppim;). However, nothing prevents the application of these concepts to other XMPP entities, such as components and servers. Given that a presence subscription typically indicates some level of trust in a peer, server deployments can use the sharing of XMPP presence information as a way to indicate that a given server has a trust relationship with a peer server. The server might then share certain kinds of additional information only with trusted peers, for example &xep0268;.</p>
|
||||
<p>To establish a trust relationship with a peer, a server shall send a presence subscription request to the peer, just as is done between XMPP users.</p>
|
||||
<p>In XMPP, rosters and presence subscriptions have been used to date only among IM users (see &xmppim;). However, nothing prevents the application of these concepts to other XMPP entities, such as components and servers. Given that a presence subscription typically indicates some level of trust in a peer, server deployments can use the sharing of XMPP presence information as a way to indicate that a given server has a trust relationship with a peer server (informally, we can say that the two servers consider each other "buddies"). The server might then share certain kinds of additional information only with its trusted peers, for example &xep0268;.</p>
|
||||
<p>To establish such a trust relationship with a peer, a server sends a presence subscription request to the peer, just as is done between XMPP users.</p>
|
||||
<example caption="Service sends subscription request to peer"><![CDATA[
|
||||
<presence from='montague.lit'
|
||||
to='capulet.lit'
|
||||
type='subscribe'/>
|
||||
]]></example>
|
||||
<p>A server MUST NOT send such a presence subscription request unless explicitly requested to do so by the server administrator(s).</p>
|
||||
<p>Upon receiving such a presence subscription request, the XMPP server software running at the peer MUST prompt the server administrator(s) to approve the request, rather than automatically approving it. Methods for doing so are out of scope for this specification.</p>
|
||||
<p>If the server administrator(s) approve the request, the peer server shall then inform the originating server that the request has been approved.</p>
|
||||
<p>A server MUST NOT send such a presence subscription request unless explicitly requested to do so by a server administrator (see below).</p>
|
||||
<p>Upon receiving such a presence subscription request, the XMPP server software running at the peer shall either prompt the server administrator to approve the request or (if explicitly configured to accept subscriptions requests) automatically approve it. (A future version of this specification might define an approval method based on &xep0004;.)</p>
|
||||
<p>If the request is approved, the peer server then informs the originating server that the request has been approved.</p>
|
||||
<example caption="Peer sends approval to server"><![CDATA[
|
||||
<presence from='capulet.lit'
|
||||
to='montague.lit'
|
||||
|
|
@ -84,8 +90,84 @@
|
|||
<p>If an XMPP server implementation supports this usage of presence subscriptions, it MUST keep a list of approved entities, which we denote a "server roster". The implementation MAY use that roster for access control purposes defined in other specifications.</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Ad-Hoc Command' anchor='command'>
|
||||
<p>This section defines an &xep0050; node scoped by the &xep0068; FORM_TYPE specified in &xep0133;. Upon advancement of this specification to Draft, this section ought to be moved to XEP-0133.</p>
|
||||
<p>The command node for this use case SHOULD be "http://jabber.org/protocol/admin#server-buddy".</p>
|
||||
<p>A sample protocol flow for this use case is shown below.</p>
|
||||
<example caption='Admin Subscribes Server to Peer Server'><![CDATA[
|
||||
<iq from='bard@shakespeare.lit/globe'
|
||||
id='server-buddy-1'
|
||||
to='shakespeare.lit'
|
||||
type='set'
|
||||
xml:lang='en'>
|
||||
<command xmlns='http://jabber.org/protocol/commands'
|
||||
action='execute'
|
||||
node='http://jabber.org/protocol/admin#server-buddy'/>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p>Unless an error occurs (see the "Error Handling" section of XEP-0133), the service SHOULD return the appropriate form.</p>
|
||||
<example caption='Service Returns Server Buddy Form to Admin'><![CDATA[
|
||||
<iq from='shakespeare.lit'
|
||||
id='server-buddy-1'
|
||||
to='bard@shakespeare.lit/globe'
|
||||
type='result'
|
||||
xml:lang='en'>
|
||||
<command xmlns='http://jabber.org/protocol/commands'
|
||||
node='http://jabber.org/protocol/admin#server-buddy'
|
||||
sessionid='server-buddy:20040408T0337Z'
|
||||
status='executing'>
|
||||
<x xmlns='jabber:x:data' type='form'>
|
||||
<title>Subscribing to a Peer Server</title>
|
||||
<instructions>Fill out this form to subscribe your server to a peer server.</instructions>
|
||||
<field type='hidden' var='FORM_TYPE'>
|
||||
<value>http://jabber.org/protocol/admin</value>
|
||||
</field>
|
||||
<field label='The Jabber ID for the peer server'
|
||||
type='jid-single'
|
||||
var='accountjid'>
|
||||
<required/>
|
||||
</field>
|
||||
</x>
|
||||
</command>
|
||||
</iq>
|
||||
]]></example>
|
||||
<example caption='Admin Submits Server Buddy Form to Service'><![CDATA[
|
||||
<iq from='bard@shakespeare.lit/globe'
|
||||
id='server-buddy-2'
|
||||
to='shakespeare.lit'
|
||||
type='set'
|
||||
xml:lang='en'>
|
||||
<command xmlns='http://jabber.org/protocol/commands'
|
||||
node='http://jabber.org/protocol/admin#server-buddy'
|
||||
sessionid='server-buddy:20040408T0337Z'>
|
||||
<x xmlns='jabber:x:data' type='submit'>
|
||||
<field type='hidden' var='FORM_TYPE'>
|
||||
<value>http://jabber.org/protocol/admin</value>
|
||||
</field>
|
||||
<field var='accountjid'>
|
||||
<value>marlowe.lit</value>
|
||||
</field>
|
||||
</x>
|
||||
</command>
|
||||
</iq>
|
||||
]]></example>
|
||||
<example caption='Service Informs Admin of Completion'><![CDATA[
|
||||
<iq from='shakespeare.lit'
|
||||
id='server-buddy-2'
|
||||
to='bard@shakespeare.lit/globe'
|
||||
type='result'
|
||||
xml:lang='en'>
|
||||
<command xmlns='http://jabber.org/protocol/commands'
|
||||
node='http://jabber.org/protocol/admin#server-buddy'
|
||||
sessionid='server-buddy:20040408T0337Z'
|
||||
status='completed'/>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p>Notification of completion MAY include the processed data in a data form of type "result".</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Security Considerations' anchor='security'>
|
||||
<p>To follow.</p>
|
||||
<p>Because server "buddies" might be granted greater privileges than unknown peers, care should be taken in sending or approving presence subscription requests.</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='IANA Considerations' anchor='iana'>
|
||||
|
|
|
|||
Loading…
Reference in New Issue