From f65def7bc3abd962da9942f9374f12a36321b2eb Mon Sep 17 00:00:00 2001 From: "Matthew A. Miller" Date: Fri, 20 Jun 2014 10:00:07 -0600 Subject: [PATCH] XEP-0030 v2.4rc1: errata reported on standards@ regarding subscriptions and available resources --- xep-0030.xml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/xep-0030.xml b/xep-0030.xml index aaf45385..245599c1 100644 --- a/xep-0030.xml +++ b/xep-0030.xml @@ -13,6 +13,7 @@ Final Standards Track Standards + XMPP Core @@ -35,6 +36,12 @@ &pgmillard; &reatmon; &stpeter; + + 2.4rc1 + 2014-06-20 + editor(mam) +

Errata submitted to standards@ regarding subscriptions and returned items.

 + 2.4 2008-06-06 @@ -674,14 +681,14 @@

In response to a disco#info request, the server MUST return a &unavailable; error if one of the following is true:

  1. The target entity does not exist (no matter if the request specifies a node or not).
    2. -
  2. The requesting entity is not authorized to receive presence from the target entity (i.e., via a presence subscription of type "both" or "from") or is not otherwise trusted (e.g., another server in a trusted network).
    3. +
  3. The requesting entity is not authorized to receive presence from the target entity (i.e., via the target having a presence subscription to the requesting entity of type "both" or "from") or is not otherwise trusted (e.g., another server in a trusted network).

  • In response to a disco#items request, the server MUST return an empty result set if:

    1. The target entity does not exist (no matter if the request specifies a node or not).
      2. -
    2. The request did not specify a node, the only items are available resources (as defined in RFC 3921), and the requesting entity is not authorized to receive presence from the target entity (i.e., via a presence subscription of type "both" or "from") or is not otherwise trusted (e.g., another server in a trusted network). However, the server MAY return items other than available resources (if any).
      3. +
    3. The request did not specify a node, the only items are available resources (as defined in RFC 3921), and the requesting entity is not authorized to receive presence from the target entity (i.e., via the target having a presence subscription to the requesting entity of type "both" or "from") or is not otherwise trusted (e.g., another server in a trusted network). However, the server MAY return items other than available resources (if any).