Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

RFC 6762, "Multicast DNS", February 2013

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

---

Errata ID: 4977
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Nathan Osman
Date Reported: 2017-03-23
Held for Document Update by: Éric Vyncke
Date Held: 2024-01-12

Section 6.1 says:

The 'Next Domain Name' field contains the record's own name. When
used with name compression, this means that the 'Next Domain Name'
field always takes exactly two bytes in the message.

It should say:

The 'Next Domain Name' field contains the record's own name.

Notes:

Section 4.1.1 of RFC 4034 states:

"A sender MUST NOT use DNS name compression on the Next Domain Name
field when transmitting an NSEC RR."

--- Verifier note ---
While errata submitter's concern is valid, this is not a stricto sensu "errata" as the existing RFC reflects the WG consensus at the publication time.


In order to comply with the existing RFC, name compression should not
be suggested.

Report New Errata