idnits 2.17.1 draft-ao-sfc-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 are 4 instances of too long lines in the document, the longest one being 43 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 73 has weird spacing: '...main-id uin...' -- The document date (March 10, 2019) is 1873 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC6241' is mentioned on line 63, but not defined == Missing Reference: 'I-D.ietf-sfc-use-case-mobility' is mentioned on line 392, but not defined == Missing Reference: 'I-D.ietf-sfc-dc-use-cases' is mentioned on line 386, but not defined == Missing Reference: 'I-D.ietf-bess-nsh-bgp-control-plane' is mentioned on line 381, but not defined == Unused Reference: 'RFC7665' is defined on line 369, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 7665 Summary: 2 errors (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SFC WG T. Ao 3 Internet-Draft R. Chen 4 Intended status: Standards Track W. Wei 5 Expires: September 11, 2019 ZTE Corporation 6 March 10, 2019 8 YANG data model for SFC 9 draft-ao-sfc-yang-00 11 Abstract 13 This document is to define the YANG data model for SFC configuration. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on September 11, 2019. 32 Copyright Notice 34 Copyright (c) 2019 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (https://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Design tree for SFC YANG data model . . . . . . . . . . . . . 2 51 3. YANG data model for SFC configuration . . . . . . . . . . . . 3 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 54 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 55 6.1. Normative References . . . . . . . . . . . . . . . . . . 8 56 6.2. Information References . . . . . . . . . . . . . . . . . 8 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 59 1. Introduction 61 YANG[RFC6020]is a data definition language that was introduced to 62 define the contents of a conceptual data store that allows networked 63 devices to be managed using NETCONF [RFC6241]. This document defines 64 a YANG data model for the configuration of SFC which data plane has 65 been defined in [RFC8300]. 67 2. Design tree for SFC YANG data model 69 module: ietf-sfc 70 +--rw sfc-config 71 | +--rw sfc-enable? boolean 72 | +--rw sfc-domain* [sfc-domain-id] 73 | +--rw sfc-domain-id uint32 74 | +--rw ipv4-prefix? inet:ipv4-prefix 75 | +--rw ipv6-prefix? inet:ipv6-prefix 76 | +--rw sfc-sfp* [sfpid si] 77 | +--rw sfpid uint32 78 | +--rw si uint16 79 | +--rw metric? uint16 80 | +--rw (nexthop-trans-type)? 81 | | +--:(ipv4-nexthop) 82 | | | +--rw nh-node-type? sfp-nexthop-type 83 | | | +--rw remote-ipv4? inet:ipv4-address 84 | | +--:(ipv6-nexthop) 85 | | | +--rw nh-node-type? sfp-nexthop-type 86 | | | +--rw remote-ipv6? inet:ipv6-address 87 | | +--:(mac-nexthops) 88 | | | +--rw nh-node-type? sfp-nexthop-type 89 | | | +--rw remote-mac? yang:mac-address 90 | | +--:(vxlan-gpe-nexthop) 91 | | +--rw nh-node-type? sfp-nexthop-type 92 | | +--rw remote-ip? inet:ipv4-address 93 | | +--rw source-ip? inet:ipv4-address 94 | | +--rw destination-ip? inet:ipv4-address 95 | | +--rw vni uint32 96 | +--rw last-sff boolean 97 +--ro sfc-state 98 +--ro sfc-enable? boolean 99 +--ro sfc-domain * [sfc-domain-id] 100 +--ro sfc-domain-id uint32 101 +--ro ipv4-prefix? inet:ipv4-prefix 102 +--ro ipv6-prefix? inet:ipv6-prefix 103 +--ro sfc-sfp-state 104 +--ro sfc-sfp*[sfpid si] 105 +--ro sfpid? uint32 106 +--ro si? uint16 107 +--ro metric? uint16 108 +--ro nexthop-trans-type? enumeration 109 | +--:(ipv4-nexthop) 110 | | +--ro nx-node-type? node-type 111 | | +--ro remote-ipv4? inet:ipv4-address 112 | +--:(ipv6-nexthop) 113 | | +--ro nx-node-type? node-type 114 | | +--ro remote-ipv6? inet:ipv6-address 115 | +--:(mac-nexthop) 116 | | +--ro nx-node-type? node-type 117 | | +--ro remote-mac? yang:mac-address 118 | +--:(vxlan-gpe-nexthop) 119 | | +--ro nx-node-type? node-type 120 | | +--ro remote-ip? inet:ipv4-address 121 | | +--ro source-ip? inet:ipv4-address 122 | | +--ro destination-ip? inet:ipv4-address 123 | | +--ro vni? uint32 124 +--ro last-sff? boolean 126 3. YANG data model for SFC configuration 128 This container defines a YANG model to configurate of SFC. The SF 129 Type listed in this YANG model is referenced by 130 [I-D.ietf-sfc-use-case-mobility] and [I-D.ietf-sfc-dc-use-cases]. 132 file "ietf-sfc@2019-03-10.yang" 133 module ietf-sfc { 134 namespace "urn:ietf:params:xml:ns:yang:ietf-sfc"; 135 prefix "sfc"; 136 import ietf-inet-types { 137 prefix "inet"; 138 } 140 import ietf-yang-types { 141 prefix "yang"; 142 } 143 organization "IETF SFC Working Group"; 145 contact 146 "WG Web: 147 WG List: 148 WG Chair:Jim Guichard 149 150 WG Chair:Joel M. Halpern 151 153 Editor: Ting Ao 154 155 Editor: Ran Chen 156 157 Editor: Wei Wei 158 159 "; 160 description 161 "The YANG module defines a generic configuration 162 model for SFC."; 164 revision 2019-03-07{ 165 description 166 "Initial revision."; 167 reference "RFC XXXX: YANG Data Model for SFC Protocol."; 168 } 169 /*Typedefs*/ 170 typedef sfp-nexthop-type { 172 type enumeration { 173 enum sff { 174 value 1 ; 175 } 176 enum sf-firewall { 177 value 2 ; 178 } 179 enum sf-dpi { 180 value 3 ; 181 } 182 enum sf-ids { 183 value 4 ; 184 } 185 enum sf-edgefw { 186 value 5 ; 187 } 188 enum sf-segfw { 189 value 6 ; 190 } 192 enum sf-appfw { 193 value 7 ; 194 } 195 enum sf-adc { 196 value 8 ; 197 } 198 enum sf-woc { 199 value 9 ; 200 } 201 enum sf-mon { 202 value 10 ; 203 } 204 enum sf-sgw { 205 value 11 ; 206 } 207 enum sf-pgw { 208 value 12 ; 209 } 210 enum sf-hss { 211 value 13 ; 212 } 213 enum sf-mme { 214 value 14 ; 215 } 216 enum sf-pcrf { 217 value 15 ; 218 } 219 enum sf-pcef { 220 value 16 ; 221 } 222 enum sf-tdf { 223 value 17 ; 224 } 225 enum sf-tssf { 226 value 18 ; 227 } 228 enum sf-tds { 229 value 19 ; 230 } 231 enum sf-pep { 232 value 20 ; 233 } 234 enum sf-ims { 235 value 21 ; 236 } 237 enum sf-li { 238 value 22 ; 239 } 241 enum sf-proxy { 242 value 23; 243 } 244 } 245 description "The nexthop node type."; 246 } 248 container sfc-config { 249 leaf sfc-enable { 250 type boolean; 251 default false ; 252 description "Enable SFC." ; 253 } 254 list sfc-domain { 255 key "sfc-domain-id"; 256 leaf sfc-domain-id { 257 type uint32; 258 description "The identifier of the sfc domain." ; 259 } 260 leaf ipv4-prefix { 261 type inet:ipv4-prefix ; 262 description "The IPv4 address of the sff."; 263 } 264 leaf ipv6-prefix { 265 type inet:ipv6-prefix ; 266 description "The IPv6 address of the sff."; 267 } 268 list sfc-sfp { 269 key "sfpid si"; 270 leaf sfpid { 271 type uint32; 272 description "The identifier of the SFP"; 273 } 274 leaf si { 275 type uint16; 276 description "Service index."; 277 } 278 leaf metric { 279 type uint16; 280 description "Forwarding metric."; 281 } 282 choice nexthop-trans-type { 283 case ipv4-nexthop { 284 leaf nh-node-type { 285 type sfp-nexthop-type ; 286 description "Nexthop node type."; 287 } 288 leaf remote-ipv4 { 289 type inet:ipv4-address ; 290 description "Remote IPv4 address."; 291 } 292 description "The configuration for SFP nexthop which encapsulation type is ethernet&ipv4."; 293 } 295 case ipv6-nexthop { 296 leaf nh-node-type { 297 type sfp-nexthop-type ; 298 description "Nexthop node type." ; 299 } 300 leaf remote-ipv6 { 301 type inet:ipv6-address ; 302 description "Remote IPv6 address."; 303 } 304 description "The configuration for SFP nexthop which encapsulation type is ethernet&ipv6."; 305 } 307 case mac-nexthops { 308 leaf nh-node-type { 309 type sfp-nexthop-type ; 310 description "Nexthop node type."; 311 } 312 leaf remote-mac { 313 type yang:mac-address ; 314 description "MAC address."; 315 } 316 description "The configuration for SFP nexthop which specifies the MAC address." ; 317 } 319 case vxlan-gpe-nexthop { 320 leaf nh-node-type { 321 type sfp-nexthop-type ; 322 description "Nexthop node type."; 323 } 324 leaf remote-ip { 325 type inet:ip-address ; 326 description "Remote IP address."; 327 } 328 leaf source-ip { 329 description "The source IP address."; 330 type inet:ipv4-address ; 331 } 332 leaf destination-ip { 333 description "The destination address."; 334 type inet:ipv4-address ; 335 } 336 leaf vni { 337 type uint32; 338 mandatory true; 339 description "VNI value of the tunnel."; 340 } 341 description "The configuration for SFP nexthop is vxlan-gpe." ; 342 } 343 description "The configuration for SFP nexthop." ; 344 } 346 leaf last-sff { 347 type boolean ; 348 default false ; 349 description "This is the SFP terminal."; 350 } 351 } 352 } 353 } 354 } 355 357 4. Security Considerations 359 TBD. 361 5. IANA Considerations 363 TBD. 365 6. References 367 6.1. Normative References 369 [RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function 370 Chaining (SFC) Architecture", RFC 7665, 371 DOI 10.17487/RFC7665, October 2015, 372 . 374 [RFC8300] Quinn, P., Ed., Elzur, U., Ed., and C. Pignataro, Ed., 375 "Network Service Header (NSH)", RFC 8300, 376 DOI 10.17487/RFC8300, January 2018, 377 . 379 6.2. Information References 381 [I-D.ietf-bess-nsh-bgp-control-plane] 382 Farrel, A., Drake, J., Rosen, E., Uttaro, J., and L. 383 Jalil, "BGP Control Plane for NSH SFC", draft-ietf-bess- 384 nsh-bgp-control-plane-09 (work in progress), March 2019. 386 [I-D.ietf-sfc-dc-use-cases] 387 Kumar, S., Tufail, M., Majee, S., Captari, C., and S. 388 Homma, "Service Function Chaining Use Cases In Data 389 Centers", draft-ietf-sfc-dc-use-cases-06 (work in 390 progress), February 2017. 392 [I-D.ietf-sfc-use-case-mobility] 393 Haeffner, W., Napper, J., Stiemerling, M., Lopez, D., and 394 J. Uttaro, "Service Function Chaining Use Cases in Mobile 395 Networks", draft-ietf-sfc-use-case-mobility-09 (work in 396 progress), January 2019. 398 Authors' Addresses 400 Ting Ao 401 ZTE Corporation 402 No.889, BiBo Road 403 Shanghai 201203 404 China 406 Phone: +86 21 68897642 407 Email: ao.ting@zte.com.cn 409 Ran Chen 410 ZTE Corporation 412 Email: ran.chen@zte.com.cn 414 Wei Wei 415 ZTE Corporation 417 Email: wei.wei@zte.com.cn