idnits 2.17.1 draft-chen-l3vpn-mt-extensions-to-mpls-l3vpn-mib-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 : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 9, 2012) is 4302 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: 'RFC2119' is mentioned on line 100, but not defined == Missing Reference: 'RFC2685' is mentioned on line 238, but not defined == Missing Reference: 'RFC4362' is mentioned on line 414, but not defined == Missing Reference: 'RFC 4362' is mentioned on line 421, but not defined == Missing Reference: 'RFC 3031' is mentioned on line 430, but not defined == Missing Reference: 'RFC 4364' is mentioned on line 430, but not defined == Unused Reference: 'RFC4382' is defined on line 442, but no explicit reference was found in the text == Unused Reference: 'I-D.li-mpls-ldp-mt-mib' is defined on line 454, but no explicit reference was found in the text == Outdated reference: A later version (-12) exists of draft-ietf-mpls-ldp-multi-topology-03 == Outdated reference: A later version (-06) exists of draft-li-mpls-ldp-mt-mib-03 Summary: 1 error (**), 0 flaws (~~), 12 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 L3VPN Working Group Emily Chen 3 Internet-Draft Huawei Technology 4 Intended status: Standards Track Chen Li 5 Expires: January 10, 2013 Lianyuan Li 6 Peng Fan 7 China Mobile 8 July 9, 2012 10 Multi Topology Extensions To MPLS/BGP Layer 3 Virtual Private Network 11 Management Information Base 12 draft-chen-l3vpn-mt-extensions-to-mpls-l3vpn-mib-00.txt 14 Abstract 16 This document defines extensions to Multiprotocol Label Switching 17 (MPLS) Layer-3 Virtual Private Networks (L3VPN) Management 18 Information Base (MIB), to support Multi Topology routing. It 19 describes managed objects to configure and/or monitor Multi Topology 20 based Multiprotocol Label Switching Layer-3 Virtual Private Networks 21 on a Multiprotocol Label Switching (MPLS) Label Switched Router (LSR) 22 supporting this feature. 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 January 10, 2013. 41 Copyright Notice 43 Copyright (c) 2012 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 This document may contain material from IETF Documents or IETF 57 Contributions published or made publicly available before November 58 10, 2008. The person(s) controlling the copyright in some of this 59 material may not have granted the IETF Trust the right to allow 60 modifications of such material outside the IETF Standards Process. 61 Without obtaining an adequate license from the person(s) controlling 62 the copyright in such materials, this document may not be modified 63 outside the IETF Standards Process, and derivative works of it may 64 not be created outside the IETF Standards Process, except to format 65 it for publication as an RFC or to translate it into languages other 66 than English. 68 Table of Contents 70 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 4. Extensions To MPLS-L3VPN-STD-MIB . . . . . . . . . . . . . . . 5 74 4.1. Example Of Setting UP MT Based MPLS L3VPN . . . . . . . . 5 75 4.2. New Definition of VRF Configuration Table . . . . . . . . 6 76 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 77 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 78 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 79 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 80 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 81 8.2. Informative References . . . . . . . . . . . . . . . . . . 12 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 84 1. Introduction 86 Multi Topology (MT) solution makes it possible to establish 87 Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) across 88 a specific, or set of, multiple topologies. By using these MT LSPs, 89 Layer-3 Virtual Private Networks (L3VPN) can benefit from the 90 advantages of Multi Topology, such as service separation, end-to-end 91 protection, simplified inter-AS deployment, etc. 93 The motivation of this document is to facilitate the configuration 94 and management of such MT based MPLS/BGP L3VPN. It defines 95 extensions to MPLS-L3VPN-STD-MIB to support MT features. 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in [RFC2119]. 101 2. Terminology 103 This document uses terminologies from the document describing the 104 MPLS architecture [RFC3031] and from the document describing MPLS 105 Layer-3 VPNs (L3VPN) [RFC4364], as well as the MPLS LDP Multi 106 Topology [I-D.ietf-mpls-ldp-multi-topology]. 108 Throughout this document, the use of the terms "Provider Edge (PE) 109 and Customer Edge (CE)" or "PE/CE" will be replaced by "PE" in all 110 cases except when a network device is a CE when used in the carrier's 111 carrier model. 113 3. Requirements 115 Within a Service Provider's MPLS backbone, besides default topology, 116 there might be some more topolgies with MT LSPs on them. Provider 117 Edge (PE) routers should associate the VPN service(s) to a specific 118 topology. Multiple VPN application can share a same topology, or use 119 their respective ones. 121 +-------+ +------+ +-------+ 122 | App 1 | * * * * * * | P1 | * * * * * * | App 1 | 123 +-------+ * +------+ * +-------+ 124 \ * * / 125 \ * * / 126 \ * * / 127 +-------+ +-------+ +-------+ +-------+ 128 | App 2 |------| PE 1 |----------------------| PE 2 |------| App 2 | 129 +-------+ +-------+ +-------+ +-------+ 130 / ' ' \ 131 / ' ' \ 132 / ' ' \ 133 +-------+ ' +------+ ' +-------+ 134 | App 3 | ' ' ' ' ' ' | P2 | ' ' ' ' ' ' | App 3 | 135 +-------+ +------+ +-------+ 137 MT Based MPLS/BGP L3VPN Example 139 Figure 1 141 In the figure above, the paths between PE1 and PE2 can be separated 142 into several topologies. In this example, PE1--PE2 belongs to 143 default topology, while PE1--P1--PE2 belongs to RED topology, and 144 PE1--P2--PE2 belongs to BLUE topology. And the applications over 145 this MT based MPLS backbone can be associated to diferrent VPNs, or 146 diferrent services (such as IPv4 and IPv6 services) in a same VPN. 147 Users are allowed to map each application to a specific topology by 148 configuration, for instance, App1 maps to the LSPs in the RED 149 topology, App2 maps to the LSPs in the default topology, App3 maps to 150 the LSPs in the BLUE topology. Then the VPN performance can be 151 monitored per topology. 153 4. Extensions To MPLS-L3VPN-STD-MIB 155 4.1. Example Of Setting UP MT Based MPLS L3VPN 157 [RFC4364] demonstrates MPLS-L3VPN-STD-MIB to setup MPLS L3VPN. In 158 order to setup MT based MPLS L3VPN, this document adds one object to 159 mplsL3VpnVrfTable to specify the topology used in MPLS backbone. 161 In mplsL3VpnVrfTable: 162 { 163 mplsL3VpnVrfName = "RED", 164 mplsL3VpnVrfDescription = "Intranet of Company ABC", 165 mplsL3VpnVrfMplsMtId = "50", -- Unsigned32 166 mplsL3VpnVrfRD = "100:1", -- octet string 167 mplsL3VpnVrfRowStatus = createAndGo(4) 168 } 170 4.2. New Definition of VRF Configuration Table 172 mplsL3VpnVrfTable OBJECT-TYPE 173 SYNTAX SEQUENCE OF MplsL3VpnVrfEntry 174 MAX-ACCESS not-accessible 175 STATUS current 176 DESCRIPTION 177 "This table specifies per-interface MPLS L3VPN 178 VRF Table capability and associated information. 179 Entries in this table define VRF routing instances 180 associated with MPLS/VPN interfaces. Note that 181 multiple interfaces can belong to the same VRF 182 instance. The collection of all VRF instances 183 comprises an actual VPN." 184 ::= { mplsL3VpnConf 2 } 186 mplsL3VpnVrfEntry OBJECT-TYPE 187 SYNTAX MplsL3VpnVrfEntry 188 MAX-ACCESS not-accessible 189 STATUS current 190 DESCRIPTION 191 "An entry in this table is created by an LSR for 192 every VRF capable of supporting MPLS L3VPN. The 193 indexing provides an ordering of VRFs per-VPN 194 interface." 195 INDEX { mplsL3VpnVrfName } 196 ::= { mplsL3VpnVrfTable 1 } 197 MplsL3VpnVrfEntry ::= SEQUENCE { 198 mplsL3VpnVrfName MplsL3VpnName, 199 mplsL3VpnVrfVpnId VPNIdOrZero, 200 mplsL3VpnVrfDescription SnmpAdminString, 201 mplsL3VpnVrfMplsMtId Unsigned32, 202 mplsL3VpnVrfRD MplsL3VpnRouteDistinguisher, 203 mplsL3VpnVrfCreationTime TimeStamp, 204 mplsL3VpnVrfOperStatus INTEGER, 205 mplsL3VpnVrfActiveInterfaces Gauge32, 206 mplsL3VpnVrfAssociatedInterfaces Unsigned32, 207 mplsL3VpnVrfConfMidRteThresh Unsigned32, 208 mplsL3VpnVrfConfHighRteThresh Unsigned32, 209 mplsL3VpnVrfConfMaxRoutes Unsigned32, 210 mplsL3VpnVrfConfLastChanged TimeStamp, 211 mplsL3VpnVrfConfRowStatus RowStatus, 212 mplsL3VpnVrfConfAdminStatus INTEGER, 213 mplsL3VpnVrfConfStorageType StorageType 214 } 216 mplsL3VpnVrfName OBJECT-TYPE 217 SYNTAX MplsL3VpnName 218 MAX-ACCESS not-accessible 219 STATUS current 220 DESCRIPTION 221 "The human-readable name of this VPN. This MAY 222 be equivalent to the [RFC2685] VPN-ID, but may 223 also vary. If it is set to the VPN ID, it MUST 224 be equivalent to the value of mplsL3VpnVrfVpnId. 225 It is strongly recommended that all sites supporting 226 VRFs that are part of the same VPN use the same 227 naming convention for VRFs as well as the same VPN 228 ID." 229 REFERENCE 230 "[RFC2685]" 231 ::= { mplsL3VpnVrfEntry 1 } 233 mplsL3VpnVrfVpnId OBJECT-TYPE 234 SYNTAX VPNIdOrZero 235 MAX-ACCESS read-create 236 STATUS current 237 DESCRIPTION 238 "The VPN ID as specified in [RFC2685]. If a VPN ID 239 has not been specified for this VRF, then this 240 variable SHOULD be set to a zero-length OCTET 241 STRING." 242 ::= { mplsL3VpnVrfEntry 2 } 244 mplsL3VpnVrfDescription OBJECT-TYPE 245 SYNTAX SnmpAdminString 246 MAX-ACCESS read-create 247 STATUS current 248 DESCRIPTION 249 "The human-readable description of this VRF." 250 DEFVAL { "" } 251 ::= { mplsL3VpnVrfEntry 3 } 253 mplsL3VpnVrfMplsMtId OBJECT-TYPE 254 SYNTAX Unsigned32 (0..65535) 255 MAX-ACCESS read-create 256 STATUS current 257 DESCRIPTION 258 "The Multi Topology Identifier used by the MPLS 259 backbone of this VRF." 260 DEFVAL { "0" } 261 REFERENCE 262 "draft-ietf-mpls-ldp-multi-topology, LDP Extensions 263 for Multi Topology Routing, Section on 264 Multi-Topology ID." 265 ::= { mplsL3VpnVrfEntry 4 } 267 mplsL3VpnVrfRD OBJECT-TYPE 268 SYNTAX MplsL3VpnRouteDistinguisher 269 MAX-ACCESS read-create 270 STATUS current 271 DESCRIPTION 272 "The route distinguisher for this VRF." 273 DEFVAL { "" } 274 ::= { mplsL3VpnVrfEntry 5 } 276 mplsL3VpnVrfCreationTime OBJECT-TYPE 277 SYNTAX TimeStamp 278 MAX-ACCESS read-only 279 STATUS current 280 DESCRIPTION 281 "The time at which this VRF entry was created." 282 ::= { mplsL3VpnVrfEntry 6 } 284 mplsL3VpnVrfOperStatus OBJECT-TYPE 285 SYNTAX INTEGER { up (1), 286 down (2) 287 } 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "Denotes whether or not a VRF is operational. A VRF is 292 up(1) when there is at least one interface associated 293 with the VRF whose ifOperStatus is up(1). A VRF is 294 down(2) when: 295 a. There does not exist at least one interface whose 296 ifOperStatus is up(1). 297 b. There are no interfaces associated with the VRF." 298 ::= { mplsL3VpnVrfEntry 7 } 300 mplsL3VpnVrfActiveInterfaces OBJECT-TYPE 301 SYNTAX Gauge32 302 MAX-ACCESS read-only 303 STATUS current 304 DESCRIPTION 305 "Total number of interfaces connected to this VRF with 306 ifOperStatus = up(1). 308 This value should increase when an interface is associated 309 with the corresponding VRF and its corresponding ifOperStatus 310 is equal to up(1). If an interface is associated whose 311 ifOperStatus is not up(1), then the value is not incremented 312 until such time as it transitions to this state. 314 This value should be decremented when an interface is 315 disassociated with a VRF or the corresponding ifOperStatus 316 transitions out of the up(1) state to any other state. 317 " 318 ::= { mplsL3VpnVrfEntry 8 } 320 mplsL3VpnVrfAssociatedInterfaces OBJECT-TYPE 321 SYNTAX Unsigned32 322 MAX-ACCESS read-only 323 STATUS current 324 DESCRIPTION 325 "Total number of interfaces connected to this VRF 326 (independent of ifOperStatus type)." 327 ::= { mplsL3VpnVrfEntry 9 } 329 mplsL3VpnVrfConfMidRteThresh OBJECT-TYPE 330 SYNTAX Unsigned32 331 MAX-ACCESS read-create 332 STATUS current 333 DESCRIPTION 334 "Denotes mid-level water marker for the number 335 of routes that this VRF may hold." 336 DEFVAL { 0 } 337 ::= { mplsL3VpnVrfEntry 10 } 339 mplsL3VpnVrfConfHighRteThresh OBJECT-TYPE 340 SYNTAX Unsigned32 341 MAX-ACCESS read-create 342 STATUS current 343 DESCRIPTION 344 "Denotes high-level water marker for the number of 345 routes that this VRF may hold." 346 DEFVAL { 0 } 347 ::= { mplsL3VpnVrfEntry 11 } 349 mplsL3VpnVrfConfMaxRoutes OBJECT-TYPE 350 SYNTAX Unsigned32 351 MAX-ACCESS read-create 352 STATUS current 353 DESCRIPTION 354 "Denotes maximum number of routes that this VRF is 355 configured to hold. This value MUST be less than or 356 equal to mplsL3VpnVrfConfMaxPossRts unless it is set 357 to 0." 358 DEFVAL { 0 } 359 ::= { mplsL3VpnVrfEntry 12 } 361 mplsL3VpnVrfConfLastChanged OBJECT-TYPE 362 SYNTAX TimeStamp 363 MAX-ACCESS read-only 364 STATUS current 365 DESCRIPTION 366 "The value of sysUpTime at the time of the last 367 change of this table entry, which includes changes of 368 VRF parameters defined in this table or addition or 369 deletion of interfaces associated with this VRF." 370 ::= { mplsL3VpnVrfEntry 13 } 372 mplsL3VpnVrfConfRowStatus OBJECT-TYPE 373 SYNTAX RowStatus 374 MAX-ACCESS read-create 375 STATUS current 376 DESCRIPTION 377 "This variable is used to create, modify, and/or 378 delete a row in this table. 379 When a row in this table is in active(1) state, no 380 objects in that row can be modified except 381 mplsL3VpnVrfConfAdminStatus, mplsL3VpnVrfConfRowStatus, 382 and mplsL3VpnVrfConfStorageType." 383 ::= { mplsL3VpnVrfEntry 14 } 385 mplsL3VpnVrfConfAdminStatus OBJECT-TYPE 386 SYNTAX INTEGER { 387 up(1), -- ready to pass packets 388 down(2), -- can't pass packets 389 testing(3) -- in some test mode 390 } 391 MAX-ACCESS read-create 392 STATUS current 393 DESCRIPTION 394 "Indicates the desired operational status of this 395 VRF." 396 ::= { mplsL3VpnVrfEntry 15 } 398 mplsL3VpnVrfConfStorageType OBJECT-TYPE 399 SYNTAX StorageType 400 MAX-ACCESS read-create 401 STATUS current 402 DESCRIPTION 403 "The storage type for this VPN VRF entry. 404 Conceptual rows having the value 'permanent' 405 need not allow write access to any columnar 406 objects in the row." 407 REFERENCE 408 "See RFC2579." 409 DEFVAL { volatile } 410 ::= { mplsL3VpnVrfEntry 16 } 412 5. Acknowledgements 414 We would like to thank authors of [RFC4362] and the authors of 415 draft-ietf-mpls-ldp-multi-topology from which some text of this 416 document has been inspired. 418 6. IANA Considerations 420 The IANA has assigned { mplsStdMIB 11 } to the MPLS-L3VPN-STD-MIB 421 module specified in [RFC 4362]. This document only makes extensions 422 to the MPLS-L3VPN-STD-MIB module, there is no further IANA 423 requirement. 425 7. Security Considerations 427 No specific security issues with the proposed solutions are known. 428 The proposed extension in this document does not introduce any new 429 security considerations beyond that already apply to the base MPLS/ 430 BGP L3VPN specification as [RFC 3031] and [RFC 4364]. 432 8. References 434 8.1. Normative References 436 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 437 Label Switching Architecture", RFC 3031, January 2001. 439 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 440 Networks (VPNs)", RFC 4364, February 2006. 442 [RFC4382] Nadeau, T. and H. van der Linde, "MPLS/BGP Layer 3 Virtual 443 Private Network (VPN) Management Information Base", 444 RFC 4382, February 2006. 446 8.2. Informative References 448 [I-D.ietf-mpls-ldp-multi-topology] 449 Zhao, Q., Fang, L., Zhou, C., Li, L., and N. So, "LDP 450 Extensions for Multi Topology Routing", 451 draft-ietf-mpls-ldp-multi-topology-03 (work in progress), 452 March 2012. 454 [I-D.li-mpls-ldp-mt-mib] 455 Li, C., Li, L., Huang, L., Chen, E., and Q. Zhao, 456 "Management Information Base for MPLS LDP Multi Topology", 457 draft-li-mpls-ldp-mt-mib-03 (work in progress), June 2012. 459 Authors' Addresses 461 Emily Chen 462 Huawei Technology 463 2330 Central Expressway 464 Santa Clara, CA 95050 465 US 467 Email: emily.chenying@huawei.com 469 Chen Li 470 China Mobile 471 32 Xuanwumen West Street, Xicheng District 472 Beijing 100053 473 P.R. China 475 Email: lichenyj@chinamobile.com 477 Lianyuan Li 478 China Mobile 479 32 Xuanwumen West Street, Xicheng District 480 Beijing 100053 481 P.R. China 483 Email: lichenyj@chinamobile.com 484 Peng Fan 485 China Mobile 486 32 Xuanwumen West Street, Xicheng District 487 Beijing 100053 488 P.R. China 490 Email: lichenyj@chinamobile.com