RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Held for Document Update (1)

RFC 6761, "Special-Use Domain Names", February 2013

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 5039

Status: Held for Document Update
Type: Editorial

Reported By: Walter H.
Date Reported: 2017-06-12
Held for Document Update by: Warren Kumari
Date Held: 2017-06-12

Section 6.1 says:

   The private-address [RFC1918] reverse-mapping domains listed below,
   and any names falling within those domains, are Special-Use Domain
   Names:

     10.in-addr.arpa.      21.172.in-addr.arpa.  26.172.in-addr.arpa.
     16.172.in-addr.arpa.  22.172.in-addr.arpa.  27.172.in-addr.arpa.
     17.172.in-addr.arpa.  30.172.in-addr.arpa.  28.172.in-addr.arpa.
     18.172.in-addr.arpa.  23.172.in-addr.arpa.  29.172.in-addr.arpa.
     19.172.in-addr.arpa.  24.172.in-addr.arpa.  31.172.in-addr.arpa.
     20.172.in-addr.arpa.  25.172.in-addr.arpa.  168.192.in-addr.arpa.

It should say:

   The private-address [RFC1918] reverse-mapping domains listed below,
   and any names falling within those domains, are Special-Use Domain
   Names:

     10.in-addr.arpa.      21.172.in-addr.arpa.  27.172.in-addr.arpa.
     16.172.in-addr.arpa.  22.172.in-addr.arpa.  28.172.in-addr.arpa.
     17.172.in-addr.arpa.  23.172.in-addr.arpa.  29.172.in-addr.arpa.
     18.172.in-addr.arpa.  24.172.in-addr.arpa.  30.172.in-addr.arpa.
     19.172.in-addr.arpa.  25.172.in-addr.arpa.  31.172.in-addr.arpa.
     20.172.in-addr.arpa.  26.172.in-addr.arpa.  168.192.in-addr.arpa.

Notes:

the original list is not correctly ordered, therefore is Errata-ID 5025 obsolete: this said that 30.172.in-addr.arpa. were missing in the original list.

Status: Rejected (2)

RFC 6761, "Special-Use Domain Names", February 2013

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 4970

Status: Rejected
Type: Technical

Reported By: Alexander Lay
Date Reported: 2017-03-15
Rejected by: Warren Kumari
Date Rejected: 2017-06-12

Section 6.1 says:

168.192.in-addr.arpa.

It should say:

192.168.in-addr.arpa.

Notes:

The IP address ranges listed in this document as private do not align with those listed as private in the referenced RFC 1918.
--VERIFIER NOTES--
Nope, there are in "reverse lookup" format.


The useful references are probably:
https://tools.ietf.org/html/rfc1033 Section IN-ADDR.ARPA and
https://tools.ietf.org/html/rfc6303 Section 4.1. RFC 1918 Zones.

More info (from rfc1033):
IN-ADDR.ARPA

The structure of names in the domain system is set up in a
hierarchical way such that the address of a name can be found by
tracing down the domain tree contacting a server for each label of
the name. Because of this 'indexing' based on name, there is no easy
way to translate a host address back into its host name.

In order to do the reverse translation easily, a domain was created
that uses hosts' addresses as part of a name that then points to the
data for that host. In this way, there is now an 'index' to hosts'
RRs based on their address. This address mapping domain is called
IN-ADDR.ARPA. Within that domain are subdomains for each network,
based on network number. Also, for consistency and natural
groupings, the 4 octets of a host number are reversed.

For example, the ARPANET is net 10. That means there is a domain
called 10.IN-ADDR.ARPA. Within this domain there is a PTR RR at
51.0.0.10.IN-ADDR that points to the RRs for the host SRI-NIC.ARPA
(who's address is 10.0.0.51). Since the NIC is also on the MILNET
(Net 26, address 26.0.0.73), there is also a PTR RR at 73.0.0.26.IN-
ADDR.ARPA that points to the same RR's for SRI-NIC.ARPA. The format
of these special pointers is defined below along with the examples
for the NIC.

PTR

<special-name> [<ttl>] [<class>] PTR <name>

The PTR record is used to let special names point to some other
location in the domain tree. They are mainly used in the IN-
ADDR.ARPA records for translation of addresses to names. PTR's
should use official names and not aliases.

For example, host SRI-NIC.ARPA with addresses 10.0.0.51 and 26.0.0.73
would have the following records in the respective zone files for net
10 and net 26:

51.0.0.10.IN-ADDR.ARPA. PTR SRI-NIC.ARPA.
73.0.0.26.IN-ADDR.ARPA. PTR SRI-NIC.ARPA.

Errata ID: 5025

Status: Rejected
Type: Technical

Reported By: Michael Kohl
Date Reported: 2017-05-25
Rejected by: Warren Kumari
Date Rejected: 2017-06-12

Section 6.1 says:

   The private-address [RFC1918] reverse-mapping domains listed below,
   and any names falling within those domains, are Special-Use Domain
   Names:

     10.in-addr.arpa.      21.172.in-addr.arpa.  26.172.in-addr.arpa.
     16.172.in-addr.arpa.  22.172.in-addr.arpa.  27.172.in-addr.arpa.
     17.172.in-addr.arpa.  30.172.in-addr.arpa.  28.172.in-addr.arpa.
     18.172.in-addr.arpa.  23.172.in-addr.arpa.  29.172.in-addr.arpa.
     19.172.in-addr.arpa.  24.172.in-addr.arpa.  31.172.in-addr.arpa.
     20.172.in-addr.arpa.  25.172.in-addr.arpa.  168.192.in-addr.arpa.

It should say:

   The private-address [RFC1918] reverse-mapping domains listed below,
   and any names falling within those domains, are Special-Use Domain
   Names:

     10.in-addr.arpa.      21.172.in-addr.arpa.  26.172.in-addr.arpa.
     16.172.in-addr.arpa.  22.172.in-addr.arpa.  27.172.in-addr.arpa.
     17.172.in-addr.arpa.  30.172.in-addr.arpa.  28.172.in-addr.arpa.
     18.172.in-addr.arpa.  23.172.in-addr.arpa.  29.172.in-addr.arpa.
     19.172.in-addr.arpa.  24.172.in-addr.arpa.  30.172.in-addr.arpa.
     20.172.in-addr.arpa.  25.172.in-addr.arpa.  31.172.in-addr.arpa.
     168.192.in-addr.arpa

Notes:

30.172.in-addr.arpa. is missing in the original list.
--VERIFIER NOTES--
Actually, as noted in Errata ID: 5039 it's not missing - it is between 22.172.in-addr.arpa and 23.172.in-addr.arpa. I've marked Errata 5039 as "Held for update" and am rejecting this one.

Report New Errata