draft-ietf-grow-bgp-session-culling-01.txt   draft-ietf-grow-bgp-session-culling-02.txt 
Global Routing Operations W. Hargrave Global Routing Operations W. Hargrave
Internet-Draft LONAP Internet-Draft LONAP
Intended status: Best Current Practice M. Griswold Intended status: Best Current Practice M. Griswold
Expires: October 7, 2017 20C Expires: January 4, 2018 20C
J. Snijders J. Snijders
NTT NTT
N. Hilliard N. Hilliard
INEX INEX
April 5, 2017 July 3, 2017
Mitigating Negative Impact of Maintenance through BGP Session Culling Mitigating Negative Impact of Maintenance through BGP Session Culling
draft-ietf-grow-bgp-session-culling-01 draft-ietf-grow-bgp-session-culling-02
Abstract Abstract
This document outlines an approach to mitigate negative impact on This document outlines an approach to mitigate negative impact on
networks resulting from maintenance activities. It includes guidance networks resulting from maintenance activities. It includes guidance
for both IP networks and Internet Exchange Points (IXPs). The for both IP networks and Internet Exchange Points (IXPs). The
approach is to ensure BGP-4 sessions affected by the maintenance are approach is to ensure BGP-4 sessions affected by the maintenance are
forcefully torn down before the actual maintenance activities forcefully torn down before the actual maintenance activities
commence. commence.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 October 7, 2017. This Internet-Draft will expire on January 4, 2018.
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 4, line 12 skipping to change at page 4, line 12
between the Administrative Shutdown and the impacting maintenance between the Administrative Shutdown and the impacting maintenance
activities is warranted. activities is warranted.
After the maintenance activities have concluded, the operator is After the maintenance activities have concluded, the operator is
expected to restore the BGP sessions to their original Administrative expected to restore the BGP sessions to their original Administrative
state. state.
3.1.1. Maintenance Considerations 3.1.1. Maintenance Considerations
Initiators of the Administrative Shutdown could consider to use Initiators of the Administrative Shutdown could consider to use
[Graceful Shutdown] to facilitate smooth drainage of traffic prior to Graceful Shutdown [I-D.ietf-grow-bgp-gshut] to facilitate smooth
session tear down, and the Shutdown Communication drainage of traffic prior to session tear down, and the Shutdown
[I-D.ietf-idr-shutdown] to inform the remote side on the nature and Communication [I-D.ietf-idr-shutdown] to inform the remote side on
duration of the maintenance activities. the nature and duration of the maintenance activities.
3.2. Involuntary BGP Session Teardown Recommendations 3.2. Involuntary BGP Session Teardown Recommendations
In the case where multilateral interconnection between BGP speakers In the case where multilateral interconnection between BGP speakers
is facilitated through a switched layer-2 fabric, such as commonly is facilitated through a switched layer-2 fabric, such as commonly
seen at Internet Exchange Points (IXPs), different operational seen at Internet Exchange Points (IXPs), different operational
considerations can apply. considerations can apply.
Operational experience shows many network operators are unable to Operational experience shows many network operators are unable to
carry out the Voluntary BGP Session Teardown recommendations, because carry out the Voluntary BGP Session Teardown recommendations, because
skipping to change at page 6, line 49 skipping to change at page 6, line 49
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
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>.
7.2. Informative References 7.2. Informative References
[I-D.ietf-grow-bgp-gshut]
Francois, P., Decraene, B., Pelsser, C., Patel, K., and C.
Filsfils, "Graceful BGP session shutdown", draft-ietf-
grow-bgp-gshut-09 (work in progress), June 2017.
[I-D.ietf-idr-shutdown] [I-D.ietf-idr-shutdown]
Snijders, J., Heitz, J., and J. Scudder, "BGP Snijders, J., Heitz, J., and J. Scudder, "BGP
Administrative Shutdown Communication", draft-ietf-idr- Administrative Shutdown Communication", draft-ietf-idr-
shutdown-07 (work in progress), March 2017. shutdown-10 (work in progress), June 2017.
[I-D.ietf-rtgwg-bgp-pic] [I-D.ietf-rtgwg-bgp-pic]
Bashandy, A., Filsfils, C., and P. Mohapatra, "BGP Prefix Bashandy, A., Filsfils, C., and P. Mohapatra, "BGP Prefix
Independent Convergence", draft-ietf-rtgwg-bgp-pic-01 Independent Convergence", draft-ietf-rtgwg-bgp-pic-05
(work in progress), June 2016. (work in progress), May 2017.
7.3. URIs 7.3. URIs
[1] https://github.com/bgp/bgp-session-culling-config-examples [1] https://github.com/bgp/bgp-session-culling-config-examples
Appendix A. Example packet filters Appendix A. Example packet filters
Example packet filters for "Involuntary BGP Session Teardown" at an Example packet filters for "Involuntary BGP Session Teardown" at an
IXP with LAN prefixes 192.0.2.0/24 and 2001:db8:2::/64. IXP with LAN prefixes 192.0.2.0/24 and 2001:db8:2::/64.
 End of changes. 8 change blocks. 
11 lines changed or deleted 16 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/