RFC Errata
Found 4 records.
Status: Verified (4)
RFC 6890, "Special-Purpose IP Address Registries", April 2013
Note: This RFC has been updated by RFC 8190
Source of RFC: IETF - NON WORKING GROUPArea Assignment: int
Errata ID: 3921
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Masataka MAWATARI
Date Reported: 2014-03-17
Verifier Name: Ted Lemon
Date Verified: 2014-03-18
Section 2.2.3 says:
+----------------------+----------------+
| Attribute | Value |
+----------------------+----------------+
| Address Block | 2001::/32 |
| Name | TEREDO |
| RFC | [RFC4380] |
| Allocation Date | January 2006 |
| Termination Date | N/A |
| Source | True |
| Destination | True |
| Forwardable | True |
| Global | False |
| Reserved-by-Protocol | False |
+----------------------+----------------+
Table 23: TEREDO
It should say:
+----------------------+----------------+
| Attribute | Value |
+----------------------+----------------+
| Address Block | 2001::/32 [3] |
| Name | TEREDO |
| RFC | [RFC4380] |
| Allocation Date | January 2006 |
| Termination Date | N/A |
| Source | True |
| Destination | True |
| Forwardable | True |
| Global | N/A [3] |
| Reserved-by-Protocol | False |
+----------------------+----------------+
[3] See [RFC4380] for details.
Table 23: TEREDO
Notes:
I think we can treat TEREDO(2001::/32) in the same way as 6to4 (2002::/16). Because both prefixes are used as the anycast prefix in the internet.
Suitable value of TEREDO is N/A that is the same value of 6to4.
So the global scope of TEREDO prefix (2001::/32) is not false.
If there is no TEREDO prefix(2001::/32) globally, the IPv6 packets from IPv6 host can't get to TEREDO relay router.
Errata ID: 6404
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Thomas
Date Reported: 2021-01-21
Verifier Name: Éric Vyncke
Date Verified: 2021-02-01
Section 2.2.2 says:
+----------------------+----------------------------+
| Attribute | Value |
+----------------------+----------------------------+
| Address Block | 0.0.0.0/8 |
| Name | "This host on this network"|
| RFC | [RFC1122], Section 3.2.1.3 |
| Allocation Date | September 1981 |
| Termination Date | N/A |
| Source | True |
| Destination | False |
| Forwardable | False |
| Global | False |
| Reserved-by-Protocol | True |
+----------------------+----------------------------+
Table 1: "This host on this network"
It should say:
+----------------------+----------------------------+
| Attribute | Value |
+----------------------+----------------------------+
| Address Block | 0.0.0.0/8 |
| Name | "This network" |
| RFC | [RFC0791], Section 3.2 |
| Allocation Date | September 1981 |
| Termination Date | N/A |
| Source | True |
| Destination | False |
| Forwardable | False |
| Global | False |
| Reserved-by-Protocol | True |
+----------------------+----------------------------+
Table 1.a: "This network"
+----------------------+----------------------------+
| Attribute | Value |
+----------------------+----------------------------+
| Address Block | 0.0.0.0/32 |
| Name | "This host on this network"|
| RFC | [RFC1122], Section 3.2.1.3 |
| Allocation Date | September 1981 |
| Termination Date | N/A |
| Source | True |
| Destination | False |
| Forwardable | False |
| Global | False |
| Reserved-by-Protocol | True |
+----------------------+----------------------------+
Table 1.b: "This host on this network"
Notes:
RFC1122 states that 0.0.0.0/32 is "this host on this network" while 0.0.0.0/8 is "this network".
---- Verifier note ----
After discussions with the authors, the original table must be split into TWO tables one for 0.0.0.0/8 and one for 0.0.0.0/32. IANA registry must also be updated.
Errata ID: 6881
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Eugene Adell
Date Reported: 2022-03-14
Verifier Name: RFC Editor
Date Verified: 2022-03-14
Section 2.2.2 says:
Tables 1 though 16, below, represent entries with which IANA has initially populated the IPv4 Special-Purpose Address Registry.
It should say:
Tables 1 through 16, below, represent entries with which IANA has initially populated the IPv4 Special-Purpose Address Registry.
Notes:
obvious typo on word "through"
Errata ID: 6882
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Eugene Adell
Date Reported: 2022-03-14
Verifier Name: RFC Editor
Date Verified: 2022-03-14
Section 2.2.3 says:
Tables 17 through 28, below, represent entries with which the IANA has initially populated the IPv6 Special-Purpose Address Registry.
It should say:
Tables 17 through 29, below, represent entries with which the IANA has initially populated the IPv6 Special-Purpose Address Registry.
Notes:
The last table (29) entry was populated at the same time than some others (loopback for example, RFC 4291)