draft-ietf-idr-dynamic-cap-05.txt   draft-ietf-idr-dynamic-cap-06.txt 
Network Working Group Enke Chen Network Working Group Enke Chen
Internet Draft Redback Networks Internet Draft Redback Networks
Expiration Date: January 2005 Srihari R. Sangli Expiration Date: February 2005 Srihari R. Sangli
Procket Networks Cisco Systems
Dynamic Capability for BGP-4 Dynamic Capability for BGP-4
draft-ietf-idr-dynamic-cap-05.txt draft-ietf-idr-dynamic-cap-06.txt
1. Status of this Memo 1. Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668. disclosed, in accordance with RFC 3668.
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
skipping to change at page 3, line 25 skipping to change at page 3, line 25
| Ack Request (1 bit) | | Ack Request (1 bit) |
+------------------------------+ +------------------------------+
| Reserved (5 bits) | | Reserved (5 bits) |
+------------------------------+ +------------------------------+
| Action (1 bit) | | Action (1 bit) |
+------------------------------+ +------------------------------+
| Sequence Number (4 octets) | | Sequence Number (4 octets) |
+------------------------------+ +------------------------------+
| Capability Code (1 octet) | | Capability Code (1 octet) |
+------------------------------+ +------------------------------+
| Capability Length (1 octet) | | Capability Length (2 octets) |
+------------------------------+ +------------------------------+
| Capability Value (variable) | | Capability Value (variable) |
+------------------------------+ +------------------------------+
The Init/Ack bit indicates whether a capability revision is being The Init/Ack bit indicates whether a capability revision is being
initiated (when set to 0), or being acknowledged (when set to 1). initiated (when set to 0), or being acknowledged (when set to 1).
The Ack Request bit indicates whether an acknowledgement is requested The Ack Request bit indicates whether an acknowledgement is requested
(when set to 1), or not (when set to 0) for a capability revision (when set to 1), or not (when set to 0) for a capability revision
being initiated. being initiated.
skipping to change at page 3, line 47 skipping to change at page 3, line 47
The Reserved bits should be set to zero by the sender and ignored by The Reserved bits should be set to zero by the sender and ignored by
the receiver. the receiver.
The Action bit is 0 for advertising a capability, and 1 for removing The Action bit is 0 for advertising a capability, and 1 for removing
a capability. a capability.
The Sequence Number field can be used by a BGP speaker to match an The Sequence Number field can be used by a BGP speaker to match an
acknowledgement with a capability revision that the speaker initiated acknowledgement with a capability revision that the speaker initiated
previously. previously.
The triple <Capability Code, Capability Length, Capability Value> is Conceptually the triple <Capability Code, Capability Length,
the same as defined in [BGP-CAP], and it specifies a capability for Capability Value> is the same as the one defined in [BGP-CAP], and it
which the "Action" shall be applied. The triple is optional when the specifies a capability for which the "Action" shall be applied. The
Init/Ack bit is set to 1. triple is optional when the Init/Ack bit is set to 1.
7. Operation 7. Operation
A BGP speaker that is willing to receive the CAPABILITY message (for A BGP speaker that is willing to receive the CAPABILITY message (for
one or more capability codes) from its peer SHOULD use the BGP one or more capability codes) from its peer SHOULD use the BGP
Capabilities Advertisement [BGP-CAP] to advertise the Dynamic Capabilities Advertisement [BGP-CAP] to advertise the Dynamic
Capability for these capability codes. Capability for these capability codes.
A BGP speaker MAY send to its peer a CAPABILITY message to initiate A BGP speaker MAY send to its peer a CAPABILITY message to initiate
revisions for one or more capability codes only if these capability revisions for one or more capability codes only if these capability
codes are listed in the Dynamic Capability of the OPEN message codes are listed in the Dynamic Capability of the OPEN message
received from its peer. received from its peer.
A CAPABILITY message MAY be received only in the Established state.
Receiving a CAPABILITY message in any other state is a Finite State
Machine Error as defined in [BGP-4]. A BGP speaker SHOULD reset the
HoldTimer upon receiving a CAPABILITY message from its peer.
When a BGP speaker sends a CAPABILITY message to its peer to initiate When a BGP speaker sends a CAPABILITY message to its peer to initiate
a capability revision, the Init/Ack bit for the capability revision a capability revision, the Init/Ack bit for the capability revision
in the message MUST be set to 0. The setting of the Ack Request bit in the message MUST be set to 0. The setting of the Ack Request bit
is capability specific. The assignment of the Sequence Number is a is capability specific. The assignment of the Sequence Number is a
local matter, but MUST allow the BGP speaker to unambiguously local matter, but MUST allow the BGP speaker to unambiguously
identify a capability revision it initiated previously based on the identify a capability revision it initiated previously based on the
Sequence Number carried in the acknowledgement from the peer. Sequence Number carried in the acknowledgement from the peer.
If the Init/Ack bit is set to 1 for a capability revision in a If the Init/Ack bit is set to 1 for a capability revision in a
CAPABILITY message received by a BGP speaker, then the BGP speaker CAPABILITY message received by a BGP speaker, then the BGP speaker
skipping to change at page 6, line 25 skipping to change at page 6, line 30
(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.
9. IANA Considerations 9. 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 needs
been assigned by IANA per RFC 2842. to be assigned by IANA per RFC 2842.
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
[BGP-MD5]. [BGP-MD5].
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
skipping to change at page 7, line 34 skipping to change at page 7, line 40
13. Author Information 13. Author Information
Enke Chen Enke Chen
Redback Networks, Inc. Redback Networks, Inc.
300 Holger Way 300 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
Procket Networks, Inc. Cisco Systems, Inc.
1100 Cadillac Court 170 W. Tasman Dr.
Milpitas, CA 95035 San Jose, CA 95134
e-mail: srihari@procket.com e-mail: rsrihari@cisco.com
14. Intellectual Property Considerations 14. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
 End of changes. 

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