draft-ietf-idr-dynamic-cap-08.txt   draft-ietf-idr-dynamic-cap-09.txt 
Network Working Group Enke Chen Network Working Group Enke Chen
Internet Draft Srihari R. Sangli Internet Draft S. Sangli
Expiration Date: June 2006 Cisco Systems Expiration Date: May 2007 Cisco Systems
Dynamic Capability for BGP-4 Dynamic Capability for BGP-4
draft-ietf-idr-dynamic-cap-08.txt draft-ietf-idr-dynamic-cap-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 28 skipping to change at page 2, line 28
2. Specification of Requirements 2. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC-2119]. document are to be interpreted as described in [RFC-2119].
3. Dynamic Capability 3. Dynamic Capability
The Dynamic Capability is a new BGP capability [BGP-CAP]. The The Dynamic Capability is a new BGP capability [BGP-CAP]. The
Capability Code for this capability is specified in the "IANA Capability Code for this capability is specified in the "IANA
Considerations" section of this document. The Capability Length Considerations" section of this document. The Capability Value field
field of this capability is one octet. The Capability Value field consists of a list of capability codes (one-octet for each) that
consists of a list of capability codes (one-octet for each) for which specify the capabilities that MAY be revised dynamically by the
the dynamic revision is supported by a BGP speaker. remote speaker.
By advertising the Dynamic Capability to a peer in the OPEN, a BGP By advertising the Dynamic Capability to a peer in the OPEN, a BGP
speaker conveys to the peer that the speaker is capable of receiving speaker conveys to the peer that the speaker is capable of receiving
and properly handling the CAPABILITY message (as defined in the next and properly handling the CAPABILITY message (as defined in the next
Section) from the peer after the BGP session has been established. Section) from the peer after the BGP session has been established.
4. Capability Message 4. Capability Message
The CAPABILITY Message is a new BGP message type with type code 6. The CAPABILITY Message is a new BGP message type with type code 6.
In addition to the fixed-size BGP header [BGP-4], the CAPABILITY In addition to the fixed-size BGP header [BGP-4], the CAPABILITY
skipping to change at page 6, line 29 skipping to change at page 6, line 29
If the Capability Value field in the CAPABILITY message is malformed If the Capability Value field in the CAPABILITY message is malformed
(the definition of "malformed" depends on the Capability Code), then (the definition of "malformed" depends on the Capability Code), then
the error subcode is set to Malformed Capability Value. the error subcode is set to Malformed Capability Value.
If the Capability Code in the CAPABILITY message is not any of the If the Capability Code in the CAPABILITY message is not any of the
capability codes advertised in the Dynamic Capability by the speaker, capability codes advertised in the Dynamic Capability by the speaker,
then the error subcode is set to Unsupported Capability Code. then the error subcode is set to Unsupported Capability Code.
7. IANA Considerations 7. IANA Considerations
This document defines the CAPABILITY message type for BGP with type
code 6, and a NOTIFICATION error code and subcodes for the errors in
a CAPABILITY message.
This document uses a BGP capability code to indicate that a BGP This document uses a BGP capability code to indicate that a BGP
speaker supports the Dynamic Capability. The capability code needs speaker supports the Dynamic Capability. The capability code needs
to be assigned by IANA per RFC 2842. to be assigned by IANA per RFC 2842.
8. Security Considerations 8. Security Considerations
This extension to BGP does not change the underlying security issues. This extension to BGP does not change the underlying security issues.
9. Acknowledgments 9. Acknowledgments
The authors would like to thank Yakov Rekhter, Ravi Chandra, Dino The authors would like to thank Yakov Rekhter, Ravi Chandra, Dino
Farinacci, Pedro Marques, Chandrashekhar Appanna, Derek Yeung, Bruno Farinacci, Pedro Marques, Chandrashekhar Appanna, Derek Yeung, Bruno
Rijsman and John Scudder for their review and comments. Rijsman and John Scudder for their review and comments.
10. Normative References 10. Normative References
[BGP-4] Rekhter, Y., T. Li, and S. Hares, "A Border Gateway Protocol [BGP-4] Rekhter, Y., T. Li, and S. Hares, "A Border Gateway Protocol
4 (BGP-4)", draft-ietf-idr-bgp4-26.txt, October 2004. 4 (BGP-4)", RFC 4271, January 2006.
[BGP-MP] T. Bates, R. Chandra, D. Katz, and Y. Rekhter, [BGP-MP] T. Bates, R. Chandra, D. Katz, and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 2858, June 2000. "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000.
[BGP-CAP] R. Chandra, J. Scudder, "Capabilities Advertisement with [BGP-CAP] R. Chandra, J. Scudder, "Capabilities Advertisement with
BGP-4", RFC 2842, May 2000. BGP-4", RFC 2842, May 2000.
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 8, line 15 skipping to change at page 8, line 31
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
13. Full Copyright Notice 13. Full Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The IETF Trust (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 7 change blocks. 
13 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/