BPM G. Fioccola Internet-Draft K. Zhu Intended status: Informational T. Zhou Expires: 19 May 2027 Huawei T. Graf Swisscom L. Zhang China Mobile 15 November 2026 An Alternate Marking Deployment Framework draft-ietf-bpm-alt-mark-deployment-01 Abstract This document provides a framework for Alternate Marking deployment and includes considerations and guidance for the deployment of the Alternate Marking methodology. 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 19 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. Fioccola, et al. Expires 19 May 2027 [Page 1] Internet-Draft alternate-marking-deployment November 2026 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2. AltMark Deployment Domain . . . . . . . . . . . . . . . . . . 4 3. AltMark Measurement Nodes . . . . . . . . . . . . . . . . . . 5 4. Type of Measurements . . . . . . . . . . . . . . . . . . . . 7 5. AltMark Manageability Framework . . . . . . . . . . . . . . . 8 6. Node Capabilities . . . . . . . . . . . . . . . . . . . . . . 9 7. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 10 7.1. YANG Data Model . . . . . . . . . . . . . . . . . . . . . 10 7.2. PCEP and BGP . . . . . . . . . . . . . . . . . . . . . . 11 8. Data Collection . . . . . . . . . . . . . . . . . . . . . . . 11 8.1. IPFIX . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.2. YANG-Push . . . . . . . . . . . . . . . . . . . . . . . . 12 8.3. Hybrid Two-Step . . . . . . . . . . . . . . . . . . . . . 12 9. Encapsulations . . . . . . . . . . . . . . . . . . . . . . . 12 9.1. IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9.2. SRv6 . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9.3. BIER . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9.4. MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9.5. SFC . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9.6. NVO3 . . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. Operational Considerations . . . . . . . . . . . . . . . . . 14 10.1. Measurement Domain Considerations . . . . . . . . . . . 14 10.2. Synchronization and Timing Considerations . . . . . . . 15 10.3. Configuration and Data Export Considerations . . . . . . 15 11. Security Considerations . . . . . . . . . . . . . . . . . . . 16 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 15.1. Normative References . . . . . . . . . . . . . . . . . . 17 15.2. Informative References . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 Fioccola, et al. Expires 19 May 2027 [Page 2] Internet-Draft alternate-marking-deployment November 2026 1. Introduction The Alternate Marking [RFC9341] and Clustered Alternate Marking [RFC9342] define the Alternate Marking technique that is a hybrid performance measurement method, per [RFC7799] classification of measurement methods. This method is based on marking consecutive batches of packets and it can be used to measure packet loss, latency, and jitter on live traffic. The first experiments on Alternate-Marking were described in [RFC8321] and [RFC8889]. According to the definitions of [RFC7799], the Alternate-Marking Method can be classified as Hybrid Type I. Indeed, Alternate Marking can be implemented by using reserved bits in the protocol header, and the change in value of these marking bits at the source node is formally considered a modification of the stream of interest. This document complements [RFC9341] and [RFC9342] as it explains the mechanisms that can be used to manage and deploy the method. This document can be considered as the base document to deploy the Alternate Marking Method. There are three complementary documents to be considered for the manageability aspects: [I-D.ietf-bpm-alt-mark-yang], which defines a YANG Data Model for the Alternate Marking Method for configuration; [I-D.ietf-bpm-on-path-telemetry-yang], which defines an On-Path Telemetry YANG Data Model for notification; [I-D.ietf-opsawg-ipfix-alt-mark], which defines IPFIX Alternate- Marking Information Elements. 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. Terminology Abbreviations used in this document: AltMark: Alternate-Marking Fioccola, et al. Expires 19 May 2027 [Page 3] Internet-Draft alternate-marking-deployment November 2026 NMS: Network Management System IPv6: Internet Protocol version 6 SRv6: Segment Routing over IPv6 data plane BIER: Bit Index Explicit Replication MPLS: Multi-Protocol Label Switching SFC: Service Function Chaining NVO3: Network Virtualization Overlays IPFIX: IP Flow Information Export PCEP: Path Computation Element Communication Protocol 2. AltMark Deployment Domain When deploying the Alternate Marking Method, it MUST be deployed in a controlled domain for security and compatibility reasons. In this regard, [RFC8799] reports further examples of specific limited domain solutions. It is not common that the user traffic originates and terminates within the controlled domain. For this reason, it will typically only be applicable in an overlay network, where user traffic is encapsulated at one domain border, decapsulated at the other domain border and the encapsulation incorporates the relevant extension header for Alternate Marking. This requirement also implies that a border node MUST be able to filter packets that carry Alternate Marking data and are entering or leaving the controlled domain. Also, since the Alternate Marking could be implemented at different layers filtering needs to be supported in all the interested layers. A controlled domain is a managed network where it is required to select, monitor and control the access to the network by enforcing policies at the domain boundaries in order to discard undesired external packets entering the domain and check the internal packets leaving the domain. It does not necessarily mean that a controlled domain is a single administrative domain or a single organization. A controlled domain can correspond to a single administrative domain or can be composed by multiple administrative domains under a defined network management. Indeed, some scenarios may imply that the Alternate Marking Method involves more than one domain, but in these cases, it is RECOMMENDED that the multiple domains create a whole controlled domain while traversing the external domain by employing IPsec authentication and encryption or other VPN technology that Fioccola, et al. Expires 19 May 2027 [Page 4] Internet-Draft alternate-marking-deployment November 2026 provides full packet confidentiality and integrity protection. It must be possible to control the domain boundaries and eventually use specific precautions if the traffic traverse the Internet. Note that, if there is a trust relationship between different entities, the controlled domain can still be considered. The different entities just need to agree on how to manage it in terms of configuration and reporting. The Alternate Marking measurement domain can overlap with the controlled domain or may be a subset of the controlled domain. The typical scenarios for the application of the Alternate Marking Method depend on the controlled domain boundaries, in particular: * the user equipment can be the starting or ending node, only in case it is fully managed and if it belongs to the controlled domain. In this case the user generated packets contain the Alternate Marking data. But, in practice, this is not common due to the fact that the user equipment cannot be totally secured in the majority of cases. * the Customer Premises Equipment (CPE) or the Provider Edge (PE) routers are most likely to be the starting or ending nodes since they can be border routers of the controlled domain. For instance, the CPE, which connects the user's premises with the service provider's network, belongs to a controlled domain only if it is managed by the service provider and if additional security measures are taken to keep it trustworthy. Typically, a CPE or a PE can encapsulate a received packet in an outer header which contains the Alternate Marking data. They can also be able to filter and drop packets from outside of the domain with inconsistent fields to make effective the relevant security rules at the domain boundaries, for example, a simple security check can be to insert the Alternate Marking data if and only if the destination is within the controlled domain. 3. AltMark Measurement Nodes An Alternate-Marking Domain consists of marking nodes, unmarking nodes, and transit nodes. Fioccola, et al. Expires 19 May 2027 [Page 5] Internet-Draft alternate-marking-deployment November 2026 * A marking node, also referred to as encapsulating node, incorporates the AltMark Data Fields into packets in order to enable Alternate-Marking. If an Alternate-Marking method is enabled for a selected flow of the traffic, the encapsulating node is responsible for applying the AltMark methodology and, in particular, the marking of the selected flow and the reading of the initial timestamps and packet counters, according to the procedures defined in [RFC9341], [RFC9342], and in the relevant data plane extensions (Section 9). * A transit node supporting an AltMark methodology only reads AltMark Data Fields in order to take timestamps and packet counters according to the procedures defined in [RFC9341], [RFC9342], and in the relevant data plane extensions (Section 9). It is worth noting that the nodes on the path may be configured to support AltMark or not, and, therefore, the measurement can be done only for the nodes configured to support an AltMark methodology, while the others are simply not considered for the metrics. * An unmarking node, also referred to as decapsulating node, reads AltMark Data Fields in order to take final timestamps and packet counters and then removes any AltMark Data Fields from packets, according to the procedures defined in [RFC9341], [RFC9342], and in the relevant data plane extensions (Section 9). Capability Capability Capability Capability discovery, discovery, discovery, discovery, Configuration Configuration Configuration Configuration and and and and Export of Export of Export of Export of AltMark data AltMark data AltMark data AltMark data | | | | | | | | | | | | User +----+----+ +----+----+ +----+----+ +----+----+ packets |Marking | | Transit | | Transit | |Unmarking| -------->|Node |====>| Node A |====>| Node B |====>|Node |--> |(mark | | | | | |(unmark | | & read) | | (read) | | (read) | | & read) | +---------+ +---------+ +---------+ +---------+ Figure 1: Roles and tasks of the Alternate-Marking Nodes The previous figure also highlights a three-step sequence for each node: discovering its capabilities, configuring it to apply AltMark methods to the selected flows, and exporting the AltMark data. Further details are provided in Section 6, Section 7, and Section 8. Fioccola, et al. Expires 19 May 2027 [Page 6] Internet-Draft alternate-marking-deployment November 2026 4. Type of Measurements The methodology described in the previous sections can be applied to various performance measurement problems. The only requirement is to select and mark the flow to be monitored. In doing so, packets are batched by the sender, and each batch is alternately marked such that it can be easily recognized by the receiver. Either one or two flag bits might be available for marking in different deployments: 1. One flag: packet loss measurement MUST be done as described in Section 3.1 of [RFC9341], while delay measurement MUST be done according to the single-marking method described in Section 3.2.1 of [RFC9341]. Mean delay (Section 3.2.1.1 of [RFC9341]) MAY also be used but it could imply more computational load. 2. Two flags: packet loss measurement MUST be done as described in Section 3.1 of [RFC9341], while delay measurement MUST be done according to double-marking method Section 3.2.2 of [RFC9341]. In this case, single-marking MAY also be used in combination with double-marking and the two approaches provide slightly different pieces of information that can be combined to have a more robust data set. There are some operational guidelines to consider for the purpose of deciding to follow the recommendations above and use one or two flags: * The Alternate-Marking method utilizes specific flags in the outer packet header, so an important factor is the number of flags available for the implementation. Indeed, if there is only one flag available there is no other way, while if two flags are available the option with two flags is certainly more complete. * The duration of the Alternate-Marking period affects the frequency of the measurement and this is a parameter that can be decided on the basis of the required temporal sampling. However, it cannot be freely chosen, as explained in Section 5 of [RFC9341]. * The Alternate-Marking methodologies enable packet loss, delay, and delay variation calculation, but in accordance with the method used (e.g., single-marking or double-marking), there are different kinds of information that can be derived. For example, to get more statistics of extent data, the option with two flags is desirable. For this reason, the type of data needed in the specific scenario is an additional element to take into account. Fioccola, et al. Expires 19 May 2027 [Page 7] Internet-Draft alternate-marking-deployment November 2026 * The Alternate-Marking methods imply different computational load depending on the method employed. Therefore, the available computational resources on the measurement points can also influence the choice. As an example, mean delay calculation may require more processing and it may not be the best option to minimize the computational load. A deployment of the Alternate-Marking Method should also take into account how to handle and recognize marked and unmarked traffic. Since Alternate-Marking normally employs a marking field which is dedicated, reserved, and included in a protocol extension, the measurement points can learn whether the measurement is activated or not by checking if the specific extension is included or not within the packets. 5. AltMark Manageability Framework Figure 2 shows an overview of the Alternate-Marking Deployment Framework, in order to present a typical deployment scenario and how the methodology can be configured, monitored and analyzed. +----------------+ +---------------+ | | Network | | | Management | | | System |-+ +---------------+ | | | | +---------------+-------+-------+---------------+ | | | | | | | | | | | | User +----+----+ +----+----+ +----+----+ +----+----+ packets |Marking | | Transit | | Transit | |Unmarking| -------->|Node |====>| Node A |====>| Node B |====>|Node |--> +---------+ +---------+ +---------+ +---------+ Figure 2: A typical Alternate-Marking deployment scenario The manageability framework presupposes the application to a controlled domain, and, as mentioned in Section 11, techniques MUST be applied for securing the data plane, control plane, and management plane in the AltMark measurement domain. Fioccola, et al. Expires 19 May 2027 [Page 8] Internet-Draft alternate-marking-deployment November 2026 The NMS is the centralized controller that issues configurations to and collects data from the managed nodes. In fact, a controller can be deployed in an AltMark measurement domain to manage every node in the controlled domain, to discover the node capabilities, to provision the relevant configurations for the application of an AltMark method to the nodes and to get all the data for the relevant performance measurement computation. The next sections describe the fundamental operations for the manageability of the AltMark methods, which are: * Node capabilities discovery (Section 6), * Configuration and activation of the measurements (Section 7), * Data collection and measurement calculation (Section 8). Note that these operations could be done by a controller and they MUST be secured in order to ensure that a node is talking with an authorized controller. 6. Node Capabilities The Alternate-Marking Method does not require that all the nodes in the measurement domain support the methodology. The only active role is played by the marking and unmarking nodes. The transit nodes play a passive role since they could only read the marking fields if they support the methods, otherwise they are simply not considered for the measurements. For this reason, it is essential to know the capabilities of at least the marking and unmarking nodes, while the transit nodes may look at the marking fields in the packets if they support the method. In the case when a controller is deployed in the AltMark measurement domain, the controller is aware of the node capabilities, can control the encapsulation used for AltMark and also checks if the controlled domain is consistently configured. In the case when a controller is not deployed in the AltMark measurement domain, the marking node may discover the enabled AltMark capabilities at the transit and unmarking nodes, so that it can use the correct encapsulation and apply the supported method (e.g., single-marking or double-marking) according to the discovered capabilities. The marking node may use NETCONF/YANG or IGP to discover these AltMark capabilities. When NETCONF/YANG is used, the marking node needs to implement a NETCONF Client, and the transit and unmarking nodes need to implement a NETCONF Server. When IGP is used, the IGP and the AltMark measurement domain must have the same Fioccola, et al. Expires 19 May 2027 [Page 9] Internet-Draft alternate-marking-deployment November 2026 coverage. [I-D.ietf-idr-bgp-ifit-capabilities] could be used for capability advertisement in order to allow the marking node to know which AltMark measurements can be applied in data packets. 7. Configuration Several mechanisms can be used for configuration and, in particular, YANG-based management protocol, PCEP [RFC5440], and BGP [RFC4271]. These are needed to signal and configure the parameters to identify the flow to monitor both in case of point-to-point flow and multipoint-to-multipoint flow. Indeed, the selection of the identification fields directly affects the type of paths that the flow would follow in the network (e.g., a 5-tuple can usually be used to identify a monitored flow). For IPv6, the setting of the Flow Monitoring Identification (FlowMonID) is used to identify a flow, also in combination with other parameters, like source and destination addresses, as described in [RFC9343]. FlowMonID can be pseudo-randomly generated by the source node or assigned by the central controller. It can be algorithmically generated by the source node, which can set it pseudo-randomly with some chance of collision, but this approach cannot guarantee the uniqueness of FlowMonID since conflicts and collisions are possible. It is RECOMMENDED that the FlowMonID is assigned by the central controller. Indeed, since the controller knows the network topology, it can allocate the value properly to avoid or minimize ambiguity and guarantee uniqueness. Further details can be found in section 5.3 of [RFC9343]. Additionally, other parameters are essential for the activation of the AltMark methodology: the choice between end-to-end or hop-by-hop measurement, the choice between the methods with one flag or two flags and the duration of the Alternate-Marking period which affects the measurement frequency (longer the duration of the block, the less frequently the measurement can be taken). The next sections report the YANG Data Model and the use of PCEP/BGP for ALtMark configuration and activation. It is worth noting that they can be used alternatively or simultaneously depending on the deployments. 7.1. YANG Data Model A YANG data model can be used for the definition of the AltMark data sent over network management protocols such as the NETCONF and RESTCONF. They can be used for configuring Alternate-Marking in network nodes that support it. An example of an Alternate-Marking YANG data model is defined in [I-D.ietf-bpm-alt-mark-yang]. Fioccola, et al. Expires 19 May 2027 [Page 10] Internet-Draft alternate-marking-deployment November 2026 7.2. PCEP and BGP There are also other control plane mechanisms to advertise and activate AltMark capabilities, using PCEP and BGP: [I-D.ietf-idr-sr-policy-ifit], [I-D.ietf-pce-pcep-ifit], and [I-D.he-idr-bgp-flowspec-ifit]. 8. Data Collection Each packet marked for Alternate-Marking, as, for example, the AltMark IPv6 option type defined in Section 3.1 of [RFC9343] or the Segment Routing TLV Type as defined in Section 3.1 of [RFC9947] is counted or timestamped according to the method. The export of data can be done using the IPFIX or YANG push metering process depending which Network Telemetry [RFC9232] protocol is used to export the data. There are at least two options for the computation: 1. A centralized solution where the NMS acts as Collector. The loss and delay metrics are computed on the NMS by comparing the packet counts and timestamps at each AltMark period, according to the AltMark technique [RFC9341] [RFC9342]. 2. A distributed solution where the computation of loss and delay metrics can be done directly on the node. In this case, the relevant counters and timestamps must be available on the node and can be carried with the packet or can be transmitted by introducing a new protocol or by extending existing protocols. For example, according to [RFC9951], it is possible to export the delay performance metrics in IPFIX. Therefore, assuming we have the counter and timestamp information directly on the node, as enabled by [RFC9947], the delay can be computed on the router. When data are collected, packet counts and timestamps are reported to the collector, but a certain synchronization mechanism is required to ensure that the collected data is correlated properly. Therefore, the Period Number (PN) can be used to help to determine the packet counts related to the same block of markers, or the timestamps related to the same marked packet. The PN is generated each time a node reads the packet counts or timestamps, and is associated with each packet count and timestamp reported. Nodes are REQUIRED to be time-synchronized as described in [RFC9341] and [RFC9342]. The PN can be calculated by dividing the local time (when the counts or timestamps are read) by the interval of the marking time period and then rounding down to the nearest whole integer using the floor function. This calculation does not require strict time synchronization, since the synchronization required for AltMark to Fioccola, et al. Expires 19 May 2027 [Page 11] Internet-Draft alternate-marking-deployment November 2026 function is enough, and the PN value will be always the same on each node under these conditions. In addition, if the PN calculation is resource consuming for the node, it may also be calculated on the NMS since the timestamp information is available there. Note that, in addition to IPFIX, YANG-Push and Hybrid Two-Step, which are reported below, it is also possible to use gRPC, an open source Remote Procedure Call (RPC) framework for exporting telemetry data. The next sections report IPFIX and YANG-Push for data collection. It is worth noting that they can be used alternatively or simultaneously depending on the deployments. 8.1. IPFIX For IPFIX [RFC7011], new Information Elements (IEs) for FlowMonID, Loss and Delay flags are needed so that the data can be aggregated according to the Alternate-Marking Method. The new IEs to export Alternate Marking measurement data are specified in [I-D.ietf-opsawg-ipfix-alt-mark]. The IPFIX entities, which are of interest to describe the relationship to the forwarding topology and the control plane are further described in [I-D.ietf-opsawg-ipfix-alt-mark]. 8.2. YANG-Push Periodic subscription as defined in Section 3.1 of [RFC8641] is used to subscribe data. [I-D.ietf-bpm-on-path-telemetry-yang] introduces a YANG data model for monitoring Alternate-Marking telemetry data. Since the amount of observed data could overwhelm a router processor on a network node, publishing data from network processors as specified in [I-D.ietf-netconf-distributed-notif] is advised. 8.3. Hybrid Two-Step Another option for collecting AltMark data can be the Hybrid Two-Step (HTS) approach, defined in [I-D.ietf-ippm-hybrid-two-step]. It is a method of telemetry collection that separates the act of measuring the performance metric from collecting this information. A packet in the flow to which the AltMark method is applied can be used as an HTS Trigger, while the HTS Follow-up packet is then generated to collect the measurement data from the nodes, as further detailed in [I-D.ietf-ippm-hybrid-two-step]. 9. Encapsulations Fioccola, et al. Expires 19 May 2027 [Page 12] Internet-Draft alternate-marking-deployment November 2026 9.1. IPv6 The Alternate-Marking encapsulation for IPv6 is defined in [RFC9343], which also discusses deployment considerations for IPv6 networks. The IPv6 AltMark Option [RFC9343] applies the Alternate Marking Method to IPv6, and defines an Extension Header Option to encode the Alternate Marking Method for both the Hop-by-Hop Options Header and the Destination Options Header. For example, [I-D.zhou-ippm-enhanced-alternate-marking] defines extended data fields for the IPv6 AltMark Option and provides enhanced capabilities to overcome some challenges and enable future proof applications. It is worth mentioning that the enhanced capabilities are intended for further use and are optional. Additional extended data fields for the IPv6 AltMark Option are introduced in [I-D.wang-ippm-ipv6-flow-measurement] and [I-D.wang-ippm-ipv6-distributed-flow-measurement]. 9.2. SRv6 The Alternate-Marking encapsulation for SRv6 is discussed in IPv6 AltMark Option [RFC9343] and [RFC9947]. However, it is to be noted that [RFC9343] also applies to SRv6. [RFC9947] is an alternative experimental approach and it uses an experimental TLV in the SRH. 9.3. BIER The Alternate-Marking encapsulation for BIER is introduced in [I-D.ietf-bier-pmmm-oam]. 9.4. MPLS The Alternate-Marking application to MPLS has some options, as introduced in [RFC9571], [RFC9714], [I-D.cx-mpls-mna-inband-pm]. 9.5. SFC The Alternate-Marking encapsulation for SFC is introduced in [I-D.mfm-ippm-sfc-nsh-pmamm]. 9.6. NVO3 The Alternate-Marking encapsulation for NVO3 is introduced in [I-D.fmm-nvo3-pm-alt-mark]. Fioccola, et al. Expires 19 May 2027 [Page 13] Internet-Draft alternate-marking-deployment November 2026 10. Operational Considerations This document aims to complement [RFC9341] and [RFC9342] in terms of operation and manageability of the methodology. Indeed, the previous sections cover the aspects related to configuration and data export. [RFC9341] and [RFC9342] already include some recommendations for deployment. Further details about the method operation are specified for the different extensions: IPv6 [RFC9343], SRH [RFC9947], and MPLS [RFC9714]. In a controlled domain, the nodes may support the AltMark specific encapsulation and this also depends on the implementation. If a node is configured to read the AltMark option, the measurement is done on that node, otherwise, it is simply not considered in the measurement. Assuming that the measurement domain overlaps with the controlled domain, the procedure for AltMark data encapsulation can be summarized as follows: * Ingress Marking Node: An Ingress Node of a controlled domain that supports the Alternate Marking Method adds the AltMark data in the data packets. * Intermediate Transit Node: if an Intermediate Node is not capable of processing the AltMark data, it simply ignores it. If an Intermediate Node is capable of processing the AltMark data, it processes it. * Egress Unmarking Node: An Egress Node is the last node of the controlled domain. The processing if the AltMark data is similar to the processing at the Intermediate Nodes. The only difference is that it needs by default to remove the AltMark data from the data packets. The nodes in the AltMark measurement domain can be configured using the YANG data model in [I-D.ietf-bpm-alt-mark-yang], while the data can be exported using IPFIX [I-D.ietf-opsawg-ipfix-alt-mark] or the on-path telemetry YANG model [I-D.ietf-bpm-on-path-telemetry-yang]. 10.1. Measurement Domain Considerations As mentioned in Section 2, the AltMark measurement domain can overlap with the controlled domain or may be a subset of the controlled domain. In general, the flow identification parameters and flow correlation values are valid only within a measurement domain. Fioccola, et al. Expires 19 May 2027 [Page 14] Internet-Draft alternate-marking-deployment November 2026 The uniqueness of the FlowMonID MUST be guaranteed only inside the measurement domain, therefore separate measurement domains may use the same FlowMonID to identify different flows. However, an implementation may use globally unique FlowMonID values across different measurement domains in order to use the same identification fields for a flow that crosses separate measurement domains. This approach could be chosen to simplify the data analysis. The PN is univocally defined in Section 8, but its value may vary in different domains depending on the length of the marking period selected for each domain. Overall, the same marking period SHOULD be used in different measurement domains if the measurement data need to be linked for analysis purposes. It is RECOMMENDED to decide a priori the measurement domain or the set of measurement domains in which the identifiers are guaranteed unique and the values are meaningful. In this way, an NMS can handle adequately both the configuration and the correlation of the flow identification parameters. 10.2. Synchronization and Timing Considerations The requirement of time synchronization is defined in Section 5 of [RFC9341] and Section 8 of [RFC9342]. However, it is worth considering what happens in case the requirement of time synchronization is not met. If the clock skew or drift implies that the synchronization and timing precondition cannot be satisfied, the measurement must be skipped for the affected intervals until synchronization is restored. The synchronization and timing issue may affect only a single node or the entire AltMark measurement domain. * If the issue affects only a single node, the measurement can still be done on all the other nodes. * If the issue affects multiple nodes (including the marking nodes) in the measurement domain, the measurement can restart as soon as the issue is resolved. 10.3. Configuration and Data Export Considerations Fault conditions may affect configuration (Section 7) and data collection (Section 8) reliability. There are different possibilities: * Configuration failures or missing exports may involve only a single node that is not a marking node. In this case the measurement can still be done for all the other nodes. Fioccola, et al. Expires 19 May 2027 [Page 15] Internet-Draft alternate-marking-deployment November 2026 * A configuration failure may involve multiple nodes and, if the marking node(s) is not configured properly, the measurement cannot be done on the other nodes. The measurement can start when the configuration succeeds. * The missing exports may involve one or more consecutive marking periods on multiple nodes and, in this case, if the marking is still working on the source node(s), the measurement is skipped only on the affected nodes and can continue from the next interval when the exports resume. Configuration mistakes and erroneous values exported can also be treated respectively as configuration failures and missing exports. But, an implementation may consider different workarounds according to the situation. 11. Security Considerations This document describes the AltMark deployment framework and security must be ensured at the data plane, control plane, and management plane. Alternate Marking [RFC9341] and Clustered Alternate Marking [RFC9342] analyze different security concerns and related solutions. These aspects are valid and applicable also to this document. In particular the fundamental security requirement is that Alternate Marking MUST only be applied in a specific limited domain, as also mentioned in [RFC8799]. At the data plane, each AltMark encapsulations MUST report the specific security considerations relevant for the forwarding plane. At the management and control plane, the AltMark manageability tools and the interface between the controller and the nodes MUST be secured in order to authenticate the authorized controller and verify the integrity of configuration procedures. Also, the data collection and reporting of data and statistics sent by the nodes to the controller MUST be secured and exported data to an unauthorized controller MUST be prevented. An operator should also put in place a means to monitor and detect misbehaving nodes and malicious controllers. 12. IANA Considerations This document has no request to IANA. Fioccola, et al. Expires 19 May 2027 [Page 16] Internet-Draft alternate-marking-deployment November 2026 13. Acknowledgements The authors of this document would like to thank Mohamed Boucadair, Greg Mirsky, Chongfeng Xie, Xiao Min, Benoit Claise, Saumya Dikshit for their comments and reviews. 14. Contributors Mauro Cociglio Email: mauro.cociglio@outlook.com Massimo Nilo FiberCop Email: massimo.nilo@fibercop.com Fabio Bulgarella Telecom Italia Email: fabio.bulgarella@guest.telecomitalia.it 15. References 15.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, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC9341] Fioccola, G., Ed., Cociglio, M., Mirsky, G., Mizrahi, T., and T. Zhou, "Alternate-Marking Method", RFC 9341, DOI 10.17487/RFC9341, December 2022, . [RFC9342] Fioccola, G., Ed., Cociglio, M., Sapio, A., Sisto, R., and T. Zhou, "Clustered Alternate-Marking Method", RFC 9342, DOI 10.17487/RFC9342, December 2022, . 15.2. Informative References Fioccola, et al. Expires 19 May 2027 [Page 17] Internet-Draft alternate-marking-deployment November 2026 [I-D.cx-mpls-mna-inband-pm] Cheng, W., Min, X., Gandhi, R., Mirsky, G., and G. Fioccola, "MNA for Performance Measurement with Alternate Marking Method", Work in Progress, Internet-Draft, draft- cx-mpls-mna-inband-pm-09, 18 August 2026, . [I-D.fmm-nvo3-pm-alt-mark] Fioccola, G., Mirsky, G., and T. Mizrahi, "Performance Measurement (PM) with Alternate Marking in Network Virtualization Overlays (NVO3)", Work in Progress, Internet-Draft, draft-fmm-nvo3-pm-alt-mark-03, 23 October 2018, . [I-D.he-idr-bgp-flowspec-ifit] hexiaoming, X., Wang, A., Cheng, W., Dong, J., and X. Min, "BGP Extensions to Enable BGP FlowSpec based IFIT", Work in Progress, Internet-Draft, draft-he-idr-bgp-flowspec- ifit-04, 30 July 2026, . [I-D.ietf-bier-pmmm-oam] Mirsky, G., Zheng, L., Chen, M., and G. Fioccola, "Performance Measurement (PM) with Marking Method in Bit Index Explicit Replication (BIER) Layer", Work in Progress, Internet-Draft, draft-ietf-bier-pmmm-oam-16, 7 November 2024, . [I-D.ietf-bpm-alt-mark-yang] Graf, T., Wang, M., Fioccola, G., Zhou, T., and X. Min, "A YANG Data Model for the Alternate-Marking Method", Work in Progress, Internet-Draft, draft-ietf-bpm-alt-mark-yang-00, 30 October 2026, . [I-D.ietf-bpm-on-path-telemetry-yang] Fioccola, G., Zhou, T., Zhu, Y., Zhang, W., Feng, A. H., and K. Zhu, "On-Path Telemetry YANG Data Models", Work in Progress, Internet-Draft, draft-ietf-bpm-on-path- telemetry-yang-00, 30 October 2026, . Fioccola, et al. Expires 19 May 2027 [Page 18] Internet-Draft alternate-marking-deployment November 2026 [I-D.ietf-idr-bgp-ifit-capabilities] Fioccola, G., Pang, R., Wang, S., Decraene, B., Zhuang, S., and H. Wang, "Advertising In-situ Flow Information Telemetry (IFIT) Capabilities in BGP", Work in Progress, Internet-Draft, draft-ietf-idr-bgp-ifit-capabilities-10, 16 October 2026, . [I-D.ietf-idr-sr-policy-ifit] Qin, F., Yuan, H., Yang, S., Zhou, T., and G. Fioccola, "BGP SR Policy Extensions to Enable IFIT", Work in Progress, Internet-Draft, draft-ietf-idr-sr-policy-ifit- 13, 16 October 2026, . [I-D.ietf-ippm-hybrid-two-step] Mirsky, G., Lingqiang, W., Zhui, G., Song, H., and P. Thubert, "Hybrid Two-Step Performance Measurement Method", Work in Progress, Internet-Draft, draft-ietf-ippm-hybrid- two-step-07, 25 October 2026, . [I-D.ietf-netconf-distributed-notif] Zhou, T., Zheng, G., Voit, E., Graf, T., and P. Francois, "Subscription to Notifications in a Distributed Architecture", Work in Progress, Internet-Draft, draft- ietf-netconf-distributed-notif-24, 31 October 2026, . [I-D.ietf-opsawg-ipfix-alt-mark] Graf, T., Fioccola, G., Zhou, T., Zhu, Y., and J. Ge, "IP Flow Information Export (IPFIX) Alternate-Marking Information Elements", Work in Progress, Internet-Draft, draft-ietf-opsawg-ipfix-alt-mark-11, 15 November 2026, . [I-D.ietf-pce-pcep-ifit] Yuan, H., 王雪荣, Yang, P., Li, W., and G. Fioccola, "Path Computation Element Communication Protocol (PCEP) Extensions to Enable IFIT", Work in Progress, Internet- Draft, draft-ietf-pce-pcep-ifit-09, 6 July 2026, . Fioccola, et al. Expires 19 May 2027 [Page 19] Internet-Draft alternate-marking-deployment November 2026 [I-D.mfm-ippm-sfc-nsh-pmamm] Mirsky, G., Fioccola, G., and T. Mizrahi, "Performance Measurement (PM) with Alternate Marking Method in Service Function Chaining (SFC) Network Service Header (NSH) Domain", Work in Progress, Internet-Draft, draft-mfm-ippm- sfc-nsh-pmamm-00, 1 April 2022, . [I-D.wang-ippm-ipv6-distributed-flow-measurement] Wang, H., Li, J., Lin, C., Min, X., and G. Mirsky, "Distributed Flow Measurement in IPv6", Work in Progress, Internet-Draft, draft-wang-ippm-ipv6-distributed-flow- measurement-07, 24 October 2026, . [I-D.wang-ippm-ipv6-flow-measurement] Li, J., Li, Z., Lin, C., Min, X., and G. Mirsky, "Flow Measurement in IPv6 Network", Work in Progress, Internet- Draft, draft-wang-ippm-ipv6-flow-measurement-11, 24 October 2026, . [I-D.zhou-ippm-enhanced-alternate-marking] Zhou, T., Fioccola, G., Liu, Y., Pang, R., Xiong, L., Lee, S., Cociglio, M., and W. Li, "Enhanced Alternate Marking Method", Work in Progress, Internet-Draft, draft-zhou- ippm-enhanced-alternate-marking-19, 5 June 2026, . [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006, . [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation Element (PCE) Communication Protocol (PCEP)", RFC 5440, DOI 10.17487/RFC5440, March 2009, . [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information", STD 77, RFC 7011, DOI 10.17487/RFC7011, September 2013, . Fioccola, et al. Expires 19 May 2027 [Page 20] Internet-Draft alternate-marking-deployment November 2026 [RFC7799] Morton, A., "Active and Passive Metrics and Methods (with Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799, May 2016, . [RFC8321] Fioccola, G., Ed., Capello, A., Cociglio, M., Castaldelli, L., Chen, M., Zheng, L., Mirsky, G., and T. Mizrahi, "Alternate-Marking Method for Passive and Hybrid Performance Monitoring", RFC 8321, DOI 10.17487/RFC8321, January 2018, . [RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641, September 2019, . [RFC8799] Carpenter, B. and B. Liu, "Limited Domains and Internet Protocols", RFC 8799, DOI 10.17487/RFC8799, July 2020, . [RFC8889] Fioccola, G., Ed., Cociglio, M., Sapio, A., and R. Sisto, "Multipoint Alternate-Marking Method for Passive and Hybrid Performance Monitoring", RFC 8889, DOI 10.17487/RFC8889, August 2020, . [RFC9232] Song, H., Qin, F., Martinez-Julia, P., Ciavaglia, L., and A. Wang, "Network Telemetry Framework", RFC 9232, DOI 10.17487/RFC9232, May 2022, . [RFC9343] Fioccola, G., Zhou, T., Cociglio, M., Qin, F., and R. Pang, "IPv6 Application of the Alternate-Marking Method", RFC 9343, DOI 10.17487/RFC9343, December 2022, . [RFC9571] Bryant, S., Ed., Swallow, G., Chen, M., Fioccola, G., and G. Mirsky, "Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels", RFC 9571, DOI 10.17487/RFC9571, May 2024, . [RFC9714] Cheng, W., Ed., Min, X., Ed., Zhou, T., Dai, J., and Y. Peleg, "Encapsulation for MPLS Performance Measurement with the Alternate-Marking Method", RFC 9714, DOI 10.17487/RFC9714, February 2025, . Fioccola, et al. Expires 19 May 2027 [Page 21] Internet-Draft alternate-marking-deployment November 2026 [RFC9947] Fioccola, G., Zhou, T., Mishra, G., Wang, X., Zhang, G., and M. Cociglio, "Application of the Alternate-Marking Method to the Segment Routing Header", RFC 9947, DOI 10.17487/RFC9947, March 2026, . [RFC9951] Graf, T., Claise, B., and A. Huang-Feng, "Export of Delay Performance Metrics in IP Flow Information Export (IPFIX)", RFC 9951, DOI 10.17487/RFC9951, April 2026, . Authors' Addresses Giuseppe Fioccola Huawei Viale Martesana, 12 20055 Vimodrone (Milan) Italy Email: giuseppe.fioccola@huawei.com Keyi Zhu Huawei 156 Beiqing Rd. Beijing 100095 China Email: zhukeyi@huawei.com Tianran Zhou Huawei 156 Beiqing Rd. Beijing 100095 China Email: zhoutianran@huawei.com Thomas Graf Swisscom Binzring 17 CH-8045 Zurich Switzerland Email: thomas.graf@swisscom.com Fioccola, et al. Expires 19 May 2027 [Page 22] Internet-Draft alternate-marking-deployment November 2026 Lin Zhang China Mobile Email: zhanglin1@cmdi.chinamobile.com Fioccola, et al. Expires 19 May 2027 [Page 23]