idnits 2.17.1 draft-nadeau-l2tpext-pw-l2tpv3-mib-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, updated by RFC 4748 on line 951. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 925. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 934. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 940. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (June 2007) is 6159 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: 'CEPMIB' is mentioned on line 144, but not defined == Missing Reference: 'TBD' is mentioned on line 757, but not defined == Missing Reference: 'RFCxxxx' is mentioned on line 523, but not defined == Missing Reference: 'RFC4001' is mentioned on line 521, but not defined == Unused Reference: 'PW-IP' is defined on line 789, but no explicit reference was found in the text == Unused Reference: 'L2TPv3-MIB' is defined on line 792, but no explicit reference was found in the text == Unused Reference: 'RFC3031' is defined on line 822, but no explicit reference was found in the text == Unused Reference: 'RFC3036' is defined on line 826, but no explicit reference was found in the text == Unused Reference: 'RFC3811' is defined on line 829, but no explicit reference was found in the text == Unused Reference: 'RFC3812' is defined on line 835, but no explicit reference was found in the text == Unused Reference: 'RFC3813' is defined on line 840, but no explicit reference was found in the text == Unused Reference: 'RFC2434' is defined on line 851, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'PW-IP' -- Possible downref: Non-RFC (?) normative reference: ref. 'L2TPv3-MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' -- Possible downref: Non-RFC (?) normative reference: ref. 'PW-MIB' ** Obsolete normative reference: RFC 3036 (Obsoleted by RFC 5036) ** Obsolete normative reference: RFC 4447 (Obsoleted by RFC 8077) -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 3 errors (**), 0 flaws (~~), 15 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Thomas D. Nadeau (Ed.) 2 Expires: Dec 2007 A S Kiran Koushik (Ed.) 3 Cisco Systems, Inc. 5 June 2007 7 Pseudo Wire (PW) over L2TPv3 Management Information Base 9 draft-nadeau-l2tpext-pw-l2tpv3-mib-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 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other documents 25 at any time. It is inappropriate to use Internet-Drafts as 26 reference 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/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright Notice 36 Copyright (C) The IETF Trust (2007). 38 Abstract 40 This memo defines an experimental portion of the Management 41 Information Base (MIB) for use with network management protocols in 42 the Internet community. In particular, it describes a MIB module 43 for PW operation over Layer Two Tunneling Protocol (Version 3) 44 "L2TPV3". 46 Table of Contents 48 Abstract..........................................................1 49 1 Introduction.................................................2 51 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 53 2 Terminology..................................................3 54 3 The Internet-Standard Management Framework...................3 55 4 Feature Checklist............................................4 56 5 MIB module usage.............................................4 57 5.1 PW L2TPv3 MIB module usage...................................4 58 6 Object definitions...........................................6 59 7 Security Considerations.....................................24 60 8 IANA considerations.........................................25 61 9 References..................................................25 62 9.1 Normative references........................................25 63 9.2 Informative references......................................26 64 10 Author's Addresses..........................................27 65 11 Full Copyright Statement....................................28 66 12 Intellectual Property Notice................................28 68 1 Introduction 70 This document describes a model for managing pseudo wire services 71 for transmission over different flavors of L2TP tunnels and IP. The 72 general PW MIB module [PW-MIB] defines the parameters global to the 73 PW regardless of underlying PSN and emulated service. Indicating 74 PSN type of L2TP or IP in PW-MIB references this module. 76 This document describes the MIB objects that define pseudo wire 77 association to the L2TP PSN and IP PSN, in a way that is not 78 specific to the carried service. 80 Conventions used in this document 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 84 this document are to be interpreted as described in RFC-2119 85 [BCP14]. 87 2 Terminology 89 This document uses terminology from the document describing the PW 90 architecture [RFC3985], [RFC3916] and [RFC4447]. 92 "PSN Tunnel" is a general term indicating a virtual connection 93 between the two PWE3 edge devices. Each tunnel may potentially 94 carry multiple PWs inside. In the scope of this document, it is 95 L2TPv3 tunnel or IP. 97 In L2TPv3 PSN, a PW connection typically uses L2TPv3 session to 98 carry the traffic. 100 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 102 3 The Internet-Standard Management Framework 104 For a detailed overview of the documents that describe the current 105 Internet-Standard Management Framework, please refer to section 7 106 of RFC 3410 [RFC3410]. 108 Managed objects are accessed via a virtual information store, 109 termed the Management Information Base or MIB. MIB objects are 110 generally accessed through the Simple Network Management Protocol 111 (SNMP). Objects in the MIB are defined using the mechanisms defined 112 in the Structure of Management Information (SMI). This memo 113 specifies a MIB module that is compliant to the SMIv2, which is 114 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] 115 and STD 58, RFC 2580 [RFC2580]. 117 4 Feature Checklist 119 The PW L2TP and IP MIB modules are designed to satisfy the following 120 requirements and constraints: 122 - The MIB module supports both manually configured and signaled 123 PWs. 125 - The MIB module supports point-to-point PW connections. 127 - The MIB module enables the use of any emulated service. 129 5 MIB module usage 131 The MIB module structure for defining a PW service is composed from 132 three types of modules. 134 The first type is the PW MIB module [PW-MIB], which configures 135 general parameters of the PW that are common to all types of 136 emulated services and PSN. 138 The second type of modules is per PSN module. There is a separate 139 module for each type of PSN. This document defines the MIB module 140 for L2TPV3 and IP (PW-L2TPV3-MIB and PW-GEN-IP-MIB). 142 The third type of modules is service-specific module, which is 143 emulated signal type dependent. These modules are defined in other 144 documents; see for example [CEPMIB]. 146 [PWTC] defines some of the object types used in this module. 148 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 150 5.1 PW L2TP or IP MIB module usage 152 - The PW table (pwTable) in [PW-MIB] is used for all PW types 153 (ATM, FR, Ethernet, SONET, etc.). This table contains high level 154 generic parameters related to the PW creation. The operator or the 155 agent create a row for each PW. 157 - If the selected PSN type in pwTable is L2TP, the agent creates a 158 row in the L2TP specific parameters table (pwL2tpv3Table) in this 159 module, which contains L2TP specific parameters such as session 160 ids etc. 162 - The operator configures the association to the desired L2TPv3 163 tunnel (required for manually configured PWs) through the 164 pwL2tpMappingTable[TBD]. 166 - If the selected PSN type in pwTable is IP, the agent creates a 167 row in the IP specific parameters table (pwGenIpTable ) in this 168 module, which contains IP specific parameters such as address etc. 170 6 Object definitions 172 6.1 PW L2TPv3 MIB definitions: 174 PW-L2TPv3-DRAFT-00-MIB DEFINITIONS ::= BEGIN 176 IMPORTS 177 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, transmission 178 FROM SNMPv2-SMI -- [RFC2578] 180 MODULE-COMPLIANCE, OBJECT-GROUP 181 FROM SNMPv2-CONF -- [RFC2580] 183 StorageType, RowStatus 184 FROM SNMPv2-TC -- [RFC2579] 186 InterfaceIndexOrZero 187 FROM IF-MIB -- [RFC2863] 189 SnmpAdminString 190 FROM SNMP-FRAMEWORK-MIB 192 pwIndex -- [RFCxxxx] 193 -- RFC Editor: Please replace XXXX with RFC number & remove this 194 -- note. 195 FROM PW-STD-MIB 197 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 199 ; 201 pwL2tpv3Draft00MIB MODULE-IDENTITY 202 LAST-UPDATED "200610051200Z" -- 05 Oct 2006 12:00:00 GMT 203 ORGANIZATION "IETF L2TP Working Group" 204 CONTACT-INFO 205 "Layer Two Tunneling Protocol Extensions WG 206 Working Group Area: Internet 207 Working Group Name: l2tpext 208 General Discussion: l2tp@l2tp.net" 210 DESCRIPTION 211 "This MIB module complements the PW-STD-MIB module for PW 212 operation over L2TPv3. 214 Copyright (C) The Internet Society (2006). This version 215 of this MIB module is part of RFC yyyy; see the RFC 216 itself for full legal notices. 217 -- RFC Ed.: replace yyyy with actual RFC number & remove 218 -- this note 219 " 220 -- Revision history. 221 REVISION "200610051200Z" -- 05 Oct 2006 12:00:00 GMT 222 DESCRIPTION 223 " First published as RFCWXYZ. " 224 -- RFC Editor: Please replace WXYZ with correct # and remove this 225 -- note 227 ::= { transmission XXX } 228 -- RFC Editor: To be assigned by IANA. Please replace XXX 229 -- with the assigned value and remove this note. 231 -- Top-level components of this MIB. 233 -- Notifications 234 pwL2tpv3Notifications OBJECT IDENTIFIER 235 ::= { pwL2tpv3Draft00MIB 0 } 237 -- Tables, Scalars 238 pwL2tpv3Objects OBJECT IDENTIFIER 239 ::= { pwL2tpv3Draft00MIB 1 } 240 -- Conformance 241 pwL2tpv3Conformance OBJECT IDENTIFIER 242 ::= { pwL2tpv3Draft00MIB 2 } 244 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 246 -- PW L2TPv3 table 248 pwL2tpv3Table OBJECT-TYPE 249 SYNTAX SEQUENCE OF PwL2tpv3Entry 250 MAX-ACCESS not-accessible 251 STATUS current 252 DESCRIPTION 253 "This table controls L2TPv3 specific parameters when the PW is 254 going to be carried over L2TPv3." 255 ::= { pwL2tpv3Objects 1 } 257 pwL2tpv3Entry OBJECT-TYPE 258 SYNTAX PwL2tpv3Entry 259 MAX-ACCESS not-accessible 260 STATUS current 261 DESCRIPTION 262 "A row in this table represents parameters 263 specific to L2TPv3 for a pseudo wire (PW). 265 A row MUST be created automatically by the local agent 266 for every entry in the pwTable if the pwPsnType is 267 l2tp. Each entry is indexed by pwIndex, which uniquely 268 identifies a singular PW. 270 A row can also be created manually in this table. 271 " 272 INDEX { pwIndex } 274 -- Ed Note: Do we need to have pwL2tpv3CtrlCfgIfIndex as an index? 276 ::= { pwL2tpv3Table 1 } 278 PwL2tpv3Entry ::= SEQUENCE { 279 pwL2tpv3SessionCfgIfIndex InterfaceIndexOrZero, 280 pwL2tpv3CtrlCfgRouterID SnmpAdminString, 281 pwL2tpv3LocalSessionID Unsigned32, 282 pwL2tpv3RemoteSessionID Unsigned32, 283 pwL2tpv3OperType BITS, 284 pwL2tpv3DataSequencing INTEGER, 285 pwL2tpv3AddrResol INTEGER, 286 pwL2tpv3Mtu Unsigned32, 287 pwL2tpv3StorageType StorageType, 288 pwL2tpv3RowStatus RowStatus 289 } 291 pwL2tpv3SessionCfgIfIndex OBJECT-TYPE 292 SYNTAX InterfaceIndexOrZero 293 MAX-ACCESS read-create 295 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 297 STATUS current 298 DESCRIPTION 299 "The interface index for the corresponding L2TP 300 interface to which this PW session is associated. 302 The value of this object must correspond to the 303 value of l2tpv3SessionCfgIfIndex in the 304 l2tpv3SessionCfgTable." 305 ::= { pwL2tpv3Entry 1 } 307 pwL2tpv3CtrlCfgRouterID OBJECT-TYPE 308 SYNTAX SnmpAdminString 309 MAX-ACCESS read-create 310 STATUS current 311 DESCRIPTION 312 "The local router ID of this peer, as communicated via 313 the Router ID AVP for this control connection. 315 The value of this object corresponds to the 316 value of l2tpv3CtrlCfgRouterID in l2tpv3CtrlCfgTable." 317 ::= { pwL2tpv3Entry 2 } 319 pwL2tpv3LocalSessionID OBJECT-TYPE 320 SYNTAX Unsigned32 321 MAX-ACCESS read-create 322 STATUS current 323 DESCRIPTION 324 "The local L2TPv3 session id for this PW. The value 325 of this object corresponds to the 326 l2tpv3SessionCfgLocalID in l2tpv3SessionCfgTable." 327 ::= { pwL2tpv3Entry 3 } 329 pwL2tpv3RemoteSessionID OBJECT-TYPE 330 SYNTAX Unsigned32 331 MAX-ACCESS read-create 332 STATUS current 333 DESCRIPTION 334 "The remote L2TPv3 session id for this PW. The value 335 of this object corresponds to the 336 l2tpv3SessionCfgRemoteID in l2tpv3SessionCfgTable." 337 ::= { pwL2tpv3Entry 4 } 339 pwL2tpv3OperType OBJECT-TYPE 340 SYNTAX BITS { 341 ifToIf (0), 342 vcToVc (1), 344 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 346 ifToVc (2), 347 vcToIf (3) 348 } 349 MAX-ACCESS read-create 350 STATUS current 351 DESCRIPTION 352 "Set by the operator to indicate the operation type of this 353 PW. " 354 REFERENCE 355 "[PW-IP] section 6." 356 ::= { pwL2tpv3Entry 5 } 358 pwL2tpv3DataSequencing OBJECT-TYPE 359 SYNTAX INTEGER { 360 noSeq (0), 361 nonIpSeq (1), 362 allSeq (2) 363 } 365 MAX-ACCESS read-create 366 STATUS current 367 DESCRIPTION 368 "Set by the operator to indicate data sequencing. 369 noSeq(0) - No incoming data packets require sequencing. 370 nonIpSeq(0)- Only non-IP data packets require sequencing. 371 allSeq(2) - All incoming data packets require sequencing." 372 REFERENCE 373 "[PW-IP] section 4.2." 374 DEFVAL { allSeq } 375 ::= { pwL2tpv3Entry 6 } 377 pwL2tpv3AddrResol OBJECT-TYPE 378 SYNTAX INTEGER { 379 static (0), 380 dynamic (1) 381 } 382 MAX-ACCESS read-create 383 STATUS current 384 DESCRIPTION 385 "The value of this object indicates the point-to-point 386 address resolution mechanism for this PW." 387 REFERENCE 388 "[PW-IP] section 5." 389 DEFVAL { static } 390 ::= { pwL2tpv3Entry 7 } 392 pwL2tpv3Mtu OBJECT-TYPE 393 SYNTAX Unsigned32 395 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 397 MAX-ACCESS read-create 398 STATUS current 399 DESCRIPTION 400 "Set by the operator to indicate the PW MTU value to be 401 used on the PW." 402 REFERENCE 403 "[PW-IP] section 4.3." 404 DEFVAL { 1500 } 405 ::= { pwL2tpv3Entry 8 } 407 pwL2tpv3StorageType OBJECT-TYPE 408 SYNTAX StorageType 409 MAX-ACCESS read-create 410 STATUS current 411 DESCRIPTION 412 "This variable indicates the storage type for this row. 413 Conceptual rows having the value 'permanent' 414 need not allow write-access to any columnar 415 objects in the row." 416 DEFVAL { volatile } 417 ::= { pwL2tpv3Entry 9 } 419 pwL2tpv3RowStatus OBJECT-TYPE 420 SYNTAX RowStatus 421 MAX-ACCESS read-create 422 STATUS current 423 DESCRIPTION 424 "This variable is used to create, modify, and/or 425 delete a row in this table. When a row in this 426 table is in active(1) state, no objects in that row 427 can be modified by the agent except 428 pwL2tpv3RowStatus and pwL2tpv3StorageType." 429 ::= { pwL2tpv3Entry 10 } 431 -- End of PW L2TPv3 table 433 -- conformance information 435 pwL2tpv3Groups OBJECT IDENTIFIER ::= { pwL2tpv3Conformance 1 } 436 pwL2tpv3Compliances OBJECT IDENTIFIER ::= { pwL2tpv3Conformance 2 } 438 -- Compliance requirement for fully compliant implementations. 440 pwL2tpv3ModuleFullCompliance MODULE-COMPLIANCE 441 STATUS current 442 DESCRIPTION 444 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 446 "The compliance statement for agents that provide full 447 support for PW-L2TP MIB Module. Such devices can 448 then be monitored and also be configured using 449 this MIB module." 451 MODULE -- this module 452 MANDATORY-GROUPS { pwL2tpv3Group 453 } 455 ::= { pwL2tpv3Compliances 1 } 457 -- Compliance requirement for Read Only compliant implementations. 459 pwL2tpv3ModuleReadOnlyCompliance MODULE-COMPLIANCE 460 STATUS current 461 DESCRIPTION 462 "The compliance statement for agents that provide read 463 only support for PW-L2TP MIB Module. Such devices can 464 then be monitored but cannot be configured using this 465 MIB module." 467 MODULE -- this module 468 MANDATORY-GROUPS { pwL2tpv3Group 469 } 471 ::= { pwL2tpv3Compliances 2 } 473 -- Units of conformance. 475 pwL2tpv3Group OBJECT-GROUP 476 OBJECTS { 477 pwL2tpv3SessionCfgIfIndex, 478 pwL2tpv3CtrlCfgRouterID, 479 pwL2tpv3LocalSessionID, 480 pwL2tpv3RemoteSessionID, 481 pwL2tpv3OperType, 482 pwL2tpv3DataSequencing, 483 pwL2tpv3AddrResol, 484 pwL2tpv3Mtu, 485 pwL2tpv3StorageType, 486 pwL2tpv3RowStatus 487 } 488 STATUS current 489 DESCRIPTION 490 "Collection of objects needed for PW over L2TPv3 PSN 492 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 494 configuration." 495 ::= { pwL2tpv3Groups 1 } 497 END 499 6.1 PW GENERIC IP MIB definitions: 501 -- PW-GEN-IP-MIB module 502 PW-GEN-IP-DRAFT-00-MIB DEFINITIONS ::= BEGIN 504 IMPORTS 505 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, transmission 506 FROM SNMPv2-SMI -- [RFC2578] 508 MODULE-COMPLIANCE, OBJECT-GROUP 509 FROM SNMPv2-CONF -- [RFC2580] 511 StorageType, RowStatus 512 FROM SNMPv2-TC -- [RFC2579] 514 InterfaceIndexOrZero 515 FROM IF-MIB -- [RFC2863] 517 SnmpAdminString 518 FROM SNMP-FRAMEWORK-MIB 520 InetAddress, InetAddressType 521 FROM INET-ADDRESS-MIB -- [RFC4001] 523 pwIndex -- [RFCxxxx] 524 -- RFC Editor: Please replace XXXX with RFC number & remove this 525 -- note. 526 FROM PW-STD-MIB 528 ; 530 pwGenIpDraft00MIB MODULE-IDENTITY 531 LAST-UPDATED "200702011200Z" -- 01 Feb 2007 12:00:00 GMT 532 ORGANIZATION "IETF L2TP Working Group" 533 CONTACT-INFO 534 "Layer Two Tunneling Protocol Extensions WG 535 Working Group Area: Internet 536 Working Group Name: l2tpext 537 General Discussion: l2tp@l2tp.net" 539 DESCRIPTION 540 "This MIB module complements the PW-STD-MIB module for PW 542 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 544 operation over IP. 546 Copyright (C) The Internet Society (2006). This version 547 of this MIB module is part of RFC yyyy; see the RFC 548 itself for full legal notices. 549 -- RFC Ed.: replace yyyy with actual RFC number & remove 550 -- this note 551 " 552 -- Revision history. 553 REVISION "200702011200Z" -- 01 Feb 2007 12:00:00 GMT 554 DESCRIPTION 555 " First published as RFCWXYZ. " 556 -- RFC Editor: Please replace WXYZ with correct # and remove this 557 -- note 559 ::= { transmission XXX } 560 -- RFC Editor: To be assigned by IANA. Please replace XXX 561 -- with the assigned value and remove this note. 563 -- Top-level components of this MIB. 565 -- Notifications 566 pwGenIpNotifications OBJECT IDENTIFIER 567 ::= { pwGenIpDraft00MIB 0 } 569 -- Tables, Scalars 570 pwGenIpObjects OBJECT IDENTIFIER 571 ::= { pwGenIpDraft00MIB 1 } 572 -- Conformance 573 pwGenIpConformance OBJECT IDENTIFIER 574 ::= { pwGenIpDraft00MIB 2 } 576 -- PW IP table 578 pwGenIpTable OBJECT-TYPE 579 SYNTAX SEQUENCE OF PwGenIpEntry 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "This table contains the Pseudo wire objects for 584 Generic IP PSN type." 585 ::= { pwGenIpObjects 2 } 587 pwGenIpEntry OBJECT-TYPE 588 SYNTAX PwGenIpEntry 590 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 592 MAX-ACCESS not-accessible 593 STATUS current 594 DESCRIPTION 595 "A row in this table represents Generic parameters 596 specific to pseudo wire (PW) over IP PSN . 598 A row MUST be created automatically by the local agent 599 for every entry in the pwTable if the pwPsnType is 600 udpOverIp. Each entry is indexed by pwIndex, which uniquely 602 identifies a singular PW. 603 " 604 INDEX { pwIndex } 606 ::= { pwGenIpTable 1 } 608 PwGenIpEntry ::= SEQUENCE { 609 pwGenSourceIpAddressType InetAddressType, 610 pwGenSourceIpAddress InetAddress, 611 pwGenIpTos Unsigned32, 612 pwGenIpTosDropPrecedence Unsigned32 613 } 615 pwGenSourceIpAddressType OBJECT-TYPE 616 SYNTAX InetAddressType 617 MAX-ACCESS read-write 618 STATUS current 619 DESCRIPTION 620 "This object indicates the type of IP address stored in 621 pwGenSourceIpAddress." 622 ::= { pwGenIpEntry 1 } 624 pwGenSourceIpAddress OBJECT-TYPE 625 SYNTAX InetAddress 626 MAX-ACCESS read-write 627 STATUS current 628 DESCRIPTION 629 "This object indicates source IP Address for PW having 630 pwPsnType= udpOverIp (3)" 631 ::= { pwGenIpEntry 2 } 633 pwGenIpTos OBJECT-TYPE 634 SYNTAX Unsigned32 635 MAX-ACCESS read-write 636 STATUS current 637 DESCRIPTION 639 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 641 "This object indicates TOS field value for PW having 642 pwPsnType= udpOverIp (3), IP precedence (bits 0-2 in IP 643 TOS byte),DSCP (bits 0-5 in IP TOS byte)." 644 ::= { pwGenIpEntry 3 } 646 pwGenIpTosDropPrecedence OBJECT-TYPE 647 SYNTAX Unsigned32 648 MAX-ACCESS read-write 649 STATUS current 650 DESCRIPTION 651 "In implementations that support two level of drop 652 precedence marking, this object defines the DSCP 653 or TOS field to be used for packets with higher drop 654 precedence compared to packets marked with pwGenIpTos, 655 otherwise this object should return the the value equal 656 to pwGenIpTos ." 658 ::= { pwGenIpEntry 4 } 660 -- End of PW IP table 662 -- conformance information 664 pwGenIpGroups OBJECT IDENTIFIER ::= { pwGenIpConformance 1 } 665 pwGenIpCompliances OBJECT IDENTIFIER ::= { pwGenIpConformance 2 } 667 -- Compliance requirement for fully compliant implementations. 669 pwGenIpModuleFullCompliance MODULE-COMPLIANCE 670 STATUS current 671 DESCRIPTION 672 "The compliance statement for agents that provide full 673 support for PW-IP MIB Module. Such devices can 674 then be monitored and also be configured using 675 this MIB module." 677 MODULE -- this module 678 MANDATORY-GROUPS { pwGenIpGroup 679 } 681 ::= { pwGenIpCompliances 1 } 683 -- Compliance requirement for Read Only compliant implementations. 685 pwGenIpModuleReadOnlyCompliance MODULE-COMPLIANCE 686 STATUS current 688 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 690 DESCRIPTION 691 "The compliance statement for agents that provide read 692 only support for PW-IP MIB Module. Such devices can 693 then be monitored but cannot be configured using this 694 MIB module." 696 MODULE -- this module 697 MANDATORY-GROUPS { pwGenIpGroup 698 } 700 ::= { pwGenIpCompliances 2 } 702 -- Units of conformance. 704 pwGenIpGroup OBJECT-GROUP 705 OBJECTS { 706 pwGenSourceIpAddressType, 707 pwGenSourceIpAddress, 708 pwGenIpTos, 709 pwGenIpTosDropPrecedence 710 } 711 STATUS current 712 DESCRIPTION 713 "Collection of objects needed for PW over IP PSN 714 configuration." 715 ::= { pwGenIpGroups 1 } 717 END 719 7 Security Considerations 721 It is clear that this MIB module is potentially useful for 722 monitoring of PW capable PEs. This MIB module can also be used for 723 configuration of certain objects, and anything that can be 724 configured can be incorrectly configured, with potentially 725 disastrous results. 727 There are a number of management objects defined in this MIB module 728 with a MAX-ACCESS clause of read-write and/or read-create. Such 729 objects may be considered sensitive or vulnerable in some network 730 environments. The support for SET operations in a non-secure 731 environment without proper protection can have a negative effect on 732 network operations. These are the tables and objects and their 733 sensitivity/vulnerability: 735 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 737 o The pwL2tpv3Table and pwL2tpv3MappingTable[TBD] collectively 738 contain objects to provision PW over L2TPV3 tunnels. 739 Unauthorized access to objects in these tables, could 740 result in disruption of traffic on the network. The use of 741 stronger mechanisms such as SNMPv3 security should be 742 considered where possible. Specifically, SNMPv3 VACM and 743 USM MUST be used with any v3 agent which implements this MIB 744 module. 745 Administrators should consider whether read access to these 746 objects should be allowed, since read access may be 747 undesirable under certain circumstances. 749 Some of the readable objects in this MIB module "i.e., objects with 750 a MAX-ACCESS other than not-accessible" may be considered sensitive 751 or vulnerable in some network environments. It is thus important 752 to control even GET and/or NOTIFY access to these objects and 753 possibly to even encrypt the values of these objects when sending 754 them over the network via SNMP. These are the tables and objects 755 and their sensitivity/vulnerability: 757 o the pwL2tpv3Table and pwL2tpv3MappingTable[TBD], 758 collectively show the PW over L2TPV3 association. 759 If an Administrator does not want to reveal this 760 information, then these tables should be 761 considered sensitive/vulnerable. 763 SNMP versions prior to SNMPv3 did not include adequate security. 764 Even if the network itself is secure "for example by using IPSec", 765 even then, there is no control as to who on the secure network is 766 allowed to access and GET/SET "read/change/create/delete" the 767 objects in this MIB module. 769 It is RECOMMENDED that implementers consider the security features 770 as provided by the SNMPv3 framework "see [RFC3410], section 8", 771 including full support for the SNMPv3 cryptographic mechanisms "for 772 authentication and privacy". 774 Further, deployment of SNMP versions prior to SNMPv3 is NOT 775 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 776 enable cryptographic security. It is then a customer/operator 777 responsibility to ensure that the SNMP entity giving access to an 778 instance of this MIB module, is properly configured to give access 779 to the objects only to those principals "users" that have 780 legitimate rights to indeed GET or SET "change/create/delete" them. 782 8 IANA considerations 783 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 785 9 References 787 9.1 Normative references 789 [PW-IP] C. Pignataro, W. Luo, "Signaling and Encapsulation for 790 the Transport of IP over L2TPv3", work-in-progress. 792 [L2TPv3-MIB] Nadeau,T., et al, "Layer Two Tunneling Protocol 793 (Version 3) L2TPv3 Management Information Base", 794 work-in-progress. 796 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 797 and OBJECT-IDENTITIES for Pseudo-Wires Management", 798 work-in-progress. 800 [PW-MIB] Zelig, D., et al, "Pseudo Wire (PW) Management 801 Information Base", work-in-progress. 803 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 804 requirement Levels", BCP 14, RFC 2119, March 1997. 806 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 807 J.,Rose, M. and S. Waldbusser, "Structure of Management 808 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 809 1999. 811 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 812 J., Rose, M. and S. Waldbusser, "Textual Conventions 813 for SMIv2", STD 58, RFC 2579, April 1999. 815 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 816 J., Rose, M. and S. Waldbusser, "Conformance Statements 817 for SMIv2", STD 58, RFC 2580, April 1999. 819 [RFC2863] McCloghrie, K., F. Kastenholz, "The Interfaces Group 820 MIB using SMIv2", RFC 2863, June 2000. 822 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 823 "Multiprotocol Label Switching Architecture", RFC 3031, 824 Jan 2001. 826 [RFC3036] Andersson, L., et al, "LDP specification", RFC 3036, 827 January 2001. 829 [RFC3811] Nadeau, T., Cucchiara, J., "Definitions of Textual 830 Conventions (TCs) for Multiprotocol Label Switching 831 (MPLS) Management", RFC 3811, June 2004. 833 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 835 [RFC3812] Srinivasan, C., Viswanathan, A., and Nadeau, T., 836 "Multiprotocol Label Switching (MPLS) Traffic 837 Engineering (TE) Management Information Base (MIB)", 838 RFC 3812, June 2004. 840 [RFC3813] Srinivasan, C., Viswanathan, A., and Nadeau, T., 841 "Multiprotocol Label Switching (MPLS) Label Switching 842 Router (LSR) Management Information Base (MIB)", RFC 843 3813, June 2004. 845 [RFC4447] Martini et al, "Pseudowire Setup and Maintenance using 846 the Label Distribution Protocol (LDP)", RFC 4447, April 847 2006. 849 9.2 Informative references 851 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing 852 an IANA Considerations Section in RFCs", BCP: 26, RFC 853 2434, October 1998. 855 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 856 "Introduction and Applicability Statements for 857 Internet-Standard Management Framework", RFC 3410, 858 December 2002. 860 [RFC3916] Xio, X., et al, "Requirements for Pseudo-Wire Emulation 861 Edge-to-Edge (PWE3)", RFC 3916, September 2004. 863 [RFC3985] Bryant, S., and Pate, P., "Pseudo Wire Emulation Edge- 864 to-Edge (PWE3) Architecture", RFC 3985, March 2005. 866 10 Author's Addresses 868 Thomas D. Nadeau 869 Cisco Systems, Inc. 870 1414 Massachusetts Ave, 871 Boxborough, MA 01719 872 Email: tnadeau@cisco.com 874 A S Kiran Koushik 875 Cisco Systems, Inc. 876 12515 Research Blvd, Bldg 4 877 Austin, TX 78759 878 Email: kkoushik@cisco.com 880 Carlos Pignataro 882 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 884 cisco Systems, Inc. 885 7025-1 Kit Creek Rd 886 PO Box 14987 887 Research Triangle Park, NC 27709-4987 888 cpignata@cisco.com 890 Orly Nicklass 891 RAD Data Communications 892 24 Raoul Wallenberg St., Bldg C 893 Tel Aviv 69719 894 ISRAEL 896 Phone: +972 3 7659969 897 Email: orly_n@rad.com 899 11 Full Copyright Statement 901 Copyright (C) The IETF Trust (2007). 903 This document is subject to the rights, licenses and restrictions 904 contained in BCP 78, and except as set forth therein, the authors 905 retain all their rights. 907 This document and the information contained herein are provided on an 908 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 909 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 910 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 911 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 912 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 913 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 914 FOR A PARTICULAR PURPOSE. 916 12 Intellectual Property Notice 918 The IETF takes no position regarding the validity or scope of any 919 Intellectual Property Rights or other rights that might be claimed to 920 pertain to the implementation or use of the technology described in 921 this document or the extent to which any license under such rights 922 might or might not be available; nor does it represent that it has 923 made any independent effort to identify any such rights. Information 924 on the procedures with respect to rights in RFC documents can be 925 found in BCP 78 and BCP 79. 927 draft-nadeau-l2tpext-pw-l2tpv3-mib-01 PW-L2TPV3-MIB June 27, 2007 929 Copies of IPR disclosures made to the IETF Secretariat and any 930 assurances of licenses to be made available, or the result of an 931 attempt made to obtain a general license or permission for the use 932 of such proprietary rights by implementers or users of this 933 specification can be obtained from the IETF on-line IPR repository 934 at http://www.ietf.org/ipr. 936 The IETF invites any interested party to bring to its attention any 937 copyrights, patents or patent applications, or other proprietary 938 rights that may cover technology that may be required to implement 939 this standard. Please address the information to the IETF at ietf- 940 ipr@ietf.org. 942 Disclaimer of Validity 944 This document and the information contained herein are provided 945 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 946 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 947 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 948 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 949 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 950 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 951 FOR A PARTICULAR PURPOSE.