idnits 2.17.1 draft-bestbar-teas-yang-topology-filter-03.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 == Line 220 has weird spacing: '...ance-id uin...' == Line 221 has weird spacing: '...sion-id uin...' == Line 229 has weird spacing: '...ance-id uin...' == Line 230 has weird spacing: '...sion-id uin...' == Line 238 has weird spacing: '...ance-id uin...' == (7 more instances...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 7, 2022) is 780 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 (-25) exists of draft-ietf-teas-ietf-network-slices-07 Summary: 0 errors (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 TEAS Working Group V. Beeram 3 Internet-Draft T. Saad 4 Intended status: Standards Track Juniper Networks 5 Expires: September 8, 2022 R. Gandhi 6 Cisco Systems 7 X. Liu 8 IBM Corporation 9 March 7, 2022 11 YANG Data Model for Topology Filter 12 draft-bestbar-teas-yang-topology-filter-03 14 Abstract 16 This document defines a YANG data model for the management of 17 topology filters/filter-sets on network elements and controllers. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 23 "OPTIONAL" in this document are to be interpreted as described in BCP 24 14 [RFC2119] [RFC8174] when, and only when, they appear in all 25 capitals, as shown here. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on September 8, 2022. 44 Copyright Notice 46 Copyright (c) 2022 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 1.1. Use-Cases . . . . . . . . . . . . . . . . . . . . . . . . 3 63 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 64 1.3. Tree Structure . . . . . . . . . . . . . . . . . . . . . 4 65 2. Topology Filter Data Model . . . . . . . . . . . . . . . . . 4 66 2.1. Model Structure . . . . . . . . . . . . . . . . . . . . . 4 67 2.1.1. Topology Filters . . . . . . . . . . . . . . . . . . 4 68 2.1.1.1. Topology Reference . . . . . . . . . . . . . . . 4 69 2.1.1.2. Filters . . . . . . . . . . . . . . . . . . . . . 5 70 2.1.2. Topology Filter-Sets . . . . . . . . . . . . . . . . 6 71 2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 6 72 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 73 4. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 12 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 75 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 76 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 77 7.1. Normative References . . . . . . . . . . . . . . . . . . 14 78 7.2. Informative References . . . . . . . . . . . . . . . . . 15 79 Appendix A. Complete Model Tree Structure . . . . . . . . . . . 16 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 82 1. Introduction 84 A topology filter is a data construct that is used to filter network 85 topologies [RFC8345]. It can be applied on either a native topology 86 or a customized topology [RFC8795] to produce a filtered set of 87 topological elements. A topology filter-set is a union of multiple 88 topology filters that can be applied in tandem on a topology. This 89 document defines a YANG data model for the management of topology 90 filters/filter-sets on network elements and controllers. 92 The authors acknowledge that an implementation may maintain network 93 topologies that are learnt via routing protocols in a Routing 94 Information Base (RIB) [RFC8431] and use routing policies [RFC9067] 95 to filter the entries in the RIB. Such an implementation is not the 96 target of this document. 98 1.1. Use-Cases 100 * Specification of topology related constraints for TE Path 101 Computation: A few examples of this are - 103 - Compute a path within a specified topology. 105 - Compute a path within the topology associated with a specific 106 IGP domain. 108 - Compute a path within the topology learnt from a specific TE 109 Information Source. 111 - Compute a path within the topology defined by the application 112 of one or more topology filters: 114 o Use a topology with elements learnt via ISIS Level-2 and 115 include resource-affinity "RED" 117 o Use a topology with elements associated with ISIS Flexible 118 Algorithm 128 and exclude resource-affinity "BLUE" 120 * Specification of topology associated with an Network Resource 121 Partition (NRP): A few examples of rules for determining the 122 topology associated with the NRP 123 [I-D.ietf-teas-ietf-network-slices] are: 125 - All the elements in the specified topology are part of the NRP 126 topology. 128 - All the topological elements associated with a specific IGP 129 domain are part of the NRP topology. 131 - All the topological elements that include resource-affinity 132 "RED" and exclude resource-affinity "BLUE" are part of the NRP 133 topology. 135 1.2. Terminology 137 The terminology for describing YANG data models is found in 138 [RFC7950]. 140 The reader is expected to be familiar with the topology modeling 141 terminology specified in [RFC8345], [RFC8776] and [RFC8795]. 143 1.3. Tree Structure 145 A simplified graphical representation of the data model is presented 146 in Appendix A of this document. The tree format defined in [RFC8340] 147 is used for the YANG data model tree representation. 149 2. Topology Filter Data Model 151 2.1. Model Structure 153 The high-level model structure defined by this document is as shown 154 below: 156 module: ietf-topology-filter 157 augment /nw:networks: 158 +--rw topology-filters! 159 | +--rw topology-filter* [name] 160 | +--rw name string 161 | +--rw topology-ref 162 | | .......... 163 | +--rw include-any 164 | | .......... 165 | +--rw include-all 166 | | .......... 167 | +--rw exclude 168 | .......... 169 +--rw topology-filter-sets! 170 +--rw topology-filter-set* [name] 171 +--rw name string 172 + .......... 174 The top-level 'networks' container [RFC8345] is augmented with a set 175 of topology filters and a set of topology filter-sets. 177 2.1.1. Topology Filters 179 The 'topology-filters' container carries a list of topology filters. 180 Each topology-filter entry specifies a set of include-any, include- 181 all and exclude filtering rules that can be applied on either the 182 native topology or a user specified topology. 184 2.1.1.1. Topology Reference 186 The 'topology-reference' container indicates the topology on which 187 the filtering rules need to be applied. The referenced topology 188 could be a predefined TE topology and/or a specific IGP domain. The 189 absence of the 'topology-reference' indicates that the filtering 190 rules are to be applied on the native topology. 192 +--rw topology-ref 193 +--rw igp-domain-identifier 194 | +--rw protocol-id? igp-protocol 195 | +--rw instance-id? uint32 196 | +--rw division-id? uint32 197 | +--rw algo-id? uint8 198 | +--rw mt-id? uint16 199 +--rw te-topology-identifier 200 +--rw provider-id? te-global-id 201 +--rw client-id? te-global-id 202 +--rw topology-id? te-topology-id 204 2.1.1.2. Filters 206 The 'include-any', 'include-all' and 'exclude' containers carry a 207 varied set of attributes that can be used as rules to filter the 208 topology. If the topology-filter entry carries no filtering rules 209 and only references a specific topology, then the set of filtered 210 topological elements produced is the same as the one defined by the 211 referenced topology. 213 +--rw include-any 214 | +--rw link-affinity* string 215 | +--rw link-name* string 216 | +--rw node-prefix* inet:ip-prefix 217 | +--rw as* inet:as-number 218 | +--rw info-source* [source-id instance-id division-id] 219 | +--rw source-id tet:te-info-source 220 | +--rw instance-id uint32 221 | +--rw division-id uint32 222 +--rw include-all 223 | +--rw link-affinity* string 224 | +--rw link-name* string 225 | +--rw node-prefix* inet:ip-prefix 226 | +--rw as* inet:as-number 227 | +--rw info-source* [source-id instance-id division-id] 228 | +--rw source-id tet:te-info-source 229 | +--rw instance-id uint32 230 | +--rw division-id uint32 231 +--rw exclude 232 +--rw link-affinity* string 233 +--rw link-name* string 234 +--rw node-prefix* inet:ip-prefix 235 +--rw as* inet:as-number 236 +--rw info-source* [source-id instance-id division-id] 237 +--rw source-id tet:te-info-source 238 +--rw instance-id uint32 239 +--rw division-id uint32 241 2.1.2. Topology Filter-Sets 243 The 'topology-filter-sets' container carries a list of topology 244 filter-sets. Each topology-filter-set entry constitutes a list of 245 topology-filter references. This is used when there is a need to 246 create a union of multiple topology filters. 248 +--rw topology-filter-sets! 249 +--rw topology-filter-set* [name] 250 +--rw name string 251 +--rw topology-filter* 252 -> ../../../topology-filters/topology-filter/name 254 2.2. YANG Module 256 file "ietf-topology-filter@2022-03-07.yang" 257 module ietf-topology-filter { 258 yang-version 1.1; 259 namespace "urn:ietf:params:xml:ns:yang:ietf-topology-filter"; 260 prefix topo-filt; 262 import ietf-inet-types { 263 prefix inet; 264 reference 265 "RFC 6991: Common YANG Data Types"; 266 } 267 import ietf-network { 268 prefix nw; 269 reference 270 "RFC 8345: A YANG Data Model for Network Topologies"; 271 } 272 import ietf-te-types { 273 prefix te-types; 274 reference 275 "RFC 8776: Common YANG Data Types for Traffic Engineering"; 276 } 277 import ietf-te-topology { 278 prefix tet; 279 reference 280 "RFC 8795: YANG Data Model for Traffic Engineering Topologies"; 281 } 283 organization 284 "IETF Traffic Engineering Architecture and Signaling (TEAS) 285 Working Group."; 286 contact 287 "WG Web: 288 WG List: 289 Editor: Vishnu Pavan Beeram 290 292 Editor: Tarek Saad 293 295 Editor: Rakesh Gandhi 296 298 Editor: Xufeng Liu 299 "; 301 description 302 "This YANG module defines data definitions for managing 303 topology filters. 305 Copyright (c) 2022 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 to 310 the license terms contained in, the Simplified BSD License set 311 forth in Section 4.c of the IETF Trust's Legal Provisions 312 Relating to IETF Documents 313 (https://trustee.ietf.org/license-info). 315 This version of this YANG module is part of RFC XXXX; see the 316 RFC itself for full legal notices."; 318 revision 2022-03-07 { 319 description 320 "Initial revision."; 321 reference 322 "RFC XXXX: YANG Data Model for Topology Filters."; 323 } 325 /* 326 * T Y P E D E F S 327 */ 329 typedef igp-protocol { 330 type enumeration { 331 enum ospfv2 { 332 description 333 "OSPFv2."; 334 } 335 enum ospfv3 { 336 description 337 "OSPFv3."; 338 } 339 enum isis { 340 description 341 "IS-IS."; 342 } 343 } 344 description 345 "IGP Protocol Type."; 346 } 348 /* 349 * G R O U P I N G S 350 */ 351 /* 352 * Grouping - Topology Information Source. 353 */ 355 grouping igp-topology-info-source { 356 description 357 "Grouping for igp topology information source."; 358 leaf protocol-id { 359 type igp-protocol; 360 description 361 "IGP Protocol Type."; 362 } 363 leaf instance-id { 364 type uint32; 365 description 366 "Information Source Instance."; 367 } 368 leaf division-id { 369 type uint32; 370 description 371 "Information Source Division."; 372 } 373 } 375 /* 376 * Grouping - IGP Domain Identifier. 377 */ 379 grouping igp-domain-identifier { 380 description 381 "Grouping for igp domain identifier."; 382 container igp-domain-identifier { 383 description 384 "Container for igp domain identifier."; 386 uses igp-topology-info-source; 387 leaf algo-id { 388 type uint8; 389 description 390 "Algorithm ID."; 391 } 392 leaf mt-id { 393 type uint16; 394 description 395 "Multi Topology ID."; 396 } 397 } 398 } 400 /* 401 * Grouping - Topology Reference 402 */ 404 grouping topology-reference { 405 description 406 "Grouping for topology reference."; 407 container topology-ref { 408 description 409 "Container for topology reference."; 410 uses igp-domain-identifier; 411 uses te-types:te-topology-identifier; 412 } 413 } 415 /* 416 * Grouping - Topology Information Sources 417 */ 419 grouping topology-info-sources { 420 description 421 "Grouping for topology information sources."; 422 list info-source { 423 key "source-id instance-id division-id"; 424 description 425 "List of information-sources."; 426 leaf source-id { 427 type tet:te-info-source; 428 description 429 "Information Source."; 430 } 431 leaf instance-id { 432 type uint32; 433 description 434 "Information Source Instance."; 435 } 436 leaf division-id { 437 type uint32; 438 description 439 "Information Source Division."; 440 } 441 } 442 } 444 /* 445 * Grouping - Custom Topology Filters 446 */ 448 grouping custom-topology-filters { 449 description 450 "Grouping for custom topology filters."; 451 leaf-list link-affinity { 452 type string; 453 description 454 "List of link affinities."; 455 } 456 leaf-list link-name { 457 type string; 458 description 459 "List of link names."; 460 } 461 leaf-list node-prefix { 462 type inet:ip-prefix; 463 description 464 "List of node IDs."; 465 } 466 leaf-list as { 467 type inet:as-number; 468 description 469 "List of AS numbers."; 470 } 471 uses topology-info-sources; 472 } 474 /* 475 * Grouping - Topology Filters 476 */ 478 grouping topology-filters { 479 description 480 "Grouping for topology filters."; 481 container topology-filters { 482 presence "Enable Topology Filters."; 483 description 484 "Container for topology filters."; 485 list topology-filter { 486 key "name"; 487 description 488 "List of topology filters."; 489 leaf name { 490 type string; 491 description 492 "A string that uniquely identifies the topology filter."; 493 } 494 uses topology-reference; 495 container include-any { 496 description 497 "Include-any filters."; 498 uses custom-topology-filters; 499 } 500 container include-all { 501 description 502 "Include-all filters."; 503 uses custom-topology-filters; 504 } 505 container exclude { 506 description 507 "Exclude filters."; 508 uses custom-topology-filters; 509 } 510 } 511 } 512 } 514 /* 515 * Grouping - Topology Filter Sets 516 */ 518 grouping topology-filter-sets { 519 description 520 "Grouping for topology filter sets."; 521 container topology-filter-sets { 522 presence "Enable Topology Filter-Sets."; 523 description 524 "Container for topology filter sets."; 525 list topology-filter-set { 526 key "name"; 527 description 528 "List of topology filter sets."; 529 leaf name { 530 type string; 531 description 532 "A string that uniquely identifies the topology 533 filter-set."; 534 } 535 leaf-list topology-filter { 536 type leafref { 537 path "../../../topo-filt:topology-filters/" 538 + "topo-filt:topology-filter/topo-filt:name"; 539 } 540 description 541 "Reference to a specific topology filter from the list 542 of topology filters."; 543 } 544 } 545 } 546 } 548 /* 549 * Augment - Topology Filters / Topology Filter-Sets 550 */ 552 augment "/nw:networks" { 553 description 554 "Augment networks with topology-filters and 555 topology-filter-sets."; 556 uses topology-filters; 557 uses topology-filter-sets; 558 } 559 } 560 562 3. Acknowledgements 564 The authors would like to thank Sudharsana Venkatraman for her input 565 from discussions. 567 4. Contributors 569 The following individuals contributed to this document: 571 Colby Barth 572 Juniper Networks 573 Email: cbarth@juniper.net 575 Srihari R. Sangli 576 Juniper Networks 577 Email: ssangli@juniper.net 578 Chandra Ramachandran 579 Juniper Networks 580 Email: csekar@juniper.net 582 5. IANA Considerations 584 This document registers the following URI in the IETF XML registry 585 [RFC3688]. Following the format in [RFC3688], the following 586 registration is requested to be made. 588 URI: urn:ietf:params:xml:ns:yang:ietf-topology-filter 589 Registrant Contact: The TEAS WG of the IETF. 590 XML: N/A, the requested URI is an XML namespace. 592 This document registers a YANG module in the YANG Module Names 593 registry [RFC6020]. 595 name: ietf-topology-filter 596 namespace: urn:ietf:params:xml:ns:yang:ietf-topology-filter 597 prefix: ns-phd 598 reference: RFCXXXX 600 6. Security Considerations 602 The YANG module specified in this document defines a schema for data 603 that is designed to be accessed via network management protocols such 604 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 605 is the secure transport layer, and the mandatory-to-implement secure 606 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 607 is HTTPS, and the mandatory-to-implement secure transport is TLS 608 [RFC8446]. 610 The Network Configuration Access Control Model (NACM) [RFC8341] 611 provides the means to restrict access for particular NETCONF or 612 RESTCONF users to a preconfigured subset of all available NETCONF or 613 RESTCONF protocol operations and content. 615 The data nodes defined in this YANG module that are 616 writable/creatable/deletable (i.e., config true, which is the 617 default) may be considered sensitive or vulnerable in some network 618 environments. Write operations (e.g., edit-config) to these data 619 nodes without proper protection can have a negative effect on network 620 operations. These are the subtrees and data nodes and their 621 sensitivity/vulnerability: 623 * "/networks/topology-filters/": This subtree specifies the 624 configurations for topology filters. By manipulating these data 625 nodes, a malicious attacker may cause unauthorized and improper 626 behavior to any service that is making use of the filtered set of 627 topological elements produced by the application of the 628 compromised topology filter. 630 * "/networks/topology-filter-sets": This subtree specifies the 631 configurations for topology filter-sets. By manipulating these 632 data nodes, a malicious attacker may cause unauthorized and 633 improper behavior to any service that is making use of the 634 filtered set of topological elements produced by the application 635 of the compromised topology filter-set. 637 The readable data nodes in this YANG module may be considered 638 sensitive or vulnerable in some network environments. It is thus 639 important to control read access (e.g., via get, get-config, or 640 notification) to these data nodes. These are the subtrees and data 641 nodes and their sensitivity/vulnerability: 643 * "/networks/topology-filter": Unauthorized access to this subtree 644 can disclose the topology filters used in the network. 646 * "/networks/topology-filter-sets": Unauthorized access to this 647 subtree can disclose the topology filter-sets used in the network. 649 7. References 651 7.1. Normative References 653 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 654 Requirement Levels", BCP 14, RFC 2119, 655 DOI 10.17487/RFC2119, March 1997, 656 . 658 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 659 DOI 10.17487/RFC3688, January 2004, 660 . 662 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 663 the Network Configuration Protocol (NETCONF)", RFC 6020, 664 DOI 10.17487/RFC6020, October 2010, 665 . 667 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 668 and A. Bierman, Ed., "Network Configuration Protocol 669 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 670 . 672 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 673 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 674 . 676 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 677 RFC 7950, DOI 10.17487/RFC7950, August 2016, 678 . 680 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 681 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 682 . 684 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 685 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 686 May 2017, . 688 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 689 Access Control Model", STD 91, RFC 8341, 690 DOI 10.17487/RFC8341, March 2018, 691 . 693 [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., 694 Ananthakrishnan, H., and X. Liu, "A YANG Data Model for 695 Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March 696 2018, . 698 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 699 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 700 . 702 [RFC8776] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 703 "Common YANG Data Types for Traffic Engineering", 704 RFC 8776, DOI 10.17487/RFC8776, June 2020, 705 . 707 [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and 708 O. Gonzalez de Dios, "YANG Data Model for Traffic 709 Engineering (TE) Topologies", RFC 8795, 710 DOI 10.17487/RFC8795, August 2020, 711 . 713 7.2. Informative References 715 [I-D.ietf-teas-ietf-network-slices] 716 Farrel, A., Drake, J., Rokui, R., Homma, S., Makhijani, 717 K., Contreras, L. M., and J. Tantsura, "Framework for IETF 718 Network Slices", draft-ietf-teas-ietf-network-slices-07 719 (work in progress), March 2022. 721 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 722 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 723 . 725 [RFC8431] Wang, L., Chen, M., Dass, A., Ananthakrishnan, H., Kini, 726 S., and N. Bahadur, "A YANG Data Model for the Routing 727 Information Base (RIB)", RFC 8431, DOI 10.17487/RFC8431, 728 September 2018, . 730 [RFC9067] Qu, Y., Tantsura, J., Lindem, A., and X. Liu, "A YANG Data 731 Model for Routing Policy", RFC 9067, DOI 10.17487/RFC9067, 732 October 2021, . 734 Appendix A. Complete Model Tree Structure 735 module: ietf-topology-filter 736 augment /nw:networks: 737 +--rw topology-filters! 738 | +--rw topology-filter* [name] 739 | +--rw name string 740 | +--rw topology-ref 741 | | +--rw igp-domain-identifier 742 | | | +--rw protocol-id? igp-protocol 743 | | | +--rw instance-id? uint32 744 | | | +--rw division-id? uint32 745 | | | +--rw algo-id? uint8 746 | | | +--rw mt-id? uint16 747 | | +--rw te-topology-identifier 748 | | +--rw provider-id? te-global-id 749 | | +--rw client-id? te-global-id 750 | | +--rw topology-id? te-topology-id 751 | +--rw include-any 752 | | +--rw link-affinity* string 753 | | +--rw link-name* string 754 | | +--rw node-prefix* inet:ip-prefix 755 | | +--rw as* inet:as-number 756 | | +--rw info-source* [source-id instance-id division-id] 757 | | +--rw source-id tet:te-info-source 758 | | +--rw instance-id uint32 759 | | +--rw division-id uint32 760 | +--rw include-all 761 | | +--rw link-affinity* string 762 | | +--rw link-name* string 763 | | +--rw node-prefix* inet:ip-prefix 764 | | +--rw as* inet:as-number 765 | | +--rw info-source* [source-id instance-id division-id] 766 | | +--rw source-id tet:te-info-source 767 | | +--rw instance-id uint32 768 | | +--rw division-id uint32 769 | +--rw exclude 770 | +--rw link-affinity* string 771 | +--rw link-name* string 772 | +--rw node-prefix* inet:ip-prefix 773 | +--rw as* inet:as-number 774 | +--rw info-source* [source-id instance-id division-id] 775 | +--rw source-id tet:te-info-source 776 | +--rw instance-id uint32 777 | +--rw division-id uint32 778 +--rw topology-filter-sets! 779 +--rw topology-filter-set* [name] 780 +--rw name string 781 +--rw topology-filter* 782 -> ../../../topology-filters/topology-filter/name 784 Authors' Addresses 786 Vishnu Pavan Beeram 787 Juniper Networks 789 Email: vbeeram@juniper.net 791 Tarek Saad 792 Juniper Networks 794 Email: tsaad@juniper.net 796 Rakesh Gandhi 797 Cisco Systems 799 Email: rgandhi@cisco.com 801 Xufeng Liu 802 IBM Corporation 804 Email: xufeng.liu.ietf@gmail.com