draft-ietf-idr-cease-subcode-01.txt   draft-ietf-idr-cease-subcode-02.txt 
Network Working Group Enke Chen Network Working Group Enke Chen
Internet Draft Redback Networks Internet Draft Redback Networks
Expiration Date: December 2002 Vincent Gillet Expiration Date: May 2003 Vincent Gillet
France Telecom France Telecom
Subcodes for BGP Cease Notification Message Subcodes for BGP Cease Notification Message
draft-ietf-idr-cease-subcode-01.txt draft-ietf-idr-cease-subcode-02.txt
1. Status of this Memo 1. Status of this Memo
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. all provisions of Section 10 of RFC2026.
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.
skipping to change at page 2, line 24 skipping to change at page 2, line 24
message: message:
Subcode Symbolic Name Subcode Symbolic Name
1 Maximum Number of Prefixes Reached 1 Maximum Number of Prefixes Reached
2 Administratively Shutdown 2 Administratively Shutdown
3 Peer Unconfigured 3 Peer Unconfigured
4 Administratively Reset 4 Administratively Reset
5 Connection Rejected 5 Connection Rejected
6 Other Configuration Change 6 Other Configuration Change
7 Connection Collision Resolution
5. Subcode Usage 5. Subcode Usage
If a BGP speaker decides to terminate its peering with a neighbor If a BGP speaker decides to terminate its peering with a neighbor
because the number of address prefixes received from the neighbor because the number of address prefixes received from the neighbor
exceeds a locally configured upper bound (as described in [BGP-4]), exceeds a locally configured upper bound (as described in [BGP-4]),
then the speaker must send to the neighbor a NOTIFICATION message then the speaker must send to the neighbor a NOTIFICATION message
with the Error Code Cease, and the Error Subcode "Maximum Number of with the Error Code Cease, and the Error Subcode "Maximum Number of
Prefixes Reached". The message may optionally include the Address Prefixes Reached". The message may optionally include the Address
Family information [BGP-MP] and the upper bound in the "Data" field Family information [BGP-MP] and the upper bound in the "Data" field
skipping to change at page 3, line 24 skipping to change at page 3, line 25
peer is not configured locally) after the speaker accepts a transport peer is not configured locally) after the speaker accepts a transport
protocol connection, then the BGP speaker should send a NOTIFICATION protocol connection, then the BGP speaker should send a NOTIFICATION
message with the Error Code Cease, and the Error Subcode "Connection message with the Error Code Cease, and the Error Subcode "Connection
Rejected". Rejected".
If a BGP speaker decides to administratively reset the peering with a If a BGP speaker decides to administratively reset the peering with a
neighbor due to a configuration change other than the ones described neighbor due to a configuration change other than the ones described
above, then the speaker should send a NOTIFICATION message with the above, then the speaker should send a NOTIFICATION message with the
Error Code Cease, and the Error Subcode "Other Configuration Change". Error Code Cease, and the Error Subcode "Other Configuration Change".
If a BGP speaker decides to send a NOTIFICATION message with the
Error Code Cease as a result of the collision resolution procedure
(as described in [BGP-4]), then the subcode should be set to
"Connection Collision Resolution".
It is recommended that a BGP speaker implement a backoff mechanism in It is recommended that a BGP speaker implement a backoff mechanism in
re-trying a BGP connection after the speaker receives a Cease re-trying a BGP connection after the speaker receives a Cease
NOTIFICATION message with subcode of "Administratively Shutdown", or NOTIFICATION message with subcode of "Administratively Shutdown", or
"Peer Unconfigured", or "Connection Rejected". An implementation may "Peer Unconfigured", or "Connection Rejected". An implementation may
impose an upper bound on the number of consecutive automatic retries. impose an upper bound on the number of consecutive automatic retries.
Once this bound is reached, the implementation would stop re-trying Once this bound is reached, the implementation would stop re-trying
any BGP connections until some administrative intervention. any BGP connections until some administrative intervention.
6. Security Considerations 6. Security Considerations
This extension to BGP does not change the underlying security issues. This extension to BGP does not change the underlying security issues.
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Yakov Rekhter for discussions and The authors would like to thank Yakov Rekhter and Pedro Marques for
review. their review and suggestions.
8. References 8. References
[BGP-4] Y. Rekhter, and T. Li, "A Border Gateway Protocol 4 (BGP-4)", [BGP-4] Y. Rekhter, T. Li and S. Hares, "A Border Gateway Protocol 4
<draft-ietf-idr-bgp4-14.txt>, October 2001. (BGP-4)", <draft-ietf-idr-bgp4-18.txt>, October 2002.
[BGP-MP] Bates, T., Chandra, R., Katz, D. and Y. Rekhter, [BGP-MP] Bates, T., Chandra, R., Katz, D. and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 2858, June 2000. "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000.
9. Author Information 9. Author Information
Enke Chen Enke Chen
Redback Networks, Inc. Redback Networks, Inc.
350 Holger Way 350 Holger Way
San Jose, CA 95134 San Jose, CA 95134
 End of changes. 

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