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