RFC Errata
RFC 5135, "IP Multicast Requirements for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT)", February 2008
Source of RFC: behave (tsv)
Errata ID: 1319
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-02-14
Held for Document Update by: Magnus Westerlund
Section 4.1, pg.6 says:
REQ-7: The NAT MUST NOT forward Local Network Control Block | (224.0.0/24) [RFC3171] (also known as "link-local multicast") traffic from its 'inside' interface(s) to its 'outside' interface.
It should say:
REQ-7: The NAT MUST NOT forward Local Network Control Block | (224.0.0.0/24) [RFC3171] (also known as "link-local multicast") traffic from its 'inside' interface(s) to its 'outside' interface.
Notes:
Location is end of Section 4.1, near the bottom of page 6.
This correction also needs to be applied to the re-statement
of REQ-7 in Section 5 (mid-page 10).
Rationale:
The basic "strategic" document for CIDR notation now is BCP 122,
RFC 4632, and that document clearly states (in section 3.1, at
the bottom of page 5):
vvvvvvv
| [...] In CIDR notation, a prefix is shown as a 4-octet
quantity, just like a traditional IPv4 address or network number,
followed by the "/" (slash) character, followed by a decimal value
between 0 and 32 that describes the number of significant bits.
Also being a BCP, RFC 5135 should follow this rule.