Inter-Domain Routing B. Rijsman Internet-Draft Juniper Networks Updates: RFC4486 November 17, 2006 (if approved) Intended status: Standards Track Expires: May 21, 2007 BFD Down Subcode for BGP Cease Notification Message draft-rijsman-bfd-down-subcode-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware 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 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. This Internet-Draft will expire on May 21, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Rijsman Expires May 21, 2007 [Page 1]
Internet-Draft BFD Down Cease Subcode November 2006 Abstract This document defines a new "BFD session down" subcode for the BGP Cease NOTIFICATION message. Rijsman Expires May 21, 2007 [Page 2]
Internet-Draft BFD Down Cease Subcode November 2006 1 BFD session down subcode A new subcode with value 9 and symbolic name "BFD Session Down" is defined for the Cease NOTIFICATION message in addition to the existing subcodes defined in RFC4486 [2]. If a BGP speaker decides to terminate its peering with a neighbor because its BFD [3] session to that neighbor went down then the speaker SHOULD send a NOTIFICATION message to the neighbor with the error code cease and the error subcode "BFD session down". The NOTIFICATION message SHOULD have no data. Rijsman Expires May 21, 2007 [Page 3]
Internet-Draft BFD Down Cease Subcode November 2006 2 IANA considerations As specified in RFC4486 [2] the "BFD Session Down" subcode is assigned using the Early IANA Allocation process defined in RFC4020 [1] which requires an Internet Draft that is proposed as Standards Track. Rijsman Expires May 21, 2007 [Page 4]
Internet-Draft BFD Down Cease Subcode November 2006 3 Security consideration This extension to BGP does not change the underlying security issues inherent in the existing BGP. Rijsman Expires May 21, 2007 [Page 5]
Internet-Draft BFD Down Cease Subcode November 2006 4. References [1] Kompella, K. and A. Zinin, "Early IANA Allocation of Standards Track Code Points", RFC 4020, February 2005. [2] Chen, E. and V. Gillet, "Subcodes for BGP Cease Notification Message", RFC 4486, April 2006. [3] Katz, D. and D. Ward, "Bidirectional Forwarding Detection", I-D draft-ietf-bfd-base-05.txt, April 2006. Rijsman Expires May 21, 2007 [Page 6]
Internet-Draft BFD Down Cease Subcode November 2006 Author's Address Bruno Rijsman Juniper Networks 10 Technology Park Drive Westford, MA 01886 USA Email: brijsman@juniper.net Rijsman Expires May 21, 2007 [Page 7]
Internet-Draft BFD Down Cease Subcode November 2006 Full Copyright Statement Copyright (C) The Internet Society (2006). 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 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. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Rijsman Expires May 21, 2007 [Page 8]