draft-ietf-idr-rfc8203bis-06.txt   draft-ietf-idr-rfc8203bis-07.txt 
IDR J. Snijders IDR J. Snijders
Internet-Draft NTT Internet-Draft NTT
Obsoletes: 8203 (if approved) J. Heitz Obsoletes: 8203 (if approved) J. Heitz
Updates: 4486 (if approved) Cisco Updates: 4486 (if approved) Cisco
Intended status: Standards Track J. Scudder Intended status: Standards Track J. Scudder
Expires: October 17, 2020 Juniper Expires: March 22, 2021 Juniper
A. Azimov A. Azimov
Yandex Yandex
April 15, 2020 September 18, 2020
Extended BGP Administrative Shutdown Communication Extended BGP Administrative Shutdown Communication
draft-ietf-idr-rfc8203bis-06 draft-ietf-idr-rfc8203bis-07
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. This document updates RFC 4486 and session was shutdown or reset. This document updates RFC 4486 and
obsoletes RFC 8203 by defining an Extended BGP Administrative obsoletes RFC 8203 by defining an Extended BGP Administrative
Shutdown Communication to improve communication using multibyte Shutdown Communication of up to 255 octets to improve communication
character sets. using multibyte character sets.
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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Status of This Memo Status of This Memo
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 October 17, 2020. This Internet-Draft will expire on March 22, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 39 skipping to change at page 2, line 39
7.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6
Appendix B. Changes to RFC 8203 . . . . . . . . . . . . . . . . 6 Appendix B. Changes to RFC 8203 . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
It can be troublesome for an operator to correlate a BGP-4 [RFC4271] It can be troublesome for an operator to correlate a BGP-4 [RFC4271]
session teardown in the network with a notice that was transmitted session teardown in the network with a notice that was transmitted
via offline methods such email or telephone calls. This document via offline methods such as email or telephone calls. This document
updates [RFC4486] by specifying a mechanism to transmit a short updates [RFC4486] by specifying a mechanism to transmit a short
freeform UTF-8 [RFC3629] message as part of a Cease NOTIFICATION freeform UTF-8 [RFC3629] message as part of a Cease NOTIFICATION
message [RFC4271] to inform the peer why the BGP session is being message [RFC4271] to inform the peer why the BGP session is being
shutdown or reset. This document obsoletes [RFC8203]; the specific shutdown or reset. This document obsoletes [RFC8203]; the specific
differences and rationale are discussed in detail in Appendix B. differences and rationale are discussed in detail in Appendix B.
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, and it sends a NOTIFICATION message with the Error Code neighbor, and it sends a NOTIFICATION message with the Error Code
"Cease" and Error Subcode "Administrative Shutdown" or "Cease" and Error Subcode "Administrative Shutdown" or
"Administrative Reset" [RFC4486], it MAY include a UTF-8 encoded "Administrative Reset" [RFC4486], it MAY include a UTF-8 encoded
string. The contents of the string are at the operator's discretion. string. The contents of the string are at the operator's discretion.
The Cease NOTIFICATION message with a Shutdown Communication is The Cease NOTIFICATION message with a Shutdown Communication is
encoded as below: encoded as 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 | Length | ... \ | Error Code 6 | Subcode | Length | ... \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ /
\ \ \ \
/ ... Shutdown Communication ... / / ... Shutdown Communication ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1 Figure 1
Subcode: the Error Subcode value MUST be one of the following Subcode: the Error Subcode value MUST be one of the following
values: 2 ("Administrative Shutdown") or 4 ("Administrative values: 2 ("Administrative Shutdown") or 4 ("Administrative
skipping to change at page 3, line 33 skipping to change at page 3, line 33
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. When the length value is zero, no Communication field in octets. When the length value is zero, no
Shutdown Communication field follows. Shutdown 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. This field is not NULL terminated. value. This field is not NUL terminated. UTF-8 "Shortest Form"
encoding is REQUIRED to guard against the technical issues
outlined in [UTR36].
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 4, line 28 skipping to change at page 4, line 29
4. Error Handling 4. Error Handling
If a Shutdown Communication with an invalid UTF-8 sequence is If a Shutdown Communication with an invalid UTF-8 sequence is
received, a message indicating this event SHOULD be logged for the received, a message indicating this event SHOULD be logged for the
attention of the operator. An erroneous or malformed Shutdown attention of the operator. An erroneous or malformed Shutdown
Communication itself MAY be logged in a hexdump format. Communication itself MAY be logged in a hexdump format.
5. IANA Considerations 5. IANA Considerations
Per this document, IANA is requested to reference this document at IANA is requested to reference this document at subcode
subcode "Administrative Shutdown", and at subcode "Administrative "Administrative Shutdown", and at subcode "Administrative Reset" in
Reset" in the "BGP Cease NOTIFICATION message subcodes" registry the "BGP Cease NOTIFICATION message subcodes" registry under the
under the "Border Gateway Protocol (BGP) Parameters" group in "Border Gateway Protocol (BGP) Parameters" group in addition to
addition to [RFC4486] and [RFC8203]. [RFC4486].
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. Implementers and There are a number of security issues with Unicode. Implementers and
operators are advised to review Unicode Technical Report #36 [UTR36] operators are advised to review Unicode Technical Report #36 [UTR36]
to learn about these issues. UTF-8 "Shortest Form" encoding is to learn about these issues. UTF-8 "Shortest Form" encoding is
REQUIRED to guard against the technical issues outlined in [UTR36]. REQUIRED to guard against the technical issues outlined in [UTR36].
As BGP Shutdown Communications are likely to appear in syslog output, As BGP Shutdown Communications are likely to appear in syslog output,
skipping to change at page 5, line 41 skipping to change at page 5, line 42
<https://www.rfc-editor.org/info/rfc4271>. <https://www.rfc-editor.org/info/rfc4271>.
[RFC4486] Chen, E. and V. Gillet, "Subcodes for BGP Cease [RFC4486] Chen, E. and V. Gillet, "Subcodes for BGP Cease
Notification Message", RFC 4486, DOI 10.17487/RFC4486, Notification Message", RFC 4486, DOI 10.17487/RFC4486,
April 2006, <https://www.rfc-editor.org/info/rfc4486>. April 2006, <https://www.rfc-editor.org/info/rfc4486>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8203] Snijders, J., Heitz, J., and J. Scudder, "BGP
Administrative Shutdown Communication", RFC 8203,
DOI 10.17487/RFC8203, July 2017,
<https://www.rfc-editor.org/info/rfc8203>.
7.2. Informative References 7.2. Informative References
[RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis",
RFC 4272, DOI 10.17487/RFC4272, January 2006, RFC 4272, DOI 10.17487/RFC4272, January 2006,
<https://www.rfc-editor.org/info/rfc4272>. <https://www.rfc-editor.org/info/rfc4272>.
[RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424,
DOI 10.17487/RFC5424, March 2009, DOI 10.17487/RFC5424, March 2009,
<https://www.rfc-editor.org/info/rfc5424>. <https://www.rfc-editor.org/info/rfc5424>.
[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
Morris, J., Hansen, M., and R. Smith, "Privacy Morris, J., Hansen, M., and R. Smith, "Privacy
Considerations for Internet Protocols", RFC 6973, Considerations for Internet Protocols", RFC 6973,
DOI 10.17487/RFC6973, July 2013, DOI 10.17487/RFC6973, July 2013,
<https://www.rfc-editor.org/info/rfc6973>. <https://www.rfc-editor.org/info/rfc6973>.
[RFC8203] Snijders, J., Heitz, J., and J. Scudder, "BGP
Administrative Shutdown Communication", RFC 8203,
DOI 10.17487/RFC8203, July 2017,
<https://www.rfc-editor.org/info/rfc8203>.
[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,
Saku Ytti, Lou Berger, Alvaro Retana, and Adam Roach. Saku Ytti, Lou Berger, Alvaro Retana, and Adam Roach.
skipping to change at page 6, line 44 skipping to change at page 6, line 45
Appendix B. Changes to RFC 8203 Appendix B. Changes to RFC 8203
The maximum permitted length was changed from 128 to 255. The maximum permitted length was changed from 128 to 255.
Feedback from operators based in regions which predominantly use Feedback from operators based in regions which predominantly use
multibyte character sets, showed that messages similar in meaning to multibyte character sets, showed that messages similar in meaning to
what can be send in other languages in using single-byte encoding, what can be send in other languages in using single-byte encoding,
failed to fit within the Length constraints as specified by failed to fit within the Length constraints as specified by
[RFC8203]. For example, the phrase: 'Planned work to add switch to [RFC8203]. For example, the phrase: 'Planned work to add switch to
stack. Completion time - 30 minutes' has length 65 bytes. Its stack. Completion time - 30 minutes' has length 65 bytes. Its
translation in Russian translation in Russian has length 139 bytes.
'&#1055;&#1083;&#1072;&#1085;&#1086;&#1074;&#1099;&#1077;
&#1088;&#1072;&#1073;&#1086;&#1090;&#1099; &#1087;&#1086; &#1076;&#10 If a Shutdown Communication message longer than 128 octets is sent to
86;&#1073;&#1072;&#1074;&#1083;&#1077;&#1085;&#1080;&#1102; &#1082;&# a BGP speaker that implements [RFC8203], then that speaker will bring
1086;&#1084;&#1084;&#1091;&#1090;&#1072;&#1090;&#1086;&#1088;&#1072;& it to the attention of an operator, but will otherwise process the
#1074; NOTIFICATION message as normal.
&#1089;&#1090;&#1077;&#1082;.&#1042;&#1088;&#1077;&#1084;&#1103; &#10
79;&#1072;&#1074;&#1077;&#1088;&#1096;&#1077;&#1085;&#1080;&#1103; -
30&#1084;&#1080;&#1085;&#1091;&#1090;' (See PDF for non-ASCII
character string) has length 139 bytes.
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. 12 change blocks. 
29 lines changed or deleted 27 lines changed or added

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