draft-ietf-lisp-yang-06.txt   draft-ietf-lisp-yang-07.txt 
LISP Working Group V. Ermagan LISP Working Group V. Ermagan
Internet-Draft A. Rodriguez-Natal Internet-Draft A. Rodriguez-Natal
Intended status: Experimental F. Coras Intended status: Experimental F. Coras
Expires: July 8, 2018 C. Moberg Expires: September 6, 2018 C. Moberg
R. Rahman R. Rahman
Cisco Systems Cisco Systems
A. Cabellos-Aparicio A. Cabellos-Aparicio
Technical University of Catalonia Technical University of Catalonia
F. Maino F. Maino
Cisco Systems Cisco Systems
January 4, 2018 March 5, 2018
LISP YANG Model LISP YANG Model
draft-ietf-lisp-yang-06 draft-ietf-lisp-yang-07
Abstract Abstract
This document describes a YANG data model to use with the Locator/ID This document describes a YANG data model to use with the Locator/ID
Separation Protocol (LISP). Separation Protocol (LISP).
The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 8, 2018. This Internet-Draft will expire on September 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 16 skipping to change at page 2, line 19
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. LISP Module . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. LISP Module . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Module Structure . . . . . . . . . . . . . . . . . . . . 3 2.1. Module Structure . . . . . . . . . . . . . . . . . . . . 3
2.2. Module Definition . . . . . . . . . . . . . . . . . . . . 5 2.2. Module Definition . . . . . . . . . . . . . . . . . . . . 5
3. LISP-ITR Module . . . . . . . . . . . . . . . . . . . . . . . 13 3. LISP-ITR Module . . . . . . . . . . . . . . . . . . . . . . . 13
3.1. Module Structure . . . . . . . . . . . . . . . . . . . . 13 3.1. Module Structure . . . . . . . . . . . . . . . . . . . . 14
3.2. Module Definition . . . . . . . . . . . . . . . . . . . . 17 3.2. Module Definition . . . . . . . . . . . . . . . . . . . . 18
4. LISP-ETR Module . . . . . . . . . . . . . . . . . . . . . . . 20 4. LISP-ETR Module . . . . . . . . . . . . . . . . . . . . . . . 21
4.1. Module Structure . . . . . . . . . . . . . . . . . . . . 20 4.1. Module Structure . . . . . . . . . . . . . . . . . . . . 21
4.2. Module Definition . . . . . . . . . . . . . . . . . . . . 22 4.2. Module Definition . . . . . . . . . . . . . . . . . . . . 23
5. LISP-Map-Server Module . . . . . . . . . . . . . . . . . . . 26 5. LISP-Map-Server Module . . . . . . . . . . . . . . . . . . . 27
5.1. Module Structure . . . . . . . . . . . . . . . . . . . . 26 5.1. Module Structure . . . . . . . . . . . . . . . . . . . . 27
5.2. Module Definition . . . . . . . . . . . . . . . . . . . . 32 5.2. Module Definition . . . . . . . . . . . . . . . . . . . . 33
6. LISP-Map-Resolver Module . . . . . . . . . . . . . . . . . . 37 6. LISP-Map-Resolver Module . . . . . . . . . . . . . . . . . . 39
6.1. Module Structure . . . . . . . . . . . . . . . . . . . . 37 6.1. Module Structure . . . . . . . . . . . . . . . . . . . . 39
6.2. Module Definition . . . . . . . . . . . . . . . . . . . . 38 6.2. Module Definition . . . . . . . . . . . . . . . . . . . . 39
7. LISP-Address-Types Module . . . . . . . . . . . . . . . . . . 39 7. LISP-Address-Types Module . . . . . . . . . . . . . . . . . . 41
7.1. Module Definition . . . . . . . . . . . . . . . . . . . . 39 7.1. Module Definition . . . . . . . . . . . . . . . . . . . . 41
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 54 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 55
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
10. Security Considerations . . . . . . . . . . . . . . . . . . . 54 10. Security Considerations . . . . . . . . . . . . . . . . . . . 56
11. Normative References . . . . . . . . . . . . . . . . . . . . 54 11. Normative References . . . . . . . . . . . . . . . . . . . . 56
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 55 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 56
1. Introduction 1. Introduction
The Locator/ID Separation Protocol (LISP) defines several network The Locator/ID Separation Protocol (LISP) defines several network
elements subject to be configured. This document presents the YANG elements subject to be configured. This document presents the YANG
data models required for basic configuration of all major LISP data models required for basic configuration of all major LISP
[RFC6830]elements. The models also capture some essential [RFC6830]elements. The models also capture some essential
operational data elements as well. operational data elements as well.
2. LISP Module 2. LISP Module
skipping to change at page 5, line 23 skipping to change at page 5, line 23
+--rw lisp-router-instance* [lisp-router-instance-id] +--rw lisp-router-instance* [lisp-router-instance-id]
+--rw lisp-router-instance-id int32 +--rw lisp-router-instance-id int32
+--rw lisp-role* [lisp-role-type] +--rw lisp-role* [lisp-role-type]
| +--rw lisp-role-type lisp-role-ref | +--rw lisp-role-type lisp-role-ref
+--rw lisp-router-id +--rw lisp-router-id
+--rw site-id? uint64 +--rw site-id? uint64
+--rw xtr-id? lisp:xtr-id-type +--rw xtr-id? lisp:xtr-id-type
2.2. Module Definition 2.2. Module Definition
<CODE BEGINS> file "ietf-lisp@2017-07-01.yang" <CODE BEGINS> file "ietf-lisp@2018-03-05.yang"
module ietf-lisp { module ietf-lisp {
namespace "urn:ietf:params:xml:ns:yang:ietf-lisp"; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp";
prefix lisp; prefix lisp;
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
} }
import ietf-lisp-address-types { import ietf-lisp-address-types {
prefix lcaf; prefix lcaf;
} }
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
organization organization
"IETF LISP (Locator/ID Separation Protocol) Working Group"; "IETF LISP (Locator/ID Separation Protocol) Working Group";
contact contact
"lisp@ietf.org"; "WG Web: <http://tools.ietf.org/wg/lisp/>
WG List: <mailto:lisp@ietf.org>
Editor: Vina Ermagan
<mailto:vermagan@cisco.com>
Editor: Alberto Rodriguez-Natal
<mailto:natal@cisco.com>
Editor: Reshad Rahman
<mailto:rrahman@cisco.com>";
description description
"This YANG module defines the generic parameters for LISP. "This YANG module defines the generic parameters for LISP.
The module can be extended by vendors to define vendor-specific The module can be extended by vendors to define vendor-specific
LISP parameters and policies. LISP parameters and policies.
Copyright (c) 2014 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 6338; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
"; ";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
reference "RFC XXXX";
revision 2017-07-01 { revision 2018-03-05 {
description description
"Initial revision."; "Initial revision.";
reference reference
"https://tools.ietf.org/html/rfc6830"; "https://tools.ietf.org/html/rfc6830";
} }
identity lisp-role { identity lisp-role {
description description
"LISP router role."; "LISP router role.";
} }
identity itr { identity itr {
skipping to change at page 17, line 48 skipping to change at page 18, line 14
| +--rw service-path | +--rw service-path
| +--rw service-path-id? service-path-id-type | +--rw service-path-id? service-path-id-type
| +--rw service-index? uint8 | +--rw service-index? uint8
+--rw priority? uint8 +--rw priority? uint8
+--rw weight? uint8 +--rw weight? uint8
+--rw multicast-priority? uint8 +--rw multicast-priority? uint8
+--rw multicast-weight? uint8 +--rw multicast-weight? uint8
3.2. Module Definition 3.2. Module Definition
<CODE BEGINS> file "ietf-lisp-itr@2017-07-01.yang" <CODE BEGINS> file "ietf-lisp-itr@2018-03-05.yang"
module ietf-lisp-itr { module ietf-lisp-itr {
namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-itr"; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-itr";
prefix lisp-itr; prefix lisp-itr;
import ietf-lisp { import ietf-lisp {
prefix lisp; prefix lisp;
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
organization organization
"IETF LISP (Locator/ID Separation Protocol) Working Group"; "IETF LISP (Locator/ID Separation Protocol) Working Group";
contact contact
"lisp@ietf.org"; "WG Web: <http://tools.ietf.org/wg/lisp/>
WG List: <mailto:lisp@ietf.org>
Editor: Vina Ermagan
<mailto:vermagan@cisco.com>
Editor: Alberto Rodriguez-Natal
<mailto:natal@cisco.com>
Editor: Reshad Rahman
<mailto:rrahman@cisco.com>";
description description
"This YANG module defines the generic parameters for a LISP "This YANG module defines the generic parameters for a LISP
ITR. The module can be extended by vendors to define ITR. The module can be extended by vendors to define
vendor-specific parameters and policies. vendor-specific parameters and policies.
Copyright (c) 2015 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
This version of this YANG module is part of RFC 6338; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
"; ";
revision 2017-07-01 { // RFC Ed.: replace XXXX with actual RFC number and remove
// this note
reference "RFC XXXX";
revision 2018-03-05 {
description description
"Initial revision."; "Initial revision.";
reference reference
"https://tools.ietf.org/html/rfc6830"; "https://tools.ietf.org/html/rfc6830";
} }
augment "/lisp:lisp/lisp:lisp-router-instances/lisp:lisp-router-instance" { augment "/lisp:lisp/lisp:lisp-router-instances/lisp:lisp-router-instance" {
when "lisp:lisp-role/lisp:lisp-role-type = 'lisp:itr' or when "lisp:lisp-role/lisp:lisp-role-type = 'lisp:itr' or
lisp:lisp-role/lisp:lisp-role-type = 'lisp:pitr'" { lisp:lisp-role/lisp:lisp-role-type = 'lisp:pitr'" {
description description
"Augment is valid when LISP role type is ITR or PITR."; "Augment is valid when LISP role type is ITR or PITR.";
skipping to change at page 22, line 36 skipping to change at page 23, line 19
| +--rw service-path-id? service-path-id-type | +--rw service-path-id? service-path-id-type
| +--rw service-index? uint8 | +--rw service-index? uint8
+--rw rlocs? -> /lisp:lisp/locator-sets/locator-set/locator-set-name +--rw rlocs? -> /lisp:lisp/locator-sets/locator-set/locator-set-name
+--rw record-ttl? uint32 +--rw record-ttl? uint32
+--rw want-map-notify? boolean +--rw want-map-notify? boolean
+--rw proxy-reply? boolean +--rw proxy-reply? boolean
+--rw registration-interval? uint16 +--rw registration-interval? uint16
4.2. Module Definition 4.2. Module Definition
<CODE BEGINS> file "ietf-lisp-etr@2017-07-01.yang" <CODE BEGINS> file "ietf-lisp-etr@2018-03-05.yang"
module ietf-lisp-etr { module ietf-lisp-etr {
namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-etr"; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-etr";
prefix lisp-etr; prefix lisp-etr;
import ietf-lisp { import ietf-lisp {
prefix lisp; prefix lisp;
} }
import ietf-lisp-address-types { import ietf-lisp-address-types {
prefix lcaf; prefix lcaf;
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
organization organization
"IETF LISP (Locator/ID Separation Protocol) Working Group"; "IETF LISP (Locator/ID Separation Protocol) Working Group";
contact contact
"lisp@ietf.org"; "WG Web: <http://tools.ietf.org/wg/lisp/>
WG List: <mailto:lisp@ietf.org>
Editor: Vina Ermagan
<mailto:vermagan@cisco.com>
Editor: Alberto Rodriguez-Natal
<mailto:natal@cisco.com>
Editor: Reshad Rahman
<mailto:rrahman@cisco.com>";
description description
"This YANG module defines the generic parameters for a LISP "This YANG module defines the generic parameters for a LISP
ETR. The module can be extended by vendors to define ETR. The module can be extended by vendors to define
vendor-specific parameters and policies. vendor-specific parameters and policies.
Copyright (c) 2015 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 6338; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
"; ";
revision 2017-07-01 { // RFC Ed.: replace XXXX with actual RFC number and remove
// this note
reference "RFC XXXX";
revision 2018-03-05 {
description description
"Initial revision."; "Initial revision.";
reference reference
"https://tools.ietf.org/html/rfc6830"; "https://tools.ietf.org/html/rfc6830";
} }
augment "/lisp:lisp/lisp:lisp-router-instances/lisp:lisp-router-instance" { augment "/lisp:lisp/lisp:lisp-router-instances/lisp:lisp-router-instance" {
when "lisp:lisp-role/lisp:lisp-role-type = 'lisp:etr' or when "lisp:lisp-role/lisp:lisp-role-type = 'lisp:etr' or
lisp:lisp-role/lisp:lisp-role-type = 'lisp:petr'" { lisp:lisp-role/lisp:lisp-role-type = 'lisp:petr'" {
description description
"Augment is valid when LISP device type is (P)ETR."; "Augment is valid when LISP device type is (P)ETR.";
skipping to change at page 32, line 34 skipping to change at page 33, line 31
| +--ro number-registered-eids? uint32 | +--ro number-registered-eids? uint32
+--ro counters +--ro counters
+--ro map-registers-in? yang:counter32 +--ro map-registers-in? yang:counter32
+--ro map-registers-in-auth-failed? yang:counter32 +--ro map-registers-in-auth-failed? yang:counter32
+--ro map-notify-records-out? yang:counter32 +--ro map-notify-records-out? yang:counter32
+--ro proxy-reply-records-out? yang:counter32 +--ro proxy-reply-records-out? yang:counter32
+--ro map-requests-forwarded-out? yang:counter32 +--ro map-requests-forwarded-out? yang:counter32
5.2. Module Definition 5.2. Module Definition
<CODE BEGINS> file "ietf-lisp-mapserver@2017-07-01.yang" <CODE BEGINS> file "ietf-lisp-mapserver@2018-03-05.yang"
module ietf-lisp-mapserver { module ietf-lisp-mapserver {
namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-mapserver"; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-mapserver";
prefix lisp-ms; prefix lisp-ms;
import ietf-lisp { import ietf-lisp {
prefix lisp; prefix lisp;
} }
import ietf-lisp-address-types { import ietf-lisp-address-types {
prefix lcaf; prefix lcaf;
} }
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
revision-date 2013-07-15; revision-date 2013-07-15;
} }
organization organization
"IETF LISP (Locator/ID Separation Protocol) Working Group"; "IETF LISP (Locator/ID Separation Protocol) Working Group";
contact contact
"lisp@ietf.org"; "WG Web: <http://tools.ietf.org/wg/lisp/>
WG List: <mailto:lisp@ietf.org>
Editor: Vina Ermagan
<mailto:vermagan@cisco.com>
Editor: Alberto Rodriguez-Natal
<mailto:natal@cisco.com>
Editor: Reshad Rahman
<mailto:rrahman@cisco.com>";
description description
"This YANG module defines the generic parameters for a LISP "This YANG module defines the generic parameters for a LISP
Map-Server. The module can be extended by vendors to define Map-Server. The module can be extended by vendors to define
vendor-specific parameters and policies. vendor-specific parameters and policies.
Copyright (c) 2015 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 6338; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
"; ";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
reference "RFC XXXX";
revision 2017-07-01 { revision 2018-03-05 {
description description
"Initial revision."; "Initial revision.";
reference reference
"https://tools.ietf.org/html/rfc6833"; "https://tools.ietf.org/html/rfc6833";
} }
identity ms { identity ms {
base lisp:lisp-role; base lisp:lisp-role;
description description
"LISP Map-Server."; "LISP Map-Server.";
skipping to change at page 33, line 42 skipping to change at page 35, line 4
base lisp:lisp-role; base lisp:lisp-role;
description description
"LISP Map-Server."; "LISP Map-Server.";
} }
grouping ms-counters { grouping ms-counters {
description "Group that defines map-server counters."; description "Group that defines map-server counters.";
container counters { container counters {
config false; config false;
description "Container for the counters"; description "Container for the counters";
leaf map-registers-in { leaf map-registers-in {
type yang:counter32; type yang:counter64;
description "Number of incoming Map-Register messages"; description "Number of incoming Map-Register messages";
} }
leaf map-registers-in-auth-failed { leaf map-registers-in-auth-failed {
type yang:counter32; type yang:counter64;
description description
"Number of incoming Map-Register messages failed "Number of incoming Map-Register messages failed
authentication"; authentication";
} }
leaf map-notify-records-out { leaf map-notify-records-out {
type yang:counter32; type yang:counter64;
description description
"Number of outgoing Map-Notify records"; "Number of outgoing Map-Notify records";
} }
leaf proxy-reply-records-out { leaf proxy-reply-records-out {
type yang:counter32; type yang:counter64;
description description
"Number of outgoing proxy Map-Reply records"; "Number of outgoing proxy Map-Reply records";
} }
leaf map-requests-forwarded-out { leaf map-requests-forwarded-out {
type yang:counter32; type yang:counter64;
description description
"Number of outgoing Map-Requests forwarded to ETR"; "Number of outgoing Map-Requests forwarded to ETR";
} }
} }
} }
augment "/lisp:lisp/lisp:lisp-router-instances" augment "/lisp:lisp/lisp:lisp-router-instances"
+ "/lisp:lisp-router-instance" { + "/lisp:lisp-router-instance" {
when "lisp:lisp-role/lisp:lisp-role-type = 'lisp-ms:ms'" { when "lisp:lisp-role/lisp:lisp-role-type = 'lisp-ms:ms'" {
description description
skipping to change at page 36, line 23 skipping to change at page 37, line 31
leaf mapping-expiration-timeout { leaf mapping-expiration-timeout {
type int16; type int16;
units "seconds"; units "seconds";
default "180"; //3 times the mapregister int default "180"; //3 times the mapregister int
description description
"Time before mapping is expired if no new "Time before mapping is expired if no new
registrations are received."; registrations are received.";
} }
container mapping-records { container mapping-records {
description description
"Datastore of registred mappings."; "Datastore of registered mappings.";
list mapping-record{ list mapping-record{
key xtr-id; key xtr-id;
description description
"Registered mapping."; "Registered mapping.";
leaf xtr-id { leaf xtr-id {
type lisp:xtr-id-type; type lisp:xtr-id-type;
description "xTR ID"; description "xTR ID";
} }
leaf site-id { leaf site-id {
type uint64; type uint64;
skipping to change at page 38, line 7 skipping to change at page 39, line 21
6.1. Module Structure 6.1. Module Structure
module: ietf-lisp-mapresolver module: ietf-lisp-mapresolver
augment /lisp:lisp/lisp:lisp-router-instances/lisp:lisp-router-instance: augment /lisp:lisp/lisp:lisp-router-instances/lisp:lisp-router-instance:
+--rw map-resolver! +--rw map-resolver!
+--rw mapping-system-type? lisp:mapping-system-ref +--rw mapping-system-type? lisp:mapping-system-ref
+--rw ms-address? inet:ip-address +--rw ms-address? inet:ip-address
6.2. Module Definition 6.2. Module Definition
<CODE BEGINS> file "ietf-lisp-mapresolver@2017-07-01.yang" <CODE BEGINS> file "ietf-lisp-mapresolver@2018-03-05.yang"
module ietf-lisp-mapresolver { module ietf-lisp-mapresolver {
namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-mapresolver"; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-mapresolver";
prefix lisp-mr; prefix lisp-mr;
import ietf-lisp { import ietf-lisp {
prefix lisp; prefix lisp;
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
organization organization
"IETF LISP (Locator/ID Separation Protocol) Working Group"; "IETF LISP (Locator/ID Separation Protocol) Working Group";
contact contact
"lisp@ietf.org"; "WG Web: <http://tools.ietf.org/wg/lisp/>
WG List: <mailto:lisp@ietf.org>
Editor: Vina Ermagan
<mailto:vermagan@cisco.com>
Editor: Alberto Rodriguez-Natal
<mailto:natal@cisco.com>
Editor: Reshad Rahman
<mailto:rrahman@cisco.com>";
description description
"This YANG module defines the generic parameters for a LISP "This YANG module defines the generic parameters for a LISP
Map-Resolver. The module can be extended by vendors to define Map-Resolver. The module can be extended by vendors to define
vendor-specific parameters and policies. vendor-specific parameters and policies.
Copyright (c) 2015 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 6338; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
"; ";
revision 2017-07-01 { // RFC Ed.: replace XXXX with actual RFC number and remove
// this note
reference "RFC XXXX";
revision 2018-05-03 {
description description
"Initial revision."; "Initial revision.";
reference reference
"https://tools.ietf.org/html/rfc6833"; "https://tools.ietf.org/html/rfc6833";
} }
identity mr { identity mr {
base lisp:lisp-role; base lisp:lisp-role;
description description
"LISP Map-Resolver."; "LISP Map-Resolver.";
} }
skipping to change at page 39, line 39 skipping to change at page 41, line 18
} }
<CODE ENDS> <CODE ENDS>
7. LISP-Address-Types Module 7. LISP-Address-Types Module
This module captures the various LISP address types, and is an This module captures the various LISP address types, and is an
essential building block used in other LISP modules. essential building block used in other LISP modules.
7.1. Module Definition 7.1. Module Definition
<CODE BEGINS> file "ietf-lisp-address-types@2015-11-05.yang" <CODE BEGINS> file "ietf-lisp-address-types@2018-03-05.yang"
module ietf-lisp-address-types { module ietf-lisp-address-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-address-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-lisp-address-types";
prefix laddr; prefix laddr;
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
revision-date 2013-07-15; revision-date 2013-07-15;
} }
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
revision-date 2013-07-15; revision-date 2013-07-15;
} }
organization organization
"IETF LISP (Locator/ID Separation Protocol) Working Group"; "IETF LISP (Locator/ID Separation Protocol) Working Group";
contact contact
"lisp@ietf.org"; "WG Web: <http://tools.ietf.org/wg/lisp/>
WG List: <mailto:lisp@ietf.org>
Editor: Vina Ermagan
<mailto:vermagan@cisco.com>
Editor: Alberto Rodriguez-Natal
<mailto:natal@cisco.com>
Editor: Reshad Rahman
<mailto:rrahman@cisco.com>";
description description
"This YANG module defines the LISP Canonical Address Formats "This YANG module defines the LISP Canonical Address Formats
(LCAF) for LISP. The module can be extended by vendors to (LCAF) for LISP. The module can be extended by vendors to
define vendor-specific parameters. define vendor-specific parameters.
Copyright (c) 2014 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 6338; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
"; ";
revision 2015-11-05 { // RFC Ed.: replace XXXX with actual RFC number and remove
// this note
reference "RFC XXXX";
revision 2018-03-05 {
description description
"Initial revision."; "Initial revision.";
reference reference
"http://tools.ietf.org/html/draft-ietf-lisp-lcaf-10"; "http://tools.ietf.org/html/draft-ietf-lisp-lcaf-10";
} }
identity lisp-address-family { identity lisp-address-family {
description description
"Base identity from which identities describing LISP address "Base identity from which identities describing LISP address
families are derived."; families are derived.";
} }
 End of changes. 46 change blocks. 
60 lines changed or deleted 143 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/