RFC 7599, "Mapping of Address and Port using Translation (MAP-T)", July 2015

Errata ID: 8063
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Scott Freemire
Date Reported: 2024-08-02
Held for Document Update by: RFC Editor
Date Held: 2024-08-02

Section 5 says:

The MAP-T algorithmic mapping rules are identical to those in
Section 5(link #1) of the MAP-E specification [RFC7597](link #2), with the following
exception: the forwarding of traffic to and from IPv4 destinations
outside a MAP-T domain is to be performed as described in this
document, instead of Section 5.4(link #3) of the MAP-E specification.

link #1: https://datatracker.ietf.org/doc/html/rfc7599#section-5
link #2: https://datatracker.ietf.org/doc/html/rfc7597
link #3: https://datatracker.ietf.org/doc/html/rfc7599#section-5.4

It should say:

The MAP-T algorithmic mapping rules are identical to those in
Section 5(link #1) of the MAP-E specification [RFC7597](link #2), with the following
exception: the forwarding of traffic to and from IPv4 destinations
outside a MAP-T domain is to be performed as described in this
document, instead of Section 5.4(link #3) of the MAP-E specification.

link #1: https://datatracker.ietf.org/doc/html/rfc7597#section-5
link #2: https://datatracker.ietf.org/doc/html/rfc7597
link #3: https://datatracker.ietf.org/doc/html/rfc7597#section-5.4

Notes:

The text in section 5 is correct, but 2 of the URL links are incorrect.
All links in section 5 should point to RFC7597.

--VERIFIER NOTES--
This is regarding the link generated in the rfc2html output, not the RFC itself (https://www.rfc-editor.org/rfc/rfc7599.txt).

Report New Errata