draft-ietf-idr-rfc3392bis-02.txt   draft-ietf-idr-rfc3392bis-03.txt 
Internet Engineering Task Force J. Scudder Internet Engineering Task Force J. Scudder
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track R. Chandra Intended status: Standards Track R. Chandra
Expires: June 13, 2009 Sonoa Systems Expires: June 19, 2009 Sonoa Systems
December 10, 2008 December 16, 2008
Capabilities Advertisement with BGP-4 Capabilities Advertisement with BGP-4
draft-ietf-idr-rfc3392bis-02.txt draft-ietf-idr-rfc3392bis-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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 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-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 13, 2009. This Internet-Draft will expire on June 19, 2009.
Copyright Notice
Copyright (c) 2008 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
This document defines an Optional Parameter, called Capabilities, This document defines an Optional Parameter, called Capabilities,
that is expected to facilitate the introduction of new capabilities that is expected to facilitate the introduction of new capabilities
in the Border Gateway Protocol (BGP) by providing graceful capability in the Border Gateway Protocol (BGP) by providing graceful capability
advertisement without requiring that BGP peering be terminated. This advertisement without requiring that BGP peering be terminated. This
document obsoletes RFC 3392. document obsoletes RFC 3392.
1. Introduction 1. Introduction
skipping to change at page 3, line 19 skipping to change at page 3, line 29
If a BGP speaker receives from its peer a capability which it does If a BGP speaker receives from its peer a capability which it does
not itself support or recognize, it SHOULD ignore that capability. not itself support or recognize, it SHOULD ignore that capability.
In particular, the Unsupported Capability NOTIFICATION message MUST In particular, the Unsupported Capability NOTIFICATION message MUST
NOT be generated in response to reception of a capability which is NOT be generated in response to reception of a capability which is
not supported by the local speaker. not supported by the local speaker.
4. Capabilities Optional Parameter (Parameter Type 2): 4. Capabilities Optional Parameter (Parameter Type 2):
This is an Optional Parameter that is used by a BGP speaker to convey 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. to its BGP peer the list of capabilities supported by the speaker.
The encoding of BGP Optional Parameters is specified in Section 4.2
of [RFC4271]. The parameter type of the Capabilities Optional
Parameter is 2.
The parameter contains one or more triples <Capability Code, The parameter contains one or more triples <Capability Code,
Capability Length, Capability Value>, where each triple is encoded as Capability Length, Capability Value>, where each triple is encoded as
shown below: shown below:
+------------------------------+ +------------------------------+
| Capability Code (1 octet) | | Capability Code (1 octet) |
+------------------------------+ +------------------------------+
| Capability Length (1 octet) | | Capability Length (1 octet) |
+------------------------------+ +------------------------------+
| Capability Value (variable) | | Capability Value (variable) |
~ ~ ~ ~
+------------------------------+ +------------------------------+
The use and meaning of these fields are as follows: The use and meaning of these fields are as follows:
Capability Code: Capability Code:
Capability Code is a one octet field that unambiguously Capability Code is a one octet unsigned binary integer that
identifies individual capabilities. unambiguously identifies individual capabilities.
Capability Length: Capability Length:
Capability Length is a one octet field that contains the length Capability Length is a one octet unsigned binary integer that
of the Capability Value field in octets. contains the length of the Capability Value field in octets.
Capability Value: Capability Value:
Capability Value is a variable length field that is interpreted Capability Value is a variable length field that is interpreted
according to the value of the Capability Code field. according to the value of the Capability Code field.
BGP speakers SHOULD NOT include more than one instance of a BGP speakers SHOULD NOT include more than one instance of a
capability with the same Capability Code, Capability Length, and capability with the same Capability Code, Capability Length, and
Capability Value. Note however, that processing of multiple Capability Value. Note however, that processing of multiple
instances of such capability does not require special handling, as instances of such capability does not require special handling, as
skipping to change at page 7, line 4 skipping to change at line 261
John G. Scudder John G. Scudder
Juniper Networks Juniper Networks
Email: jgs@juniper.net Email: jgs@juniper.net
Ravi Chandra Ravi Chandra
Sonoa Systems Sonoa Systems
Email: rchandra@sonoasystems.com Email: rchandra@sonoasystems.com
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.
 End of changes. 8 change blocks. 
12 lines changed or deleted 25 lines changed or added

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