idnits 2.17.1 draft-ietf-l1vpn-ospf-auto-discovery-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 437. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 448. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 455. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 461. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. 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 an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The abstract seems to contain references ([L1VPN-FRMWK], [L1VPN-BM]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2006) is 6403 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) -- Possible downref: Normative reference to a draft: ref. 'L1VPN-BM' == Outdated reference: A later version (-05) exists of draft-ietf-l1vpn-framework-00 -- No information found for draft-ouldbrahim-l1vpn-bgp-auto-discovery- - is the name correct? Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Igor Bryskin (ADVA Optical Networking) 2 Category: Standards Track Lou Berger (LabN Consulting, LLC) 3 Expiration Date: April 2007 5 October 2006 7 OSPF Based L1VPN Auto-Discovery 9 draft-ietf-l1vpn-ospf-auto-discovery-01.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/1id-abstracts.html 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html 34 Abstract 36 This document defines an OSPF based layer-1 VPN auto-discovery 37 mechanism. This mechanism enables PEs using the OSPF IGP to 38 dynamically learn about existence of each other, and attributes of 39 currently configured CE-PE links and their associations with L1VPNs. 40 This document builds on [L1VPN-FRMWK] and provides an auto-discovery 41 mechanism as discussed in [L1VPN-BM]. 43 Contents 45 1 Terminology ............................................... 3 46 2 Introduction .............................................. 4 47 3 L1VPN LSA and its TLVs .................................... 5 48 3.1 L1VPN LSA ................................................. 5 49 3.2 L1VPN INFO TLV ............................................ 6 50 4 L1VPN LSA Advertising and Processing ...................... 7 51 4.1 Discussion and Example .................................... 7 52 5 Backward compatibility .................................... 8 53 6 Security Considerations ................................... 9 54 7 Intellectual Property Statement ........................... 9 55 8 Acknowledgement ........................................... 10 56 9 References ................................................ 10 57 9.1 Normative References ...................................... 10 58 9.2 Informative References .................................... 10 59 10 Authors' Addresses ........................................ 11 60 11 Full Copyright Statement .................................. 11 61 12 Intellectual Property ..................................... 11 62 Conventions used in this document 64 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 65 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 66 document are to be interpreted as described in [RFC2119]. 68 1. Terminology 70 The reader of this document should be familiar with the terms used in 71 [L1VPN-FRMWK] and [L1VPN-BM]. In particular the following terms: 73 L1VPN - Layer One Virtual Private Network 75 CE - Customer (edge) network element directly connected to the 76 Provider network (terminates one or more links to one or 77 more PEs); it is also connected to one or more Cs and/or 78 other CEs 80 C - Customer network element that is not connected to the 81 Provider network but is connected to one or more other Cs 82 and/or CEs 84 PE - Provider (edge) network element directly connected to one or 85 more Customer networks (terminates one or more links to one 86 or more CEs associated with the same or different L1VPNs); 87 it is also connected to one or more Ps and/or other PEs 89 P - Provider (core) network element that is not directly 90 connected to any of Customer networks; P is connected to one 91 or more other Ps and/or PEs 93 LSDB - Link State Database: a data structure supported by an IGP 94 speaker 96 PIT - Port Information Table 98 CPI - Customer Port Identifier 100 PPI - Provider Port Identifier 102 2. Introduction 104 The framework for Layer 1 VPNs is described in [L1VPN-FRMWK]. Basic 105 mode operation is further defined in [L1VPN-BM]. [L1VPN-BM] document 106 identifies the information that is necessary to map customer 107 information (ports identifiers) to provider information 108 (identifiers). It also states that this mapping information may be 109 provided via provisioning or via an auto-discovery mechanism. This 110 document provides such an auto-discovery mechanism using the OSPF 111 IGP. Figure 1 shows the L1VPN basic service being supported using 112 OSPF based L1VPN auto-discovery. See [L1VPN-BGP] for a parallel 113 L1VPN auto-discovery that uses BGP. The IGP approach described in 114 this document is particularly useful in networks where BGP is not 115 typically used. 117 PE PE 118 +---------+ +--------------+ 119 +--------+ | +------+| | +----------+ | +--------+ 120 | VPN-A | | |VPN-A || | | VPN-A | | | VPN-A | 121 | CE1 |--| |PIT || OSPF LSAs | | PIT | |-| CE2 | 122 +--------+ | | ||<----------->| | | | +--------+ 123 | +------+| Distribution| +----------+ | 124 | | | | 125 +--------+ | +------+| | +----------+ | +--------+ 126 | VPN-B | | |VPN-B || -------- | | VPN-B | | | VPN-B | 127 | CE1 |--| |PIT ||-( GMPLS )--| | PIT | |-| CE2 | 128 +--------+ | | || (Backbone ) | | | | +--------+ 129 | +------+| --------- | +----------+ | 130 | | | | 131 +--------+ | +-----+ | | +----------+ | +--------+ 132 | VPN-C | | |VPN-C| | | | VPN-C | | | VPN-C | 133 | CE1 |--| |PIT | | | | PIT | |-| CE2 | 134 +--------+ | | | | | | | | +--------+ 135 | +-----+ | | +----------+ | 136 +---------+ +--------------+ 138 Figure 1: OSPF Auto-Discovery for L1VPNs 140 The approach used in this document to provide OSPF based L1VPN auto- 141 discovery uses an Opaque LSA of a new Opaque Type (referred as a 142 L1VPN LSA). 144 There is a TLV type defined for use within a L1VPN LSA. The TLV, 145 which is referred to as L1VPN Info TLV, is used to propagate tuple and VPIN ID mappings. 148 3. L1VPN LSA and its TLVs 150 This section defines the L1VPN LSA and its TLVs. 152 3.1. L1VPN LSA 154 The format of a L1VPN LSA is as follows: 156 0 1 2 3 157 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 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 | LS age | Options | LS Type | 160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 | Opaque Type | Opaque ID | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | Advertising Router | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | LS Sequence Number | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | LS checksum | Length | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 | L1VPN Info TLV | 170 | ... | 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 172 | TE Link TLV | 173 | ... | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 176 LS age 177 As defined in [RFC2328] 179 Options 180 As defined in [RFC2328]. 182 LS Type 183 This field MUST be set to 11. 185 Opaque Type 186 The value of this field MUST be set to TBA (by IANA). 188 Opaque ID 189 As defined in [RFC2370] 191 Advertising Router 192 As defined in [RFC2328]. 194 LS Sequence Number 195 As defined in [RFC2328]. 197 LS checksum 198 As defined in [RFC2328]. 200 Length 201 As defined in [RFC2328]. 203 L1VPN Info TLV 204 A single TLV, as defined in section 3.2 206 TE Link TLV 207 A single TE Link TLV (as defined in [RFC3630] and [RFC4203]) 208 MAY be included in a L1VPN LSA 210 3.2. L1VPN INFO TLV 212 The following TLV is introduced: 214 Name: L1VPN IPv4 Info 215 Type: 1 216 Length: Variable 218 0 1 2 3 219 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 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | L1VPN TLV length | L1VPN TLV Type | 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 | L1VPN Globally unique identifier | 224 | | 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 226 | PE TE Address | 227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 | ... | 229 | L1VPN Auto-Discovery Information | 230 | ... | 231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 TLV length 234 The length of the TLV in bytes, including the 4 bytes of 235 the TLV header. 237 L1VPN TLV Type 238 The type of the TLV. 240 L1VPN Globally unique identifier 241 As defined in [L1VPN-BM]. 243 PE TE Address 244 Valid PE TE address: either TE Router ID specified in the 245 Router Address TLV or local numbered TE link ID specified in 246 the Local interface IP address sub-TLV of the TE Link TLV of the 247 TE LSA originated by the PE 249 L1VPN Auto-discovery information 250 As defined in [L1VPN-BM]. 252 4. L1VPN LSA Advertising and Processing 254 PEs advertise local tuples in L1VPN LSAs containing L1VPN 255 Info TLVs. Each PE MUST originate a separate L1VPN LSA with AS 256 flooding scope for each local CE-PE link. The LSA MUST be originated 257 once on the PE restart and every time when there is a change in the 258 PIT entry associated with a local CE-PE link. The LSA MUST include a 259 single L1VPN Info TLV and MAY include a single TE Link TLV as per 260 [RFC3630] and [RFC4203]. 262 L1VPN LSAs are flooded to all PEs within the AS according to 263 [RFC2370] or [2370BIS]. Every time a PE receives a new, removed or 264 modified such LSA, the PE MUST check whether it maintains a PIT 265 associated with the L1VPN specified in the L1VPN Globally unique 266 identifier field. If this is the case (the appropriate PIT will be 267 found if one or more local CE-PE links that belong to the L1VPN are 268 configured), the PE SHOULD add, remove or modify the PIT entry 269 associated with each of the advertised CE-PE links accordingly. Thus, 270 in the steady mode all PEs associated with a particular L1VPN 271 maintain identical local PITs for the L1VPN. 273 4.1. Discussion and Example 275 The L1VPN auto-discovery mechanism described in this document does 276 not prevent a PE from applying any local policy with respect to PIT 277 management. For example, it should be possible to configure permanent 278 (static) PIT entries, blocking information carried in L1VPN LSAs that 279 are advertised by some remote PEs from making it to the PITs and so 280 forth. 282 The reason why it is required that the value specified in the PE TE 283 Address field of the L1VPN Info TLV matches a valid PE TE Router ID 284 or numbered TE Link ID is to ensure that CEs attached to this PE 285 could be resolved to the PE as it is known to the Traffic Engineering 286 Database (TED) and hence TE paths towards the CEs across the Provider 287 domain could be computed. 289 Let us consider example presented on Figure 2. 291 CE11 CE13 292 | | 293 CE22---PE1--------P------PE2 294 | | 295 CE15 PE3 296 | 297 CE24 299 Figure 2: Single area configuration 301 Let us assume that PE1 is connected to CE11 and CE15 in L1VPN1 and to 302 CE22 in L1VPN2; PE2 is connected to CE13 in L1VPN1; PE3 is connected 303 to CE24 in L1VPN2. In this configuration PE1 manages two PITs: PIT1 304 for L1VPN1 and PIT2 for L1VPN2; PE2 manages only PIT1, and PE3 305 manages only PIT2. PE1 originates three L1VPN LSAs, each containing a 306 L1VPN Info TLV advertising links PE1-CE11, PE1-CE22 and PE1-CE15 307 respectively. PE2 originates a single L1VPN LSA for link PE2-CE13 and 308 PE3 originates a single L1VPN LSA for link PE3-CE24. In the steady 309 mode PIT1 on PE1 and PE3 will contain information on links PE1-CE11, 310 PE1-CE15 and PE2-CE13; PIT2 on PE1 and PE2 will contain entries for 311 links PE1-CE22 and PE3-CE24. Thus, all PEs will learn about all 312 remote PE-CE links for all L1VPNs supported by PEs. 314 Note that P in this configuration does not have links connecting it 315 to any of L1VPNs. It neither originates L1VPN LSAs nor maintains any 316 PITs. However, it does participate in the flooding of all of the 317 L1VPN LSA and hence maintains the LSAs in its LSDB. This is a cause 318 for scalability concerns and could prove to be problematic on large 319 networks. 321 5. Backward compatibility 323 Neither the TLV nor the LSA introduced in this document present any 324 interoperability issues. OSPF speakers that do not support L1VPN 325 auto-discovery application (Ps for example) just participate in the 326 L1VPN LSAs flooding process but should ignore the LSAs contents. 328 6. Security Considerations 330 The solution presented in this document describes how PEs dynamically 331 learn L1VPN specific information. Mechanisms to deliver the VPN 332 membership information to CEs are explicitly out of scope of this 333 document. Therefore, no new security issues are raised in this 334 document. 336 7. Intellectual Property Statement 338 The IETF takes no position regarding the validity or scope of any 339 Intellectual Property Rights or other rights that might be claimed to 340 pertain to the implementation or use of the technology described in 341 this document or the extent to which any license under such rights 342 might or might not be available; nor does it represent that it has 343 made any independent effort to identify any such rights. Information 344 on the procedures with respect to rights in RFC documents can be 345 found in BCP 78 and BCP 79. 347 Copies of IPR disclosures made to the IETF Secretariat and any 348 assurances of licenses to be made available, or the result of an 349 attempt made to obtain a general license or permission for the use of 350 such proprietary rights by implementers or users of this 351 specification can be obtained from the IETF on-line IPR repository at 352 http://www.ietf.org/ipr. 354 The IETF invites any interested party to bring to its attention any 355 copyrights, patents or patent applications, or other proprietary 356 rights that may cover technology that may be required to implement 357 this standard. Please address the information to the IETF at ietf- 358 ipr@ietf.org. 360 Internet-Drafts are working documents of the Internet Engineering 361 Task Force (IETF), its areas, and its working groups. Note that other 362 groups may also distribute working documents as Internet- Drafts. 364 Internet-Drafts are draft documents valid for a maximum of six 365 months and may be updated, replaced, or obsoleted by other documents 366 at any time. It is inappropriate to use Internet-Drafts as reference 367 material or to cite them other than as "work in progress". 369 8. Acknowledgement 371 We would like to thank Adrian Farrel for his useful comments. 373 9. References 375 9.1. Normative References 377 [RFC2119] Bradner, S., "Key words for use in RFCs to indicate 378 requirements levels", RFC 2119, March 1997. 380 [RFC2328] Moy, J., " OSPF Version 2 ", RFC 2328, April 1998. 382 [RFC2370] Coltun, R., " The OSPF Opaque LSA Option ", RFC 2730, 383 July 1998. 385 [RFC3630] Ktaz, D., Kompela, K., Yeung. D.., " Traffic Engineering 386 (TE) Extensions to OSPF Version 2", RFC 3630, September 387 2003. 389 [RFC4203] Kompela, K., Rekhter, Y. " OSPF Extensions in Support of 390 Generalized Multi-Protocol Label Switching (GMPLS)", RFC 391 4203, October 2005. 393 [L1VPN-BM] Fedyk, D., Rekhter, Y. (Eds.), "Layer 1 VPN Basic 394 Mode", draft-fedyk-l1vpn-basic-mode-01.txt, January 395 2006, work in progress. 397 9.2. Informative References 399 [2370BIS] Berger, L., Bryskin, I., Zinin, A., "The OSPF Opaque LSA 400 Option", work in progress, draft-berger-ospf-rfc2370bis, 401 October, 2006. 403 [L1VPN-FRMWK] Tomonori Takeda, et al., " Framework and 404 Requirements for Layer 1 Virtual Private Networks", 405 draft-ietf-l1vpn-framework-00.txt, August 2005, work 406 in progress 408 [L1VPN-BGP] Ould-Brahim H., Fedyk D., Rekhter, Y., "BGP-based Auto- 409 Discovery for L1VPNs ", work in progress, 410 draft-ouldbrahim-l1vpn-bgp-auto-discovery- 412 10. Authors' Addresses 414 Igor Bryskin 415 ADVA Optical Networking Inc 416 7926 Jones Branch Drive 417 Suite 615 418 McLean, VA - 22102 419 Email: ibryskin@advaoptical.com 421 Lou Berger 422 LabN Consulting, LLC 423 Email: lberger@labn.net 425 11. Full Copyright Statement 427 Copyright (C) The Internet Society (2006). This document is subject 428 to the rights, licenses and restrictions contained in BCP 78, and 429 except as set forth therein, the authors retain all their rights. 431 This document and the information contained herein are provided on an 432 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 433 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 434 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 435 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 436 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 437 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 439 12. Intellectual Property 441 The IETF takes no position regarding the validity or scope of any 442 Intellectual Property Rights or other rights that might be claimed to 443 pertain to the implementation or use of the technology described in 444 this document or the extent to which any license under such rights 445 might or might not be available; nor does it represent that it has 446 made any independent effort to identify any such rights. Information 447 on the procedures with respect to rights in RFC documents can be 448 found in BCP 78 and BCP 79. 450 Copies of IPR disclosures made to the IETF Secretariat and any 451 assurances of licenses to be made available, or the result of an 452 attempt made to obtain a general license or permission for the use of 453 such proprietary rights by implementers or users of this 454 specification can be obtained from the IETF on-line IPR repository at 455 http://www.ietf.org/ipr. 457 The IETF invites any interested party to bring to its attention any 458 copyrights, patents or patent applications, or other proprietary 459 rights that may cover technology that may be required to implement 460 this standard. Please address the information to the IETF at ietf- 461 ipr@ietf.org.