RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (1)

RFC 7622, "Extensible Messaging and Presence Protocol (XMPP): Address Format", September 2015

Source of RFC: xmpp (art)

Errata ID: 4560

Status: Verified
Type: Editorial

Reported By: Peter Saint-Andre
Date Reported: 2015-12-07
Verifier Name: Barry Leiba
Date Verified: 2015-12-12

Section 3.5 says:

   | 18| <juliet@example.com/ foo>    | Leading space in resourcepart |

It should say:

[nothing]

Notes:

Example 18 is wrong because a leading space is currently allowed by RFC 7622 (at least, it is not disallowed by the OpaqueString profile defined in RFC 7613). It is true that leading and trailing spaces are disallowed by the Nickname profile, but we do not reference that here. This example should be removed in any updates to RFC 7622.

Status: Reported (1)

RFC 7622, "Extensible Messaging and Presence Protocol (XMPP): Address Format", September 2015

Source of RFC: xmpp (art)

Errata ID: 4534

Status: Reported
Type: Editorial

Reported By: Sam Whited
Date Reported: 2015-11-14

Section 3.2.2 says:


   An entity that performs enforcement in XMPP domainpart slots MUST
   prepare a string as described in Section 3.2.1 and MUST also apply
   the normalization, case-mapping, and width-mapping rules defined in
   [RFC5892].

It should say:


  An entity that performs enforcement in XMPP domainpart slots MUST
  prepare a string as described in Section 3.2.1 and MUST also apply
  the normalization, case-mapping, and width-mapping rules defined in
  [RFC5895].

Notes:

RFC 5892 is just a list of codepoints; the rules which it is referring too (and which are referred too in the ABNF and othe places in the document) are in RFC 5895.

Status: Held for Document Update (1)

RFC 7622, "Extensible Messaging and Presence Protocol (XMPP): Address Format", September 2015

Source of RFC: xmpp (art)

Errata ID: 4470

Status: Held for Document Update
Type: Editorial

Reported By: Stéphane Bortzmeyer
Date Reported: 2015-09-10
Held for Document Update by: Ben Campbell
Date Held: 2015-09-12

Section 3.5 says:

<king@example.com/&#x265A>;

It should say:

<king@example.com/&#x265A;>

Notes:

Right angle bracket arrived too soon.

Report New Errata



Search RFCs
Advanced Search
×