wdiff draft-ietf-6man-spring-srv6-oam-12.txt draft-ietf-6man-spring-srv6-oam-13.txt

6man Z. Ali
Internet-Draft C. Filsfils
Intended status: Standards Track Cisco Systems
Expires: June 1, July 27, 2022 S. Matsushima
Softbank
D. Voyer
Bell Canada
M. Chen
Huawei
November 28, 2021
January 23, 2022

Operations, Administration, and Maintenance (OAM) in Segment Routing
Networks with IPv6 Data plane (SRv6)
draft-ietf-6man-spring-srv6-oam-12
draft-ietf-6man-spring-srv6-oam-13

Abstract

This document describes how the existing IPv6 mechanisms for ping and
traceroute can be used in an SRv6 network. The document also
specifies the OAM flag in the Segment Routing Header (SRH) for
performing controllable and predictable flow sampling from segment
endpoints. In addition, the document describes how a centralized
monitoring system performs a path continuity check between any nodes
within an SRv6 domain.

Status of This Memo

This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

This Internet-Draft will expire on June 1, July 27, 2022.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Terminology and Reference Topology . . . . . . . . . . . 4
2. OAM Mechanisms . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. O-flag in Segment Routing Header . . . . . . . . . . . . 5
2.1.1. O-flag Processing . . . . . . . . . . . . . . . . . . 6
2.2. OAM Operations . . . . . . . . . . . . . . . . . . . . . 8
3. Illustrations . . . . Implementation Status . . . . . . . . . . . . . . . . . . . . 8
3.1. Ping in SRv6 Networks . . . .
4. Security Considerations . . . . . . . . . . . . . . 9
3.1.1. Pinging an IPv6 Address via a Segment-list . . . . . 9
3.1.2. Pinging a SID . . . . .
5. Privacy Considerations . . . . . . . . . . . . . . . 10
3.2. Traceroute . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . 11
3.2.1. Traceroute to an IPv6 Address via a Segment-list . . 11
3.2.2. Traceroute to a SID 9
7. References . . . . . . . . . . . . . . . . . 13
3.3. A Hybrid OAM Using O-flag . . . . . . . . 10
7.1. Normative References . . . . . . . . 15
3.4. Monitoring of SRv6 Paths . . . . . . . . . . 10
7.2. Informative References . . . . . . 17
4. Implementation Status . . . . . . . . . . . 10
Appendix A. Illustrations . . . . . . . . . 18
5. Security Considerations . . . . . . . . . . 12
A.1. Ping in SRv6 Networks . . . . . . . . . 18
6. Privacy Considerations . . . . . . . . . 12
A.1.1. Pinging an IPv6 Address via a Segment-list . . . . . 13
A.1.2. Pinging a SID . . . . . 19
7. IANA Considerations . . . . . . . . . . . . . . . 14
A.2. Traceroute . . . . . . 19
8. Acknowledgements . . . . . . . . . . . . . . . . . 15
A.2.1. Traceroute to an IPv6 Address via a Segment-list . . 15
A.2.2. Traceroute to a SID . . . 20
9. Contributors . . . . . . . . . . . . . . 17
A.3. A Hybrid OAM Using O-flag . . . . . . . . . . 20
10. References . . . . . . 18
A.4. Monitoring of SRv6 Paths . . . . . . . . . . . . . . . . 21
Appendix B. Acknowledgements . . . 21
10.1. Normative References . . . . . . . . . . . . . . . 22
Appendix C. Contributors . . . 21
10.2. Informative References . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23

1. Introduction

As Segment Routing with IPv6 data plane (SRv6) [RFC8402] simply adds
a new type of Routing Extension Header, existing IPv6 OAM mechanisms
can be used in an SRv6 network. This document describes how the
existing IPv6 mechanisms for ping and traceroute can be used in an
SRv6 network. This includes illustrations of pinging an SRv6 SID to
verify that the SID is reachable and is locally programmed at the
target node. This also includes illustrations for tracerouting to an
SRv6 SID for hop-by-hop fault localization as well as path tracing to
a SID.

The document also introduces enhancements for the OAM mechanism for
SRv6 networks for performing controllable and predictable flow
sampling from segment endpoints using, e.g., IP Flow Information
Export (IPFIX) protocol [RFC7011]. Specifically, the document
specifies the O-flag in SRH as a marking-bit in the user packets to
trigger the telemetry data collection and export at the segment
endpoints.

The document also outlines how the centralized OAM technique in
[RFC8403] can be extended for SRv6 to perform a path continuity check
between any nodes within an SRv6 domain. Specifically, the document
illustrates how a centralized monitoring system can monitor arbitrary
SRv6 paths by creating the loopback probes that originate and
terminate at the centralized monitoring system.

1.1. Requirements Language

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 BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.

1.2. Abbreviations

The following abbreviations are used in this document:

SID: Segment ID.

SL: Segments Left.

SR: Segment Routing.

SRH: Segment Routing Header [RFC8754].

SRv6: Segment Routing with IPv6 Data plane.

PSP: Penultimate Segment Pop of the SRH [RFC8986].

USP: Ultimate Segment Pop of the SRH [RFC8986].

ICMPv6: ICMPv6 Specification [RFC4443].

IS-IS: Intermediate System to Intermediate System
OSPF: Open Shortest Path First protocol [RFC2328]

IGP: Interior Gateway Protocols (e.g., OSPF, IS-IS).

BGP-LS: Border Gateway Protocol - Link State Extensions [RFC8571]

1.3. Terminology and Reference Topology

Throughout the document, the following terminology and simple
topology is used for illustration.

+--------------------------| N100 |---------------------------------+
| |
| ====== link1====== link3------ link5====== link9------ ====== |
||N1||------||N2||------| N3 |------||N4||------| N5 |---||N7||
|| ||------|| ||------| |------|| ||------| |---|| ||
====== link2====== link4------ link6======link10------ ======
| | | |
---+-- | ------ | --+---
|CE 1| +-------| N6 |---------+ |CE 2|
------ link7 | | link8 ------
------

Figure 1 Reference Topology

In the reference topology:

Node j has a IPv6 loopback address 2001:db8:L:j::/128.

Nodes N1, N2, N4 and N7 are SRv6-capable nodes.

Nodes N3, N5 and N6 are IPv6 nodes that are not SRv6-capable.
Such nodes are referred as non-SRv6 capable nodes.

CE1 and CE2 are Customer Edge devices of any data plane capability
(e.g., IPv4, IPv6, L2, etc.).

A SID at node j with locator block 2001:db8:K::/48 and function U
is represented by 2001:db8:K:j:U::.

Node N100 is a controller.

The IPv6 address of the nth Link between node i and j at the i
side is represented as 2001:db8:i:j:in::, e.g., the IPv6 address
of link6 (the 2nd link between N3 and N4) at N3 in Figure 1 is
2001:db8:3:4:32::. Similarly, the IPv6 address of link5 (the 1st
link between N3 and N4) at node N3 is 2001:db8:3:4:31::.

2001:db8:K:j:Xin:: is explicitly allocated as the End.X SID at
node j towards neighbor node i via nth Link between node i and
node j. e.g., 2001:db8:K:2:X31:: represents End.X at N2 towards
N3 via link3 (the 1st link between N2 and N3). Similarly,
2001:db8:K:4:X52:: represents the End.X at N4 towards N5 via
link10 (the 2nd link between N4 and N5). Please refer to
[RFC8986] for description of End.X SID.

A SID list is represented as <S1, S2, S3> where S1 is the first
SID to visit, S2 is the second SID to visit and S3 is the last SID
to visit along the SR path.

(SA,DA) (S3, S2, S1; SL)(payload) represents an IPv6 packet with:

* IPv6 header with source address SA, destination addresses DA
and SRH as next-header

* SRH with SID list <S1, S2, S3> with SegmentsLeft = SL

* Note the difference between the < > and () symbols: <S1, S2,
S3> represents a SID list where S1 is the first SID and S3 is
the last SID to traverse. (S3, S2, S1; SL) represents the same
SID list but encoded in the SRH format where the rightmost SID
in the SRH is the first SID and the leftmost SID in the SRH is
the last SID. When referring to an SR policy in a high-level
use-case, it is simpler to use the <S1, S2, S3> notation. When
referring to an illustration of the detailed packet behavior,
the (S3, S2, S1; SL) notation is more convenient.

* (payload) represents the the payload of the packet.

2. OAM Mechanisms

This section defines OAM enhancement for the SRv6 networks.

2.1. O-flag in Segment Routing Header

