idnits 2.17.1 draft-ietf-softwire-dslite-yang-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 : ---------------------------------------------------------------------------- ** There are 9 instances of too long lines in the document, the longest one being 25 characters in excess of 72. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 9, 2017) is 2362 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) == Outdated reference: A later version (-17) exists of draft-ietf-opsawg-nat-yang-05 ** Obsolete normative reference: RFC 6536 (Obsoleted by RFC 8341) ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) == Outdated reference: A later version (-05) exists of draft-boucadair-pcp-yang-04 == Outdated reference: A later version (-06) exists of draft-ietf-netmod-yang-tree-diagrams-01 -- Obsolete informational reference (is this intentional?): RFC 6087 (Obsoleted by RFC 8407) Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Boucadair 3 Internet-Draft C. Jacquenet 4 Intended status: Standards Track Orange 5 Expires: April 12, 2018 S. Sivakumar 6 Cisco Systems 7 October 9, 2017 9 YANG Data Modules for the DS-Lite 10 draft-ietf-softwire-dslite-yang-07 12 Abstract 14 This document defines YANG modules for the DS-Lite Address Family 15 Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements . 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on April 12, 2018. 34 Copyright Notice 36 Copyright (c) 2017 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (https://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 53 2. DS-Lite YANG Modules: An Overview . . . . . . . . . . . . . . 4 54 3. DS-Lite AFTR YANG Module . . . . . . . . . . . . . . . . . . 7 55 4. DS-Lite B4 YANG Module . . . . . . . . . . . . . . . . . . . 13 56 5. Security Considerations . . . . . . . . . . . . . . . . . . . 16 57 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 58 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 59 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 60 8.1. Normative references . . . . . . . . . . . . . . . . . . 17 61 8.2. Informative references . . . . . . . . . . . . . . . . . 18 62 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 20 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 65 1. Introduction 67 This document defines data models for DS-Lite [RFC6333], using the 68 YANG data modeling language [RFC7950]. Both the Address Family 69 Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements 70 are covered by this specification. As a reminder, Figure 1 71 illustrates an overview of the DS-Lite architecture that involves 72 AFTR and B4 elements. 74 +-----------+ 75 | Host | 76 +-----+-----+ 77 |10.0.0.1 78 | 79 | 80 |10.0.0.2 81 +---------|---------+ 82 | | | 83 | Home router | 84 |+--------+--------+| 85 || B4 || 86 |+--------+--------+| 87 +--------|||--------+ 88 |||2001:db8:0:1::1 89 ||| 90 |||<-IPv4-in-IPv6 softwire 91 ||| 92 -------|||------- 93 / ||| \ 94 | ISP core network | 95 \ ||| / 96 -------|||------- 97 ||| 98 |||2001:db8:0:2::1 99 +--------|||--------+ 100 | AFTR | 101 |+--------+--------+| 102 || Concentrator || 103 |+--------+--------+| 104 | |NAT| | 105 | +-+-+ | 106 +---------|---------+ 107 |192.0.2.1 108 | 109 --------|-------- 110 / | \ 111 | Internet | 112 \ | / 113 --------|-------- 114 | 115 |198.51.100.1 116 +-----+-----+ 117 | IPv4 Host | 118 +-----------+ 120 Figure 1: DS-Lite Base Architecture 122 DS-Lite deployment considerations are discussed in [RFC6908]. 124 This document follows the guidelines of [RFC6087], uses the common 125 YANG types defined in [RFC6991], and adopts Network Management 126 Datastore Architecture (NMDA). 128 1.1. Terminology 130 This document makes use of the terms defined in Section 3 of 131 [RFC6333]. 133 The terminology for describing YANG data modules is defined in 134 [RFC7950]. 136 The meaning of the symbols in tree diagrams is defined in 137 [I-D.ietf-netmod-yang-tree-diagrams]. 139 2. DS-Lite YANG Modules: An Overview 141 As shown in Figure 1: 143 o The AFTR element is a combination of an IPv4-in-IPv6 144 encapsualtion/decapsulation function and a NAT function. 146 o The B4 element is an IPv4-in-IPv6 encapsulation function. 148 Therefore, the AFTR YANG module is designed to augment both the 149 Interfaces YANG module [RFC7223] and the NAT YANG module 150 [I-D.ietf-opsawg-nat-yang] with DS-Lite specific features. The B4 151 YANG module augments the interfaces YANG module. 153 Concretely, the AFTR YANG module (Figure 2) augments the Interfaces 154 YANG module with the following: 156 o An IPv6 address used by the AFTR for sending and receiving IPv4- 157 in-IPv6 packets (aftr-ipv6-address). 159 o An IPv4 address that is used by the AFTR for troubleshooting 160 purposes (aftr-ipv4-address): According to [RFC6333], that address 161 can be used to report ICMP problems and will appear in traceroute 162 outputs. 164 o The tunnel MTU to avoid fragmentation (tunnel-mtu): Since using an 165 IPv4-in-IPv6 encapsulation to carry IPv4 traffic over IPv6 reduces 166 the effective MTU of the datagram, operators should be able to 167 increase the MTU size by at least 40 bytes to accommodate both the 168 IPv6 encapsulation header and the IPv4 datagram without 169 fragmenting the IPv6 packet (Section 2.2 of [RFC6908]). 171 o A policy to limit the number of DS-Lite softwires per subscriber 172 (max-softwire-per-subscriber): This policy aims to prevent a 173 misbehaving subscriber from mounting several DS-Lite softwires 174 that would consume additional AFTR resources (e.g., get more 175 external ports if the quota were enforced on a per-softwire basis, 176 consume extra processing due to a large number of active 177 softwires) [RFC7785]. 179 o A DSCP marking policy to be followed when encapsulating/ 180 decapsulating packets (v6-v4-dscp-preservation): Section 2.10 of 181 [RFC6908] discusses the uniform model which assumes that 182 implementations of this model copy the DSCP value to the outer IP 183 header at encapsulation and copy the outer header's DSCP value to 184 the inner IP header at decapsulation. Operators should configure 185 the AFTR so that it copies the DSCP value in the IPv4 header to 186 the Traffic Class field in the IPv6 header, and vice versa. 188 In addition, the AFTR YANG module augments the NAT YANG module (nat- 189 policy, in particular) with the following: 191 o A policy to instruct the AFTR whether a state can be automatically 192 migrated (state-migrate): This policy avoids stale mappings at the 193 AFTR and minimizes the risk of service disruption for subscribers. 194 According to [RFC7785], the AFTR should migrate existing state to 195 be bound to the new IPv6 address in the event a new IPv6 address 196 is assigned to the B4 element. This operation ensures that 197 traffic destined to the previous B4's IPv6 address will be 198 redirected to the newer B4's IPv6 address. 200 o An instruction to rewrite the TCP Maximum Segment Size (MSS) 201 option (mss-clamping) to avoid TCP fragmentation. 203 Given that the NAT44 table of the AFTR element is extended to include 204 the source IPv6 address of incoming packets, the AFTR YANG module 205 augments the NAT mapping-entry with the following: 207 o b4-ipv6-address which is used to record the source IPv6 address of 208 a packet received from a B4 element. This IPv6 address is 209 required to disambiguate between the overlapping IPv4 address 210 space of customers. 212 o The value of the Traffic Class field in the IPv6 header as 213 received from a B4 element (v6-dscp): This information is used to 214 preserve DSCP marking when encapsulating/decapsulationg at the 215 AFTR. 217 o The IPv4 DSCP marking of the IPv4 packet received from a B4 218 element (internal-v4-dscp): This information can be used by the 219 AFTR fro enforcing the poi 221 o The IPv4 DSCP marking as set by the AFTR in its external interface 222 (external-v4-dscp): An AFTR can be instructed to preserve the same 223 marking or to set it to another value when forwarding an IPv4 224 packet upstream. 226 module: ietf-dslite-aftr 227 augment /if:interfaces/if:interface: 228 +--rw aftr-ipv6-address? inet:ipv6-address 229 +--rw aftr-ipv4-address? inet:ipv4-address 230 +--rw tunnel-mtu? uint16 231 +--rw max-softwire-per-subscriber? uint8 232 +--rw v6-v4-dscp-preservation? boolean 233 augment /nat:nat-module/nat:nat-instances/nat:nat-instance/nat:nat-policy: 234 +--rw state-migrate? boolean 235 +--rw mss-clamping 236 +--rw mss-clamping-enable? boolean 237 +--rw mss-value? uint16 238 augment /nat:nat-module/nat:nat-instances/nat:nat-instance/nat:mapping-table/nat:mapping-entry: 239 +--rw b4-ipv6-address? inet:ipv6-address 240 +--rw v6-dscp? uint8 241 +--rw internal-v4-dscp? uint8 242 +--rw external-v4-dscp? uint8 244 Figure 2: YANG Module for DS-Lite AFTR 246 Examples to illustrate the use of this module are provided in 247 Appendix A. 249 The B4 YANG module (Figure 3) augments the Interfaces YANG module 250 with the following: 252 o An IPv6 address used by a B4 element for sending and receiving 253 IPv4-in-IPv6 packets (b4-ipv6-address). 255 o The IPv6 address of the AFTR to use by a B4 element (aftr- 256 ipv6-addr). 258 o An IPv4 address that is used by a B4 element for troubleshooting 259 purposes (b4-ipv4-address). 261 o The tunnel MTU at the B4 side to avoid fragmentation (tunnel-mtu). 263 o An instruction whether DSCP marking is to preserved when 264 encapsulating an IPv4 packet in an IPv6 packet (v6-v4-dscp- 265 preservation). 267 module: ietf-dslite-b4 268 augment /if:interfaces/if:interface: 269 +--rw b4-ipv6-address? inet:ipv6-address 270 +--rw aftr-ipv6-addr? inet:ipv6-address 271 +--rw b4-ipv4-address? inet:ipv4-address 272 +--rw tunnel-mtu? uint16 273 +--rw v6-v4-dscp-preservation? boolean 275 Figure 3: YANG Module for DS-Lite B4 277 PCP-related considerations are out of scope of the document. A YANG 278 module for PCP is documented in [I-D.boucadair-pcp-yang]. 280 3. DS-Lite AFTR YANG Module 282 file "ietf-dslite-aftr@2017-10-09.yang" 284 module ietf-dslite-aftr { 285 yang-version 1.1; 287 namespace "urn:ietf:params:xml:ns:yang:ietf-dslite-aftr"; 288 prefix dslite-aftr; 290 import ietf-inet-types { prefix inet; } 291 import ietf-interfaces { prefix if; } 292 import iana-if-type { prefix ianaift; } 293 import ietf-nat {prefix nat;} 295 organization "Softwire Working Group"; 296 contact 297 "Mohamed Boucadair 298 Christian Jacquenet 299 Senthil Sivakumar "; 301 description 302 "This module is a YANG module for DS-Lite AFTR 303 implementations. 305 Copyright (c) 2017 IETF Trust and the persons identified as 306 authors of the code. All rights reserved. 308 Redistribution and use in source and binary forms, with or 309 without modification, is permitted pursuant to, and subject 310 to the license terms contained in, the Simplified BSD License 311 set forth in Section 4.c of the IETF Trust's Legal Provisions 312 Relating to IETF Documents 313 (http://trustee.ietf.org/license-info). 315 This version of this YANG module is part of RFC XXXX; see 316 the RFC itself for full legal notices."; 318 revision 2017-10-09 { 319 description "Early yangdoctors review."; 320 reference "-ietf-07"; 321 } 323 revision 2017-08-10 { 324 description "The module augments also the Interface module."; 325 reference "-ietf-04"; 326 } 328 revision 2017-07-27 { 329 description "Redesign the module as an augment of the NAT YANG module."; 330 reference "-ietf-04"; 331 } 333 revision 2017-07-03 { 334 description "Fix some minor points."; 335 reference "-ietf-03"; 336 } 338 revision 2017-01-03 { 339 description "Fixed a compilation error: 340 https://github.com/mbj4668/pyang/issues/296."; 341 reference "-ietf-02"; 342 } 344 revision 2016-11-14 { 345 description "Integrates the comments from Ian: 346 add B4 module, add an MSS leaf, add more details about 347 logging protocols, and other edits."; 348 reference "-ietf-01"; 349 } 351 revision 2016-07-27 { 352 description "-00 IETF version."; 353 reference "-ietf-00"; 354 } 356 revision 2016-06-13 { 357 description "Update the module."; 358 reference "-04"; 360 } 362 revision 2015-12-16 { 363 description "Fix an error."; 364 reference "-03"; 365 } 367 revision 2015-09-01 { 368 description "Add port threshold notifications."; 369 reference "-02"; 370 } 372 revision 2015-08-31 { 373 description "Fix a timeout issue."; 374 reference "-01"; 375 } 377 revision 2015-08-17 { 378 description "First spec."; 379 reference "-00"; 380 } 382 // Augment Interface module with DS-Lite Softwire 384 augment "/if:interfaces/if:interface" { 385 when "if:type = 'ianaift:tunnel'"; 387 description 388 "Augments Interface module with AFTR parameters. 389 IANA interface types are maintained at this registery: 390 https://www.iana.org/assignments/ianaiftype-mib/ianaiftype-mib. 392 tunnel (131), -- Encapsulation interface"; 394 leaf aftr-ipv6-address { 395 type inet:ipv6-address; 397 description 398 "IPv6 address of the DS-Lite AFTR."; 400 reference 401 "RFC 6333."; 402 } 404 leaf aftr-ipv4-address { 405 type inet:ipv4-address; 406 default "192.0.0.1"; 407 description 408 "IPv4 address of the DS-Lite AFTR. 409 192.0.0.1 is reserved for the AFTR element. 410 This address can be used to report ICMP 411 problems and will appear in traceroute 412 outputs."; 414 reference 415 "RFC 6333."; 416 } 418 leaf tunnel-mtu { 419 type uint16; 421 description 422 "Configures a tunnel MTU. 423 [RFC6908] specifies that since 424 fragmentation and reassembly is not 425 optimal, the operator should do 426 everything possible to eliminate 427 the need for it. If the operator uses 428 simple IPv4-in-IPv6 softwire, it is 429 recommended that the MTU size of the IPv6 430 network between the B4 and the AFTR 431 accounts for the additional overhead 432 (40 bytes)."; 434 reference 435 "RFC 6908."; 436 } 438 leaf max-softwire-per-subscriber { 439 type uint8; 440 default 1; 442 description 443 "Configures the maximum softwires per subscriber 444 feature. 446 A subscriber is uniquely identified by means 447 of subscriber-mask. 449 This policy aims to prevent a misbehaving 450 subscriber from mounting several DS-Lite 451 softwires that would consume additional AFTR 452 resources (e.g., get more external ports if 453 the quota were enforced on a per-softwire basis, 454 consume extra processing due to a large number 455 of active softwires)."; 457 reference 458 "Section 4 of RFC 7785."; 459 } 461 leaf v6-v4-dscp-preservation { 462 type boolean; 464 description 465 "Copies the DSCP value from the IPv6 header 466 and vice versa. 468 According to Section 2.10 of [RFC6908], 469 operators should use this model 470 by provisioning the network such that 471 the AFTR copies the DSCP value in the IPv4 472 header to the Traffic Class field in 473 the IPv6 header, after the encapsulation 474 for the downstream traffic."; 476 reference 477 "Section 2.10 of RFC 6908."; 478 } 479 } 481 // Augment NAT module with AFTR parameters 483 augment "/nat:nat-module/nat:nat-instances/"+ 484 "nat:nat-instance/nat:nat-policy" { 486 when "../nat:nat-capabilities/nat:nat-flavor = 'nat:nat44'"; 488 description 489 "Augments the NAT44 module with AFTR parameters."; 491 leaf state-migrate { 492 type boolean; 493 default true; 495 description 496 "State migration is enabled by default. 498 In the event a new IPv6 address is assigned to the B4 element, 499 the AFTR should migrate existing state to be bound to the new 500 IPv6 address. This operation ensures that traffic destined to 501 the previous B4's IPv6 address will be redirected to the newer 502 B4's IPv6 address. The destination IPv6 address for tunneling 503 return traffic from the AFTR should be the last seen as the B4's 504 IPv6 source address from the CPE. 506 The AFTR uses the subscriber-mask to determine whether two 507 IPv6 addresses belong to the same CPE (e.g., if the 508 subscriber-mask is set to 56, the AFTR concludes that 509 2001:db8:100:100::1 and 2001:db8:100:100::2 belong to the same 510 CPE assigned with 2001:db8:100:100::/56)."; 512 reference 513 "RFC 7785."; 514 } 516 container mss-clamping { 517 description 518 "MSS rewriting configuration to avoid IPv6 519 fragmentation."; 521 leaf mss-clamping-enable { 522 type boolean; 524 description 525 "Enable/disable MSS rewriting feature."; 526 } 528 leaf mss-value { 529 type uint16; 530 units "octets"; 532 description 533 "Sets the MSS value to be used for 534 MSS rewriting."; 535 } 536 } 537 } 539 // Augment NAT mapping entry: Extended NAT44 mapping Entry 541 augment "/nat:nat-module/nat:nat-instances/nat:nat-instance/"+ 542 "nat:mapping-table/nat:mapping-entry"{ 544 when "../../nat:nat-capabilities/nat:nat-flavor = 'nat:nat44'"; 546 description 547 "Augments the NAT44 mapping table with DS-Lite specifics."; 549 leaf b4-ipv6-address { 550 type inet:ipv6-address; 552 description 553 "Corresponds to the IPv6 address 554 used by the B4 element."; 556 reference 557 "RFC 6333."; 558 } 560 leaf v6-dscp { 561 type uint8; 563 description 564 "DSCP value used at the softwire level 565 (i.e., IPv6 header)."; 566 } 568 leaf internal-v4-dscp { 569 type uint8; 571 description 572 "DSCP value of the encapsulated IPv4 packet."; 573 } 575 leaf external-v4-dscp { 576 type uint8; 578 description 579 "DSCP value of the translated IPv4 packet 580 as marked by the AFTR."; 581 } 582 } 583 } 584 586 4. DS-Lite B4 YANG Module 588 file "ietf-dslite-b4@2017-10-09.yang" 590 module ietf-dslite-b4 { 591 yang-version 1.1; 592 namespace "urn:ietf:params:xml:ns:yang:ietf-dslite-b4"; 593 prefix dslite-b4; 595 import ietf-inet-types { prefix inet; } 596 import ietf-interfaces { prefix if; } 597 import iana-if-type { prefix ianaift; } 598 organization "Softwire Working Group"; 599 contact 600 "Mohamed Boucadair 601 Christian Jacquenet 602 Senthil Sivakumar "; 604 description 605 "This module is a YANG module for DS-Lite B4 implementations. 607 Copyright (c) 2017 IETF Trust and the persons identified as 608 authors of the code. All rights reserved. 610 Redistribution and use in source and binary forms, with or 611 without modification, is permitted pursuant to, and subject 612 to the license terms contained in, the Simplified BSD License 613 set forth in Section 4.c of the IETF Trust's Legal Provisions 614 Relating to IETF Documents 615 (http://trustee.ietf.org/license-info). 617 This version of this YANG module is part of RFC XXXX; see 618 the RFC itself for full legal notices."; 620 revision 2017-10-09 { 621 description "Early yangdoctors review."; 622 reference "-ietf-07"; 623 } 625 revision 2017-08-10 { 626 description "Augment the interfaces YANG module."; 627 reference "-ietf-05"; 628 } 630 revision 2017-07-27 { 631 description "Separate B4 from AFTR."; 632 reference "-ietf-04"; 633 } 635 // Augment Interface module with DS-Lite Softwire 637 augment "/if:interfaces/if:interface" { 638 when "if:type = 'ianaift:tunnel'"; 640 description 641 "Augments Interface module with B4 parameters. 642 IANA interface types are maintained at this registry: 643 https://www.iana.org/assignments/ianaiftype-mib/ianaiftype-mib. 645 tunnel (131), -- Encapsulation interface"; 647 leaf b4-ipv6-address { 648 type inet:ipv6-address; 650 description 651 "The IPv6 address used by the B4 element."; 653 reference 654 "RFC 6333."; 655 } 657 leaf aftr-ipv6-addr { 658 type inet:ipv6-address; 660 description 661 "The AFTR's IPv6 address."; 663 reference 664 "RFC 6333."; 665 } 667 leaf b4-ipv4-address { 668 type inet:ipv4-address; 669 default "192.0.0.2"; 671 description 672 "IPv4 address of the DS-Lite B4. 673 192.0.0.0/29 is reserved for the B4 element. 674 This address can be used to report ICMP 675 problems and will appear in traceroute 676 outputs."; 678 reference 679 "RFC 6333."; 680 } 682 leaf tunnel-mtu { 683 type uint16; 685 description 686 "Configures a tunnel MTU. 687 [RFC6908] specifies that since 688 fragmentation and reassembly is not 689 optimal, the operator should do 690 everything possible to eliminate 691 the need for it. If the operator uses 692 simple IPv4-in-IPv6 softwire, it is 693 recommended that the MTU size of the IPv6 694 network between the B4 and the AFTR 695 accounts for the additional overhead 696 (40 bytes)."; 698 reference 699 "RFC 6908."; 700 } 702 leaf v6-v4-dscp-preservation { 703 type boolean; 705 description 706 "Copies the DSCP value from the IPv6 header 707 and vice versa. 708 Operators should use this model 709 by provisioning the network such that 710 the AFTR copies the DSCP value in the IPv4 711 header to the Traffic Class field in 712 the IPv6 header, after the encapsulation 713 for the downstream traffic."; 715 reference 716 "Section 2.10 of RFC 6908."; 717 } 718 } 719 } 720 722 5. Security Considerations 724 The YANG module defined in this memo is designed to be accessed via 725 the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the 726 secure transport layer and the support of SSH is mandatory to 727 implement secure transport [RFC6242]. The NETCONF access control 728 model [RFC6536] provides means to restrict access for particular 729 NETCONF users to a pre-configured subset of all available NETCONF 730 protocol operations and contents. 732 All data nodes defined in the YANG module which can be created, 733 modified and deleted (i.e., config true, which is the default). 734 These data nodes are considered sensitive. Write operations (e.g., 735 edit-config) applied to these data nodes without proper protection 736 can negatively affect network operations. 738 6. IANA Considerations 740 This document requests IANA to register the following URIs in the 741 "IETF XML Registry" [RFC3688]: 743 URI: urn:ietf:params:xml:ns:yang:ietf-dslite-aftr 744 Registrant Contact: The IESG. 745 XML: N/A; the requested URI is an XML namespace. 747 URI: urn:ietf:params:xml:ns:yang:ietf-dslite-b4 748 Registrant Contact: The IESG. 749 XML: N/A; the requested URI is an XML namespace. 751 This document requests IANA to register the following YANG modules in 752 the "YANG Module Names" registry [RFC7950]. 754 name: ietf-dslite-aftr 755 namespace: urn:ietf:params:xml:ns:yang:ietf-dslite-aftr 756 prefix: dslite-aftr 757 reference: RFC XXXX 759 name: ietf-dslite-b4 760 namespace: urn:ietf:params:xml:ns:yang:ietf-dslite-b4 761 prefix: dslite-b4 762 reference: RFC XXXX 764 7. Acknowledgements 766 Thanks to Q. Wu for identifying a compiling error. Mahesh 767 Jethanandani provided an eraly ynagdoctors review; many thanks to 768 him. 770 Many thanks to Ian Farrer for the review and comments 772 8. References 774 8.1. Normative references 776 [I-D.ietf-opsawg-nat-yang] 777 Boucadair, M., Sivakumar, S., Jacquenet, C., Vinapamula, 778 S., and Q. Wu, "A YANG Data Model for Network Address 779 Translation (NAT) and Network Prefix Translation (NPT)", 780 draft-ietf-opsawg-nat-yang-05 (work in progress), October 781 2017. 783 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 784 DOI 10.17487/RFC3688, January 2004, 785 . 787 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 788 and A. Bierman, Ed., "Network Configuration Protocol 789 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 790 . 792 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 793 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 794 . 796 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 797 Stack Lite Broadband Deployments Following IPv4 798 Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011, 799 . 801 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 802 Protocol (NETCONF) Access Control Model", RFC 6536, 803 DOI 10.17487/RFC6536, March 2012, 804 . 806 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 807 RFC 6991, DOI 10.17487/RFC6991, July 2013, 808 . 810 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 811 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 812 . 814 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 815 RFC 7950, DOI 10.17487/RFC7950, August 2016, 816 . 818 8.2. Informative references 820 [I-D.boucadair-pcp-yang] 821 Boucadair, M., Jacquenet, C., Sivakumar, S., and S. 822 Vinapamula, "YANG Data Models for the Port Control 823 Protocol (PCP)", draft-boucadair-pcp-yang-04 (work in 824 progress), May 2017. 826 [I-D.ietf-netmod-yang-tree-diagrams] 827 Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- 828 ietf-netmod-yang-tree-diagrams-01 (work in progress), June 829 2017. 831 [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG 832 Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, 833 January 2011, . 835 [RFC6908] Lee, Y., Maglione, R., Williams, C., Jacquenet, C., and M. 836 Boucadair, "Deployment Considerations for Dual-Stack 837 Lite", RFC 6908, DOI 10.17487/RFC6908, March 2013, 838 . 840 [RFC7785] Vinapamula, S. and M. Boucadair, "Recommendations for 841 Prefix Binding in the Context of Softwire Dual-Stack 842 Lite", RFC 7785, DOI 10.17487/RFC7785, February 2016, 843 . 845 Appendix A. Examples 847 The following example shows an AFTR that is reachable at 2001:db8::2. 848 Also, this XML snippet indicates that the AFTR is provided with an 849 IPv4 address (192.0.0.1) to be used for troubleshooting purposes such 850 as reporting problems to B4s. Moreover, the AFTR is instructed to 851 limit the number of softwires per subscriber to '1'. 853 854 myAFTR 855 ianaift:tunnel 856 true 857 2001:db8::2 858 192.0.0.1 859 1 860 862 The following shows an XML excerpt depicting a dynamic UDP mapping 863 entry maintained by a DS-Lite AFTR. In reference to this example, 864 the UDP packet received with a source IPv6 address (2001:db8::1), a 865 source IPv4 address (192.0.2.1) and source port number (1568) is 866 translated into a UDP packet having a source IPv4 address 867 (198.51.100.1) and source port (15000). The lifetime of this mapping 868 is 300 seconds. 870 871 15 872 873 dynamic-explicit 874 875 876 17 877 878 879 2001:db8::1 880 881 882 192.0.2.1 883 884 885 886 1568 887 888 889 890 198.51.100.1 891 892 893 894 15000 895 896 897 898 300 899 900 902 Authors' Addresses 904 Mohamed Boucadair 905 Orange 906 Rennes 35000 907 France 909 EMail: mohamed.boucadair@orange.com 911 Christian Jacquenet 912 Orange 913 Rennes 35000 914 France 916 EMail: christian.jacquenet@orange.com 917 Senthil Sivakumar 918 Cisco Systems 919 7100-8 Kit Creek Road 920 Research Triangle Park, North Carolina 27709 921 USA 923 Phone: +1 919 392 5158 924 EMail: ssenthil@cisco.com