From 360de1eed61bc733acd471710cb881e102a7e2e2 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 20 Nov 2007 02:49:38 +0000 Subject: [PATCH] 1.5pre8 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1403 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0115.xml | 28 ++++++++-------------------- 1 file changed, 8 insertions(+), 20 deletions(-) diff --git a/xep-0115.xml b/xep-0115.xml index adf95b98..ecf611e6 100644 --- a/xep-0115.xml +++ b/xep-0115.xml @@ -28,10 +28,10 @@ &stpeter; &remko; - 1.5pre7 - 2007-11-08 + 1.5pre8 + in progress, last updated 2007-11-19 jjh/psa -

Required inclusion of the hash attribute in non-legacy mode; removed schema default for hash attribute; clarified meaning of node attribute; further specified security considerations; clarified handling of the legacy format to assist developers.

+

Removed hash attribute since only SHA-1 is used; clarified meaning of node attribute; further specified security considerations; clarified handling of the legacy format to assist developers.

1.4 @@ -126,8 +126,7 @@ ]]> @@ -159,8 +158,7 @@ ]]> @@ -169,7 +167,6 @@ @@ -178,8 +175,7 @@ ]]> @@ -225,11 +221,6 @@ A set of nametokens specifying additional feature bundles; this attribute is deprecated (see the Legacy Format section of this document). DEPRECATED - - hash - The hashing algorithm used in generated the 'ver' attribute (see &ianahashes;). The value SHOULD be "sha-1". - REQUIRED - node A unique identifier for the software underlying the entity, typically a URL at the website of the project or company that produces the software. * @@ -275,8 +266,7 @@ ]]> @@ -321,7 +311,6 @@ @@ -400,7 +389,6 @@ - @@ -426,7 +414,7 @@
  • When receiving caps information from a legacy entity, an application SHOULD check the 'node', 'ver', and 'ext' combinations as specified in the archived version 1.3 of this specification, and MAY cache the results.
  • When sending a disco#info request to a legacy entity, an application SHOULD send the request to the entity's JID with a service discovery node of "node#ver".
  • -

    If an application does not support the legacy format, it SHUOLD proceed as follows:

    +

    If an application does not support the legacy format, it SHOULD proceed as follows:

    • When receiving caps information from a legacy entity, an application SHOULD ignore the 'ver' value entirely (since it cannot be verified) and SHOULD NOT cache it, since the application cannot validate the identity and features by checking the hash.
    • When sending a disco#info request to a legacy entity, an application SHOULD send the request to the entity's JID without a service discovery node of "node#ver".