draft-ietf-idr-rfc8203bis-02.txt   draft-ietf-idr-rfc8203bis-03.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 27, 2019 Juniper Expires: October 27, 2019 Juniper
A. Azimov A. Azimov
Qrator Yandex
April 25, 2019 April 25, 2019
Extended BGP Administrative Shutdown Communication Extended BGP Administrative Shutdown Communication
draft-ietf-idr-rfc8203bis-02 draft-ietf-idr-rfc8203bis-03
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 to improve communication using multibyte
character sets. character sets.
skipping to change at page 5, line 24 skipping to change at page 5, line 24
been spent to verify the information presented here that was supplied been spent to verify the information presented here that was supplied
by IETF contributors. This is not intended as, and must not be by IETF contributors. This is not intended as, and must not be
construed to be, a catalog of available implementations or their construed to be, a catalog of available implementations or their
features. Readers are advised to note that other implementations may features. Readers are advised to note that other implementations may
exist. exist.
As of today these vendors have produced an implementation of the As of today these vendors have produced an implementation of the
Shutdown Communication: Shutdown Communication:
o Juniper Junos o Juniper Junos
o ... o OpenBSD OpenBGPD
o ... o ...
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 7, line 42 skipping to change at page 7, line 42
John Scudder John Scudder
Juniper Networks Juniper Networks
1194 N. Mathilda Ave 1194 N. Mathilda Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
United States of America United States of America
Email: jgs@juniper.net Email: jgs@juniper.net
Alexander Azimov Alexander Azimov
Qrator Labs Yandex
Email: aa@qrator.net Email: a.e.azimov@gmail.com
 End of changes. 5 change blocks. 
4 lines changed or deleted 4 lines changed or added

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