RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (2)

RFC 7600, "IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)", July 2015

Source of RFC: softwire (int)

Errata ID: 4430

Status: Verified
Type: Editorial

Reported By: Michelle Cotton
Date Reported: 2015-07-28
Verifier Name: RFC Editor
Date Verified: 2015-07-28

Section 6 says:

(need to add the below text)

It should say:

This address is to be used only as IPv4 source of an ICMP error 
packet whose cause originated within a tunnel across an IPv6-only 
domain. As such, it should never be used as a destination 
(and consequently never forwarded). When receiving an IPv4 
packet with this address as source, no specific action that would 
reserve this address for this protocol is required (dealing as usual 
with the error cause specified in the ICMP packet is sufficient).


Notes:

While processing the IANA Actions for this document, the authors requested that the above text be added to the IANA Considerations section. The published version does not include this text.

Verifier Notes: The RFC Editor missed adding this text per the message from the IANA.

Errata ID: 4661

Status: Verified
Type: Editorial

Reported By: Masao Uebayashi
Date Reported: 2016-04-10
Verifier Name: Terry Manderson
Date Verified: 2016-05-12

Section 3 says:

BR(s) and/or N4T64+

It should say:

BR(s) and/or NAT64+

Notes:

A minor typo in Figure 1 (s/N4T64+/NAT64+/).

Report New Errata