| CARVIEW |
Select Language
HTTP/2 200
date: Sun, 12 Oct 2025 03:14:33 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=b832a46as776i7jiqiurpa17tc; path=/
set-cookie: __cf_bm=VqurPxg1rX7pK_iq98JvTsTqW9MpHIfenj6AsUakHwg-1760238873-1.0.1.1-_P8vLRGBs86u6y6ZilUIyflkTqOKsRO16adynv37L1gGsJf_3VIUYn.jwT7nU83lbvD4A.Xs6d8pCBqlixy7a7Q8xjqOvjSaxLQDGJ2xscY; path=/; expires=Sun, 12-Oct-25 03:44:33 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: 98d36d7aae3fc195-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: Held for Document Update (1)
RFC 7934, "Host Address Availability Recommendations", July 2016
Source of RFC: v6ops (ops)
Errata ID: 4806
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Mark Smith
Date Reported: 2016-09-20
Held for Document Update by: Joel Jaeggli
Date Held: 2017-03-29
Section 3 says:
3. Benefits of Providing Multiple Addresses
Today, there are many host functions that require more than one IP
address to be available to the host, including:
o Privacy addressing to prevent tracking by off-network hosts
[RFC4941].
...
It should say:
3. Benefits of Providing Multiple Addresses
Today, there are many host functions that require more than one IP
address to be available to the host, including:
o Privacy addressing to prevent tracking by off-network hosts
[RFC4941].
...
o Other potential use cases such as those described in [RFC1681].
Notes:
Somewhat trivial errata, a reference to RFC1681, " On Many Addresses per Host", would be good to credit Steve's early thoughts, and those which probably in part lead to [TARP]. No urgency to update, a note to include it if this RFC is ever updated.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us