idnits 2.17.1 draft-ietf-netmod-iana-afn-safi-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 : ---------------------------------------------------------------------------- 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 (July 4, 2013) is 3948 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) == Missing Reference: 'RFC2453' is mentioned on line 673, but not defined == Missing Reference: 'RFC2858' is mentioned on line 673, but not defined ** Obsolete undefined reference: RFC 2858 (Obsoleted by RFC 4760) == Missing Reference: 'RFCXXXX' is mentioned on line 682, but not defined == Missing Reference: 'RFC4760' is mentioned on line 682, but not defined Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Bjorklund 3 Internet-Draft Tail-f Systems 4 Intended status: Standards Track July 4, 2013 5 Expires: January 5, 2014 7 IANA Address Family Numbers and Subsequent Address Family Identifiers 8 YANG Module 9 draft-ietf-netmod-iana-afn-safi-00 11 Abstract 13 This document defines the initial version of the iana-afn-safi YANG 14 module. 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 January 5, 2014. 33 Copyright Notice 35 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. IANA Maintained AFN and SAFI YANG Module . . . . . . . . . . . 4 52 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 53 3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 17 54 3.2. YANG Module Registrations . . . . . . . . . . . . . . . . 17 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . 18 56 5. Normative References . . . . . . . . . . . . . . . . . . . . . 19 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20 59 1. Introduction 61 This document defines the initial version of the iana-afn-safi YANG 62 module, for Address Family Numbers (AFN) and Subsequent Address 63 Family Identifiers (SAFI). 65 The iana-afn-safi module reflects IANA's existing "Address Family 66 Numbers" and "SAFI Values" registries. 68 Whenever a new address family number is added to the "Address Family 69 Numbers" registry, the IANA-ADDRESS-FAMILY-NUMBERS-MIB and the iana- 70 afn-safi YANG module are updated by IANA. 72 Whenever a new subsequent address family identifier is added to the 73 "SAFI Values" registry, the iana-afn-safi YANG module is updated by 74 IANA. 76 2. IANA Maintained AFN and SAFI YANG Module 78 file "iana-afn-safi.yang" 80 module iana-afn-safi { 81 namespace "urn:ietf:params:xml:ns:yang:iana-afn-safi"; 82 prefix "ianaaf"; 84 organization 85 "IANA"; 86 contact 87 " Internet Assigned Numbers Authority 89 Postal: ICANN 90 4676 Admiralty Way, Suite 330 91 Marina del Rey, CA 90292 93 Tel: +1 310 823 9358 94 E-Mail: iana&iana.org"; 95 description 96 "This YANG module provides two typedefs containing YANG 97 definitions for the following IANA-registered enumerations: 99 - Address Family Numbers (AFN) 101 - Subsequent Address Family Identifiers (SAFI) 103 The latest revision of this YANG module can be obtained from the 104 IANA web site. 106 Copyright (c) 2012 IETF Trust and the persons identified as 107 authors of the code. All rights reserved. 109 Redistribution and use in source and binary forms, with or 110 without modification, is permitted pursuant to, and subject to 111 the license terms contained in, the Simplified BSD License set 112 forth in Section 4.c of the IETF Trust's Legal Provisions 113 Relating to IETF Documents 114 (http://trustee.ietf.org/license-info). 116 This version of this YANG module is part of RFC XXXX; see the 117 RFC itself for full legal notices."; 118 // RFC Ed.: replace XXXX with actual RFC number and remove this 119 // note. 121 // RFC Ed.: update the date below with the date of RFC publication 122 // and remove this note. 123 revision 2013-07-04 { 124 description 125 "Initial revision."; 126 reference 127 "RFC XXXX: IANA Address Family Numbers and 128 Subsequent Address Family Identifiers YANG Module"; 129 } 131 typedef address-family { 132 type enumeration { 133 // value 0 is reserved by IANA 134 enum ipV4 { 135 value "1"; 136 description 137 "IP version 4"; 138 } 139 enum ipV6 { 140 value "2"; 141 description 142 "IP version 6"; 143 } 144 enum nsap { 145 value "3"; 146 description 147 "NSAP"; 148 } 149 enum hdlc { 150 value "4"; 151 description 152 "HDLC (8-bit multidrop)"; 153 } 154 enum bbn1822 { 155 value "5"; 156 description 157 "BBN 1822"; 158 } 159 enum all802 { 160 value "6"; 161 description 162 "802 (includes all 802 media plus Ethernet 'canonical 163 format')"; 164 } 165 enum e163 { 166 value "7"; 167 description 168 "E.163"; 169 } 170 enum e164 { 171 value "8"; 172 description 173 "E.164 (SMDS, FrameRelay, ATM)"; 174 } 175 enum f69 { 176 value "9"; 177 description 178 "F.69 (Telex)"; 179 } 180 enum x121 { 181 value "10"; 182 description 183 "X.121 (X.25, Frame Relay)"; 184 } 185 enum ipx { 186 value "11"; 187 description 188 "IPX (Internetwork Packet Exchange)"; 189 } 190 enum appletalk { 191 value "12"; 192 description 193 "Appletalk"; 194 } 195 enum decnetIV { 196 value "13"; 197 description 198 "DECnet IV"; 199 } 200 enum banyanVines { 201 value "14"; 202 description 203 "Banyan Vines"; 204 } 205 enum e164withNsap { 206 value "15"; 207 description 208 "E.164 with NSAP format subaddress"; 209 reference 210 "ATM Forum UNI 3.1"; 211 } 212 enum dns { 213 value "16"; 214 description 215 "DNS (Domain Name System)"; 216 } 217 enum distinguishedName { 218 value "17"; 219 description 220 "Distinguished Name (per X.500)"; 221 } 222 enum asNumber { 223 value "18"; 224 description 225 "Autonomous System Number"; 226 } 227 enum xtpOverIpv4 { 228 value "19"; 229 description 230 "XTP over IP version 4"; 231 } 232 enum xtpOverIpv6 { 233 value "20"; 234 description 235 "XTP over IP version 6"; 236 } 237 enum xtpNativeModeXTP { 238 value "21"; 239 description 240 "XTP native mode XTP"; 241 } 242 enum fibreChannelWWPN { 243 value "22"; 244 description 245 "Fibre Channel World-Wide Port Name"; 246 } 247 enum fibreChannelWWNN { 248 value "23"; 249 description 250 "Fibre Channel World-Wide Node Name"; 251 } 252 enum gwid { 253 value "24"; 254 description 255 "Gateway Identifier"; 256 } 257 // FIXME: This one is actually called "afi" in the MIB, but 258 // that must be a mistake. 259 enum l2vpn { 260 value "25"; 261 description 262 "AFI for L2VPN information"; 263 reference 264 "RFC 4761: Virtual Private LAN Service (VPLS): Using BGP 265 for Auto-Discovery and Signaling 267 RFC 6074: Provisioning, Auto-Discovery, and Signaling in 268 Layer 2 Virtual Private Networks (L2VPNs)"; 269 } 270 enum mplsTpSectionEndpointIdentifier { 271 value "26"; 272 description 273 "MPLS-TP Section Endpoint Identifier"; 274 reference 275 "draft-ietf-mpls-gach-adv"; 276 } 277 enum mplsTpLspEndpointIdentifier { 278 value "27"; 279 description 280 "MPLS-TP LSP Endpoint Identifier"; 281 reference 282 "draft-ietf-mpls-gach-adv"; 283 } 284 enum mplsTpPseudowireEndpointIdentifier { 285 value "28"; 286 description 287 "MPLS-TP Pseudowire Endpoint Identifier"; 288 reference 289 "draft-ietf-mpls-gach-adv"; 290 } 291 enum eigrpCommonServiceFamily { 292 value "16384"; 293 description 294 "EIGRP Common Service Family"; 295 } 296 enum eigrpIpv4ServiceFamily { 297 value "16385"; 298 description 299 "EIGRP IPv4 Service Family"; 300 } 301 enum eigrpIpv6ServiceFamily { 302 value "16386"; 303 description 304 "EIGRP IPv6 Service Family"; 305 } 306 enum lispCanonicalAddressFormat { 307 value "16387"; 308 description 309 "LISP Canonical Address Format (LCAF)"; 310 } 311 enum bgpLs { 312 value "16388"; 313 description 314 "BGP-LS"; 315 reference 316 "draft-ietf-idr-ls-distribution"; 317 } 318 enum 48BitMac { 319 value "16389"; 320 description 321 "48-bit MAC"; 322 reference 323 "draft-eastlake-rfc5342bis"; 324 } 325 enum 64BitMac { 326 value "16390"; 327 description 328 "64-bit MAC"; 329 reference 330 "draft-eastlake-rfc5342bis"; 331 } 332 // value 65535 is reserved by IANA 333 } 334 description 335 "This typedef is a YANG enumeration of IANA-registered address 336 family numbers (AFN)."; 337 reference 338 "IANA Address Family Numbers registry. 339 "; 340 } 342 typedef subsequent-address-family { 343 type enumeration { 344 // value 0 is reserved by IANA 345 enum nlriUnicast { 346 value "1"; 347 description 348 "Network Layer Reachability Information used for unicast 349 forwarding"; 350 reference 351 "RFC 4760: Multiprotocol Extensions for BGP-4"; 352 } 353 enum nlriMulticast { 354 value "2"; 355 description 356 "Network Layer Reachability Information used for multicast 357 forwarding"; 358 reference 359 "RFC 4760: Multiprotocol Extensions for BGP-4"; 360 } 361 // value 3 is reserved by IANA 362 enum nlriMpls { 363 value "4"; 364 description 365 "Network Layer Reachability Information (NLRI) with MPLS 366 Labels"; 367 reference 368 "RFC 3107: Carrying Label Information in BGP-4"; 369 } 370 enum mcastVpn { 371 value "5"; 372 description 373 "MCAST-VPN"; 374 reference 375 "RFC 6514: BGP Encodings and Procedures for Multicast in 376 MPLS/BGP IP VPNs"; 377 } 378 enum nlriDynamicMsPw { 379 value "6"; 380 status "obsolete"; 381 description 382 "Network Layer Reachability Information used for Dynamic 383 Placement of Multi-Segment Pseudowires (TEMPORARY - 384 Expires 2008-08-23)"; 385 reference 386 "draft-ietf-pwe3-dynamic-ms-pw: Dynamic Placement of Multi 387 Segment Pseudowires"; 388 } 389 enum encapsulation { 390 value "7"; 391 description 392 "Encapsulation SAFI"; 393 reference 394 "RFC 5512: The BGP Encapsulation Subsequent Address Family 395 Identifier (SAFI) and the BGP Tunnel Encapsulation 396 Attribute"; 397 } 398 enum tunnel { 399 value "64"; 400 status "obsolete"; 401 description 402 "Tunnel SAFI"; 403 reference 404 "draft-nalawade-kapoor-tunnel-safi: BGP Tunnel SAFI"; 405 } 406 enum vpls { 407 value "65"; 408 description 409 "Virtual Private LAN Service (VPLS)"; 410 reference 411 "RFC 4761: Virtual Private LAN Service (VPLS): Using BGP 412 for Auto-Discovery and Signaling 414 RFC 6074: Provisioning, Auto-Discovery, and Signaling in 415 Layer 2 Virtual Private Networks (L2VPNs)"; 416 } 417 enum bgpMdt { 418 value "66"; 419 description 420 "BGP MDT SAFI"; 421 reference 422 "RFC 6037: Cisco Systems' Solution for Multicast in 423 BGP/MPLS IP VPNs"; 424 } 425 enum bgp4over6 { 426 value "67"; 427 description 428 "BGP 4over6 SAFI"; 429 reference 430 "RFC 5747: 4over6 Transit Solution Using IP Encapsulation 431 and MP-BGP Extensions"; 432 } 433 enum bgp6over4 { 434 value "68"; 435 description 436 "BGP 6over4 SAFI"; 437 } 438 enum l1VpnAutoDiscovery { 439 value "69"; 440 description 441 "Layer-1 VPN auto-discovery information"; 442 reference 443 "RFC 5195: BGP-Based Auto-Discovery for Layer-1 VPNs"; 444 } 445 enum mplsVpn { 446 value "128"; 447 description 448 "MPLS-labeled VPN address"; 449 reference 450 "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)"; 451 } 452 enum multicastBgpMplsVpn { 453 value "129"; 454 description 455 "Multicast for BGP/MPLS IP Virtual Private Networks 456 (VPNs)"; 457 reference 458 "RFC 6513: Multicast in MPLS/BGP IP VPNs 459 RFC 6514: BGP Encodings and Procedures for Multicast in 460 MPLS/BGP IP VPNs"; 461 } 462 // values 130-131 are reserved by IANA 463 enum routeTargetConstraints { 464 value "132"; 465 description 466 "Route Target constraints"; 467 reference 468 "RFC 4684: Constrained Route Distribution for Border 469 Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) 470 Internet Protocol (IP) Virtual Private Networks (VPNs)"; 471 } 472 enum ipv4DissFlow { 473 value "133"; 474 description 475 "IPv4 dissemination of flow specification rules"; 476 reference 477 "RFC 5575: Dissemination of Flow Specification Rules"; 478 } 479 enum vpnv4DissFlow { 480 value "134"; 481 description 482 "VPNv4 dissemination of flow specification rules"; 483 reference 484 "RFC 5575: Dissemination of Flow Specification Rules"; 485 } 486 // values 135-139 are reserved by IANA 487 enum vpnAutoDiscovery { 488 value "140"; 489 status "obsolete"; 490 description 491 "VPN auto-discovery"; 492 reference 493 "draft-ietf-l3vpn-bgpvpn-auto: Using BGP as an 494 Auto-Discovery Mechanism for VR-based Layer-3 VPNs"; 495 } 496 // values 141-240 are reserved by IANA 497 enum private241 { 498 value "241"; 499 description 500 "Reserved for Private Use"; 501 reference 502 "RFC 4760: Multiprotocol Extensions for BGP-4"; 503 } 504 enum private242 { 505 value "242"; 506 description 507 "Reserved for Private Use"; 508 reference 509 "RFC 4760: Multiprotocol Extensions for BGP-4"; 510 } 511 enum private243 { 512 value "243"; 513 description 514 "Reserved for Private Use"; 515 reference 516 "RFC 4760: Multiprotocol Extensions for BGP-4"; 517 } 518 enum private244 { 519 value "244"; 520 description 521 "Reserved for Private Use"; 522 reference 523 "RFC 4760: Multiprotocol Extensions for BGP-4"; 524 } 525 enum private245 { 526 value "245"; 527 description 528 "Reserved for Private Use"; 529 reference 530 "RFC 4760: Multiprotocol Extensions for BGP-4"; 531 } 532 enum private246 { 533 value "246"; 534 description 535 "Reserved for Private Use"; 536 reference 537 "RFC 4760: Multiprotocol Extensions for BGP-4"; 538 } 539 enum private247 { 540 value "247"; 541 description 542 "Reserved for Private Use"; 543 reference 544 "RFC 4760: Multiprotocol Extensions for BGP-4"; 545 } 546 enum private248 { 547 value "248"; 548 description 549 "Reserved for Private Use"; 550 reference 551 "RFC 4760: Multiprotocol Extensions for BGP-4"; 552 } 553 enum private249 { 554 value "249"; 555 description 556 "Reserved for Private Use"; 557 reference 558 "RFC 4760: Multiprotocol Extensions for BGP-4"; 559 } 560 enum private250 { 561 value "250"; 562 description 563 "Reserved for Private Use"; 564 reference 565 "RFC 4760: Multiprotocol Extensions for BGP-4"; 566 } 567 enum private251 { 568 value "251"; 569 description 570 "Reserved for Private Use"; 571 reference 572 "RFC 4760: Multiprotocol Extensions for BGP-4"; 573 } 574 enum private252 { 575 value "252"; 576 description 577 "Reserved for Private Use"; 578 reference 579 "RFC 4760: Multiprotocol Extensions for BGP-4"; 580 } 581 enum private253 { 582 value "253"; 583 description 584 "Reserved for Private Use"; 585 reference 586 "RFC 4760: Multiprotocol Extensions for BGP-4"; 587 } 588 enum private254 { 589 value "254"; 590 description 591 "Reserved for Private Use"; 592 reference 593 "RFC 4760: Multiprotocol Extensions for BGP-4"; 594 } 595 // value 255 is reserved by IANA 596 } 597 description 598 "This typedef is a YANG enumeration of IANA-registered 599 subsequent address family identifiers (SAFI)."; 600 reference 601 "IANA SAFI Values registry. 602 "; 604 } 605 } 607 609 3. IANA Considerations 611 This document defines the initial version of the IANA-maintained 612 iana-afn-safi YANG module. 614 IANA is requested to extend the registries "Address Family Numbers" 615 and "SAFI Values" with a "Name" column. IANA is also requested to 616 add this new Note to these registries: 618 The name of an entry in this registry must be a legal SMIv2 619 enumeration label. 621 The existing entries in the "Address Family Numbers" registry should 622 get their names from the corresponding "enum" statement in the 623 "address-family" typedef. 625 The existing entries in the "SAFI Values" registry should get their 626 names from the corresponding "enum" statement in the 627 "subsequent-address-family" typedef. 629 The iana-afn-safi module is intended to reflect the "Address Family 630 Numbers" and "SAFI Values" registries. When an AFN or SAFI is added 631 to these registries, a new "enum" statement must be added to the 632 "address-family" or "subsequent-address-family" typedefs. The name 633 of the "enum" is the value of the "Name" column in the registry. 635 The following substatements to the "enum" statement should be 636 defined: 638 "value": Replicate the value from the registry. 640 "status": Include only if a registration has been deprecated (use 641 the value "deprecated") or obsoleted (use the value 642 "obsolete"). 644 "description": Replicate the description from the registry, if any. 646 "reference": Replicate the reference from the registry, if any, and 647 add the title of the document. 649 If a parameter is marked as "reserved" in these registries, no "enum" 650 statement is added to the corresponding typedef. Instead a comment 651 is added, on the form: 653 // value NN is reserved by XX 655 Unassigned values are not present in the module. 657 When the iana-afn-safi YANG module is updated, a new "revision" 658 statement must be added. 660 IANA is requested to add this new Note to the "Address Family 661 Numbers" and "SAFI Values" registries: 663 When this registry is modified, the YANG module iana-afn-safi 664 must be updated as defined in RFC XXXX. 666 The Reference text in the "Address Family Numbers" registry needs to 667 be updated as: 669 OLD: 670 [RFC2453][RFC2858] 672 NEW: 673 [RFC2453][RFC2858][RFCXXXX] 675 The Reference text in the "SAFI Values" registry needs to be updated 676 as: 678 OLD: 679 [RFC4760] 681 NEW: 682 [RFC4760][RFCXXXX] 684 3.1. URI Registrations 686 This document registers a URI in the IETF XML registry [RFC3688]. 687 Following the format in RFC 3688, the following registration is 688 requested to be made. 690 URI: urn:ietf:params:xml:ns:yang:iana-afn-safi 692 Registrant Contact: IANA. 694 XML: N/A, the requested URI is an XML namespace. 696 3.2. YANG Module Registrations 698 This document registers a YANG module in the YANG Module Names 699 registry [RFC6020]. 701 name: iana-afn-safi 702 namespace: urn:ietf:params:xml:ns:yang:iana-afn-safi 703 prefix: ianaaf 704 reference: RFC XXXX 706 4. Security Considerations 708 Since this document does not introduce any technology or protocol, 709 there are no security issues to be considered for this document 710 itself. 712 5. Normative References 714 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 715 January 2004. 717 [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the 718 Network Configuration Protocol (NETCONF)", RFC 6020, 719 October 2010. 721 Author's Address 723 Martin Bjorklund 724 Tail-f Systems 726 Email: mbj@tail-f.com