[RFC8754] describes the Segment Routing Header (SRH) and how SR
capable nodes use it. The SRH contains an 8-bit "Flags" field.

This document defines the following bit in the SRH Flags field to
carry the O-flag:

0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| |O| |
+-+-+-+-+-+-+-+-+

Where:

O-flag: OAM flag in the SRH Flags field defined in [RFC8754].

2.1.1. O-flag Processing

The O-flag in SRH is used as a marking-bit in the user packets to
trigger the telemetry data collection and export at the segment
endpoints.

An SR domain ingress edge node encapsulates packets traversing the SR
domain as defined in [RFC8754]. The SR domain ingress edge node MAY
use the O-flag in SRH for marking the packet to trigger the telemetry
data collection and export at the segment endpoints. Based on a
local configuration, the SR domain ingress edge node may implement a
classification and sampling mechanism to mark a packet with the
O-flag in SRH. Specification of the classification and sampling
method is outside the scope of this document.

This document does not specify the data elements that need to be
exported and the associated configurations. Similarly, this document
does not define any formats for exporting the data elements.
Nonetheless, without the loss of generality, this document assumes IP
Flow Information Export (IPFIX) protocol [RFC7011] is used for
exporting the traffic flow information from the network devices to a
controller for monitoring and analytics. Similarly, without the loss
of generality, this document assumes requested information elements
are configured by the management plane through data set templates
(e.g., as in IPFIX [RFC7012]).

Implementation of the O-flag is OPTIONAL. If a node does not support
the O-flag, then upon reception it simply ignores it. If a node
supports the O-flag, it can optionally advertise its potential via
control plane protocol(s).

When N receives a packet destined to S and S is a local SID, the line
S01 of the pseudo-code associated with the SID S, as defined in
section 4.3.1.1 of [RFC8754], is appended to as follows for the
O-flag processing.

S01.1. IF O-flag is set and local configuration permits
O-flag processing {
a. Make a copy of the packet.
b. Send the copied packet, along with a timestamp
to the OAM process for telemetry data collection
and export. ;; Ref1
}
Ref1: To provide an accurate timestamp, an implementation should copy
and record the timestamp as soon as possible during packet processing.
Timestamp and any other metadata is not carried in the packet forwarded to the next hop.

Please note that the O-flag processing happens before execution of
regular processing of the local SID S. Specifically, the line S01.1
of the pseudo-code specified in this document is inserted between
line S01 and S02 of the pseudo-code defined in section 4.3.1.1 of
[RFC8754].

Based on the requested information elements configured by the
management plane through data set templates [RFC7012], the OAM
process exports the requested information elements. The information
elements include parts of the packet header and/or parts of the
packet payload for flow identification. The OAM process uses
information elements defined in IPFIX [RFC7011] and PSAMP [RFC5476]
for exporting the requested sections of the mirrored packets.

If the penultimate segment of a segment-list is a Penultimate Segment
Pop (PSP) SID, telemetry data from the ultimate segment cannot be
requested. This is because, when the penultimate segment is a PSP
SID, the SRH is removed at the penultimate segment and the O-flag is
not processed at the ultimate segment.

The processing node MUST rate-limit the number of packets punted to
the OAM process to a configurable rate. This is to avoid hitting any
performance impact on the OAM and the telemetry collection processes.
Failure in implementing the rate limit can lead to a denial-of-
service attack, as detailed in Section 5. section 4.

The OAM process MUST NOT process the copy of the packet or respond to
any upper-layer header (like ICMP, UDP, etc.) payload to prevent
multiple evaluations of the datagram.

The OAM process is expected to be located on the routing node
processing the packet. Although the specification of the OAM process
or the external controller operations are beyond the scope of this
document, the OAM process SHOULD NOT be topologically distant from
the routing node, as this is likely to create significant security
and congestion issues. How to correlate the data collected from
different nodes at an external controller is also outside the scope
of the document. Section 3 Appendix A illustrates use of the O-flag for
implementing a hybrid OAM mechanism, where the "hybrid"
classification is based on RFC7799 [RFC7799].

2.2. OAM Operations

IPv6 OAM operations can be performed for any SRv6 SID whose behavior
allows Upper Layer Header processing for an applicable OAM payload
(e.g., ICMP, UDP).

Ping to an SRv6 SID is used to verify that the SID is reachable and
is locally programmed at the target node. Traceroute to a SID is
used for hop-by-hop fault localization as well as path tracing to a
SID. Section 3 Appendix A illustrates the ICMPv6 based ping and the UDP based
traceroute mechanisms for ping and traceroute to an SRv6 SID.
Although this document only illustrates ICMPv6 ping and UDP based
traceroute to an SRv6 SID, the procedures are equally applicable to
other IPv6 OAM probing to an SRv6 SID (e.g., Bidirectional Forwarding
Detection (BFD) [RFC5880], Seamless BFD (SBFD) [RFC7880], STAMP probe
message processing [I-D.gandhi-spring-stamp-srpm], etc.).
Specifically, as long as local configuration allows the Upper-layer
Header processing of the applicable OAM payload 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
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
exercise all of its processing depending on its behavior definition.
For example, ping to an End.X SID [RFC8986] only validates the SID is
locally programmed at the target node and does not validate switching
to the correct outgoing interface. To exercise the behavior of a
target SID, the OAM operation should construct the probe in a manner
similar to a data packet that exercises the SID behavior, i.e. to
include that SID as a transit SID in either an SRH or IPv6 DA of an
outer IPv6 header or as appropriate based on the definition of the
SID behavior.

3. Illustrations Implementation Status

This section shows how some of the existing IPv6 OAM mechanisms can is to be used in an SRv6 network. It also illustrates removed prior to publishing as an OAM mechanism RFC.

See [I-D.matsushima-spring-srv6-deployment-status] for
performing controllable updated
deployment and predictable flow sampling from segment
endpoints. How centralized interoperability reports.

4. Security Considerations

[RFC8754] defines the notion of an SR domain and use of SRH within
the SR domain. The use of OAM technique in [RFC8403] can be
extended for SRv6 is also procedures described in this Section.

3.1. Ping in SRv6 Networks

The existing mechanism to perform the reachability checks, along the
shortest path, continues to work without any modification. Any IPv6
node (SRv6 capable or a non-SRv6 capable) can initiate, transit, and
egress a ping packet.

The following subsections outline some additional use cases of the
ICMPv6 ping in the SRv6 networks.

3.1.1. Pinging an IPv6 Address via a Segment-list

If an SRv6-capable ingress node wants to ping an IPv6 address via an
arbitrary segment list <S1, S2, S3>, it needs document
is restricted to initiate an ICMPv6
ping with an SR header containing domain. For example, similar to the SID list <S1, S2, S3>. This
manipulation, O-flag manipulation is
illustrated using not considered as a threat
within the topology SR domain. Procedures for securing an SR domain are
defined the section 5.1 and section 7 of [RFC8754].

As noted in Figure 1. User issues a ping from
node N1 to a loopback section 7.1 of [RFC8754], compromised nodes within the SR
domain may mount attacks. The O-flag may be set by an attacking node N5, via
attempting a denial-of-service attack on the OAM process at the
segment list
<2001:db8:K:2:X31::, 2001:db8:K:4:X52::>. The SID behavior used in endpoint node. An implementation correctly implementing the example
rate limiting in section 2.1.1 is End.X SID, not susceptible to that denial-of-
service attack. Additionally, SRH Flags are protected by the HMAC
TLV, as described in [RFC8986], but the
procedure section 2.1.2.1 of [RFC8754]. Once an HMAC is equally applicable to any other (transit) SID type.

Figure 2 contains sample output
generated for a ping request initiated at node
N1 to a loopback address of node N5 via a segment list
<2001:db8:K:2:X31::, 2001:db8:K:4:X52::>.

> ping 2001:db8:L:5:: via segment-list 2001:db8:K:2:X31::,
2001:db8:K:4:X52::

Sending 5, 100-byte ICMPv6 Echos to B5::, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.625
/0.749/0.931 ms

Figure 2 A sample ping output at with the O-flag set, it can be used for
an SRv6-capable node

All transit nodes process arbitrary amount of traffic using that segment list with O-flag
set.

The security properties of the echo request message like any other
data packet carrying SR header and hence do not require any change.
Similarly, channel used to send exported packets
marked by the egress node O-flag will depend on the specific OAM processes used.
An on-path attacker able to observe this OAM channel could conduct
traffic analysis, or potentially eavesdropping (depending on the OAM
configuration), of this telemetry for the entire SR domain from such
a vantage point.

