< draft-xiao-ippm-ioam-conf-state-03.txt   draft-xiao-ippm-ioam-conf-state-04.txt >
IPPM Working Group X. Min IPPM Working Group X. Min
Internet-Draft G. Mirsky Internet-Draft G. Mirsky
Intended status: Standards Track ZTE Intended status: Standards Track ZTE
Expires: September 9, 2019 L. Bo Expires: January 9, 2020 L. Bo
China Telecom China Telecom
March 8, 2019 July 8, 2019
Echo Request/Reply for In-situ OAM Capabilities Echo Request/Reply for In-situ OAM Capabilities
draft-xiao-ippm-ioam-conf-state-03 draft-xiao-ippm-ioam-conf-state-04
Abstract Abstract
This document describes an extension to the echo request/reply This document describes an extension to the echo request/reply
mechanisms used in MPLS LSP, SRv6, and SFC environments, which can be mechanisms used in SR-MPLS, SRv6, and SFC environments, which can be
used within an IOAM domain, allowing the IOAM encapsulating node to used within an IOAM domain, allowing the IOAM encapsulating node to
acquire IOAM capabilities of each IOAM transit node and/or IOAM acquire IOAM capabilities of each IOAM transit node and/or IOAM
decapsulating node. decapsulating node.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 September 9, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
skipping to change at page 3, line 8 skipping to change at page 3, line 8
and the decapsulating node are referred to as domain edge devices, and the decapsulating node are referred to as domain edge devices,
which can be hosts or network devices. which can be hosts or network devices.
In order to add accurate IOAM data container to the packet, the IOAM In order to add accurate IOAM data container to the packet, the IOAM
encapsulating node needs to know IOAM capabilities at the IOAM encapsulating node needs to know IOAM capabilities at the IOAM
transit nodes and/or the IOAM decapsulating node as a whole, e.g., transit nodes and/or the IOAM decapsulating node as a whole, e.g.,
how many IOAM transit nodes will add tracing data and what kinds of how many IOAM transit nodes will add tracing data and what kinds of
data fields will be added. data fields will be added.
This document describes an extension to the echo request/reply This document describes an extension to the echo request/reply
mechanisms used in MPLS LSP, SRv6, and SFC environments, which can be mechanisms used in SR-MPLS, SRv6, and SFC environments, which can be
used within an IOAM domain, allowing the IOAM encapsulating node to used within an IOAM domain, allowing the IOAM encapsulating node to
acquire IOAM capabilities of each IOAM transit node and/or IOAM acquire IOAM capabilities of each IOAM transit node and/or IOAM
decapsulating node. decapsulating node.
The following documents contain references to the echo request/reply The following documents contain references to the echo request/reply
mechanisms used in MPLS LSP, SRv6, and SFC environments: mechanisms used in SR-MPLS, SRv6, and SFC environments:
o [RFC8029] ("Detecting Multiprotocol Label Switched (MPLS) Data- o [RFC8029] ("Detecting Multiprotocol Label Switched (MPLS) Data-
Plane Failures") Plane Failures")
o [I-D.ali-spring-srv6-oam] ("Operations, Administration, and o [I-D.ali-6man-spring-srv6-oam] ("Operations, Administration, and
Maintenance (OAM) in Segment Routing Networks with IPv6 Data plane Maintenance (OAM) in Segment Routing Networks with IPv6 Data plane
(SRv6)") (SRv6)")
o [I-D.ietf-sfc-multi-layer-oam] ("Active OAM for Service Function o [I-D.ietf-sfc-multi-layer-oam] ("Active OAM for Service Function
Chains in Networks") Chains in Networks")
The feature described in this document is assumedly applied to The feature described in this document is assumedly applied to
explicit path (strict or loose), because the precondition for this explicit path (strict or loose), because the precondition for this
feature to work is that the echo request reaches each IOAM transit feature to work is that the echo request reaches each IOAM transit
node as live traffic traverses. node as live traffic traverses.
skipping to change at page 4, line 12 skipping to change at page 4, line 12
OAM: Operations, Administration, and Maintenance OAM: Operations, Administration, and Maintenance
POSIX: Portable Operating System Interface POSIX: Portable Operating System Interface
POT: Proof of Transit POT: Proof of Transit
PTP: Precision Time Protocol PTP: Precision Time Protocol
SFC: Service Function Chain SFC: Service Function Chain
SR-MPLS: Segment Routing with MPLS Data plane
SRv6: Segment Routing with IPv6 Data plane SRv6: Segment Routing with IPv6 Data plane
TTL: Time to Live TTL: Time to Live
1.1.2. Requirements Language 1.1.2. Requirements Language
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
skipping to change at page 13, line 5 skipping to change at page 13, line 5
6. Acknowledgements 6. Acknowledgements
The authors would like to acknowledge Tianran Zhou for his careful The authors would like to acknowledge Tianran Zhou for his careful
review and helpful comments. review and helpful comments.
The authors appreciate the f2f discussion with Frank Brockners on The authors appreciate the f2f discussion with Frank Brockners on
this document. this document.
7. Normative References 7. Normative References
[I-D.ali-spring-srv6-oam] [I-D.ali-6man-spring-srv6-oam]
Ali, Z., Filsfils, C., Kumar, N., Pignataro, C., Ali, Z., Filsfils, C., Kumar, N., Pignataro, C., Gandhi,
faiqbal@cisco.com, f., Gandhi, R., Leddy, J., Matsushima, R., Brockners, F., Leddy, J., Matsushima, S., Raszuk, R.,
S., Raszuk, R., daniel.voyer@bell.ca, d., Dawra, G., daniel.voyer@bell.ca, d., Dawra, G., Peirens, B., Chen,
Peirens, B., Chen, M., and G. Naik, "Operations, M., Li, C., and F. Iqbal, "Operations, Administration, and
Administration, and Maintenance (OAM) in Segment Routing Maintenance (OAM) in Segment Routing Networks with IPv6
Networks with IPv6 Data plane (SRv6)", draft-ali-spring- Data plane (SRv6)", draft-ali-6man-spring-srv6-oam-01
srv6-oam-02 (work in progress), October 2018. (work in progress), March 2019.
[I-D.ietf-ippm-ioam-data] [I-D.ietf-ippm-ioam-data]
Brockners, F., Bhandari, S., Pignataro, C., Gredler, H., Brockners, F., Bhandari, S., Pignataro, C., Gredler, H.,
Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov, Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov,
P., Chang, R., daniel.bernier@bell.ca, d., and J. Lemon, P., Chang, R., daniel.bernier@bell.ca, d., and J. Lemon,
"Data Fields for In-situ OAM", draft-ietf-ippm-ioam- "Data Fields for In-situ OAM", draft-ietf-ippm-ioam-
data-04 (work in progress), October 2018. data-05 (work in progress), March 2019.
[I-D.ietf-sfc-multi-layer-oam] [I-D.ietf-sfc-multi-layer-oam]
Mirsky, G., Meng, W., Khasnabish, B., and C. Wang, "Active Mirsky, G., Meng, W., Khasnabish, B., and C. Wang, "Active
OAM for Service Function Chains in Networks", draft-ietf- OAM for Service Function Chains in Networks", draft-ietf-
sfc-multi-layer-oam-01 (work in progress), January 2019. sfc-multi-layer-oam-03 (work in progress), May 2019.
[IEEE1588v2] [IEEE1588v2]
Institute of Electrical and Electronics Engineers, "IEEE Institute of Electrical and Electronics Engineers, "IEEE
Std 1588-2008 - IEEE Standard for a Precision Clock Std 1588-2008 - IEEE Standard for a Precision Clock
Synchronization Protocol for Networked Measurement and Synchronization Protocol for Networked Measurement and
Control Systems", IEEE Std 1588-2008, 2008, Control Systems", IEEE Std 1588-2008, 2008,
<http://standards.ieee.org/findstds/ <http://standards.ieee.org/findstds/
standard/1588-2008.html>. standard/1588-2008.html>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 End of changes. 12 change blocks. 
18 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/