idnits 2.17.1 draft-ietf-teas-yang-sr-te-topo-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 == Line 195 has weird spacing: '...r-bound uin...' == Line 196 has weird spacing: '...r-bound uin...' == Line 200 has weird spacing: '...r-bound uin...' == Line 201 has weird spacing: '...r-bound uin...' == Line 203 has weird spacing: '...r-bound uin...' == (2 more instances...) == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (February 20, 2018) is 2247 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: 'RFC3688' is mentioned on line 457, but not defined == Missing Reference: 'RFC6020' is mentioned on line 472, but not defined == Unused Reference: 'I-D.ietf-teas-yang-te-topo' is defined on line 535, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-spring-sr-yang' is defined on line 541, but no explicit reference was found in the text == Outdated reference: A later version (-22) exists of draft-ietf-teas-yang-te-topo-13 == Outdated reference: A later version (-30) exists of draft-ietf-spring-sr-yang-08 Summary: 0 errors (**), 0 flaws (~~), 14 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Liu 3 Internet-Draft Jabil 4 Intended status: Standards Track I. Bryskin 5 Expires: August 24, 2018 Huawei Technologies 6 V. Beeram 7 Juniper Networks 8 T. Saad 9 Cisco Systems Inc 10 H. Shah 11 Ciena 12 S. Litkowski 13 Orange Business Service 14 February 20, 2018 16 YANG Data Model for SR and SR TE Topologies 17 draft-ietf-teas-yang-sr-te-topo-00 19 Abstract 21 This document defines a YANG data model for Segment Routing (SR) 22 topology and Segment Routing (SR) traffic engineering (TE) topology. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on August 24, 2018. 41 Copyright Notice 43 Copyright (c) 2018 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 3 61 2.1. Segment Routing (SR) topology . . . . . . . . . . . . . . 3 62 2.2. Segment Routing (SR) TE topology . . . . . . . . . . . . 3 63 2.3. Relations to ietf-segment-routing . . . . . . . . . . . . 4 64 2.4. Open Items . . . . . . . . . . . . . . . . . . . . . . . 4 65 3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 4 66 4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 6 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 68 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 70 7.1. Normative References . . . . . . . . . . . . . . . . . . 11 71 7.2. Informative References . . . . . . . . . . . . . . . . . 12 72 Appendix A. Companion YANG Model for Non-NMDA Compliant 73 Implementations . . . . . . . . . . . . . . . . . . 13 74 A.1. SR Topology State Module . . . . . . . . . . . . . . . . 13 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 77 1. Introduction 79 This document defines a YANG [RFC7950] data model for describing the 80 presentations of Segment Routing (SR) topology and Segment Routing 81 (SR) traffic engineering (TE) topology. 83 1.1. Terminology 85 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 87 "OPTIONAL" in this document are to be interpreted as described in BCP 88 14, [RFC2119]. 90 The following terms are defined in [RFC7950] and are not redefined 91 here: 93 o augment 95 o data model 96 o data node 98 2. Modeling Considerations 100 2.1. Segment Routing (SR) topology 102 The Layer 3 network topology model is discussed in 103 [I-D.ietf-i2rs-yang-l3-topology]. The Segment Routing (SR) topology 104 model proposed in this document augments and uses the ietf-l3- 105 unicast-igp-topology module defined in 106 [I-D.ietf-i2rs-yang-l3-topology]. SR related attributes are covered 107 in the ietf-sr-topology model. 109 +------------------------------+ 110 | Layer 3 Network Topology | 111 | ietf-l3-unicast-topology | 112 +------------------------------+ 113 | 114 | 115 | 116 V 117 +------------------------+ 118 | SR Topology | 119 | ietf-sr-topology | 120 +------------------------+ 122 2.2. Segment Routing (SR) TE topology 124 When traffic engineering is enabled on an SR topology, there will be 125 associations between objects in SR topologies and objects in TE 126 topologies. An SR TE topology is both an SR topology and a layer 3 127 TE topology. Multiple inheritance is used to achieve such relations. 129 +------------------+ +---------------------+ 130 | SR Topology | | L3 TE Topology | 131 | ietf-sr-topology | | ietf-l3-te-topology | 132 +------------------+ +---------------------+ 133 \ / 134 \ / 135 \ / 136 v v 137 +------------------------+ 138 | SR TE Topology | 139 | | 140 +------------------------+ 142 Each type of topologies is indicated by "network-types" defined in 143 [I-D.ietf-i2rs-yang-network-topo]. For the three types of topologies 144 above, the data representations are: 146 L3 Topology: 148 /nd:networks/nd:network/nd:network-types/l3-unicast-topology 150 L3 TE Topology: 152 /nd:networks/nd:network/nd:network-types/l3-unicast-topology/l3-te 154 SR Topology: 156 /nd:networks/nd:network/nd:network-types/l3-unicast-topology/sr 158 SR TE Topology: (multiple inheritance) 160 /nd:networks/nd:network/nd:network-types/l3-unicast-topology/l3-te 161 /nd:networks/nd:network/nd:network-types/l3-unicast-topology/sr 163 2.3. Relations to ietf-segment-routing 165 [I-D.ietf-spring-sr-yang]defines ietf-segment-routing that is a model 166 intended to be used on network elements to configure or operate 167 segment routing; ietf-sr-topology defined in this document is 168 intended to be used on a controller for the network-wide operations 169 such as path computation. 171 SR topology model shares many modeling constructs defined in ietf- 172 segment-routing. The module ietf-sr-topology uses the types and 173 groupings defined in ietf-segment-routing. 175 2.4. Open Items 177 a. Protection on link: The feature of link protection will be 178 modeled in the next revision. 180 b. Link bundle: The feature of link bundle will be modeled in the 181 next revision. 183 3. Model Structure 185 The model tree structure of the Segment Routing (SR) topology module 186 is as shown below: 188 module: ietf-sr-topology 189 augment /nw:networks/nw:network/nw:network-types 190 /l3t:l3-unicast-topology: 191 +--rw sr! 192 augment /nw:networks/nw:network/l3t:l3-topology-attributes: 193 +--rw sr 194 +--rw srgb* [lower-bound upper-bound] 195 +--rw lower-bound uint32 196 +--rw upper-bound uint32 197 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes: 198 +--rw sr 199 +--rw srgb* [lower-bound upper-bound] 200 | +--rw lower-bound uint32 201 | +--rw upper-bound uint32 202 +--rw srlb* [lower-bound upper-bound] 203 | +--rw lower-bound uint32 204 | +--rw upper-bound uint32 205 +--rw node-capabilities 206 | +--rw transport-planes* [transport-plane] 207 | | +--rw transport-plane identityref 208 | +--rw readable-label-stack-depth? uint8 209 +--ro information-source? enumeration 210 +--ro information-source-state 211 +--ro credibility-preference? uint16 212 augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes 213 /l3t:prefix: 214 +--rw sr! 215 +--rw value-type? enumeration 216 +--rw start-sid uint32 217 +--rw range? uint32 218 +--rw algorithm? identityref 219 +--rw last-hop-behavior? enumeration 220 {sid-last-hop-behavior}? 221 +--rw is-local? boolean 222 augment /nw:networks/nw:network/nw:node/nt:termination-point 223 /l3t:l3-termination-point-attributes: 224 augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes: 225 +--rw sr 226 +--rw sid? uint32 227 +--rw value-type? enumeration 228 +--rw is-local? boolean 229 +--ro is-part-of-set? boolean 230 +--ro is-on-lan? boolean 231 +--ro information-source? enumeration 232 +--ro information-source-state 233 +--ro credibility-preference? uint16 235 4. YANG Module 237 file "ietf-sr-topology@2017-10-30.yang" 238 module ietf-sr-topology { 239 yang-version 1.1; 240 namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology"; 241 prefix "srt"; 243 import ietf-network { 244 prefix "nw"; 245 } 246 import ietf-network-topology { 247 prefix "nt"; 248 } 249 import ietf-l3-unicast-topology { 250 prefix "l3t"; 251 } 252 import ietf-segment-routing-common { 253 prefix "sr-cmn"; 254 } 256 organization "TBD"; 257 contact "TBD"; 258 description "L3 TE Topology model"; 260 revision 2017-10-30 { 261 description "Initial revision"; 262 reference "TBD"; 263 } 265 grouping sr-topology-type { 266 description 267 "Identifies the SR topology type."; 268 container sr { 269 presence "Indiates SR Topology"; 270 description 271 "Its presence identifies the SR topology type."; 272 } 273 } 275 augment "/nw:networks/nw:network/nw:network-types/" 276 + "l3t:l3-unicast-topology" { 277 description 278 "Defines the SR topology type."; 279 uses sr-topology-type; 280 } 281 augment "/nw:networks/nw:network/l3t:l3-topology-attributes" { 282 when "../nw:network-types/l3t:l3-unicast-topology/sr" { 283 description "Augment only for SR topology."; 284 } 285 description "Augment topology configuration"; 286 uses sr-topology-attributes; 287 } 289 augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" { 290 when "../../nw:network-types/l3t:l3-unicast-topology/sr" { 291 description "Augment only for SR topology."; 292 } 293 description "Augment node configuration."; 294 uses sr-node-attributes; 295 } 297 augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" 298 + "/l3t:prefix" { 299 when "../../../nw:network-types/l3t:l3-unicast-topology/sr" { 300 description "Augment only for SR topology."; 301 } 302 description "Augment node prefix."; 303 uses sr-node-prefix-attributes; 304 } 306 augment "/nw:networks/nw:network/nw:node/nt:termination-point/" 307 + "l3t:l3-termination-point-attributes" { 308 when "../../../nw:network-types/l3t:l3-unicast-topology/" 309 + "sr" { 310 description "Augment only for SR topology."; 311 } 312 description "Augment termination point configuration"; 313 uses sr-tp-attributes; 314 } 316 augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" { 317 when "../../nw:network-types/l3t:l3-unicast-topology/sr" { 318 description "Augment only for SR topology."; 319 } 320 description "Augment link configuration."; 321 uses sr-link-attributes; 322 } 324 grouping sr-topology-attributes { 325 description "SR topology scope attributes."; 326 container sr { 327 description 328 "Containing SR attributes."; 330 uses sr-cmn:srgb-cfg; 331 } // sr 332 } // sr-topology-attributes 334 grouping information-source-attributes { 335 description 336 "The attributes identifying source that has provided the 337 related information, and the source credibility."; 338 leaf information-source { 339 type enumeration { 340 enum "unknown" { 341 description "The source is unknown."; 342 } 343 enum "locally-configured" { 344 description "Configured entity."; 345 } 346 enum "ospfv2" { 347 description "OSPFv2."; 348 } 349 enum "ospfv3" { 350 description "OSPFv3."; 351 } 352 enum "isis" { 353 description "ISIS."; 354 } 355 enum "system-processed" { 356 description "System processed entity."; 357 } 358 enum "other" { 359 description "Other source."; 360 } 361 } 362 config false; 363 description 364 "Indicates the source of the information."; 365 } 366 container information-source-state { 367 config false; 368 description 369 "The container contains state attributes related to 370 the information source."; 371 leaf credibility-preference { 372 type uint16; 373 description 374 "The preference value to calculate the traffic 375 engineering database credibility value used for 376 tie-break selection between different 377 information-source values. 379 Higher value is more preferable."; 380 } 381 } 382 } // information-source-attributes 384 grouping sr-node-attributes { 385 description "SR node scope attributes."; 386 container sr { 387 description 388 "Containing SR attributes."; 389 uses sr-cmn:srgb-cfg; 390 uses sr-cmn:srlb-cfg; 391 uses sr-cmn:node-capabilities; 392 // Operational state data 393 uses information-source-attributes; 394 } // sr 395 } // sr-node-attributes 397 grouping sr-node-prefix-attributes { 398 description "Containing SR attributes for a prefix."; 399 container sr { 400 presence "Presence indicates SR is enabled."; 401 description 402 "Containing SR attributes for a prefix."; 403 uses sr-cmn:prefix-sid-attributes; 404 uses sr-cmn:last-hop-behavior; 405 leaf is-local { 406 type boolean; 407 description 408 "'true' if the SID is local."; 409 } 410 } // sr 411 } // sr-node-prefix-attributes 413 grouping sr-tp-attributes { 414 description "SR termination point scope attributes"; 415 } // sr-tp-attributes 417 grouping sr-link-attributes { 418 description "SR link scope attributes"; 419 container sr { 420 description 421 "Containing SR attributes."; 422 leaf sid { 423 type uint32; 424 description 425 "SID."; 426 } 427 uses sr-cmn:sid-value-type; 428 leaf is-local { 429 type boolean; 430 description 431 "'true' if the SID is local."; 432 } 433 leaf is-part-of-set { 434 type boolean; 435 config false; 436 description 437 "'true' if the SID is part of a set."; 438 } 439 leaf is-on-lan { 440 type boolean; 441 config false; 442 description 443 "'true' if on a lan."; 444 } 445 uses information-source-attributes; 446 } // sr 447 } // sr-link-attributes 448 } 449 451 5. IANA Considerations 453 RFC Ed.: In this section, replace all occurrences of 'XXXX' with the 454 actual RFC number (and remove this note). 456 This document registers the following namespace URIs in the IETF XML 457 registry [RFC3688]: 459 -------------------------------------------------------------------- 460 URI: urn:ietf:params:xml:ns:yang:ietf-sr-topology 461 Registrant Contact: The IESG. 462 XML: N/A, the requested URI is an XML namespace. 463 -------------------------------------------------------------------- 465 -------------------------------------------------------------------- 466 URI: urn:ietf:params:xml:ns:yang:ietf-sr-topology-state 467 Registrant Contact: The IESG. 468 XML: N/A, the requested URI is an XML namespace. 469 -------------------------------------------------------------------- 471 This document registers the following YANG modules in the YANG Module 472 Names registry [RFC6020]: 474 -------------------------------------------------------------------- 475 name: ietf-sr-topology 476 namespace: urn:ietf:params:xml:ns:yang:ietf-sr-topology 477 prefix: srt 478 reference: RFC XXXX 479 -------------------------------------------------------------------- 481 -------------------------------------------------------------------- 482 name: ietf-sr-topology-state 483 namespace: urn:ietf:params:xml:ns:yang:ietf-sr-topology-state 484 prefix: srt-s 485 reference: RFC XXXX 486 -------------------------------------------------------------------- 488 6. Security Considerations 490 The configuration, state, action and notification data defined in 491 this document are designed to be accessed via the NETCONF protocol 492 [RFC6241]. The data-model by itself does not create any security 493 implications. The security considerations for the NETCONF protocol 494 are applicable. The NETCONF protocol used for sending the data 495 supports authentication and encryption. 497 7. References 499 7.1. Normative References 501 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 502 Requirement Levels", BCP 14, RFC 2119, 503 DOI 10.17487/RFC2119, March 1997, . 506 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 507 and A. Bierman, Ed., "Network Configuration Protocol 508 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 509 . 511 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 512 RFC 7950, DOI 10.17487/RFC7950, August 2016, 513 . 515 [I-D.ietf-netmod-revised-datastores] 516 Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 517 and R. Wilton, "Network Management Datastore 518 Architecture", draft-ietf-netmod-revised-datastores-10 519 (work in progress), January 2018. 521 7.2. Informative References 523 [I-D.ietf-i2rs-yang-network-topo] 524 Clemm, A., Medved, J., Varga, R., Bahadur, N., 525 Ananthakrishnan, H., and X. Liu, "A Data Model for Network 526 Topologies", draft-ietf-i2rs-yang-network-topo-20 (work in 527 progress), December 2017. 529 [I-D.ietf-i2rs-yang-l3-topology] 530 Clemm, A., Medved, J., Varga, R., Liu, X., 531 Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model 532 for Layer 3 Topologies", draft-ietf-i2rs-yang- 533 l3-topology-16 (work in progress), December 2017. 535 [I-D.ietf-teas-yang-te-topo] 536 Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and 537 O. Dios, "YANG Data Model for Traffic Engineering (TE) 538 Topologies", draft-ietf-teas-yang-te-topo-13 (work in 539 progress), October 2017. 541 [I-D.ietf-spring-sr-yang] 542 Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG 543 Data Model for Segment Routing", draft-ietf-spring-sr- 544 yang-08 (work in progress), December 2017. 546 Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations 548 The YANG module ietf-sr-topology defined in this document is designed 549 to be used in conjunction with implementations that support the 550 Network Management Datastore Architecture (NMDA) defined in 551 [I-D.ietf-netmod-revised-datastores]. In order to allow 552 implementations to use the model even in cases when NMDA is not 553 supported, the following companion module, ietf-sr-topology-state, is 554 defined as state model, which mirrors the module ietf-sr-topology 555 defined earlier in this document. However, all data nodes in the 556 companion module are non-configurable, to represent the applied 557 configuration or the derived operational states. 559 The companion module, ietf-sr-topology-state, is redundant and SHOULD 560 NOT be supported by implementations that support NMDA. 562 As the structure of the companion module mirrors that of the 563 coorespinding NMDA model, the YANG tree of the companion module is 564 not depicted separately. 566 A.1. SR Topology State Module 568 file "ietf-sr-topology-state@2017-10-30.yang" 569 module ietf-sr-topology-state { 570 yang-version 1.1; 571 namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology-state"; 572 prefix "srt-s"; 574 import ietf-sr-topology { 575 prefix "srt"; 576 } 577 import ietf-network-state { 578 prefix "nw-s"; 579 } 580 import ietf-network-topology-state { 581 prefix "nt-s"; 582 } 583 import ietf-l3-unicast-topology-state { 584 prefix "l3t-s"; 585 } 586 import ietf-segment-routing-common { 587 prefix "sr-cmn"; 588 } 590 organization "TBD"; 591 contact "TBD"; 592 description "L3 TE Topology model"; 593 revision 2017-10-30 { 594 description "Initial revision"; 595 reference "TBD"; 596 } 598 augment "/nw-s:networks/nw-s:network/nw-s:network-types/" 599 + "l3t-s:l3-unicast-topology" { 600 description 601 "Defines the SR topology type."; 602 uses srt:sr-topology-type; 603 } 605 augment "/nw-s:networks/nw-s:network/" 606 + "l3t-s:l3-topology-attributes" { 607 when "../nw-s:network-types/l3t-s:l3-unicast-topology/sr" { 608 description "Augment only for SR topology."; 609 } 610 description "Augment topology configuration"; 611 uses srt:sr-topology-attributes; 612 } 614 augment "/nw-s:networks/nw-s:network/nw-s:node/" 615 + "l3t-s:l3-node-attributes" { 616 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/sr" { 617 description "Augment only for SR topology."; 618 } 619 description "Augment node configuration."; 620 uses srt:sr-node-attributes; 621 } 623 augment "/nw-s:networks/nw-s:network/nw-s:node/" 624 + "l3t-s:l3-node-attributes/l3t-s:prefix" { 625 when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/sr" { 626 description "Augment only for SR topology."; 627 } 628 description "Augment node prefix."; 629 uses srt:sr-node-prefix-attributes; 630 } 632 augment "/nw-s:networks/nw-s:network/nw-s:node/" 633 + "nt-s:termination-point/" 634 + "l3t-s:l3-termination-point-attributes" { 635 when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/" 636 + "sr" { 637 description "Augment only for SR topology."; 638 } 639 description "Augment termination point configuration"; 640 uses srt:sr-tp-attributes; 642 } 644 augment "/nw-s:networks/nw-s:network/nt-s:link/" 645 + "l3t-s:l3-link-attributes" { 646 when "../../nw-s:network-types/l3t-s:l3-unicast-topology/sr" { 647 description "Augment only for SR topology."; 648 } 649 description "Augment link configuration."; 650 uses srt:sr-link-attributes; 651 } 653 grouping sr-topology-attributes { 654 description "SR topology scope attributes."; 655 container sr { 656 description 657 "Containing SR attributes."; 658 uses sr-cmn:srgb-cfg; 659 } // sr 660 } // sr-topology-attributes 661 } 662 664 Authors' Addresses 666 Xufeng Liu 667 Jabil 668 8281 Greensboro Drive, Suite 200 669 McLean VA 22102 670 USA 672 EMail: Xufeng_Liu@jabil.com 674 Igor Bryskin 675 Huawei Technologies 677 EMail: Igor.Bryskin@huawei.com 679 Vishnu Pavan Beeram 680 Juniper Networks 682 EMail: vbeeram@juniper.net 683 Tarek Saad 684 Cisco Systems Inc 686 EMail: tsaad@cisco.com 688 Himanshu Shah 689 Ciena 691 EMail: hshah@ciena.com 693 Stephane Litkowski 694 Orange Business Service 696 EMail: stephane.litkowski@orange.com