idnits 2.17.1 draft-ietf-softwire-iftunnel-07.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 (June 13, 2019) is 1778 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' == Outdated reference: A later version (-07) exists of draft-thaler-iftype-reg-02 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 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: December 15, 2019 Deutsche Telekom AG 6 R. Asati 7 Cisco Systems, Inc. 8 June 13, 2019 10 Tunnel Interface Types YANG Module 11 draft-ietf-softwire-iftunnel-07 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 December 15, 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. Guidelines and registration procedures for interface 113 types and sub-types are discussed in [I-D.thaler-iftype-reg]. 115 This document uses the common YANG types defined in [RFC6991] and 116 adopts the Network Management Datastore Architecture (NMDA 117 [RFC8342]). 119 The terminology for describing YANG modules is defined in [RFC7950]. 120 The meanings of the symbols used in the tree diagram are defined in 121 [RFC8340]. 123 2. IANA Tunnel Type YANG Module 125 The iana-tunnel-type module imports the 'iana-if-type' module defined 126 in [RFC7224]. 128 The initial version of the module includes tunnel types defined in 129 [RFC4087], [RFC7856], [RFC7870], and [RFC6346]. 131 file "iana-tunnel-type@2019-04-04.yang" 133 module iana-tunnel-type { 134 yang-version 1.1; 135 namespace "urn:ietf:params:xml:ns:yang:iana-tunnel-type"; 136 prefix iana-tunnel-type; 138 import iana-if-type { 139 prefix ift; 140 reference 141 "RFC 7224: IANA Interface Type YANG Module"; 142 } 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."; 288 reference 289 "Microsoft Corporation, IP over HTTPS (IP-HTTPS) Tunneling 290 Protocol Specification, 291 https://msdn.microsoft.com/en-us/library/dd358571.aspx"; 292 } 293 identity softwiremesh { 294 base ift:tunnel; 295 description 296 "softwire mesh tunnel."; 297 reference 298 "RFC 5565: Softwire Mesh Framework"; 299 } 300 identity dslite { 301 base ift:tunnel; 302 description 303 "DS-Lite tunnel."; 304 reference 305 "RFC 6333: Dual-Stack Lite Broadband Deployments Following 306 IPv4 Exhaustion"; 307 } 308 identity aplusp { 309 base ift:tunnel; 310 description 311 "A+P encapsulation."; 312 reference 313 "RFC 6346: The Address plus Port (A+P) Approach to the IPv4 314 Address Shortage"; 315 } 316 } 317 319 3. Security Considerations 321 The YANG module specified in this document defines a schema for data 322 that is designed to be accessed via network management protocols such 323 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 324 is the secure transport layer, and the mandatory-to-implement secure 325 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 326 is HTTPS, and the mandatory-to-implement secure transport is TLS 327 [RFC8446]. 329 The Network Configuration Access Control Model (NACM) [RFC8341] 330 provides the means to restrict access for particular NETCONF or 331 RESTCONF users to a preconfigured subset of all available NETCONF or 332 RESTCONF protocol operations and content. 334 The module defined in this document defines YANG identities for the 335 iana-tunnel-types registry. These identities are intended to be 336 referenced by other YANG modules, and by themselves do not expose any 337 nodes which are writable, contain read-only state, or RPCs. As such, 338 there are no additional security issues to be considered relating to 339 the module defined in this document. 341 4. IANA Considerations 343 4.1. YANG Module 345 This document requests IANA to register the following URI in the "ns" 346 subregistry within the "IETF XML Registry" [RFC3688]: 348 URI: urn:ietf:params:xml:ns:yang:iana-tunnel-type 349 Registrant Contact: IANA. 350 XML: N/A; the requested URI is an XML namespace. 352 This document requests IANA to register the following following YANG 353 module in the "YANG Module Names" subregistry [RFC7950] within the 354 "YANG Parameters" registry. 356 Name: iana-tunnel-type 357 Namespace: urn:ietf:params:xml:ns:yang:iana-tunnel-type 358 Prefix: iana-tunnel-type 359 Reference: RFC XXXX 361 This document defines the initial version of the IANA-maintained 362 iana-tunnel-type YANG module. IANA is requested to add this note: 364 Tunnel type values must not be directly added to the iana-tunnel- 365 type YANG module. They must instead be respectively added to the 366 "tunnelType" sub-registry (under the "ifType definitions" 367 registry). 369 When a tunnel type is added to the "tunnelType" sub-registry, a new 370 "identity" statement must be added to the iana-tunnel-type YANG 371 module. The name of the "identity" is the lower-case of the 372 corresponding enumeration in the IANAifType-MIB (i.e., 373 IANAtunnelType). The "identity" statement should have the following 374 sub-statements defined: 376 "base": Contains 'ift:tunnel'. 378 "description": Replicates the description from the registry. 380 "reference": Replicates the reference from the registry and add the 381 title of the document. 383 Unassigned or reserved values are not present in the module. 385 When the iana-tunnel-type YANG module is updated, a new "revision" 386 statement must be added in front of the existing revision statements. 388 IANA is requested to add this note to "tunnelType" sub-registry: 390 When this registry is modified, the YANG module iana-tunnel-type 391 must be updated as defined in RFCXXXX. 393 4.2. Updates to the IANA tunnelType Table 395 This document requests IANA to update the following entries available 396 at https://www.iana.org/assignments/smi-numbers/smi- 397 numbers.xhtml#smi-numbers-6: 399 OLD: 401 Decimal Name Description References 402 2 direct no intermediate header [RFC4087] 403 3 gre GRE encapsulation [RFC4087] 404 4 minimal Minimal encapsulation [RFC4087] 405 5 l2tp L2TP encapsulation [RFC4087] 406 6 pptp PPTP encapsulation [RFC4087] 407 7 l2f L2F encapsulation [RFC4087] 408 8 udp UDP encapsulation [RFC4087] 409 9 atmp ATMP encapsulation [RFC4087] 410 10 msdp MSDP encapsulation [RFC4087] 411 11 sixToFour 6to4 encapsulation [RFC4087] 412 12 sixOverFour 6over4 encapsulation [RFC4087] 413 13 isatap ISATAP encapsulation [RFC4087] 414 14 teredo Teredo encapsulation [RFC4087] 415 16 softwireMesh softwire mesh tunnel [RFC7856] 416 17 dsLite DS-Lite tunnel [RFC7870] 417 NEW: 419 Decimal Name Description References 420 2 direct no intermediate header [RFC2003] 421 [RFC4213] 422 3 gre GRE encapsulation [RFC1701] 423 [RFC1702] 424 [RFC7676] 425 4 minimal Minimal encapsulation [RFC2004] 426 5 l2tp L2TP encapsulation [RFC2661] 427 6 pptp PPTP encapsulation [RFC2637] 428 7 l2f L2F encapsulation [RFC2341] 429 8 udp UDP encapsulation [RFC8085] 430 9 atmp ATMP encapsulation [RFC2107] 431 10 msdp MSDP encapsulation [RFC3618] 432 11 sixToFour 6to4 encapsulation [RFC3056] 433 12 sixOverFour 6over4 encapsulation [RFC2529] 434 13 isatap ISATAP encapsulation [RFC5214] 435 14 teredo Teredo encapsulation [RFC4380] 436 16 softwireMesh softwire mesh tunnel [RFC5565] 437 17 dsLite DS-Lite tunnel [RFC6333] 439 5. Acknowledgements 441 Special thanks to Tom Petch and Martin Bjorklund for the detailed 442 review and suggestions. 444 Thanks to Andy Bierman for the Yangdoctors review. 446 Thanks to Dale Worley, David Black, and Yaron Sheffer for the review. 448 6. References 450 6.1. Normative References 452 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 453 DOI 10.17487/RFC3688, January 2004, 454 . 456 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 457 and A. Bierman, Ed., "Network Configuration Protocol 458 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 459 . 461 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 462 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 463 . 465 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 466 RFC 6991, DOI 10.17487/RFC6991, July 2013, 467 . 469 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 470 RFC 7224, DOI 10.17487/RFC7224, May 2014, 471 . 473 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 474 RFC 7950, DOI 10.17487/RFC7950, August 2016, 475 . 477 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 478 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 479 . 481 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 482 Access Control Model", STD 91, RFC 8341, 483 DOI 10.17487/RFC8341, March 2018, 484 . 486 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 487 and R. Wilton, "Network Management Datastore Architecture 488 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 489 . 491 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 492 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 493 . 495 [TUNNELTYPE-IANA-REGISTRY] 496 Internet Assigned Numbers Authority, "ifType definitions: 497 tunnelType", . 500 6.2. Informative References 502 [I-D.ietf-softwire-yang] 503 Farrer, I. and M. Boucadair, "YANG Modules for IPv4-in- 504 IPv6 Address plus Port (A+P) Softwires", draft-ietf- 505 softwire-yang-16 (work in progress), January 2019. 507 [I-D.thaler-iftype-reg] 508 Thaler, D. and D. Romascanu, "Guidelines and Registration 509 Procedures for Interface Types", draft-thaler-iftype- 510 reg-02 (work in progress), March 2019. 512 [RFC1701] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic 513 Routing Encapsulation (GRE)", RFC 1701, 514 DOI 10.17487/RFC1701, October 1994, 515 . 517 [RFC1702] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic 518 Routing Encapsulation over IPv4 networks", RFC 1702, 519 DOI 10.17487/RFC1702, October 1994, 520 . 522 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, 523 DOI 10.17487/RFC2003, October 1996, 524 . 526 [RFC2004] Perkins, C., "Minimal Encapsulation within IP", RFC 2004, 527 DOI 10.17487/RFC2004, October 1996, 528 . 530 [RFC2107] Hamzeh, K., "Ascend Tunnel Management Protocol - ATMP", 531 RFC 2107, DOI 10.17487/RFC2107, February 1997, 532 . 534 [RFC2341] Valencia, A., Littlewood, M., and T. Kolar, "Cisco Layer 535 Two Forwarding (Protocol) "L2F"", RFC 2341, 536 DOI 10.17487/RFC2341, May 1998, 537 . 539 [RFC2529] Carpenter, B. and C. Jung, "Transmission of IPv6 over IPv4 540 Domains without Explicit Tunnels", RFC 2529, 541 DOI 10.17487/RFC2529, March 1999, 542 . 544 [RFC2637] Hamzeh, K., Pall, G., Verthein, W., Taarud, J., Little, 545 W., and G. Zorn, "Point-to-Point Tunneling Protocol 546 (PPTP)", RFC 2637, DOI 10.17487/RFC2637, July 1999, 547 . 549 [RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, 550 G., and B. Palter, "Layer Two Tunneling Protocol "L2TP"", 551 RFC 2661, DOI 10.17487/RFC2661, August 1999, 552 . 554 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 555 via IPv4 Clouds", RFC 3056, DOI 10.17487/RFC3056, February 556 2001, . 558 [RFC3618] Fenner, B., Ed. and D. Meyer, Ed., "Multicast Source 559 Discovery Protocol (MSDP)", RFC 3618, 560 DOI 10.17487/RFC3618, October 2003, 561 . 563 [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, 564 DOI 10.17487/RFC4087, June 2005, 565 . 567 [RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms 568 for IPv6 Hosts and Routers", RFC 4213, 569 DOI 10.17487/RFC4213, October 2005, 570 . 572 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 573 Network Address Translations (NATs)", RFC 4380, 574 DOI 10.17487/RFC4380, February 2006, 575 . 577 [RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 578 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, 579 DOI 10.17487/RFC5214, March 2008, 580 . 582 [RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh 583 Framework", RFC 5565, DOI 10.17487/RFC5565, June 2009, 584 . 586 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 587 Stack Lite Broadband Deployments Following IPv4 588 Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011, 589 . 591 [RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to 592 the IPv4 Address Shortage", RFC 6346, 593 DOI 10.17487/RFC6346, August 2011, 594 . 596 [RFC7676] Pignataro, C., Bonica, R., and S. Krishnan, "IPv6 Support 597 for Generic Routing Encapsulation (GRE)", RFC 7676, 598 DOI 10.17487/RFC7676, October 2015, 599 . 601 [RFC7856] Cui, Y., Dong, J., Wu, P., Xu, M., and A. Yla-Jaaski, 602 "Softwire Mesh Management Information Base (MIB)", 603 RFC 7856, DOI 10.17487/RFC7856, May 2016, 604 . 606 [RFC7870] Fu, Y., Jiang, S., Dong, J., and Y. Chen, "Dual-Stack Lite 607 (DS-Lite) Management Information Base (MIB) for Address 608 Family Transition Routers (AFTRs)", RFC 7870, 609 DOI 10.17487/RFC7870, June 2016, 610 . 612 [RFC8085] Eggert, L., Fairhurst, G., and G. Shepherd, "UDP Usage 613 Guidelines", BCP 145, RFC 8085, DOI 10.17487/RFC8085, 614 March 2017, . 616 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 617 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 618 . 620 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 621 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 622 . 624 Appendix A. Example Usage 626 The following example illustrates how the Interface YANG module can 627 be augmented with tunnel-specific parameters. In this example, the 628 module is augmented with a 'remote-endpoint' for the tunnel. A tree 629 structure is provided below: 631 module: example-iftunnel-extension 632 augment /if:interfaces/if:interface: 633 +--rw remote-endpoint? inet:ipv6-address 635 The 'example-iftunnel-extension' module imports the modules defined 636 in [RFC6991] and [RFC8343] in addition to the "iana-tunnel-type" 637 module defined in this document. 639 module example-iftunnel-extension { 640 yang-version 1.1; 642 namespace "urn:ietf:params:xml:ns:yang:example-iftunnel-extension"; 643 prefix example; 645 import ietf-inet-types { 646 prefix inet; 647 reference 648 "Section 4 of RFC 6991"; 649 } 651 import ietf-interfaces { 652 prefix if; 653 reference 654 "RFC 8343: A YANG Data Model for Interface Management"; 655 } 657 import iana-tunnel-type { 658 prefix iana-tunnel-type; 659 reference 660 "RFC XXXX: A Tunnel Extension to the Interface Management 661 YANG Module"; 662 } 664 organization "IETF Softwire Working Group"; 666 contact 668 "WG Web: 669 WG List: 671 Author: Mohamed Boucadair 672 "; 674 description 675 "This is an example YANG module to extend the Interface YANG 676 module with tunnel-specific parameters. 678 Copyright (c) 2019 IETF Trust and the persons identified as 679 authors of the code. All rights reserved. 681 Redistribution and use in source and binary forms, with or 682 without modification, is permitted pursuant to, and subject 683 to the license terms contained in, the Simplified BSD License 684 set forth in Section 4.c of the IETF Trust's Legal Provisions 685 Relating to IETF Documents 686 (http://trustee.ietf.org/license-info). 688 This version of this YANG module is part of RFC XXXX; see 689 the RFC itself for full legal notices."; 691 revision 2019-04-04 { 692 description 693 "Initial revision."; 694 reference 695 "RFC XXXX: Tunnel Interface Types YANG Module"; 696 } 698 augment "/if:interfaces/if:interface" { 699 when "derived-from(if:type, 'iana-tunnel-type:gre')"; 700 description 701 "Augments Interface module with specific tunnel parameters."; 703 leaf remote-endpoint { 704 type inet:ipv6-address; 705 description 706 "IPv6 address of the remote GRE endpoint."; 707 } 708 } 709 } 711 Authors' Addresses 713 Mohamed Boucadair 714 Orange 715 Rennes 35000 716 France 718 Email: mohamed.boucadair@orange.com 720 Ian Farrer 721 Deutsche Telekom AG 722 CTO-ATI,Landgrabenweg 151 723 Bonn, NRW 53227 724 Germany 726 Email: ian.farrer@telekom.de 728 Rajiv Asati 729 Cisco Systems, Inc. 730 7025 Kit Creek Rd. 731 RTP, NC 27709 732 USA 734 Email: Rajiva@cisco.com