draft-ietf-bfd-vxlan-13.txt   draft-ietf-bfd-vxlan-14.txt 
BFD S. Pallagatti, Ed. BFD S. Pallagatti, Ed.
Internet-Draft VMware Internet-Draft VMware
Intended status: Informational S. Paragiri Intended status: Informational S. Paragiri
Expires: January 7, 2021 Individual Contributor Expires: January 29, 2021 Individual Contributor
V. Govindan V. Govindan
M. Mudigonda M. Mudigonda
Cisco Cisco
G. Mirsky G. Mirsky
ZTE Corp. ZTE Corp.
July 6, 2020 July 28, 2020
BFD for VXLAN BFD for VXLAN
draft-ietf-bfd-vxlan-13 draft-ietf-bfd-vxlan-14
Abstract Abstract
This document describes the use of the Bidirectional Forwarding This document describes the use of the Bidirectional Forwarding
Detection (BFD) protocol in point-to-point Virtual eXtensible Local Detection (BFD) protocol in point-to-point Virtual eXtensible Local
Area Network (VXLAN) tunnels used to form an overlay network. Area Network (VXLAN) tunnels used to form an overlay network.
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 January 7, 2021. This Internet-Draft will expire on January 29, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 21 skipping to change at page 2, line 21
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in this Document . . . . . . . . . . . . . . 3 2. Conventions Used in this Document . . . . . . . . . . . . . . 3
2.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Use of the Management VNI . . . . . . . . . . . . . . . . . . 5 4. Use of the Management VNI . . . . . . . . . . . . . . . . . . 5
5. BFD Packet Transmission over VXLAN Tunnel . . . . . . . . . . 6 5. BFD Packet Transmission over VXLAN Tunnel . . . . . . . . . . 6
6. Reception of BFD Packet from VXLAN Tunnel . . . . . . . . . . 8 6. Reception of BFD Packet from VXLAN Tunnel . . . . . . . . . . 8
7. Echo BFD . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. Echo BFD . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 8 9. Security Considerations . . . . . . . . . . . . . . . . . . . 9
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
12.1. Normative References . . . . . . . . . . . . . . . . . . 9 12.1. Normative References . . . . . . . . . . . . . . . . . . 10
12.2. Informational References . . . . . . . . . . . . . . . . 10 12.2. Informational References . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
"Virtual eXtensible Local Area Network" (VXLAN) [RFC7348] provides an "Virtual eXtensible Local Area Network" (VXLAN) [RFC7348] provides an
encapsulation scheme that allows building an overlay network by 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.
One use of VXLAN is in data centers interconnecting virtual machines One use of VXLAN is in data centers interconnecting virtual machines
(VMs) of a tenant. VXLAN addresses requirements of the Layer 2 and (VMs) of a tenant. VXLAN addresses requirements of the Layer 2 and
skipping to change at page 5, line 42 skipping to change at page 5, line 42
Figure 1: Reference VXLAN Domain Figure 1: Reference VXLAN Domain
At the same time, a service layer BFD session may be used between the At the same time, a service layer BFD session may be used between the
tenants of VTEPs IP1 and IP2 to provide end-to-end fault management tenants of VTEPs IP1 and IP2 to provide end-to-end fault management
(this use case is outside the scope of this document). In such a (this use case is outside the scope of this document). In such a
case, for VTEPs BFD Control packets of that session are case, for VTEPs BFD Control packets of that session are
indistinguishable from data packets. indistinguishable from data packets.
For BFD Control packets encapsulated in VXLAN (Figure 2), the inner For BFD Control packets encapsulated in VXLAN (Figure 2), the inner
destination IP address SHOULD be set to one of the loopback addresses destination IP address SHOULD be set to one of the loopback addresses
from 127/8 range for IPv4 or to one of IPv4-mapped IPv4 loopback from 127/8 range for IPv4 or to one of IPv4-mapped IPv6 loopback
addresses from ::ffff:127.0.0.0/104 range for IPv6. addresses from ::ffff:127.0.0.0/104 range for IPv6.
4. Use of the Management VNI 4. Use of the Management VNI
In most cases, a single BFD session is sufficient for the given VTEP In most cases, a single BFD session is sufficient for the given VTEP
to monitor the reachability of a remote VTEP, regardless of the to monitor the reachability of a remote VTEP, regardless of the
number of VNIs. When the single BFD session is used to monitor the number of VNIs. When the single BFD session is used to monitor the
reachability of the remote VTEP, an implementation SHOULD choose any reachability of the remote VTEP, an implementation SHOULD choose any
of the VNIs. An implementation that supports this specification MUST of the VNIs. An implementation that supports this specification MUST
support the use of the Management VNI as control and management support the use of the Management VNI as control and management
skipping to change at page 8, line 7 skipping to change at page 8, line 7
VXLAN packet. The choice of Destination MAC and Destination IP VXLAN packet. The choice of Destination MAC and Destination IP
addresses for the inner Ethernet frame MUST ensure that the BFD addresses for the inner Ethernet frame MUST ensure that the BFD
Control packet is not forwarded to a tenant but is processed locally Control packet is not forwarded to a tenant but is processed locally
at the remote VTEP. The inner Ethernet frame carrying the BFD at the remote VTEP. The inner Ethernet frame carrying the BFD
Control packet- has the following format: Control packet- has the following format:
Ethernet Header: Ethernet Header:
Destination MAC: A Management VNI, which does not have any Destination MAC: A Management VNI, which does not have any
tenants, will have no dedicated MAC address for decapsulated tenants, will have no dedicated MAC address for decapsulated
traffic. The value X:X:X:X:X SHOULD be used in this field. traffic. The value [TBD1] SHOULD be used in this field.
Source MAC: MAC address associated with the originating VTEP. Source MAC: MAC address associated with the originating VTEP.
IP header: IP header:
Destination IP: IP address MUST NOT be of one of tenant's IP Destination IP: IP address MUST NOT be of one of tenant's IP
addresses. The IP address SHOULD be selected from the range addresses. The IP address SHOULD be selected from the range
127/8 for IPv4, for IPv6 - from the range ::ffff:127.0.0.0/104. 127/8 for IPv4, for IPv6 - from the range ::ffff:127.0.0.0/104.
Alternatively, the destination IP address MAY be set to VTEP's Alternatively, the destination IP address MAY be set to VTEP's
IP address. IP address.
skipping to change at page 8, line 44 skipping to change at page 8, line 44
The received packet's inner IP payload is then validated according to The received packet's inner IP payload is then validated according to
Sections 4 and 5 in [RFC5881]. Sections 4 and 5 in [RFC5881].
7. Echo BFD 7. Echo BFD
Support for echo BFD is outside the scope of this document. Support for echo BFD is outside the scope of this document.
8. IANA Considerations 8. IANA Considerations
This specification has no IANA action requested. This section may be IANA is requested to assign a single MAC address to the value TBD1
deleted before the publication. from the "IANA Unicast 48-bit MAC Address" registry from the
"Unassigned (small allocations)" block. The Usage field will be "BFD
for VXLAN" with a Reference field of this document.
9. Security Considerations 9. Security Considerations
Security issues discussed in [RFC5880], [RFC5881], and [RFC7348] Security issues discussed in [RFC5880], [RFC5881], and [RFC7348]
apply to this document. apply to this document.
This document recommends using an address from the Internal host This document recommends using an address from the Internal host
loopback addresses 127/8 range for IPv4 or an IP4-mapped IPv4 loopback addresses 127/8 range for IPv4 or an IP4-mapped IPv6
loopback address from ::ffff:127.0.0.0/104 range for IPv6 as the loopback address from ::ffff:127.0.0.0/104 range for IPv6 as the
destination IP address in the inner IP header. Using such an address destination IP address in the inner IP header. Using such an address
prevents the forwarding of the encapsulated BFD control message by a prevents the forwarding of the encapsulated BFD control message by a
transient node in case the VXLAN tunnel is broken as according to transient node in case the VXLAN tunnel is broken as according to
[RFC1812]: [RFC1812].
A router SHOULD NOT forward, except over a loopback interface, any A router SHOULD NOT forward, except over a loopback interface, any
packet that has a destination address on network 127. A router packet that has a destination address on network 127. A router
MAY have a switch that allows the network manager to disable these MAY have a switch that allows the network manager to disable these
checks. If such a switch is provided, it MUST default to checks. If such a switch is provided, it MUST default to
performing the checks. performing the checks.
The use of IPv4-mapped IPv6 addresses has the same property as using
the IPv4 network 127/8, moreover, the IPv4-mapped IPv6 addresses
prefix is not advertised in any routing protocol.
If the implementation supports establishing multiple BFD sessions If the implementation supports establishing multiple BFD sessions
between the same pair of VTEPs, there SHOULD be a mechanism to between the same pair of VTEPs, there SHOULD be a mechanism to
control the maximum number of such sessions that can be active at the control the maximum number of such sessions that can be active at the
same time. same time.
10. Contributors 10. Contributors
Reshad Rahman Reshad Rahman
rrahman@cisco.com rrahman@cisco.com
Cisco Cisco
 End of changes. 13 change blocks. 
14 lines changed or deleted 20 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/