mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-28 12:12:22 -05:00
1.1 published
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@598 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
parent
27635c0a45
commit
a037ddd440
31
xep-0092.xml
31
xep-0092.xml
@ -23,22 +23,22 @@
|
|||||||
</schemaloc>
|
</schemaloc>
|
||||||
&stpeter;
|
&stpeter;
|
||||||
<revision>
|
<revision>
|
||||||
<version>1.1pre1</version>
|
<version>1.1</version>
|
||||||
<date>in progress, last updated 2007-02-08</date>
|
<date>2007-02-15</date>
|
||||||
<initials>psa</initials>
|
<initials>psa</initials>
|
||||||
<remark>Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; recommended use of Entity Capabilities instead of Software Version when presence information is available; added proviso to security considerations regarding disclosure of operating system information.</remark>
|
<remark><p>Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; recommended use of Entity Capabilities instead of Software Version when presence information is available; added proviso to security considerations regarding disclosure of operating system information; added section on Service Discovery.</p></remark>
|
||||||
</revision>
|
</revision>
|
||||||
<revision>
|
<revision>
|
||||||
<version>1.0</version>
|
<version>1.0</version>
|
||||||
<date>2003-10-08</date>
|
<date>2003-10-08</date>
|
||||||
<initials>psa</initials>
|
<initials>psa</initials>
|
||||||
<remark>Per a vote of the Jabber Council, changed status to Active.</remark>
|
<remark><p>Per a vote of the Jabber Council, changed status to Active.</p></remark>
|
||||||
</revision>
|
</revision>
|
||||||
<revision>
|
<revision>
|
||||||
<version>0.1</version>
|
<version>0.1</version>
|
||||||
<date>2003-05-22</date>
|
<date>2003-05-22</date>
|
||||||
<initials>psa</initials>
|
<initials>psa</initials>
|
||||||
<remark>Initial version.</remark>
|
<remark><p>Initial version.</p></remark>
|
||||||
</revision>
|
</revision>
|
||||||
</header>
|
</header>
|
||||||
<section1 topic='Introduction' anchor='intro'>
|
<section1 topic='Introduction' anchor='intro'>
|
||||||
@ -78,6 +78,27 @@
|
|||||||
]]></example>
|
]]></example>
|
||||||
<p>The standard error conditions described in &xep0086; apply (e.g., service unavailable if the entity does not support the namespace).</p>
|
<p>The standard error conditions described in &xep0086; apply (e.g., service unavailable if the entity does not support the namespace).</p>
|
||||||
</section1>
|
</section1>
|
||||||
|
<section1 topic='Determining Support' anchor='disco'>
|
||||||
|
<p>In order for a requesting entity to determine if a responding entity supports result set management, it SHOULD send a &xep0030; information request to the responding entity:</p>
|
||||||
|
<example caption='Requesting entity queries responding entity regarding protocol support'><![CDATA[
|
||||||
|
<iq from='stpeter@jabber.org/roundabout'
|
||||||
|
to='conference.jabber.org'
|
||||||
|
id='disco1'>
|
||||||
|
<query xmlns='http://jabber.org/protocol/disco#info'/>
|
||||||
|
</iq>
|
||||||
|
]]></example>
|
||||||
|
<example caption='Responding entity communicates protocol support'><![CDATA[
|
||||||
|
<iq from='conference.jabber.org'
|
||||||
|
to='stpeter@jabber.org/roundabout'
|
||||||
|
id='disco1'>
|
||||||
|
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||||
|
...
|
||||||
|
<feature var='jabber:iq:version'/>
|
||||||
|
...
|
||||||
|
</query>
|
||||||
|
</iq>
|
||||||
|
]]></example>
|
||||||
|
</section1>
|
||||||
<section1 topic='Security Considerations' anchor='security'>
|
<section1 topic='Security Considerations' anchor='security'>
|
||||||
<p>Revealing the application's underlying operating system may open the user or system to attacks directed against that operating system; therefore, an application MUST provide a way for a human user or administrator to disable sharing of information about the operating system.</p>
|
<p>Revealing the application's underlying operating system may open the user or system to attacks directed against that operating system; therefore, an application MUST provide a way for a human user or administrator to disable sharing of information about the operating system.</p>
|
||||||
</section1>
|
</section1>
|
||||||
|
Loading…
Reference in New Issue
Block a user