draft-ietf-idr-shutdown-05.txt   draft-ietf-idr-shutdown-06.txt 
IDR J. Snijders IDR J. Snijders
Internet-Draft NTT Internet-Draft NTT
Updates: 4486 (if approved) J. Heitz Updates: 4486 (if approved) J. Heitz
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: August 4, 2017 J. Scudder Expires: August 15, 2017 J. Scudder
Juniper Juniper
January 31, 2017 February 11, 2017
BGP Administrative Shutdown Communication BGP Administrative Shutdown Communication
draft-ietf-idr-shutdown-05 draft-ietf-idr-shutdown-06
Abstract Abstract
This document enhances the BGP Cease NOTIFICATION message This document enhances the BGP Cease NOTIFICATION message
"Administrative Shutdown" and "Administrative Reset" subcodes for "Administrative Shutdown" and "Administrative Reset" subcodes for
operators to transmit a short freeform message to describe why a BGP operators to transmit a short freeform message to describe why a BGP
session was shutdown or reset. session was shutdown or reset. This document updates RFC 4486.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on August 4, 2017. This Internet-Draft will expire on August 15, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Shutdown Communication . . . . . . . . . . . . . . . . . . . 2 2. Shutdown Communication . . . . . . . . . . . . . . . . . . . 3
3. Operational Considerations . . . . . . . . . . . . . . . . . 3 3. Operational Considerations . . . . . . . . . . . . . . . . . 3
4. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 4 4. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 4 7. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 4
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . 5 8.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
skipping to change at page 3, line 29 skipping to change at page 3, line 41
Length: this 8-bit field represents the length of the Shutdown Length: this 8-bit field represents the length of the Shutdown
Communication field in octets. The length value MUST range from 0 Communication field in octets. The length value MUST range from 0
to 128 inclusive. When the length value is zero, no Shutdown to 128 inclusive. When the length value is zero, no Shutdown
Communication field follows. Communication field follows.
Shutdown Communication: to support international characters, the Shutdown Communication: to support international characters, the
Shutdown Communication field MUST be encoded using UTF-8. A Shutdown Communication field MUST be encoded using UTF-8. A
receiving BGP speaker MUST NOT interpret invalid UTF-8 sequences. receiving BGP speaker MUST NOT interpret invalid UTF-8 sequences.
Note that when the Shutdown Communication contains multibyte Note that when the Shutdown Communication contains multibyte
characters, the number of characters will be less than the length characters, the number of characters will be less than the length
value. value. This field is not NUL terminated.
Mechanisms concerning the reporting of information contained in the Mechanisms concerning the reporting of information contained in the
Shutdown Communication are implementation specific but SHOULD include Shutdown Communication are implementation specific but SHOULD include
methods such as SYSLOG [RFC5424]. methods such as SYSLOG [RFC5424].
3. Operational Considerations 3. Operational Considerations
Operators are encouraged to use the Shutdown Communication to inform Operators are encouraged to use the Shutdown Communication to inform
their peers of the reason for the shutdown of the BGP session and their peers of the reason for the shutdown of the BGP session and
include out-of-band reference materials. An example of a useful include out-of-band reference materials. An example of a useful
skipping to change at page 6, line 14 skipping to change at page 6, line 22
[UTR36] Davis, M. and M. Suignard, "Unicode Security [UTR36] Davis, M. and M. Suignard, "Unicode Security
Considerations", Unicode Technical Report #36, August Considerations", Unicode Technical Report #36, August
2010, <http://unicode.org/reports/tr36/>. 2010, <http://unicode.org/reports/tr36/>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors would like to gratefully acknowledge Tom Scholl, David The authors would like to gratefully acknowledge Tom Scholl, David
Freedman, Jared Mauch, Jeff Haas, Peter Hessler, Bruno Decraene, John Freedman, Jared Mauch, Jeff Haas, Peter Hessler, Bruno Decraene, John
Heasley, Peter van Dijk, Arjen Zonneveld, James Bensley, Susan Hares, Heasley, Peter van Dijk, Arjen Zonneveld, James Bensley, Susan Hares,
and Saku Ytti. Saku Ytti, and Lou Berger.
Authors' Addresses Authors' Addresses
Job Snijders Job Snijders
NTT Communications NTT Communications
Theodorus Majofskistraat 100 Theodorus Majofskistraat 100
Amsterdam 1065 SZ Amsterdam 1065 SZ
The Netherlands The Netherlands
Email: job@ntt.net Email: job@ntt.net
 End of changes. 9 change blocks. 
8 lines changed or deleted 20 lines changed or added

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