RFC 5492 - Capabilities Advertisement with BGP-4
Published: February 2009
Category: Standards Track
Authors: J. Scudder (Juniper Networks), R. Chandra (Sonoa Systems)
Obsoletes: RFC 3392
ISSN: 2070-1721
Abstract
This document defines an Optional Parameter, called Capabilities, that is expected to facilitate the introduction of new capabilities in the Border Gateway Protocol (BGP) by providing graceful capability advertisement without requiring that BGP peering be terminated.
This document obsoletes RFC 3392.
Status of This Memo
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
Contents
- 1. Introduction
- 2. Requirements Language
- 3. Overview of Operations
- 4. Capabilities Optional Parameter (Parameter Type 2)
- 5. Extensions to Error Handling
- 6. IANA Considerations
- 7. Security Considerations
- 8. Acknowledgments
- 9. References
- Appendix A. Comparison between RFC 2842 and RFC 3392
- Appendix B. Comparison between RFC 3392 and This Document
- Authors' Addresses