This document does not require impose any change additional security challenges to process the
ICMPv6 echo request. For example,
be considered beyond security threats described in the ping example [RFC4884],
[RFC4443], [RFC0792], [RFC8754] and [RFC8986].

5. Privacy Considerations

The per-packet marking capabilities of Figure 2:

o Node N1 initiates an ICMPv6 ping packet with SRH as follows
(2001:db8:L:1::, 2001:db8:K:2:X31::) (2001:db8:L:5::,
2001:db8:K:4:X52::, 2001:db8:K:2:X31::, SL=2, NH = ICMPv6)(ICMPv6
Echo Request).

o Node N2, which the O-flag provides a granular
mechanism to collect telemetry. When this collection is deployed by
an SRv6-capable node, performs operator with knowledge and consent of the standard SRH
processing. Specifically, users, it executes the End.X behavior
indicated by the 2001:db8:K:2:X31:: SID will enable a
variety of diagnostics and forwards the packet on
link3 monitoring to N3.

o Node N3, which is a non-SRv6 capable node, performs the standard
IPv6 processing. Specifically, it forwards the echo request based
on the DA 2001:db8:K:4:X52:: in the IPv6 header.

o Node N4, which is an SRv6-capable node, performs the standard SRH
processing. Specifically, it observes the End.X behavior
(2001:db8:K:4:X52::) and forwards the packet on link10 towards N5.
If 2001:db8:K:4:X52:: is a PSP SID, the penultimate node (Node N4)
does not, should not and cannot differentiate between support the data
packets and OAM probes. Specifically, if 2001:db8:K:4:X52:: is a
PSP SID, node N4 executes the SID like any other data packet with
DA = 2001:db8:K:4:X52:: and removes the SRH.

o The echo request packet at N5 arrives as an IPv6 packet with or
without security
operations use cases needed for resilient network operations.
However, this collection mechanism will also provide an SRH. If N5 receives the packet with SRH, it skips SRH
processing (SL=0). In either case, Node N5 performs the standard
ICMPv6 processing on the echo request and responds with the echo
reply message to N1. The echo reply message is IP routed.

3.1.2. Pinging a SID

The ping explicit
protocol mechanism described above applies equally to perform SID
reachability check operators for surveillance and pervasive
monitoring use cases done contrary to validate the SID is locally programmed at the target node. user's consent.

6. IANA Considerations

This is explained using an example in document requests that IANA allocate the
following. The example uses ping to an END SID, as described following registration
in
[RFC8986], but the procedure is equally applicable to ping any other
SID behaviors.

Consider "Segment Routing Header Flags" sub-registry for the example where the user wants to ping a remote SID
2001:db8:K:4::, via 2001:db8:K:2:X31::, from node N1. The ICMPv6
echo request is processed at the individual nodes along the path as
follows:

o Node N1 initiates an ICMPv6 ping packet with SRH as follows
(2001:db8:L:1::, 2001:db8:K:2:X31::) (2001:db8:K:4::,
2001:db8:K:2:X31::; SL=1; NH=ICMPv6)(ICMPv6 Echo Request).

o Node N2, which is an SRv6-capable node, performs the standard SRH
processing. Specifically, it executes the End.X behavior
indicated "Internet
Protocol Version 6 (IPv6) Parameters" registry maintained by the 2001:db8:K:2:X31:: SID on the echo request
packet. If 2001:db8:K:2:X31:: is a PSP SID, node N4 executes the
SID like any other data packet with DA = 2001:db8:K:2:X31:: IANA:

+-------+------------------------------+---------------+
| Bit | Description | Reference |
+=======+==============================+===============+
| 2 | O-flag | This document |
+-------+------------------------------+---------------+

7. References

7.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.

