RFC Errata
Found 3 records.
Status: Verified (1)
RFC 2663, "IP Network Address Translator (NAT) Terminology and Considerations", August 1999
Source of RFC: nat (tsv)
Errata ID: 400
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Javier Waisbrot
Date Reported: 2002-11-14
Section 2.6 says:
the NAT device cannot safely assume that the segments containing FINs or SYNs will be the last packets of the session (i.e., there could be retransmissions).
It should say:
the NAT device cannot safely assume that the segments containing FINs or RSTs will be the last packets of the session (i.e., there could be retransmissions).
Status: Held for Document Update (1)
RFC 2663, "IP Network Address Translator (NAT) Terminology and Considerations", August 1999
Source of RFC: nat (tsv)
Errata ID: 1432
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Harald Hubich
Date Reported: 2008-05-29
Held for Document Update by: Wesley Eddy
Section 4.3. says:
b) After twice-NAT translation, in private network
SA: 200.200.200.1 DA: 172.16.1.100
It should say:
b) After twice-NAT translation, in private network
DA: 200.200.200.1 SA: 172.16.1.100
Notes:
tricky :)
Status: Rejected (1)
RFC 2663, "IP Network Address Translator (NAT) Terminology and Considerations", August 1999
Source of RFC: nat (tsv)
Errata ID: 5555
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Majid Motallebikashani
Date Reported: 2018-11-17
Rejected by: Mirja Kühlewind
Date Rejected: 2018-11-26
Section 3.3 says:
Changes to ICMP error message will include changes to the original IP packet (or portions thereof) embedded in the payload of the ICMP error message.
It should say:
Changes to ICMP error message will include changes to the original IP packet and portions of data embedded in the payload of the ICMP error message.
Notes:
IP packet is not embedded in ICMP payload, but the other way around.
--VERIFIER NOTES--
The orginal IP packet IS included in the ICMP payload.