draft-ietf-bfd-vxlan-04.txt   draft-ietf-bfd-vxlan-05.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: May 27, 2019 Juniper Networks Expires: June 22, 2019 Juniper Networks
V. Govindan V. Govindan
M. Mudigonda M. Mudigonda
Cisco Cisco
G. Mirsky G. Mirsky
ZTE Corp. ZTE Corp.
November 23, 2018 December 19, 2018
BFD for VXLAN BFD for VXLAN
draft-ietf-bfd-vxlan-04 draft-ietf-bfd-vxlan-05
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 May 27, 2019. This Internet-Draft will expire on June 22, 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 2, line 14 skipping to change at page 2, line 14
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
2. Conventions used in this document . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . 3
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. BFD Packet Transmission over VXLAN Tunnel . . . . . . . . . . 5 5. BFD Packet Transmission over VXLAN Tunnel . . . . . . . . . . 6
5.1. BFD Packet Encapsulation in VXLAN . . . . . . . . . . . . 6 5.1. BFD Packet Encapsulation in VXLAN . . . . . . . . . . . . 7
6. Reception of BFD packet from VXLAN Tunnel . . . . . . . . . . 7 6. Reception of BFD packet from VXLAN Tunnel . . . . . . . . . . 8
6.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 7 6.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 8
7. Use of reserved VNI . . . . . . . . . . . . . . . . . . . . . 8 7. Use of reserved VNI . . . . . . . . . . . . . . . . . . . . . 9
8. Echo BFD . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Echo BFD . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. Security Considerations . . . . . . . . . . . . . . . . . . . 8 10. Security Considerations . . . . . . . . . . . . . . . . . . . 9
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
13.1. Normative References . . . . . . . . . . . . . . . . . . 9 13.1. Normative References . . . . . . . . . . . . . . . . . . 10
13.2. Informational References . . . . . . . . . . . . . . . . 10 13.2. Informational References . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
"Virtual eXtensible Local Area Network" (VXLAN) [RFC7348]. provides "Virtual eXtensible Local Area Network" (VXLAN) [RFC7348]. provides
an encapsulation scheme that allows building an overlay network by an encapsulation scheme that allows building an overlay network by
decoupling the address space of the attached virtual hosts from that decoupling the address space of the attached virtual hosts from that
of the network. of the network.
VXLAN is typically deployed in data centers interconnecting One use of VXLAN is in data centers interconnecting VMs of a tenant.
virtualized hosts of a tenant. VXLAN addresses requirements of the VXLAN addresses requirements of the Layer 2 and Layer 3 data center
Layer 2 and Layer 3 data center network infrastructure in the network infrastructure in the presence of VMs in a multi-tenant
presence of VMs in a multi-tenant environment, discussed in section 3 environment, discussed in section 3 [RFC7348], by providing Layer 2
[RFC7348], by providing Layer 2 overlay scheme on a Layer 3 network. overlay scheme on a Layer 3 network. Another use is as an
encapsulation for Ethernet VPN [RFC8365].
This document is written assuming the use of VXLAN for virtualized
hosts and refers to VMs and VTEPs in hypervisors. However, the
concepts are equally applicable to non-virtualized hosts attached to
VTEPs in switches.
In the absence of a router in the overlay, a VM can communicate with In the absence of a router in the overlay, a VM can communicate with
another VM only if they are on the same VXLAN segment. VMs are another VM only if they are on the same VXLAN segment. VMs are
unaware of VXLAN tunnels as a VXLAN tunnel is terminated on a VXLAN unaware of VXLAN tunnels as a VXLAN tunnel is terminated on a VXLAN
Tunnel End Point (VTEP) (hypervisor/TOR). VTEPs (hypervisor/TOR) are Tunnel End Point (VTEP) (hypervisor/TOR). VTEPs (hypervisor/TOR) are
responsible for encapsulating and decapsulating frames exchanged responsible for encapsulating and decapsulating frames exchanged
among VMs. among VMs.
Ability to monitor path continuity, i.e., perform proactive Ability to monitor path continuity, i.e., perform proactive
continuity check (CC) for these tunnels, is important. The continuity check (CC) for these tunnels, is important. The
skipping to change at page 9, line 26 skipping to change at page 10, line 26
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
[I-D.ietf-bfd-multipoint] [I-D.ietf-bfd-multipoint]
Katz, D., Ward, D., Networks, J., and G. Mirsky, "BFD for Katz, D., Ward, D., Networks, J., and G. Mirsky, "BFD for
Multipoint Networks", draft-ietf-bfd-multipoint-18 (work Multipoint Networks", draft-ietf-bfd-multipoint-19 (work
in progress), June 2018. in progress), December 2018.
[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>.
[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>.
skipping to change at page 10, line 17 skipping to change at page 11, line 17
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
13.2. Informational References 13.2. Informational References
[RFC8293] Ghanwani, A., Dunbar, L., McBride, M., Bannai, V., and R. [RFC8293] Ghanwani, A., Dunbar, L., McBride, M., Bannai, V., and R.
Krishnan, "A Framework for Multicast in Network Krishnan, "A Framework for Multicast in Network
Virtualization over Layer 3", RFC 8293, Virtualization over Layer 3", RFC 8293,
DOI 10.17487/RFC8293, January 2018, DOI 10.17487/RFC8293, January 2018,
<https://www.rfc-editor.org/info/rfc8293>. <https://www.rfc-editor.org/info/rfc8293>.
[RFC8365] Sajassi, A., Ed., Drake, J., Ed., Bitar, N., Shekhar, R.,
Uttaro, J., and W. Henderickx, "A Network Virtualization
Overlay Solution Using Ethernet VPN (EVPN)", RFC 8365,
DOI 10.17487/RFC8365, March 2018,
<https://www.rfc-editor.org/info/rfc8365>.
Authors' Addresses Authors' Addresses
Santosh Pallagatti (editor) Santosh Pallagatti (editor)
Rtbrick Rtbrick
Email: santosh.pallagatti@gmail.com Email: santosh.pallagatti@gmail.com
Sudarsan Paragiri Sudarsan Paragiri
Juniper Networks Juniper Networks
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
 End of changes. 9 change blocks. 
27 lines changed or deleted 39 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/