IPPM T. Graf Internet-Draft Swisscom Intended status: Standards Track G. Fioccola Expires: 25 April 2024 T. Zhou Huawei 23 October 2023 A YANG Data Model for the Alternate Marking Method draft-gfz-ippm-alt-mark-yang-00 Abstract Alternate-Marking Method is a technique used to perform packet loss, delay, and jitter measurements on in-flight packets. This document defines a YANG data model for the Alternate Marking Method. 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 25 April 2024. Copyright Notice Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved. 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. Graf, et al. Expires 25 April 2024 [Page 1] Internet-Draft yang-alternate-marking October 2023 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 1.2. Conventions . . . . . . . . . . . . . . . . . . . . . . . 2 2. AltMark Tree Diagram . . . . . . . . . . . . . . . . . . . . 3 3. AltMark Profile . . . . . . . . . . . . . . . . . . . . . . . 4 4. Alternate Marking Method YANG Data Model . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 8.1. Normative References . . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 1. Introduction Alternate-Marking Method [RFC9341] [RFC9342] (AltMark) is a technique used to perform packet loss, delay, and jitter measurements on in- flight packets. This document defines a YANG data model for the Alternate Marking Method. 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. Conventions The following terms are defined in [RFC7950] and are used in this specification: * augment * data model * data node The terminology for describing YANG data models is found in [RFC7950]. Graf, et al. Expires 25 April 2024 [Page 2] Internet-Draft yang-alternate-marking October 2023 2. AltMark Tree Diagram Tree diagrams used in this document follow the notation defined in [RFC8340]. The AltMark model is organized as shown in the following figure. Each AltMark profile associates with one flow and the corresponding AltMark information. The "altmark-info" is a container for all the read only information that assists monitoring systems in the interpretation of the AltMark data. module: ietf-alt-mark +--ro altmark-info | +--ro timestamp-type? | +--ro available-interface* [if-name] | +--ro if-name if:interface-ref +--rw altmark-profiles +--rw admin-config | +--rw enabled? boolean +--rw altmark-profile [profile-name] +--rw profile-name string +--rw filter | +--rw filter-type? altmark-filter-type | +--rw ace-name? -> /acl:acls/acl/aces/ace/name +--rw protocol-type? altmark-protocol-type +--rw node-action altmark-node-action +--rw period? uint64 +--rw flow-mon-id? uint32 +--rw measurement-mode? altmark-measurement-mode +--rw enable-loss-measurement? boolean +--rw enable-delay-measurement? boolean In the "altmark-profiles", the "enabled" is an administrative configuration. When set to true, AltMark configuration is enabled for the system. Meanwhile, the AltMark data-plane functionality is enabled. The "filter" is used to identify a flow, where the AltMark data can be applied. There may be multiple filter types. ACL [RFC8519] is a common way to specify a flow. The AltMark profile can associate with an ACE(Access Control Entry). AltMark actions MUST be driven by the accepted packets, when the matched ACE "forwarding" action is "accept". Graf, et al. Expires 25 April 2024 [Page 3] Internet-Draft yang-alternate-marking October 2023 The AltMark data can be encapsulated into multiple protocols, e.g., IPv6 [RFC9343] and SRH [I-D.fz-spring-srv6-alt-mark]. Additional protocol extensions are reported in [I-D.fz-ippm-alt-mark-deployment] The "protocol-type" is used to indicate the protocol for the AltMark application. For example, if the "protocol-type" is IPv6, the AltMark marking node will encapsulate the associated flow with the IPv6 [RFC9343] format. 3. AltMark Profile The AltMark data is expected to be read and exported or locally aggregated at every node that the flow traverses within the AltMark domain. The "altmark-profile" contains the detailed information for the AltMark data. The information includes: * profile-name: it is the unique identifier for each AltMark profile * filter: it is used to identify a flow, where the AltMark data can be applied * protocol-type: it is used to indicate the protocol for the AltMark application * node-action: indicates the operation applied to the flow (e.g. marking AltMark header, read the AltMark data, or unmarking AltMark header). * period: it indicates the AltMark period (see [I-D.fz-ippm-alt-mark-deployment]). * flow-mon-id: it is used to identify the monitored flow and to correlate the exported data of the same flow from multiple nodes and from multiple packets. * measurement-mode: it specifies the measurement mode: hop-by-hop or end-to-end. * enable-loss-measurement: if true, it enables loss measurements. * enable-delay-measurement: if true, it enables delay measurements. Note that users can augment this module. 4. Alternate Marking Method YANG Data Model Graf, et al. Expires 25 April 2024 [Page 4] Internet-Draft yang-alternate-marking October 2023 file "ietf-AMM@2023-10-11.yang" module ietf-alt-mark { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-altmark"; prefix "altmark"; import ietf-access-control-list { prefix "acl"; reference "RFC 8519: YANG Data Model for Network Access Control Lists (ACLs)"; } import ietf-interfaces { prefix "if"; reference "RFC 8343: A YANG Data Model for Interface Management"; } import ietf-lime-time-types { prefix "lime"; reference "RFC 8532: Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications"; } organization "IETF IPPM (IP Performance Metrics) Working Group"; contact "WG Web: WG List: Editor: thomas.graf@swisscom.com Editor: giuseppe.fioccola@huawei.com Editor: zhoutianran@huawei.com; description "This YANG module specifies a vendor-independent data model for the Alternate Marking (AltMark). 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 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here. Copyright (c) 2023 IETF Trust and the persons identified as Graf, et al. Expires 25 April 2024 [Page 5] Internet-Draft yang-alternate-marking October 2023 authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; revision 2023-10-11 { description "First revision."; reference "RFC XXXX: A YANG Data Model for Alternate-Marking"; } /* * FEATURES */ feature altmark { description "This feature indicated that the Alternate-Marking Method is supported."; reference "RFC 9341: Alternate-Marking Method"; reference "RFC 9342: Clustered Alternate-Marking Method"; } /* * IDENTITIES */ identity filter { description "Base identity to represent a filter. A filter is used to specify the flow to which the AltMark method is applied. "; } identity acl-filter { base filter; description "Apply ACL rules to specify the flow."; } identity protocol { description Graf, et al. Expires 25 April 2024 [Page 6] Internet-Draft yang-alternate-marking October 2023 "Base identity to represent the protocol. It's used to indicate the protocol for the application of the AltMark method."; } identity ipv6 { base protocol; description "The AltMark method is applied to IPv6 protocol."; reference "RFC 9343: IPv6 Application of the Alternate-Marking Method"; } identity srh { base protocol; description "The AltMark method is applied to SRH."; reference "[I-D.fz-spring-srv6-alt-mark]: Application of the Alternate Marking Method to the Segment Routing Header"; } identity node-action { description "Base identity to represent the node actions. It's used to indicate what action the node will take."; } identity action-marking { base node-action; description "It indicates that the node must mark the AltMark data field, according to the operations described in RFC 9341 and RFC 9342"; } identity action-unmarking { base node-action; description "It indicates that the node must unmark the AltMark data field, according to the operations described in RFC 9341 and RFC 9342"; } identity action-read { base node-action; description "It indicates the node only reads the AltMark data, according to the operations described in RFC 9341 and RFC 9342"; } Graf, et al. Expires 25 April 2024 [Page 7] Internet-Draft yang-alternate-marking October 2023 identity period { description "It indicates the AltMark Period."; } identity flow-mon-id { description "It indicates the FlowMonID."; } identity measurement-mode { description "It indicates the measurement mode."; } identity hbh-measurement { base measurement-mode; description "It indicates that hop-by-hop measurements can be enabled."; } identity e2e-measurement { base measurement-mode; description "It indicates that end-to-end measurements can be enabled."; } identity enable-loss-measurement { description "It indicates that loss measurements are enabled."; } identity enable-delay-measurement { description "It indicates that delay measurements are enabled."; } /* * TYPE DEFINITIONS */ typedef altmark-filter-type { type identityref { base filter; } description "It specifies a known type of filter."; } Graf, et al. Expires 25 April 2024 [Page 8] Internet-Draft yang-alternate-marking October 2023 typedef altmark-protocol-type { type identityref { base protocol; } description "It specifies a known type of carrier protocol for the AltMark data."; } typedef altmark-measurement-mode { type identityref { base measurement-mode; } description "It specifies the measurement mode."; } /* * GROUP DEFINITIONS */ grouping altmark-filter { description "A grouping for AltMark filter definition"; leaf filter-type { type altmark-filter-type; description "filter type"; } leaf ace-name { when "derived-from-or-self(../filter-type, 'altmark:acl-filter')"; type leafref { path "/acl:acls/acl:acl/acl:aces/acl:ace/acl:name"; } description "The Access Control Entry name is used to refer to an ACL specification."; } } grouping measurement-mode { description "A grouping for measurement mode."; leaf hbh-measurement { type boolean; default false; description "This object indicates that hop-by-hop measurements can be enabled."; Graf, et al. Expires 25 April 2024 [Page 9] Internet-Draft yang-alternate-marking October 2023 } leaf e2e-measurement { type boolean; default false; description "This object indicates that end-to-end measurements can be enabled."; } } grouping altmark-setup { description "A grouping for AltMark profile."; leaf node-action { type altmark-node-action; default action-read; description "This object indicates the action that the node needs to take, i.e. marking/read/unmarking."; } leaf period { type uint64; description "It specifies the AltMark marking period."; } leaf altmark-flowmonid { type uint32; description "It specifies the FlowMonID. A 20-bit flow identifier. The field is set at the marking node. The FlowMonID can be uniformly assigned by a central controller or algorithmically generated by the marking node. The latter approach cannot guarantee the uniqueness of the FlowMonID, yet the conflict probability is small due to the large space. FlowMonID is used to identify the flow and to correlate the exported data of the same flow from multiple nodes and from multiple packets."; } } } grouping altmark-admin-config { description "AltMark top-level administrative configuration."; Graf, et al. Expires 25 April 2024 [Page 10] Internet-Draft yang-alternate-marking October 2023 leaf enabled { type boolean; default false; description "This object is to control the availability of configuration. It MUST be true before anything in the /altmark/altmark-profile can be edited. If false, any configuration in place is not used."; } } /* * DATA NODES */ container AltMark { description "AltMark top level container"; container altmark-info { config false; description "Describes information such as units or timestamp format that assists monitoring systems in the interpretation of the AltMark data."; leaf timestamp-type { type identityref { base lime:timestamp-type; } description "Type of timestamp, such as Truncated PTP or NTP."; } list available-interface { key "if-name"; description "A list of available interfaces that support Alternate-Marking."; leaf if-name { type if:interface-ref; description "This is a reference to the Interface name."; } } } container altmark-profiles { description "Contains the AltMark profiles."; Graf, et al. Expires 25 April 2024 [Page 11] Internet-Draft yang-alternate-marking October 2023 container admin-config { description "Contains all the administrative configurations related to the AltMark functionalities"; uses altmark-admin-config; } list altmark-profile { if-feature altmark; key "profile-name"; description "It describes the list of the AltMark profiles configured on the node"; leaf profile-name { type string{ length "1..300"; } description "Unique identifier for each AltMark profile."; } container filter { uses altmark-filter; description "The filter which is used to indicate the flow where the AltMark is applied."; } leaf protocol-type { type altmark-protocol-type; description "This item is used to indicate the carrier protocol where the AltMark is applied."; } uses altmark-setup; uses measurement-mode; leaf enable-loss-measurement { type boolean; default false; description "If true, it object indicates that loss measurements are enabled."; } leaf enable-delay-measurement { type boolean; Graf, et al. Expires 25 April 2024 [Page 12] Internet-Draft yang-alternate-marking October 2023 default false; description "If true, it indicates that delay measurements are enabled."; } } } } } 5. Security Considerations Alternate Marking [RFC9341] and Multipoint 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]. The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446]. The Network Configuration Access Control Model (NACM) [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. There are a number of data nodes defined in this YANG module. These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: * /altmark/altmark-profiles/admin-config The items in the container above include the top level administrative configurations related to the AltMark functionalities. Unexpected changes to these items could lead to the AltMark function disruption and/ or misbehavior of the AltMark. Graf, et al. Expires 25 April 2024 [Page 13] Internet-Draft yang-alternate-marking October 2023 * /altmark/altmark-profiles/altmark-profile The entries in the container above include the AltMark profile configurations which indirectly create or modify the device configurations. Unexpected changes to these entries could lead to the mistake of the AltMark behavior for the corresponding flows. 6. IANA Considerations IANA is requested to assign a new URI from the IETF XML Registry [RFC3688]. The following URI is suggested: URI: urn:ietf:params:xml:ns:yang:ietf-altmark Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace. This document also requests a new YANG module name in the YANG Module Names registry [RFC7950] with the following suggestion: name: ietf-altmark namespace: urn:ietf:params:xml:ns:yang:ietf-altmark prefix: altmark reference: RFC XXXX 7. Acknowledgements TBD 8. References 8.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, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . Graf, et al. Expires 25 April 2024 [Page 14] Internet-Draft yang-alternate-marking October 2023 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . [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, . 8.2. Informative References [I-D.fz-ippm-alt-mark-deployment] Fioccola, G., Zhou, T., Milan, F., and M. Nilo, "Alternate Marking Deployment Framework", Work in Progress, Internet- Draft, draft-fz-ippm-alt-mark-deployment-00, 7 July 2023, . [I-D.fz-spring-srv6-alt-mark] Fioccola, G., Zhou, T., Cociglio, M., Mishra, G. S., wang, X., and G. Zhang, "Application of the Alternate Marking Method to the Segment Routing Header", Work in Progress, Internet-Draft, draft-fz-spring-srv6-alt-mark-07, 22 September 2023, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, . [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . Graf, et al. Expires 25 April 2024 [Page 15] Internet-Draft yang-alternate-marking October 2023 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10.17487/RFC8341, March 2018, . [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, . [RFC8519] Jethanandani, M., Agarwal, S., Huang, L., and D. Blair, "YANG Data Model for Network Access Control Lists (ACLs)", RFC 8519, DOI 10.17487/RFC8519, March 2019, . [RFC8799] Carpenter, B. and B. Liu, "Limited Domains and Internet Protocols", RFC 8799, DOI 10.17487/RFC8799, July 2020, . [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, . Authors' Addresses Thomas Graf Swisscom Binzring 17 CH-8045 Zurich Switzerland Email: thomas.graf@swisscom.com Giuseppe Fioccola Huawei Palazzo Verrocchio, Centro Direzionale Milano 2 20054 Segrate (Milan) Italy Email: giuseppe.fioccola@huawei.com Tianran Zhou Huawei 156 Beiqing Rd. Beijing 100095 China Email: zhoutianran@huawei.com Graf, et al. Expires 25 April 2024 [Page 16]