draft-ietf-idr-shutdown-06.txt | draft-ietf-idr-shutdown-07.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: August 15, 2017 J. Scudder | Expires: September 4, 2017 J. Scudder | |||
Juniper | Juniper | |||
February 11, 2017 | March 3, 2017 | |||
BGP Administrative Shutdown Communication | BGP Administrative Shutdown Communication | |||
draft-ietf-idr-shutdown-06 | draft-ietf-idr-shutdown-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. | 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 August 15, 2017. | This Internet-Draft will expire on September 4, 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 5, line 21 ¶ | skipping to change at page 5, line 21 ¶ | |||
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 ExaBGP | o ExaBGP | |||
o pmacct | o pmacct | |||
o OpenBGPD | o OpenBGPD | |||
o GoBGP | o GoBGP | |||
o FreeRangeRouting (frr) | ||||
o tcpdump (packet analyser) | o tcpdump (packet analyser) | |||
o Wireshark (packet analyser) | o Wireshark (packet analyser) | |||
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, | |||
End of changes. 5 change blocks. | ||||
4 lines changed or deleted | 5 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/ |