idnits 2.17.1 draft-ietf-softwire-iftunnel-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 21, 2019) is 1801 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'TUNNELTYPE-IANA-REGISTRY' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Softwire Working Group M. Boucadair 3 Internet-Draft Orange 4 Intended status: Standards Track I. Farrer 5 Expires: November 22, 2019 Deutsche Telekom AG 6 R. Asati 7 Cisco Systems, Inc. 8 May 21, 2019 10 Tunnel Interface Types YANG Module 11 draft-ietf-softwire-iftunnel-06 13 Abstract 15 This document specifies the initial version of a YANG module 16 containing a collection of IANA maintained YANG identities, used as 17 interface types for tunnel interfaces. The module reflects the 18 "tunnelType" registry maintained by IANA. The latest revision of 19 this YANG module can be obtained from the IANA web site. 21 Tunnel type values are not directly added to the Tunnel Interface 22 Types YANG module; they must instead be added to the "tunnelType" 23 IANA registry. Once a new tunnel type registration is made by IANA 24 for a new tunneling scheme or even an existing one that is not 25 already listed in the current registry (e.g., LISP, NSH), IANA will 26 update the Tunnel Interface Types YANG module accordingly. 28 Some of the IETF-defined tunneling techniques are not listed in the 29 current IANA registry. It is not the intent of this document to 30 update the existing IANA registry with a comprehensive list of tunnel 31 technologies. Registrants must follow the IETF registration 32 procedure for interface types whenever a new tunnel type is needed. 34 Editorial Note (To be removed by RFC Editor) 36 Please update these statements in the document with the RFC number to 37 be assigned to this document: 39 o "This version of this YANG module is part of RFC XXXX;" 41 o "RFC XXXX: Tunnel Interface Types YANG Module"; 43 o "reference: RFC XXXX" 45 o "...must be updated as defined in RFCXXXX." 47 Please update the "revision" date of the YANG modules. 49 Status of This Memo 51 This Internet-Draft is submitted in full conformance with the 52 provisions of BCP 78 and BCP 79. 54 Internet-Drafts are working documents of the Internet Engineering 55 Task Force (IETF). Note that other groups may also distribute 56 working documents as Internet-Drafts. The list of current Internet- 57 Drafts is at https://datatracker.ietf.org/drafts/current/. 59 Internet-Drafts are draft documents valid for a maximum of six months 60 and may be updated, replaced, or obsoleted by other documents at any 61 time. It is inappropriate to use Internet-Drafts as reference 62 material or to cite them other than as "work in progress." 64 This Internet-Draft will expire on November 22, 2019. 66 Copyright Notice 68 Copyright (c) 2019 IETF Trust and the persons identified as the 69 document authors. All rights reserved. 71 This document is subject to BCP 78 and the IETF Trust's Legal 72 Provisions Relating to IETF Documents 73 (https://trustee.ietf.org/license-info) in effect on the date of 74 publication of this document. Please review these documents 75 carefully, as they describe your rights and restrictions with respect 76 to this document. Code Components extracted from this document must 77 include Simplified BSD License text as described in Section 4.e of 78 the Trust Legal Provisions and are provided without warranty as 79 described in the Simplified BSD License. 81 Table of Contents 83 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 84 2. IANA Tunnel Type YANG Module . . . . . . . . . . . . . . . . 3 85 3. Security Considerations . . . . . . . . . . . . . . . . . . . 7 86 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 87 4.1. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 8 88 4.2. Updates to the IANA tunnelType Table . . . . . . . . . . 9 89 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 90 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 91 6.1. Normative References . . . . . . . . . . . . . . . . . . 10 92 6.2. Informative References . . . . . . . . . . . . . . . . . 11 93 Appendix A. Example Usage . . . . . . . . . . . . . . . . . . . 14 94 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 96 1. Introduction 98 This document specifies the initial version of the iana-tunnel-type 99 YANG module containing a collection of IANA maintained YANG 100 identities identifying tunnel interface types. The module reflects 101 IANA's registry maintained at [TUNNELTYPE-IANA-REGISTRY]. The latest 102 revision of this module can be obtained from the IANA web site. 104 Tunnel-specific extensions may be added to the Interface module 105 [RFC8343] as a function of the tunnel type. An example of this is 106 provided in Appendix A. It is not the intention of this document to 107 define tunnel-specific extensions for every tunnel encapsulation 108 technology; those are discussed in dedicated documents such as 109 [I-D.ietf-softwire-yang]. Likewise, it is out of the scope of this 110 document to update the existing IANA registry 111 [TUNNELTYPE-IANA-REGISTRY] with a comprehensive list of tunnel 112 technologies. 114 This document uses the common YANG types defined in [RFC6991] and 115 adopts the Network Management Datastore Architecture (NMDA 116 [RFC8342]). 118 The terminology for describing YANG modules is defined in [RFC7950]. 119 The meanings of the symbols used in the tree diagram are defined in 120 [RFC8340]. 122 2. IANA Tunnel Type YANG Module 124 The iana-tunnel-type module imports the 'iana-if-type' module defined 125 in [RFC7224]. 127 The initial version of the module includes tunnel types defined in 128 [RFC4087], [RFC7856], [RFC7870], and [RFC6346]. 130 file "iana-tunnel-type@2019-04-04.yang" 132 module iana-tunnel-type { 133 yang-version 1.1; 134 namespace "urn:ietf:params:xml:ns:yang:iana-tunnel-type"; 135 prefix iana-tunnel-type; 137 import iana-if-type { 138 prefix ift; 139 reference 140 "RFC 7224: IANA Interface Type YANG Module"; 141 } 143 organization 144 "IANA"; 145 contact 146 "Internet Assigned Numbers Authority 148 Postal: ICANN 149 12025 Waterfront Drive, Suite 300 150 Los Angeles, CA 90094-2536 151 United States of America 152 Tel: +1 310 301 5800 153 "; 155 description 156 "This module contains a collection of YANG identities defined 157 by IANA and used as interface types for tunnel interfaces. 159 Copyright (c) 2019 IETF Trust and the persons identified as 160 authors of the code. All rights reserved. 162 Redistribution and use in source and binary forms, with or 163 without modification, is permitted pursuant to, and subject 164 to the license terms contained in, the Simplified BSD License 165 set forth in Section 4.c of the IETF Trust's Legal Provisions 166 Relating to IETF Documents 167 (http://trustee.ietf.org/license-info). 169 This version of this YANG module is part of RFC XXXX; see 170 the RFC itself for full legal notices."; 172 revision 2019-04-04 { 173 description 174 "Initial revision."; 175 reference 176 "RFC XXXX: Tunnel Interface Types YANG Module"; 177 } 178 identity other { 179 base ift:tunnel; 180 description 181 "None of the following values."; 182 reference 183 "RFC 4087: IP Tunnel MIB"; 184 } 185 identity direct { 186 base ift:tunnel; 187 description 188 "No intermediate header."; 189 reference 190 "RFC 2003: IP Encapsulation within IP 191 RFC 4213: Basic Transition Mechanisms for IPv6 Hosts 192 and Routers"; 193 } 194 identity gre { 195 base ift:tunnel; 196 description 197 "GRE encapsulation."; 198 reference 199 "RFC 1701: Generic Routing Encapsulation (GRE) 200 RFC 1702: Generic Routing Encapsulation over IPv4 networks 201 RFC 7676: IPv6 Support for Generic Routing Encapsulation 202 (GRE)"; 203 } 204 identity minimal { 205 base ift:tunnel; 206 description 207 "Minimal encapsulation."; 208 reference 209 "RFC 2004: Minimal Encapsulation within IP"; 210 } 211 identity l2tp { 212 base ift:tunnel; 213 description 214 "L2TP encapsulation."; 215 reference 216 "RFC 2661: Layer Two Tunneling Protocol (L2TP)"; 217 } 218 identity pptp { 219 base ift:tunnel; 220 description 221 "PPTP encapsulation."; 222 reference 223 "RFC 2637: Point-to-Point Tunneling Protocol (PPTP)"; 224 } 225 identity l2f { 226 base ift:tunnel; 227 description 228 "L2F encapsulation."; 229 reference 230 "RFC 2341: Cisco Layer Two Forwarding (Protocol) (L2F)"; 231 } 232 identity udp { 233 base ift:tunnel; 234 description 235 "UDP encapsulation."; 236 reference 237 "Section 3.1.11 of RFC 8085"; 238 } 239 identity atmp { 240 base ift:tunnel; 241 description 242 "ATMP encapsulation."; 243 reference 244 "RFC 2107: Ascend Tunnel Management Protocol - ATMP"; 245 } 246 identity msdp { 247 base ift:tunnel; 248 description 249 "MSDP encapsulation."; 250 reference 251 "RFC 3618: Multicast Source Discovery Protocol (MSDP)"; 252 } 253 identity sixtofour { 254 base ift:tunnel; 255 description 256 "6to4 encapsulation."; 257 reference 258 "RFC 3056: Connection of IPv6 Domains via IPv4 Clouds"; 259 } 260 identity sixoverfour { 261 base ift:tunnel; 262 description 263 "6over4 encapsulation."; 264 reference 265 "RFC 2529: Transmission of IPv6 over IPv4 Domains without 266 Explicit Tunnels"; 267 } 268 identity isatap { 269 base ift:tunnel; 270 description 271 "ISATAP encapsulation."; 272 reference 273 "RFC 5214: Intra-Site Automatic Tunnel Addressing Protocol 274 (ISATAP)"; 275 } 276 identity teredo { 277 base ift:tunnel; 278 description 279 "Teredo encapsulation."; 280 reference 281 "RFC 4380: Teredo- Tunneling IPv6 over UDP through 282 Network Address Translations (NATs)"; 283 } 284 identity iphttps { 285 base ift:tunnel; 286 description 287 "IP over HTTPS (IP-HTTPS) Tunneling Protocol."; 289 reference 290 "Microsoft Corporation, IP over HTTPS (IP-HTTPS) Tunneling 291 Protocol Specification, 292 https://msdn.microsoft.com/en-us/library/dd358571.aspx"; 293 } 294 identity softwiremesh { 295 base ift:tunnel; 296 description 297 "softwire mesh tunnel."; 298 reference 299 "RFC 5565: Softwire Mesh Framework"; 300 } 301 identity dslite { 302 base ift:tunnel; 303 description 304 "DS-Lite tunnel."; 305 reference 306 "RFC 6333: Dual-Stack Lite Broadband Deployments Following 307 IPv4 Exhaustion"; 308 } 309 identity aplusp { 310 base ift:tunnel; 311 description 312 "A+P encapsulation."; 313 reference 314 "RFC 6346: The Address plus Port (A+P) Approach to the IPv4 315 Address Shortage"; 316 } 317 } 318 320 3. Security Considerations 322 The YANG module specified in this document defines a schema for data 323 that is designed to be accessed via network management protocols such 324 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 325 is the secure transport layer, and the mandatory-to-implement secure 326 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 327 is HTTPS, and the mandatory-to-implement secure transport is TLS 328 [RFC8446]. 330 The Network Configuration Access Control Model (NACM) [RFC8341] 331 provides the means to restrict access for particular NETCONF or 332 RESTCONF users to a preconfigured subset of all available NETCONF or 333 RESTCONF protocol operations and content. 335 The module defined in this document defines YANG identities for the 336 iana-tunnel-types registry. These identies are intended to be 337 referenced by other YANG modules, and by themselves do not expose any 338 nodes which are writable, contain read-only state, or RPCs. As such, 339 there are no additional security issues to be considered relating to 340 the module defined in this document. 342 4. IANA Considerations 344 4.1. YANG Module 346 This document requests IANA to register the following URI in the "ns" 347 subregistry within the "IETF XML Registry" [RFC3688]: 349 URI: urn:ietf:params:xml:ns:yang:iana-tunnel-type 350 Registrant Contact: IANA. 351 XML: N/A; the requested URI is an XML namespace. 353 This document requests IANA to register the following following YANG 354 module in the "YANG Module Names" subregistry [RFC7950] within the 355 "YANG Parameters" registry. 357 Name: iana-tunnel-type 358 Namespace: urn:ietf:params:xml:ns:yang:iana-tunnel-type 359 Prefix: iana-tunnel-type 360 Reference: RFC XXXX 362 This document defines the initial version of the IANA-maintained 363 iana-tunnel-type YANG module. IANA is requested to add this note: 365 Tunnel type values must not be directly added to the iana-tunnel- 366 type YANG module. They must instead be respectively added to the 367 "tunnelType" sub-registry (under the "ifType definitions" 368 registry). 370 When a tunnel type is added to the "tunnelType" sub-registry, a new 371 "identity" statement must be added to the iana-tunnel-type YANG 372 module. The name of the "identity" is the lower-case of the 373 corresponding enumeration in the IANAifType-MIB (i.e., 374 IANAtunnelType). The "identity" statement should have the following 375 sub-statements defined: 377 "base": Contains 'ift:tunnel'. 379 "description": Replicates the description from the registry. 381 "reference": Replicates the reference from the registry and add the 382 title of the document. 384 Unassigned or reserved values are not present in the module. 386 When the iana-tunnel-type YANG module is updated, a new "revision" 387 statement must be added in front of the existing revision statements. 389 IANA is requested to add this note to "tunnelType" sub-registry: 391 When this registry is modified, the YANG module iana-tunnel-type 392 must be updated as defined in RFCXXXX. 394 4.2. Updates to the IANA tunnelType Table 396 This document requests IANA to update the following entries available 397 at https://www.iana.org/assignments/smi-numbers/smi- 398 numbers.xhtml#smi-numbers-6: 400 OLD: 402 Decimal Name Description References 403 2 direct no intermediate header [RFC4087] 404 3 gre GRE encapsulation [RFC4087] 405 4 minimal Minimal encapsulation [RFC4087] 406 5 l2tp L2TP encapsulation [RFC4087] 407 6 pptp PPTP encapsulation [RFC4087] 408 7 l2f L2F encapsulation [RFC4087] 409 8 udp UDP encapsulation [RFC4087] 410 9 atmp ATMP encapsulation [RFC4087] 411 10 msdp MSDP encapsulation [RFC4087] 412 11 sixToFour 6to4 encapsulation [RFC4087] 413 12 sixOverFour 6over4 encapsulation [RFC4087] 414 13 isatap ISATAP encapsulation [RFC4087] 415 14 teredo Teredo encapsulation [RFC4087] 416 16 softwireMesh softwire mesh tunnel [RFC7856] 417 17 dsLite DS-Lite tunnel [RFC7870] 418 NEW: 420 Decimal Name Description References 421 2 direct no intermediate header [RFC2003] 422 [RFC4213] 423 3 gre GRE encapsulation [RFC1701] 424 [RFC1702] 425 [RFC7676] 426 4 minimal Minimal encapsulation [RFC2004] 427 5 l2tp L2TP encapsulation [RFC2661] 428 6 pptp PPTP encapsulation [RFC2637] 429 7 l2f L2F encapsulation [RFC2341] 430 8 udp UDP encapsulation [RFC8085] 431 9 atmp ATMP encapsulation [RFC2107] 432 10 msdp MSDP encapsulation [RFC3618] 433 11 sixToFour 6to4 encapsulation [RFC3056] 434 12 sixOverFour 6over4 encapsulation [RFC2529] 435 13 isatap ISATAP encapsulation [RFC5214] 436 14 teredo Teredo encapsulation [RFC4380] 437 16 softwireMesh softwire mesh tunnel [RFC5565] 438 17 dsLite DS-Lite tunnel [RFC6333] 440 5. Acknowledgements 442 Special thanks to Tom Petch and Martin Bjorklund for the detailed 443 review and suggestions. 445 Thanks to Andy Bierman for the Yangdoctors review. 447 Thanks to Dale Worley, David Black, and Yaron Sheffer for the review. 449 6. References 451 6.1. Normative References 453 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 454 DOI 10.17487/RFC3688, January 2004, 455 . 457 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 458 and A. Bierman, Ed., "Network Configuration Protocol 459 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 460 . 462 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 463 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 464 . 466 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 467 RFC 6991, DOI 10.17487/RFC6991, July 2013, 468 . 470 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 471 RFC 7224, DOI 10.17487/RFC7224, May 2014, 472 . 474 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 475 RFC 7950, DOI 10.17487/RFC7950, August 2016, 476 . 478 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 479 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 480 . 482 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 483 Access Control Model", STD 91, RFC 8341, 484 DOI 10.17487/RFC8341, March 2018, 485 . 487 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 488 and R. Wilton, "Network Management Datastore Architecture 489 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 490 . 492 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 493 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 494 . 496 [TUNNELTYPE-IANA-REGISTRY] 497 Internet Assigned Numbers Authority, "ifType definitions: 498 tunnelType", . 501 6.2. Informative References 503 [I-D.ietf-softwire-yang] 504 Farrer, I. and M. Boucadair, "YANG Modules for IPv4-in- 505 IPv6 Address plus Port (A+P) Softwires", draft-ietf- 506 softwire-yang-16 (work in progress), January 2019. 508 [RFC1701] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic 509 Routing Encapsulation (GRE)", RFC 1701, 510 DOI 10.17487/RFC1701, October 1994, 511 . 513 [RFC1702] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic 514 Routing Encapsulation over IPv4 networks", RFC 1702, 515 DOI 10.17487/RFC1702, October 1994, 516 . 518 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, 519 DOI 10.17487/RFC2003, October 1996, 520 . 522 [RFC2004] Perkins, C., "Minimal Encapsulation within IP", RFC 2004, 523 DOI 10.17487/RFC2004, October 1996, 524 . 526 [RFC2107] Hamzeh, K., "Ascend Tunnel Management Protocol - ATMP", 527 RFC 2107, DOI 10.17487/RFC2107, February 1997, 528 . 530 [RFC2341] Valencia, A., Littlewood, M., and T. Kolar, "Cisco Layer 531 Two Forwarding (Protocol) "L2F"", RFC 2341, 532 DOI 10.17487/RFC2341, May 1998, 533 . 535 [RFC2529] Carpenter, B. and C. Jung, "Transmission of IPv6 over IPv4 536 Domains without Explicit Tunnels", RFC 2529, 537 DOI 10.17487/RFC2529, March 1999, 538 . 540 [RFC2637] Hamzeh, K., Pall, G., Verthein, W., Taarud, J., Little, 541 W., and G. Zorn, "Point-to-Point Tunneling Protocol 542 (PPTP)", RFC 2637, DOI 10.17487/RFC2637, July 1999, 543 . 545 [RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, 546 G., and B. Palter, "Layer Two Tunneling Protocol "L2TP"", 547 RFC 2661, DOI 10.17487/RFC2661, August 1999, 548 . 550 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 551 via IPv4 Clouds", RFC 3056, DOI 10.17487/RFC3056, February 552 2001, . 554 [RFC3618] Fenner, B., Ed. and D. Meyer, Ed., "Multicast Source 555 Discovery Protocol (MSDP)", RFC 3618, 556 DOI 10.17487/RFC3618, October 2003, 557 . 559 [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, 560 DOI 10.17487/RFC4087, June 2005, 561 . 563 [RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms 564 for IPv6 Hosts and Routers", RFC 4213, 565 DOI 10.17487/RFC4213, October 2005, 566 . 568 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 569 Network Address Translations (NATs)", RFC 4380, 570 DOI 10.17487/RFC4380, February 2006, 571 . 573 [RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 574 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, 575 DOI 10.17487/RFC5214, March 2008, 576 . 578 [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh 579 Framework", RFC 5565, DOI 10.17487/RFC5565, June 2009, 580 . 582 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 583 Stack Lite Broadband Deployments Following IPv4 584 Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011, 585 . 587 [RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to 588 the IPv4 Address Shortage", RFC 6346, 589 DOI 10.17487/RFC6346, August 2011, 590 . 592 [RFC7676] Pignataro, C., Bonica, R., and S. Krishnan, "IPv6 Support 593 for Generic Routing Encapsulation (GRE)", RFC 7676, 594 DOI 10.17487/RFC7676, October 2015, 595 . 597 [RFC7856] Cui, Y., Dong, J., Wu, P., Xu, M., and A. Yla-Jaaski, 598 "Softwire Mesh Management Information Base (MIB)", 599 RFC 7856, DOI 10.17487/RFC7856, May 2016, 600 . 602 [RFC7870] Fu, Y., Jiang, S., Dong, J., and Y. Chen, "Dual-Stack Lite 603 (DS-Lite) Management Information Base (MIB) for Address 604 Family Transition Routers (AFTRs)", RFC 7870, 605 DOI 10.17487/RFC7870, June 2016, 606 . 608 [RFC8085] Eggert, L., Fairhurst, G., and G. Shepherd, "UDP Usage 609 Guidelines", BCP 145, RFC 8085, DOI 10.17487/RFC8085, 610 March 2017, . 612 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 613 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 614 . 616 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 617 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 618 . 620 Appendix A. Example Usage 622 The following example illustrates how the Interface YANG module can 623 be augmented with tunnel-specific paramters. In this example, the 624 module is augmented with a 'remote-endpoint' for the tunnel. A tree 625 structure is provided below: 627 module: example-iftunnel-extension 628 augment /if:interfaces/if:interface: 629 +--rw remote-endpoint? inet:ipv6-address 631 The 'example-iftunnel-extension' module imports the modules defined 632 in [RFC6991] and [RFC8343] in addition to the "iana-tunnel-type" 633 module defined in this document. 635 module example-iftunnel-extension { 636 yang-version 1.1; 638 namespace "urn:ietf:params:xml:ns:yang:ietf-extension-example"; 639 prefix example; 641 import ietf-inet-types { 642 prefix inet; 643 reference 644 "Section 4 of RFC 6991"; 645 } 647 import ietf-interfaces { 648 prefix if; 649 reference 650 "RFC 8343: A YANG Data Model for Interface Management"; 651 } 653 import iana-tunnel-type { 654 prefix iana-tunnel-type; 655 reference 656 "RFC XXXX: A Tunnel Extension to the Interface Management 657 YANG Module"; 658 } 660 organization "IETF Softwire Working Group"; 662 contact 664 "WG Web: 665 WG List: 667 Author: Mohamed Boucadair 668 "; 670 description 671 "This is an example YANG module to extend the Interface YANG 672 module with tunnel-specific parameters. 674 Copyright (c) 2019 IETF Trust and the persons identified as 675 authors of the code. All rights reserved. 677 Redistribution and use in source and binary forms, with or 678 without modification, is permitted pursuant to, and subject 679 to the license terms contained in, the Simplified BSD License 680 set forth in Section 4.c of the IETF Trust's Legal Provisions 681 Relating to IETF Documents 682 (http://trustee.ietf.org/license-info). 684 This version of this YANG module is part of RFC XXXX; see 685 the RFC itself for full legal notices."; 687 revision 2019-04-04 { 688 description 689 "Initial revision."; 690 reference 691 "RFC XXXX: Tunnel Interface Types YANG Module"; 692 } 694 augment "/if:interfaces/if:interface" { 695 when "derived-from(if:type, 'iana-tunnel-type:gre')"; 696 description 697 "Augments Interface module with specific tunnel parameters."; 699 leaf remote-endpoint { 700 type inet:ipv6-address; 701 description 702 "IPv6 address of the remote GRE endpoint."; 703 } 705 } 706 } 708 Authors' Addresses 710 Mohamed Boucadair 711 Orange 712 Rennes 35000 713 France 715 Email: mohamed.boucadair@orange.com 717 Ian Farrer 718 Deutsche Telekom AG 719 CTO-ATI,Landgrabenweg 151 720 Bonn, NRW 53227 721 Germany 723 Email: ian.farrer@telekom.de 725 Rajiv Asati 726 Cisco Systems, Inc. 727 7025 Kit Creek Rd. 728 RTP, NC 27709 729 USA 731 Email: Rajiva@cisco.com