RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (1)

RFC 6762, "Multicast DNS", February 2013

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

Errata ID: 4977

Status: Reported
Type: Technical

Reported By: Nathan Osman
Date Reported: 2017-03-23

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."

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

Status: Rejected (1)

RFC 6762, "Multicast DNS", February 2013

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

Errata ID: 4529

Status: Rejected
Type: Technical

Reported By: Willem Bermon
Date Reported: 2015-11-11
Rejected by: Brian Haberman
Date Rejected: 2016-04-05

Section Appendix G says:

We do not recommend use of unregistered top-level
   domains at all, but should network operators decide to do this, the
   following top-level domains have been used on private internal
   networks without the problems caused by trying to reuse ".local." for
   this purpose:

      .intranet.
      .internal.
      .private.
      .corp.
      .home.
      .lan.

It should say:

We do not recommend use of unregistered top-level domains.

Notes:

Since TLDs like .private are currently available for register. Appendix G is outdated and I would strongly advise the IETF to remove the suggested TLDs since they are no longer problem free. I believe that it is wise to make a harder statement in the RFC.
--VERIFIER NOTES--
During the development of this RFC, the text is consistent with the consensus of the community. Later developments by ICANN superseded the appendix, but that is not applicable for an erratum. Updates to the text should be proposed via the draft publication process.

Report New Errata



Search RFCs
Advanced Search
×