draft-ietf-idr-rfc8203bis-07.txt   draft-ietf-idr-rfc8203bis-08.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: March 22, 2021 Juniper Expires: April 17, 2021 Juniper
A. Azimov A. Azimov
Yandex Yandex
September 18, 2020 October 14, 2020
Extended BGP Administrative Shutdown Communication Extended BGP Administrative Shutdown Communication
draft-ietf-idr-rfc8203bis-07 draft-ietf-idr-rfc8203bis-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 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 of up to 255 octets to improve communication Shutdown Communication of up to 255 octets to improve communication
using multibyte character sets. using multibyte character sets.
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 March 22, 2021. This Internet-Draft will expire on April 17, 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 30 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Shutdown Communication . . . . . . . . . . . . . . . . . . . 2 2. Shutdown Communication . . . . . . . . . . . . . . . . . . . 2
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. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 6
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 as 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
skipping to change at page 4, line 10 skipping to change at page 4, line 10
"[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.
If a Shutdown Communication longer than 128 octets is sent to a BGP If a Shutdown Communication longer than 128 octets is sent to a BGP
speaker that implements [RFC8203], then that speaker will treat it as speaker that implements [RFC8203], then that speaker will treat it as
an error, the consequence of which is a log message. For this an error, the consequence of which should be a log message.
reason, operators would be wise to keep shutdown communications to
less than 128 octets when feasible.
There is no guarantee that the receiver supports either this If a Shutdown Communication of any length is sent to a BGP speaker
specification or [RFC8203], so any shutdown communication might not that implements neither [RFC8203] nor this specification, then that
be logged in an easily-readable form at all. Therefore, operators speaker will treat it as an error, the consequence of which should be
would also be wise not to rely on shutdown communications as their a log message.
sole form of communication with their peer for important events.
In any case, a receiver of a NOTIFICATION message is unable to
acknowledge the receipt and correct understanding of any Shutdown
Communication.
Operators should not rely on Shutdown Communications as their sole
form of communication with their peer for important events.
If it is known that the peer BGP speaker supports this specification,
then a Shutdown Communication that is not longer than 255 octets MAY
be sent. Otherwise, a Shutdown Communication MAY be sent, but it
SHOULD NOT be longer than 128 octets.
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
 End of changes. 7 change blocks. 
13 lines changed or deleted 22 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/