draft-ietf-idr-rs-bfd-05.txt   draft-ietf-idr-rs-bfd-06.txt 
Network Working Group R. Bush Network Working Group R. Bush
Internet-Draft Internet Initiative Japan Internet-Draft Internet Initiative Japan
Intended status: Standards Track J. Haas Intended status: Standards Track J. Haas
Expires: October 13, 2018 J. Scudder Expires: April 4, 2019 J. Scudder
Juniper Networks, Inc. Juniper Networks, Inc.
A. Nipper A. Nipper
C. Dietzel C. Dietzel
DE-CIX DE-CIX
April 11, 2018 October 1, 2018
Making Route Servers Aware of Data Link Failures at IXPs Making Route Servers Aware of Data Link Failures at IXPs
draft-ietf-idr-rs-bfd-05 draft-ietf-idr-rs-bfd-06
Abstract Abstract
When BGP route servers are used, the data plane is not congruent with When BGP route servers are used, the data plane is not congruent with
the control plane. Therefore, peers at an Internet exchange can lose the control plane. Therefore, peers at an Internet exchange can lose
data connectivity without the control plane being aware of it, and data connectivity without the control plane being aware of it, and
packets are lost. This document proposes the use of a newly defined packets are lost. This document proposes the use of a newly defined
BGP Subsequent Address Family Identifier (SAFI) both to allow the BGP Subsequent Address Family Identifier (SAFI) both to allow the
route server to request its clients use BFD to track data plane route server to request its clients use BFD to track data plane
connectivity to their peers' addresses, and for the clients to signal connectivity to their peers' addresses, and for the clients to signal
skipping to change at page 1, line 43 skipping to change at page 1, line 43
words, without normative meaning. words, without normative meaning.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 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 13, 2018. This Internet-Draft will expire on April 4, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 (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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 11, line 27 skipping to change at page 11, line 27
includes forcing a BFD session to stay Up when its real state is includes forcing a BFD session to stay Up when its real state is
Down. These attacks may be mitigated using the BFD security Down. These attacks may be mitigated using the BFD security
mechanisms defined in [RFC5880]. mechanisms defined in [RFC5880].
12. References 12. References
12.1. Normative References 12.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-
<https://www.rfc-editor.org/info/rfc2119>. 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, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc4271>. editor.org/info/rfc4271>.
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760,
DOI 10.17487/RFC4760, January 2007, DOI 10.17487/RFC4760, January 2007, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc4760>. editor.org/info/rfc4760>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>. <https://www.rfc-editor.org/info/rfc5880>.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881,
DOI 10.17487/RFC5881, June 2010, DOI 10.17487/RFC5881, June 2010, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc5881>. editor.org/info/rfc5881>.
[RFC7947] Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker, [RFC7947] Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker,
"Internet Exchange BGP Route Server", RFC 7947, "Internet Exchange BGP Route Server", RFC 7947,
DOI 10.17487/RFC7947, September 2016, DOI 10.17487/RFC7947, September 2016, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc7947>. editor.org/info/rfc7947>.
12.2. Informative References 12.2. Informative References
[I-D.chen-bfd-unsolicited] [I-D.chen-bfd-unsolicited]
Chen, E., Shen, N., and R. Raszuk, "Unsolicited BFD for Chen, E., Shen, N., and R. Raszuk, "Unsolicited BFD for
Sessionless Applications", draft-chen-bfd-unsolicited-02 Sessionless Applications", draft-chen-bfd-unsolicited-02
(work in progress), January 2018. (work in progress), January 2018.
[I-D.ietf-idr-bgp-bestpath-selection-criteria] [I-D.ietf-idr-bgp-bestpath-selection-criteria]
Asati, R., "BGP Bestpath Selection Criteria Enhancement", Asati, R., "BGP Bestpath Selection Criteria Enhancement",
draft-ietf-idr-bgp-bestpath-selection-criteria-08 (work in draft-ietf-idr-bgp-bestpath-selection-criteria-09 (work in
progress), October 2017. progress), June 2018.
[RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis",
RFC 4272, DOI 10.17487/RFC4272, January 2006, RFC 4272, DOI 10.17487/RFC4272, January 2006,
<https://www.rfc-editor.org/info/rfc4272>. <https://www.rfc-editor.org/info/rfc4272>.
[RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., and S. [RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., and S.
Pallagatti, "Seamless Bidirectional Forwarding Detection Pallagatti, "Seamless Bidirectional Forwarding Detection
(S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016, (S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016,
<https://www.rfc-editor.org/info/rfc7880>. <https://www.rfc-editor.org/info/rfc7880>.
Appendix A. Summary of Document Changes Appendix A. Summary of Document Changes
idr-06: Refresh -05.
idr-04 to idr-05: Added reference to "BGP Bestpath Selection idr-04 to idr-05: Added reference to "BGP Bestpath Selection
Criteria Enhancement" draft. Rename "next hop" field of NLRI to Criteria Enhancement" draft. Rename "next hop" field of NLRI to
"Indirect Peer's Address". Add suggestion about AS_PATH length "Indirect Peer's Address". Add suggestion about AS_PATH length
checks. checks.
idr-03 to idr-04: Note other forms of connectivity checks. idr-03 to idr-04: Note other forms of connectivity checks.
idr-02 to idr-03: Substantial rewrite. Introduce NLRI format that idr-02 to idr-03: Substantial rewrite. Introduce NLRI format that
embeds state. embeds state.
idr-01 to idr-02: Move from BGP-LS to NH-Reach SAFI. Lots of idr-01 to idr-02: Move from BGP-LS to NH-Reach SAFI. Lots of
editorial changes. editorial changes.
idr-00 to idr-01: Add BGP Capability. Move from NH-Cost to BGP-LS. idr-00 to idr-01: Add BGP Capability. Move from NH-Cost to BGP-LS.
 End of changes. 13 change blocks. 
18 lines changed or deleted 19 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/