[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (RFC 3392) 00 01 02 03 04 05 RFC 5492

Internet Engineering Task Force                               J. Scudder
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                              R. Chandra
Expires: November 23, 2008                                 Sonoa Systems
                                                            May 22, 2008


                 Capabilities Advertisement with BGP-4
                    draft-ietf-idr-rfc3392bis-00.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   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
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on November 23, 2008.

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.


1.  Introduction

   The base BGP-4 specification [RFC4271] requires that when a BGP
   speaker receives an OPEN message with one or more unrecognized



Scudder & Chandra       Expires November 23, 2008               [Page 1]


Internet-Draft              Abbreviated Title                   May 2008


   Optional Parameters, the speaker must terminate BGP peering.  This
   complicates introduction of new capabilities in BGP.


2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].


3.  Overview of Operations

   When a BGP speaker [RFC4271] that supports capabilities advertisement
   sends an OPEN message to its BGP peer, the message MAY include an
   Optional Parameter, called Capabilities.  The parameter lists the
   capabilities supported by the speaker.

   A BGP speaker determines the capabilities supported by its peer by
   examining the list of capabilities present in the Capabilities
   Optional Parameter carried by the OPEN message that the speaker
   receives from the peer.

   A BGP speaker that supports a particular capability may use this
   capability with its peer after the speaker determines (as described
   above) that the peer supports this capability.  Simply put, a given
   capability can be used on a peering if that capability has been
   advertised by both peers.  If either peer has not advertised it, the
   capability cannot be used.

   A BGP speaker determines that its peer doesn't support capabilities
   advertisement, if in response to an OPEN message that carries the
   Capabilities Optional Parameter, the speaker receives a NOTIFICATION
   message with the Error Subcode set to Unsupported Optional Parameter.
   (This is a consequence of the base BGP-4 specification [RFC4271] and
   not a new requirement.)  In this case the speaker SHOULD attempt to
   re-establish a BGP connection with the peer without sending to the
   peer the Capabilities Optional Parameter.

   If a BGP speaker that supports a certain capability requires that
   this capability be used on a peering but determines that its peer
   doesn't support this capability, the speaker MAY send a NOTIFICATION
   message to the peer, and terminate peering (see Section "Extensions
   to Error Handling" for more details).  The Error Subcode in the
   message is set to Unsupported Capability.  The message SHOULD contain
   the capability (capabilities) that causes the speaker to send the
   message.  The decision to send the message and terminate peering is
   local to the speaker.  If terminated, such peering SHOULD NOT be re-



Scudder & Chandra       Expires November 23, 2008               [Page 2]


Internet-Draft              Abbreviated Title                   May 2008


   established automatically.  An example of when this procedure might
   be followed is if a BGP speaker is attempting to establish an IPv6
   peering but determines that its peer does not support Multiprotocol
   Extensions for BGP-4 [RFC4760].

   If a BGP speaker receives from its peer a capability which it does
   not itself support, it SHOULD ignore that capability.  In particular,
   the Unsupported Capability NOTIFICATION message MUST NOT be generated
   in response to reception of a capability which is not supported by
   the local speaker.


4.  Capabilities Optional Parameter (Parameter Type 2):

   This is an Optional Parameter that is used by a BGP speaker to convey
   to its BGP peer the list of capabilities supported by the speaker.

   The parameter contains one or more triples <Capability Code,
   Capability Length, Capability Value>, where each triple is encoded as
   shown below:

          +------------------------------+
          | Capability Code (1 octet)    |
          +------------------------------+
          | Capability Length (1 octet)  |
          +------------------------------+
          | Capability Value (variable)  |
          +------------------------------+

                                 Figure 1

   The use and meaning of these fields are as follows:

      Capability Code:

         Capability Code is a one octet field that unambiguously
         identifies individual capabilities.

      Capability Length:

         Capability Length is a one octet field that contains the length
         of the Capability Value field in octets.

      Capability Value:

         Capability Value is a variable length field that is interpreted
         according to the value of the Capability Code field.




Scudder & Chandra       Expires November 23, 2008               [Page 3]


Internet-Draft              Abbreviated Title                   May 2008


   BGP speakers SHOULD NOT include more than one instance of a
   capability with the same Capability Code, Capability Length, and
   Capability Value.  Note however, that processing of multiple
   instances of such capability does not require special handling, as
   additional instances do not change the meaning of the announced
   capability.

   BGP speakers MAY include more than one instance of a capability (as
   identified by the Capability Code) with non-zero Capability Length
   field, but with different Capability Value, and either the same or
   different Capability Length.  Processing of these capability
   instances is specific to the Capability Code and MUST be described in
   the document introducing the new capability.


5.  Extensions to Error Handling

   This document defines new Error Subcode - Unsupported Capability.
   The value of this Subcode is 7.  The Data field in the NOTIFICATION
   message SHOULD list the set of capabilities that cause the speaker to
   send the message.  Each such capability is encoded the same way as it
   would be encoded in the OPEN message.

   As the Overview of Operations section notes, the Unsupported
   Capability NOTIFICATION is a way for a BGP speaker to complain that
   its peer does not support a required capability, without which the
   peering cannot proceed.  It MUST NOT be used when a BGP speaker
   receives a capability which it does not understand; such capabilities
   SHOULD be ignored.


6.  IANA Considerations

   This document defines a Capability Optional Parameter along with a
   Capability Code field.  IANA maintains the registry for Capability
   Code values.  Capability Code value 0 is reserved.  Capability Code
   values 1 through 63 are to be assigned by IANA using the "IETF
   Consensus" policy defined in [RFC2434].  Capability Code values 64
   through 127 are to be assigned by IANA, using the "First Come First
   Served" policy defined in [RFC2434].  Capability Code values 128
   through 255 are for "Private Use" as defined in [RFC2434].


7.  Security Considerations

   This extension to BGP does not change the underlying security issues
   inherent in the existing BGP [RFC4272].




Scudder & Chandra       Expires November 23, 2008               [Page 4]


Internet-Draft              Abbreviated Title                   May 2008


8.  Acknowledgements

   The authors would like to thank members of the IDR Working Group for
   their review and comments.


9.  References

9.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2434]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 2434,
              October 1998.

   [RFC4271]  Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
              Protocol 4 (BGP-4)", RFC 4271, January 2006.

9.2.  Informative References

   [RFC4272]  Murphy, S., "BGP Security Vulnerabilities Analysis",
              RFC 4272, January 2006.

   [RFC4760]  Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
              "Multiprotocol Extensions for BGP-4", RFC 4760,
              January 2007.


Appendix A.  Comparison with RFC 2842

   In addition to several minor editorial changes, this document also
   clarifies how to handle multiple instances of the same capability.


Appendix B.  Comparison with RFC 3392

   In addition to minor editorial changes, this document also clarifies
   the use of the Unsupported Optional Parameter NOTIFICATION message,
   and updates references to the base BGP-4 specification [RFC4271] and
   security analysis [RFC4272].









Scudder & Chandra       Expires November 23, 2008               [Page 5]


Internet-Draft              Abbreviated Title                   May 2008


Authors' Addresses

   John G. Scudder
   Juniper Networks

   Email: jgs@juniper.net


   Ravi Chandra
   Sonoa Systems

   Email: rchandra@sonoasystems.com







































Scudder & Chandra       Expires November 23, 2008               [Page 6]


Internet-Draft              Abbreviated Title                   May 2008


Full Copyright Statement

   Copyright (C) The IETF Trust (2008).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.











Scudder & Chandra       Expires November 23, 2008               [Page 7]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/