draft-ietf-idr-dynamic-cap-03.txt   draft-ietf-idr-dynamic-cap-04.txt 
Network Working Group Enke Chen Network Working Group Enke Chen
Internet Draft Redback Networks Internet Draft Redback Networks
Expiration Date: June 2003 Srihari R. Sangli Expiration Date: February 2004 Srihari R. Sangli
Procket Networks Procket Networks
Dynamic Capability for BGP-4 Dynamic Capability for BGP-4
draft-ietf-idr-dynamic-cap-03.txt draft-ietf-idr-dynamic-cap-04.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 except that the right to all provisions of Section 10 of RFC2026 except that the right to
produce derivative works is not granted. produce derivative works is not granted.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
skipping to change at page 5, line 13 skipping to change at page 5, line 13
then the error subcode is set to Unsupported Capability Code. then the error subcode is set to Unsupported Capability Code.
8. IANA Considerations 8. IANA Considerations
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 has speaker supports the Dynamic Capability. The capability code has
been assigned by IANA per RFC 2842. been assigned by IANA per RFC 2842.
9. Intellectual Property Considerations 9. Intellectual Property Considerations
Cisco Systems may seek patent or other intellectual property This section is taken from Section 10.4 of [RFC-2026].
protection for some of all of the technologies disclosed in this
document. If any standards arising from this document are or become The IETF takes no position regarding the validity or scope of any
protected by one or more patents assigned to Cisco Systems, Cisco intellectual property or other rights that might be claimed to
intends to disclose those patents and license them on reasonable and pertain to the implementation or use of the technology described in
non-discriminatory terms. this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights.
10. Security Considerations 10. Security Considerations
This extension to BGP does not change the underlying security issues. This extension to BGP does not change the underlying security issues.
11. Acknowledgments 11. 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.
skipping to change at page 6, line 4 skipping to change at page 6, line 29
[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.
[BGP-4BYTE-AS] Q. Vohra, E. Chen, "BGP support for four-octet AS [BGP-4BYTE-AS] Q. Vohra, E. Chen, "BGP support for four-octet AS
number space", Work in Progress, <draft-ietf-idr-as4bytes-04.txt>, number space", Work in Progress, <draft-ietf-idr-as4bytes-04.txt>,
September 2001. September 2001.
[RFC-2026] Bradner, S., "The Internet Standards Process -- Revision
3", RFC 2026, October 1996.
13. Author Information 13. Author Information
Enke Chen Enke Chen
Redback Networks, Inc. Redback Networks, Inc.
350 Holger Way 350 Holger Way
San Jose, CA 95134 San Jose, CA 95134
e-mail: enke@redback.com e-mail: enke@redback.com
Srihari R. Sangli Srihari R. Sangli
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/