idnits 2.17.00 (12 Aug 2021) /tmp/idnits7322/draft-zheng-intarea-tunneling-for-ipv6-yang-00.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 : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (May 22, 2015) is 2556 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) == Unused Reference: 'RFC6241' is defined on line 266, but no explicit reference was found in the text == Unused Reference: 'RFC6242' is defined on line 270, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2629 (Obsoleted by RFC 7749) ** Downref: Normative reference to an Informational RFC: RFC 5214 Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Zheng 3 Internet-Draft Huawei Technologies 4 Intended status: Standards Track May 22, 2015 5 Expires: November 23, 2015 7 A YANG Model for Managing IPv6 Tunneling 8 draft-zheng-intarea-tunneling-for-ipv6-yang-00 10 Abstract 12 This document describes a data model of tunneling for managing IPv6- 13 over-IPv4 tunneling, which is used to support the transition from 14 IPv4-only networks to integrated IPv4-based and IPv6-based networks. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on November 23, 2015. 33 Copyright Notice 35 Copyright (c) 2015 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Requirements Language and Terminology . . . . . . . . . . . . 2 52 3. Design of the IPv6-over-IPv4 Tunneling Model . . . . . . . . 3 53 4. IPv6-over-IPv4 Tunneling YANG Model . . . . . . . . . . . . . 3 54 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 55 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 56 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 57 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 58 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 59 8.2. Informative References . . . . . . . . . . . . . . . . . 6 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 62 1. Introduction 64 An IPv6-over-IPv4 tunnel encapsulates IPv6 packets in IPv4 packets 65 for delivery across an IPv4 infrastructure (a core network or the 66 Internet). By using these tunnels, nodes in different isolated IPv6 67 networks could communicate with each other without upgrading the IPv4 68 infrastructure between them.These tunnels can be configured between 69 border routers or between a border router and a host; however, both 70 tunnel endpoints must support both IPv4 and IPv6 protocol stacks. 72 The following types of overlay tunneling mechanisms are normally 73 supported by vendors: 75 o Manual 77 o 6to4 79 o Generic Routing Encapsulation (GRE) 81 o IPv4-compatible 83 o Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) 85 The definition of this YANG model reference several correspond RFCs 86 which include [RFC4213], [RFC3056], and [RFC5214]. 88 2. Requirements Language and Terminology 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 92 "OPTIONAL" in this document are to be interpreted as described in 93 [RFC2119] when they appear in ALL CAPS. When these words are not in 94 ALL CAPS (such as "should" or "Should"), they have their usual 95 English meanings, and are not to be interpreted as [RFC2119] key 96 words. 98 Terminology: 100 o IP: Internet Protocol 102 o IPv4: Internet Protocol version 4 104 o IPv6: Internet Protocol version 6 106 3. Design of the IPv6-over-IPv4 Tunneling Model 108 This document defines a YANG [RFC6020] configuration data model that 109 may be used to configure the IPv6-over-IPv4 Tunneling on a system. 111 The model includes the general attributes of current vendors which 112 support IPv6-over-IPv4 Tunneling feature. 114 This draft addresses the common leafs between almost all vendors, if 115 necessary it can be augmented with proprietary features. 117 This model consists of tunnel interface name, source interface, 118 source IP address, destination IP address and the tunnel mode. The 119 IPv6-over-IPv4 Tunneling feature depend on the IPv6 feature. 121 module: tunnel64 122 +--rw tunneling-for-IPv6 123 +--rw Tunnel* [tunnel-name] 124 +--rw tunnel-name string 125 +--ro tunnel-interface-name? if:interface-ref 126 +--rw tunnel-type? enumeration 127 +--rw source-ip-address? inet:ipv4-address 128 +--rw source-interface? if:interface-ref 129 +--rw destination-ip-address? inet:ipv4-address 131 4. IPv6-over-IPv4 Tunneling YANG Model 133 file "tunnel64.yang" 135 module tunnel64 { 136 namespace "urn:ietf:params:xml:ns:yang:ietf-tunnel64"; 137 prefix tunnel64; 139 import ietf-inet-types { 140 prefix inet; 141 } 143 import ietf-interfaces{ 144 prefix if; 145 } 146 organization "Internet Area Working Group (intarea)"; 147 contact 148 "WG List: 150 Author: Guangying Zheng 151 "; 153 description 154 "This module contains a collection of YANG definitions 155 of tunneling for IPv6 configuration."; 157 revision 2015-05-21 { 158 description 159 "Initial Revision"; 160 reference 161 "This model references RFC2893,RFC3056,RFC4214."; 162 } 164 feature tunneling-for-IPv6 { 165 description 166 "This feature represents the feeture of tunneling for IPv6."; 167 } 169 container tunneling-for-IPv6 { 171 list Tunnel{ 173 key tunnel-name; 174 min-elements 0; 175 max-elements unbounded; 177 leaf tunnel-name { 178 config true; 179 type string; 180 } 181 leaf tunnel-interface-name { 182 config false; 183 type if:interface-ref; 185 } 186 leaf tunnel-type { 187 config true; 188 type enumeration { 189 enum manual { 190 value 0; 191 description "a manual IPv6 tunnel"; 192 } 193 enum 6to4 { 194 value 1; 195 description "a 6to4 tunnel"; 196 } 197 enum auto-tunnel { 198 value 2; 199 description "an IPv4-compatible IPv6 tunnel"; 200 } 201 } 202 } 203 leaf source-ip-address { 204 config true; 205 type inet:ipv4-address; 207 } 208 leaf source-interface { 209 config true; 210 type if:interface-ref; 212 } 213 leaf destination-ip-address { 214 config true; 215 type inet:ipv4-address; 217 } 218 } 220 } 221 } 223 225 5. Security Considerations 227 TBD. 229 6. IANA Considerations 231 This draft does not request any IANA action. 233 7. Acknowledgements 235 Many valuable comments were received from Bing Liu, Gang Yan and Yongkang Zhang 236 to improve the draft. 238 This document was produced using the xml2rfc tool [RFC2629]. 240 8. References 242 8.1. Normative References 244 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 245 Requirement Levels", BCP 14, RFC 2119, March 1997. 247 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 248 June 1999. 250 [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains 251 via IPv4 Clouds", RFC 3056, February 2001. 253 [RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms 254 for IPv6 Hosts and Routers", RFC 4213, October 2005. 256 [RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 257 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, 258 March 2008. 260 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 261 Network Configuration Protocol (NETCONF)", RFC 6020, 262 October 2010. 264 8.2. Informative References 266 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. 267 Bierman, "Network Configuration Protocol (NETCONF)", RFC 268 6241, June 2011. 270 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 271 Shell (SSH)", RFC 6242, June 2011. 273 Author's Address 275 Guangying Zheng 276 Huawei Technologies 277 N9-3-B01 Building, Huawei Technologies Co., Ltd 278 No.101 Yuhuatai Rd., Nanjing 279 P.R. China 281 Email: zhengguangying@huawei.com