[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.

[RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J.,
Matsushima, S., and
removes the SRH.

o Node N3, which is a non-SRv6 capable node, performs the standard D. Voyer, "IPv6 Segment Routing Header
(SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020,
<https://www.rfc-editor.org/info/rfc8754>.

[RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,
D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 processing. Specifically, it forwards the echo request based
on DA = 2001:db8:K:4::
(SRv6) Network Programming", RFC 8986,
DOI 10.17487/RFC8986, February 2021,
<https://www.rfc-editor.org/info/rfc8986>.

7.2. Informative References

[I-D.gandhi-spring-stamp-srpm]
Gandhi, R., Filsfils, C., Voyer, D., Chen, M., Janssens,
B., and R. Foote, "Performance Measurement Using Simple
TWAMP (STAMP) for Segment Routing Networks", draft-gandhi-
spring-stamp-srpm-07 (work in progress), July 2021.

[I-D.ietf-ippm-ioam-data]
Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields
for In-situ OAM", draft-ietf-ippm-ioam-data-11 (work in
progress), November 2020.

[I-D.matsushima-spring-srv6-deployment-status]
Matsushima, S., Filsfils, C., Ali, Z., Li, Z., and K.
Rajaraman, "SRv6 Implementation and Deployment Status",
draft-matsushima-spring-srv6-deployment-status-11 (work in
progress), February 2021.

[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, DOI 10.17487/RFC0792, September 1981,
<https://www.rfc-editor.org/info/rfc792>.

[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
DOI 10.17487/RFC2328, April 1998,
<https://www.rfc-editor.org/info/rfc2328>.

[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
Control Message Protocol (ICMPv6) for the IPv6 header.

o When node N4 receives the packet, it processes the target SID
(2001:db8:K:4::).

o If the target SID (2001:db8:K:4::) is not locally instantiated Internet
Protocol Version 6 (IPv6) Specification", STD 89,
RFC 4443, DOI 10.17487/RFC4443, March 2006,
<https://www.rfc-editor.org/info/rfc4443>.

[RFC4884] Bonica, R., Gan, D., Tappan, D., and C. Pignataro,
"Extended ICMP to Support Multi-Part Messages", RFC 4884,
DOI 10.17487/RFC4884, April 2007,
<https://www.rfc-editor.org/info/rfc4884>.

[RFC5476] Claise, B., Ed., Johnson, A., and J. Quittek, "Packet
Sampling (PSAMP) Protocol Specifications", RFC 5476,
DOI 10.17487/RFC5476, March 2009,
<https://www.rfc-editor.org/info/rfc5476>.

[RFC5837] Atlas, A., Ed., Bonica, R., Ed., Pignataro, C., Ed., Shen,
N., and JR. Rivers, "Extending ICMP for Interface and
Next-Hop Identification", RFC 5837, DOI 10.17487/RFC5837,
April 2010, <https://www.rfc-editor.org/info/rfc5837>.

[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>.

[RFC7011] Claise, B., Ed., Trammell, B., Ed., and
does not represent a local interface, the packet is discarded

o If the target SID (2001:db8:K:4::) is locally instantiated or
represents a local interface, the node processes the upper layer
header. As part P. Aitken,
"Specification of the upper layer header processing node N4
respond to IP Flow Information Export (IPFIX)
Protocol for the ICMPv6 echo request message Exchange of Flow Information", STD 77,
RFC 7011, DOI 10.17487/RFC7011, September 2013,
<https://www.rfc-editor.org/info/rfc7011>.

[RFC7012] Claise, B., Ed. and responds with B. Trammell, Ed., "Information Model
for IP Flow Information Export (IPFIX)", RFC 7012,
DOI 10.17487/RFC7012, September 2013,
<https://www.rfc-editor.org/info/rfc7012>.

[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
May 2016, <https://www.rfc-editor.org/info/rfc7799>.

[RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., and S.
Pallagatti, "Seamless Bidirectional Forwarding Detection
(S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016,
<https://www.rfc-editor.org/info/rfc7880>.

[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
July 2018, <https://www.rfc-editor.org/info/rfc8402>.

[RFC8403] Geib, R., Ed., Filsfils, C., Pignataro, C., Ed., and N.
Kumar, "A Scalable and Topology-Aware MPLS Data-Plane
Monitoring System", RFC 8403, DOI 10.17487/RFC8403, July
2018, <https://www.rfc-editor.org/info/rfc8403>.

[RFC8571] Ginsberg, L., Ed., Previdi, S., Wu, Q., Tantsura, J., and
C. Filsfils, "BGP - Link State (BGP-LS) Advertisement of
IGP Traffic Engineering Performance Metric Extensions",
RFC 8571, DOI 10.17487/RFC8571, March 2019,
<https://www.rfc-editor.org/info/rfc8571>.

Appendix A. Illustrations

This appendix shows how some of the
echo reply message. The echo reply message existing IPv6 OAM mechanisms can
be used in an SRv6 network. It also illustrates an OAM mechanism for
performing controllable and predictable flow sampling from segment
endpoints. How centralized OAM technique in [RFC8403] can be
extended for SRv6 is IP routed.

3.2. Traceroute also described in this appendix.

A.1. Ping in SRv6 Networks

The existing traceroute mechanisms, mechanism to perform the reachability checks, along the
shortest path, continues to work without any modification. Any IPv6
node (SRv6 capable or a non-SRv6 capable) can initiate, transit, and
egress a
traceroute probe. ping packet.

The following subsections outline some additional use cases of the
traceroute
ICMPv6 ping in the SRv6 networks.

3.2.1. Traceroute to

A.1.1. Pinging an IPv6 Address via a Segment-list

If an SRv6-capable ingress node wants to traceroute to ping an IPv6 address via an
arbitrary segment list <S1, S2, S3>, it needs to initiate a
traceroute probe with an SR header containing the SID list <S1, S2,
S3>. User issues a traceroute from node N1 to a loopback of node N5,
via segment list <2001:db8:K:2:X31::, 2001:db8:K:4:X52::>. The SID
behavior used in the example is End.X SID, as described in [RFC8986],
but the procedure is equally applicable to any other (transit) SID
type. Figure 3 contains sample output for the traceroute request.

> traceroute 2001:db8:L:5:: via segment-list 2001:db8:K:2:X31::,
2001:db8:K:4:X52::

Tracing the route to 2001:db8:L:5::
1 2001:db8:2:1:21:: 0.512 msec 0.425 msec 0.374 msec
DA: 2001:db8:K:2:X31::,
SRH:(2001:db8:L:5::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::, SL=2)
2 2001:db8:3:2:31:: 0.721 msec 0.810 msec 0.795 msec
DA: 2001:db8:K:4:X52::,
SRH:(2001:db8:L:5::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::, SL=1)
3 2001:db8:4:3::41:: 0.921 msec 0.816 msec 0.759 msec
DA: 2001:db8:K:4:X52::,
SRH:(2001:db8:L:5::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::, SL=1)
4 2001:db8:5:4::52:: 0.879 msec 0.916 msec 1.024 msec
DA: 2001:db8:L:5::

Figure 3 A sample traceroute output at an SRv6-capable node

In the sample traceroute output, the information displayed at each
hop is obtained using the contents of the "Time Exceeded" or
"Destination Unreachable" ICMPv6 responses. These ICMPv6 responses
are IP routed.

In the sample traceroute output, the information for link3 is
returned by N3, which is a non-SRv6 capable node. Nonetheless, the
ingress node is able to display ICMPv6
ping with an SR header contents as the packet
travels through containing the IPv6 classic node. SID list <S1, S2, S3>. This is because
illustrated using the "Time
Exceeded Message" ICMPv6 message can contain as much topology in Figure 1. User issues a ping from
node N1 to a loopback of the invoking
packet as possible without the ICMPv6 packet exceeding the minimum
IPv6 MTU [RFC4443]. node N5, via segment list
<2001:db8:K:2:X31::, 2001:db8:K:4:X52::>. The SR header SID behavior used in
the example is included End.X SID, as described in these ICMPv6
messages initiated by [RFC8986], but the non-SRv6 capable transit nodes that are not
running SRv6 software. Specifically,
procedure is equally applicable to any other (transit) SID type.

Figure 2 contains sample output for a ping request initiated at node generating ICMPv6
message containing
N1 to a copy loopback address of node N5 via a segment list
<2001:db8:K:2:X31::, 2001:db8:K:4:X52::>.

> ping 2001:db8:L:5:: via segment-list 2001:db8:K:2:X31::,
2001:db8:K:4:X52::

Sending 5, 100-byte ICMPv6 Echos to B5::, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.625
/0.749/0.931 ms

Figure 2 A sample ping output at an SRv6-capable node

All transit nodes process the invoking echo request message like any other
data packet carrying SR header and hence do not require any change.
Similarly, the egress node does not need require any change to
understand process the extension header(s)
ICMPv6 echo request. For example, in the invoking packet.

The segment list information returned for the first hop is returned
by ping example of Figure 2:

o Node N1 initiates an ICMPv6 ping packet with SRH as follows
(2001:db8:L:1::, 2001:db8:K:2:X31::) (2001:db8:L:5::,
2001:db8:K:4:X52::, 2001:db8:K:2:X31::, SL=2, NH = ICMPv6)(ICMPv6
Echo Request).

o Node N2, which is an SRv6-capable node. Just like for the second hop, node, performs the ingress node is able to display SR header contents for standard SRH
processing. Specifically, it executes the first
hop.

There is no difference in processing of End.X behavior
indicated by the traceroute probe at an
IPv6 classic node and an SRv6-capable node. Similarly, both IPv6
classic 2001:db8:K:2:X31:: SID and SRv6-capable nodes may use the address of forwards the interface packet on which probe was received as the source address in the ICMPv6
response. ICMPv6 extensions defined in [RFC5837] can be used
link3 to
display information about the IP interface through N3.

o Node N3, which is a non-SRv6 capable node, performs the datagram
would have been forwarded had standard
IPv6 processing. Specifically, it been forwardable, and forwards the IP next
hop to which echo request based
on the datagram would have been forwarded, DA 2001:db8:K:4:X52:: in the IP interface
upon IPv6 header.

o Node N4, which a datagram arrived, the sub-IP component of is an IP
interface upon which a datagram arrived.

The IP address of SRv6-capable node, performs the interface on which standard SRH
processing. Specifically, it observes the traceroute probe was
received is useful. This information can also be used to verify if
SIDs 2001:db8:K:2:X31:: End.X behavior
(2001:db8:K:4:X52::) and forwards the packet on link10 towards N5.
If 2001:db8:K:4:X52:: are executed correctly
by N2 is a PSP SID, the penultimate node (Node N4)
does not, should not and N4, respectively. Specifically, cannot differentiate between the information displayed
for data
packets and OAM probes. Specifically, if 2001:db8:K:4:X52:: is a
PSP SID, node N4 executes the second hop contains SID like any other data packet with
DA = 2001:db8:K:4:X52:: and removes the incoming interface address
2001:db8:2:3:31:: SRH.

o The echo request packet at N3. This matches N5 arrives as an IPv6 packet with or
without an SRH. If N5 receives the expected interface
bound to End.X behavior 2001:db8:K:2:X31:: (link3). Similarly, the
information displayed for packet with SRH, it skips SRH
processing (SL=0). In either case, Node N5 performs the fourth hop contains standard
ICMPv6 processing on the incoming
interface address 2001:db8:4:5::52:: at N5. This matches echo request and responds with the
expected interface bound to the End.X behavior 2001:db8:K:4:X52::
(link10).

3.2.2. Traceroute echo
reply message to N1. The echo reply message is IP routed.

A.1.2. Pinging a SID

The classic traceroute ping mechanism described in the previous section above applies equally to traceroute a remote perform SID behavior, as
reachability check and to validate the SID is locally programmed at
the target node. This is explained using an example in the
following. The example uses traceroute ping to an END SID, as described in
[RFC8986], but the procedure is equally applicable to
tracerouting ping any other
SID behaviors.

Please note that traceroute to a SID is exemplified using UDP probes.
However, the procedure is equally applicable to other implementations
of traceroute mechanism. The UDP encoded message to traceroute a SID
would use the UDP ports assigned by IANA for "traceroute use".

Consider the example where the user wants to traceroute ping a remote SID
2001:db8:K:4::, via 2001:db8:K:2:X31::, from node N1. The traceroute
probe ICMPv6
echo request is processed at the individual nodes along the path as
follows:

o Node N1 initiates a traceroute probe an ICMPv6 ping packet with SRH as follows
(2001:db8:L:1::, 2001:db8:K:2:X31::) (2001:db8:K:4::,
2001:db8:K:2:X31::; SL=1; NH=UDP)(Traceroute probe). The first
traceroute probe is sent with hop-count value set to 1. The hop-
count value is incremented by 1 for each following traceroute
probes.

o When node N2 receives the packet with hop-count = 1, it processes
the hop-count expiry. Specifically, the node N2 responds with the
ICMPv6 message (Type: "Time Exceeded", Code: "Hop limit exceeded
in transit"). The ICMPv6 response is IP routed. NH=ICMPv6)(ICMPv6 Echo Request).

o When Node N2 receives the packet with hop-count > 1, it N2, which is an SRv6-capable node, performs the standard SRH
processing. Specifically, it executes the End.X behavior
indicated by the 2001:db8:K:2:X31:: SID on the traceroute
probe. echo request
packet. If 2001:db8:K:2:X31:: is a PSP SID, node N2 N4 executes the
SID like any other data packet with DA = 2001:db8:K:2:X31:: and
removes the SRH.

o When node N3, which is a non-SRv6 capable node, receives the
packet with hop-count = 1, it processes the hop-count expiry.
Specifically, the node N3 responds with the ICMPv6 message (Type:
"Time Exceeded", Code: "Hop limit exceeded in Transit"). The
ICMPv6 response is IP routed.

o When node Node N3, which is a non-SRv6 capable node, receives the
packet with hop-count > 1, it performs the standard
IPv6 processing. Specifically, it forwards the traceroute probe echo request based
on DA = 2001:db8:K:4:: in the IPv6 header.

o When node N4 receives the packet with DA set to the local SID
2001:db8:K:4::, packet, it processes the END SID. target SID
(2001:db8:K:4::).

o If the target SID (2001:db8:K:4::) is not locally instantiated and
does not represent a local interface, the packet is discarded. discarded

o If the target SID (2001:db8:K:4::) is locally instantiated or
represents a local interface, the node processes the upper layer
header. As part of the upper layer header processing node N4
responds with
respond to the ICMPv6 echo request message (Type: Destination unreachable,
Code: Port Unreachable). and responds with the
echo reply message. The ICMPv6 response echo reply message is IP routed.

A.2. Traceroute

The existing traceroute mechanisms, along the shortest path,
continues to work without any modification. Any IPv6 node (SRv6
capable or a non-SRv6 capable) can initiate, transit, and egress a
traceroute probe.

The following subsections outline some additional use cases of the
traceroute in the SRv6 networks.

A.2.1. Traceroute to an IPv6 Address via a Segment-list

If an SRv6-capable ingress node wants to traceroute to IPv6 address
via an arbitrary segment list <S1, S2, S3>, it needs to initiate a
traceroute probe with an SR header containing the SID list <S1, S2,
S3>. User issues a traceroute from node N1 to a loopback of node N5,
via segment list <2001:db8:K:2:X31::, 2001:db8:K:4:X52::>. The SID
behavior used in the example is End.X SID, as described in [RFC8986],
but the procedure is equally applicable to any other (transit) SID
type. Figure 4 displays a 3 contains sample traceroute output for this example. the traceroute request.

> traceroute 2001:db8:K:4:X52:: 2001:db8:L:5:: via segment-list 2001:db8:K:2:X31:: 2001:db8:K:2:X31::,
2001:db8:K:4:X52::

Tracing the route to SID 2001:db8:K:4:X52:: 2001:db8:L:5::
1 2001:db8:2:1:21:: 0.512 msec 0.425 msec 0.374 msec
DA: 2001:db8:K:2:X31::,
SRH:(2001:db8:K:4:X52::, 2001:db8:K:2:X31::; SL=1)
SRH:(2001:db8:L:5::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::, SL=2)
2 2001:db8:3:2:21:: 2001:db8:3:2:31:: 0.721 msec 0.810 msec 0.795 msec
DA: 2001:db8:K:4:X52::,
SRH:(2001:db8:K:4:X52::, 2001:db8:K:2:X31::; SL=0)
SRH:(2001:db8:L:5::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::, SL=1)
3 2001:db8:4:3:41:: 2001:db8:4:3::41:: 0.921 msec 0.816 msec 0.759 msec
DA: 2001:db8:K:4:X52::,
SRH:(2001:db8:K:4:X52::, 2001:db8:K:2:X31::; SL=0)

Figure
SRH:(2001:db8:L:5::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::, SL=1)
4 2001:db8:5:4::52:: 0.879 msec 0.916 msec 1.024 msec
DA: 2001:db8:L:5::

Figure 3 A sample traceroute output for hop-by-hop at an SRv6-capable node

In the sample traceroute to a SID

3.3. A Hybrid OAM Using O-flag

This section illustrates a hybrid OAM mechanism using output, the information displayed at each
hop is obtained using the O-flag.
Without loss contents of the generality, "Time Exceeded" or
"Destination Unreachable" ICMPv6 responses. These ICMPv6 responses
are IP routed.

In the illustration assumes N100 sample traceroute output, the information for link3 is
returned by N3, which is a
centralized controller.

The illustration non-SRv6 capable node. Nonetheless, the
ingress node is different than able to display SR header contents as the In-situ OAM defined in [I.D-
draft-ietf-ippm-ioam-data]. packet
travels through the non-SRv6 capable node. This is because In-situ OAM records
operational and telemetry information in the "Time
Exceeded Message" ICMPv6 message can contain as much of the invoking
packet as possible without the ICMPv6 packet
traverses a path between two points in exceeding the network [I.D-draft-ietf-
ippm-ioam-data]. minimum
IPv6 MTU [RFC4443]. The illustration in this subsection does not
require the recording of OAM data SR header is included in these ICMPv6
messages initiated by the packet.

The illustration does non-SRv6 capable transit nodes that are not assume any formats for exporting the data
elements or
running SRv6 software. Specifically, a node generating ICMPv6
message containing a copy of the data elements that invoking packet does not need to be exported. The
illustration assumes system clocks among all nodes
understand the extension header(s) in the SR domain
are synchronized.

Consider invoking packet.

The segment list information returned for the example where first hop is returned
by N2, which is an SRv6-capable node. Just like for the user wants to monitor sampled IPv4 VPN
999 traffic going from CE1 to CE2 via a low latency SR policy P
installed at Node N1. To exercise a low latency path, second hop,
the ingress node is able to display SR Policy
P forces header contents for the packet via segments 2001:db8:K:2:X31:: and
2001:db8:K:4:X52::. The VPN SID at N7 associated with VPN 999 is
2001:db8:K:7:DT999::. 2001:db8:K:7:DT999:: first
hop.

There is a USP SID. N1, N4,
and N7 are capable of no difference in processing O-flag but N2 is not capable of
processing O-flag. N100 is the centralized controller traceroute probe at an
SRv6-capable and a non-SRv6 capable of
processing node. Similarly, both
SRv6-capable and correlating the copy of the packets sent from non-SRv6 capable nodes
N1, N4, and N7. N100 is aware of O-flag processing capabilities.
Controller N100 with may use the help from nodes N1, N4, N7 and implements a
hybrid OAM mechanism using address of the O-flag
interface on which probe was received as follows:

o A packet P1:(IPv4 header)(payload) is sent from CE1 to Node N1.

o Node N1 steers the packet P1 through source address in the Policy P. Based on a
local configuration, Node N1 also implements logic to sample
traffic steered through policy P for hybrid OAM purposes.
Specification for
ICMPv6 response. ICMPv6 extensions defined in [RFC5837] can be used
to display information about the sampling logic is beyond IP interface through which the scope of this
document. Consider
datagram would have been forwarded had it been forwardable, and the case where packet P1 is classified as a
packet
IP next hop to be monitored via the hybrid OAM. Node N1 sets O-flag
during which the encapsulation required by policy P. As part of setting datagram would have been forwarded, the O-flag, node N1 also sends IP
interface upon which a timestamped copy of datagram arrived, the packet
P1: (2001:db8:L:1::, 2001:db8:K:2:X31::) (2001:db8:K:7:DT999::,
2001:db8:K:4:X52::, 2001:db8:K:2:X31::; SL=2; O-flag=1;
NH=IPv4)(IPv4 header)(payload) to sub-IP component of an
IP interface upon which a local OAM process. datagram arrived.

The local
OAM process sends a full or partial copy IP address of the packet P1 to the
controller N100. The OAM process includes interface on which the recorded timestamp,
additional OAM traceroute probe was
received is useful. This information like incoming can also be used to verify if
SIDs 2001:db8:K:2:X31:: and outgoing interface,
etc. along with any applicable metadata. Node N1 forwards 2001:db8:K:4:X52:: are executed correctly
by N2 and N4, respectively. Specifically, the
original packet towards information displayed
for the next segment 2001:db8:K:2:X31::.

o When node N2 receives second hop contains the packet incoming interface address
2001:db8:2:3:31:: at N3. This matches with O-flag set, it ignores the
O-flag. This is because node N2 is not capable of processing expected interface
bound to End.X behavior 2001:db8:K:2:X31:: (link3). Similarly, the
O-flag. Node N2 performs
information displayed for the standard SRv6 SID and SRH
processing. Specifically, it executes fourth hop contains the incoming
interface address 2001:db8:4:5::52:: at N5. This matches with the
expected interface bound to the End.X behavior
indicated by 2001:db8:K:4:X52::
(link10).

A.2.2. Traceroute to a SID

The mechanism to traceroute an IPv6 Address via a Segment-list
described in the 2001:db8:K:2:X31:: previous section applies equally to traceroute a
remote SID behavior, as explained using an example in the following.
The example uses traceroute to an END SID, as described in [RFC8986]
and forwards [RFC8986],
but the packet P1 (2001:db8:L:1::, 2001:db8:K:4:X52::)
(2001:db8:K:7:DT999::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::;
SL=1; O-flag=1; NH=IPv4)(IPv4 header)(payload) over link 3 towards
Node N3.

o When node N3, which procedure is equally applicable to tracerouting any other SID
behaviors.

Please note that traceroute to a non-SRv6 capable node, receives SID is exemplified using UDP probes.
However, the
packet P1 , it performs procedure is equally applicable to other implementations
of traceroute mechanism. The UDP encoded message to traceroute a SID
would use the standard IPv6 processing.
Specifically, it forwards UDP ports assigned by IANA for "traceroute use".

Consider the packet P1 based on DA
2001:db8:K:4:X52:: in example where the IPv6 header.

o When user wants to traceroute a remote SID
2001:db8:K:4::, via 2001:db8:K:2:X31::, from node N4 receives N1. The traceroute
probe is processed at the individual nodes along the path as follows:

o Node N1 initiates a traceroute probe packet P1 as follows
(2001:db8:L:1::,
2001:db8:K:4:X52::) (2001:db8:K:7:DT999::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::) (2001:db8:K:4::,
2001:db8:K:2:X31::; SL=1; O-flag=1; NH=IPv4)(IPv4
header)(payload), it processes the O-flag. As part of processing
the O-flag, it sends a timestamped copy of the packet NH=UDP)(Traceroute probe). The first
traceroute probe is sent with hop-count value set to a local
OAM process. Based on a local configuration, the local OAM
process sends a full or partial copy of 1. The hop-
count value is incremented by 1 for each following traceroute
probes.

o When node N2 receives the packet P1 to with hop-count = 1, it processes
the
controller N100. The OAM process includes hop-count expiry. Specifically, the recorded timestamp,
additional OAM information like incoming and outgoing interface,
etc. along node N2 responds with any applicable metadata. the
ICMPv6 message (Type: "Time Exceeded", Code: "Hop limit exceeded
in transit"). The ICMPv6 response is IP routed.

o When Node N4 N2 receives the packet with hop-count > 1, it performs
the standard SRv6 SID and SRH processing on the original packet P1. processing. Specifically, it executes the End.X
behavior indicated by the
2001:db8:K:4:X52:: 2001:db8:K:2:X31:: SID and forwards on the traceroute
probe. If 2001:db8:K:2:X31:: is a PSP SID, node N2 executes the
SID like any other data packet P1 (2001:db8:L:1::,
2001:db8:K:7:DT999::) (2001:db8:K:7:DT999::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::; SL=0; O-flag=1; NH=IPv4)(IPv4 header)(payload)
over link 10 towards Node N5. with DA = 2001:db8:K:2:X31:: and
removes the SRH.

o When node N5, N3, which is a non-SRv6 capable node, receives the
packet P1, with hop-count = 1, it performs processes the standard IPv6 processing. hop-count expiry.
Specifically, it forwards the packet based on DA
2001:db8:K:7:DT999:: in node N3 responds with the IPv6 header. ICMPv6 message (Type:
"Time Exceeded", Code: "Hop limit exceeded in Transit"). The
ICMPv6 response is IP routed.

o When node N7 receives the packet P1 (2001:db8:L:1::,
2001:db8:K:7:DT999::) (2001:db8:K:7:DT999::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::; SL=0; O-flag=1; NH=IPv4)(IPv4
header)(payload), it processes the O-flag. As part of processing
the O-flag, it sends a timestamped copy of the packet to a local
OAM process. The local OAM process sends N3, which is a full or partial copy
of non-SRv6 capable node, receives the
packet P1 to the controller N100. The OAM process includes
the recorded timestamp, additional OAM information like incoming
and outgoing interface, etc. along with any applicable metadata.
Node N7 hop-count > 1, it performs the standard SRv6 SID and SRH processing on the
original packet P1. IPv6
processing. Specifically, it executes the VPN SID
indicated by forwards the 2001:db8:K:7:DT999:: SID and traceroute probe based
on lookup DA 2001:db8:K:4:: in
table 100 forwards the packet P1 (IPv4 header)(payload) towards CE
2. IPv6 header.

o The controller N100 processes and correlates the copy of the
packets sent from nodes N1, When node N4 and N7 to find segment-by-segment
delays and provide other hybrid OAM information related to receives the packet
P1. For segment-by-segment delay computation, with DA set to the local SID
2001:db8:K:4::, it is assumed that
clock are synchronized time across processes the SR domain. END SID.

o The process continues for any other sampled packets.

3.4. Monitoring of SRv6 Paths

In the recent past, network operators demonstrated interest in
performing network OAM functions in a centralized manner. [RFC8403]
describes such a centralized OAM mechanism. Specifically, If the
document describes a procedure that can be used to perform path
continuity check between any nodes within an SR domain from target SID (2001:db8:K:4::) is not locally instantiated and
does not represent a
centralized monitoring system. However, the document focuses on SR
networks with MPLS data plane. This document describes how local interface, the
concept can be used to perform path monitoring in an SRv6 network
from a centralized controller.

In packet is discarded.

o If the reference topology in Figure 1, N100 uses an IGP protocol like
OSPF target SID (2001:db8:K:4::) is locally instantiated or IS-IS to get the topology view within the IGP domain. N100
can also use BGP-LS to get
represents a local interface, the complete view of an inter-domain
topology. The controller leverages node processes the visibility upper layer
header. As part of the topology to
monitor the paths between upper layer header processing node N4
responds with the various endpoints. ICMPv6 message (Type: Destination unreachable,
Code: Port Unreachable). The controller N100 advertises an END SID [RFC8986]
2001:db8:K:100:1::. To monitor any arbitrary SRv6 paths, ICMPv6 response is IP routed.

Figure 4 displays a sample traceroute output for this example.

> traceroute 2001:db8:K:4:X52:: via segment-list 2001:db8:K:2:X31::

Tracing the
controller can create route to SID 2001:db8:K:4:X52::
1 2001:db8:2:1:21:: 0.512 msec 0.425 msec 0.374 msec
DA: 2001:db8:K:2:X31::,
SRH:(2001:db8:K:4:X52::, 2001:db8:K:2:X31::; SL=1)
2 2001:db8:3:2:21:: 0.721 msec 0.810 msec 0.795 msec
DA: 2001:db8:K:4:X52::,
SRH:(2001:db8:K:4:X52::, 2001:db8:K:2:X31::; SL=0)
3 2001:db8:4:3:41:: 0.921 msec 0.816 msec 0.759 msec
DA: 2001:db8:K:4:X52::,
SRH:(2001:db8:K:4:X52::, 2001:db8:K:2:X31::; SL=0)

Figure 4 A sample output for hop-by-hop traceroute to a loopback probe that originates and terminates
on Node N100. To distinguish between SID

A.3. A Hybrid OAM Using O-flag

This section illustrates a failure in hybrid OAM mechanism using the monitored path
and the O-flag.
Without loss of connectivity between the controller and the network, Node
N100 runs a suitable mechanism to monitor its connectivity to generality, the
monitored network.

The loopback probes are exemplified using an example where controller illustration assumes N100 needs to verify is a segment list <2001:db8:K:2:X31::,
2001:db8:K:4:X52::>:

o N100 generates an OAM packet (2001:db8:L:100::,
2001:db8:K:2:X31::)(2001:db8:K:100:1::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::, SL=2)(OAM Payload).
centralized controller.

The controller routes the
probe packet towards the first segment, which illustration is
2001:db8:K:2:X31::.

o Node N2 executes the End.X behavior indicated by different than the
2001:db8:K:2:X31:: SID In-situ OAM defined in [I.D-
draft-ietf-ippm-ioam-data]. This is because In-situ OAM records
operational and forwards telemetry information in the packet (2001:db8:L:100::,
2001:db8:K:4:X52::)(2001:db8:K:100:1::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::, SL=1)(OAM Payload) on link3 to N3.

o Node N3, which is a non-SRv6 capable node, performs the standard
IPv6 processing. Specifically, it forwards as the packet based on
traverses a path between two points in the DA 2001:db8:K:4:X52:: network [I.D-draft-ietf-
ippm-ioam-data]. The illustration in this subsection does not
require the IPv6 header.

o Node N4 executes recording of OAM data in the End.X behavior indicated by packet.

The illustration does not assume any formats for exporting the
2001:db8:K:4:X52:: SID and forwards data
elements or the packet (2001:db8:L:100::,
2001:db8:K:100:1::)(2001:db8:K:100:1::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::, SL=0)(OAM Payload) on link10 data elements that need to N5.

o be exported. The
illustration assumes system clocks among all nodes in the SR domain
are synchronized.

Consider the example where the user wants to monitor sampled IPv4 VPN
999 traffic going from CE1 to CE2 via a low latency SR policy P
installed at Node N5, which is N1. To exercise a non-SRv6 capable node, performs low latency path, the standard
IPv6 processing. Specifically, it forwards SR Policy
P forces the packet based on
the DA 2001:db8:K:100:1:: in the IPv6 header.

o Node via segments 2001:db8:K:2:X31:: and
2001:db8:K:4:X52::. The VPN SID at N7 associated with VPN 999 is
2001:db8:K:7:DT999::. 2001:db8:K:7:DT999:: is a USP SID. N1, N4,
and N7 are capable of processing O-flag but N2 is not capable of
processing O-flag. N100 executes is the standard SRv6 END behavior. It
decapsulates centralized controller capable of
processing and correlating the header copy of the packets sent from nodes
N1, N4, and consume N7. N100 is aware of O-flag processing capabilities.
Controller N100 with the probe for help from nodes N1, N4, N7 and implements a
hybrid OAM processing.
The information in mechanism using the OAM payload O-flag as follows:

o A packet P1:(IPv4 header)(payload) is used sent from CE1 to detect any missing
probes, round trip delay, etc.

The OAM payload type or Node N1.

o Node N1 steers the information carried in packet P1 through the OAM probe is Policy P. Based on a
local implementation decision at configuration, Node N1 also implements logic to sample
traffic steered through policy P for hybrid OAM purposes.
Specification for the controller and sampling logic is outside beyond the scope of this
document.

4. Implementation Status

This section is to be removed prior to publishing as an RFC.

See [I-D.matsushima-spring-srv6-deployment-status] for updated
deployment and interoperability reports.

5. Security Considerations

[RFC8754] defines the notion of an SR domain and use of SRH within
the SR domain. The use of OAM procedures described in this document
is restricted to an SR domain. For example, similar to Consider the SID
manipulation, O-flag manipulation case where packet P1 is not considered classified as a threat
within
packet to be monitored via the SR domain. Procedures for securing an SR domain are
defined hybrid OAM. Node N1 sets O-flag
during the section 5.1 and section 7 of [RFC8754]. encapsulation required by policy P. As noted in section 7.1 part of [RFC8754], compromised nodes within setting
the SR
domain may mount attacks. The O-flag may be set by an attacking O-flag, node
attempting N1 also sends a denial-of-service attack on timestamped copy of the packet
P1: (2001:db8:L:1::, 2001:db8:K:2:X31::) (2001:db8:K:7:DT999::,
2001:db8:K:4:X52::, 2001:db8:K:2:X31::; SL=2; O-flag=1;
NH=IPv4)(IPv4 header)(payload) to a local OAM process. The local
OAM process sends a full or partial copy of the packet P1 to the
controller N100. The OAM process at includes the recorded timestamp,
additional OAM information like incoming and outgoing interface,
etc. along with any applicable metadata. Node N1 forwards the
original packet towards the next segment endpoint node. An implementation correctly implementing 2001:db8:K:2:X31::.

o When node N2 receives the
rate limiting in section 2.1.1 packet with O-flag set, it ignores the
O-flag. This is because node N2 is not susceptible to that denial-of-
service attack. Additionally, capable of processing the
O-flag. Node N2 performs the standard SRv6 SID and SRH Flags are protected
processing. Specifically, it executes the End.X behavior
indicated by the HMAC
TLV, 2001:db8:K:2:X31:: SID as described in Section 2.1.2.1 of [RFC8754]. Once an HMAC [RFC8986]
and forwards the packet P1 (2001:db8:L:1::, 2001:db8:K:4:X52::)
(2001:db8:K:7:DT999::, 2001:db8:K:4:X52::, 2001:db8:K:2:X31::;
SL=1; O-flag=1; NH=IPv4)(IPv4 header)(payload) over link 3 towards
Node N3.

o When node N3, which is
generated for a segment list with non-SRv6 capable node, receives the O-flag set,
packet P1 , it can be used for
an arbitrary amount of traffic using that segment list with O-flag
set.

The security properties of performs the channel used to send exported packets
marked by standard IPv6 processing.

Specifically, it forwards the O-flag will depend packet P1 based on DA
2001:db8:K:4:X52:: in the specific OAM IPv6 header.

o When node N4 receives the packet P1 (2001:db8:L:1::,
2001:db8:K:4:X52::) (2001:db8:K:7:DT999::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::; SL=1; O-flag=1; NH=IPv4)(IPv4
header)(payload), it processes used.
An on-path attacker able the O-flag. As part of processing
the O-flag, it sends a timestamped copy of the packet to observe this a local
OAM channel could conduct
traffic analysis, or potentially eavesdropping (depending process. Based on a local configuration, the local OAM
configuration),
process sends a full or partial copy of this telemetry for the entire SR domain from such
a vantage point.

This document does not impose any additional security challenges packet P1 to
be considered beyond security threats described in [RFC4884],
[RFC4443], [RFC0792], [RFC8754] and [RFC8986].

6. Privacy Considerations the
controller N100. The per-packet marking capabilities of OAM process includes the O-flag provides a granular
mechanism to collect telemetry. When this collection is deployed by
an operator recorded timestamp,
additional OAM information like incoming and outgoing interface,
etc. along with knowledge any applicable metadata. Node N4 performs the
standard SRv6 SID and consent of SRH processing on the users, original packet P1.
Specifically, it will enable a
variety of diagnostics and monitoring to support executes the OAM and security
operations use cases needed for resilient network operations.
However, this collection mechanism will also provide an explicit
protocol mechanism to operators for surveillance End.X behavior indicated by the
2001:db8:K:4:X52:: SID and pervasive
monitoring use cases done contrary to forwards the user's consent.

7. IANA Considerations

This document requests that IANA allocate packet P1 (2001:db8:L:1::,
2001:db8:K:7:DT999::) (2001:db8:K:7:DT999::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::; SL=0; O-flag=1; NH=IPv4)(IPv4 header)(payload)
over link 10 towards Node N5.

o When node N5, which is a non-SRv6 capable node, receives the following registration
packet P1, it performs the standard IPv6 processing.
Specifically, it forwards the packet based on DA
2001:db8:K:7:DT999:: in the "Segment Routing Header Flags" sub-registry for IPv6 header.

8. Acknowledgements

The authors would like packet to thank Joel M. Halpern, Greg Mirsky, Bob
Hinden, Loa Andersson, Gaurav Naik, Ketan Talaulikar and Haoyu Song
for their review comments.

9. Contributors a local
OAM process. The following people have contributed to this document:

Robert Raszuk
Bloomberg LP
Email: robert@raszuk.net

John Leddy
Individual
Email: john@leddy.net

Gaurav Dawra
LinkedIn
Email: gdawra.ietf@gmail.com

Bart Peirens
Proximus
Email: bart.peirens@proximus.com

Nagendra Kumar
Cisco Systems, Inc.
Email: naikumar@cisco.com

Carlos Pignataro
Cisco Systems, Inc.
Email: cpignata@cisco.com

Rakesh Gandhi
Cisco Systems, Inc.
Canada
Email: rgandhi@cisco.com
Frank Brockners
Cisco Systems, Inc.
Germany
Email: fbrockne@cisco.com

Darren Dukes
Cisco Systems, Inc.
Email: ddukes@cisco.com

Cheng Li
Huawei
Email: chengli13@huawei.com

Faisal Iqbal
Individual
Email: faisal.ietf@gmail.com

10. References

10.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.

[RFC8174] Leiba, B., "Ambiguity local OAM process sends a full or partial copy
of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.

[RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J.,
Matsushima, S., the packet P1 to the controller N100. The OAM process includes
the recorded timestamp, additional OAM information like incoming
and D. Voyer, "IPv6 Segment Routing Header
(SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020,
<https://www.rfc-editor.org/info/rfc8754>.

[RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,
D., Matsushima, S., outgoing interface, etc. along with any applicable metadata.
Node N7 performs the standard SRv6 SID and Z. Li, "Segment Routing over IPv6
(SRv6) Network Programming", RFC 8986,
DOI 10.17487/RFC8986, February 2021,
<https://www.rfc-editor.org/info/rfc8986>.

10.2. Informative References

[I-D.gandhi-spring-stamp-srpm]
Gandhi, R., Filsfils, C., Voyer, D., Chen, M., Janssens,
B., SRH processing on the
original packet P1. Specifically, it executes the VPN SID
indicated by the 2001:db8:K:7:DT999:: SID and R. Foote, "Performance Measurement Using Simple
TWAMP (STAMP) for Segment Routing Networks", draft-gandhi-
spring-stamp-srpm-07 (work based on lookup in progress), July 2021.

[I-D.ietf-ippm-ioam-data]
Brockners, F., Bhandari, S.,
table 100 forwards the packet P1 (IPv4 header)(payload) towards CE
2.

o The controller N100 processes and T. Mizrahi, "Data Fields
for In-situ OAM", draft-ietf-ippm-ioam-data-11 (work in
progress), November 2020.

[I-D.matsushima-spring-srv6-deployment-status]
Matsushima, S., Filsfils, C., Ali, Z., Li, Z., correlates the copy of the
packets sent from nodes N1, N4 and K.
Rajaraman, "SRv6 Implementation N7 to find segment-by-segment
delays and Deployment Status",
draft-matsushima-spring-srv6-deployment-status-11 (work provide other hybrid OAM information related to packet
P1. For segment-by-segment delay computation, it is assumed that
clock are synchronized time across the SR domain.

o The process continues for any other sampled packets.

A.4. Monitoring of SRv6 Paths

In the recent past, network operators demonstrated interest in
performing network OAM functions in a centralized manner. [RFC8403]
describes such a centralized OAM mechanism. Specifically, the
document describes a procedure that can be used to perform path
continuity check between any nodes within an SR domain from a
centralized monitoring system. However, the document focuses on SR
networks with MPLS data plane. This document describes how the
concept can be used to perform path monitoring in
progress), February 2021.

[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, DOI 10.17487/RFC0792, September 1981,
<https://www.rfc-editor.org/info/rfc792>.

[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
DOI 10.17487/RFC2328, April 1998,
<https://www.rfc-editor.org/info/rfc2328>.

[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
Control Message Protocol (ICMPv6) for an SRv6 network
from a centralized controller.

In the Internet
Protocol Version 6 (IPv6) Specification", STD 89,
RFC 4443, DOI 10.17487/RFC4443, March 2006,
<https://www.rfc-editor.org/info/rfc4443>.

[RFC4884] Bonica, R., Gan, D., Tappan, D., and C. Pignataro,
"Extended ICMP reference topology in Figure 1, N100 uses an IGP protocol like
OSPF or IS-IS to Support Multi-Part Messages", RFC 4884,
DOI 10.17487/RFC4884, April 2007,
<https://www.rfc-editor.org/info/rfc4884>.

[RFC5476] Claise, B., Ed., Johnson, A., and J. Quittek, "Packet
Sampling (PSAMP) Protocol Specifications", RFC 5476,
DOI 10.17487/RFC5476, March 2009,
<https://www.rfc-editor.org/info/rfc5476>.

[RFC5880] Katz, D. get the topology view within the IGP domain. N100
can also use BGP-LS to get the complete view of an inter-domain
topology. The controller leverages the visibility of the topology to
monitor the paths between the various endpoints.

The controller N100 advertises an END SID [RFC8986]
2001:db8:K:100:1::. To monitor any arbitrary SRv6 paths, the
controller can create a loopback probe that originates and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>.

[RFC7011] Claise, B., Ed., Trammell, B., Ed., terminates
on Node N100. To distinguish between a failure in the monitored path
and P. Aitken,
"Specification loss of connectivity between the IP Flow Information Export (IPFIX)
Protocol for the Exchange of Flow Information", STD 77,
RFC 7011, DOI 10.17487/RFC7011, September 2013,
<https://www.rfc-editor.org/info/rfc7011>.

[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model
for IP Flow Information Export (IPFIX)", RFC 7012,
DOI 10.17487/RFC7012, September 2013,
<https://www.rfc-editor.org/info/rfc7012>.

[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
May 2016, <https://www.rfc-editor.org/info/rfc7799>.

[RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., controller and S.
Pallagatti, "Seamless Bidirectional Forwarding Detection
(S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016,
<https://www.rfc-editor.org/info/rfc7880>.

[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., the network, Node
N100 runs a suitable mechanism to monitor its connectivity to the
monitored network.

The loopback probes are exemplified using an example where controller
N100 needs to verify a segment list <2001:db8:K:2:X31::,
2001:db8:K:4:X52::>:

o N100 generates an OAM packet (2001:db8:L:100::,
2001:db8:K:2:X31::)(2001:db8:K:100:1::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::, SL=2)(OAM Payload). The controller routes the
probe packet towards the first segment, which is
2001:db8:K:2:X31::.

o Node N2 executes the End.X behavior indicated by the
2001:db8:K:2:X31:: SID and R. Shakir, "Segment
Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
July 2018, <https://www.rfc-editor.org/info/rfc8402>.

[RFC8403] Geib, R., Ed., Filsfils, C., Pignataro, C., Ed., forwards the packet (2001:db8:L:100::,
2001:db8:K:4:X52::)(2001:db8:K:100:1::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::, SL=1)(OAM Payload) on link3 to N3.

o Node N3, which is a non-SRv6 capable node, performs the standard
IPv6 processing. Specifically, it forwards the packet based on
the DA 2001:db8:K:4:X52:: in the IPv6 header.

o Node N4 executes the End.X behavior indicated by the
2001:db8:K:4:X52:: SID and N.
Kumar, "A Scalable forwards the packet (2001:db8:L:100::,
2001:db8:K:100:1::)(2001:db8:K:100:1::, 2001:db8:K:4:X52::,
2001:db8:K:2:X31::, SL=0)(OAM Payload) on link10 to N5.

o Node N5, which is a non-SRv6 capable node, performs the standard
IPv6 processing. Specifically, it forwards the packet based on
the DA 2001:db8:K:100:1:: in the IPv6 header.

o Node N100 executes the standard SRv6 END behavior. It
decapsulates the header and Topology-Aware MPLS Data-Plane
Monitoring System", RFC 8403, DOI 10.17487/RFC8403, July
2018, <https://www.rfc-editor.org/info/rfc8403>.

[RFC8571] Ginsberg, L., Ed., Previdi, S., Wu, Q., Tantsura, J., consume the probe for OAM processing.
The information in the OAM payload is used to detect any missing
probes, round trip delay, etc.

The OAM payload type or the information carried in the OAM probe is a
local implementation decision at the controller and
C. Filsfils, "BGP - Link State (BGP-LS) Advertisement is outside the
scope of
IGP Traffic Engineering Performance Metric Extensions",
RFC 8571, DOI 10.17487/RFC8571, March 2019,
<https://www.rfc-editor.org/info/rfc8571>. this document.

Appendix B. Acknowledgements

The authors would like to thank Joel M. Halpern, Greg Mirsky, Bob
Hinden, Loa Andersson, Gaurav Naik, Ketan Talaulikar and Haoyu Song
for their review comments.

Appendix C. Contributors

The following people have contributed to this document:

Robert Raszuk
Bloomberg LP
Email: robert@raszuk.net

John Leddy
Individual
Email: john@leddy.net

Gaurav Dawra
LinkedIn
Email: gdawra.ietf@gmail.com

Bart Peirens
Proximus
Email: bart.peirens@proximus.com
Nagendra Kumar
Cisco Systems, Inc.
Email: naikumar@cisco.com

Carlos Pignataro
Cisco Systems, Inc.
Email: cpignata@cisco.com

Rakesh Gandhi
Cisco Systems, Inc.
Canada
Email: rgandhi@cisco.com

Frank Brockners
Cisco Systems, Inc.
Germany
Email: fbrockne@cisco.com

Darren Dukes
Cisco Systems, Inc.
Email: ddukes@cisco.com

Cheng Li
Huawei
Email: chengli13@huawei.com

Faisal Iqbal
Individual
Email: faisal.ietf@gmail.com

Authors' Addresses

Zafar Ali
Cisco Systems

Email: zali@cisco.com
Clarence Filsfils
Cisco Systems

Email: cfilsfil@cisco.com

Satoru Matsushima
Softbank

Email: satoru.matsushima@g.softbank.co.jp

Daniel Voyer
Bell Canada

Email: daniel.voyer@bell.ca

Mach Chen
Huawei

Email: mach.chen@huawei.com