RFC Errata
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
See Also: RFC 6890 w/ inline errata
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.