idnits 2.17.1 draft-rao-ccamp-otn-mlnmrn-ospfte-ext-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 : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 144: '...r upper SC and Encoding type MUST have...' RFC 2119 keyword, line 153: '...an OTN interface MUST include the Laye...' RFC 2119 keyword, line 155: '... node MUST look at the LayerID sub-T...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 1, 2012) is 4257 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) == Unused Reference: 'RFC5212' is defined on line 169, but no explicit reference was found in the text == Unused Reference: 'RFC6001' is defined on line 173, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 5212 -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-OTN-OSPF' Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Khuzema Pithewan 3 Intended Status: Standard Track Rajan Rao 4 Infinera 5 Expires: February 2, 2013 August 1, 2012 7 OSPF-TE extensions for MLNMRN based on OTN 8 draft-rao-ccamp-otn-mlnmrn-ospfte-ext-00.txt 10 Abstract 12 This document specifies OSPF extensions for multi-layer/multi-region 13 where one of the regions is OTN. 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as 23 Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 Copyright and License Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. OTN Layer Identification . . . . . . . . . . . . . . . . . . . 3 55 3. Interface Adjustment Capability Extensions for OTN . . . . . . 4 56 4 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 5 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 58 6 Security Considerations . . . . . . . . . . . . . . . . . . . . 5 59 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 60 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 62 1 Introduction 64 This document specifies the OSPF extensions required to work in 65 multi-region networks involving OTN. The specification is based on 66 the requirement as specified in RFC 5212. As per the said RFC, ISCD 67 characterizes the information associated to one or more network 68 layers. Same RFC also says that the information about the adjustment 69 capabilities of the nodes in the network allow the path computation 70 process to select an end-to-end multi-layer or multi- region path 71 that includes links with different switching capabilities joined by 72 LSRs that can adapt (i.e., adjust) the signal between the links. By 73 inference, information about the adjustment capabilities should be 74 able to identify a layer in ISCD, if ISCD specifies more than one 75 layer. 77 RFC6001 specifies how to advertise adjustment capabilities between 78 two switching regions. IACD definition has provision to extend it for 79 a specific technology through Adjustment Capability Specific 80 information (ACSI) field, if required. ACSI field can be used to 81 identify a layer in the multi-layer ISCD. OTN being defined as multi- 82 layer ISCD, the corresponding IACD needs to be extended to be able to 83 carry layer identification so as to enable multi-layer/multi-region 84 path computation. 86 2. OTN Layer Identification 88 [GMPLS-OTN-OSPF] defines attributes that identifies a layer in multi- 89 layer OTN ISCD. These attributes are part of Bandwidth sub-TLV in 90 Switch capability specific information of ISCD. These attributes are 91 reproduced here for completeness sake. 93 * Signal Type: Layer for which bandwidth is being advertised. 94 * Hierarchy : also called as multiplexing branch that specifies all 95 the layers between server layer and signal type. 96 * TSG : Time Slot Granularity 98 3. Interface Adjustment Capability Extensions for OTN 100 RFC6001 defines IACD sub-TLV as follows. Please refer to the RFC for 101 definition of individual fields of the sub-TLV. 102 0 1 2 3 103 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 104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 105 | Lower SC | Lower Encoding| Upper SC | Upper Encoding| 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | Max LSP Bandwidth at priority 0 | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | Max LSP Bandwidth at priority 1 | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 | Max LSP Bandwidth at priority 2 | 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | Max LSP Bandwidth at priority 3 | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | Max LSP Bandwidth at priority 4 | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | Max LSP Bandwidth at priority 5 | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | Max LSP Bandwidth at priority 6 | 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | Max LSP Bandwidth at priority 7 | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Adjustment Capability-specific information | 124 | (variable) | 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 Adjustment Capability-specific information abbreviated as ACSI 128 henceforth for OTN G.709v3 carries LayerID Sub-TLV which is defined 129 as follows 131 0 1 2 3 132 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 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Type = 1 (LayerID TLV) | Length | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Signal type | Num of stages |TSG | Res | Stage#1 | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Stage#2 | ... | Stage#N | Padding | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 The definition & meaning of fields used in the above sub-TLV is same 142 as in bandwidth sub-TLV of ISCD as defined in [GMPLS-OTN-OSPF]. This 143 LayerID sub-TLV is applicable only when one of the regions is OTN, 144 which means either lower or upper SC and Encoding type MUST have 145 Switch Cap as OTN-TDM and encoding type as G.709 ODUk. The 8 146 priorities of the BW as defined in main IACD structure, is adjustment 147 capability between the two regions where one of the region is 148 identifies by LayerID sub-TLV. 150 4 Procedure 152 A node advertising IACD for the bandwidth between a non-OTN interface 153 and an OTN interface MUST include the Layer ID TLV as part of ACSI as 154 defined above. For multi-region path computation, the path computing 155 node MUST look at the LayerID sub-TLV (in ACSI part of IACD) if 156 lower/upper SC and encoding type is OTN-TDM and G.709 ODUk 157 respectively to identify the layer in OTN ISCD. 159 5 IANA Considerations 161 TBD 163 6 Security Considerations 165 TBD 167 7 References 169 [RFC5212] K. Shiomoto, Papadimitriou, D.,JL. Le Roux, Vigoureux, M., 170 Brungard, D., "Requirements for GMPLS-Based Multi-Layer 171 and Multi-Region Networks (MLN/ MRN)",RFC 5212, July 2008. 173 [RFC6001] Papadimitriou, D., Vigoureux, M., Shiomoto, K., Brungard, 174 D., and JL. Le Roux, "Generalized MPLS (GMPLS) Protocol 175 Extensions for Multi-Layer and Multi-Region Networks 176 (MLN/MRN)", RFC 6001, October 2010. 178 [GMPLS-OTN-OSPF] Traffic Engineering Extensions to OSPF for 179 Generalized MPLS (GMPLS) 181 8 Authors' Addresses 183 Khuzema Pithewan 184 Infinera 185 140 Caspian Ct., Sunnyvale, CA 94089 186 Email: kpithewan@infinera.com 188 Rajan Rao 189 Infinera 190 140 Caspian Ct., Sunnyvale, CA 94089 191 Email: rrao@infinera.com