One document matched: draft-ooamdt-rtgwg-ooam-header-00.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"[
<!ENTITY RFC2119 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
<!ENTITY I-D.ietf-nvo3-geneve SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-nvo3-geneve-01.xml">
<!ENTITY I-D.ietf-nvo3-gue SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-nvo3-gue-04.xml">
<!ENTITY I-D.ietf-nvo3-vxlan-gpe SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-nvo3-vxlan-gpe-02.xml">
<!ENTITY I-D.ietf-bier-mpls-encapsulation SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-bier-mpls-encapsulation-04.xml">
<!ENTITY I-D.ietf-sfc-nsh SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-sfc-nsh-05.xml">
<!--
<!ENTITY RFC4379 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4379.xml">
<!ENTITY RFC6374 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6374.xml">
<!ENTITY RFC5880 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5880.xml">
<!ENTITY RFC5882 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5882.xml">
<!ENTITY RFC5883 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5883.xml">
<!ENTITY RFC5884 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5884.xml">
<!ENTITY RFC5885 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5885.xml">
<!ENTITY RFC7726 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7726.xml">
<!ENTITY RFC5357 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5357.xml">
<!ENTITY RFC6038 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6038.xml">
<!ENTITY RFC7750 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7750.xml">
<!ENTITY RFC6428 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6428.xml">
<!ENTITY RFC7276 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7276.xml">
<!ENTITY RFC7746 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7746.xml">
<!ENTITY RFC7594 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7594.xml">
<!ENTITY I-D.ietf-bfd-multipoint SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-bfd-multipoint-07.xml">
<!ENTITY I-D.ietf-bfd-multipoint-active-tail SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-bfd-multipoint-active-tail-01.xml">
<!ENTITY I-D.ietf-bfd-seamless-base SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-bfd-seamless-base-08.xml">
<!ENTITY I-D.ietf-bfd-seamless-ip SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-bfd-seamless-ip-03.xml">
<!ENTITY I-D.ietf-mpls-rfc6374-udp-return-path SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-mpls-rfc6374-udp-return-path-04.xml">
<!ENTITY I-D.kumarzheng-bier-ping SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-kumarzheng-bier-ping-02.xml">
<!ENTITY I-D.tempia-ippm-p3m SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-tempia-ippm-p3m-03.xml">
<!ENTITY I-D.mirsky-bier-pmmm-oam SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-mirsky-bier-pmmm-oam-01.xml">
<!ENTITY I-D.lapukhov-dataplane-probe SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-lapukhov-dataplane-probe-00.xml">
<!ENTITY I-D.ashwood-nvo3-oam-requirements SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ashwood-nvo3-oam-requirements-04.xml">
<!ENTITY I-D.nordmark-nvo3-transcending-traceroute SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-nordmark-nvo3-transcending-traceroute-02.xml">
<!ENTITY I-D.saum-nvo3-pmtud-over-vxlan SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-saum-nvo3-pmtud-over-vxlan-02.xml">
<!ENTITY I-D.singh-nvo3-vxlan-router-alert SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-singh-nvo3-vxlan-router-alert-02.xml">
<!ENTITY I-D.spallagatti-bfd-vxlan SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-spallagatti-bfd-vxlan-02.xml">
<!ENTITY I-D.ietf-rtgwg-dt-encap SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.draft-ietf-rtgwg-dt-encap-02.xml">
-->
]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" ipr="trust200902" docName="draft-ooamdt-rtgwg-ooam-header-00">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<front>
<title abbrev='OAM Header for use in Overlay Networks'>OAM Header for use in Overlay Networks</title>
<author initials='G.' surname="Mirsky" fullname='Greg Mirsky'>
<organization>Ericsson</organization>
<address>
<email>gregory.mirsky@ericsson.com</email>
</address>
</author>
<author initials='E.' surname="Nordmark" fullname='Erik Nordmark'>
<organization>Arista Networks</organization>
<address>
<email>nordmark@acm.org</email>
</address>
</author>
<author initials='C.' surname="Pignataro" fullname='Carlos Pignataro'>
<organization>Cisco Systems, Inc.</organization>
<address>
<email>cpignata@cisco.com</email>
</address>
</author>
<author initials='N.' surname="Kumar" fullname='Nagendra Kumar'>
<organization>Cisco Systems, Inc.</organization>
<address>
<email>naikumar@cisco.com</email>
</address>
</author>
<author initials='D.' surname="Kumar" fullname='Deepak Kumar'>
<organization>Cisco Systems, Inc.</organization>
<address>
<email>dekumar@cisco.com</email>
</address>
</author>
<author initials='M.' surname="Chen" fullname='Mach Chen'>
<organization>Huawei Technologies</organization>
<address>
<email>mach.chen@huawei.com</email>
</address>
</author>
<author initials='Y.' surname="Li" fullname='Yizhou Li'>
<organization>Huawei Technologies</organization>
<address>
<email>liyizhou@huawei.com</email>
</address>
</author>
<author initials='D.' surname="Mozes" fullname='David Mozes'>
<organization>Mellanox Technologies Ltd.</organization>
<address>
<email>davidm@mellanox.com</email>
</address>
</author>
<!--
<author initials='S' surname="Pallagatti" fullname='Santosh Pallagatti'>
<organization></organization>
<address>
<email>santosh.pallagatti@gmail.com</email>
</address>
</author>
-->
<author initials='I' surname="Bagdonas" fullname='Ignas Bagdonas'>
<organization></organization>
<address>
<email>ibagdona@gmail.com</email>
</address>
</author>
<date day="8" month="July" year="2016" />
<area>Routing</area>
<workgroup>Routing Area Working Group</workgroup>
<keyword>Internet-Draft</keyword>
<keyword>OAM</keyword>
<abstract>
<t>
</t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<t>
New protocols that support overlay networks like VxLAN-GPE <xref target=" I-D.ietf-nvo3-vxlan-gpe"/>,
GUE <xref target="I-D.ietf-nvo3-gue"/>, Geneve <xref target="I-D.ietf-nvo3-geneve"/>,
BIER <xref target="I-D.ietf-bier-mpls-encapsulation"/>, and NSH <xref target="I-D.ietf-sfc-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.
</t>
<t>
This document introduces Overlay OAM Header to be used in overlay networks to de-multiplex Overlay OAM
protocols.
</t>
<section title="Conventions used in this document">
<section title="Terminology">
<t>
Term "Overlay OAM" used in this document interchangeably with longer version
"set of OAM protocols, methods and tools for Overlay networks".
</t>
<t>CC Continuity Check </t>
<t>CV Connectivity Verification </t>
<t>FM Fault Management </t>
<t>G-ACh Generic Associated Channel </t>
<t>Geneve Generic Network Virtualization Encapsulation </t>
<t>GUE Generic UDP Encapsulation </t>
<t>MPLS Multiprotocol Label Switching </t>
<t>NVO3 Network Virtualization Overlays </t>
<t>
OAM Operations, Administration, and Maintenance</t>
<t>SFC Service Function Chaining</t>
<t>SFP Service Function Path</t>
<t>VxLAN Virtual eXtensible Local Area Network</t>
<t>VxLAN-GPE Generic Protocol Extension for VxLAN</t>
</section>
<section title="Requirements Language">
<t>
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
<xref target="RFC2119"></xref>.
</t>
</section>
</section>
</section>
<section anchor="ooam-header" title="Overlay OAM Header">
<t>
<figure align="left" anchor="ooam-header-pic"
title="Overlay OAM Header format">
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| V | Msg Type | Flags | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ OOAM Control Packet ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>
<list>
<t>V - two bits long field indicates the current version of the Overlay OAM Header. The current value is 0.
</t>
<t>Msg Type - six bits long field identifies OAM protocol, e.g. Ping or BFD.
</t>
<t>
Flags - eight bits long field carries bit flags that define optional capability and thus processing of the
OOAM control packet, e.g. optional timestamping.
</t>
<t>Length - two octets long field that is length of the OOAM control packet in octets.
</t>
</list>
</t>
<t>
The OOAM header may be followed by the Timestamp control block <xref target="ooam-timestamp-pic"/> and then by
OOAM Control Packet identified by the Msg Type field.
<figure align="left" anchor="ooam-timestamp-pic"
title="Timestamp block format">
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QTF | RTF | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp 1 |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp 4 |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>where:
<list>
<t>QTF - Querier timestamp format </t>
<t>RTF - Responder timestamp format </t>
<t>Timestamp 1-4 - 64-bit timestamp values </t>
</list>
</t>
</section>
<section anchor="iana-considerations" title="IANA Considerations">
<t>
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 <xref target="RFC5226"/>
.
Remaining code points are allocated according to the table <xref target="iana-ooam-header-type-tbl"/>:
</t>
<texttable anchor="iana-ooam-header-type-tbl" title="Overlay OAM Protocol type">
<ttcol align='left'>Value</ttcol>
<ttcol align='center'>Description</ttcol>
<ttcol align='left'>Reference</ttcol>
<c>0</c>
<c>Reserved</c>
<c></c>
<c>1 - 32767</c>
<c>Reserved</c>
<c>IETF Consensus</c>
<c>32768 - 65530</c>
<c>Reserved</c>
<c>First Come First Served</c>
<c>65531 - 65534</c>
<c>Reserved</c>
<c>Private Use</c>
<c>65535</c>
<c>Reserved</c>
<c></c>
</texttable>
</section>
<section anchor="security-considerations" title="Security Considerations">
<t>
TBD
</t>
</section>
<section anchor="ack" title="Acknowledgement">
<t>
TBD
</t>
</section>
</middle>
<back>
<references title="Normative References">
&RFC2119;
</references>
<references title="Informative References">
&RFC5226;
&I-D.ietf-nvo3-geneve;
&I-D.ietf-nvo3-gue;
&I-D.ietf-nvo3-vxlan-gpe;
&I-D.ietf-bier-mpls-encapsulation;
&I-D.ietf-sfc-nsh;
<!--
&RFC4379;
&RFC6374;
&RFC5880;
&RFC5884;
&RFC5882;
&RFC5883;
&RFC5885;
&RFC6428;
&RFC7726;
&RFC5357;
&RFC6038;
&RFC7750;
&RFC7276;
&RFC7746;
&RFC7594;
&I-D.ietf-bfd-multipoint;
&I-D.ietf-bfd-multipoint-active-tail;
&I-D.ietf-bfd-seamless-base;
&I-D.ietf-bfd-seamless-ip;
&I-D.kumarzheng-bier-ping;
&I-D.ietf-mpls-rfc6374-udp-return-path;
&I-D.mirsky-bier-pmmm-oam;
&I-D.tempia-ippm-p3m;
&I-D.lapukhov-dataplane-probe;
&I-D.ashwood-nvo3-oam-requirements;
&I-D.nordmark-nvo3-transcending-traceroute;
&I-D.saum-nvo3-pmtud-over-vxlan;
&I-D.singh-nvo3-vxlan-router-alert;
&I-D.spallagatti-bfd-vxlan;
-->
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 10:59:08 |