idnits 2.17.1 draft-zzhang-l2l3-vpn-mcast-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: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 10 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 7 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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (January 07, 2013) is 4127 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: 'RFC3418' is defined on line 339, but no explicit reference was found in the text == Unused Reference: 'RFC6513' is defined on line 363, but no explicit reference was found in the text == Unused Reference: 'RFC6514' is defined on line 367, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-l2vpn-vpls-mib' is defined on line 377, but no explicit reference was found in the text == Outdated reference: A later version (-16) exists of draft-ietf-l2vpn-vpls-mcast-11 == Outdated reference: A later version (-15) exists of draft-ietf-l2vpn-vpls-mib-07 Summary: 1 error (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 L3 VPN Working Group J. Zhang 3 Internet-Draft Juniper Networks, Inc. 4 Intended status: Standards Track January 07, 2013 5 Expires: July 11, 2013 7 L2L3 VPN Multicast MIB 8 draft-zzhang-l2l3-vpn-mcast-mib-00 10 Abstract 12 This memo defines an experimental portion of the Management 13 Information Base for use with network management protocols in the 14 Internet community. 16 In particular, it describes managed objects common to both VPLS and 17 VPN Multicast. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on July 11, 2013. 36 Copyright Notice 38 Copyright (c) 2013 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. The Internet-Standard Management Framework . . . . . . . . . . 3 55 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 4. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . . 3 57 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 59 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 60 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 61 8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 62 8.2. Informative References . . . . . . . . . . . . . . . . . . 9 64 1. Introduction 66 Multicast in VPLS and VPN can be achieved by using provider tunnels 67 to deliver to all or a subset of PEs. The signaling of provider 68 tunnel choice is very similar for both VPLS and VPN multicast (aka 69 MVPN), and this memo describes managed objects common to both VPLS 70 Multicast [I-D.ietf-l2vpn-vpls-mcast] and MVPN [RFC 6513/6514]. 72 2. The Internet-Standard Management Framework 74 For a detailed overview of the documents that describe the current 75 Internet-Standard Management Framework, please refer to section 7 of 76 RFC 3410 [RFC3410]. 78 Managed objects are accessed via a virtual information store, termed 79 the Management Information Base or MIB. MIB objects are generally 80 accessed through the Simple Network Management Protocol (SNMP). 81 Objects in the MIB are defined using the mechanisms defined in the 82 Structure of Management Information (SMI). This memo specifies a MIB 83 module that is compliant to the SMIv2, which is described in STD 58, 84 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 85 [RFC2580]. 87 3. Conventions 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in RFC 2119 [RFC2119]. 93 4. Summary of MIB Module 95 L2L3-VPN-MCAST-MIB ontains a Textual Convention, 96 L2L3VpnMcastProviderTunnelType, and a 97 l2L3VpnMcastPmsiTunnelAttributeTable. Other MIB objects ([I-D.ietf- 98 l2vpn-vpls-mcast], [I-D. ietf-l3vpn-mvpn-mib]) may point to entries 99 in the l2L3VpnMcastPmsiTunnelAttributeTable. 101 5. Definitions 103 L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN 105 IMPORTS 106 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 107 experimental, Unsigned32 108 FROM SNMPv2-SMI 110 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 111 FROM SNMPv2-CONF 113 TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval 114 FROM SNMPv2-TC 116 SnmpAdminString 117 FROM SNMP-FRAMEWORK-MIB 119 InetAddress, InetAddressType 120 FROM INET-ADDRESS-MIB 122 MplsLabel 123 FROM MPLS-TC-STD-MIB 125 l2L3VpnMcastMIB MODULE-IDENTITY 126 LAST-UPDATED "201301071200Z" -- 07 January 2013 12:00:00 GMT 127 ORGANIZATION "IETF Layer-3 Virtual Private 128 Networks Working Group." 129 CONTACT-INFO 131 " 132 Comments and discussion to l3vpn@ietf.org 133 Jeffrey (Zhaohui) Zhang 134 Juniper Networks, Inc. 135 10 Technology Park Drive 136 Westford, MA 01886 137 USA 138 Email: zzhang@juniper.net 139 " 141 DESCRIPTION 142 "This MIB contains common managed object definitions for 143 multicast in Layer 2 and Layer 3 VPNs, defined by 144 [I-D.ietf-l2vpn-vpls-mcast] and RFC 6513/6514. 145 Copyright (C) The Internet Society (2013)." 147 -- Revision history. 149 REVISION "201301071200Z" -- 07 January 2013 12:00:00 GMT 150 DESCRIPTION 151 "Initial version of the draft." 152 ::= { experimental 99 } -- number to be assigned 154 -- Texual convention 156 L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION 157 SYNTAX INTEGER { unconfigured (0), 158 pim-asm (1), 159 pim-ssm (2), 160 pim-bidir (3), 161 rsvp-p2mp (4), 162 ldp-p2mp (5), 163 ingress-replication (6), 164 ldp-mp2mp (7) 165 } 166 STATUS current 167 DESCRIPTION 168 "Types of provider tunnels used for multicast in a l2/l3vpn." 169 REFERENCE 170 "[RFC6514]" 172 -- Top level components of this MIB. 173 -- tables, scalars 175 l2L3VpnMcastObjects OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 1 } 176 l2L3VpnMcastStates OBJECT IDENTIFIER ::= { l2L3VpnMcastObjects 1 } 178 -- Table of PMSI attributes 180 l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE 181 SYNTAX SEQUENCE OF L2L3vpnMcastPmsiTunnelAttributeEntry 182 MAX-ACCESS not-accessible 183 STATUS current 184 DESCRIPTION 185 "This table is for advertised/received PMSI attributes, 186 to be referred to by I-PMSI or S-PMSI table entries" 187 ::= {l2L3VpnMcastStates 1 } 189 l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE 190 SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry 191 MAX-ACCESS not-accessible 192 STATUS current 193 DESCRIPTION 194 "An entry in this table corresponds to an PMSI attribute 195 that is advertised/received on this router. 196 For BGP-based signaling (for I-PMSI via auto-discovery 197 procedure, or for S-PMSI via S-PMSI A-D routes), 198 they are just as signaled by BGP (RFC 6514 section 5, 199 'PMSI Tunnel attribute'). 200 For UDP-based S-PMSI signaling for PIM-MVPN, 201 they're derived from S-PMSI Join Message 202 (RFC 6513 section 7.4.2, 'UDP-based Protocol').. 204 Note that BGP-based signaling may be used for 205 PIM-MVPN as well." 206 INDEX { 207 l2L3VpnMcastPmsiTunnelAttributeFlags, 208 l2L3VpnMcastPmsiTunnelAttributeType, 209 l2L3VpnMcastPmsiTunnelAttributeLabel, 210 l2L3VpnMcastPmsiTunnelAttributeId 211 } 212 ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } 214 L2L3VpnMcastPmsiTunnelAttributeEntry ::= SEQUENCE { 215 l2L3VpnMcastPmsiTunnelAttributeFlags OCTET STRING, 216 l2L3VpnMcastPmsiTunnelAttributeType Unsigned32, 217 l2L3VpnMcastPmsiTunnelAttributeLabel MplsLabel, 218 l2L3VpnMcastPmsiTunnelAttributeId OCTET STRING, 219 l2L3VpnMcastPmsiTunnelPointer RowPointer, 220 l2L3VpnMcastPmsiTunnelIf RowPointer 221 } 223 l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE 224 SYNTAX OCTET STRING (SIZE (1)) 225 MAX-ACCESS not-accessible 226 STATUS current 227 DESCRIPTION 228 "For UDP-based S-PMSI signaling for PIM-MVPN, this is 0. 229 For BGP-based I/S-PMSI signaling, 230 per RFC 6514 section 5, 'PMSI Tunnel Attribute': 232 The Flags field has the following format: 234 0 1 2 3 4 5 6 7 235 +-+-+-+-+-+-+-+-+ 236 | reserved |L| 237 +-+-+-+-+-+-+-+-+ 239 This document defines the following flags: 241 + Leaf Information Required (L)" 242 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } 244 l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE 245 SYNTAX L2L3VpnMcastProviderTunnelType 246 MAX-ACCESS not-accessible 247 STATUS current 248 DESCRIPTION 249 "For BGP-based I/S-PMSI signaling for either PIM or BGP-MVPN, 250 per RFC 6514 section 5, 'PMSI Tunnel Attribute': 252 The Tunnel Type identifies the type of the tunneling technology used 253 to establish the PMSI tunnel. The type determines the syntax and 254 semantics of the Tunnel Identifier field. This document defines the 255 following Tunnel Types: 257 0 - No tunnel information present 258 1 - RSVP-TE P2MP LSP 259 2 - mLDP P2MP LSP 260 3 - PIM-SSM Tree 261 4 - PIM-SM Tree 262 5 - PIM-Bidir Tree 263 6 - Ingress Replication 264 7 - mLDP MP2MP LSP 266 For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 does not 267 specify if a PIM provider tunnel is SSM, SM or Bidir, 268 and an agent can use either type 3, 4, or 5 based on its 269 best knowledge." 270 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } 272 l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE 273 SYNTAX MplsLabel 274 MAX-ACCESS not-accessible 275 STATUS current 276 DESCRIPTION 277 "For BGP-based I/S-PMSI signaling, 278 per RFC 6514 section 5, 'PMSI Tunnel Attribute': 280 If the MPLS Label field is non-zero, then it contains an MPLS label 281 encoded as 3 octets, where the high-order 20 bits contain the label 282 value. Absence of MPLS Label is indicated by setting the MPLS Label 283 field to zero. 285 For UDP-based S-PMSI signaling for PIM-MVPN, this is not 286 applicable for now, as RFC 6513 does not specify 287 mpls encapsulation and tunnel aggregation with UDP-based 288 signaling." 289 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } 291 l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE 292 SYNTAX OCTET STRING ( SIZE (4|8|12) ) 293 MAX-ACCESS not-accessible 294 STATUS current 295 DESCRIPTION 296 "For BGP-based signaling, as defined in RFC 6514 section 5, 297 'PMSI Tunnel Attribute'. 299 For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 only 300 specifies the 'P-Group' address, and that is filled into 301 the first four octets of this field." 302 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } 304 l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE 305 SYNTAX RowPointer 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "If the tunnel exists in some MIB table, this is the row pointer 310 to it." 311 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } 313 l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE 314 SYNTAX RowPointer 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "If the tunnel has a corresponding interface, this is the 319 row pointer to the ifName table." 320 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } 322 END 324 6. Security Considerations 326 N/A 328 7. IANA Considerations 330 IANA is requested to root MIB objects in the MIB module contained in 331 this document under the transmission subtree. 333 . 335 8. References 337 8.1. Normative References 339 [RFC3418] Presuhn, R., "Management Information 340 Base (MIB) for the Simple Network 341 Management Protocol (SNMP)", STD 62, 342 RFC 3418, December 2002. 344 [RFC2119] Bradner, S., "Key words for use in RFCs 345 to Indicate Requirement Levels", BCP 14, 346 RFC 2119, March 1997. 348 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 349 and J. Schoenwaelder, Ed., "Structure of 350 Management Information Version 2 351 (SMIv2)", STD 58, RFC 2578, April 1999. 353 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 354 and J. Schoenwaelder, Ed., "Textual 355 Conventions for SMIv2", STD 58, 356 RFC 2579, April 1999. 358 [RFC2580] McCloghrie, K., Perkins, D., and J. 359 Schoenwaelder, "Conformance Statements 360 for SMIv2", STD 58, RFC 2580, 361 April 1999. 363 [RFC6513] Rosen, E. and R. Aggarwal, "Multicast in 364 MPLS/BGP IP VPNs", RFC 6513, 365 February 2012. 367 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and 368 Y. Rekhter, "BGP Encodings and 369 Procedures for Multicast in MPLS/BGP IP 370 VPNs", RFC 6514, February 2012. 372 [I-D.ietf-l2vpn-vpls-mcast] Aggarwal, R., Rekhter, Y., Kamite, Y., 373 and L. Fang, "Multicast in VPLS", 374 draft-ietf-l2vpn-vpls-mcast-11 (work in 375 progress), July 2012. 377 [I-D.ietf-l2vpn-vpls-mib] Nadeau, T., Koushik, K., and R. 378 Mediratta, "Virtual Private Lan Services 379 (VPLS) Management Information Base", 380 draft-ietf-l2vpn-vpls-mib-07 (work in 381 progress), September 2012. 383 8.2. Informative References 385 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 386 Stewart, "Introduction and Applicability 387 Statements for Internet-Standard 388 Management Framework", RFC 3410, 389 December 2002. 391 Author's Address 393 Zhaohui Zhang 394 Juniper Networks, Inc. 395 10 Technology Park Drive 396 Westford, MA 01886 397 USA 399 EMail: zzhang@juniper.net