idnits 2.17.1 draft-ceccarelli-ccamp-gmpls-ospf-g709-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 39 characters in excess of 72. ** The abstract seems to contain references ([G709-V3]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == 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 (July 9, 2010) is 5038 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: 'G709-V3' is mentioned on line 107, but not defined == Missing Reference: 'WSON-Frame' is mentioned on line 126, but not defined == Missing Reference: 'RFC 3630' is mentioned on line 413, but not defined == Missing Reference: 'RFC 4203' is mentioned on line 416, but not defined == Missing Reference: 'RFC3471' is mentioned on line 211, but not defined == Missing Reference: 'RFC4328' is mentioned on line 211, but not defined == Unused Reference: 'RFC2119' is defined on line 652, but no explicit reference was found in the text == Unused Reference: 'RFC2370' is defined on line 658, but no explicit reference was found in the text == Unused Reference: 'RFC4201' is defined on line 665, but no explicit reference was found in the text == Unused Reference: 'G.709' is defined on line 685, but no explicit reference was found in the text == Unused Reference: 'G.709-v3' is defined on line 689, but no explicit reference was found in the text == Unused Reference: 'Gsup43' is defined on line 693, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MLN-EXT' == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-g709-framework-02 ** Downref: Normative reference to an Informational draft: draft-ietf-ccamp-gmpls-g709-framework (ref. 'OTN-FWK') -- No information found for draft-bddg-ccamp-otn-g709-info-model - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'OTN-INFO' ** Downref: Normative reference to an Experimental RFC: RFC 2154 ** Obsolete normative reference: RFC 2370 (Obsoleted by RFC 5250) ** Downref: Normative reference to an Informational RFC: RFC 5339 Summary: 6 errors (**), 0 flaws (~~), 15 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group D. Ceccarelli 3 Internet-Draft D. Caviglia 4 Intended status: Standards Track Ericsson 5 Expires: January 10, 2011 F. Zhang 6 D. Li 7 Huawei Technologies 8 Y. Xu 9 CATR 10 S. Belotti 11 P. Grandi 12 Alcatel-Lucent 13 July 9, 2010 15 Traffic Engineering Extensions to OSPF for Generalized MPLS (GMPLS) 16 Control of Evolving G.709 OTN Networks 17 draft-ceccarelli-ccamp-gmpls-ospf-g709-02 19 Abstract 21 The recent revision of ITU-T Recommendation G.709 [G709-V3] has 22 introduced new fixed and flexible ODU containers, enabling optimized 23 support for an increasingly abundant service mix. 25 This document describes OSPF routing protocol extensions to support 26 Generalized MPLS (GMPLS) control of all currently defined ODU 27 containers, in support of both sub-lambda and lambda level routing 28 granularity. 30 Status of this Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at http://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on January 10, 2011. 47 Copyright Notice 48 Copyright (c) 2010 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. OSPF Extensions . . . . . . . . . . . . . . . . . . . . . . . 4 65 2.1. OTN Interface Switching Capability Descriptor . . . . . . 4 66 2.2. Example using OTN-ISCD . . . . . . . . . . . . . . . . . . 9 67 3. Compatibility Considerations . . . . . . . . . . . . . . . . . 16 68 4. Security Considerations . . . . . . . . . . . . . . . . . . . 16 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 70 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 16 71 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 72 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 73 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17 74 8.2. Informative References . . . . . . . . . . . . . . . . . . 18 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 77 1. Introduction 79 An Opaque OSPF (Open Shortest Path First) LSA (Link State 80 Advertisements) carrying application-specific information can be 81 generated and advertised to other nodes following the flooding 82 procedures defined in [RFC5250]. Three types of opaque LSA are 83 defined, i.e. type 9 - link-local flooding scope, type 10 - area- 84 local flooding scope, type 11 - AS flooding scope. 86 Traffic Engineering (TE) LSA using type 10 opaque LSA is defined in 87 [RFC3630] for TE purposes. This type of LSA is composed of a 88 standard LSA header and a payload including one top-level TLV (Type/ 89 Length/Value triplet) and possible several nested sub-TLVs. 90 [RFC3630] defines two top-level TLVs: Router Address TLV and Link 91 TLV; and nine possible sub-TLVs for the Link TLV, used to carry link 92 related TE information. 94 The Link type sub-TLVs are enhanced by [RFC4203] in order to support 95 GMPLS networks and related specific link information. 97 In GMPLS networks each node generates TE LSAs to advertise its TE 98 information and capabilities (link-specific or node-specific), 99 through the network. The TE information carried in the LSAs are 100 collected by the other nodes of the network and stored into their 101 local Traffic Engineering Databases (TED). 103 In GMPLS enabled G.709 Optical Transport Networks (OTNs), routing 104 serves as the foundation for automatically establishing ODUk 105 connections through GMPLS RSVP-TE signaling. 107 G.709 OTN [G709-V3] includes new fixed and flexible ODU containers, 108 two types of Tributary Slots (i.e., 1.25Gbps and 2.5Gbps), and 109 supports various multiplexing relationships (e.g., ODUj multiplexed 110 into ODUk (j ::= < Link Type > < Link ID > < Link 408 Local/Remote Identifiers > < OTN ISCD > 410 o Link Type sub-TLV: Defined in [RFC 3630], G.709 digital links are 411 always type 1 - Point-to-point link. 413 o Link ID sub-TLV: Defined in [RFC 3630], for point-to-point link, 414 indicates the remote router ID. 416 o Link Local/Remote Identifiers sub-TLV: Defined in [RFC 4203], 417 indicates the local link ID and the remote link ID. 419 o OTN ISCD sub-TLV: Defined in this document, carries the 420 characteristic of this G.709 digital TE link. 422 Just after the creation of the TE Link comprising the two component 423 links, the OTN ISCD sub-TLV would be advertised as follows: 425 0 1 2 3 426 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 428 | SC = TDM | Enc = G709 | Reserved | 429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 |1|0|0|0|1|0|0|1|T1.25| | Reserved | 431 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 432 | SType=ODU0(0) |0| 8 TS @ P0 | 433 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 434 | SType=ODU0(0) |0| 8 TS @ P3 | 435 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 436 | SType=ODU0(0) |0| 8 TS @ P7 | 437 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 438 | SType=ODU1(1) |0| 8+32 = 40 TS @ P0 | 439 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 440 | SType=ODU1(1) |0| 8+32 = 40 TS @ P3 | 441 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 442 | SType=ODU1(1) |0| 8+32 = 40 TS @ P7 | 443 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 444 | SType=ODU3(22)|0| 32 TS @ P0 | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 | SType=ODU3(22)|0| 32 TS @ P3 | 447 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 448 | SType=ODU3(22)|0| 32 TS @ P7 | 449 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 450 | SType=ODU2(21)|0| 8 TS @ P0 | 451 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 452 | SType=ODU2(21)|0| 8 TS @ P3 | 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 | SType=ODU2(21)|0| 8 TS @ P7 | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 | SType=ODUflex |0| 8+32 = 40 TS @ P0 | 457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 458 | SType=ODUflex |0| 8+32 = 40 TS @ P3 | 459 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 460 | SType=ODUflex |0| 8+32 = 40 TS @ P7 | 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | SType=ODUflex|1| 32 TS @ P0 | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 | SType=ODUflex|1| 32 TS @ P3 | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | SType=ODUflex|1| 32 TS @ P7 | 467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 Figure 4: Example - OTN-ISCD sub-TLV(to) 471 Suppose that at time t1 an ODUflex LSP is created allocating 35 Gbps 472 at priority 3. The OTN ISCD sub-TLV will be modified as follows: 474 0 1 2 3 475 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 476 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 477 | SC = TDM | Enc = G709 | Reserved | 478 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 479 |1|0|0|0|1|0|0|1|T1.25| | Reserved | 480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 481 | SType=ODU0(0) |0| 8 TS @ P0 | 482 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 483 | SType=ODU0(0) |0| 8 TS @ P3 | 484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 485 | SType=ODU0(0) |0| 8 TS @ P7 | 486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 487 | SType=ODU1(1) |0| 8+32 = 40 TS @ P0 | 488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 489 | SType=ODU1(1) |0| 8+4 = 12 TS @ P3 | 490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 491 | SType=ODU1(1) |0| 8+4 = 12 TS @ P7 | 492 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 493 | SType=ODU3(22)|0| 32 TS @ P0 | 494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 495 | SType=ODU3(22)|0| 0 TS @ P3 | 496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 497 | SType=ODU3(22)|0| 0 TS @ P7 | 498 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 499 | SType=ODU2(21)|0| 8 TS @ P0 | 500 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 501 | SType=ODU2(21)|0| 8 TS @ P3 | 502 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 503 | SType=ODU2(21)|0| 8 TS @ P7 | 504 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 505 | SType=ODUflex |0| 8+32 = 40 TS @ P0 | 506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 507 | SType=ODUflex |0| 8+4 = 12 TS @ P3 | 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 | SType=ODUflex |0| 8+4 = 12 TS @ P7 | 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 | SType=ODUflex |1| 32 TS @ P0 | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | SType=ODUflex |1| 8 TS @ P3 | 514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 515 | SType=ODUflex |1| 8 TS @ P7 | 516 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 518 Figure 5: Example - OTN-ISCD sub-TLV(t1) 520 The last example shows how the prehemption is managed. In 521 particular, if at time t2 a new 15 GBps ODUflex LSP with priority 0 522 is created, the LSP with priority 3 is pre-empted and its resources 523 (or part of them) are allocated to the LSP with higher priority. The 524 OTN ISCD sub-TLV is updated accordingly to Figure 6: 526 0 1 2 3 527 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 529 | SC = TDM | Enc = G709 | Reserved | 530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 531 |1|0|0|0|1|0|0|1|T1.25| | Reserved | 532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 533 | SType=ODU0 |0| 8 TS @ P0 | 534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 535 | SType=ODU0 |0| 8 TS @ P3 | 536 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 537 | SType=ODU0 |0| 8 TS @ P7 | 538 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 539 | SType=ODU1 |0| 8+20 = 28 TS @ P0 | 540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 541 | SType=ODU1 |0| 8+20 = 28 TS @ P3 | 542 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 543 | SType=ODU1 |0| 8+20 = 28 TS @ P7 | 544 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 545 | SType=OTU3 |0| 0 TS @ P0 | 546 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 547 | SType=OTU3 |0| 0 TS @ P3 | 548 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 549 | SType=OTU3 |0| 0 TS @ P7 | 550 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 551 | SType=OTU2 |0| 8 TS @ P0 | 552 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 553 | SType=OTU2 |0| 8 TS @ P3 | 554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 555 | SType=OTU2 |0| 8 TS @ P7 | 556 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 557 | SType=ODUflex|0| 8+20 = 28 TS @ P0 | 558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 559 | SType=ODUflex|0| 8+20 = 28 TS @ P3 | 560 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 561 | SType=ODUflex|0| 8+20 = 28 TS @ P7 | 562 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 563 | SType=ODUflex|1| 20 TS @ P0 | 564 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 565 | SType=ODUflex|1| 20 TS @ P3 | 566 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 567 | SType=ODUflex|1| 20 TS @ P7 | 568 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 570 Figure 6: Example - OTN-ISCD (t2) 572 3. Compatibility Considerations 574 The legacy nodes that do not implement the extensions defined in this 575 document are able, per [RFC3630] section 4, to ignore the LSA 576 containing an OTN ISCD sub-TLV. They will continue to flood the LSA 577 to other neighbors, but will not use the information carried in this 578 LSA. 580 4. Security Considerations 582 This document specifies the contents of Opaque LSAs in OSPFv2. As 583 Opaque LSAs are not used for SPF computation or normal routing, the 584 extensions specified here have no direct effect on IP routing. 585 Tampering with GMPLS TE LSAs may have an effect on the underlying 586 transport (optical and/or SONET-SDH) network. [RFC3630] suggests 587 mechanisms such as [RFC2154] to protect the transmission of this 588 information, and those or other mechanisms should be used to secure 589 and/or authenticate the information carried in the Opaque LSAs. 591 5. IANA Considerations 593 TBD 595 6. Contributors 597 Xiaobing Zi 599 Huawei Technologies 601 F3-5-B R&D Center, Huawei Base 603 Bantian, Longgang District 605 Shenzhen 518129 P.R.China 607 Email: zixiaobing@huawei.com 609 Francesco Fondelli 611 Ericsson 613 Via Negrone 1/A 614 Genova - 16145 616 Email: francesco.fondelli@ericsson.com 618 Marco Corsi 620 Altran Italia 622 Via Negrone 1/A 624 Genova - 16145 626 EMail: marco.corsi@altran.it 628 7. Acknowledgements 630 The authors would like to thank Eric Gray for his precious comments 631 and advices. 633 8. References 635 8.1. Normative References 637 [MLN-EXT] D.Papadimitriou, M.Vigoureux, K.Shiomoto, D.Brungard, J.Le 638 Roux, "Generalized Multi-Protocol Extensions for Multi- 639 Layer and Multi-Region Network (MLN/MRN)", February 2010. 641 [OTN-FWK] F.Zhang, D.Li, H.LI, S.Belotti, "Framework for GMPLS and 642 PCE Control of G.709 Optical Transport networks, work in 643 progress draft-ietf-ccamp-gmpls-g709-framework-02", 644 July 2010. 646 [OTN-INFO] 647 S.Belotti, P.Grandi, D.Ceccarelli, D.Caviglia, F.Zhang, 648 D.Li, "Information model for G.709 Optical Transport 649 Networks (OTN), work in progress 650 draft-bddg-ccamp-otn-g709-info-model-01", July 2010. 652 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 653 Requirement Levels", BCP 14, RFC 2119, March 1997. 655 [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with 656 Digital Signatures", RFC 2154, June 1997. 658 [RFC2370] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, 659 July 1998. 661 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 662 (TE) Extensions to OSPF Version 2", RFC 3630, 663 September 2003. 665 [RFC4201] Kompella, K., Rekhter, Y., and L. Berger, "Link Bundling 666 in MPLS Traffic Engineering (TE)", RFC 4201, October 2005. 668 [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in 669 Support of Generalized Multi-Protocol Label Switching 670 (GMPLS)", RFC 4202, October 2005. 672 [RFC4203] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 673 of Generalized Multi-Protocol Label Switching (GMPLS)", 674 RFC 4203, October 2005. 676 [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The 677 OSPF Opaque LSA Option", RFC 5250, July 2008. 679 [RFC5339] Le Roux, JL. and D. Papadimitriou, "Evaluation of Existing 680 GMPLS Protocols against Multi-Layer and Multi-Region 681 Networks (MLN/MRN)", RFC 5339, September 2008. 683 8.2. Informative References 685 [G.709] ITU-T, "Interface for the Optical Transport Network 686 (OTN)", G.709 Recommendation (and Amendment 1), 687 February 2001. 689 [G.709-v3] 690 ITU-T, "Draft revised G.709, version 3", consented 691 by ITU-T on Oct 2009. 693 [Gsup43] ITU-T, "Proposed revision of G.sup43 (for agreement)", 694 December 2008. 696 Authors' Addresses 698 Daniele Ceccarelli 699 Ericsson 700 Via A. Negrone 1/A 701 Genova - Sestri Ponente 702 Italy 704 Email: daniele.ceccarelli@ericsson.com 706 Diego Caviglia 707 Ericsson 708 Via A. Negrone 1/A 709 Genova - Sestri Ponente 710 Italy 712 Email: diego.caviglia@ericsson.com 714 Fatai Zhang 715 Huawei Technologies 716 F3-5-B R&D Center, Huawei Base 717 Shenzhen 518129 P.R.China Bantian, Longgang District 718 Phone: +86-755-28972912 720 Email: zhangfatai@huawei.com 722 Dan Li 723 Huawei Technologies 724 F3-5-B R&D Center, Huawei Base 725 Shenzhen 518129 P.R.China Bantian, Longgang District 726 Phone: +86-755-28973237 728 Email: danli@huawei.com 730 Yunbin Xu 731 CATR 732 11 Yue Tan Nan Jie 733 Beijing 734 P.R.China 736 Email: xuyunbin@mail.ritt.com.cn 737 Sergio Belotti 738 Alcatel-Lucent 739 Via Trento, 30 740 Vimercate 741 Italy 743 Email: sergio.belotti@alcatel-lucent.com 745 Pietro Vittorio Grandi 746 Alcatel-Lucent 747 Via Trento, 30 748 Vimercate 749 Italy 751 Email: pietro_vittorio.grandi@alcatel-lucent.com