OAM Header for use in Overlay Networks

New protocols that support overlay networks like VxLAN-GPE , GUE , Geneve , BIER , and NSH support multi-protocol payload, e.g. Ethernet, IPv4/IPv6, and recognize Operations, Administration, and Maintenance (OAM) as one of distinct types. That ensures that Overlay OAM packets are sharing fate with Overlay data packet traversing the underlay. This document introduces Overlay OAM Header to be used in overlay networks to de-multiplex Overlay OAM protocols.

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 .

V - two bits long field indicates the current version of the Overlay OAM Header. The current value is 0. Msg Type - six bits long field identifies OAM protocol, e.g. Ping or BFD. Flags - eight bits long field carries bit flags that define optional capability and thus processing of the OOAM control packet, e.g. optional timestamping. Length - two octets long field that is length of the OOAM control packet in octets. The OOAM header may be followed by the Timestamp control block and then by OOAM Control Packet identified by the Msg Type field.

where: QTF - Querier timestamp format RTF - Responder timestamp format Timestamp 1-4 - 64-bit timestamp values

IANA is requested to create new registry called "Overlay OAM Protocol Types". All code points in the range 1 through 32767 in this registry shall be allocated according to the "IETF Review" procedure as specified in . Remaining code points are allocated according to the table : Value Description Reference 0 Reserved 1 - 32767 Reserved IETF Consensus 32768 - 65530 Reserved First Come First Served 65531 - 65534 Reserved Private Use 65535 Reserved

TBD