idnits 2.17.1 draft-ceccarelli-ccamp-gmpls-ospf-g709-04.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 are 2 instances of too long lines in the document, the longest one being 4 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 date (October 22, 2010) is 4935 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 85, but not defined == Missing Reference: 'WSON-Frame' is mentioned on line 101, but not defined == Missing Reference: 'RFC 3630' is mentioned on line 120, but not defined == Missing Reference: 'RFC 4203' is mentioned on line 120, but not defined == Unused Reference: 'RFC2370' is defined on line 702, but no explicit reference was found in the text == Unused Reference: 'RFC4201' is defined on line 709, but no explicit reference was found in the text == Unused Reference: 'RFC4203' is defined on line 716, but no explicit reference was found in the text == Unused Reference: 'RFC5250' is defined on line 720, but no explicit reference was found in the text == Unused Reference: 'G.709' is defined on line 729, but no explicit reference was found in the text == Unused Reference: 'G.709-v3' is defined on line 733, but no explicit reference was found in the text == Unused Reference: 'Gsup43' is defined on line 737, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MLN-EXT' -- No information found for draft-bccgd-ccamp-gmpls-ospf-agnostic - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'OSPF-AGN' == 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 (~~), 13 warnings (==), 6 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: April 25, 2011 F. Zhang 6 D. Li 7 Huawei Technologies 8 Y. Xu 9 CATR 10 S. Belotti 11 P. Grandi 12 Alcatel-Lucent 13 J. Drake 14 Juniper 15 October 22, 2010 17 Traffic Engineering Extensions to OSPF for Generalized MPLS (GMPLS) 18 Control of Evolving G.709 OTN Networks 19 draft-ceccarelli-ccamp-gmpls-ospf-g709-04 21 Abstract 23 The recent revision of ITU-T Recommendation G.709 [G709-V3] has 24 introduced new fixed and flexible ODU containers, enabling optimized 25 support for an increasingly abundant service mix. 27 This document describes OSPF routing protocol extensions to support 28 Generalized MPLS (GMPLS) control of all currently defined ODU 29 containers, in support of both sub-lambda and lambda level routing 30 granularity. 32 Status of this Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on April 25, 2011. 49 Copyright Notice 51 Copyright (c) 2010 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. OSPF Extensions . . . . . . . . . . . . . . . . . . . . . . . 3 69 2.1. Bandwidth Accounting sub-TLV . . . . . . . . . . . . . . . 4 70 2.2. Example using BA sub-TLV . . . . . . . . . . . . . . . . . 7 71 2.3. Example of T and S bits usage . . . . . . . . . . . . . . 13 72 3. Scalability Improvement . . . . . . . . . . . . . . . . . . . 14 73 4. Compatibility Considerations . . . . . . . . . . . . . . . . . 14 74 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 75 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 76 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 77 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 78 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 79 9.1. Normative References . . . . . . . . . . . . . . . . . . . 16 80 9.2. Informative References . . . . . . . . . . . . . . . . . . 17 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 83 1. Introduction 85 G.709 OTN [G709-V3] includes new fixed and flexible ODU containers, 86 two types of Tributary Slots (i.e., 1.25Gbps and 2.5Gbps), and 87 supports various multiplexing relationships (e.g., ODUj multiplexed 88 into ODUk (j