Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

RFC 6296, "IPv6-to-IPv6 Network Prefix Translation", June 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: ops
See Also: RFC 6296 w/ inline errata

---

Errata ID: 3033
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Marek Kopecký
Date Reported: 2011-11-21
Verifier Name: ron bonica
Date Verified: 2011-12-06

Section 3.6 says:

So, the value 0xD550 is written in the 16-bit subnet area,
resulting in a mapped external address of 2001:0DB8:0001:D550::1234.

When a response datagram is received, it will contain the destination
address 2001:0DB8:0001:D550::0001, which will be mapped back to
FD01:0203:0405:0001::1234 using the inverse mapping algorithm.

It should say:

So, the value 0xD550 is written in the 16-bit subnet area,
resulting in a mapped external address of 2001:0DB8:0001:D550::1234.

When a response datagram is received, it will contain the destination
address 2001:0DB8:0001:D550::1234, which will be mapped back to
FD01:0203:0405:0001::1234 using the inverse mapping algorithm.

Notes:

PC sends the packet with Ipv6 source address 2001:0DB8:0001:D550::1234. When a response datagram is received, it must contain the destination address 2001:0DB8:0001:D550::1234.

Report New Errata