draft-ietf-nvo3-bfd-geneve-03.txt   draft-ietf-nvo3-bfd-geneve-04.txt 
NVO3 Working Group X. Min NVO3 Working Group X. Min
Internet-Draft G. Mirsky Internet-Draft G. Mirsky
Intended status: Standards Track ZTE Corp. Intended status: Standards Track ZTE Corp.
Expires: November 14, 2021 S. Pallagatti Expires: 3 February 2022 S. Pallagatti
VMware VMware
J. Tantsura J. Tantsura
Juniper Networks Microsoft
May 13, 2021 S. Aldrin
Google
2 August 2021
BFD for Geneve BFD for Geneve
draft-ietf-nvo3-bfd-geneve-03 draft-ietf-nvo3-bfd-geneve-04
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 Generic Network Detection (BFD) protocol in point-to-point Generic Network
Virtualization Encapsulation (Geneve) tunnels used to make up an Virtualization Encapsulation (Geneve) tunnels used to make up an
overlay network. overlay network.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 39
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 November 14, 2021. This Internet-Draft will expire on 3 February 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as 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. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. BFD Packet Transmission over Geneve Tunnel . . . . . . . . . 3 3. BFD Packet Transmission over Geneve Tunnel . . . . . . . . . 3
3.1. BFD Encapsulation With Inner Ethernet/IP/UDP Header . . . 3 3.1. BFD Encapsulation With Inner Ethernet/IP/UDP Header . . . 4
3.2. BFD Encapsulation With Inner IP/UDP Header . . . . . . . 5 3.2. BFD Encapsulation With Inner IP/UDP Header . . . . . . . 6
4. Reception of BFD packet from Geneve Tunnel . . . . . . . . . 7 4. Reception of BFD packet from Geneve Tunnel . . . . . . . . . 8
4.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 8 4.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 9 8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
"Generic Network Virtualization Encapsulation" (Geneve) [RFC8926] "Generic Network Virtualization Encapsulation" (Geneve) [RFC8926]
provides an encapsulation scheme that allows building an overlay provides an encapsulation scheme that allows building an overlay
network by decoupling the address space of the attached virtual hosts network by decoupling the address space of the attached virtual hosts
from that of the network. from that of the network.
This document describes the use of Bidirectional Forwarding Detection This document describes the use of Bidirectional Forwarding Detection
(BFD) protocol [RFC5880] to enable monitoring continuity of the path (BFD) protocol [RFC5880] to enable monitoring continuity of the path
skipping to change at page 4, line 51 skipping to change at page 5, line 44
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ BFD Control Packet ~ ~ BFD Control Packet ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Outer Ethernet FCS | | Outer Ethernet FCS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Geneve Encapsulation of BFD Control Packet With the Inner Figure 1: Geneve Encapsulation of BFD Control Packet With the Inner
Ethernet/IP/UDP Header Ethernet/IP/UDP Header
The BFD packet MUST be carried inside the inner Ethernet frame of the The BFD packet MUST be carried inside the inner Ethernet frame of the
Geneve packet. The inner Ethernet frame carrying the BFD Control Geneve packet. The inner Ethernet frame carrying the BFD Control
packet has the following format: packet has the following format:
Ethernet Header: Ethernet Header:
Source MAC: MAC address of a VAP of the originating NVE. - Source MAC: MAC address of a VAP of the originating NVE.
Destination MAC: MAC address of a VAP of the terminating NVE. - Destination MAC: MAC address of a VAP of the terminating NVE.
IP Header: IP Header:
Source IP: IP address of a VAP of the originating NVE. If the - Source IP: IP address of a VAP of the originating NVE. If the
VAP of the originating NVE has no IP address, then the IP VAP of the originating NVE has no IP address, then the IP
address 0.0.0.0 for IPv4 or ::/128 for IPv6 MUST be used. address 0.0.0.0 for IPv4 or ::/128 for IPv6 MUST be used.
Destination IP: IP address of a VAP of the terminating NVE. If - Destination IP: IP address of a VAP of the terminating NVE. If
the VAP of the terminating NVE has no IP address, then the IP the VAP of the terminating NVE has no IP address, then the IP
address 127.0.0.1 for IPv4 or ::1/128 for IPv6 MUST be used. address 127.0.0.1 for IPv4 or ::1/128 for IPv6 MUST be used.
TTL or Hop Limit: MUST be set to 255 in accordance with - TTL or Hop Limit: MUST be set to 255 in accordance with
[RFC5881]. [RFC5881].
The fields of the UDP header and the BFD Control packet are The fields of the UDP header and the BFD Control packet are
encoded as specified in [RFC5881]. encoded as specified in [RFC5881].
When the BFD packets are encapsulated in Geneve in this way, the When the BFD packets are encapsulated in Geneve in this way, the
Geneve header defined in [RFC8926] follows the value set below. Geneve header defined in [RFC8926] follows the value set below.
Opt Len field SHOULD be set to 0, which indicates there isn't any Opt Len field SHOULD be set to 0, which indicates there isn't any
variable length option. variable length option.
skipping to change at page 6, line 46 skipping to change at page 7, line 39
~ Inner UDP Header ~ ~ Inner UDP Header ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ BFD Control Packet ~ ~ BFD Control Packet ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FCS | | FCS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Geneve Encapsulation of BFD Control Packet With the Inner Figure 2: Geneve Encapsulation of BFD Control Packet With the
IP/UDP Header Inner IP/UDP Header
The BFD packet MUST be carried inside the inner IP packet of the The BFD packet MUST be carried inside the inner IP packet of the
Geneve packet. The inner IP packet carrying the BFD Control packet Geneve packet. The inner IP packet carrying the BFD Control packet
has the following format: has the following format:
IP header: IP header:
Source IP: IP address of a VAP of the originating NVE. - Source IP: IP address of a VAP of the originating NVE.
Destination IP: IP address of a VAP of the terminating NVE. - Destination IP: IP address of a VAP of the terminating NVE.
TTL or Hop Limit: MUST be set to 255 in accordance with - TTL or Hop Limit: MUST be set to 255 in accordance with
[RFC5881]. [RFC5881].
The fields of the UDP header and the BFD Control packet are The fields of the UDP header and the BFD Control packet are
encoded as specified in [RFC5881]. encoded as specified in [RFC5881].
When the BFD packets are encapsulated in Geneve in this way, the When the BFD packets are encapsulated in Geneve in this way, the
Geneve header defined in [RFC8926] follows the value set below. Geneve header defined in [RFC8926] follows the value set below.
Opt Len field SHOULD be set to 0, which indicates there isn't any Opt Len field SHOULD be set to 0, which indicates there isn't any
variable length option. variable length option.
skipping to change at page 9, line 39 skipping to change at page 10, line 39
[RFC8926] Gross, J., Ed., Ganga, I., Ed., and T. Sridhar, Ed., [RFC8926] Gross, J., Ed., Ganga, I., Ed., and T. Sridhar, Ed.,
"Geneve: Generic Network Virtualization Encapsulation", "Geneve: Generic Network Virtualization Encapsulation",
RFC 8926, DOI 10.17487/RFC8926, November 2020, RFC 8926, DOI 10.17487/RFC8926, November 2020,
<https://www.rfc-editor.org/info/rfc8926>. <https://www.rfc-editor.org/info/rfc8926>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-nvo3-geneve-oam] [I-D.ietf-nvo3-geneve-oam]
Mirsky, G., Boutros, S., Black, D., and S. Pallagatti, Mirsky, G., Boutros, S., Black, D., and S. Pallagatti,
"OAM for use in GENEVE", draft-ietf-nvo3-geneve-oam-01 "OAM for use in GENEVE", Work in Progress, Internet-Draft,
(work in progress), November 2020. draft-ietf-nvo3-geneve-oam-02, 17 May 2021,
<https://www.ietf.org/archive/id/draft-ietf-nvo3-geneve-
oam-02.txt>.
[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,
L., Sridhar, T., Bursell, M., and C. Wright, "Virtual L., Sridhar, T., Bursell, M., and C. Wright, "Virtual
eXtensible Local Area Network (VXLAN): A Framework for eXtensible Local Area Network (VXLAN): A Framework for
Overlaying Virtualized Layer 2 Networks over Layer 3 Overlaying Virtualized Layer 2 Networks over Layer 3
Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014,
<https://www.rfc-editor.org/info/rfc7348>. <https://www.rfc-editor.org/info/rfc7348>.
[RFC7365] Lasserre, M., Balus, F., Morin, T., Bitar, N., and Y. [RFC7365] Lasserre, M., Balus, F., Morin, T., Bitar, N., and Y.
Rekhter, "Framework for Data Center (DC) Network Rekhter, "Framework for Data Center (DC) Network
skipping to change at page 10, line 29 skipping to change at page 11, line 34
Xiao Min Xiao Min
ZTE Corp. ZTE Corp.
Nanjing Nanjing
China China
Phone: +86 25 88013062 Phone: +86 25 88013062
Email: xiao.min2@zte.com.cn Email: xiao.min2@zte.com.cn
Greg Mirsky Greg Mirsky
ZTE Corp. ZTE Corp.
USA United States of America
Email: gregory.mirsky@ztetx.com Email: gregory.mirsky@ztetx.com
Santosh Pallagatti Santosh Pallagatti
VMware VMware
India
Email: santosh.pallagatti@gmail.com Email: santosh.pallagatti@gmail.com
Jeff Tantsura Jeff Tantsura
Juniper Networks Microsoft
United States of America
Email: jefftant.ietf@gmail.com Email: jefftant.ietf@gmail.com
Sam Aldrin
Google
United States of America
Email: aldrin.ietf@gmail.com
 End of changes. 21 change blocks. 
39 lines changed or deleted 44 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/