< draft-ietf-ippm-ioam-deployment-00.txt   draft-ietf-ippm-ioam-deployment-01.txt >
ippm F. Brockners, Ed. ippm F. Brockners, Ed.
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Best Current Practice S. Bhandari, Ed. Intended status: Best Current Practice S. Bhandari, Ed.
Expires: April 22, 2022 Thoughtspot Expires: October 13, 2022 Thoughtspot
D. Bernier D. Bernier
Bell Canada Bell Canada
T. Mizrahi, Ed. T. Mizrahi, Ed.
Huawei Huawei
October 19, 2021 April 11, 2022
In-situ OAM Deployment In-situ OAM Deployment
draft-ietf-ippm-ioam-deployment-00 draft-ietf-ippm-ioam-deployment-01
Abstract Abstract
In-situ Operations, Administration, and Maintenance (IOAM) collects In-situ Operations, Administration, and Maintenance (IOAM) collects
operational and telemetry information in the packet while the packet operational and telemetry information in the packet while the packet
traverses a path between two points in the network. This document traverses a path between two points in the network. This document
provides a framework for IOAM deployment and provides best current provides a framework for IOAM deployment and provides best current
practices. practices.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 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 April 22, 2022. This Internet-Draft will expire on October 13, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IOAM Deployment: Domains And Nodes . . . . . . . . . . . . . 4 3. IOAM Deployment: Domains And Nodes . . . . . . . . . . . . . 4
4. Types of IOAM . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Types of IOAM . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Per-hop Tracing IOAM . . . . . . . . . . . . . . . . . . 6 4.1. Per-hop Tracing IOAM . . . . . . . . . . . . . . . . . . 7
4.2. Proof of Transit IOAM . . . . . . . . . . . . . . . . . . 8 4.2. Proof of Transit IOAM . . . . . . . . . . . . . . . . . . 8
4.3. Edge to Edge IOAM . . . . . . . . . . . . . . . . . . . . 8 4.3. Edge to Edge IOAM . . . . . . . . . . . . . . . . . . . . 8
4.4. Direct Export IOAM . . . . . . . . . . . . . . . . . . . 8 4.4. Direct Export IOAM . . . . . . . . . . . . . . . . . . . 8
5. IOAM Encapsulations . . . . . . . . . . . . . . . . . . . . . 8 5. IOAM Encapsulations . . . . . . . . . . . . . . . . . . . . . 9
5.1. IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. NSH . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.2. NSH . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.3. GRE . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.3. BIER . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.4. Geneve . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.4. GRE . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.5. Segment Routing . . . . . . . . . . . . . . . . . . . . . 10 5.5. Geneve . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.6. Segment Routing for IPv6 . . . . . . . . . . . . . . . . 10 5.6. Segment Routing . . . . . . . . . . . . . . . . . . . . . 10
5.7. VXLAN-GPE . . . . . . . . . . . . . . . . . . . . . . . . 10 5.7. Segment Routing for IPv6 . . . . . . . . . . . . . . . . 10
5.8. VXLAN-GPE . . . . . . . . . . . . . . . . . . . . . . . . 10
6. IOAM Data Export . . . . . . . . . . . . . . . . . . . . . . 10 6. IOAM Data Export . . . . . . . . . . . . . . . . . . . . . . 10
7. IOAM Deployment Considerations . . . . . . . . . . . . . . . 11 7. IOAM Deployment Considerations . . . . . . . . . . . . . . . 12
7.1. IOAM Namespaces . . . . . . . . . . . . . . . . . . . . . 12 7.1. IOAM Namespaces . . . . . . . . . . . . . . . . . . . . . 12
7.2. IOAM Layering . . . . . . . . . . . . . . . . . . . . . . 13 7.2. IOAM Layering . . . . . . . . . . . . . . . . . . . . . . 14
7.3. IOAM Trace Option Types . . . . . . . . . . . . . . . . . 14 7.3. IOAM Trace Option Types . . . . . . . . . . . . . . . . . 15
7.4. Traffic-sets That IOAM Is Applied To . . . . . . . . . . 16 7.4. Traffic-sets That IOAM Is Applied To . . . . . . . . . . 17
7.5. IOAM Loopback Mode . . . . . . . . . . . . . . . . . . . 16 7.5. IOAM Loopback Mode . . . . . . . . . . . . . . . . . . . 17
7.6. IOAM Active Mode . . . . . . . . . . . . . . . . . . . . 16 7.6. IOAM Active Mode . . . . . . . . . . . . . . . . . . . . 17
7.7. Brown Field Deployments: IOAM Unaware Nodes . . . . . . . 17 7.7. Brown Field Deployments: IOAM Unaware Nodes . . . . . . . 18
8. IOAM Manageability . . . . . . . . . . . . . . . . . . . . . 17 8. IOAM Manageability . . . . . . . . . . . . . . . . . . . . . 18
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 10. Security Considerations . . . . . . . . . . . . . . . . . . . 19
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
12.1. Normative References . . . . . . . . . . . . . . . . . . 19 12.1. Normative References . . . . . . . . . . . . . . . . . . 20
12.2. Informative References . . . . . . . . . . . . . . . . . 20 12.2. Informative References . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
"In-situ" Operations, Administration, and Maintenance (IOAM) collects "In-situ" Operations, Administration, and Maintenance (IOAM) collects
OAM information within the packet while the packet traverses a OAM information within the packet while the packet traverses a
particular network domain. The term "in-situ" refers to the fact particular network domain. The term "in-situ" refers to the fact
that the OAM data is added to the data packets rather than is being that the OAM data is added to the data packets rather than is being
sent within packets specifically dedicated to OAM. IOAM is to sent within packets specifically dedicated to OAM. IOAM is to
complement mechanisms such as Ping, Traceroute, or other active complement mechanisms such as Ping, Traceroute, or other active
probing mechanisms. In terms of "active" or "passive" OAM, "in-situ" probing mechanisms. In terms of "active" or "passive" OAM, "in-situ"
skipping to change at page 3, line 30 skipping to change at page 3, line 31
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Abbreviations used in this document: Abbreviations used in this document:
BIER: Bit Index Explicit Replication
E2E: Edge to Edge E2E: Edge to Edge
Geneve: Generic Network Virtualization Encapsulation Geneve: Generic Network Virtualization Encapsulation
[I-D.ietf-nvo3-geneve] [I-D.ietf-nvo3-geneve]
GRE: Generic Routing Encapsulation GRE: Generic Routing Encapsulation
IOAM: In-situ Operations, Administration, and Maintenance IOAM: In-situ Operations, Administration, and Maintenance
MTU: Maximum Transmit Unit MTU: Maximum Transmit Unit
skipping to change at page 8, line 47 skipping to change at page 9, line 10
be directly exported to a collector rather than being collected be directly exported to a collector rather than being collected
within the data packets. The IOAM Direct Export Option-Type consist within the data packets. The IOAM Direct Export Option-Type consist
of a fixed size "IOAM direct export option header". Direct Export of a fixed size "IOAM direct export option header". Direct Export
for IOAM is defined in [I-D.ietf-ippm-ioam-direct-export]. for IOAM is defined in [I-D.ietf-ippm-ioam-direct-export].
5. IOAM Encapsulations 5. IOAM Encapsulations
IOAM data fields and associated data types for in-situ OAM are IOAM data fields and associated data types for in-situ OAM are
defined in [I-D.ietf-ippm-ioam-data]. The in-situ OAM data field can defined in [I-D.ietf-ippm-ioam-data]. The in-situ OAM data field can
be transported by a variety of transport protocols, including NSH, be transported by a variety of transport protocols, including NSH,
Segment Routing, Geneve, IPv6, etc. Segment Routing, Geneve, BIER, IPv6, etc.
5.1. IPv6 5.1. IPv6
IOAM encapsulation for IPv6 is defined in IOAM encapsulation for IPv6 is defined in
[I-D.ietf-ippm-ioam-ipv6-options]. IOAM deployment considerations [I-D.ietf-ippm-ioam-ipv6-options], which also discussed IOAM
for IPv6 networks are found in deployment considerations for IPv6 networks
[I-D.ioametal-ippm-6man-ioam-ipv6-deployment].
5.2. NSH 5.2. NSH
IOAM encapsulation for NSH is defined in [I-D.ietf-sfc-ioam-nsh]. IOAM encapsulation for NSH is defined in [I-D.ietf-sfc-ioam-nsh].
5.3. GRE 5.3. BIER
IOAM encapsulation for BIER is defined in [I-D.xzlnp-bier-ioam].
5.4. GRE
IOAM encapsulation for GRE is outlined as part of the "EtherType IOAM encapsulation for GRE is outlined as part of the "EtherType
Protocol Identification of In-situ OAM Data" in Protocol Identification of In-situ OAM Data" in
[I-D.weis-ippm-ioam-eth], though no example protocol header stacks [I-D.weis-ippm-ioam-eth], though no example protocol header stacks
are provided in the document. When used with GRE, the IOAM-Option- are provided in the document. When used with GRE, the IOAM-Option-
Types (the below diagram uses "IOAM" as shorthand for IOAM-Option- Types (the below diagram uses "IOAM" as shorthand for IOAM-Option-
Types) are sequenced in behind the GRE header that follows the Types) are sequenced in behind the GRE header that follows the
"outer" IP header. Figure 2 shows two example protocol header stacks "outer" IP header. Figure 2 shows two example protocol header stacks
that use GRE along with IOAM. that use GRE along with IOAM.
skipping to change at page 10, line 5 skipping to change at page 10, line 26
+----------------+ +----------------+ +----------------+ +----------------+
| IP header | | IP header | | IP header | | IP header |
+----------------+ +----------------+ +----------------+ +----------------+
| Layer 2 | | Layer 2 | | Layer 2 | | Layer 2 |
+----------------+ +----------------+ +----------------+ +----------------+
| Layer 1 | | Layer 1 | | Layer 1 | | Layer 1 |
+----------------+ +----------------+ +----------------+ +----------------+
Figure 2: GRE with IOAM examples Figure 2: GRE with IOAM examples
5.4. Geneve 5.5. Geneve
IOAM encapsulation for Geneve is defined in IOAM encapsulation for Geneve is defined in
[I-D.brockners-ippm-ioam-geneve]. [I-D.brockners-ippm-ioam-geneve].
5.5. Segment Routing 5.6. Segment Routing
IOAM encapsulation for Segment Routing is defined in IOAM encapsulation for Segment Routing is defined in
[I-D.gandhi-spring-ioam-sr-mpls]. [I-D.gandhi-spring-ioam-sr-mpls].
5.6. Segment Routing for IPv6 5.7. Segment Routing for IPv6
IOAM encapsulation for Segment Routing over IPv6 is defined in IOAM encapsulation for Segment Routing over IPv6 is defined in
[I-D.ali-spring-ioam-srv6]. [I-D.ali-spring-ioam-srv6].
5.7. VXLAN-GPE 5.8. VXLAN-GPE
IOAM encapsulation for VXLAN-GPE is defined in IOAM encapsulation for VXLAN-GPE is defined in
[I-D.brockners-ippm-ioam-vxlan-gpe]. [I-D.brockners-ippm-ioam-vxlan-gpe].
6. IOAM Data Export 6. IOAM Data Export
IOAM nodes collect information for packets traversing a domain that IOAM nodes collect information for packets traversing a domain that
supports IOAM. IOAM decapsulating nodes as well as IOAM transit supports IOAM. IOAM decapsulating nodes as well as IOAM transit
nodes can choose to retrieve IOAM information from the packet, nodes can choose to retrieve IOAM information from the packet,
process the information further and export the information using process the information further and export the information using
skipping to change at page 20, line 11 skipping to change at page 21, line 11
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
12.2. Informative References 12.2. Informative References
[I-D.ali-spring-ioam-srv6] [I-D.ali-spring-ioam-srv6]
Ali, Z., Gandhi, R., Filsfils, C., Brockners, F., Nainar, Ali, Z., Gandhi, R., Filsfils, C., Brockners, F., Nainar,
N., Pignataro, C., Li, C., Chen, M., and G. Dawra, N., Pignataro, C., Li, C., Chen, M., and G. Dawra,
"Segment Routing Header encapsulation for In-situ OAM "Segment Routing Header encapsulation for In-situ OAM
Data", draft-ali-spring-ioam-srv6-04 (work in progress), Data", draft-ali-spring-ioam-srv6-05 (work in progress),
July 2021. January 2022.
[I-D.brockners-ippm-ioam-geneve] [I-D.brockners-ippm-ioam-geneve]
Brockners, F., Bhandari, S., Govindan, V. P., Pignataro, Brockners, F., Bhandari, S., Govindan, V. P., Pignataro,
C., Nainar, N. K., Gredler, H., Leddy, J., Youell, S., C., Nainar, N. K., Gredler, H., Leddy, J., Youell, S.,
Mizrahi, T., Lapukhov, P., Gafni, B., Kfir, A., and M. Mizrahi, T., Lapukhov, P., Gafni, B., Kfir, A., and M.
Spiegel, "Geneve encapsulation for In-situ OAM Data", Spiegel, "Geneve encapsulation for In-situ OAM Data",
draft-brockners-ippm-ioam-geneve-05 (work in progress), draft-brockners-ippm-ioam-geneve-05 (work in progress),
November 2020. November 2020.
[I-D.brockners-ippm-ioam-vxlan-gpe] [I-D.brockners-ippm-ioam-vxlan-gpe]
skipping to change at page 20, line 37 skipping to change at page 21, line 37
ioam-vxlan-gpe-03 (work in progress), November 2019. ioam-vxlan-gpe-03 (work in progress), November 2019.
[I-D.gandhi-spring-ioam-sr-mpls] [I-D.gandhi-spring-ioam-sr-mpls]
Gandhi, R., Ali, Z., Filsfils, C., Brockners, F., Wen, B., Gandhi, R., Ali, Z., Filsfils, C., Brockners, F., Wen, B.,
and V. Kozak, "Segment Routing with MPLS Data Plane and V. Kozak, "Segment Routing with MPLS Data Plane
Encapsulation for In-situ OAM Data", draft-gandhi-spring- Encapsulation for In-situ OAM Data", draft-gandhi-spring-
ioam-sr-mpls-02 (work in progress), August 2019. ioam-sr-mpls-02 (work in progress), August 2019.
[I-D.ietf-ippm-ioam-data] [I-D.ietf-ippm-ioam-data]
Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields
for In-situ OAM", draft-ietf-ippm-ioam-data-15 (work in for In-situ OAM", draft-ietf-ippm-ioam-data-17 (work in
progress), October 2021. progress), December 2021.
[I-D.ietf-ippm-ioam-direct-export] [I-D.ietf-ippm-ioam-direct-export]
Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F., Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F.,
Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ
OAM Direct Exporting", draft-ietf-ippm-ioam-direct- OAM Direct Exporting", draft-ietf-ippm-ioam-direct-
export-07 (work in progress), October 2021. export-07 (work in progress), October 2021.
[I-D.ietf-ippm-ioam-flags] [I-D.ietf-ippm-ioam-flags]
Mizrahi, T., Brockners, F., Bhandari, S., Sivakolundu, R., Mizrahi, T., Brockners, F., Bhandari, S., Sivakolundu, R.,
Pignataro, C., Kfir, A., Gafni, B., Spiegel, M., and J. Pignataro, C., Kfir, A., Gafni, B., Spiegel, M., and J.
Lemon, "In-situ OAM Loopback and Active Flags", draft- Lemon, "In-situ OAM Loopback and Active Flags", draft-
ietf-ippm-ioam-flags-07 (work in progress), October 2021. ietf-ippm-ioam-flags-07 (work in progress), October 2021.
[I-D.ietf-ippm-ioam-ipv6-options] [I-D.ietf-ippm-ioam-ipv6-options]
Bhandari, S. and F. Brockners, "In-situ OAM IPv6 Options", Bhandari, S. and F. Brockners, "In-situ OAM IPv6 Options",
draft-ietf-ippm-ioam-ipv6-options-06 (work in progress), draft-ietf-ippm-ioam-ipv6-options-07 (work in progress),
July 2021. February 2022.
[I-D.ietf-nvo3-geneve] [I-D.ietf-nvo3-geneve]
Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic
Network Virtualization Encapsulation", draft-ietf- Network Virtualization Encapsulation", draft-ietf-
nvo3-geneve-16 (work in progress), March 2020. nvo3-geneve-16 (work in progress), March 2020.
[I-D.ietf-nvo3-vxlan-gpe] [I-D.ietf-nvo3-vxlan-gpe]
(Editor), F. M., (editor), L. K., and U. E. (editor), (Editor), F. M., (editor), L. K., and U. E. (editor),
"Generic Protocol Extension for VXLAN (VXLAN-GPE)", draft- "Generic Protocol Extension for VXLAN (VXLAN-GPE)", draft-
ietf-nvo3-vxlan-gpe-12 (work in progress), September 2021. ietf-nvo3-vxlan-gpe-12 (work in progress), September 2021.
[I-D.ietf-sfc-ioam-nsh] [I-D.ietf-sfc-ioam-nsh]
Brockners, F. and S. Bhandari, "Network Service Header Brockners, F. and S. Bhandari, "Network Service Header
(NSH) Encapsulation for In-situ OAM (IOAM) Data", draft- (NSH) Encapsulation for In-situ OAM (IOAM) Data", draft-
ietf-sfc-ioam-nsh-06 (work in progress), July 2021. ietf-sfc-ioam-nsh-08 (work in progress), April 2022.
[I-D.ietf-sfc-proof-of-transit] [I-D.ietf-sfc-proof-of-transit]
Brockners, F., Bhandari, S., Mizrahi, T., Dara, S., and S. Brockners, F., Bhandari, S., Mizrahi, T., Dara, S., and S.
Youell, "Proof of Transit", draft-ietf-sfc-proof-of- Youell, "Proof of Transit", draft-ietf-sfc-proof-of-
transit-08 (work in progress), November 2020. transit-08 (work in progress), November 2020.
[I-D.ioametal-ippm-6man-ioam-ipv6-deployment]
Bhandari, S., Brockners, F., Mizrahi, T., Kfir, A., Gafni,
B., Spiegel, M., Krishnan, S., and M. Smith, "Deployment
Considerations for In-situ OAM with IPv6 Options", draft-
ioametal-ippm-6man-ioam-ipv6-deployment-03 (work in
progress), March 2020.
[I-D.mizrahi-ippm-ioam-profile] [I-D.mizrahi-ippm-ioam-profile]
Mizrahi, T., Brockners, F., Bhandari, S., Sivakolundu, R., Mizrahi, T., Brockners, F., Bhandari, S., Sivakolundu, R.,
Pignataro, C., Kfir, A., Gafni, B., Spiegel, M., Zhou, T., Pignataro, C., Kfir, A., Gafni, B., Spiegel, M., and T.
and J. Lemon, "In Situ OAM Profiles", draft-mizrahi-ippm- Zhou, "In Situ OAM Profiles", draft-mizrahi-ippm-ioam-
ioam-profile-05 (work in progress), August 2021. profile-06 (work in progress), February 2022.
[I-D.spiegel-ippm-ioam-rawexport] [I-D.spiegel-ippm-ioam-rawexport]
Spiegel, M., Brockners, F., Bhandari, S., and R. Spiegel, M., Brockners, F., Bhandari, S., and R.
Sivakolundu, "In-situ OAM raw data export with IPFIX", Sivakolundu, "In-situ OAM raw data export with IPFIX",
draft-spiegel-ippm-ioam-rawexport-05 (work in progress), draft-spiegel-ippm-ioam-rawexport-06 (work in progress),
July 2021. February 2022.
[I-D.weis-ippm-ioam-eth] [I-D.weis-ippm-ioam-eth]
Weis, B., Brockners, F., Hill, C., Bhandari, S., Govindan, Weis, B., Brockners, F., Hill, C., Bhandari, S., Govindan,
V. P., Pignataro, C., Gredler, H., Leddy, J., Youell, S., V. P., Pignataro, C., Nainar, N. K., Gredler, H., Leddy,
Mizrahi, T., Kfir, A., Gafni, B., Lapukhov, P., and M. J., Youell, S., Mizrahi, T., Kfir, A., Gafni, B.,
Spiegel, "EtherType Protocol Identification of In-situ OAM Lapukhov, P., and M. Spiegel, "EtherType Protocol
Data", draft-weis-ippm-ioam-eth-04 (work in progress), May Identification of In-situ OAM Data", draft-weis-ippm-ioam-
2020. eth-05 (work in progress), February 2022.
[I-D.xzlnp-bier-ioam]
Min, X., Zhang, Z., Liu, Y., Nainar, N. K., and C.
Pignataro, "Bit Index Explicit Replication (BIER)
Encapsulation for In-situ OAM (IOAM) Data", draft-xzlnp-
bier-ioam-03 (work in progress), January 2022.
[I-D.zhou-ippm-ioam-yang] [I-D.zhou-ippm-ioam-yang]
Zhou, T., Guichard, J., Brockners, F., and S. Raghavan, "A Zhou, T., Guichard, J., Brockners, F., and S. Raghavan, "A
YANG Data Model for In-Situ OAM", draft-zhou-ippm-ioam- YANG Data Model for In-Situ OAM", draft-zhou-ippm-ioam-
yang-08 (work in progress), July 2020. yang-08 (work in progress), July 2020.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms "Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<https://www.rfc-editor.org/info/rfc5905>. <https://www.rfc-editor.org/info/rfc5905>.
 End of changes. 26 change blocks. 
60 lines changed or deleted 65 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/