draft-ietf-idr-shutdown-07.txt   draft-ietf-idr-shutdown-08.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: September 4, 2017 J. Scudder Expires: November 6, 2017 J. Scudder
Juniper Juniper
March 3, 2017 May 5, 2017
BGP Administrative Shutdown Communication BGP Administrative Shutdown Communication
draft-ietf-idr-shutdown-07 draft-ietf-idr-shutdown-08
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. session was shutdown or reset. This document updates RFC 4486.
Requirements Language Requirements Language
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 September 4, 2017. This Internet-Draft will expire on November 6, 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
skipping to change at page 2, line 35 skipping to change at page 2, line 35
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Shutdown Communication . . . . . . . . . . . . . . . . . . . 3 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 5
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 . . . . . . . . . . . . . . . . . 6
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
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 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] updates [RFC4486] by specifying a mechanism to transmit a short
message as part of a Cease NOTIFICATION message [RFC4486] to inform freeform UTF-8 [RFC3629] message as part of a Cease NOTIFICATION
the peer why the BGP session is being shutdown or reset. message [RFC4271] to inform the peer why the BGP session is being
shutdown or reset.
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, and it sends a NOTIFICATION message with the Error Code
NOTIFICATION message with the Error Code "Cease" and Error Subcode "Cease" and Error Subcode "Administrative Shutdown" or
"Administrative Shutdown" or "Administrative Reset" followed by a "Administrative Reset" [RFC4486], it MAY include an UTF-8 encoded
length field and an UTF-8 encoded string. The contents of the string string. The contents of the string are at the operator's discretion.
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
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
Reset"). Reset").
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
skipping to change at page 4, line 16 skipping to change at page 4, line 18
"[TICKET-1-1438367390]" is a ticket reference with significance to "[TICKET-1-1438367390]" is a ticket reference with significance to
both the sender and receiver, followed by a brief human readable both the sender and receiver, followed by a brief human readable
message regarding the reason for the BGP session shutdown followed by message regarding the reason for the BGP session shutdown followed by
an indication about the length of the maintenance. The receiver can an indication about the length of the maintenance. The receiver can
now use the string 'TICKET-1-1438367390' to search in their email now use the string 'TICKET-1-1438367390' to search in their email
archive to find more details. archive to find more details.
4. Error Handling 4. Error Handling
Any erroneous or malformed Shutdown Communication received SHOULD be If a Shutdown Communication with an invalid Length value, or an
logged for the attention of the operator and then MAY be discarded. invalid UTF-8 sequence is received, a message indicating this event
SHOULD be logged for the attention of the operator. An erroneous or
malformed Shutdown 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 Per this document, IANA is requested to reference this document at
subcode "Administrative Shutdown", and at subcode "Administrative subcode "Administrative Shutdown", and at subcode "Administrative
Reset" in the "Cease NOTIFICATION message subcodes" registry under Reset" in the "Cease NOTIFICATION message subcodes" registry under
the "Border Gateway Protocol (BGP) Parameters" group in addition to the "Border Gateway Protocol (BGP) Parameters" group in addition to
[RFC4486]. [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
operator are 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. UTF-8 "Shortest Form" encoding is REQUIRED to guard
outlined in UTR36 by REQUIRING "shortest form" encoding. However, against the technical issues outlined in UTR36. However, the visual
the visual spoofing due to character confusion still persists. This spoofing due to character confusion still persists. This
specification minimizes the effects of visual spoofing by limiting specification minimizes the effects of visual spoofing by limiting
the length of the Shutdown Communication. the length of the Shutdown Communication.
Users of this mechanism should be aware that unless a transport that Users of this mechanism should be aware that unless a transport that
provides integrity (such as TCP-AO [RFC5925]) is used for the BGP provides integrity is used for the BGP session in question, a
session in question, a Shutdown Communication message could be Shutdown Communication message could be forged. Unless a transport
forged. Unless a transport that provides confidentiality (such as that provides confidentiality is used, a Shutdown Communication
IPSec [RFC4303]) is used, a Shutdown Communication message could be message could be snooped by an attacker. These issues are common to
snooped by an attacker. These issues are common to any BGP message any BGP message but may be of greater interest in the context of this
but may be of greater interest in the context of this proposal since proposal since the information carried in the message is generally
the information carried in the message is generally expected to be expected to be used for human-to-human communication. Refer to the
used for human-to-human communication. related considerations in [RFC4271] and [RFC4272].
Users of this mechanism should consider applying data minimization
practises as outlined in Section 6.1 [RFC6973] as a received Shutdown
Communication may be used at the receiver's discretion.
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
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in RFC7942. The Internet-Draft, and is based on a proposal described in RFC7942. The
description of implementations in this section is intended to assist description of implementations in this section is intended to assist
the IETF in its decision processes in progressing drafts to RFCs. the IETF in its decision processes in progressing drafts to RFCs.
Please note that the listing of any individual implementation here Please note that the listing of any individual implementation here
does not imply endorsement by the IETF. Furthermore, no effort has does not imply endorsement by the IETF. Furthermore, no effort has
skipping to change at page 5, line 49 skipping to change at page 6, line 11
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006,
<http://www.rfc-editor.org/info/rfc4271>. <http://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, <http://www.rfc-editor.org/info/rfc4486>. April 2006, <http://www.rfc-editor.org/info/rfc4486>.
8.2. Informative References 8.2. Informative References
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis",
RFC 4303, DOI 10.17487/RFC4303, December 2005, RFC 4272, DOI 10.17487/RFC4272, January 2006,
<http://www.rfc-editor.org/info/rfc4303>. <http://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,
<http://www.rfc-editor.org/info/rfc5424>. <http://www.rfc-editor.org/info/rfc5424>.
[RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
Authentication Option", RFC 5925, DOI 10.17487/RFC5925, Morris, J., Hansen, M., and R. Smith, "Privacy
June 2010, <http://www.rfc-editor.org/info/rfc5925>. Considerations for Internet Protocols", RFC 6973,
DOI 10.17487/RFC6973, July 2013,
<http://www.rfc-editor.org/info/rfc6973>.
[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, and Lou Berger. Saku Ytti, Lou Berger, and Alvaro Retana.
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. 15 change blocks. 
34 lines changed or deleted 45 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/