LISP Working Group V. Ermagan Internet-Draft Google Intended status: Experimental A. Rodriguez-Natal Expires: 4 May 2027 F. Coras Cisco C. Moberg NVIDIA R. Rahman Equinix A. Cabellos-Aparicio Technical University of Catalonia F. Maino Cisco 31 October 2026 LISP YANG Model draft-ietf-lisp-yang-26 Abstract This document describes a YANG data model to use with the Locator/ID Separation Protocol (LISP). This model can be used to configure and monitor the different control plane and data plane elements that enable a LISP network. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA) defined in [RFC8342]. 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 4 May 2027. Ermagan, et al. Expires 4 May 2027 [Page 1] Internet-Draft LISP-YANG October 2026 Copyright Notice Copyright (c) 2026 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Prefixes . . . . . . . . . . . . . . . . . . . . . . . . 3 2. LISP Module . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Module Structure . . . . . . . . . . . . . . . . . . . . 4 2.2. Module Definition . . . . . . . . . . . . . . . . . . . . 7 3. LISP-ITR Module . . . . . . . . . . . . . . . . . . . . . . . 19 3.1. Module Structure . . . . . . . . . . . . . . . . . . . . 19 3.2. Module Definition . . . . . . . . . . . . . . . . . . . . 24 4. LISP-ETR Module . . . . . . . . . . . . . . . . . . . . . . . 28 4.1. Module Structure . . . . . . . . . . . . . . . . . . . . 28 4.2. Module Definition . . . . . . . . . . . . . . . . . . . . 30 5. LISP-Map-Server Module . . . . . . . . . . . . . . . . . . . 34 5.1. Module Structure . . . . . . . . . . . . . . . . . . . . 34 5.2. Module Definition . . . . . . . . . . . . . . . . . . . . 43 6. LISP-Map-Resolver Module . . . . . . . . . . . . . . . . . . 49 6.1. Module Structure . . . . . . . . . . . . . . . . . . . . 49 6.2. Module Definition . . . . . . . . . . . . . . . . . . . . 49 7. LISP-Address-Types Module . . . . . . . . . . . . . . . . . . 51 7.1. Module Definition . . . . . . . . . . . . . . . . . . . . 52 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 74 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 74 10. Security Considerations . . . . . . . . . . . . . . . . . . . 76 11. Normative References . . . . . . . . . . . . . . . . . . . . 79 Appendix A. Data Model examples . . . . . . . . . . . . . . . . 81 A.1. LISP protocol instance . . . . . . . . . . . . . . . . . 81 A.2. LISP ITR . . . . . . . . . . . . . . . . . . . . . . . . 83 A.3. LISP ETR . . . . . . . . . . . . . . . . . . . . . . . . 83 A.4. LISP Map-Server . . . . . . . . . . . . . . . . . . . . . 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 87 Ermagan, et al. Expires 4 May 2027 [Page 2] Internet-Draft LISP-YANG October 2026 1. Introduction The Locator/ID Separation Protocol (LISP) defines several network elements subject to be configured. This document presents YANG data models that are required for basic configuration of all major LISP [RFC9301] elements. The models also capture some essential operational data elements as well. The rationale behind these models is to extend 'ietf-routing' with LISP specifics, and although a network device might implement several LISP roles simultaneously, the model has been divided into different modules for ease of management and to better represent the separation between the different logical LISP elements. 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD 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. Tree Diagrams This document uses the graphical representation of data models defined in [RFC8340]. 1.3. Prefixes The table below provides a summary of the prefixes used by this document. Ermagan, et al. Expires 4 May 2027 [Page 3] Internet-Draft LISP-YANG October 2026 +==========+=========================+===========+ | Prefix | YANG module | Reference | +==========+=========================+===========+ | lisp | ietf-lisp | Section 2 | +----------+-------------------------+-----------+ | if | ietf-interfaces | [RFC8343] | +----------+-------------------------+-----------+ | lisp-at | ietf-lisp-address-types | Section 7 | +----------+-------------------------+-----------+ | yang | ietf-yang-types | [RFC6991] | +----------+-------------------------+-----------+ | rt | ietf-routing | [RFC8349] | +----------+-------------------------+-----------+ | ni | ietf-network-instance | [RFC8529] | +----------+-------------------------+-----------+ | lisp-itr | ietf-lisp-itr | Section 3 | +----------+-------------------------+-----------+ | inet | ietf-inet-types | [RFC6991] | +----------+-------------------------+-----------+ | lisp-etr | ietf-lisp-etr | Section 4 | +----------+-------------------------+-----------+ | lisp-ms | ietf-lisp-mapserver | Section 5 | +----------+-------------------------+-----------+ | lisp-mr | ietf-lisp-mapresolver | Section 6 | +----------+-------------------------+-----------+ Table 1: Prefixes and corresponding YANG modules 2. LISP Module This is the base LISP module. It is further augmented by the LISP device role specific modules defined elsewhere in this document. 2.1. Module Structure module: ietf-lisp augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol: +--rw lisp +--rw locator-sets | +--rw locator-set* [locator-set-name] | +--rw locator-set-name lisp-at:id-type | +--rw (locator-type)? | +--:(local-interface) | | +--rw interface* [interface-ref] | | +--rw interface-ref if:interface-ref | | +--rw priority? uint8 Ermagan, et al. Expires 4 May 2027 [Page 4] Internet-Draft LISP-YANG October 2026 | | +--rw weight? uint8 | | +--rw multicast-priority? uint8 | | +--rw multicast-weight? uint8 | +--:(general-locator) | +--rw locator* [locator-id] | +--rw locator-id lisp-at:id-type | +--rw locator-address | | +--rw address-type | | | lisp-address-family-ref | | +--rw (address)? | | +--:(no-address) | | | +--rw no-address? empty | | +--:(ipv4) | | | +--rw ipv4? | | | inet:ipv4-address | | +--:(ipv4-prefix) | | | +--rw ipv4-prefix? | | | inet:ipv4-prefix | | +--:(ipv6) | | | +--rw ipv6? | | | inet:ipv6-address | | +--:(ipv6-prefix) | | | +--rw ipv6-prefix? | | | inet:ipv6-prefix | | +--:(mac) | | | +--rw mac? | | | yang:mac-address | | +--:(distinguished-name) | | | +--rw distinguished-name? | | | distinguished-name-type | | +--:(as-number) | | | +--rw as-number? | | | inet:as-number | | +--:(null-address) | | | +--rw null-address | | | +--rw address? empty | | +--:(afi-list) | | | +--rw afi-list | | | +--rw address-list* simple-address | | +--:(instance-id) | | | +--rw instance-id | | | +--rw instance-id? uint32 | | | +--rw mask-length? uint8 | | | +--rw address? simple-address | | +--:(as-number-lcaf) | | | +--rw as-number-lcaf | | | +--rw as? inet:as-number | | | +--rw address? Ermagan, et al. Expires 4 May 2027 [Page 5] Internet-Draft LISP-YANG October 2026 | | | ip-address-or-prefix | | +--:(application-data) | | | +--rw application-data | | | +--rw address? | | | | ip-address-or-prefix | | | +--rw protocol? uint8 | | | +--rw ip-tos? int32 | | | +--rw local-port-low? | | | | inet:port-number | | | +--rw local-port-high? | | | | inet:port-number | | | +--rw remote-port-low? | | | | inet:port-number | | | +--rw remote-port-high? | | | inet:port-number | | +--:(geo-coordinates) | | | +--rw geo-coordinates | | | +--rw latitude? bits | | | +--rw latitude-degrees? uint8 | | | +--rw latitude-minutes? uint8 | | | +--rw latitude-seconds? uint8 | | | +--rw longitude? bits | | | +--rw longitude-degrees? uint16 | | | +--rw longitude-minutes? uint8 | | | +--rw longitude-seconds? uint8 | | | +--rw altitude? int32 | | | +--rw address? | | | simple-address | | +--:(nat-traversal) | | | +--rw nat-traversal | | | +--rw ms-udp-port? uint16 | | | +--rw etr-udp-port? uint16 | | | +--rw global-etr-rloc? | | | | inet:ip-address | | | +--rw ms-rloc? | | | | inet:ip-address | | | +--rw private-etr-rloc? | | | | inet:ip-address | | | +--rw rtr-rlocs* | | | inet:ip-address | | +--:(explicit-locator-path) | | | +--rw explicit-locator-path | | | +--rw hop* [hop-id] | | | +--rw hop-id id-type | | | +--rw address union | | | +--rw lrs-bits? bits | | +--:(source-dest-key) | | | +--rw source-dest-key Ermagan, et al. Expires 4 May 2027 [Page 6] Internet-Draft LISP-YANG October 2026 | | | +--rw source | | | | ip-address-or-prefix | | | +--rw dest | | | ip-address-or-prefix | | +--:(key-value-address) | | +--rw key-value-address | | +--rw key? simple-address | | +--rw value? simple-address | +--rw priority? uint8 | +--rw weight? uint8 | +--rw multicast-priority? uint8 | +--rw multicast-weight? uint8 +--rw lisp-role* [lisp-role-type] | +--rw lisp-role-type lisp-role-ref +--rw lisp-router-id | +--rw site-id? uint64 | +--rw xtr-id? lisp:xtr-id-type +--rw vpns +--rw vpn* [instance-id] +--rw instance-id lisp-at:instance-id-type +--rw iid-name -> /ni:network-instances/network-instance/name 2.2. Module Definition file "ietf-lisp@2024-10-20.yang" module ietf-lisp { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp"; prefix lisp; import ietf-interfaces { prefix if; reference "RFC 8343: A YANG Data Model for Interface Management"; } // RFC Ed.: replace occurrences of XXXX with actual RFC number // and remove this note import ietf-lisp-address-types { prefix lisp-at; reference "RFC XXXX: LISP YANG model"; } import ietf-yang-types { prefix yang; Ermagan, et al. Expires 4 May 2027 [Page 7] Internet-Draft LISP-YANG October 2026 reference "RFC 6991: Common YANG Data Types"; } import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA version)"; } import ietf-network-instance { prefix ni; reference "RFC 8529: YANG Model for Network Instances"; } organization "IETF LISP (Locator/ID Separation Protocol) Working Group"; contact "WG Web: WG List: Editor: Vina Ermagan Editor: Alberto Rodriguez-Natal Editor: Reshad Rahman "; description "This YANG module defines the generic parameters for LISP. The module can be extended by vendors to define vendor-specific LISP parameters and policies. Copyright (c) 2024 IETF Trust and the persons identified as 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; see the RFC itself for full legal notices. "; reference Ermagan, et al. Expires 4 May 2027 [Page 8] Internet-Draft LISP-YANG October 2026 "RFC XXXX"; revision 2024-10-20 { description "Initial revision."; reference "RFC XXXX"; } /* * Identity definitions */ identity lisp { base rt:control-plane-protocol; description "LISP protocol."; reference "RFC 9301: Locator/ID Separation Protocol (LISP) Control Plane"; } identity lisp-role { description "LISP router role."; } identity itr { base lisp-role; description "LISP ITR."; } identity pitr { base lisp-role; description "LISP PITR."; } identity etr { base lisp-role; description "LISP ETR."; } identity petr { base lisp-role; description "LISP PETR."; Ermagan, et al. Expires 4 May 2027 [Page 9] Internet-Draft LISP-YANG October 2026 } identity mapping-system { description "Mapping System interface"; } identity single-node-mapping-system { base mapping-system; description "Logically singular Map Server."; } identity map-reply-act { description "Defines the lisp map-cache ACT type."; reference "https://www.iana.org/assignments/lisp-parameters" + "/lisp-parameters.xhtml#lisp-act-value"; } identity no-action { base map-reply-act; description "Mapping is kept alive and no encapsulation occurs."; } identity natively-forward { base map-reply-act; description "Matching packets are not encapsulated or dropped but natively forwarded."; } identity send-map-request { base map-reply-act; description "Matching packets invoke Map-Requests."; } identity drop-no-reason { base map-reply-act; description "Matching packets are dropped."; } identity drop-policy-denied { base map-reply-act; Ermagan, et al. Expires 4 May 2027 [Page 10] Internet-Draft LISP-YANG October 2026 description "Matching packets are dropped (due to policy)."; } identity drop-auth-failure { base map-reply-act; description "Matching packets are dropped (due to authentication failure)."; } identity auth-algorithm { description "Base identity for the authentication mechanisms supported by LISP."; reference "https://www.iana.org/assignments/lisp-parameters" + "/lisp-parameters.xhtml#lisp-key-id-numbers"; } identity no-auth-algorithm { base auth-algorithm; description "No authentication."; } identity hmac-sha-1-96-none { base auth-algorithm; description "MAC = HMAC-SHA-1-96 (RFC2404), KDF = none."; } identity hmac-sha-256-128-none { base auth-algorithm; description "MAC = HMAC-SHA-256-128 (RFC4868), KDF = none."; } identity hmac-sha-256-128-HKDF-SHA2562 { base auth-algorithm; description "MAC = HMAC-SHA-256-128, KDF = HKDF-SHA2562 (RFC4868)."; } typedef mapping-system-ref { type identityref { base mapping-system; } description Ermagan, et al. Expires 4 May 2027 [Page 11] Internet-Draft LISP-YANG October 2026 "Mapping System reference."; } typedef lisp-role-ref { type identityref { base lisp-role; } description "LISP role reference."; } typedef map-reply-action { type identityref { base map-reply-act; } description "Map-Reply action reference."; } typedef eid-id { type lisp-at:id-type; description "Type encoding of lisp-addresses to be generally used in EID keyed lists."; } typedef auth-algorithm-type { type identityref { base auth-algorithm; } description "Authentication algorithm reference."; } typedef xtr-id-type { type binary { length "16"; } description "128-bit xTR identifier."; } grouping locator-properties { description "Properties of a RLOC."; leaf priority { type uint8; description Ermagan, et al. Expires 4 May 2027 [Page 12] Internet-Draft LISP-YANG October 2026 "Locator priority."; } leaf weight { type uint8; description "Locator weight."; } leaf multicast-priority { type uint8; description "Locator's multicast priority."; } leaf multicast-weight { type uint8; description "Locator's multicast weight."; } } grouping locators-grouping { description "Grouping that defines a list of LISP locators."; list locator { key "locator-id"; description "List of routing locators."; leaf locator-id { type lisp-at:id-type; description "Locator id."; } container locator-address { uses lisp-at:lisp-address; description "The locator address provided in LISP canonical address format."; } uses locator-properties; } } grouping local-locators-grouping { description "Grouping that defines a list of LISP locators."; list interface { key "interface-ref"; description "The address type of the locator."; Ermagan, et al. Expires 4 May 2027 [Page 13] Internet-Draft LISP-YANG October 2026 leaf interface-ref { type if:interface-ref; description "The name of the interface supporting the locator."; } uses locator-properties; } } grouping mapping { description "Grouping that defines a LISP mapping."; container eid { uses lisp-at:lisp-address; description "End-host Identifier (EID) to be mapped to a list of locators."; } leaf time-to-live { type uint32; units "minutes"; description "Mapping validity period in minutes (as per RF6830)."; } leaf creation-time { type yang:date-and-time; config false; description "Time when the mapping was created."; } leaf authoritative { type bits { bit A { description "Authoritative bit."; } } description "Bit that indicates if mapping comes from an authoritative source."; } leaf static { type boolean; default "false"; description "This leaf should be true if the mapping is static."; } choice locator-list { Ermagan, et al. Expires 4 May 2027 [Page 14] Internet-Draft LISP-YANG October 2026 description "list of locators are either negative, or positive."; case negative-mapping { leaf map-reply-action { type map-reply-action; description "Forwarding action for a negative mapping."; } } case positive-mapping { container rlocs { uses locators-grouping; description "List of locators for a positive mapping."; } } } } grouping mappings { description "Grouping that defines a list of LISP mappings."; list vpn { key "instance-id"; description "VPN to which the mappings belong."; leaf instance-id { type leafref { path "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/lisp:lisp" + "/lisp:vpns/lisp:vpn" + "/lisp:instance-id"; } description "VPN identifier."; } container mappings { description "Mappings within the VPN."; list mapping { key "eid-id"; description "List of EID to RLOCs mappings."; leaf eid-id { type eid-id; description "Id that uniquely identifies a mapping."; } Ermagan, et al. Expires 4 May 2027 [Page 15] Internet-Draft LISP-YANG October 2026 uses mapping; } } } } grouping auth-key { description "Grouping that defines authentication keys."; container authentication-keys { description "Multiple authentication keys can be defined."; list authentication-key { key "auth-key-id"; description "Authentication key parameters."; leaf auth-key-id { type lisp-at:id-type; description "Identifier of the authentication key."; } leaf-list auth-algorithm-id { type lisp:auth-algorithm-type; description "Authentication algorithm used with the key."; } leaf auth-key-value { type string; description "Clear text authentication key."; } } } } augment "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol" { when "derived-from-or-self(rt:type, 'lisp:lisp')" { description "This augmentation is only valid for a control-plane protocol instance of LISP."; } description "LISP protocol ietf-routing module control-plane-protocol augmentation."; container lisp { description "Parameters for the LISP subsystem."; Ermagan, et al. Expires 4 May 2027 [Page 16] Internet-Draft LISP-YANG October 2026 container locator-sets { description "Container that defines a named locator set which can be referenced elsewhere."; list locator-set { key "locator-set-name"; description "Multiple locator sets can be defined."; leaf locator-set-name { type lisp-at:id-type; description "Locator set name."; } choice locator-type { description "Locator sets can be based on local interfaces, or general locators."; case local-interface { uses local-locators-grouping; description "List of locators in this set based on local interfaces."; } case general-locator { uses locators-grouping; description "List of locators in this set based on lisp-address."; } } } } list lisp-role { key "lisp-role-type"; description "List of lisp device roles such as MS, MR, ITR, PITR, ETR or PETR."; leaf lisp-role-type { type lisp-role-ref; description "The type of LISP device - identity derived from the 'lisp-device' base identity."; } } container lisp-router-id { when "../lisp-role/lisp-role-type = 'lisp:itr' or ../lisp-role/lisp-role-type = 'lisp:pitr' or ../lisp-role/lisp-role-type = 'lisp:etr' or Ermagan, et al. Expires 4 May 2027 [Page 17] Internet-Draft LISP-YANG October 2026 ../lisp-role/lisp-role-type = 'lisp:petr'" { description "Only when ITR, PITR, ETR or PETR."; } description "Site-ID and xTR-ID of the device."; leaf site-id { type uint64; description "Site ID."; } leaf xtr-id { type lisp:xtr-id-type; description "xTR ID."; } } container vpns { when "../lisp-role/lisp-role-type = 'lisp:itr' or ../lisp-role/lisp-role-type = 'lisp:pitr' or ../lisp-role/lisp-role-type = 'lisp:etr' or ../lisp-role/lisp-role-type = 'lisp:petr'" { description "Only when ITR, PITR, ETR or PETR."; } description "VPNs."; list vpn { key "instance-id"; unique "iid-name"; description "List of VPNs."; leaf instance-id { type lisp-at:instance-id-type; description "VPN identifier. The value 0 for instance-id must be used for the default VRF."; } leaf iid-name { type leafref { path "/ni:network-instances/ni:network-instance" + "/ni:name"; } mandatory true; description "Name of VPN (e.g. VRF) to which an instance-id is bound. Each instance-id is bound to a different VPN."; } Ermagan, et al. Expires 4 May 2027 [Page 18] Internet-Draft LISP-YANG October 2026 } } } } } 3. LISP-ITR Module This module captures the configuration data model of a LISP (proxy) Ingress Tunnel Router or LISP (p)ITR. The model also captures some operational data elements. 3.1. Module Structure module: ietf-lisp-itr augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/lisp:lisp: +--rw itr! +--rw rloc-probing! | +--rw interval? uint16 | +--rw retries? uint8 | +--rw retries-interval? uint16 +--rw itr-rlocs? leafref +--rw map-resolvers | +--rw map-resolver* inet:ip-address +--rw proxy-etrs | +--rw proxy-etr-address* inet:ip-address +--rw map-cache +--ro size? uint32 +--ro limit? uint32 +--rw vpn* [instance-id] +--rw instance-id leafref +--rw mappings +--rw mapping* [eid-id] +--rw eid-id eid-id +--rw eid | +--rw address-type | | lisp-address-family-ref | +--rw (address)? | +--:(no-address) | | +--rw no-address? empty | +--:(ipv4) | | +--rw ipv4? | | inet:ipv4-address | +--:(ipv4-prefix) | | +--rw ipv4-prefix? Ermagan, et al. Expires 4 May 2027 [Page 19] Internet-Draft LISP-YANG October 2026 | | inet:ipv4-prefix | +--:(ipv6) | | +--rw ipv6? | | inet:ipv6-address | +--:(ipv6-prefix) | | +--rw ipv6-prefix? | | inet:ipv6-prefix | +--:(mac) | | +--rw mac? | | yang:mac-address | +--:(distinguished-name) | | +--rw distinguished-name? | | distinguished-name-type | +--:(as-number) | | +--rw as-number? | | inet:as-number | +--:(null-address) | | +--rw null-address | | +--rw address? empty | +--:(afi-list) | | +--rw afi-list | | +--rw address-list* simple-address | +--:(instance-id) | | +--rw instance-id | | +--rw instance-id? uint32 | | +--rw mask-length? uint8 | | +--rw address? simple-address | +--:(as-number-lcaf) | | +--rw as-number-lcaf | | +--rw as? inet:as-number | | +--rw address? ip-address-or-prefix | +--:(application-data) | | +--rw application-data | | +--rw address? | | | ip-address-or-prefix | | +--rw protocol? uint8 | | +--rw ip-tos? int32 | | +--rw local-port-low? | | | inet:port-number | | +--rw local-port-high? | | | inet:port-number | | +--rw remote-port-low? | | | inet:port-number | | +--rw remote-port-high? | | inet:port-number | +--:(geo-coordinates) | | +--rw geo-coordinates | | +--rw latitude? bits Ermagan, et al. Expires 4 May 2027 [Page 20] Internet-Draft LISP-YANG October 2026 | | +--rw latitude-degrees? uint8 | | +--rw latitude-minutes? uint8 | | +--rw latitude-seconds? uint8 | | +--rw longitude? bits | | +--rw longitude-degrees? uint16 | | +--rw longitude-minutes? uint8 | | +--rw longitude-seconds? uint8 | | +--rw altitude? int32 | | +--rw address? simple-address | +--:(nat-traversal) | | +--rw nat-traversal | | +--rw ms-udp-port? uint16 | | +--rw etr-udp-port? uint16 | | +--rw global-etr-rloc? | | | inet:ip-address | | +--rw ms-rloc? | | | inet:ip-address | | +--rw private-etr-rloc? | | | inet:ip-address | | +--rw rtr-rlocs* | | inet:ip-address | +--:(explicit-locator-path) | | +--rw explicit-locator-path | | +--rw hop* [hop-id] | | +--rw hop-id id-type | | +--rw address union | | +--rw lrs-bits? bits | +--:(source-dest-key) | | +--rw source-dest-key | | +--rw source ip-address-or-prefix | | +--rw dest ip-address-or-prefix | +--:(key-value-address) | +--rw key-value-address | +--rw key? simple-address | +--rw value? simple-address +--rw time-to-live? uint32 +--ro creation-time? yang:date-and-time +--rw authoritative? bits +--rw static? boolean +--rw (locator-list)? +--:(negative-mapping) | +--rw map-reply-action? map-reply-action +--:(positive-mapping) +--rw rlocs +--rw locator* [locator-id] +--rw locator-id | lisp-at:id-type +--rw locator-address Ermagan, et al. Expires 4 May 2027 [Page 21] Internet-Draft LISP-YANG October 2026 | +--rw address-type | | lisp-address-family-ref | +--rw (address)? | +--:(no-address) | | +--rw no-address? | | empty | +--:(ipv4) | | +--rw ipv4? | | inet:ipv4-address | +--:(ipv4-prefix) | | +--rw ipv4-prefix? | | inet:ipv4-prefix | +--:(ipv6) | | +--rw ipv6? | | inet:ipv6-address | +--:(ipv6-prefix) | | +--rw ipv6-prefix? | | inet:ipv6-prefix | +--:(mac) | | +--rw mac? | | yang:mac-address | +--:(distinguished-name) | | +--rw distinguished-name? | | distinguished-name-type | +--:(as-number) | | +--rw as-number? | | inet:as-number | +--:(null-address) | | +--rw null-address | | +--rw address? empty | +--:(afi-list) | | +--rw afi-list | | +--rw address-list* | | simple-address | +--:(instance-id) | | +--rw instance-id | | +--rw instance-id? | | | uint32 | | +--rw mask-length? uint8 | | +--rw address? | | simple-address | +--:(as-number-lcaf) | | +--rw as-number-lcaf | | +--rw as? | | | inet:as-number | | +--rw address? | | ip-address-or-prefix | +--:(application-data) Ermagan, et al. Expires 4 May 2027 [Page 22] Internet-Draft LISP-YANG October 2026 | | +--rw application-data | | +--rw address? | | | ip-address-or-prefix | | +--rw protocol? | | | uint8 | | +--rw ip-tos? | | | int32 | | +--rw local-port-low? | | | inet:port-number | | +--rw local-port-high? | | | inet:port-number | | +--rw remote-port-low? | | | inet:port-number | | +--rw remote-port-high? | | inet:port-number | +--:(geo-coordinates) | | +--rw geo-coordinates | | +--rw latitude? | | | bits | | +--rw latitude-degrees? | | | uint8 | | +--rw latitude-minutes? | | | uint8 | | +--rw latitude-seconds? | | | uint8 | | +--rw longitude? | | | bits | | +--rw longitude-degrees? | | | uint16 | | +--rw longitude-minutes? | | | uint8 | | +--rw longitude-seconds? | | | uint8 | | +--rw altitude? | | | int32 | | +--rw address? | | simple-address | +--:(nat-traversal) | | +--rw nat-traversal | | +--rw ms-udp-port? | | | uint16 | | +--rw etr-udp-port? | | | uint16 | | +--rw global-etr-rloc? | | | inet:ip-address | | +--rw ms-rloc? | | | inet:ip-address | | +--rw private-etr-rloc? Ermagan, et al. Expires 4 May 2027 [Page 23] Internet-Draft LISP-YANG October 2026 | | | inet:ip-address | | +--rw rtr-rlocs* | | inet:ip-address | +--:(explicit-locator-path) | | +--rw explicit-locator-path | | +--rw hop* [hop-id] | | +--rw hop-id id-type | | +--rw address | | | union | | +--rw lrs-bits? bits | +--:(source-dest-key) | | +--rw source-dest-key | | +--rw source | | | ip-address-or-prefix | | +--rw dest | | ip-address-or-prefix | +--:(key-value-address) | +--rw key-value-address | +--rw key? simple-address | +--rw value? simple-address +--rw priority? uint8 +--rw weight? uint8 +--rw multicast-priority? uint8 +--rw multicast-weight? uint8 3.2. Module Definition file "ietf-lisp-itr@2024-10-20.yang" module ietf-lisp-itr { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-itr"; prefix lisp-itr; // RFC Ed.: replace occurrences of XXXX with actual RFC number // and remove this note import ietf-lisp { prefix lisp; reference "RFC XXXX: LISP YANG model"; } import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-routing { prefix rt; Ermagan, et al. Expires 4 May 2027 [Page 24] Internet-Draft LISP-YANG October 2026 reference "RFC 8349: A YANG Data Model for Routing Management (NMDA version)"; } organization "IETF LISP (Locator/ID Separation Protocol) Working Group"; contact "WG Web: WG List: Editor: Vina Ermagan Editor: Alberto Rodriguez-Natal Editor: Reshad Rahman "; description "This YANG module defines the generic parameters for a LISP ITR. The module can be extended by vendors to define vendor-specific parameters and policies. Copyright (c) 2024 IETF Trust and the persons identified as 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; see the RFC itself for full legal notices. "; reference "RFC XXXX"; revision 2024-10-20 { description "Initial revision."; reference "RFC XXXX"; } augment "/rt:routing/rt:control-plane-protocols" Ermagan, et al. Expires 4 May 2027 [Page 25] Internet-Draft LISP-YANG October 2026 + "/rt:control-plane-protocol/lisp:lisp" { when "lisp:lisp-role/lisp:lisp-role-type = 'lisp:itr' or lisp:lisp-role/lisp:lisp-role-type = 'lisp:pitr'" { description "Augment is valid when LISP role type is ITR or PITR."; } description "This augments the LISP devices list with (P)ITR specific parameters."; container itr { presence "LISP (P)ITR operation enabled"; description "ITR parameters."; container rloc-probing { presence "RLOC probing active"; description "RLOC-probing parameters."; leaf interval { type uint16; units "seconds"; description "Interval in seconds for resending the probes."; } leaf retries { type uint8; description "Number of retries for sending the probes."; } leaf retries-interval { type uint16; units "seconds"; description "Interval in seconds between retries when sending probes. The action taken if all retries fail to receive is implementation specific."; } } leaf itr-rlocs { type leafref { path "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/lisp:lisp" + "/lisp:locator-sets/lisp:locator-set" + "/lisp:locator-set-name"; } description "Reference to a locator set that the (P)ITR includes in Map-Requests"; } Ermagan, et al. Expires 4 May 2027 [Page 26] Internet-Draft LISP-YANG October 2026 container map-resolvers { description "Map-Resolvers that the (P)ITR uses."; leaf-list map-resolver { type inet:ip-address; description "Each Map-Resolver within the list of Map-Resolvers."; } } container proxy-etrs { when "../../lisp:lisp-role/lisp:lisp-role-type='lisp:itr'" { description "Container exists only when LISP role type is ITR."; } description "Proxy ETRs that the ITR uses."; leaf-list proxy-etr-address { type inet:ip-address; description "Proxy ETR RLOC address."; } } container map-cache { leaf size { type uint32; config false; description "Current number of entries in the EID-to-RLOC map-cache."; } leaf limit { type uint32; config false; description "Maximum permissible number of entries in the EID-to-RLOC map-cache."; } uses lisp:mappings; description "EID to RLOCs mappings cache."; } } } } Ermagan, et al. Expires 4 May 2027 [Page 27] Internet-Draft LISP-YANG October 2026 4. LISP-ETR Module This module captures the configuration data model of a LISP (proxy) Egress Tunnel Router or (p)ETR. The model also captures some operational data elements. 4.1. Module Structure module: ietf-lisp-etr augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/lisp:lisp: +--rw etr! +--rw map-servers | +--rw map-server* [ms-address] | +--rw ms-address inet:ip-address | +--rw authentication-keys | +--rw authentication-key* [auth-key-id] | +--rw auth-key-id lisp-at:id-type | +--rw auth-algorithm-id* lisp:auth-algorithm-type | +--rw auth-key-value? string +--rw local-eids +--rw vpn* [instance-id] +--rw instance-id leafref +--rw eids +--rw local-eid* [eid-id] +--rw eid-id lisp:eid-id +--rw eid-address | +--rw address-type | | lisp-address-family-ref | +--rw (address)? | +--:(no-address) | | +--rw no-address? empty | +--:(ipv4) | | +--rw ipv4? | | inet:ipv4-address | +--:(ipv4-prefix) | | +--rw ipv4-prefix? | | inet:ipv4-prefix | +--:(ipv6) | | +--rw ipv6? | | inet:ipv6-address | +--:(ipv6-prefix) | | +--rw ipv6-prefix? | | inet:ipv6-prefix | +--:(mac) | | +--rw mac? | | yang:mac-address Ermagan, et al. Expires 4 May 2027 [Page 28] Internet-Draft LISP-YANG October 2026 | +--:(distinguished-name) | | +--rw distinguished-name? | | distinguished-name-type | +--:(as-number) | | +--rw as-number? | | inet:as-number | +--:(null-address) | | +--rw null-address | | +--rw address? empty | +--:(afi-list) | | +--rw afi-list | | +--rw address-list* simple-address | +--:(instance-id) | | +--rw instance-id | | +--rw instance-id? uint32 | | +--rw mask-length? uint8 | | +--rw address? simple-address | +--:(as-number-lcaf) | | +--rw as-number-lcaf | | +--rw as? inet:as-number | | +--rw address? ip-address-or-prefix | +--:(application-data) | | +--rw application-data | | +--rw address? | | | ip-address-or-prefix | | +--rw protocol? uint8 | | +--rw ip-tos? int32 | | +--rw local-port-low? | | | inet:port-number | | +--rw local-port-high? | | | inet:port-number | | +--rw remote-port-low? | | | inet:port-number | | +--rw remote-port-high? | | inet:port-number | +--:(geo-coordinates) | | +--rw geo-coordinates | | +--rw latitude? bits | | +--rw latitude-degrees? uint8 | | +--rw latitude-minutes? uint8 | | +--rw latitude-seconds? uint8 | | +--rw longitude? bits | | +--rw longitude-degrees? uint16 | | +--rw longitude-minutes? uint8 | | +--rw longitude-seconds? uint8 | | +--rw altitude? int32 | | +--rw address? simple-address | +--:(nat-traversal) Ermagan, et al. Expires 4 May 2027 [Page 29] Internet-Draft LISP-YANG October 2026 | | +--rw nat-traversal | | +--rw ms-udp-port? uint16 | | +--rw etr-udp-port? uint16 | | +--rw global-etr-rloc? | | | inet:ip-address | | +--rw ms-rloc? | | | inet:ip-address | | +--rw private-etr-rloc? | | | inet:ip-address | | +--rw rtr-rlocs* | | inet:ip-address | +--:(explicit-locator-path) | | +--rw explicit-locator-path | | +--rw hop* [hop-id] | | +--rw hop-id id-type | | +--rw address union | | +--rw lrs-bits? bits | +--:(source-dest-key) | | +--rw source-dest-key | | +--rw source ip-address-or-prefix | | +--rw dest ip-address-or-prefix | +--:(key-value-address) | +--rw key-value-address | +--rw key? simple-address | +--rw value? simple-address +--rw rlocs? leafref +--rw record-ttl? uint32 +--rw want-map-notify? boolean +--rw proxy-reply? boolean +--rw registration-interval? uint16 4.2. Module Definition file "ietf-lisp-etr@2024-10-20.yang" module ietf-lisp-etr { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-etr"; prefix lisp-etr; // RFC Ed.: replace occurrences of XXXX with actual RFC number // and remove this note import ietf-lisp { prefix lisp; reference "RFC XXXX: LISP YANG model"; } import ietf-lisp-address-types { Ermagan, et al. Expires 4 May 2027 [Page 30] Internet-Draft LISP-YANG October 2026 prefix lisp-at; reference "RFC XXXX: LISP YANG model"; } import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-routing { prefix "rt"; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA version)"; } organization "IETF LISP (Locator/ID Separation Protocol) Working Group"; contact "WG Web: WG List: Editor: Vina Ermagan Editor: Alberto Rodriguez-Natal Editor: Reshad Rahman "; description "This YANG module defines the generic parameters for a LISP ETR. The module can be extended by vendors to define vendor-specific parameters and policies. Copyright (c) 2024 IETF Trust and the persons identified as 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; see the RFC itself for full legal notices. "; reference "RFC XXXX"; Ermagan, et al. Expires 4 May 2027 [Page 31] Internet-Draft LISP-YANG October 2026 revision 2024-10-20 { description "Initial revision."; reference "RFC XXXX"; } augment "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/lisp:lisp" { when "lisp:lisp-role/lisp:lisp-role-type = 'lisp:etr' or lisp:lisp-role/lisp:lisp-role-type = 'lisp:petr'" { description "Augment is valid when LISP device type is (P)ETR."; } description "This augments the LISP devices list with (P)ETR specific parameters."; container etr { presence "LISP (P)ETR operation enabled"; description "(P)ETR parameters."; container map-servers { when "../../lisp:lisp-role/lisp:lisp-role-type='lisp:etr'" { description "Container exists only when LISP device type is ETR."; } description "Map-Servers that the ETR uses."; list map-server { key "ms-address"; description "Each Map-Server within the list of Map-Servers."; leaf ms-address { type inet:ip-address; description "Map-Server address."; } uses lisp:auth-key; } } container local-eids { when "../../lisp:lisp-role/lisp:lisp-role-type='lisp:etr'" { description "Container exists only when LISP device type is ETR."; } description "VPNs served by the ETR."; Ermagan, et al. Expires 4 May 2027 [Page 32] Internet-Draft LISP-YANG October 2026 list vpn { key "instance-id"; description "VPN for local-EIDs."; leaf instance-id { type leafref { path "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/lisp:lisp" + "/lisp:vpns/lisp:vpn" + "/lisp:instance-id"; } description "VPN identifier."; } container eids { description "EIDs served by the ETR."; list local-eid { key "eid-id"; description "List of local EIDs."; leaf eid-id { type lisp:eid-id; description "Unique id of local EID."; } container eid-address { uses lisp-at:lisp-address; description "EID address in generic LISP address format."; } leaf rlocs { type leafref { path "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/lisp:lisp" + "/lisp:locator-sets/lisp:locator-set" + "/lisp:locator-set-name"; } description "Locator set mapped to this local EID."; } leaf record-ttl { type uint32; units minutes; description "Validity period of the EID to RLOCs mapping provided in Map-Replies."; } Ermagan, et al. Expires 4 May 2027 [Page 33] Internet-Draft LISP-YANG October 2026 leaf want-map-notify { type boolean; default "true"; description "Flag which if set in a Map-Register requests that a Map-Notify be sent in response."; } leaf proxy-reply { type boolean; default "false"; description "Flag which if set in a Map-Register requests that the Map-Server proxy Map-Replies for the ETR."; } leaf registration-interval { type uint16; units "seconds"; default "60"; description "Interval between consecutive Map-Registers."; } } } } } } } } 5. LISP-Map-Server Module This module captures the configuration data model of a LISP Map Server [RFC9301]. The model also captures some operational data elements. 5.1. Module Structure module: ietf-lisp-mapserver augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/lisp:lisp: +--rw map-server! +--rw sites | +--rw site* [site-id] | +--rw site-id uint64 | +--rw authentication-keys | | +--rw authentication-key* [auth-key-id] Ermagan, et al. Expires 4 May 2027 [Page 34] Internet-Draft LISP-YANG October 2026 | | +--rw auth-key-id lisp-at:id-type | | +--rw auth-algorithm-id* lisp:auth-algorithm-type | | +--rw auth-key-value? string | +--rw xtr-ids* [xtr-id] | +--rw xtr-id uint64 | +--rw authentication-keys | +--rw authentication-key* [auth-key-id] | +--rw auth-key-id lisp-at:id-type | +--rw auth-algorithm-id* | | lisp:auth-algorithm-type | +--rw auth-key-value? string +--rw vpns | +--rw vpn* [instance-id] | +--rw instance-id lisp-at:instance-id-type | +--rw mappings | | +--rw mapping* [eid-id] | | +--rw eid-id lisp:eid-id | | +--rw eid-address | | | +--rw address-type | | | | lisp-address-family-ref | | | +--rw (address)? | | | +--:(no-address) | | | | +--rw no-address? empty | | | +--:(ipv4) | | | | +--rw ipv4? | | | | inet:ipv4-address | | | +--:(ipv4-prefix) | | | | +--rw ipv4-prefix? | | | | inet:ipv4-prefix | | | +--:(ipv6) | | | | +--rw ipv6? | | | | inet:ipv6-address | | | +--:(ipv6-prefix) | | | | +--rw ipv6-prefix? | | | | inet:ipv6-prefix | | | +--:(mac) | | | | +--rw mac? | | | | yang:mac-address | | | +--:(distinguished-name) | | | | +--rw distinguished-name? | | | | distinguished-name-type | | | +--:(as-number) | | | | +--rw as-number? | | | | inet:as-number | | | +--:(null-address) | | | | +--rw null-address | | | | +--rw address? empty | | | +--:(afi-list) Ermagan, et al. Expires 4 May 2027 [Page 35] Internet-Draft LISP-YANG October 2026 | | | | +--rw afi-list | | | | +--rw address-list* simple-address | | | +--:(instance-id) | | | | +--rw instance-id | | | | +--rw instance-id? uint32 | | | | +--rw mask-length? uint8 | | | | +--rw address? simple-address | | | +--:(as-number-lcaf) | | | | +--rw as-number-lcaf | | | | +--rw as? inet:as-number | | | | +--rw address? ip-address-or-prefix | | | +--:(application-data) | | | | +--rw application-data | | | | +--rw address? | | | | | ip-address-or-prefix | | | | +--rw protocol? uint8 | | | | +--rw ip-tos? int32 | | | | +--rw local-port-low? | | | | | inet:port-number | | | | +--rw local-port-high? | | | | | inet:port-number | | | | +--rw remote-port-low? | | | | | inet:port-number | | | | +--rw remote-port-high? | | | | inet:port-number | | | +--:(geo-coordinates) | | | | +--rw geo-coordinates | | | | +--rw latitude? bits | | | | +--rw latitude-degrees? uint8 | | | | +--rw latitude-minutes? uint8 | | | | +--rw latitude-seconds? uint8 | | | | +--rw longitude? bits | | | | +--rw longitude-degrees? uint16 | | | | +--rw longitude-minutes? uint8 | | | | +--rw longitude-seconds? uint8 | | | | +--rw altitude? int32 | | | | +--rw address? simple-address | | | +--:(nat-traversal) | | | | +--rw nat-traversal | | | | +--rw ms-udp-port? uint16 | | | | +--rw etr-udp-port? uint16 | | | | +--rw global-etr-rloc? | | | | | inet:ip-address | | | | +--rw ms-rloc? | | | | | inet:ip-address | | | | +--rw private-etr-rloc? | | | | | inet:ip-address | | | | +--rw rtr-rlocs* Ermagan, et al. Expires 4 May 2027 [Page 36] Internet-Draft LISP-YANG October 2026 | | | | inet:ip-address | | | +--:(explicit-locator-path) | | | | +--rw explicit-locator-path | | | | +--rw hop* [hop-id] | | | | +--rw hop-id id-type | | | | +--rw address union | | | | +--rw lrs-bits? bits | | | +--:(source-dest-key) | | | | +--rw source-dest-key | | | | +--rw source ip-address-or-prefix | | | | +--rw dest ip-address-or-prefix | | | +--:(key-value-address) | | | +--rw key-value-address | | | +--rw key? simple-address | | | +--rw value? simple-address | | +--rw site-id* uint64 | | +--rw more-specifics-accepted? boolean | | +--rw mapping-expiration-timeout? int16 | | +--ro first-registration-time? | | | yang:date-and-time | | +--ro last-registration-time? | | | yang:date-and-time | | +--rw mapping-records | | +--rw mapping-record* [xtr-id] | | +--rw xtr-id | | | lisp:xtr-id-type | | +--rw site-id? uint64 | | +--rw eid | | | +--rw address-type | | | | lisp-address-family-ref | | | +--rw (address)? | | | +--:(no-address) | | | | +--rw no-address? empty | | | +--:(ipv4) | | | | +--rw ipv4? | | | | inet:ipv4-address | | | +--:(ipv4-prefix) | | | | +--rw ipv4-prefix? | | | | inet:ipv4-prefix | | | +--:(ipv6) | | | | +--rw ipv6? | | | | inet:ipv6-address | | | +--:(ipv6-prefix) | | | | +--rw ipv6-prefix? | | | | inet:ipv6-prefix | | | +--:(mac) | | | | +--rw mac? | | | | yang:mac-address Ermagan, et al. Expires 4 May 2027 [Page 37] Internet-Draft LISP-YANG October 2026 | | | +--:(distinguished-name) | | | | +--rw distinguished-name? | | | | distinguished-name-type | | | +--:(as-number) | | | | +--rw as-number? | | | | inet:as-number | | | +--:(null-address) | | | | +--rw null-address | | | | +--rw address? empty | | | +--:(afi-list) | | | | +--rw afi-list | | | | +--rw address-list* | | | | simple-address | | | +--:(instance-id) | | | | +--rw instance-id | | | | +--rw instance-id? | | | | | uint32 | | | | +--rw mask-length? uint8 | | | | +--rw address? simple-address | | | +--:(as-number-lcaf) | | | | +--rw as-number-lcaf | | | | +--rw as? inet:as-number | | | | +--rw address? | | | | ip-address-or-prefix | | | +--:(application-data) | | | | +--rw application-data | | | | +--rw address? | | | | | ip-address-or-prefix | | | | +--rw protocol? uint8 | | | | +--rw ip-tos? int32 | | | | +--rw local-port-low? | | | | | inet:port-number | | | | +--rw local-port-high? | | | | | inet:port-number | | | | +--rw remote-port-low? | | | | | inet:port-number | | | | +--rw remote-port-high? | | | | inet:port-number | | | +--:(geo-coordinates) | | | | +--rw geo-coordinates | | | | +--rw latitude? bits | | | | +--rw latitude-degrees? uint8 | | | | +--rw latitude-minutes? uint8 | | | | +--rw latitude-seconds? uint8 | | | | +--rw longitude? bits | | | | +--rw longitude-degrees? uint16 | | | | +--rw longitude-minutes? uint8 | | | | +--rw longitude-seconds? uint8 Ermagan, et al. Expires 4 May 2027 [Page 38] Internet-Draft LISP-YANG October 2026 | | | | +--rw altitude? int32 | | | | +--rw address? | | | | simple-address | | | +--:(nat-traversal) | | | | +--rw nat-traversal | | | | +--rw ms-udp-port? uint16 | | | | +--rw etr-udp-port? uint16 | | | | +--rw global-etr-rloc? | | | | | inet:ip-address | | | | +--rw ms-rloc? | | | | | inet:ip-address | | | | +--rw private-etr-rloc? | | | | | inet:ip-address | | | | +--rw rtr-rlocs* | | | | inet:ip-address | | | +--:(explicit-locator-path) | | | | +--rw explicit-locator-path | | | | +--rw hop* [hop-id] | | | | +--rw hop-id id-type | | | | +--rw address union | | | | +--rw lrs-bits? bits | | | +--:(source-dest-key) | | | | +--rw source-dest-key | | | | +--rw source | | | | | ip-address-or-prefix | | | | +--rw dest | | | | ip-address-or-prefix | | | +--:(key-value-address) | | | +--rw key-value-address | | | +--rw key? simple-address | | | +--rw value? simple-address | | +--rw time-to-live? uint32 | | +--ro creation-time? | | | yang:date-and-time | | +--rw authoritative? bits | | +--rw static? boolean | | +--rw (locator-list)? | | +--:(negative-mapping) | | | +--rw map-reply-action? | | | map-reply-action | | +--:(positive-mapping) | | +--rw rlocs | | +--rw locator* [locator-id] | | +--rw locator-id | | | lisp-at:id-type | | +--rw locator-address | | | +--rw address-type | | | | lisp-address-family-ref Ermagan, et al. Expires 4 May 2027 [Page 39] Internet-Draft LISP-YANG October 2026 | | | +--rw (address)? | | | +--:(no-address) | | | | +--rw no-address? | | | | empty | | | +--:(ipv4) | | | | +--rw ipv4? | | | | inet:ipv4-address | | | +--:(ipv4-prefix) | | | | +--rw ipv4-prefix? | | | | inet:ipv4-prefix | | | +--:(ipv6) | | | | +--rw ipv6? | | | | inet:ipv6-address | | | +--:(ipv6-prefix) | | | | +--rw ipv6-prefix? | | | | inet:ipv6-prefix | | | +--:(mac) | | | | +--rw mac? | | | | yang:mac-address | | | +--:(distinguished-name) | | | | +--rw distinguished-name? | | | | distinguished-name-type | | | +--:(as-number) | | | | +--rw as-number? | | | | inet:as-number | | | +--:(null-address) | | | | +--rw null-address | | | | +--rw address? empty | | | +--:(afi-list) | | | | +--rw afi-list | | | | +--rw address-list* | | | | simple-address | | | +--:(instance-id) | | | | +--rw instance-id | | | | +--rw instance-id? | | | | | uint32 | | | | +--rw mask-length? | | | | | uint8 | | | | +--rw address? | | | | simple-address | | | +--:(as-number-lcaf) | | | | +--rw as-number-lcaf | | | | +--rw as? | | | | | inet:as-number | | | | +--rw address? | | | | ip-address-or-prefix | | | +--:(application-data) | | | | +--rw application-data Ermagan, et al. Expires 4 May 2027 [Page 40] Internet-Draft LISP-YANG October 2026 | | | | +--rw address? | | | | | ip-address-or-prefix | | | | +--rw protocol? | | | | | uint8 | | | | +--rw ip-tos? | | | | | int32 | | | | +--rw local-port-low? | | | | | inet:port-number | | | | +--rw local-port-high? | | | | | inet:port-number | | | | +--rw remote-port-low? | | | | | inet:port-number | | | | +--rw remote-port-high? | | | | inet:port-number | | | +--:(geo-coordinates) | | | | +--rw geo-coordinates | | | | +--rw latitude? | | | | | bits | | | | +--rw latitude-degrees? | | | | | uint8 | | | | +--rw latitude-minutes? | | | | | uint8 | | | | +--rw latitude-seconds? | | | | | uint8 | | | | +--rw longitude? | | | | | bits | | | | +--rw longitude-degrees? | | | | | uint16 | | | | +--rw longitude-minutes? | | | | | uint8 | | | | +--rw longitude-seconds? | | | | | uint8 | | | | +--rw altitude? | | | | | int32 | | | | +--rw address? | | | | simple-address | | | +--:(nat-traversal) | | | | +--rw nat-traversal | | | | +--rw ms-udp-port? | | | | | uint16 | | | | +--rw etr-udp-port? | | | | | uint16 | | | | +--rw global-etr-rloc? | | | | | inet:ip-address | | | | +--rw ms-rloc? | | | | | inet:ip-address | | | | +--rw private-etr-rloc? | | | | | inet:ip-address Ermagan, et al. Expires 4 May 2027 [Page 41] Internet-Draft LISP-YANG October 2026 | | | | +--rw rtr-rlocs* | | | | inet:ip-address | | | +--:(explicit-locator-path) | | | | +--rw explicit-locator-path | | | | +--rw hop* [hop-id] | | | | +--rw hop-id | | | | | id-type | | | | +--rw address | | | | | union | | | | +--rw lrs-bits? | | | | bits | | | +--:(source-dest-key) | | | | +--rw source-dest-key | | | | +--rw source | | | | | ip-address-or-prefix | | | | +--rw dest | | | | ip-address-or-prefix | | | +--:(key-value-address) | | | +--rw key-value-address | | | +--rw key? | | | | simple-address | | | +--rw value? | | | simple-address | | +--rw priority? uint8 | | +--rw weight? uint8 | | +--rw multicast-priority? uint8 | | +--rw multicast-weight? uint8 | +--ro counters | +--ro discontinuity-time yang:date-and-time | +--ro map-registers-in? yang:counter64 | +--ro map-registers-in-auth-failed? yang:counter64 | +--ro map-notify-records-out? yang:counter64 | +--ro proxy-reply-records-out? yang:counter64 | +--ro map-requests-forwarded-out? yang:counter64 +--rw mapping-system-type? lisp:mapping-system-ref +--ro summary | +--ro number-configured-sites? uint32 | +--ro number-registered-sites? uint32 | +--ro af-datum | +--ro af-data* [address-type] | +--ro address-type | | lisp-at:lisp-address-family-ref | +--ro number-configured-eids? uint32 | +--ro number-registered-eids? uint32 +--ro counters +--ro discontinuity-time yang:date-and-time +--ro map-registers-in? yang:counter64 +--ro map-registers-in-auth-failed? yang:counter64 Ermagan, et al. Expires 4 May 2027 [Page 42] Internet-Draft LISP-YANG October 2026 +--ro map-notify-records-out? yang:counter64 +--ro proxy-reply-records-out? yang:counter64 +--ro map-requests-forwarded-out? yang:counter64 5.2. Module Definition file "ietf-lisp-mapserver@2024-10-20.yang" module ietf-lisp-mapserver { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-mapserver"; prefix lisp-ms; // RFC Ed.: replace occurrences of XXXX with actual RFC number // and remove this note import ietf-lisp { prefix lisp; reference "RFC XXXX: LISP YANG model"; } import ietf-lisp-address-types { prefix lisp-at; reference "RFC XXXX: LISP YANG model"; } import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Data Types"; } import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA version)"; } organization "IETF LISP (Locator/ID Separation Protocol) Working Group"; contact "WG Web: WG List: Editor: Vina Ermagan Editor: Alberto Rodriguez-Natal Ermagan, et al. Expires 4 May 2027 [Page 43] Internet-Draft LISP-YANG October 2026 Editor: Reshad Rahman "; description "This YANG module defines the generic parameters for a LISP Map-Server. The module can be extended by vendors to define vendor-specific parameters and policies. Copyright (c) 2024 IETF Trust and the persons identified as 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; see the RFC itself for full legal notices. "; reference "RFC XXXX"; revision 2024-10-20 { description "Initial revision."; reference "RFC XXXX"; } identity ms { base lisp:lisp-role; description "LISP Map-Server."; } grouping ms-counters { description "Grouping that defines map-server counters."; container counters { config false; description "Container for the counters."; leaf discontinuity-time { type yang:date-and-time; mandatory true; description "The time on the most recent occasion at which any Ermagan, et al. Expires 4 May 2027 [Page 44] Internet-Draft LISP-YANG October 2026 of these counters suffered a discontinuity."; } leaf map-registers-in { type yang:counter64; description "Number of incoming Map-Register messages."; } leaf map-registers-in-auth-failed { type yang:counter64; description "Number of incoming Map-Register messages failed authentication."; } leaf map-notify-records-out { type yang:counter64; description "Number of outgoing Map-Notify records."; } leaf proxy-reply-records-out { type yang:counter64; description "Number of outgoing proxy Map-Reply records."; } leaf map-requests-forwarded-out { type yang:counter64; description "Number of outgoing Map-Requests forwarded to ETR."; } } } augment "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/lisp:lisp" { when "lisp:lisp-role/lisp:lisp-role-type = 'lisp-ms:ms'" { description "Augment is valid when LISP device type is Map-Server."; } description "This augments the LISP devices list with Map-Server specific parameters."; container map-server { presence "LISP Map-Server operation enabled"; description "Map-Server parameters."; container sites { description "Sites to accept registrations from."; list site { Ermagan, et al. Expires 4 May 2027 [Page 45] Internet-Draft LISP-YANG October 2026 key "site-id"; description "Site that can send registrations."; leaf site-id { type uint64; description "Site ID."; } uses lisp:auth-key; list xtr-ids { key "xtr-id"; description "xTR-ID specific configuration."; leaf xtr-id { type uint64; description "xTR ID."; } uses lisp:auth-key; } } } container vpns { description "VPNs for which the Map-Server accepts registrations."; list vpn { key "instance-id"; description "VPN instances in the Map-Server."; leaf instance-id { type lisp-at:instance-id-type; description "VPN identifier."; } container mappings { description "EIDs registered by device."; list mapping { key "eid-id"; description "List of EIDs registered by device."; leaf eid-id { type lisp:eid-id; description "Id of the EID registered."; } container eid-address { uses lisp-at:lisp-address; Ermagan, et al. Expires 4 May 2027 [Page 46] Internet-Draft LISP-YANG October 2026 description "EID in generic LISP address format registered with the Map-Server."; } leaf-list site-id { type uint64; description "Site ID."; } leaf more-specifics-accepted { type boolean; default "false"; description "Flag indicating if more specific prefixes can be registered."; } leaf mapping-expiration-timeout { type int16; units "seconds"; default "180"; //3 times the mapregister int description "Time before mapping is expired if no new registrations are received."; } leaf first-registration-time { type yang:date-and-time; config false; description "Time at which the first registration for this EID was received."; } leaf last-registration-time { type yang:date-and-time; config false; description "Time at which the last registration for this EID was received."; } container mapping-records { description "Datastore of registered mappings."; list mapping-record { key "xtr-id"; description "Registered mapping."; leaf xtr-id { type lisp:xtr-id-type; description Ermagan, et al. Expires 4 May 2027 [Page 47] Internet-Draft LISP-YANG October 2026 "xTR ID."; } leaf site-id { type uint64; description "Site ID."; } uses lisp:mapping; } } } } uses ms-counters; } } leaf mapping-system-type { type lisp:mapping-system-ref; description "A reference to the mapping system."; } container summary { config false; description "Summary state information."; leaf number-configured-sites { type uint32; description "Number of configured LISP site.s"; } leaf number-registered-sites { type uint32; description "Number of registered LISP sites."; } container af-datum { description "Number of configured EIDs per each AF."; list af-data { key "address-type"; description "Number of configured EIDs for this AF."; leaf address-type { type lisp-at:lisp-address-family-ref; description "AF type."; } leaf number-configured-eids { type uint32; Ermagan, et al. Expires 4 May 2027 [Page 48] Internet-Draft LISP-YANG October 2026 description "Number of configured EIDs for this AF."; } leaf number-registered-eids { type uint32; description "Number of registered EIDs for this AF."; } } } } uses ms-counters; } } } 6. LISP-Map-Resolver Module This module captures the configuration data model of a LISP Map Resolver [RFC9301]. The model also captures some operational data elements. 6.1. Module Structure module: ietf-lisp-mapresolver augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/lisp:lisp: +--rw map-resolver! +--rw mapping-system-type? lisp:mapping-system-ref +--rw ms-address? inet:ip-address 6.2. Module Definition file "ietf-lisp-mapresolver@2024-10-20.yang" module ietf-lisp-mapresolver { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-mapresolver"; prefix lisp-mr; // RFC Ed.: replace occurrences of XXXX with actual RFC number // and remove this note import ietf-lisp { prefix lisp; reference "RFC XXXX: LISP YANG model"; Ermagan, et al. Expires 4 May 2027 [Page 49] Internet-Draft LISP-YANG October 2026 } import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA version)"; } organization "IETF LISP (Locator/ID Separation Protocol) Working Group"; contact "WG Web: WG List: Editor: Vina Ermagan Editor: Alberto Rodriguez-Natal Editor: Reshad Rahman "; description "This YANG module defines the generic parameters for a LISP Map-Resolver. The module can be extended by vendors to define vendor-specific parameters and policies. Copyright (c) 2024 IETF Trust and the persons identified as 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; see the RFC itself for full legal notices. "; reference "RFC XXXX"; Ermagan, et al. Expires 4 May 2027 [Page 50] Internet-Draft LISP-YANG October 2026 revision 2024-10-20 { description "Initial revision."; reference "RFC XXXX"; } identity mr { base lisp:lisp-role; description "LISP Map-Resolver."; } augment "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/lisp:lisp" { when "lisp:lisp-role/lisp:lisp-role-type = 'lisp-mr:mr'" { description "Augment is valid when LISP device type is Map-Resolver."; } description "This augments the LISP devices list with Map-Resolver specific parameters."; container map-resolver { presence "LISP Map-Resolver operation enabled"; description "Map-Resolver parameters."; leaf mapping-system-type { type lisp:mapping-system-ref; description "A reference to the mapping system."; } leaf ms-address { when "../mapping-system-type=" + "'lisp:single-node-mapping-system'"; type inet:ip-address; description "Address to reach the Map-Server when lisp-mr:single-node-mapping-system is being used."; } } } } 7. LISP-Address-Types Module This module captures the various LISP address types, and is an essential building block used in other LISP modules. Ermagan, et al. Expires 4 May 2027 [Page 51] Internet-Draft LISP-YANG October 2026 7.1. Module Definition file "ietf-lisp-address-types@2026-10-31.yang" module ietf-lisp-address-types { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-address-types"; prefix laddr; import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Data Types"; } organization "IETF LISP (Locator/ID Separation Protocol) Working Group"; contact "WG Web: WG List: Editor: Vina Ermagan Editor: Alberto Rodriguez-Natal Editor: Reshad Rahman "; description "This YANG module defines the LISP Canonical Address Formats (LCAF) for LISP. The module can be extended by vendors to define vendor-specific parameters. Copyright (c) 2026 IETF Trust and the persons identified as 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). Ermagan, et al. Expires 4 May 2027 [Page 52] Internet-Draft LISP-YANG October 2026 This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices. "; // RFC Ed.: replace XXXX with actual RFC number and remove // this note reference "RFC XXXX"; revision 2026-10-31 { description "Initial revision."; reference "RFC XXXX"; } identity lisp-address-family { description "Base identity from which identities describing LISP address families are derived."; } identity no-address-afi { base lisp-address-family; description "IANA Reserved."; } identity ipv4-afi { base lisp-address-family; description "IANA IPv4 address family."; } identity ipv4-prefix-afi { base lisp-address-family; description "IANA IPv4 address family prefix."; } identity ipv6-afi { base lisp-address-family; description "IANA IPv6 address family."; } Ermagan, et al. Expires 4 May 2027 [Page 53] Internet-Draft LISP-YANG October 2026 identity ipv6-prefix-afi { base lisp-address-family; description "IANA IPv6 address family prefix."; } identity mac-afi { base lisp-address-family; description "IANA MAC address family."; } identity distinguished-name-afi { base lisp-address-family; description "IANA Distinguished Name address family."; } identity as-number-afi { base lisp-address-family; description "IANA AS Number address family."; } identity lcaf { base lisp-address-family; description "IANA LISP Canonical Address Format address family."; } identity null-address-lcaf { base lcaf; description "Null body LCAF type."; } identity afi-list-lcaf { base lcaf; description "AFI-List LCAF type."; } identity instance-id-lcaf { base lcaf; description "Instance-ID LCAF type."; } Ermagan, et al. Expires 4 May 2027 [Page 54] Internet-Draft LISP-YANG October 2026 identity as-number-lcaf { base lcaf; description "AS Number LCAF type."; } identity application-data-lcaf { base lcaf; description "Application Data LCAF type."; } identity opaque-key-lcaf { base lcaf; description "Opaque Key LCAF type."; } identity nat-traversal-lcaf { base lcaf; description "NAT-Traversal LCAF type."; } identity nonce-locator-lcaf { base lcaf; description "Nonce-Locator LCAF type."; } identity multicast-info-lcaf { base lcaf; description "Multicast Info LCAF type."; } identity explicit-locator-path-lcaf { base lcaf; description "Explicit Locator Path LCAF type."; } identity security-key-lcaf { base lcaf; description "Security Key LCAF type."; } Ermagan, et al. Expires 4 May 2027 [Page 55] Internet-Draft LISP-YANG October 2026 identity source-dest-key-lcaf { base lcaf; description "Source/Dest LCAF type."; } identity replication-list-lcaf { base lcaf; description "Replication-List LCAF type."; } identity json-data-model-lcaf { base lcaf; description "JSON Data Model LCAF type."; } identity key-value-address-lcaf { base lcaf; description "Key/Value Address LCAF type."; } identity encapsulation-format-lcaf { base lcaf; description "Encapsulation Format LCAF type."; } identity vendor-specific-lcaf { base lcaf; description "Vendor-Specific LCAF type."; } typedef instance-id-type { type uint32 { range "0..16777215"; } description "Defines the range of values for an Instance ID."; } typedef distinguished-name-type { type string; description "Distinguished Name address."; Ermagan, et al. Expires 4 May 2027 [Page 56] Internet-Draft LISP-YANG October 2026 reference "http://www.iana.org/assignments/address-family-numbers/ address-family-numbers.xhtml"; } typedef ip-address-or-prefix { type union { type inet:ip-address; type inet:ip-prefix; } description "An IPv4 or IPv6 address or prefix."; } typedef simple-address { type union { type inet:ip-address; type inet:ip-prefix; type yang:mac-address; type distinguished-name-type; type inet:as-number; } description "Union of address types that can be part of LCAFs."; } typedef lisp-address-family-ref { type identityref { base lisp-address-family; } description "LISP address family reference."; } typedef lcaf-ref { type identityref { base lcaf; } description "LCAF types reference."; } typedef id-type { type string { length "1..64"; pattern '[a-zA-Z0-9][a-zA-Z0-9\-_.:]*'; } description Ermagan, et al. Expires 4 May 2027 [Page 57] Internet-Draft LISP-YANG October 2026 "Pattern and length for general ids."; } grouping lisp-address { description "Generic LISP address."; leaf address-type { type lisp-address-family-ref; mandatory true; description "Type of the LISP address."; } choice address { description "Various LISP address types, including IP, MAC, and LCAF."; leaf no-address { when "../address-type = 'laddr:no-address-afi'" { description "When AFI is 0."; } type empty; description "No address."; } leaf ipv4 { when "../address-type = 'laddr:ipv4-afi'" { description "When AFI is IPv4."; } type inet:ipv4-address; description "IPv4 address."; } leaf ipv4-prefix { when "../address-type = 'laddr:ipv4-prefix-afi'" { description "When AFI is IPv4."; } type inet:ipv4-prefix; description "IPv4 prefix."; } leaf ipv6 { when "../address-type = 'laddr:ipv6-afi'" { description "When AFI is IPv6."; } type inet:ipv6-address; Ermagan, et al. Expires 4 May 2027 [Page 58] Internet-Draft LISP-YANG October 2026 description "IPv6 address."; } leaf ipv6-prefix { when "../address-type = 'laddr:ipv6-prefix-afi'" { description "When AFI is IPv6."; } type inet:ipv6-prefix; description "IPv6 address."; } leaf mac { when "../address-type = 'laddr:mac-afi'" { description "When AFI is MAC."; } type yang:mac-address; description "MAC address."; } leaf distinguished-name { when "../address-type = 'laddr:distinguished-name-afi'" { description "When AFI is distinguished-name."; } type distinguished-name-type; description "Distinguished Name address."; } leaf as-number { when "../address-type = 'laddr:as-number-afi'" { description "When AFI is as-number."; } type inet:as-number; description "AS Number."; } container null-address { when "../address-type = 'laddr:null-address-lcaf'" { description "When LCAF type is null."; } description "Null body LCAF type"; leaf address { type empty; Ermagan, et al. Expires 4 May 2027 [Page 59] Internet-Draft LISP-YANG October 2026 description "AFI address."; } } container afi-list { when "../address-type = 'laddr:afi-list-lcaf'" { description "When LCAF type is AFI-List."; } description "AFI-List LCAF type."; reference "RC8060: LISP Canonical Address Format (LCAF) #section-4.10"; leaf-list address-list { type simple-address; description "List of AFI addresses."; } } container instance-id { when "../address-type = 'laddr:instance-id-lcaf'" { description "When LCAF type is Instance ID as per RFC8060."; } description "Instance ID LCAF type."; reference "RC8060: LISP Canonical Address Format (LCAF) #section-4.1"; leaf instance-id { type uint32; description "32-bit LCAF Instance ID."; } leaf mask-length { type uint8 { range "0..32"; } default "0"; description "Mask length."; } leaf address { type simple-address; description "AFI address."; } Ermagan, et al. Expires 4 May 2027 [Page 60] Internet-Draft LISP-YANG October 2026 } container as-number-lcaf { when "../address-type = 'laddr:as-number-lcaf'" { description "When LCAF type is AS-Number."; } description "AS Number LCAF type."; reference "RC8060: LISP Canonical Address Format (LCAF) #section-4.2"; leaf as { type inet:as-number; description "AS number."; } leaf address { type ip-address-or-prefix; description "IPv4 or IPv6 address or prefix."; } } container application-data { when "../address-type = 'laddr:application-data-lcaf'" { description "When LCAF type is Application Data."; } description "Application Data LCAF type."; reference "RC8060: LISP Canonical Address Format (LCAF) #section-5.1"; leaf address { type ip-address-or-prefix; description "IPv4 or IPv6 address or prefix."; } leaf protocol { type uint8 { range "6 | 17 | 132"; } description "Protocol number."; } leaf ip-tos { type int32 { range "0..1048575"; } Ermagan, et al. Expires 4 May 2027 [Page 61] Internet-Draft LISP-YANG October 2026 description "IP TOS, IPv6 TC, or Flow Label field."; } leaf local-port-low { type inet:port-number; description "Low end of local port range."; } leaf local-port-high { type inet:port-number; must '. >= ../local-port-low'; description "High end of local port range."; } leaf remote-port-low { type inet:port-number; description "Low end of remote port range."; } leaf remote-port-high { type inet:port-number; must '. >= ../remote-port-low'; description "High end of remote port range."; } } container opaque-key { when "../address-type = 'laddr:opaque-key-lcaf'" { description "When LCAF type is Opaque Key."; } description "Opaque Key LCAF type. The key fields are encoded in user order and MUST all have the same decoded-octet length."; reference "draft-ietf-lisp-rfc8060bis: LISP Canonical Address Format (LCAF), Section 4.5."; list key-field { key "key-field-id"; min-elements 1; max-elements 16; ordered-by user; description "Ordered key subfields. The list size and wildcard leaves determine the Key Field Num and Key Wildcard Fields wire values."; leaf key-field-id { type id-type; Ermagan, et al. Expires 4 May 2027 [Page 62] Internet-Draft LISP-YANG October 2026 description "Management identifier for the key field; it is not transmitted on the wire."; } leaf wildcard { type boolean; default "false"; description "Indicates that this key field is not used in a lookup."; } leaf value { type binary; mandatory true; description "Opaque key-field value."; } } } container nat-traversal { when "../address-type = 'laddr:nat-traversal-lcaf'" { description "When LCAF type is NAT-Traversal."; } description "NAT-Traversal LCAF type. All RLOC addresses MUST use the same AFI. Implementations MUST reject configuration that mixes IPv4 and IPv6 addresses."; reference "RC8060: LISP Canonical Address Format (LCAF) #section-4.4"; leaf ms-udp-port { type uint16 { range "4342"; } default "4342"; description "Map-Server UDP port."; } leaf etr-udp-port { type uint16; description "ETR UDP port."; } leaf global-etr-rloc { type inet:ip-address; description "Global ETR RLOC address."; } Ermagan, et al. Expires 4 May 2027 [Page 63] Internet-Draft LISP-YANG October 2026 leaf ms-rloc { type inet:ip-address; description "Map-Server RLOC address."; } leaf private-etr-rloc { type inet:ip-address; description "Private ETR RLOC address."; } leaf-list rtr-rlocs { type inet:ip-address; description "List of RTR RLOC addresses."; } } container nonce-locator { when "../address-type = 'laddr:nonce-locator-lcaf'" { description "When LCAF type is Nonce Locator."; } description "Nonce Locator LCAF type."; reference "draft-ietf-lisp-rfc8060bis: LISP Canonical Address Format (LCAF), Section 4.7."; leaf nonce { type uint32 { range "0..16777215"; } mandatory true; description "24-bit nonce value."; } leaf address { type inet:ip-address; mandatory true; description "IPv4 or IPv6 locator address."; } } container multicast-info { when "../address-type = 'laddr:multicast-info-lcaf'" { description "When LCAF type is Multicast Info."; } must "not(source-ipv4) or " + "(source-mask-length <= 32 and " Ermagan, et al. Expires 4 May 2027 [Page 64] Internet-Draft LISP-YANG October 2026 + "group-mask-length <= 32)" { error-message "IPv4 source and group masks cannot exceed 32 bits."; } must "not(source-mac) or " + "(source-mask-length <= 48 and " + "group-mask-length <= 48)" { error-message "MAC source and group masks cannot exceed 48 bits."; } description "Multicast Info LCAF type. Source and group addresses use the same address family. The group address MUST be a multicast or broadcast address."; reference "draft-ietf-lisp-rfc8060bis: LISP Canonical Address Format (LCAF), Section 4.8."; leaf instance-id { type uint32; mandatory true; description "32-bit LCAF Instance ID."; } leaf source-mask-length { type uint8 { range "0..128"; } mandatory true; description "Source mask length. The maximum is 32 for IPv4, 128 for IPv6, and 48 for a MAC address."; } leaf group-mask-length { type uint8 { range "0..128"; } mandatory true; description "Group mask length. The maximum is 32 for IPv4, 128 for IPv6, and 48 for a MAC address."; } choice address-family { mandatory true; description "Address family shared by the source and group."; case ipv4 { leaf source-ipv4 { type inet:ipv4-address; Ermagan, et al. Expires 4 May 2027 [Page 65] Internet-Draft LISP-YANG October 2026 mandatory true; description "IPv4 source or subnet address. An all-zero value is the wildcard source."; } leaf group-ipv4 { type inet:ipv4-address; mandatory true; description "IPv4 multicast or broadcast group address."; } } case ipv6 { leaf source-ipv6 { type inet:ipv6-address; mandatory true; description "IPv6 source or subnet address. An all-zero value is the wildcard source."; } leaf group-ipv6 { type inet:ipv6-address; mandatory true; description "IPv6 multicast group address."; } } case mac { leaf source-mac { type yang:mac-address; mandatory true; description "MAC source or subnet address. An all-zero value is the wildcard source."; } leaf group-mac { type yang:mac-address; mandatory true; description "Multicast or broadcast MAC group address."; } } } } container explicit-locator-path { when "../address-type = 'laddr:explicit-locator-path-lcaf'" { description "When LCAF type type is Explicit Locator Path."; Ermagan, et al. Expires 4 May 2027 [Page 66] Internet-Draft LISP-YANG October 2026 } description "Explicit Locator Path LCAF type. All hop addresses MUST use the same AFI: IPv4, IPv6, or MAC. Implementations MUST reject configuration that mixes address families."; reference "RC8060: LISP Canonical Address Format (LCAF) #section-4.6"; list hop { key "hop-id"; min-elements 1; ordered-by user; description "List of locator hops forming the explicit path."; leaf hop-id { type id-type; description "Unique identifier for the hop."; } leaf address { type union { type inet:ip-address; type yang:mac-address; } mandatory true; description "IPv4, IPv6, or MAC reencapsulation address."; } leaf lrs-bits { type bits { bit lookup { description "Lookup bit."; } bit rloc-probe { description "RLOC-probe bit."; } bit strict { description "Strict bit."; } } description "Flag bits per hop."; } } } Ermagan, et al. Expires 4 May 2027 [Page 67] Internet-Draft LISP-YANG October 2026 container security-key { when "../address-type = 'laddr:security-key-lcaf'" { description "When LCAF type is Security Key."; } description "Security Key LCAF type. Key Count and each Key Length are derived from the key-section list."; reference "draft-ietf-lisp-rfc8060bis: LISP Canonical Address Format (LCAF), Section 4.10."; leaf key-algorithm { type uint8; mandatory true; description "Algorithm that determines the key-material format."; } leaf revoke { type boolean; default "false"; description "Indicates that the key is being revoked."; } list key-section { key "key-id"; max-elements 255; ordered-by user; description "Ordered key sections."; leaf key-id { type uint8 { range "1..255"; } description "Management identifier for the key section; it is not transmitted on the wire."; } leaf key-material { type binary { length "0..65535"; } mandatory true; description "Key material for this section."; } } leaf address { type inet:ip-address; Ermagan, et al. Expires 4 May 2027 [Page 68] Internet-Draft LISP-YANG October 2026 mandatory true; description "IPv4 or IPv6 locator that owns the security key."; } } container source-dest-key { when "../address-type = 'laddr:source-dest-key-lcaf'" { description "When LCAF type type is Source/Dest."; } description "Source/Dest LCAF type. The source and destination MUST use the same AFI. Implementations MUST reject configuration that specifies different AFIs."; reference "RC8060: LISP Canonical Address Format (LCAF) #section-4.8"; leaf source { type ip-address-or-prefix; mandatory true; description "Source address or prefix. A host address denotes a /32 IPv4 prefix or a /128 IPv6 prefix."; } leaf dest { type ip-address-or-prefix; mandatory true; description "Destination address or prefix. A host address denotes a /32 IPv4 prefix or a /128 IPv6 prefix."; } } container replication-list { when "../address-type = 'laddr:replication-list-lcaf'" { description "When LCAF type is Replication List."; } description "Replication List LCAF type. All entries use the address family selected by the enclosing choice."; reference "draft-ietf-lisp-rfc8060bis: LISP Canonical Address Format (LCAF), Section 4.12."; choice address-family { mandatory true; description "Address family shared by all replication entries."; case ipv4 { Ermagan, et al. Expires 4 May 2027 [Page 69] Internet-Draft LISP-YANG October 2026 list ipv4-entry { key "entry-id"; min-elements 1; ordered-by user; description "Ordered IPv4 replication entries."; leaf entry-id { type id-type; description "Management identifier for the entry; it is not transmitted on the wire."; } leaf level { type uint8; mandatory true; description "Overlay distribution-tree level."; } leaf address { type inet:ipv4-address; mandatory true; description "IPv4 RTR or ETR address."; } } } case ipv6 { list ipv6-entry { key "entry-id"; min-elements 1; ordered-by user; description "Ordered IPv6 replication entries."; leaf entry-id { type id-type; description "Management identifier for the entry; it is not transmitted on the wire."; } leaf level { type uint8; mandatory true; description "Overlay distribution-tree level."; } leaf address { type inet:ipv6-address; mandatory true; Ermagan, et al. Expires 4 May 2027 [Page 70] Internet-Draft LISP-YANG October 2026 description "IPv6 RTR or ETR address."; } } } } } container json-data-model { when "../address-type = 'laddr:json-data-model-lcaf'" { description "When LCAF type is JSON Data Model."; } description "JSON Data Model LCAF type. The selected encoding determines the B bit, and the encoded value determines JSON Length."; reference "draft-ietf-lisp-rfc8060bis: LISP Canonical Address Format (LCAF), Section 4.13."; choice json-encoding { mandatory true; description "JSON encoding carried by this LCAF."; leaf json-text { type string { length "1..65535"; } description "RFC 8259 JSON text encoding."; } leaf json-binary { type binary { length "1..65535"; } description "Universal Binary JSON encoding."; } } leaf address { type simple-address; description "Optional address associated with the JSON data model."; } } container key-value-address { when "../address-type = 'laddr:key-value-address-lcaf'" { description "When LCAF type type is Key/Value Address."; } Ermagan, et al. Expires 4 May 2027 [Page 71] Internet-Draft LISP-YANG October 2026 description "Key/Value Address LCAF type. The key and value MUST use the same AFI. Implementations MUST reject configuration that specifies different AFIs."; reference "RC8060: LISP Canonical Address Format (LCAF) #section-5.5"; leaf key { type simple-address; description "Address as Key."; } leaf value { type simple-address; description "Address as Value."; } } container encapsulation-format { when "../address-type = 'laddr:encapsulation-format-lcaf'" { description "When LCAF type is Encapsulation Format."; } description "Encapsulation Format LCAF type."; reference "draft-ietf-lisp-rfc8060bis: LISP Canonical Address Format (LCAF), Section 4.15."; leaf encapsulations { type bits { bit no-encapsulation { position 0; description "No encapsulation."; } bit gue { position 25; description "Generic UDP Encapsulation."; } bit geneve { position 26; description "Geneve encapsulation."; } bit nv-gre { position 27; description Ermagan, et al. Expires 4 May 2027 [Page 72] Internet-Draft LISP-YANG October 2026 "NV-GRE encapsulation."; } bit vxlan-gpe { position 28; description "VXLAN-GPE encapsulation."; } bit vxlan { position 29; description "VXLAN encapsulation."; } bit layer-2-lisp { position 30; description "Layer 2 LISP encapsulation."; } bit layer-3-lisp { position 31; description "Layer 3 LISP encapsulation."; } } must "string-length(normalize-space(.)) > 0"; mandatory true; description "Supported encapsulation formats."; } leaf address { type inet:ip-address; mandatory true; description "IPv4 or IPv6 RLOC address."; } } container vendor-specific { when "../address-type = 'laddr:vendor-specific-lcaf'" { description "When LCAF type is Vendor-Specific."; } description "Vendor-Specific LCAF type."; reference "draft-ietf-lisp-rfc8060bis: LISP Canonical Address Format (LCAF), Section 4.16."; leaf oui { type yang:hex-string { length "8"; // "aa:bb:cc" Ermagan, et al. Expires 4 May 2027 [Page 73] Internet-Draft LISP-YANG October 2026 } mandatory true; description "A 24-bit IEEE Organizationally Unique Identifier."; reference "IEEE Std 802, subclause 8.2.2"; } leaf internal-format { type binary; mandatory true; description "Vendor-defined internal-format data."; } } } } } 8. Acknowledgments The authors would like the following individuals for their valuable reviews, feedback, and comments: Joe Clarke, Christian Hopps, Mohamed Boucadair. The tree view and the YANG model shown in this document have been formated with the 'pyang' tool. 9. IANA Considerations The IANA is requested to as assign a new namespace URI from the IETF XML registry. This document registers the following namesace URIs in the IETF XML registry [RFC3688]: URI: urn:ietf:params:xml:ns:yang:ietf-lisp Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-lisp-itr Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-lisp-etr Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. Ermagan, et al. Expires 4 May 2027 [Page 74] Internet-Draft LISP-YANG October 2026 URI: urn:ietf:params:xml:ns:yang:ietf-lisp-mapserver Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-lisp-mapresolver Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-lisp-address-types Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. This document registers the following YANG modules in the "YANG Module Names" registry [RFC6020]: Name: ietf-lisp Namespace: urn:ietf:params:xml:ns:yang:ietf-lisp Prefix: lisp Reference: RFC XXXX Name: ietf-lisp-itr Namespace: urn:ietf:params:xml:ns:yang:ietf-lisp-itr Prefix: lisp-itr Reference: RFC XXXX Name: ietf-lisp-etr Namespace: urn:ietf:params:xml:ns:yang:ietf-lisp-etr Prefix: lisp-etr Reference: RFC XXXX Name: ietf-lisp-mapserver Namespace: urn:ietf:params:xml:ns:yang:ietf-lisp-mapserver Prefix: lisp-ms Reference: RFC XXXX Name: ietf-lisp-mapresolver Namespace: urn:ietf:params:xml:ns:yang:ietf-lisp-mapresolver Prefix: lisp-mr Reference: RFC XXXX Name: ietf-lisp-address-types Namespace: urn:ietf:params:xml:ns:yang:ietf-lisp-address-types Prefix: lisp-at Reference: RFC XXXX These modules are not maintained by IANA. Ermagan, et al. Expires 4 May 2027 [Page 75] Internet-Draft LISP-YANG October 2026 10. Security Considerations The YANG modules specified in this document define 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 NETCONF access control model [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a pre- configured subset of all available NETCONF or RESTCONF protocol operations and content. The security considerations of LISP control-plane [RFC9301] and LISP data-plane [RFC9300] as well as the LISP threat analysis [RFC7835] apply to this YANG model. There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). 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: /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ lisp:lisp/ Access to the locator-sets node may modify which interfaces are used for data and/or control traffic as well as affect the load balancing of data-plane traffic. Access to the lisp-role node may prevent the device from perform its intended data-plane and/or control-plane operation. Access to the router-id node allows to modify the unique identifier of the device, which may result in disruption of its LISP control-plane operation. Access to the vpn node may allow to redirect data-plane traffic to erroneous local or remote network instances. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:map-server Access to the sites node can prevent authorized devices from registering mappings in the Map-Server and/or allow unauthorized devices to so. Access to the vpn node can result in corrupted mapping sate that may propagate across the LISP network, potentially resulting in forwarding of data-plane traffic to arbitrary Ermagan, et al. Expires 4 May 2027 [Page 76] Internet-Draft LISP-YANG October 2026 destinations and general disruption of the data-plane operation. Access to mapping-system-type and/or ddt-mapping-system nodes may prevent the device to connect to the Mapping System infrastructure and consequentially to attract Map-Request messages. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:map-resolver Access to mapping-system-type, ms-address and/or ddt-mapping-system nodes may prevent the device to connect to the Mapping System infrastructure and forward Map-Request messages. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:itr Access to the rloc-probing node can increase the control-plane overhead in the device or affect the capability of the device to detect failures on the underlay. Access to the itr-rlocs node may prevent the device from getting Map-Reply messages. Access to the map-resolvers node can prevent the device from sending its Map- Request messages to valid Map-Resolvers. Access to the proxy-etrs nodes can affect the capability of the device to send data-plane traffic towards non-LISP destinations. Access to the map-cache node can result in forwarding of data-plane traffic to arbitrary destinations and general disruption of data-plane operation. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:etr Access to the map-servers node can prevent the device from registering its local mappings into the Mapping System. Access to the local-eids node can disrupt data-plane operation on the device and/or result in the device registering corrupted mappings into the Mapping System. Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability: /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ lisp:lisp Access to the locator-sets node can expose the locators the device is using for its control and/or data operation. Access to the lisp-role node can disclose the LISP roles instantiated at the device which facilitates mounting attacks against the device. Access to the Ermagan, et al. Expires 4 May 2027 [Page 77] Internet-Draft LISP-YANG October 2026 router-id node can expose the unique identifier of device which may allow a third party to track its control-plane operation and/or impersonate the device. Access to the vpn node can leak the local mapping between LISP Instance IDs and local network instances. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:map-server Access to the sites node can expose the credentials used to register mappings and allow unauthorized devices to do so. Access to the vpn node can expose the mappings currently registered in the device, which has privacy implications. Access to the mapping-system-type node may reveal the Mapping System in use which can be used to mount attacks against the device and/or the Mapping System. Access to the summary and counters nodes may expose operational statistics of the device. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:map-resolver Access to the mapping-system-type node may reveal the Mapping System in use which can be used to mount attacks against the device and/or the Mapping System. Access to the ms-address and/or ddt-mapping- system nodes can leak the information about the Mapping System infrastructure used by the device, which can be used to block communication and/or mount attacks against it. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:itr Access to the rloc-probing node can expose if and how the device is using control-plane signaling to probe underlay locators. Access to the itr-rlocs node may disclose the addresses the device is using to receive Map-Reply messages. Access to the map-resolvers node can expose the Map-Resolvers used by the device, which can be used to mount attacks against the device and/or the Mapping System. Access to the proxy-etrs node can disclose the PETRs used by the device, which can be used to mount attacks against the device and/or PETRs. Access to the map-cache node can expose the mappings currently cached in the device, which has privacy implications. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:etr Ermagan, et al. Expires 4 May 2027 [Page 78] Internet-Draft LISP-YANG October 2026 Access to the map-servers node can expose the credentials used by the device to register mappings into the Mapping System allowing an unauthorized device to impersonate and register mappings on behalf the authorized device. Access to the local-eids node can expose the local EIDs currently being served by the device, which has privacy implications. /rt:routing/rt:control-plane-protocols/rt:control-plane- protocol/lisp:lisp/lisp:address-types Access to the geo-coordinates node can expose geographical location information about the devices/networks/users, which has privacy implications. 11. Normative References [IANA_address_family_numbers] IANA, "Address Family Numbers", . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC2404] Madson, C. and R. Glenn, "The Use of HMAC-SHA-1-96 within ESP and AH", RFC 2404, DOI 10.17487/RFC2404, November 1998, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC4868] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-SHA- 384, and HMAC-SHA-512 with IPsec", RFC 4868, DOI 10.17487/RFC4868, May 2007, . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [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, . Ermagan, et al. Expires 4 May 2027 [Page 79] Internet-Draft LISP-YANG October 2026 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, . [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, . [RFC7835] Saucez, D., Iannone, L., and O. Bonaventure, "Locator/ID Separation Protocol (LISP) Threat Analysis", RFC 7835, DOI 10.17487/RFC7835, April 2016, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . [RFC8060] Farinacci, D., Meyer, D., and J. Snijders, "LISP Canonical Address Format (LCAF)", RFC 8060, DOI 10.17487/RFC8060, February 2017, . [RFC8111] Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. Smirnov, "Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)", RFC 8111, DOI 10.17487/RFC8111, May 2017, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10.17487/RFC8341, March 2018, . [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, . [RFC8343] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, . Ermagan, et al. Expires 4 May 2027 [Page 80] Internet-Draft LISP-YANG October 2026 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Routing Management (NMDA Version)", RFC 8349, DOI 10.17487/RFC8349, March 2018, . [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, . [RFC8529] Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X. Liu, "YANG Data Model for Network Instances", RFC 8529, DOI 10.17487/RFC8529, March 2019, . [RFC9300] Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. Cabellos, Ed., "The Locator/ID Separation Protocol (LISP)", RFC 9300, DOI 10.17487/RFC9300, October 2022, . [RFC9301] Farinacci, D., Maino, F., Fuller, V., and A. Cabellos, Ed., "Locator/ID Separation Protocol (LISP) Control Plane", RFC 9301, DOI 10.17487/RFC9301, October 2022, . Appendix A. Data Model examples This section presents some simple and illustrative examples on how to configure LISP. A.1. LISP protocol instance The following is an example configuration for a LISP protocol instance with the name "LISP1". There are also 2 VNIs configured. Ermagan, et al. Expires 4 May 2027 [Page 81] Internet-Draft LISP-YANG October 2026 VRF-BLUE true VRF-RED true lisp:lisp LISP1 etr itr 1000 VRF-BLUE 2000 VRF-RED Ermagan, et al. Expires 4 May 2027 [Page 82] Internet-Draft LISP-YANG October 2026 A.2. LISP ITR The following is an example configuration for ITR functionality under "LISP1". There are 2 Map-Resolvers configured. lisp:lisp LISP1 itr 2001:db8:203:0:113::1 2001:db8:204:0:113::1 A.3. LISP ETR The following is an example configuration for ETR functionality under "LISP1". There are 2 Map-Servers and 2 local EIDs configured. VRF-BLUE true Ermagan, et al. Expires 4 May 2027 [Page 83] Internet-Draft LISP-YANG October 2026 VRF-RED true lisp:lisp LISP1 etr 1 1000 VRF-BLUE 2000 VRF-RED 2001:db8:203:0:113::1 key1 hmac-sha-256-128 *Kye^$$1#gb91U04zpa 2001:db8:204:0:113::1 Ermagan, et al. Expires 4 May 2027 [Page 84] Internet-Draft LISP-YANG October 2026 key1 hmac-sha-256-128 *Kye^$$1#gb91U04zpa 1000 2001:db8:400:0:100::0 lisp-at:ipv6-prefix-afi 2001:db8:400:0:100::/80 2000 2001:db8:800:0:200::0 lisp-at:ipv6-prefix-afi 2001:db8:800:0:200::/80 Ermagan, et al. Expires 4 May 2027 [Page 85] Internet-Draft LISP-YANG October 2026 A.4. LISP Map-Server The following is an example configuration for Map-Server functionality under "LISP1". There are 2 mappings configured. lisp:lisp LISP1 lisp-ms:ms 1 key1 hmac-sha-256-128 *Kye^$$1#gb91U04zpa 1000 1 lisp-at:ipv6-prefix-afi Ermagan, et al. Expires 4 May 2027 [Page 86] Internet-Draft LISP-YANG October 2026 2001:db8:400:0:100::/80 2000 1 lisp-at:ipv6-prefix-afi 2001:db8:800:0:200::/80 Authors' Addresses Vina Ermagan Google United States of America Email: ermagan@gmail.com Alberto Rodriguez-Natal Cisco Spain Email: natal@cisco.com Ermagan, et al. Expires 4 May 2027 [Page 87] Internet-Draft LISP-YANG October 2026 Florin Coras Cisco San Jose, CA United States of America Email: fcoras@cisco.com Carl Moberg NVIDIA Email: cmoberg@nvidia.com Reshad Rahman Equinix Canada Email: reshad@yahoo.com Albert Cabellos-Aparicio Technical University of Catalonia Barcelona Spain Email: acabello@ac.upc.edu Fabio Maino Cisco San Jose, CA United States of America Email: fmaino@cisco.com Ermagan, et al. Expires 4 May 2027 [Page 88]