draft-ietf-bfd-vxlan-15.txt   draft-ietf-bfd-vxlan-16.txt 
BFD S. Pallagatti, Ed. BFD S. Pallagatti, Ed.
Internet-Draft VMware Internet-Draft VMware
Intended status: Informational G. Mirsky, Ed. Intended status: Informational G. Mirsky, Ed.
Expires: April 4, 2021 ZTE Corp. Expires: April 29, 2021 ZTE Corp.
S. Paragiri S. Paragiri
Individual Contributor Individual Contributor
V. Govindan V. Govindan
M. Mudigonda M. Mudigonda
Cisco Cisco
October 1, 2020 October 26, 2020
BFD for VXLAN BFD for VXLAN
draft-ietf-bfd-vxlan-15 draft-ietf-bfd-vxlan-16
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 April 4, 2021. This Internet-Draft will expire on April 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 5, line 37 skipping to change at page 5, line 37
| | | | | | | | | | | |
| +---------+ +---------+ | | +---------+ +---------+ |
| Server 2 | | Server 2 |
+--------------------------+ +--------------------------+
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, the 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 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
skipping to change at page 8, line 11 skipping to change at page 8, line 11
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.
Ethertype: is set to 0x0800 if the inner IP header is IPv4, and
is set to 0x86DD if the inner IP header is IPv6.
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.
Source IP: IP address of the originating VTEP. Source IP: IP address of the originating VTEP.
 End of changes. 6 change blocks. 
5 lines changed or deleted 8 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/