draft-ietf-bfd-vxlan-14.txt   draft-ietf-bfd-vxlan-15.txt 
BFD S. Pallagatti, Ed. BFD S. Pallagatti, Ed.
Internet-Draft VMware Internet-Draft VMware
Intended status: Informational S. Paragiri Intended status: Informational G. Mirsky, Ed.
Expires: January 29, 2021 Individual Contributor Expires: April 4, 2021 ZTE Corp.
S. Paragiri
Individual Contributor
V. Govindan V. Govindan
M. Mudigonda M. Mudigonda
Cisco Cisco
G. Mirsky October 1, 2020
ZTE Corp.
July 28, 2020
BFD for VXLAN BFD for VXLAN
draft-ietf-bfd-vxlan-14 draft-ietf-bfd-vxlan-15
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 29, 2021. This Internet-Draft will expire on April 4, 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 3, line 16 skipping to change at page 3, line 16
exchanged among VMs. exchanged among VMs.
The ability to monitor path continuity, i.e., perform proactive The ability to monitor path continuity, i.e., perform proactive
continuity check (CC) for point-to-point (p2p) VXLAN tunnels, is continuity check (CC) for point-to-point (p2p) VXLAN tunnels, is
important. The asynchronous mode of BFD, as defined in [RFC5880], is important. The asynchronous mode of BFD, as defined in [RFC5880], is
used to monitor a p2p VXLAN tunnel. used to monitor a p2p VXLAN tunnel.
In the case where a Multicast Service Node (MSN) (as described in In the case where a Multicast Service Node (MSN) (as described in
Section 3.3 of [RFC8293]) participates in VXLAN, the mechanisms Section 3.3 of [RFC8293]) participates in VXLAN, the mechanisms
described in this document apply and can, therefore, be used to test described in this document apply and can, therefore, be used to test
the connectivity from the source NVE to the MSN. the continuity of the path between the source NVE and the MSN.
This document describes the use of Bidirectional Forwarding Detection This document describes the use of Bidirectional Forwarding Detection
(BFD) protocol to enable monitoring continuity of the path between (BFD) protocol to enable monitoring continuity of the path between
VXLAN VTEPs that are performing as Network Virtualization Endpoints, VXLAN VTEPs that are performing as Network Virtualization Endpoints,
and/or availability of a replicator MSN using a Management VNI and/or between the source NVE and a replicator MSN using a Management
(Section 4). All other uses of the specification to test toward VNI (Section 4). All other uses of the specification to test toward
other VXLAN endpoints are out of the scope. other VXLAN endpoints are out of the scope.
2. Conventions Used in this Document 2. Conventions Used in this Document
2.1. Acronyms 2.1. Acronyms
BFD Bidirectional Forwarding Detection BFD Bidirectional Forwarding Detection
CC Continuity Check CC Continuity Check
skipping to change at page 5, line 49 skipping to change at page 5, line 49
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 IPv6 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. BFD control messages MUST be sent using the
reachability of the remote VTEP, an implementation SHOULD choose any Management VNI which acts as the as control and management channel
of the VNIs. An implementation that supports this specification MUST between VTEPs. An implementation MAY support operating BFD on
support the use of the Management VNI as control and management another (non-Management) VNI although the implications of this are
channel between VTEPs. The selection of the VNI number of the outside the scope of this document. The selection of the VNI number
Management VNI MUST be controlled through a management plane. An of the Management VNI MUST be controlled through a management plane.
implementation MAY use VNI number 1 as the default value for the An implementation MAY use VNI number 1 as the default value for the
Management VNI. All VXLAN packets received on the Management VNI Management VNI. All VXLAN packets received on the Management VNI
MUST be processed locally and MUST NOT be forwarded to a tenant. MUST be processed locally and MUST NOT be forwarded to a tenant.
5. BFD Packet Transmission over VXLAN Tunnel 5. BFD Packet Transmission over VXLAN Tunnel
BFD packets MUST be encapsulated and sent to a remote VTEP as BFD packets MUST be encapsulated and sent to a remote VTEP as
explained in this section. Implementations SHOULD ensure that the explained in this section. Implementations SHOULD ensure that the
BFD packets follow the same forwarding path as VXLAN data packets BFD packets follow the same forwarding path as VXLAN data packets
within the sender system. within the sender system.
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 [TBD1] 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 11, line 12 skipping to change at page 11, line 12
DOI 10.17487/RFC8365, March 2018, DOI 10.17487/RFC8365, March 2018,
<https://www.rfc-editor.org/info/rfc8365>. <https://www.rfc-editor.org/info/rfc8365>.
Authors' Addresses Authors' Addresses
Santosh Pallagatti (editor) Santosh Pallagatti (editor)
VMware VMware
Email: santosh.pallagatti@gmail.com Email: santosh.pallagatti@gmail.com
Greg Mirsky (editor)
ZTE Corp.
Email: gregimirsky@gmail.com
Sudarsan Paragiri Sudarsan Paragiri
Individual Contributor Individual Contributor
Email: sudarsan.225@gmail.com Email: sudarsan.225@gmail.com
Vengada Prasad Govindan Vengada Prasad Govindan
Cisco Cisco
Email: venggovi@cisco.com Email: venggovi@cisco.com
Mallik Mudigonda Mallik Mudigonda
Cisco Cisco
Email: mmudigon@cisco.com Email: mmudigon@cisco.com
Greg Mirsky
ZTE Corp.
Email: gregimirsky@gmail.com
 End of changes. 10 change blocks. 
18 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/