On-demand Continuity Check (CC) and Connectivity Verification(CV) for Overlay Networks

Operations, Administration, and Maintenance (OAM) toolset provides methods for fault management and performance monitoring in each layer of the network, in order to improve their ability to support services with guaranteed and strict Service Level Agreements (SLAs) while reducing operational costs.

Term "Overlay OAM" used in this document interchangeably with longer version "set of OAM protocols, methods and tools for Overlay networks". CC Continuity Check CV Connectivity Verification FM Fault Management G-ACh Generic Associated Channel Geneve Generic Network Virtualization Encapsulation GUE Generic UDP Encapsulation MPLS Multiprotocol Label Switching NVO3 Network Virtualization Overlays OAM Operations, Administration, and Maintenance SFC Service Function Chaining SFP Service Function Path VxLAN Virtual eXtensible Local Area Network VxLAN-GPE Generic Protocol Extension for VxLAN

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

The format of the control packet to support ping and traceroute functionality in overlay networks is similar to the format of MPLS LSP Ping .

The interpretation of the fields is The Version reflects the current version. The version number is to be incremented whenever a change is made that affects the ability of an implementation to correctly parse or process control packet. The Global Flags is a bit vector field The Message Type filed reflects the type of the packet. Value TBA2 identifies echo request and TBA3 - echo reply The Reply Mode defines the type of the return path requested by the sender of the Echo Request. Return Codes and Subcodes can be used to inform the sender about result of processing its request. The Sender's Handle is filled in by the sender, and returned unchanged by the receiver in the echo reply. The Sequence Number is assigned by the sender and can be (for example) used to detect missed replies. TLVs (Type-Length-Value tuples) have the two octets long Type field, two octets long Length field that is length of the Value field in octets.

The Reply Mode field directs whether and how the echo reply message should be sent. The sender of the echo request MAY use TLVs to request that corresponding echo reply be sent using the specified path. Value TBA3 is referred as "Do not reply" mode and suppresses transmission of echo reply packet. Default value (TBA4) for the Reply mode field requests the responder to send the echo reply packet out-of-band as IPv4 or IPv6 UDP packet. [Selection of destination and source IP addresses and UDP port numbers to be provided in the next update.]

IANA is requested to assign new type from the Overlay OAM Protocol Types registry as follows: Value Description Reference TBA1 Overlay Ping This document

IANA is requested to create new Overlay Ping Parameters registry.

IANA is requested to create in the Overlay Ping Parameters registry the new sub-registry Message Types. All code points in the range 1 through 191 in this registry shall be allocated according to the "IETF Review" procedure as specified in and assign values as follows: Value Description Reference 0 Reserved TBA1 Overlay Echo Request This document TBA2 Overlay Echo Reply This document 192-251 Unassigned First Come First Served 252-254 Reserved Private Use 255 Reserved

IANA is requested to create in the Overlay Ping Parameters registry the new sub-registry Reply Modes All code points in the range 1 through 191 in this registry shall be allocated according to the "IETF Review" procedure as specified in and assign values as follows: Value Description Reference 0 Reserved TBA3 Do not reply This document TBA4 Reply via an IPv4/IPv6 UDP packet This document 192-251 Unassigned First Come First Served 252-254 Reserved Private Use 255 Reserved

TBD