idnits 2.17.1 draft-ietf-rtgwg-routing-types-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 doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- The document date (December 16, 2016) is 2688 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) -- Looks like a reference, but probably isn't: '1' on line 721 == Missing Reference: 'RFC3688' is mentioned on line 622, but not defined == Outdated reference: A later version (-17) exists of draft-ietf-bfd-yang-03 == Outdated reference: A later version (-17) exists of draft-ietf-idr-bgp-model-02 == Outdated reference: A later version (-29) exists of draft-ietf-ospf-yang-06 == Outdated reference: A later version (-17) exists of draft-ietf-pim-yang-03 == Outdated reference: A later version (-19) exists of draft-ietf-teas-yang-rsvp-06 Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Liu 3 Internet-Draft Kuatro Technologies 4 Intended status: Standards Track Y. Qu 5 Expires: June 19, 2017 A. Lindem 6 Cisco Systems 7 C. Hopps 8 Deutsche Telekom 9 L. Berger 10 LabN Consulting, L.L.C. 11 December 16, 2016 13 Routing Area Common YANG Data Types 14 draft-ietf-rtgwg-routing-types-00 16 Abstract 18 This document defines a collection of common data types using YANG 19 data modeling language. These derived common types are designed to 20 be imported by other modules defined in the routing area. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on June 19, 2017. 39 Copyright Notice 41 Copyright (c) 2016 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 58 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 62 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 63 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 64 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 65 7.1. Normative References . . . . . . . . . . . . . . . . . . 14 66 7.2. Informative References . . . . . . . . . . . . . . . . . 15 67 7.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 16 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 70 1. Introduction 72 YANG [RFC6020] [RFC7950] is a data modeling language used to model 73 configuration data, state data, Remote Procedure Calls, and 74 notifications for network management protocols. The YANG language 75 supports a small set of built-in data types and provides mechanisms 76 to derive other types from the built-in types. 78 This document introduces a collection of common data types derived 79 from the built-in YANG data types. The derived types are designed to 80 be the common types applicable for modeling in the routing area. 82 1.1. Requirements Language 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this 86 document are to be interpreted as described in BCP 14, RFC 2119 87 [RFC2119]. 89 1.2. Terminology 91 The terminology for describing YANG data models is found in 92 [RFC7950]. 94 2. Overview 96 This document defines the following data types: 98 router-id 99 Router Identifiers are commonly used to identify a nodes in 100 routing and other control plane protocols. An example usage of 101 router-id can be found in [I-D.ietf-ospf-yang]. 103 address-family 104 This type defines values for use in address family identifiers. 105 The values are based on the IANA Address Family Numbers Registry 106 [1]. An example usage can be found in [I-D.ietf-idr-bgp-model]. 108 route-target 109 Route Targets (RTs) are commonly used to control the distribution 110 of virtual routing and forwarding (VRF) information, see 111 [RFC4364], in support of virtual private networks (VPNs). An 112 example usage can be found in [I-D.ietf-idr-bgp-model] and 114 route-distinguisher 115 Route Distinguishers (RDs) are commonly used to identify separate 116 routes in support of virtual private networks (VPNs). For 117 example, in [RFC4364], RDs are commonly used to identify 118 independent VPNs and VRFs, and more generally, to identify 119 multiple routes to the same prefix. An example usage can be found 120 in [I-D.ietf-idr-bgp-model]. 122 ieee-bandwidth 123 Bandwidth in IEEE 754 floating point 32-bit binary format 124 [IEEE754]. Commonly used in Traffic Engineering control plane 125 protocols. An example of where this type may/will be used is 126 [I-D.ietf-ospf-yang]. 128 link-access-type 129 This type identifies the IGP link type. An example of where this 130 type may/will be used is [I-D.ietf-ospf-yang]. 132 multicast-source-ipv4-addr-type 133 IPv4 source address type for use in multicast control protocols. 134 This type also allows the indication of wildcard sources, i.e., 135 "*". An example of where this type may/will be used is 136 [I-D.ietf-pim-yang]. 138 multicast-source-ipv6-addr-type 139 IPv6 source address type for use in multicast control protocols. 140 This type also allows the indication of wildcard sources, i.e., 141 "*". An example of where this type may/will be used is 142 [I-D.ietf-pim-yang]. 144 timer-multiplier 145 This type is used in conjunction with a timer-value type. It is 146 generally used to indicate define the number of timer-value 147 intervals that may expire before a specific event must occur. 148 Examples of this include the arrival of any BFD packets, see 149 [RFC5880] Section 6.8.4, or hello_interval in [RFC3209]. Example 150 of where this type may/will be used is [I-D.ietf-idr-bgp-model] 151 and [I-D.ietf-teas-yang-rsvp]. 153 timer-value-seconds16 154 This type covers timers which can be set in seconds, not set, or 155 set to infinity. This type supports a range of values that can be 156 represented in a uint16 (2 octets). An example of where this type 157 may/will be used is [I-D.ietf-ospf-yang]. 159 timer-value-seconds32 160 This type covers timers which can be set in seconds, not set, or 161 set to infinity. This type supports a range of values that can be 162 represented in a uint32 (4 octets). An example of where this type 163 may/will be used is [I-D.ietf-teas-yang-rsvp]. 165 timer-value-milliseconds 166 This type covers timers which can be set in milliseconds, not set, 167 or set to infinity. This type supports a range of values that can 168 be represented in a uint32 (4 octets). Examples of where this 169 type may/will be used include [I-D.ietf-teas-yang-rsvp] and 170 [I-D.ietf-bfd-yang]. 172 3. YANG Module 174 file "ietf-routing-types@2016-10-28.yang" 175 module ietf-routing-types { 177 namespace "urn:ietf:params:xml:ns:yang:ietf-routing-types"; 178 prefix "rt-types"; 180 import ietf-yang-types { 181 prefix "yang"; 182 } 184 import ietf-inet-types { 185 prefix "inet"; 186 } 188 organization "IETF Routing Area Working Group (rtgwg)"; 189 contact 190 "Routing Area Working Group - "; 192 description 193 "This module contains a collection of YANG data types 194 considered generally useful for routing protocols."; 196 revision 2016-10-28 { 197 description 198 "Initial revision."; 199 reference 200 "RFC TBD: Routing YANG Data Types"; 201 } 203 /*** collection of types related to routing ***/ 204 typedef router-id { 205 type yang:dotted-quad; 206 description 207 "A 32-bit number in the dotted quad format assigned to each 208 router. This number uniquely identifies the router within an 209 Autonomous System."; 210 } 212 // address-family 213 identity address-family { 214 description 215 "Base identity from which identities describing address 216 families are derived."; 217 } 219 identity ipv4 { 220 base address-family; 221 description 222 "This identity represents IPv4 address family."; 223 } 225 identity ipv6 { 226 base address-family; 227 description 228 "This identity represents IPv6 address family."; 229 } 231 //The rest of the values deinfed in the IANA registry 233 identity nsap { 234 base address-family; 235 description 236 "Address family from IANA registry."; 238 } 239 identity hdlc { 240 base address-family; 241 description 242 "(8-bit multidrop) 243 Address family from IANA registry."; 244 } 245 identity bbn1822 { 246 base address-family; 247 description 248 "AHIP (BBN report #1822) 249 Address family from IANA registry."; 250 } 251 identity ieee802 { 252 base address-family; 253 description 254 "(includes all 802 media plus Ethernet canonical format) 255 Address family from IANA registry."; 256 } 257 identity e163 { 258 base address-family; 259 description 260 "Address family from IANA registry."; 261 } 262 identity e164 { 263 base address-family; 264 description 265 "SMDS, Frame Relay, ATM 266 Address family from IANA registry."; 267 } 268 identity f69 { 269 base address-family; 270 description 271 "(Telex) 272 Address family from IANA registry."; 273 } 274 identity x121 { 275 base address-family; 276 description 277 "(X.25, Frame Relay) 278 Address family from IANA registry."; 279 } 280 identity ipx { 281 base address-family; 282 description 283 "Address family from IANA registry."; 284 } 285 identity appletalk { 286 base address-family; 287 description 288 "Address family from IANA registry."; 289 } 290 identity decnet-iv { 291 base address-family; 292 description 293 "Decnet IV 294 Address family from IANA registry."; 295 } 296 identity vines { 297 base address-family; 298 description 299 "Banyan Vines 300 Address family from IANA registry."; 301 } 302 identity e164-nsap { 303 base address-family; 304 description 305 "E.164 with NSAP format subaddress 306 Address family from IANA registry."; 307 } 308 identity dns { 309 base address-family; 310 description 311 "Domain Name System 312 Address family from IANA registry."; 313 } 314 identity dn { 315 base address-family; 316 description 317 "Distinguished Name 318 Address family from IANA registry."; 319 } 320 identity as-num { 321 base address-family; 322 description 323 "AS Number 324 Address family from IANA registry."; 325 } 326 identity xtp-v4 { 327 base address-family; 328 description 329 "XTP over IPv4 330 Address family from IANA registry."; 331 } 332 identity xtp-v6 { 333 base address-family; 334 description 335 "XTP over IPv6 336 Address family from IANA registry."; 337 } 338 identity xtp { 339 base address-family; 340 description 341 "XTP native mode XTP 342 Address family from IANA registry."; 343 } 344 identity fc-port { 345 base address-family; 346 description 347 "Fibre Channel World-Wide Port Name 348 Address family from IANA registry."; 349 } 350 identity fc-node { 351 base address-family; 352 description 353 "Fibre Channel World-Wide Node Name 354 Address family from IANA registry."; 355 } 356 identity gwid { 357 base address-family; 358 description 359 "Address family from IANA registry."; 360 } 361 identity l2vpn { 362 base address-family; 363 description 364 "Address family from IANA registry."; 365 } 366 identity mpls-tp-section-eid { 367 base address-family; 368 description 369 "MPLS-TP Section Endpoint Identifier 370 Address family from IANA registry."; 371 } 372 identity mpls-tp-lsp-eid { 373 base address-family; 374 description 375 "MPLS-TP LSP Endpoint Identifier 376 Address family from IANA registry."; 377 } 378 identity mpls-tp-pwe-eid { 379 base address-family; 380 description 381 "MPLS-TP Pseudowire Endpoint Identifier 382 Address family from IANA registry."; 383 } 384 identity mt-v4 { 385 base address-family; 386 description 387 "Multi-Topology IPv4. 388 Address family from IANA registry."; 389 } 390 identity mt-v6 { 391 base address-family; 392 description 393 "Multi-Topology IPv6. 394 Address family from IANA registry."; 395 } 397 /*** collection of types related to VPN ***/ 398 typedef route-target { 399 type string { 400 pattern 401 '(0:(6553[0-5]|655[0-2]\d|65[0-4]\d{2}|6[0-4]\d{3}|' 402 + '[0-5]?\d{0,3}\d):(429496729[0-5]|42949672[0-8]\d|' 403 + '4294967[01]\d{2}|429496[0-6]\d{3}|42949[0-5]\d{4}|' 404 + '4294[0-8]\d{5}|429[0-3]\d{6}|42[0-8]\d{7}|4[01]\d{8}|' 405 + '[0-3]?\d{0,8}\d))|' 406 + '(1:(((\d|[1-9]\d|1\d{2}|2[0-4]\d|25[0-5])\.){3}(\d|[1-9]\d|' 407 + '1\d{2}|2[0-4]\d|25[0-5])):(6553[0-5]|655[0-2]\d|' 408 + '65[0-4]\d{2}|6[0-4]\d{3}|[0-5]?\d{0,3}\d))|' 409 + '(2:(429496729[0-5]|42949672[0-8]\d|4294967[01]\d{2}|' 410 + '429496[0-6]\d{3}|42949[0-5]\d{4}|4294[0-8]\d{5}|' 411 + '429[0-3]\d{6}|42[0-8]\d{7}|4[01]\d{8}|[0-3]?\d{0,8}\d):' 412 + '(6553[0-5]|655[0-2]\d|65[0-4]\d{2}|6[0-4]\d{3}|' 413 + '[0-5]?\d{0,3}\d))'; 414 } 415 description 416 "Route target has a similar format to route distinguisher. 417 A route target consists of three fields: 418 a 2-byte type field, an administrator field, 419 and an assigned number field. 420 According to the data formats for type 0, 1, and 2 defined in 421 RFC4360, the encoding pattern is defined as: 423 0:2-byte-asn:4-byte-number 424 1:4-byte-ipv4addr:2-byte-number 425 2:4-byte-asn:2-byte-number. 427 Some valid examples are: 0:100:100, 1:1.1.1.1:100, and 428 2:1234567890:203."; 429 reference 430 "RFC4360: BGP Extended Communities Attribute."; 431 } 433 typedef route-distinguisher { 434 type string { 435 pattern 436 '(0:(6553[0-5]|655[0-2]\d|65[0-4]\d{2}|6[0-4]\d{3}|' 437 + '[0-5]?\d{0,3}\d):(429496729[0-5]|42949672[0-8]\d|' 438 + '4294967[01]\d{2}|429496[0-6]\d{3}|42949[0-5]\d{4}|' 439 + '4294[0-8]\d{5}|429[0-3]\d{6}|42[0-8]\d{7}|4[01]\d{8}|' 440 + '[0-3]?\d{0,8}\d))|' 441 + '(1:(((\d|[1-9]\d|1\d{2}|2[0-4]\d|25[0-5])\.){3}(\d|[1-9]\d|' 442 + '1\d{2}|2[0-4]\d|25[0-5])):(6553[0-5]|655[0-2]\d|' 443 + '65[0-4]\d{2}|6[0-4]\d{3}|[0-5]?\d{0,3}\d))|' 444 + '(2:(429496729[0-5]|42949672[0-8]\d|4294967[01]\d{2}|' 445 + '429496[0-6]\d{3}|42949[0-5]\d{4}|4294[0-8]\d{5}|' 446 + '429[0-3]\d{6}|42[0-8]\d{7}|4[01]\d{8}|[0-3]?\d{0,8}\d):' 447 + '(6553[0-5]|655[0-2]\d|65[0-4]\d{2}|6[0-4]\d{3}|' 448 + '[0-5]?\d{0,3}\d))|' 449 + '(([3-9a-fA-F]|[1-9a-fA-F][\da-fA-F]{1,3}):' 450 + '[\da-fA-F]{1,12})'; 451 } 452 description 453 "Route distinguisher has a similar format to route target. 454 An route distinguisher consists of three fields: 455 a 2-byte type field, an administrator field, 456 and an assigned number field. 457 According to the data formats for type 0, 1, and 2 defined in 458 RFC4364, the encoding pattern is defined as: 460 0:2-byte-asn:4-byte-number 461 1:4-byte-ipv4addr:2-byte-number 462 2:4-byte-asn:2-byte-number. 463 2-byte-other-hex-number:6-byte-hex-number 465 Some valid examples are: 0:100:100, 1:1.1.1.1:100, and 466 2:1234567890:203."; 467 reference 468 "RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs)."; 469 } 471 /*** collection of types common to protocols ***/ 472 typedef ieee-bandwidth { 473 type string { 474 pattern 475 '0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|' 476 + '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|' 477 + '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}'; 479 } 480 description 481 "Bandwidth in IEEE 754 floating point 32-bit binary format: 482 (-1)**(S) * 2**(Exponent-127) * (1 + Fraction), 483 where Exponent uses 8 bits, and Fraction uses 23 bits. 484 The units are bytes per second. 485 The encoding format is the external hexadecimal-significand 486 character sequences specified in IEEE 754 and C99, 487 restricted to be normalized, non-negative, and non-fraction: 488 0x1.hhhhhhp{+}d or 0X1.HHHHHHP{+}D 489 where 'h' and 'H' are hexadecimal digits, 'd' and 'D' are 490 integers in the range of [0..127]. 491 When six hexadecimal digits are used for 'hhhhhh' or 'HHHHHH', 492 the least significant digit must be an even number. 493 'x' and 'X' indicate hexadecimal; 'p' and 'P' indicate power 494 of two. 495 Some examples are: 0x0p0, 0x1p10, and 0x1.abcde2p+20"; 496 reference 497 "IEEE Std 754-2008: IEEE Standard for Floating-Point 498 Arithmetic."; 499 } 501 typedef link-access-type { 502 type enumeration { 503 enum "broadcast" { 504 description 505 "Specify broadcast multi-access network."; 506 } 507 enum "non-broadcast" { 508 description 509 "Specify Non-Broadcast Multi-Access (NBMA) network."; 510 } 511 enum "point-to-multipoint" { 512 description 513 "Specify point-to-multipoint network."; 514 } 515 enum "point-to-point" { 516 description 517 "Specify point-to-point network."; 518 } 519 } 520 description 521 "Link access type."; 522 } 524 typedef multicast-source-ipv4-addr-type { 525 type union { 526 type enumeration { 527 enum '*' { 528 description 529 "Any source address."; 530 } 531 } 532 type inet:ipv4-address; 533 } 534 description 535 "Multicast source IP address type."; 536 } 538 typedef multicast-source-ipv6-addr-type { 539 type union { 540 type enumeration { 541 enum '*' { 542 description 543 "Any source address."; 544 } 545 } 546 type inet:ipv6-address; 547 } 548 description 549 "Multicast source IP address type."; 550 } 552 typedef timer-multiplier { 553 type uint8; 554 description 555 "The number of timer value intervals that should be 556 interpreted as a failure."; 557 } 559 typedef timer-value-seconds16 { 560 type union { 561 type uint16 { 562 range "1..65535"; 563 } 564 type enumeration { 565 enum "infinity" { 566 description "The timer is set to infinity."; 567 } 568 enum "no-expiry" { 569 description "The timer is not set."; 570 } 571 } 572 } 573 units seconds; 574 description "Timer value type, in seconds (16 bit range)."; 576 } 578 typedef timer-value-seconds32 { 579 type union { 580 type uint32 { 581 range "1..4294967295"; 582 } 583 type enumeration { 584 enum "infinity" { 585 description "The timer is set to infinity."; 586 } 587 enum "no-expiry" { 588 description "The timer is not set."; 589 } 590 } 591 } 592 units seconds; 593 description "Timer value type, in seconds (32 bit range)."; 594 } 596 typedef timer-value-milliseconds { 597 type union { 598 type uint32{ 599 range "1..4294967295"; 600 } 601 type enumeration { 602 enum "infinity" { 603 description "The timer is set to infinity."; 604 } 605 enum "no-expiry" { 606 description "The timer is not set."; 607 } 608 } 609 } 610 units milliseconds; 611 description "Timer value type, in milliseconds."; 612 } 613 } 614 616 4. IANA Considerations 618 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 619 actual RFC number (and remove this note). 621 This document registers the following namespace URIs in the IETF XML 622 registry [RFC3688]: 624 -------------------------------------------------------------------- 625 URI: urn:ietf:params:xml:ns:yang:ietf-routing-types 626 Registrant Contact: The IESG. 627 XML: N/A, the requested URI is an XML namespace. 628 -------------------------------------------------------------------- 630 This document registers the following YANG modules in the YANG Module 631 Names registry [RFC6020]: 633 -------------------------------------------------------------------- 634 name: ietf-routing-types 635 namespace: urn:ietf:params:xml:ns:yang:ietf-routing-types 636 prefix: rt-types 637 reference: RFC XXXX 638 -------------------------------------------------------------------- 640 5. Security Considerations 642 This document defines common data types using the YANG data modeling 643 language. The definitions themselves have no security impact on the 644 Internet, but the usage of these definitions in concrete YANG modules 645 might have. The security considerations spelled out in the YANG 646 specification [RFC7950] apply for this document as well. 648 6. Acknowledgements 650 The Routing Area Yang Architecture design team members included Acee 651 Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Ebben Aries, 652 Lou Berger, Qin Wu, Rob Shakir, Xufeng Liu, and Yingzhen Qu. 654 7. References 656 7.1. Normative References 658 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 659 Requirement Levels", BCP 14, RFC 2119, 660 DOI 10.17487/RFC2119, March 1997, 661 . 663 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 664 the Network Configuration Protocol (NETCONF)", RFC 6020, 665 DOI 10.17487/RFC6020, October 2010, 666 . 668 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 669 RFC 7950, DOI 10.17487/RFC7950, August 2016, 670 . 672 7.2. Informative References 674 [IEEE754] IEEE, "IEEE Standard for Floating-Point Arithmetic", IEEE 675 Std 754-2008, August 2008. 677 [I-D.ietf-bfd-yang] 678 Zheng, L., Rahman, R., Networks, J., Jethanandani, M., and 679 G. Mirsky, "Yang Data Model for Bidirectional Forwarding 680 Detection (BFD)", draft-ietf-bfd-yang-03 (work in 681 progress), July 2016. 683 [I-D.ietf-idr-bgp-model] 684 Shaikh, A., Shakir, R., Patel, K., Hares, S., D'Souza, K., 685 Bansal, D., Clemm, A., Zhdankin, A., Jethanandani, M., and 686 X. Liu, "BGP Model for Service Provider Networks", draft- 687 ietf-idr-bgp-model-02 (work in progress), July 2016. 689 [I-D.ietf-ospf-yang] 690 Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, 691 "Yang Data Model for OSPF Protocol", draft-ietf-ospf- 692 yang-06 (work in progress), October 2016. 694 [I-D.ietf-pim-yang] 695 Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu, 696 Y., and f. hu, "A YANG data model for Protocol-Independent 697 Multicast (PIM)", draft-ietf-pim-yang-03 (work in 698 progress), October 2016. 700 [I-D.ietf-teas-yang-rsvp] 701 Beeram, V., Saad, T., Gandhi, R., Liu, X., Shah, H., Chen, 702 X., Jones, R., and B. Wen, "A YANG Data Model for Resource 703 Reservation Protocol (RSVP)", draft-ietf-teas-yang-rsvp-06 704 (work in progress), October 2016. 706 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., 707 and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 708 Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, 709 . 711 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 712 Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 713 2006, . 715 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 716 (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, 717 . 719 7.3. URIs 721 [1] http://www.iana.org/assignments/address-family-numbers/address- 722 family-numbers.xhtml 724 Authors' Addresses 726 Xufeng Liu 727 Kuatro Technologies 728 8281 Greensboro Drive, Suite 200 729 McLean VA 22102 730 USA 732 EMail: xliu@kuatrotech.com 734 Yingzhen Qu 735 Cisco Systems 736 170 West Tasman Drive 737 San Jose CA 95134 738 USA 740 EMail: yiqu@cisco.com 742 Acee Lindem 743 Cisco Systems 744 301 Midenhall Way 745 Cary, NC 27513 746 USA 748 EMail: acee@cisco.com 750 Christian Hopps 751 Deutsche Telekom 753 EMail: chopps@chopps.org 755 Lou Berger 756 LabN Consulting, L.L.C. 758 EMail: lberger@labn.net