Subject: [mpls] [Errata Rejected] RFC3107 (4500)

From: RFC Errata System <[email-masked]>
Date: Thu, 11 Feb 2016 15:38:04 -0800 (PST)

The following errata report has been rejected for RFC3107,
"Carrying Label Information in BGP-4".

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

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Alexander Okonnikov <[email-masked]>
Date Reported: 2015-10-13
Rejected by: Deborah Brungard (IESG)

Section: 5

Original Text
-------------
   A BGP speaker that is capable of handling multiple routes to a
   destination (as described above) should use the Capabilities Optional
   Parameter, as defined in [BGP-CAP], to inform its peers about this
   capability.  The value of this capability is 4.

Corrected Text
--------------
   A BGP speaker that is capable of handling multiple routes to a
   destination (as described above) should use the Capabilities Optional
   Parameter, as defined in [BGP-CAP], to inform its peers about this
   capability.  This capability is advertised using the Capability Code
   4 and Capability Length 0.

Notes
-----
To remove confusion what word value means - Capability Value or value of Capability Code.
Also, format of multiple routes capability is not described, so length = 0 is assumed.
 --VERIFIER NOTES-- 

--------------------------------------
RFC3107 (draft-ietf-mpls-bgp4-mpls-04)
--------------------------------------
Title               : Carrying Label Information in BGP-4
Publication Date    : May 2001
Author(s)           : Y. Rekhter, E. Rosen
Category            : PROPOSED STANDARD
Source              : Multiprotocol Label Switching
Area                : Routing
Stream              : IETF
Verifying Party     : IESG