CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 04:47:23 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=2thpv2ff8bu0o8060tifs30f04; path=/
set-cookie: __cf_bm=bq8Cz2yGZEcwKLHT218xUsNSNPNmtCWPG9sdIZ4vLqw-1759985243-1.0.1.1-yacVlRqvezqIBB7uSIgfvMvYPJRafp0ZMdb7cTbCSLNSACY8Q6o39pfLpDXEn1wuMLKxMjxX1cPuBHIQYDw5565NEcePKxul09Hot_oVtPI; path=/; expires=Thu, 09-Oct-25 05:17:23 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 98bb3d57ed6b165e-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
Found 1 record.
Status: Reported (1)
RFC 5453, "Reserved IPv6 Interface Identifiers", February 2009
Source of RFC: 6man (int)
Errata ID: 5589
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Brian Carpenter
Date Reported: 2019-01-02
Section 3 says:
+-----------------------------------------+-------------------------+ | Interface Identifier Range | Description | +-----------------------------------------+-------------------------+ | 0000:0000:0000:0000 | Subnet-Router Anycast | | | [RFC4291] | | | | | FDFF:FFFF:FFFF:FF80-FDFF:FFFF:FFFF:FFFF | Reserved Subnet Anycast | | | Addresses[RFC2526] | +-----------------------------------------+-------------------------+ Table 1: Current Assignments
It should say:
+-----------------------------------------+-------------------------+ | Interface Identifier Range | Description | +-----------------------------------------+-------------------------+ | 0000:0000:0000:0000 | Subnet-Router Anycast | | | [RFC4291] | | | | | FDFF:FFFF:FFFF:FF80-FDFF:FFFF:FFFF:FFFF | Reserved Subnet Anycast | | FFFF:FFFF:FFFF:FF80-FFFF:FFFF:FFFF:FFFF | Addresses[RFC2526] | +-----------------------------------------+-------------------------+ Table 1: Current Assignments
Notes:
Both these ranges are in fact reserved by Section 2 of RFC2526. Under current recommendations [RFC7217] the FDFF range is no longer recommended for routine use, and the FFFF range is equally likely to occur in a pseudo-random 64-bit IID. Credit to Kerry Lynn for pointing this out.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us