draft-ietf-6man-spring-srv6-oam-06.txt   draft-ietf-6man-spring-srv6-oam-07.txt 
6man Z. Ali 6man Z. Ali
Internet-Draft C. Filsfils Internet-Draft C. Filsfils
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: January 14, 2021 S. Matsushima Expires: January 27, 2021 S. Matsushima
Softbank Softbank
D. Voyer D. Voyer
Bell Canada Bell Canada
M. Chen M. Chen
Huawei Huawei
July 13, 2020 July 26, 2020
Operations, Administration, and Maintenance (OAM) in Segment Routing Operations, Administration, and Maintenance (OAM) in Segment Routing
Networks with IPv6 Data plane (SRv6) Networks with IPv6 Data plane (SRv6)
draft-ietf-6man-spring-srv6-oam-06 draft-ietf-6man-spring-srv6-oam-07
Abstract Abstract
This document describes how the existing IPv6 OAM mechanisms can be This document describes how the existing IPv6 OAM mechanisms can be
used in an SRv6 network. The document also introduces enhancements used in an SRv6 network. The document also introduces enhancements
for OAM mechanisms for SRv6 networks. for OAM mechanisms for SRv6 networks.
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
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 January 14, 2021. This Internet-Draft will expire on January 27, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 7, line 26 skipping to change at page 7, line 26
(e.g., ICMP, UDP). (e.g., ICMP, UDP).
Ping to a SID is used for SID connectivity checks and to validate the Ping to a SID is used for SID connectivity checks and to validate the
availability of a SID. Traceroute to a SID is used for hop-by-hop availability of a SID. Traceroute to a SID is used for hop-by-hop
fault localization as well as path tracing to a SID. Section 3 fault localization as well as path tracing to a SID. Section 3
illustrates the ICMPv6 based ping and the UDP based traceroute illustrates the ICMPv6 based ping and the UDP based traceroute
mechanisms for ping and traceroute to an SRv6 SID. Although this mechanisms for ping and traceroute to an SRv6 SID. Although this
document only illustrates ICMP ping and UDP-based traceroute to an document only illustrates ICMP ping and UDP-based traceroute to an
SRv6 SID, the procedures are equally applicable to other IPv6 OAM SRv6 SID, the procedures are equally applicable to other IPv6 OAM
probing to an SRv6 SID (e.g., Bidirectional Forwarding Detection probing to an SRv6 SID (e.g., Bidirectional Forwarding Detection
(BFD) [RFC5880], Seamless BFD (SBFD) [RFC7880], Two-Way Active (BFD) [RFC5880], Seamless BFD (SBFD) [RFC7880], TWAMP Light and STAMP
Measurement Protocol (TWAMP) [RFC5357], Simple Two-Way Active probe message processing as described in
Measurement Protocol (STAMP) [RFC8762], etc.). Specifically, as long [I-D.gandhi-spring-twamp-srpm] and [I-D.gandhi-spring-stamp-srpm],
as local configuration allows the Upper-layer Header processing of respectively, etc.). Specifically, as long as local configuration
the applicable OAM payload for SRv6 SIDs, the existing IPv6 OAM allows the Upper-layer Header processing of the applicable OAM payload
techniques can be used to target a probe to a (remote) SID. for SRv6 SIDs, the existing IPv6 OAM techniques can be used to target
a probe to a (remote) SID.
IPv6 OAM operations can be performed with the target SID in the IPv6 IPv6 OAM operations can be performed with the target SID in the IPv6
destination address without SRH or with SRH where the target SID is destination address without SRH or with SRH where the target SID is
the last segment. In general, OAM operations to a target SID may not the last segment. In general, OAM operations to a target SID may not
exercise all of its processing depending on its behavior definition. exercise all of its processing depending on its behavior definition.
For example, ping to an END.X SID (refer [I-D.ietf-spring-srv6- For example, ping to an END.X SID (refer [I-D.ietf-spring-srv6-
network-programming]) at the target node only validates availability network-programming]) at the target node only validates availability
of the SID and does not validate switching to the correct outgoing of the SID and does not validate switching to the correct outgoing
interface. To exercise the behavior of a target SID, the OAM interface. To exercise the behavior of a target SID, the OAM
operation SHOULD construct the probe in a manner similar to a data operation SHOULD construct the probe in a manner similar to a data
skipping to change at page 19, line 37 skipping to change at page 19, line 37
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J.,
Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header
(SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020,
<https://www.rfc-editor.org/info/rfc8754>. <https://www.rfc-editor.org/info/rfc8754>.
9.2. Informative References 9.2. Informative References
[I-D.gandhi-spring-stamp-srpm]
Gandhi, R., Filsfils, C., Voyer, D., Chen, M., and B.
Janssens, "Performance Measurement Using STAMP for Segment
Routing Networks", draft-gandhi-spring-stamp-srpm-01 (work
in progress), June 2020.
[I-D.gandhi-spring-twamp-srpm]
Gandhi, R., Filsfils, C., Voyer, D., Chen, M., and B.
Janssens, "Performance Measurement Using TWAMP Light for
Segment Routing Networks", draft-gandhi-spring-twamp-
srpm-09 (work in progress), June 2020.
[I-D.ietf-spring-srv6-network-programming] [I-D.ietf-spring-srv6-network-programming]
Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., Filsfils, C., Camarillo, P., Leddy, J., Voyer, D.,
Matsushima, S., and Z. Li, "SRv6 Network Programming", Matsushima, S., and Z. Li, "SRv6 Network Programming",
draft-ietf-spring-srv6-network-programming-16 (work in draft-ietf-spring-srv6-network-programming-16 (work in
progress), June 2020. progress), June 2020.
[I-D.matsushima-spring-srv6-deployment-status] [I-D.matsushima-spring-srv6-deployment-status]
Matsushima, S., Filsfils, C., Ali, Z., Li, Z., and K. Matsushima, S., Filsfils, C., Ali, Z., Li, Z., and K.
Rajaraman, "SRv6 Implementation and Deployment Status", Rajaraman, "SRv6 Implementation and Deployment Status",
draft-matsushima-spring-srv6-deployment-status-07 (work in draft-matsushima-spring-srv6-deployment-status-07 (work in
skipping to change at page 20, line 20 skipping to change at page 20, line 32
Control Message Protocol (ICMPv6) for the Internet Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification", STD 89, Protocol Version 6 (IPv6) Specification", STD 89,
RFC 4443, DOI 10.17487/RFC4443, March 2006, RFC 4443, DOI 10.17487/RFC4443, March 2006,
<https://www.rfc-editor.org/info/rfc4443>. <https://www.rfc-editor.org/info/rfc4443>.
[RFC4884] Bonica, R., Gan, D., Tappan, D., and C. Pignataro, [RFC4884] Bonica, R., Gan, D., Tappan, D., and C. Pignataro,
"Extended ICMP to Support Multi-Part Messages", RFC 4884, "Extended ICMP to Support Multi-Part Messages", RFC 4884,
DOI 10.17487/RFC4884, April 2007, DOI 10.17487/RFC4884, April 2007,
<https://www.rfc-editor.org/info/rfc4884>. <https://www.rfc-editor.org/info/rfc4884>.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
RFC 5357, DOI 10.17487/RFC5357, October 2008,
<https://www.rfc-editor.org/info/rfc5357>.
[RFC5476] Claise, B., Ed., Johnson, A., and J. Quittek, "Packet [RFC5476] Claise, B., Ed., Johnson, A., and J. Quittek, "Packet
Sampling (PSAMP) Protocol Specifications", RFC 5476, Sampling (PSAMP) Protocol Specifications", RFC 5476,
DOI 10.17487/RFC5476, March 2009, DOI 10.17487/RFC5476, March 2009,
<https://www.rfc-editor.org/info/rfc5476>. <https://www.rfc-editor.org/info/rfc5476>.
[RFC5837] Atlas, A., Ed., Bonica, R., Ed., Pignataro, C., Ed., Shen, [RFC5837] Atlas, A., Ed., Bonica, R., Ed., Pignataro, C., Ed., Shen,
N., and JR. Rivers, "Extending ICMP for Interface and N., and JR. Rivers, "Extending ICMP for Interface and
Next-Hop Identification", RFC 5837, DOI 10.17487/RFC5837, Next-Hop Identification", RFC 5837, DOI 10.17487/RFC5837,
April 2010, <https://www.rfc-editor.org/info/rfc5837>. April 2010, <https://www.rfc-editor.org/info/rfc5837>.
skipping to change at page 21, line 24 skipping to change at page 21, line 33
[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
July 2018, <https://www.rfc-editor.org/info/rfc8402>. July 2018, <https://www.rfc-editor.org/info/rfc8402>.
[RFC8403] Geib, R., Ed., Filsfils, C., Pignataro, C., Ed., and N. [RFC8403] Geib, R., Ed., Filsfils, C., Pignataro, C., Ed., and N.
Kumar, "A Scalable and Topology-Aware MPLS Data-Plane Kumar, "A Scalable and Topology-Aware MPLS Data-Plane
Monitoring System", RFC 8403, DOI 10.17487/RFC8403, July Monitoring System", RFC 8403, DOI 10.17487/RFC8403, July
2018, <https://www.rfc-editor.org/info/rfc8403>. 2018, <https://www.rfc-editor.org/info/rfc8403>.
[RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple
Two-Way Active Measurement Protocol", RFC 8762,
DOI 10.17487/RFC8762, March 2020,
<https://www.rfc-editor.org/info/rfc8762>.
Authors' Addresses Authors' Addresses
Zafar Ali Zafar Ali
Cisco Systems Cisco Systems
Email: zali@cisco.com Email: zali@cisco.com
Clarence Filsfils Clarence Filsfils
Cisco Systems Cisco Systems
 End of changes. 8 change blocks. 
20 lines changed or deleted 23 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/