draft-ietf-idr-shutdown-00.txt   draft-ietf-idr-shutdown-01.txt 
IDR J. Snijders IDR J. Snijders
Internet-Draft NTT Internet-Draft NTT
Intended status: Standards Track J. Heitz Updates: 4486 (if approved) J. Heitz
Expires: June 3, 2017 Cisco Intended status: Standards Track Cisco
J. Scudder Expires: June 3, 2017 J. Scudder
Juniper Juniper
November 30, 2016 November 30, 2016
The Shutdown Communication BGP Cease Notification Message subcode BGP Administrative Shutdown with Additional Communication
draft-ietf-idr-shutdown-00 draft-ietf-idr-shutdown-01
Abstract Abstract
This document defines the BGP Cease NOTIFICATION message "Shutdown This document enhances the BGP Cease NOTIFICATION message
Communication" subcode for operators to transmit a short freeform "Administrative Shutdown" subcode for operators to transmit a short
message to describe why a BGP session was shutdown. freeform message to describe why a BGP session was shutdown.
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 2, line 41 skipping to change at page 2, line 41
via off-line methods such email or telephone calls. This document via off-line methods such email or telephone calls. This document
specifies a mechanism to transmit a short freeform UTF-8 [RFC3629] specifies a mechanism to transmit a short freeform UTF-8 [RFC3629]
message as part of a Cease NOTIFICATION message [RFC4486] to inform message as part of a Cease NOTIFICATION message [RFC4486] to inform
the peer why the BGP session is being shutdown. the peer why the BGP session is being shutdown.
2. Shutdown Communication 2. Shutdown Communication
If a BGP speaker decides to terminate its session with a BGP If a BGP speaker decides to terminate its session with a BGP
neighbor, then the BGP speaker MAY send to the neighbor a neighbor, then the BGP speaker MAY send to the neighbor a
NOTIFICATION message with the Error Code "Cease" and the Error NOTIFICATION message with the Error Code "Cease" and the Error
Subcode TBD "Shutdown Communication" followed by a freeform UTF-8 Subcode "Administrative Shutdown" followed by a freeform UTF-8
encoded string with a REQUIRED maximum length of 128 octets. The encoded string with a REQUIRED maximum length of 128 octets. The
contents of the string are at the operator's discretion. contents of the string are at the operator's discretion.
The Shutdown Communication Cease NOTIFICATION message is encoded as The Shutdown Communication Cease NOTIFICATION message is encoded as
following: below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error code 6 | subcode TBD | ... | | Error code 6 | subcode 2 | Length | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... Shutdown Communication ... | | ... Shutdown Communication ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Length value can range from 0 to 128 and indicates how many
octets of Shutdown Communication follow.
To support international characters, the Shutdown Communication field To support international characters, the Shutdown Communication field
MUST be encoded using UTF-8. MUST be encoded using UTF-8.
The sending BGP speaker SHOULD avoid octet values below 32 (control The sending BGP speaker SHOULD avoid octet values below 32 (control
characters), however these values are legal. Following UNICODE TR36 characters), however these values are legal. Following UNICODE TR36
[UTR36], Sec 3.1, the sending BGP speaker MUST encode messages in the [UTR36], Sec 3.1, the sending BGP speaker MUST encode messages in the
"shortest form" and MUST NOT interpret messages in the "non shortest "shortest form" and MUST NOT interpret messages in the "non-shortest
form". A receiving BGP speaker MUST NOT interpret invalid UTF-8 form". A receiving BGP speaker MUST NOT interpret invalid UTF-8
sequences. sequences.
It is RECOMMENDED that a BGP speaker receiving a Shutdown
Communication observe retry behaviour in line with the RFC4486
[RFC4486] behaviour for "Administrative Shutdown" (sec 4.0).
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 with a reference and reason as to why the BGP session is their peers of the reason for the shutdown of the BGP session and
shut down. An example of a useful Shutdown Communication would be: include out-of-band reference materials. An example of a useful
Shutdown Communication would be:
"[VNOC-1-1438367390] software upgrade, back in 2 hours" "[TICKET-1-1438367390] software upgrade, back in 2 hours"
"[VNOC-1-1438367390]" is a ticket reference with significance to both "[TICKET-1-1438367390]" is a ticket reference with significance to
the sender and receiver, followed by a brief human readable message both the sender and receiver, followed by a brief human readable
regarding the work triggering the BGP session shutdown followed by an message regarding the reason for the BGP session shutdown followed by
indication about the length of the maintenance. The receiver can now an indication about the length of the maintenance. The receiver can
use the string 'VNOC-1-1438367390' to search in their email archive now use the string 'TICKET-1-1438367390' to search in their email
to find more details. archive to find more details.
4. Error Handling 4. Error Handling
Any erroneous or malformed Shutdown Communication received SHOULD be Any erroneous or malformed Shutdown Communication received SHOULD be
logged for the attention of the operator and then MAY be discarded. logged for the attention of the operator and then MAY be discarded.
5. IANA Considerations 5. IANA Considerations
Per this document, IANA is requested to assign a subcode named Per this document, IANA is requested to reference this document at
"Shutdown Communication" in the "Cease NOTIFICATION message subcodes" subcode "Administrative Shutdown" in the "Cease NOTIFICATION message
registry under the "Border Gateway Protocol (BGP) Parameters" group. subcodes" registry under the "Border Gateway Protocol (BGP)
Parameters" group.
6. Security Considerations 6. Security Considerations
This document uses UTF-8 encoding for the Shutdown Communication. This document uses UTF-8 encoding for the Shutdown Communication.
There are a number of security issues with UNICODE. Any implementer There are a number of security issues with UNICODE. Implementers and
and operator is advised to review UNICODE TR36 [UTR36] to learn about operator are advised to review UNICODE TR36 [UTR36] to learn about
these issues. This document guards against the technical issues these issues. This document guards against the technical issues
outlined in UTR36 by REQUIRING "shortest form" encoding. However, outlined in UTR36 by REQUIRING "shortest form" encoding. However,
the visual spoofing due to character confusion still persists. This the visual spoofing due to character confusion still persists. This
document tries to minimize the effects of visual spoofing by allowing document tries to minimize the effects of visual spoofing by allowing
UNICODE only where local script is expected and needed, and by UNICODE only where local script is expected and needed, and by
limiting the length of the Shutdown Communication. limiting the length of the Shutdown Communication.
7. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION 7. Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION
This section records the status of known implementations of the This section records the status of known implementations of the
skipping to change at page 5, line 35 skipping to change at page 5, line 35
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<http://www.rfc-editor.org/info/rfc7942>. <http://www.rfc-editor.org/info/rfc7942>.
[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 author would like to gratefully acknowledge Tom Scholl, David The authors would like to gratefully acknowledge Tom Scholl, David
Freedman, and Jared Mauch. Freedman, Jared Mauch, Jeff Haas, Peter Hessler, Bruno Decraene, and
John Heasley.
Authors' Addresses Authors' Addresses
Job Snijders Job Snijders
NTT Communications NTT Communications
Theodorus Majofskistraat 100 Theodorus Majofskistraat 100
Amsterdam 1065 SZ Amsterdam 1065 SZ
NL NL
Email: job@ntt.net Email: job@ntt.net
 End of changes. 15 change blocks. 
32 lines changed or deleted 34 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/