--- 1/draft-ietf-lisp-yang-10.txt 2019-03-06 15:13:14.184612739 -0800 +++ 2/draft-ietf-lisp-yang-11.txt 2019-03-06 15:13:14.328616269 -0800 @@ -1,25 +1,26 @@ LISP Working Group V. Ermagan -Internet-Draft A. Rodriguez-Natal -Intended status: Experimental F. Coras -Expires: May 8, 2019 C. Moberg +Internet-Draft Google +Intended status: Experimental A. Rodriguez-Natal +Expires: September 7, 2019 F. Coras + C. Moberg R. Rahman Cisco Systems A. Cabellos-Aparicio Technical University of Catalonia F. Maino Cisco Systems - November 4, 2018 + March 6, 2019 LISP YANG Model - draft-ietf-lisp-yang-10 + draft-ietf-lisp-yang-11 Abstract This document describes a YANG data model to use with the Locator/ID Separation Protocol (LISP). The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA). Status of This Memo @@ -30,25 +31,25 @@ 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 May 8, 2019. + This Internet-Draft will expire on September 7, 2019. Copyright Notice - Copyright (c) 2018 IETF Trust and the persons identified as the + Copyright (c) 2019 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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -56,49 +57,50 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 2. LISP Module . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Module Structure . . . . . . . . . . . . . . . . . . . . 3 2.2. Module Definition . . . . . . . . . . . . . . . . . . . . 6 3. LISP-ITR Module . . . . . . . . . . . . . . . . . . . . . . . 16 - 3.1. Module Structure . . . . . . . . . . . . . . . . . . . . 16 + 3.1. Module Structure . . . . . . . . . . . . . . . . . . . . 17 3.2. Module Definition . . . . . . . . . . . . . . . . . . . . 22 - 4. LISP-ETR Module . . . . . . . . . . . . . . . . . . . . . . . 25 - 4.1. Module Structure . . . . . . . . . . . . . . . . . . . . 25 + 4. LISP-ETR Module . . . . . . . . . . . . . . . . . . . . . . . 26 + 4.1. Module Structure . . . . . . . . . . . . . . . . . . . . 26 4.2. Module Definition . . . . . . . . . . . . . . . . . . . . 28 5. LISP-Map-Server Module . . . . . . . . . . . . . . . . . . . 32 - 5.1. Module Structure . . . . . . . . . . . . . . . . . . . . 32 + 5.1. Module Structure . . . . . . . . . . . . . . . . . . . . 33 5.2. Module Definition . . . . . . . . . . . . . . . . . . . . 41 6. LISP-Map-Resolver Module . . . . . . . . . . . . . . . . . . 47 6.1. Module Structure . . . . . . . . . . . . . . . . . . . . 47 - 6.2. Module Definition . . . . . . . . . . . . . . . . . . . . 47 - 7. LISP-Address-Types Module . . . . . . . . . . . . . . . . . . 49 - 7.1. Module Definition . . . . . . . . . . . . . . . . . . . . 49 + 6.2. Module Definition . . . . . . . . . . . . . . . . . . . . 48 + 7. LISP-Address-Types Module . . . . . . . . . . . . . . . . . . 50 + 7.1. Module Definition . . . . . . . . . . . . . . . . . . . . 50 7.2. Data Model examples . . . . . . . . . . . . . . . . . . . 64 7.2.1. LISP protocol instance . . . . . . . . . . . . . . . 64 - 7.2.2. LISP ITR . . . . . . . . . . . . . . . . . . . . . . 65 + 7.2.2. LISP ITR . . . . . . . . . . . . . . . . . . . . . . 66 7.2.3. LISP ETR . . . . . . . . . . . . . . . . . . . . . . 66 - 7.2.4. LISP Map-Server . . . . . . . . . . . . . . . . . . . 68 - 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69 - 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69 - 10. Security Considerations . . . . . . . . . . . . . . . . . . . 71 - 11. Normative References . . . . . . . . . . . . . . . . . . . . 74 + 7.2.4. LISP Map-Server . . . . . . . . . . . . . . . . . . . 69 + 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 70 + 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 70 + 10. Security Considerations . . . . . . . . . . . . . . . . . . . 72 + 11. Normative References . . . . . . . . . . . . . . . . . . . . 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76 1. Introduction The Locator/ID Separation Protocol (LISP) defines several network elements subject to be configured. This document presents the YANG data models required for basic configuration of all major LISP + [RFC6830] elements. The models also capture some essential operational data elements as well. 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. @@ -129,22 +131,20 @@ | | +--rw priority? uint8 | | +--rw weight? uint8 | | +--rw multicast-priority? uint8 | | +--rw multicast-weight? uint8 | +--:(general-locator) | +--rw locator* [id] | +--rw id string | +--rw locator-address | | +--rw address-type | | | lisp-address-family-ref - | | +--rw virtual-network-id? - | | | instance-id-type | | +--rw (address)? | | +--:(no-address) | | | +--rw no-address? empty | | +--:(ipv4) | | | +--rw ipv4? | | | inet:ipv4-address | | +--:(ipv4-prefix) | | | +--rw ipv4-prefix? | | | inet:ipv4-prefix | | +--:(ipv6) @@ -164,21 +164,21 @@ | | | 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 iid? + | | | +--rw instance-id? | | | | instance-id-type | | | +--rw mask-length? uint8 | | | +--rw address? simple-address | | +--:(as-number-lcaf) | | | +--rw as-number-lcaf | | | +--rw as? inet:as-number | | | +--rw address? simple-address | | +--:(application-data) | | | +--rw application-data | | | +--rw address? @@ -239,29 +239,29 @@ | | +--rw service-index? uint8 | +--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 virtual-networks - +--rw virtual-network* [vni] - +--rw vni lcaf:instance-id-type - +--rw ni-name? + +--rw vpns + +--rw vpn* [instance-id] + +--rw instance-id lcaf:instance-id-type + +--rw iid-name -> /ni:network-instances/network-instance/name 2.2. Module Definition - file "ietf-lisp@2018-11-04.yang" + file "ietf-lisp@2019-03-05.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 @@ -291,21 +291,21 @@ "RFC YYYY: 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. @@ -319,27 +319,26 @@ set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://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 2018-11-04 { + revision 2019-03-05 { description "Initial revision."; reference "https://tools.ietf.org/html/rfc6830"; } - /* * Identity definitions */ identity lisp { base "rt:control-plane-protocol"; description "LISP protocol."; reference "RFC 6830: The Locator/ID Separation Protocol (LISP)."; } @@ -417,21 +417,21 @@ description "Defines the lisp map-cache ACT type"; reference "https://tools.ietf.org/html/rfc6830#section-6.1.4"; } typedef eid-id { type string; description "Type encoding of lisp-addresses to be generally used in EID keyed lists."; } - typedef auth-key-type { + typedef auth-algorithm-type { type enumeration { enum none { value 0; description "No authentication."; } enum hmac-sha-1-96 { value 1; description "HMAC-SHA-1-96 (RFC2404) authentication is used."; @@ -472,26 +472,25 @@ leaf multicast-priority { type uint8; description "Locator's multicast priority"; } leaf multicast-weight { type uint8; description "Locator's multicast weight"; } - } grouping locators-grouping { description - "Group that defines a list of LISP locators."; + "Grouping that defines a list of LISP locators."; list locator { key "id"; description "List of routing locators"; leaf id { type string { length "1..64"; } description "Locator id"; @@ -502,37 +501,37 @@ "The locator address provided in LISP canonincal address format."; } uses locator-properties; } } grouping local-locators-grouping { description - "Group that defines a list of LISP locators."; + "Grouping that defines a list of LISP locators."; list interface { key "interface-ref"; description "The address type of the locator"; leaf interface-ref { type if:interface-ref; description "The name of the interface supporting the locator."; } uses locator-properties; } } grouping mapping { description - "Group that defines a LISP mapping."; + "Grouping that defines a LISP mapping."; container eid { uses lcaf:lisp-address; description "End-host Identifier (EID) to be mapped to a list of locators"; } leaf time-to-live { type uint32; units minutes; description @@ -569,61 +568,87 @@ 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 - "Group that defines a list of LISP mappings."; - list virtual-network { - key "vni"; + "Grouping that defines a list of LISP mappings."; + list vpn { + key "instance-id"; description - "Virtual network to which the mappings belong."; - leaf vni { + "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:virtual-networks/lisp:virtual-network" - + "/lisp:vni"; + + "/lisp:vpns/lisp:vpn" + + "/lisp:instance-id"; } description - "Virtual network identifier."; + "VPN identifier."; } container mappings { description - "Mappings within the virtual network."; + "Mappings within the VPN."; list mapping { key "id"; description "List of EID to RLOCs mappings."; leaf id { type eid-id; description "Id that uniquely identifies a mapping."; } 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 string; + 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."; @@ -672,65 +697,65 @@ 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 = 'itr' or - ../lisp-role/lisp-role-type = 'pitr' or - ../lisp-role/lisp-role-type = 'etr' or - ../lisp-role/lisp-role-type = 'petr'" { + 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 "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 virtual-networks { - when "../lisp-role/lisp-role-type = 'itr' or - ../lisp-role/lisp-role-type = 'pitr' or - ../lisp-role/lisp-role-type = 'etr' or - ../lisp-role/lisp-role-type = 'petr'" { + 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 "Virtual networks"; - list virtual-network { - key vni; - unique "ni-name"; - description "List of virtual networks"; + description "VPNs"; + list vpn { + key instance-id; + unique "iid-name"; + description "List of VPNs"; - leaf vni { + leaf instance-id { type lcaf:instance-id-type; description - "Virtual network identifier"; + "VPN identifier. The value 0 for instance-id must be used + for the default VRF."; } - leaf ni-name { + leaf iid-name { type leafref { path "/ni:network-instances/ni:network-instance/ni:name"; } mandatory true; description - "Name of Network Instance (e.g. VRF) to which a VNI is - bound. Each VNI is bound to a different Network - Instance"; + "Name of VPN (e.g. VRF) to which an instance-id is + bound. Each instance-id is bound to a different VPN"; } } } } } } 3. LISP-ITR Module @@ -748,30 +773,31 @@ | +--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 virtual-network* [vni] - +--rw vni lcaf:instance-id-type + +--rw vpn* [instance-id] + +--rw instance-id + | -> /rt:routing/control-plane-protocols + | /control-plane-protocol/lisp:lisp/vpns + | /vpn/instance-id +--rw mappings +--rw mapping* [id] +--rw id eid-id +--rw eid | +--rw address-type | | lisp-address-family-ref - | +--rw virtual-network-id? - | | instance-id-type | +--rw (address)? | +--:(no-address) | | +--rw no-address? empty | +--:(ipv4) | | +--rw ipv4? | | inet:ipv4-address | +--:(ipv4-prefix) | | +--rw ipv4-prefix? | | inet:ipv4-prefix | +--:(ipv6) @@ -790,21 +816,21 @@ | | +--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 iid? instance-id-type + | | +--rw instance-id? instance-id-type | | +--rw mask-length? uint8 | | +--rw address? simple-address | +--:(as-number-lcaf) | | +--rw as-number-lcaf | | +--rw as? inet:as-number | | +--rw address? simple-address | +--:(application-data) | | +--rw application-data | | +--rw address? | | | simple-address @@ -869,22 +895,20 @@ +--rw (locator-list)? +--:(negative-mapping) | +--rw map-reply-action? map-reply-action +--:(positive-mapping) +--rw rlocs +--rw locator* [id] +--rw id string +--rw locator-address | +--rw address-type | | lisp-address-family-ref - | +--rw virtual-network-id? - | | instance-id-type | +--rw (address)? | +--:(no-address) | | +--rw no-address? | | empty | +--:(ipv4) | | +--rw ipv4? | | inet:ipv4-address | +--:(ipv4-prefix) | | +--rw ipv4-prefix? | | inet:ipv4-prefix @@ -905,21 +929,21 @@ | | 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 iid? + | | +--rw instance-id? | | | instance-id-type | | +--rw mask-length? uint8 | | +--rw address? | | simple-address | +--:(as-number-lcaf) | | +--rw as-number-lcaf | | +--rw as? | | | inet:as-number | | +--rw address? | | simple-address @@ -1001,21 +1025,21 @@ | | service-path-id-type | +--rw service-index? | uint8 +--rw priority? uint8 +--rw weight? uint8 +--rw multicast-priority? uint8 +--rw multicast-weight? uint8 3.2. Module Definition - file "ietf-lisp-itr@2018-06-29.yang" + file "ietf-lisp-itr@2019-02-23.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 occurences of XXXX with actual RFC number // and remove this note import ietf-lisp { @@ -1033,21 +1057,21 @@ (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. @@ -1061,21 +1085,21 @@ set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://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 2018-06-29 { + revision 2019-02-23 { description "Initial revision."; reference "https://tools.ietf.org/html/rfc6830"; } augment "/rt:routing/rt:control-plane-protocols" + "/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 @@ -1177,33 +1201,37 @@ 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 auth-key? string - | +--rw auth-key-type? lisp:auth-key-type + | +--rw authentication-keys + | +--rw authentication-key* [auth-key-id] + | +--rw auth-key-id string + | +--rw auth-algorithm-id* lisp:auth-algorithm-type + | +--rw auth-key-value? string +--rw local-eids - +--rw virtual-network* [vni] - +--rw vni lcaf:instance-id-type + +--rw vpn* [instance-id] + +--rw instance-id + | -> /rt:routing/control-plane-protocols + | /control-plane-protocol/lisp:lisp/vpns + | /vpn/instance-id +--rw eids +--rw local-eid* [id] +--rw id lisp:eid-id +--rw eid-address | +--rw address-type | | lisp-address-family-ref - | +--rw virtual-network-id? - | | instance-id-type | +--rw (address)? | +--:(no-address) | | +--rw no-address? empty | +--:(ipv4) | | +--rw ipv4? | | inet:ipv4-address | +--:(ipv4-prefix) | | +--rw ipv4-prefix? | | inet:ipv4-prefix | +--:(ipv6) @@ -1222,21 +1250,21 @@ | | +--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 iid? instance-id-type + | | +--rw instance-id? instance-id-type | | +--rw mask-length? uint8 | | +--rw address? simple-address | +--:(as-number-lcaf) | | +--rw as-number-lcaf | | +--rw as? inet:as-number | | +--rw address? simple-address | +--:(application-data) | | +--rw application-data | | +--rw address? | | | simple-address @@ -1288,31 +1316,34 @@ | +--:(key-value-address) | | +--rw key-value-address | | +--rw key? simple-address | | +--rw value? simple-address | +--:(service-path) | +--rw service-path | +--rw service-path-id? | | service-path-id-type | +--rw service-index? uint8 +--rw rlocs? leafref + | -> /rt:routing/control-plane-protocols + | /control-plane-protocol/lisp:lisp + | /locator-sets + | /locator-set/locator-set-name +--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@2018-09-06.yang" + file "ietf-lisp-etr@2019-02-23.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 occurences of XXXX with actual RFC number // and remove this note import ietf-lisp { prefix lisp; reference "RFC XXXX: LISP YANG model"; } @@ -1331,21 +1362,21 @@ (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. @@ -1359,21 +1390,21 @@ set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://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 2018-09-06 { + revision 2019-02-23 { description "Initial revision."; reference "https://tools.ietf.org/html/rfc6830"; } 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 @@ -1395,59 +1426,50 @@ 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."; + } - leaf auth-key { - type string; - description - "Map-Server authentication key."; - } - leaf auth-key-type { - type lisp:auth-key-type; - description - "Map-Server authentication type."; - } + 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 - "Virtual networks served by the ETR."; - list virtual-network { - key "vni"; + "VPNs served by the ETR."; + list vpn { + key "instance-id"; description - "Virtual network for local-EIDs."; - leaf vni { + "VPN for local-EIDs."; + leaf instance-id { type leafref { path "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/lisp:lisp" - + "/lisp:virtual-networks/lisp:virtual-network" - + "/lisp:vni"; + + "/lisp:vpns/lisp:vpn" + + "/lisp:instance-id"; } description - "Virtual network identifier."; + "VPN identifier."; } container eids { description "EIDs served by the ETR."; - list local-eid { key "id"; description "List of local EIDs."; leaf id { type lisp:eid-id; description "Unique id of local EID."; } container eid-address { @@ -1510,34 +1532,43 @@ 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 auth-key + | +--rw authentication-keys + | | +--rw authentication-key* [auth-key-id] + | | +--rw auth-key-id string + | | +--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 string + | +--rw auth-algorithm-id* + | | lisp:auth-algorithm-type | +--rw auth-key-value? string - | +--rw auth-key-type* lisp:auth-key-type - +--rw virtual-network-ids - | +--rw virtual-network-identifier* [vni] - | +--rw vni lcaf:instance-id-type + +--rw vpns + | +--rw vpn* [instance-id] + | +--rw instance-id lcaf: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 virtual-network-id? - | | | | instance-id-type | | | +--rw (address)? | | | +--:(no-address) | | | | +--rw no-address? empty | | | +--:(ipv4) | | | | +--rw ipv4? | | | | inet:ipv4-address | | | +--:(ipv4-prefix) | | | | +--rw ipv4-prefix? | | | | inet:ipv4-prefix | | | +--:(ipv6) @@ -1556,21 +1587,21 @@ | | | | +--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 iid? instance-id-type + | | | | +--rw instance-id? instance-id-type | | | | +--rw mask-length? uint8 | | | | +--rw address? simple-address | | | +--:(as-number-lcaf) | | | | +--rw as-number-lcaf | | | | +--rw as? inet:as-number | | | | +--rw address? simple-address | | | +--:(application-data) | | | | +--rw application-data | | | | +--rw address? | | | | | simple-address @@ -1636,22 +1667,20 @@ | | +--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 virtual-network-id? - | | | | instance-id-type | | | +--rw (address)? | | | +--:(no-address) | | | | +--rw no-address? | | | | empty | | | +--:(ipv4) | | | | +--rw ipv4? | | | | inet:ipv4-address | | | +--:(ipv4-prefix) | | | | +--rw ipv4-prefix? | | | | inet:ipv4-prefix @@ -1672,21 +1701,21 @@ | | | | 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 iid? + | | | | +--rw instance-id? | | | | | instance-id-type | | | | +--rw mask-length? uint8 | | | | +--rw address? | | | | simple-address | | | +--:(as-number-lcaf) | | | | +--rw as-number-lcaf | | | | +--rw as? inet:as-number | | | | +--rw address? simple-address | | | +--:(application-data) | | | | +--rw application-data @@ -1758,22 +1787,20 @@ | | | +--rw map-reply-action? | | | map-reply-action | | +--:(positive-mapping) | | +--rw rlocs | | +--rw locator* [id] | | +--rw id | | | string | | +--rw locator-address | | | +--rw address-type | | | | lisp-address-family-ref - | | | +--rw virtual-network-id? - | | | | instance-id-type | | | +--rw (address)? | | | +--:(no-address) | | | | +--rw no-address? | | | | empty | | | +--:(ipv4) | | | | +--rw ipv4? | | | | inet:ipv4-address | | | +--:(ipv4-prefix) | | | | +--rw ipv4-prefix? | | | | inet:ipv4-prefix @@ -1795,21 +1822,21 @@ | | | +--:(null-address) | | | | +--rw null-address | | | | +--rw address? | | | | empty | | | +--:(afi-list) | | | | +--rw afi-list | | | | +--rw address-list* | | | | simple-address | | | +--:(instance-id) | | | | +--rw instance-id - | | | | +--rw iid? + | | | | +--rw instance-id? | | | | | instance-id-type | | | | +--rw mask-length? | | | | | uint8 | | | | +--rw address? | | | | simple-address | | | +--:(as-number-lcaf) | | | | +--rw as-number-lcaf | | | | +--rw as? | | | | | inet:as-number | | | | +--rw address? @@ -1919,21 +1946,21 @@ | +--ro number-registered-eids? uint32 +--ro counters +--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 5.2. Module Definition - file "ietf-lisp-mapserver@2018-06-29.yang" + file "ietf-lisp-mapserver@2019-03-05.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 occurences of XXXX with actual RFC number // and remove this note import ietf-lisp { @@ -1955,28 +1982,27 @@ (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-Server. The module can be extended by vendors to define vendor-specific parameters and policies. Copyright (c) 2018 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 @@ -1977,42 +2003,41 @@ Copyright (c) 2018 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 Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://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 2018-06-29 { + revision 2019-03-05 { description "Initial revision."; reference "https://tools.ietf.org/html/rfc6833"; } identity ms { base lisp:lisp-role; description "LISP Map-Server."; } grouping ms-counters { - description "Group that defines map-server counters."; + description "Grouping that defines map-server counters."; container counters { config false; description "Container for the counters"; leaf map-registers-in { type yang:counter64; description "Number of incoming Map-Register messages"; } leaf map-registers-in-auth-failed { @@ -2059,47 +2083,43 @@ description "Sites to accept registrations from."; list site { key site-id; description "Site that can send registrations."; leaf site-id { type uint64; description "Site ID"; } - container auth-key { - description - "Site authentication key."; - leaf auth-key-value { - type string; - description - "Clear text authentication key"; - } - leaf-list auth-key-type { - type lisp:auth-key-type; - description - "Authentication key type."; + 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 virtual-network-ids { + container vpns { description - "Sites for which the Map-Server accepts registrations."; - list virtual-network-identifier { - key "vni"; + "VPNs for which the Map-Server accepts registrations."; + list vpn { + key "instance-id"; description - "Virtual network instances in the Map-Server."; - leaf vni { + "VPN instances in the Map-Server."; + leaf instance-id { type lcaf:instance-id-type; description - "Virtual network identifier."; + "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; @@ -2225,21 +2243,21 @@ 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@2018-06-29.yang" + file "ietf-lisp-mapresolver@2019-02-23.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 occurences of XXXX with actual RFC number // and remove this note import ietf-lisp { @@ -2257,21 +2275,21 @@ (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. @@ -2285,21 +2303,21 @@ set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://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 2018-06-29 { + revision 2019-02-23 { description "Initial revision."; reference "https://tools.ietf.org/html/rfc6833"; } identity mr { base lisp:lisp-role; description "LISP Map-Resolver."; } @@ -2334,21 +2352,21 @@ } 7. LISP-Address-Types Module This module captures the various LISP address types, and is an essential building block used in other LISP modules. 7.1. Module Definition - file "ietf-lisp-address-types@2018-06-29.yang" + file "ietf-lisp-address-types@2019-02-23.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"; @@ -2349,31 +2367,30 @@ 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. @@ -2389,25 +2406,25 @@ (http://trustee.ietf.org/license-info). 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 2018-06-29 { + revision 2019-02-23 { description "Initial revision."; reference - "http://tools.ietf.org/html/draft-ietf-lisp-lcaf-10"; + "RC8060: LISP Canonical Address Format (LCAF)"; } 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."; @@ -2594,25 +2610,20 @@ grouping lisp-address { description "Generic LISP address."; leaf address-type { type lisp-address-family-ref; mandatory true; description "Type of the LISP address."; } - leaf virtual-network-id { - type instance-id-type; - description - "Virtual Network Identifier (instance-id) of the 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; @@ -2708,28 +2718,29 @@ #section-4.16.1"; 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"; + "When LCAF type is Instance ID as per RFC8060."; } description "Instance ID LCAF type."; + reference "http://tools.ietf.org/html/draft-ietf-lisp-lcaf-10 #section-4.2"; - leaf iid { + leaf instance-id { type instance-id-type; description "Instance ID value."; } leaf mask-length { type uint8; description "Mask length."; } leaf address { @@ -3051,50 +3061,57 @@ This section presents some simple and illustrative examples on how to configure LISP. 7.2.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. - + VRF-BLUE true VRF-RED true lisp:lisp LISP1 - - - 1000 - VRF-BLUE - - - 2000 - VRF-RED - - + + etr + + + itr + + + + 1000 + VRF-BLUE + + + 2000 + VRF-RED + + 7.2.2. LISP ITR The following is an example configuration for ITR functionality under "LISP1". There are 2 Map-Resolvers configured. @@ -3124,20 +3141,33 @@ 7.2.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 + + + VRF-RED + + true + + lisp:lisp LISP1 etr @@ -3137,75 +3167,96 @@ lisp:lisp LISP1 etr 1 - + + + 1000 + VRF-BLUE + + + 2000 + VRF-RED + + 2001:db8:203:0:113::1 - *Kye^$$1#gb91U04zpa! - hmac-sha-256-128 + + + key1 + + hmac-sha-256-128 + + *Kye^$$1#gb91U04zpa + + 2001:db8:204:0:113::1 - *Kye^$$1#gb91U04zpa! - hmac-sha-256-128 + + + key1 + + hmac-sha-256-128 + + *Kye^$$1#gb91U04zpa + + - - 1000 + + 1000 2001:db8:400:0:100::0 laddr:ipv6-prefix-afi 2001:db8:400:0:100::/80 - - - 2000 + + + 2000 2001:db8:800:0:200::0 laddr:ipv6-prefix-afi 2001:db8:800:0:200::/80 - + - - 7.2.4. LISP Map-Server The following is an example configuration for Map-Server functionality under "LISP1". There are 2 mappings configured. @@ -3212,63 +3263,69 @@ lisp:lisp LISP1 lisp-ms:ms - + 1 - - *Kye^$$1#gb91U04zpa! - hmac-sha-256-128 - + + + key1 + + hmac-sha-256-128 + + *Kye^$$1#gb91U04zpa + + - - - 1000 + + + 1000 1 laddr:ipv6-prefix-afi - + 2001:db8:400:0:100::/80 - - - 2000 + + + 2000 1 laddr:ipv6-prefix-afi 2001:db8:800:0:200::/80 - - + + 8. Acknowledgments The tree view and the YANG model shown in this document have been @@ -3325,22 +3383,22 @@ 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 + 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. -------------------------------------------------------------------- 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 @@ -3369,36 +3427,35 @@ /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 virtual-networks node may - allow to redirect data-plane traffic to erroneous local or remote - network instances. + 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 virtual-network-ids node can result in - corrupted mapping sate that may propagate across the LISP network, - potentially resulting in forwarding of data-plane traffic to - arbitrary 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. + 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 + 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 @@ -3424,42 +3481,40 @@ 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 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 virtual-networks node can leak - the local mapping between LISP Instance IDs and local network - instances. + 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 - virtual-network-ids 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. + 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. @@ -3565,26 +3619,24 @@ 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, . Authors' Addresses Vina Ermagan - Cisco Systems - San Jose, CA + Google USA - Email: vermagan@cisco.com - + Email: ermagan@gmail.com Alberto Rodriguez-Natal Cisco Systems San Jose, CA USA Email: natal@cisco.com Florin Coras Cisco Systems San Jose, CA