Network Working Group Enke Chen Internet Draft Redback Networks Expiration Date: May 2003 Vincent Gillet France Telecom Subcodes for BGP Cease Notification Message draft-ietf-idr-cease-subcode-02.txt 1. Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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. 2. Abstract This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in co-relating network events and diagnosing BGP peering issues. Chen & Gillet [Page 1] Internet Draft draft-ietf-idr-cease-subcode-02.txt November 2002 3. Introduction This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in co-relating network events and diagnosing BGP peering issues. 4. Subcode Definition The following subcodes are defined for the Cease NOTIFICATION message: Subcode Symbolic Name 1 Maximum Number of Prefixes Reached 2 Administratively Shutdown 3 Peer Unconfigured 4 Administratively Reset 5 Connection Rejected 6 Other Configuration Change 7 Connection Collision Resolution 5. Subcode Usage If a BGP speaker decides to terminate its peering with a neighbor because the number of address prefixes received from the neighbor exceeds a locally configured upper bound (as described in [BGP-4]), then the speaker must send to the neighbor a NOTIFICATION message with the Error Code Cease, and the Error Subcode "Maximum Number of Prefixes Reached". The message may optionally include the Address Family information [BGP-MP] and the upper bound in the "Data" field with the following format: +-------------------------------+ | AFI (2 octets) | +-------------------------------+ | SAFI (1 octet) | +-------------------------------+ | Prefix upper bound (4 octets) | +-------------------------------+ where the meaning and use of the tuple is the same as defined in [BGP-MP, sect. 7]. If a BGP speaker decides to administratively shut down its peering with a neighbor, then the speaker should send a NOTIFICATION message with the Error Code Cease, and the Error Subcode "Administratively Chen & Gillet [Page 2] Internet Draft draft-ietf-idr-cease-subcode-02.txt November 2002 Shutdown". If a BGP speaker decides to unconfigure a peer, then the speaker should send a NOTIFICATION message with the Error Code Cease, and the Error Subcode "Peer Unconfigured". If a BGP speaker decides to administratively reset the peering with a neighbor, then the speaker should send a NOTIFICATION message with the Error Code Cease, and the Error Subcode "Administratively Reset". If a BGP speaker decides to dis-allow a BGP connection (e.g., the peer is not configured locally) after the speaker accepts a transport protocol connection, then the BGP speaker should send a NOTIFICATION message with the Error Code Cease, and the Error Subcode "Connection Rejected". If a BGP speaker decides to administratively reset the peering with a neighbor due to a configuration change other than the ones described above, then the speaker should send a NOTIFICATION message with the 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 re-trying a BGP connection after the speaker receives a Cease NOTIFICATION message with subcode of "Administratively Shutdown", or "Peer Unconfigured", or "Connection Rejected". An implementation may impose an upper bound on the number of consecutive automatic retries. Once this bound is reached, the implementation would stop re-trying any BGP connections until some administrative intervention. 6. Security Considerations This extension to BGP does not change the underlying security issues. Chen & Gillet [Page 3] Internet Draft draft-ietf-idr-cease-subcode-02.txt November 2002 7. Acknowledgments The authors would like to thank Yakov Rekhter and Pedro Marques for their review and suggestions. 8. References [BGP-4] Y. Rekhter, T. Li and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", , October 2002. [BGP-MP] Bates, T., Chandra, R., Katz, D. and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000. 9. Author Information Enke Chen Redback Networks, Inc. 350 Holger Way San Jose, CA 95134 Email: enke@redback.com Vincent Gillet France Telecom Longues Distances 246 rue de Bercy 75594 Paris Cedex 12 FRANCE Email: vgi@opentransit.net Chen & Gillet [Page 4]