draft-ietf-idr-dynamic-cap-13.txt   draft-ietf-idr-dynamic-cap-14.txt 
Network Working Group E. Chen Network Working Group E. Chen
Internet Draft S. Sangli Internet Draft S. Sangli
Expiration Date: December 3, 2011 Cisco Systems Expiration Date: June 6, 2012 Cisco Systems
June 2, 2011 December 5, 2011
Dynamic Capability for BGP-4 Dynamic Capability for BGP-4
draft-ietf-idr-dynamic-cap-13.txt draft-ietf-idr-dynamic-cap-14.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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 December 3, 2011. This Internet-Draft will expire on June 6, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 46 skipping to change at page 4, line 46
capability revision previously initiated. The BGP speaker SHALL capability revision previously initiated. The BGP speaker SHALL
ignore an acknowledgment for a capability revision in which an ignore an acknowledgment for a capability revision in which an
acknowledgment was not requested by the BGP speaker. If the Sequence acknowledgment was not requested by the BGP speaker. If the Sequence
Number carried in the capability revision does not match any of the Number carried in the capability revision does not match any of the
the Sequence Numbers used in the capability revisions initiated by the Sequence Numbers used in the capability revisions initiated by
the BGP speaker, then the BGP speaker SHOULD send a NOTIFICATION the BGP speaker, then the BGP speaker SHOULD send a NOTIFICATION
message as specified in the Error Handling section. message as specified in the Error Handling section.
If the Init/Ack bit is set to 0 for a capability revision in a If the Init/Ack bit is set to 0 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
SHOULD first validate the capability code in the message. If the SHOULD first validate the capability code in the message. If the
capability code is not listed in the Dynamic Capability advertised by capability code is not listed in the Dynamic Capability advertised by
the speaker to the peer, the BGP speaker SHOULD send a NOTIFICATION the speaker to the peer, the BGP speaker SHOULD send a NOTIFICATION
message as specified in the Error Handling section. For a valid message as specified in the Error Handling section. For a valid
capability code, if the Ack Request bit is set to 1, the BGP speaker capability code, if the Ack Request bit is set to 1, the BGP speaker
MUST first send a CAPABILITY message to acknowledge the receipt of MUST first send a CAPABILITY message to acknowledge the receipt of
the capability revision. The Init/Ack bit in the acknowledgment MUST the capability revision. The Init/Ack bit in the acknowledgment MUST
be set to 1, and all the other fields in the capability revision MUST be set to 1, and all the other fields in the capability revision MUST
be kept unchanged. be kept unchanged.
After receiving a capability revision initiated by a peer, the BGP After receiving a capability revision initiated by a peer, the BGP
skipping to change at page 5, line 23 skipping to change at page 5, line 23
not advertised previously. The procedures specified in the "Error not advertised previously. The procedures specified in the "Error
Handling" section SHOULD be followed when an error is detected in Handling" section SHOULD be followed when an error is detected in
processing the CAPABILITY message. processing the CAPABILITY message.
In order to avoid ambiguities in sending and processing UPDATE In order to avoid ambiguities in sending and processing UPDATE
messages, certain capability revisions may require close coordination messages, certain capability revisions may require close coordination
between the BGP speaker (the Initiator) that initiates the capability between the BGP speaker (the Initiator) that initiates the capability
revisions and another BGP speaker (the Receiver) that receives the revisions and another BGP speaker (the Receiver) that receives the
capability revisions. The mechanism of acknowledgment defined in capability revisions. The mechanism of acknowledgment defined in
this document SHALL be used for the revision of such a capability. this document SHALL be used for the revision of such a capability.
For the Initiator, the capability revision SHALL take effect (for For the Initiator, the capability revision SHALL take effect (for the
sending updates) immediately after the capability revision is sent, purpose of sending updates) immediately after the capability revision
and the capability revision SHALL take effect (for receiving updates) is sent, and the capability revision SHALL take effect (for the
immediately after an acknowledgment is received from the Receiver. purpose of receiving updates) immediately after an acknowledgment is
For the Receiver, the capability revision SHALL take effect (for received from the Receiver. For the Receiver, the capability
receiving updates) immediately after the capability revision is revision SHALL take effect (for the purpose of receiving updates)
received from the Initiator, and the capability revision SHALL take immediately after the capability revision is received from the
effect (for sending updates) immediately after an acknowledgment is Initiator, and the capability revision SHALL take effect (for the
purpose of sending updates) immediately after an acknowledgment is
sent. sent.
5. Error Handling 5. Error Handling
This document defines a new NOTIFICATION error code: This document defines a new NOTIFICATION error code:
Error Code Symbolic Name Error Code Symbolic Name
7 CAPABILITY Message Error 7 CAPABILITY Message Error
 End of changes. 6 change blocks. 
14 lines changed or deleted 15 lines changed or added

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