The following errata report has been submitted for RFC4632,
"Classless Inter-domain Routing (CIDR): The Internet Address Assignment and 
Aggregation Plan".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4632&eid=4194

--------------------------------------
Type: Editorial
Reported by: larry <[email protected]>

Section: 5.3

Original Text
-------------
 Systems that process route announcements must be able to verify that
   information that they receive is acceptable according to policy
   rules.  Implementations that filter route advertisements must allow
   masks or prefix lengths in filter elements.  Thus, filter elements
   that formerly were specified as

      accept 172.16.0.0
      accept 172.25.120.0.0
      accept 172.31.0.0
      deny 10.2.0.0
      accept 10.0.0.0

Corrected Text
--------------
 Systems that process route announcements must be able to verify that
   information that they receive is acceptable according to policy
   rules.  Implementations that filter route advertisements must allow
   masks or prefix lengths in filter elements.  Thus, filter elements
   that formerly were specified as

      accept 172.16.0.0
      accept 172.25.120.0
      accept 172.31.0.0
      deny 10.2.0.0
      accept 10.0.0.0

Notes
-----
the second network address has 40 bits (5 groups of numbers instead of 4-32 
bits).

172.25.120.0.0

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC4632 (draft-ietf-grow-rfc1519bis-04)
--------------------------------------
Title               : Classless Inter-domain Routing (CIDR): The Internet 
Address Assignment and Aggregation Plan
Publication Date    : August 2006
Author(s)           : V. Fuller, T. Li
Category            : BEST CURRENT PRACTICE
Source              : Global Routing Operations
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to