draft-ietf-bfd-vxlan-05.txt   draft-ietf-bfd-vxlan-06.txt 
BFD S. Pallagatti, Ed. BFD S. Pallagatti, Ed.
Internet-Draft Rtbrick Internet-Draft Rtbrick
Intended status: Standards Track S. Paragiri Intended status: Standards Track S. Paragiri
Expires: June 22, 2019 Juniper Networks Expires: June 29, 2019 Juniper Networks
V. Govindan V. Govindan
M. Mudigonda M. Mudigonda
Cisco Cisco
G. Mirsky G. Mirsky
ZTE Corp. ZTE Corp.
December 19, 2018 December 26, 2018
BFD for VXLAN BFD for VXLAN
draft-ietf-bfd-vxlan-05 draft-ietf-bfd-vxlan-06
Abstract Abstract
This document describes the use of the Bidirectional Forwarding This document describes the use of the Bidirectional Forwarding
Detection (BFD) protocol in Virtual eXtensible Local Area Network Detection (BFD) protocol in Virtual eXtensible Local Area Network
(VXLAN) overlay networks. (VXLAN) overlay networks.
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
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 June 22, 2019. This Internet-Draft will expire on June 29, 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 (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 9, line 29 skipping to change at page 9, line 29
number of VNIs in common. When the single BFD session is used to number of VNIs in common. When the single BFD session is used to
monitor reachability of the remote VTEP, an implementation SHOULD use monitor reachability of the remote VTEP, an implementation SHOULD use
a VNI of 0. a VNI of 0.
8. Echo BFD 8. Echo BFD
Support for echo BFD is outside the scope of this document. Support for echo BFD is outside the scope of this document.
9. IANA Considerations 9. IANA Considerations
IANA has assigned TBA as a dedicated MAC address from the IANA 8-bit IANA has assigned TBA as a dedicated MAC address from the IANA 48-bit
unicast MAC address registry to be used as the Destination MAC unicast MAC address registry to be used as the Destination MAC
address of the inner Ethernet of VXLAN when carrying BFD control address of the inner Ethernet of VXLAN when carrying BFD control
packets. packets.
10. Security Considerations 10. Security Considerations
The document requires setting the inner IP TTL to 1 which could be The document requires setting the inner IP TTL to 1 which could be
used as a DDoS attack vector. Thus the implementation MUST have used as a DDoS attack vector. Thus the implementation MUST have
throttling in place to control the rate of BFD control packets sent throttling in place to control the rate of BFD control packets sent
to the control plane. Throttling MAY be relaxed for BFD packets to the control plane. Throttling MAY be relaxed for BFD packets
skipping to change at page 10, line 13 skipping to change at page 10, line 13
referred to in the list of normative references. referred to in the list of normative references.
11. Contributors 11. Contributors
Reshad Rahman Reshad Rahman
rrahman@cisco.com rrahman@cisco.com
Cisco Cisco
12. Acknowledgments 12. Acknowledgments
Authors would like to thank Jeff Hass of Juniper Networks for his Authors would like to thank Jeff Haas of Juniper Networks for his
reviews and feedback on this material. reviews and feedback on this material.
Authors would also like to thank Nobo Akiya, Marc Binderberger, Authors would also like to thank Nobo Akiya, Marc Binderberger,
Shahram Davari, Donald E. Eastlake 3rd, and Anoop Ghanwani for the Shahram Davari, Donald E. Eastlake 3rd, and Anoop Ghanwani for the
extensive reviews and the most detailed and helpful comments. extensive reviews and the most detailed and helpful comments.
13. References 13. References
13.1. Normative References 13.1. Normative References
 End of changes. 6 change blocks. 
6 lines changed or deleted 6 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/