RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 5 records.

Status: Verified (3)

RFC 3958, "Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)", January 2005

Note: This RFC has been updated by RFC 8553

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 2106
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Leslie Daigle
Date Reported: 2010-04-02
Verifier Name: Alexey Melnikov
Date Verified: 2010-04-04

Section 6.5 says: 

iana-registered-protocol  = ALPHA *31ALPHANUM

It should say:

iana-registered-protocol  = ALPHA *31ALPHANUMSYM

Notes:

Previous erratum suggested the fix was to add an ALPHANUM production, but the correct fix is to change ALPHANUM to ALPHANUMSYM in this production.

Errata ID: 8532
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Marc Petit-Huguenin
Date Reported: 2025-08-18
Verifier Name: Orie Steele
Date Verified: 2025-08-19

Section 2.2.4 says: 

"As shown in the example set above, it is possible to have multiple 
possible targets for a single application service+protocol pair."

It should say:

"It is possible to have multiple possible targets for a single 
application service+protocol pair."

Notes:

The example in section 2.2 does not contain multiple targets for a single application service+protocol pair.

Errata ID: 4451
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Frans Oilinki
Date Reported: 2015-08-19
Verifier Name: Orie Steele
Date Verified: 2024-03-29

Section 2.2 says: 

   example.com.
   ;;       order pref flags
   IN NAPTR 100   10   ""    "WP:whois++"      ( ; service
                             ""                  ; regexp
                             bunyip.example.     ; replacement
                                               )
   IN NAPTR 100   20   "s"   "WP:ldap"         ( ; service
                             ""                  ; regexp
                            _ldap._tcp.myldap.example.com. ; replacement
                                               )
   IN NAPTR 200   10   ""    "EM:protA"        ( ; service
                             ""                  ; regexp
                             someisp.example.    ; replacement
                                               )
   IN NAPTR 200   30   "a"   "EM:protB"          ; service
                             ""                  ; regexp
                             myprotB.example.com.; replacement
                                               )

It should say:

   example.com.
   ;;       order pref flags
   IN NAPTR 100   10   ""    "WP:whois++"      ( ; service
                             ""                  ; regexp
                             bunyip.example.     ; replacement
                                               )
   IN NAPTR 100   20   "s"   "WP:ldap"         ( ; service
                             ""                  ; regexp
                            _ldap._tcp.myldap.example.com. ; replacement
                                               )
   IN NAPTR 200   10   ""    "EM:protA"        ( ; service
                             ""                  ; regexp
                             someisp.example.    ; replacement
                                               )
   IN NAPTR 200   30   "a"   "EM:protB"        ( ; service
                             ""                  ; regexp
                             myprotB.example.com.; replacement
                                               )

Notes:

Not so familiar with BIND syntax, but by appearance, the last entry seems to be missing a beginning parenthesis. There is another similar omission in section 4.2 (thinkingcat.example definition, this time missing an ending parenthesis).

Status: Held for Document Update (1)

RFC 3958, "Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)", January 2005

Note: This RFC has been updated by RFC 8553

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 8533
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Marc Petit-Huguenin
Date Reported: 2025-08-18
Held for Document Update by: Orie Steele
Date Held: 2025-08-19

Section 2.2.4 says: 

"Failure" is declared, and backtracking must be used, when"

It should say:

"Failure" is declared, and backtracking must be used, when

 o  a direct or indirect loop is detected;"

Notes:

If the target is identical to the domain name of the NAPTR record, or is identical to one of the previous domain names used to reached that target, then a client will potentially loop forever.

Status: Rejected (1)

RFC 3958, "Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)", January 2005

Note: This RFC has been updated by RFC 8553

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 608
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Stéphane Bortzmeyer
Date Reported: 2007-10-17
Rejected by: Alexey Melnikov
Date Rejected: 2010-04-05

Section 6.5 says: 

iana-registered-protocol  = ALPHA *31ALPHANUM

It should say:

Maybe:

iana-registered-protocol  = ALPHA *31ALPHANUM
ALPHANUM =  ALPHA / DIGIT

Notes:

The ALPHANUM production is missing from the grammar (and is not in
RFC 4234 either).

Alexey: this was obsoleted by Erratum # 2106.

--VERIFIER NOTES--
Obsoleted by Erratum # 2106, which fixed this properly.

Report New Errata



Advanced Search