moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-08-13 16:53:48 -04:00
Code Issues Releases Wiki Activity

conformance language tweak

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3121 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-05-05 20:38:14 +00:00
parent 5fa4180f10
commit 1d274600c5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xep-0199.xml
View File

@ -201,7 +201,7 @@
id='comp1'
type='result'/>
]]></example>
<p>If the pinged entity does not support the ping namespace, it MUST return a &unavailable; error:</p>
<p>If the pinged entity does not support the ping namespace, <cite>RFC 3920</cite> requires it to return a &unavailable; error:</p>
<example caption="Ping Not Supported"><![CDATA[
<iq from='juliet@capulet.lit/chamber'
to='chat.shakespeare.lit'
@ -242,7 +242,7 @@
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>If a server receives a ping request directed to a full JID &LOCALFULL; associated with a registered account but there is no connected resource matching the 'to' address, it MUST reply with a &unavailable; error and set the 'from' address of the IQ-error to the full JID provided in the 'to' address of the ping request. If a connected resource receives a ping request but it does not want to reveal its network availability to the sender for any reason (e.g., because the sender is not authorized to know the connected resource's availability), then it too MUST reply with a &unavailable; error. This consistency between the server response and the client response helps to prevent presence leaks.</p>
<p>If a server receives a ping request directed to a full JID &LOCALFULL; associated with a registered account but there is no connected resource matching the 'to' address, <cite>RFC 3920</cite> requires it to reply with a &unavailable; error and set the 'from' address of the IQ-error to the full JID provided in the 'to' address of the ping request. If a connected resource receives a ping request but it does not want to reveal its network availability to the sender for any reason (e.g., because the sender is not authorized to know the connected resource's availability), then it too MUST reply with a &unavailable; error. This consistency between the server response and the client response helps to prevent presence leaks.</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>