idnits 2.17.1 draft-ietf-pwe3-tdm-mib-11.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 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1876. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1887. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1894. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1900. 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 : ---------------------------------------------------------------------------- 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 (October 20, 2008) is 5660 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: Non-RFC (?) normative reference: ref. 'TDMCP-EXT' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Pseudo Wire Edge to Edge Emulation O. Nicklass 3 Internet-Draft RADVISION Ltd. 4 Intended status: Standards Track October 20, 2008 5 Expires: April 23, 2009 7 Managed Objects for TDM over Packet Switched Network (PSN) 8 draft-ietf-pwe3-tdm-mib-11.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on April 23, 2009. 35 Abstract 37 This memo defines a portion of the Management Information Base (MIB) 38 for use with network management protocols in the Internet community. 39 In particular, it describes managed objects for pseudo wire 40 encapsulation for structured or unstructured TDM (T1, E1, T3, E3) 41 circuits over a Packet Switch Network (PSN). 43 Table of Contents 45 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 46 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 47 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 48 4. The Internet-Standard Management Framework . . . . . . . . . . 4 49 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 50 6. TDM MIB module usage . . . . . . . . . . . . . . . . . . . . . 5 51 6.1. Structure of TDM MIB . . . . . . . . . . . . . . . . . . . 5 52 6.2. TDM Connection configuration Procedure . . . . . . . . . . 6 53 6.3. TDM PW Monitoring . . . . . . . . . . . . . . . . . . . . 6 54 7. Example of actual TDM PW Setup . . . . . . . . . . . . . . . . 7 55 8. Object definition . . . . . . . . . . . . . . . . . . . . . . 9 56 9. Security considerations . . . . . . . . . . . . . . . . . . . 43 57 10. IANA considerations . . . . . . . . . . . . . . . . . . . . . 44 58 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 45 59 11.1. Normative references . . . . . . . . . . . . . . . . . . . 45 60 11.2. Informative references . . . . . . . . . . . . . . . . . . 47 61 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 47 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 47 63 Intellectual Property and Copyright Statements . . . . . . . . . . 48 65 1. Introduction 67 This document describes a model for managing TDM pseudo wires, i.e. 68 TDM data encapsulated for transmission over a Packet Switched Network 69 (PSN). The term TDM in this document is limited to the scope of PDH 70 hierarchy. It is currently specified to carry any TDM Signals in 71 either Structure Agnostic Transport mode (E1, T1, E3 and T3) or in 72 Structure Aware Transport mode (E1, T1 and NxDS0) as defined in PWE3 73 TDM Requirements document [RFC4197]. 75 This document is closely related to [SATOP], [TDMOIP] and [CESOPSN] 76 which describe the encapsulation of TDM signals and provide the 77 Circuit Emulation Service over a Packet Switched Network (PSN). 79 The TDM management model consists of several MIB modules, following 80 the layering model described in the PWE3 Architecture [RFC3985] 81 document. The TDM MIB module described in this document works 82 closely with the MIB modules described in [DS3MIB], [DS1MIB], 83 [DS0MIB], [IFMIB], [PWMIB] and the textual conventions defined in 84 [PWTC]. The conceptual layering and relationship among all those is 85 described in Figure 1 below. A TDM connection will be a pseudo-wire 86 (PW) connection. It will not be treated as an interface and will 87 therefore not be represented in the ifTable. 89 Figure 1:Conceptual Layering 91 +-------------------+ 92 | TDM MIB | DS1MIB, DS3MIB, 93 +-------------------+ DS0MIB 94 | 95 +-------------------+ PW-TDM-MIB, 96 Service | TDM PW MIB | PW-CESOPSN-MIB, 97 Layer +-------------------+ PW-TDMOIP-MIB 99 - - - - - - - - - - - | - - - - - - - - - - - - - - - 100 Generic +-------------------+ 101 PW | Generic PW MIBS | PW-TC-MIB, 102 Layer +-------------------+ PW-MIB 103 - - - - - - - - - - - -| - - - - - - - - - - - - - - - 104 +-------------------+ 105 PSN VC | MPLS VC MIBS | PW-MPLS-MIB 106 Layer +-------------------+ 107 - - - - - - - - - - - -| - - - - - - - - - - - - - - - 108 +-------------------+ 109 PSN | MPLS MIBs | MPLS-TE-STD-MIB, 110 Layer +-------------------+ MPLS-LSR-STD-MIB 111 Figure 1 113 Comments should be made directly to PWE3 group at pwe3@ietf.org. 115 2. Conventions 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 119 document are to be interpreted as described in RFC-2119 [BCP14]. 121 3. Terminology 123 The Basic terminology used to refer to transmission direction in this 124 document is taken from [SATOP] draft that describes a mechanism for 125 transporting Structure-Agnostic (TDM) bit-streams over a packet- 126 oriented network. For simplifying this document the terminology is 127 used for structure and unstructured TDM as well. 129 "PSN-bound" references the traffic direction where TDM data is 130 received, adapted to packet based on number of payload bytes per 131 packet, assigned a relevant TDM header (Sequence numbers, flags, and 132 timestamps (if the RTP header is used)), prepended multiplexing layer 133 and PSN headers and sent into the PSN. 135 Conversely, The "CE-bound" references the traffic direction where 136 packets are received from the PSN, packet payloads are reassembled by 137 including a jitter buffer where payload of the received TDM packets 138 is stored prior to play-out to the TDM line. The size of this buffer 139 SHOULD be locally configurable to allow accommodation to the PSN- 140 specific packet delay variation. 142 The CE-bound TDM inter-working function (IWF) SHOULD use the sequence 143 number in the control word for detection of lost (LOPS) and mis- 144 ordered packets. If the RTP header is used, the RTP sequence numbers 145 MAY be used for the same purposes. 147 4. The Internet-Standard Management Framework 149 For a detailed overview of the documents that describe the current 150 Internet-Standard Management Framework, please refer to section 7 of 151 RFC 3410 [RFC3410]. 153 Managed objects are accessed via a virtual information store, termed 154 the Management Information Base or MIB. MIB objects are generally 155 accessed through the Simple Network Management Protocol (SNMP). 157 Objects in the MIB are defined using the mechanisms defined in the 158 Structure of Management Information (SMI). This memo specifies a MIB 159 module that is compliant to the SMIv2, which is described in STD 58, 160 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 161 [RFC2580]. 163 5. Overview 165 This MIB module is designed to satisfy the following requirements and 166 constraints: 167 1. Fits within the architecture defined by [RFC3985] and [PWMIB]. 168 2. The MIB module supports edge-to-edge emulation of any TDM 169 connections. 170 3. The MIB module configures the connection. The connection 171 specific behavior is provided via the supplement MIB modules. 172 4. The MIB module reports various alarms, counters and status 173 objects. 175 6. TDM MIB module usage 177 6.1. Structure of TDM MIB 179 The MIB consists of five tables; 181 -The TDM PW Table (pwTDMTable) contains generic TDM information 182 regarding the PW connection. It contains the ifIndex of the TDM 183 interface, an index to an entry in the generic configuration table 184 (pwTDMCfgTable), an index to an entry in the specific configuration 185 table (pwCXXXCfgTable, where XXX can be TDMoIP or CESoPSN), config 186 error indications, and various status indications. The two indices 187 of the two configuration tables are providing the connection 188 parameters. The TDM interface can be a full link of any TDM type 189 like E1 or DS3 for example, or the interface of the bundle holding 190 the collection of time slots to be transmitted. Based on the TDM PW 191 type the relevant pwXXXCfgTable from the relevant MIB module will be 192 used. The specific types are: 193 o 17 Structure-agnostic E1 over Packet 194 o 18 Structure-agnostic T1 (DS1) over Packet 195 o 19 Structure-agnostic E3 over Packet 196 o 20 Structure-agnostic T3 (DS3) over Packet 197 o 21 CESoPSN basic mode (XXX=CESoPSN) 198 o 22 TDMoIP AAL1mode (XXX=TDMoIP) 199 o 23 CESoPSN TDM with CAS (XXX=CESoPSN) 200 o 24 TDMoIP AAL2 Mode (XXX=TDMoIP) 202 - The TDM generic parameter Table (pwTDMCfgTable, ) contains TDM 203 generic configurable parameters for any TDM Type. 205 - The TDM Performance Current Table (pwTDMPerfCurrentTable) contains 206 TDM statistics for the current 15-minute period. 208 - The TDM Performance Interval Table (pwTDMPerfIntervalTable) 209 contains TDM statistics for historical intervals (usually 96 15- 210 minute entries to cover a 24 hour period). 212 - The TDM Performance one day Interval Table 213 (pwTDMPerf1DayIntervalTable) contains TDM statistics for historical 214 intervals accumulated per day. Usually 30 1-Day entries to cover a 215 monthly period. 217 6.2. TDM Connection configuration Procedure 219 Configuring a TDM PW involves the following steps: 221 First Configure the parameters of the interface specific layer using 222 DS1-MIB and or DS3-MIB. 224 Next, if applicable, create a bundle of Time Slots using DS0 Bundle 225 MIB [DS0MIB]. 227 Next, create an entry in the pwTable and configure the PSN tunnels: 229 - Follow steps as defined in [PWMIB]. 231 NOTE: The agent should create an entry in the pwTDMTable for any 232 entry created in the pwTable with pwType equal to a value between 233 (17) to (24). 235 Next complete the TDM PW configuration: 237 - If necessary, create an entry in the relevant pwXXXCfgTable and in 238 the pwTDMTable (suitable entries may already exist in both tables). 240 - Set the index of the relevant pwXXXCfgTable entry and of the 241 relevant pwTDMCfgTable entry in the pwTDMTable. 243 6.3. TDM PW Monitoring 245 Upon making the TDM PW operational, the pwTDMPerfCurrentTable, 246 pwTDMPerfIntervalTable, and PwTDMPerf1DayIntervalTable can be used to 247 monitor the various counters, indicators, and conditions of the PW. 248 All performance parameters are accumulated in daily intervals and in 249 fifteen minute intervals. The number of daily intervals kept by the 250 agent are based on the specific implementation. The fifteen minute 251 intervals up to 96 intervals (24 hours worth) are all kept by the 252 agent. Fewer than 96 intervals of data will be available if the 253 agent has been restarted within the last 24 hours. Performance 254 parameters continue to be collected when the interface is down. 255 There is no requirement for an agent to ensure fixed relationship 256 between the start of a fifteen minute interval and any wall clock; 257 however some agents may align the fifteen minute intervals with 258 quarter hours. Performance parameters are of types PerfCurrentCount 259 and PerfIntervalCount. These textual conventions are all Gauge32, 260 and they are used because it is possible for these objects to 261 decrease. 263 7. Example of actual TDM PW Setup 265 This section provides an example of using the various MIB objects 266 described in the following section to set up a TDM PW connection. 268 First example, setting a connection of DS1 type. Second example 269 setting a connection with bandwidth of 3 DS0 (time slots). 271 While those examples are not meant to illustrate all options of the 272 MIB, they are intended as an aid to understanding some of the key 273 concepts. See [PWMIB] for an example of setting up PSN Tunnels. 275 First example: 276 1. Configure the DS1 interface using DS1-MIB. 277 2. If needed, Create an entry in the pwTDMCfgTable (assuming index = 278 10); Verify that there are no errors in the configuration using 279 the relevant object. 280 3. Get a new pwIndexNext [PWMIB] and create a new pwTable entry 281 using the value of pwIndexNext (assume here, the PW index = 20). 282 4. Set the pwType [PWMIB] of the new entry to the relevant value 283 (17) or (18). This should create a new entry in the pwTDMTable. 284 5. Configure the newly created TDM PW with the required pointers, 285 indices, the relevant entry in pwTDMCfgTable (index 10). 287 In [DS1MIB] dsx1IfIndex (ifIndex = 5) 288 In pwTDMCfgTable entry: Set the connection characteristic 289 parameters: 291 { 293 pwTDMCfgPayloadSize = 43 -- payload bytes 294 pwTDMCfgPktReorder = FALSE 295 pwTDMCfgRtpHdrUsed = FALSE 296 pwTDMCfgJtrBfrDepth = 30000 -- micro-seconds 298 } 300 In pwTDMTable entry: Set the relevant ifIndex, the generic 301 TDM Index and the specific TDM index to complete creation: 303 { 304 pwTDMIfIndex = 5 -- IfIndex of associated entry 305 -- in DS1 table 306 pwGenTDMCfgIndex = 10 -- Index of associated entry 307 -- in pwTDMCfgTable. 308 pwRelTDMCfgIndex = 0 -- No Index in associated entry 309 -- in pwXXXCfgTable. 310 } 312 Verify that there are no error bits set in pwTDMConfigError. 314 Second example: 315 1. Configure the DS1 interface using DS1-MIB. 316 2. set up a bundle and get its dsx0BundleIfIndex. Setting up the 317 bundle should involve using IFMIB properly. 318 3. Since structured TDMoIP circuit is defined, the next MIB module 319 to be used is TDMoIP-MIB. 320 4. If needed, Create an entry in the pwTDMCfgTable (assuming index = 321 7): 322 5. If needed, Create an entry in the pwXXXCfgTable (index = 11). 323 XXX can be TDMoIP or CESoPSN 324 6. Verify that there are no error in the configuration using the 325 relevant object when signaling is in use. 326 7. Get a new pwIndexNext [PWMIB] and create a new pwTable entry 327 using the value of pwIndexNext. 328 8. Set the pwType [PWMIB] of the new entry to (24). This should 329 create a new entry in the pwTDMTable. 330 9. Configure the newly created TDM PW with the required pointers, 331 indices and the relevant entries in pwTDMCfgTable and in 332 pwXXXCfgTable (assuming indexes 7 and 11). 334 In [DS1MIB] dsx1IfIndex (ifIndex) = 5 335 In [DS0MIB] dsx0BundleIfIndex = 8 337 In pwTDMTable entry: Set the relevant ifIndex, the generic 338 TDM Index and the specific TDM index to complete creation: 340 { 341 pwTDMIfIndex = 8 -- IfIndex of associated entry 342 -- in DS0 table 343 pwGenTDMCfgIndex = 7 -- Index of associated entry 344 -- in pwTDMCfgTable. 345 pwRelTDMCfgIndex = 11 -- Index of associated entry 346 -- in pwXXXCfgTable. 347 -- pwXXXCfgTable might be an implementation specific table too. 348 } 350 Verify that there are no error bits set in pwTDMConfigError. 352 8. Object definition 354 PW-TDM-MIB DEFINITIONS ::= BEGIN 355 IMPORTS 356 MODULE-IDENTITY, OBJECT-TYPE, 357 Integer32, Counter32, Unsigned32, mib-2 358 FROM SNMPv2-SMI 360 MODULE-COMPLIANCE, OBJECT-GROUP 361 FROM SNMPv2-CONF 363 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 364 TimeStamp 365 FROM SNMPv2-TC 367 InterfaceIndexOrZero 368 FROM IF-MIB -- [IFMIB] 370 SnmpAdminString 371 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 373 PerfCurrentCount, PerfIntervalCount 374 FROM PerfHist-TC-MIB 376 pwIndex 377 FROM PW-STD-MIB 379 PwCfgIndexOrzero 380 FROM PW-TC-STD-MIB; 382 -- The TDM MIB 383 pwTDMMIB MODULE-IDENTITY 385 LAST-UPDATED "200804290000Z" 386 ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3) 387 Working Group" 388 CONTACT-INFO 389 " Orly Nicklass 390 Postal: RADVISION Ltd. 391 24Raul Wallenberg St. 392 Tel Aviv, Israel 393 Email: orlyn@radvision.com 395 The PWE3 Working Group (email distribution pwe3@ietf.org, 396 http://www.ietf.org/html.charters/pwe3-charter.html) 397 " 399 DESCRIPTION 400 "This MIB contains managed object definitions for 401 encapsulating TDM (T1,E1, T3, E3, NxDS0) as 402 pseudo-wires over packet-switching networks (PSN). 404 This MIB supplements the PW-STD-MIB as in: Zelig, D., 405 Nadeau,T. 'Pseudo Wire (PW) Management Information Base'. 406 The PW-STD-MIB contains structures and MIB associations 407 generic to Pseudo-Wire (PW) emulation. PW-specific 408 MIBs (such as this) contain config and stats for specific 409 PW types. 411 Copyright (C) The IETF Trust (2007). This version 412 of this MIB module is part of RFC yyyy; see the RFC 413 itself for full legal notices. 414 -- RFC Ed.: replace yyyy with actual RFC number & remove this 415 note" 417 REVISION "200804290000Z" 418 DESCRIPTION 419 "Initial version published as part of RFC YYYY." 420 -- RFC Editor: please replace YYYY with IANA assigned value, and 421 -- delete this note. 423 ::= { mib-2 XXX } 424 -- RFC Editor: replace XXX with IANA-assigned number & remove this 425 -- note. Please see IANA considerations section 427 -- Local Textual conventions 428 PwTDMCfgIndex ::= TEXTUAL-CONVENTION 429 STATUS current 430 DESCRIPTION 431 "Index into the relevant pwXXXCfgTable." 432 SYNTAX Unsigned32 (1..4294967295) 434 -- Notifications 435 pwTDMNotifications OBJECT IDENTIFIER 436 ::= { pwTDMMIB 0 } 437 -- Tables, Scalars 438 pwTDMObjects OBJECT IDENTIFIER 439 ::= { pwTDMMIB 1 } 440 -- Conformance 441 pwTDMConformance OBJECT IDENTIFIER 442 ::= { pwTDMMIB 2 } 444 -- TDM PW table 446 pwTDMTable OBJECT-TYPE 447 SYNTAX SEQUENCE OF PwTDMEntry 448 MAX-ACCESS not-accessible 449 STATUS current 450 DESCRIPTION 451 "This table contains basic information including ifIndex, 452 and pointers to entries in the relevant TDM config 453 tables for this TDM PW." 454 ::= { pwTDMObjects 1 } 456 pwTDMEntry OBJECT-TYPE 457 SYNTAX PwTDMEntry 458 MAX-ACCESS not-accessible 459 STATUS current 460 DESCRIPTION 461 "This table is indexed by the same index that was 462 created for the associated entry in the PW Table 463 (in the PW-STD-MIB). 465 - The PwIndex. 467 An entry is created in this table by the agent for every 468 entry in the pwTable with a pwType equal to one of the 469 following: 470 e1Satop(17), t1Satop(18), e3Satop(19), t3Satop(20), 471 basicCesPsn(21), basicTdmIp(22), tdmCasCesPsn(23), 472 tdmCasTdmIp(24). 473 Unless otherwise specified, all writeable objects in this 474 table MUST NOT be changed after row activation in the 475 generic pwTable (see [PWMIB])and values must persist 476 after reboot." 478 INDEX { pwIndex } 480 ::= { pwTDMTable 1 } 482 PwTDMEntry ::= SEQUENCE { 484 pwTDMRate Integer32, 485 pwTDMIfIndex InterfaceIndexOrZero, 486 pwGenTDMCfgIndex PwCfgIndexOrzero, 487 pwRelTDMCfgIndex PwCfgIndexOrzero, 489 pwTDMConfigError BITS, 490 pwTDMTimeElapsed Integer32, 491 pwTDMValidIntervals Integer32, 492 pwTDMValidDayIntervals Integer32, 493 pwTDMLastEsTimeStamp TimeStamp 494 } 496 pwTDMRate OBJECT-TYPE 497 SYNTAX Integer32 498 MAX-ACCESS read-write 499 STATUS current 500 DESCRIPTION 501 "The parameter represents the bit-rate of the TDM service 502 in multiples of the 'basic' 64 Kbit/s rate [TDMCP-EXT]. 503 It complements the definition of pwType used in 504 PW-STD-MIB. 505 For structure-agnostic the following should be used: 506 a) Satop E1 - 32 507 b) Satop T1 emulation: 508 i) MUST be set to 24 in the basic emulation mode 509 ii) MUST be set to 25 for the 'Octet-aligned T1' 510 emulation mode 511 c) Satop E3 - 535 512 d) Satop T3 - 699 513 For all kinds of structure-aware emulation, this parameter 514 MUST be set to N where N is the number of DS0 channels 515 in the corresponding attachment circuit." 516 REFERENCE 517 "TDMCP-EXT" 518 DEFVAL { 32 } 519 ::= { pwTDMEntry 1 } 521 pwTDMIfIndex OBJECT-TYPE 522 SYNTAX InterfaceIndexOrZero 523 MAX-ACCESS read-write 524 STATUS current 525 DESCRIPTION 526 "This is a unique index within the ifTable. It represents 527 the interface index of the full link or the interface 528 index for the bundle holding the group of 529 time slots to be transmitted via this PW connection. 531 A value of zero indicates an interface index that has yet 532 to be determined. 533 Once set, if the TDM ifIndex is (for some reason) later 534 removed, the agent SHOULD delete the associated PW rows 535 (e.g., this pwTDMTable entry). If the agent does not 536 delete the rows, the agent MUST set this object to 537 zero." 538 ::= { pwTDMEntry 2 } 540 pwGenTDMCfgIndex OBJECT-TYPE 541 SYNTAX PwCfgIndexOrzero 542 MAX-ACCESS read-write 543 STATUS current 544 DESCRIPTION 545 "Index to the generic parameters in the TDM configuration 546 table that appears in this MIB module. It is likely that 547 multiple TDM PWs of the same characteristic will share 548 a single TDM Cfg entry." 549 ::= { pwTDMEntry 3 } 551 pwRelTDMCfgIndex OBJECT-TYPE 552 SYNTAX PwCfgIndexOrzero 553 MAX-ACCESS read-write 554 STATUS current 555 DESCRIPTION 556 "Index to the relevant TDM configuration table entry 557 that appears in one of the related MIB modules 558 such as TDMoIP or CESoPSN. It is likely that 559 multiple TDM PWs of the same characteristic will share 560 a single configuration entry of the relevant type. 561 The value 0 implies no entry in other related MIB" 562 ::= { pwTDMEntry 4 } 564 pwTDMConfigError OBJECT-TYPE 565 SYNTAX BITS { 566 notApplicable ( 0), 567 tdmTypeIncompatible ( 1), 568 peerRtpIncompatible ( 2), 569 peerPayloadSizeIncompatible ( 3) 570 } 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "Any of the bits are set if the local configuration is 575 not compatible with the peer configuration as available 576 from the various parameters options. Setting is done based 577 on signaling, or else value (0) will be set. 579 -tdmTypeIncompatible bit is set if the local configuration 580 is not carrying the same TDM type as the peer configuration. 582 -peerRtpIncompatible bit is set if the local configuration 583 is configured to send RTP packets for this PW, and the 584 remote is not capable of accepting RTP packets. 586 -peerPayloadSizeIncompatible bit is set if the local 587 configuration is not carrying the same Payload Size as the 588 peer configuration. " 589 ::= { pwTDMEntry 5} 591 pwTDMTimeElapsed OBJECT-TYPE 592 SYNTAX Integer32 (1..900) 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "The number of seconds, including partial seconds, 597 that have elapsed since the beginning of the current 598 measurement period. If, for some reason, such as an 599 adjustment in the system's time-of-day clock, the 600 current interval exceeds the maximum value, the 601 agent will return the maximum value." 602 ::= { pwTDMEntry 6} 604 pwTDMValidIntervals OBJECT-TYPE 605 SYNTAX Integer32 (0..96) 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "The number of previous 15-minute intervals for which data 610 was collected. 611 An agent with TDM capability must be capable of supporting 612 at least n intervals. The minimum value of n is 4, The 613 default of n is 32 and the maximum value of n is 96. 614 The value will be n unless the measurement was (re-) 615 started within the last (n*15) minutes, in which case 616 the value will be the number of complete 15 minute 617 intervals for which the agent has at least some data. 618 In certain cases(e.g., in the case where the agent is 619 a proxy) it is possible that some intervals are unavailable. 620 In this case, this interval is the maximum interval number 621 for which data is available. " 622 ::= { pwTDMEntry 7} 624 pwTDMValidDayIntervals OBJECT-TYPE 625 SYNTAX Integer32 (0..30) 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "The number of previous days for which data 630 was collected. 631 An agent with TDM capability must be capable of supporting 632 at least n intervals. The minimum value of n is 1, The 633 default of n is 1 and the maximum value of n is 30." 634 ::= { pwTDMEntry 8} 636 pwTDMLastEsTimeStamp OBJECT-TYPE 637 SYNTAX TimeStamp 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "The value of sysUpTime at the most recent occasion at 642 which the TDM PW entered the ES or SES state." 643 ::= { pwTDMEntry 11} 645 -- End of TDM PW table 647 -- PW Generic TDM PW Configuration Table 648 pwTDMCfgIndexNext OBJECT-TYPE 649 SYNTAX Unsigned32 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "This object contains the value to be used for 654 pwTDMCfgIndex when creating entries in the 655 pwTDMCfgTable. The value 0 indicates that no 656 unassigned entries are available. To obtain the 657 value of pwTDMCfgIndexNext for a new entry in the 658 pwTDMCfgTable, the manager issues a management 659 protocol retrieval operation. The agent will 660 determine through its local policy when this 661 index value will be made available for reuse." 663 ::= { pwTDMObjects 2 } 665 pwTDMCfgTable OBJECT-TYPE 666 SYNTAX SEQUENCE OF PwTDMCfgEntry 667 MAX-ACCESS not-accessible 668 STATUS current 669 DESCRIPTION 670 "This table contains a set of parameters that may be 671 referenced by one or more TDM PWs in pwTDMTable." 673 ::= { pwTDMObjects 3 } 675 pwTDMCfgEntry OBJECT-TYPE 676 SYNTAX PwTDMCfgEntry 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "These parameters define the characteristics of a 681 TDM PW. They are grouped here to ease NMS burden. 682 Once an entry is created here it may be re-used 683 by many PWs. 684 Unless otherwise specified, all objects in this table 685 MUST NOT be changed after row activation (see [PWMIB]) 686 if the row index is in use by an entry in pwTDMTable. 687 Rows must persist after reboot." 689 INDEX { pwTDMCfgIndex } 691 ::= { pwTDMCfgTable 1 } 693 PwTDMCfgEntry ::= SEQUENCE { 694 pwTDMCfgIndex PwTDMCfgIndex, 695 pwTDMCfgRowStatus RowStatus, 696 pwTDMCfgPayloadSize Unsigned32, 697 pwTDMCfgPktReorder TruthValue, 698 pwTDMCfgRtpHdrUsed TruthValue, 699 pwTDMCfgJtrBfrDepth Unsigned32, 700 pwTDMCfgPayloadSuppression INTEGER, 702 pwTDMCfgConsecPktsInSynch Unsigned32, 703 pwTDMCfgConsecMissPktsOutSynch Unsigned32, 704 pwTDMCfgSetUp2SynchTimeOut Unsigned32, 706 pwTDMCfgPktReplacePolicy INTEGER, 708 pwTDMCfgAvePktLossTimeWindow Integer32, 709 pwTDMCfgExcessivePktLossThreshold Unsigned32, 711 pwTDMCfgAlarmThreshold Unsigned32, 712 pwTDMCfgClearAlarmThreshold Unsigned32, 713 pwTDMCfgMissingPktsToSes Unsigned32, 715 pwTDMCfgTimestampMode INTEGER, 716 pwTDMCfgStorageType StorageType, 717 pwTDMCfgPktFiller Unsigned32, 718 pwTDMCfgName SnmpAdminString 719 } 721 pwTDMCfgIndex OBJECT-TYPE 722 SYNTAX PwTDMCfgIndex 723 MAX-ACCESS not-accessible 724 STATUS current 725 DESCRIPTION 726 "Index to an entry in this table. When an NMS creates 727 a new entry/row in this table, it best makes use of 728 the value of the pwTDMCfgIndexNext object in order to 729 find a free or available index value." 730 ::= { pwTDMCfgEntry 1 } 732 pwTDMCfgRowStatus OBJECT-TYPE 733 SYNTAX RowStatus 734 MAX-ACCESS read-create 735 STATUS current 736 DESCRIPTION 737 "Object used for creating, modifying, and deleting 738 a row from this table. The following objects cannot be 739 modified if the entry is in use and the status is active: 740 pwTDMCfgPayloadSize, pwTDMCfgRtpHdrUsed, 741 pwTDMCfgJtrBfrDepth, and pwTDMCfgPayloadSuppression. 742 The row cannot be deleted if the entry is in use" 743 ::= { pwTDMCfgEntry 2 } 745 pwTDMCfgPayloadSize OBJECT-TYPE 746 SYNTAX Unsigned32 747 MAX-ACCESS read-create 748 STATUS current 749 DESCRIPTION 750 "The value of this object indicates the PayLoad Size (in bytes) 751 to be defined during the PW setUp. Upon TX, implementation 752 must be capable of carrying that amount of bytes. 753 Upon RX, when the LEN field is set to 0, the payload of 754 packet MUST assume this size, and if the actual 755 packet size is inconsistent with this length, 756 the packet MUST be considered to be malformed. " 757 ::= { pwTDMCfgEntry 4 } 759 pwTDMCfgPktReorder OBJECT-TYPE 760 SYNTAX TruthValue 761 MAX-ACCESS read-create 762 STATUS current 763 DESCRIPTION 764 "If set True: as CE bound packets are queued in the 765 jitter buffer, out of order packets are re-ordered. The 766 maximum sequence number differential (i.e., the range in 767 which re-sequencing can occur) is dependant on the depth 768 of the jitter buffer. See pwTDMCfgJtrBfrDepth. 770 NOTE: Some implementations may not support this feature. 771 The agent should then reject a SET request for true." 772 ::= { pwTDMCfgEntry 5 } 774 pwTDMCfgRtpHdrUsed OBJECT-TYPE 775 SYNTAX TruthValue 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "If set to False: an RTP header is not pre-pended to the 780 TDM packet." 781 REFERENCE 782 "SATOP" 783 DEFVAL { false } 784 ::= { pwTDMCfgEntry 6 } 786 pwTDMCfgJtrBfrDepth OBJECT-TYPE 787 SYNTAX Unsigned32 788 UNITS "microsecond" 789 MAX-ACCESS read-create 790 STATUS current 791 DESCRIPTION 792 "The size of this buffer SHOULD be locally 793 configured to allow accommodation to the PSN-specific packet 794 delay variation. 796 If configured to a value not supported by the 797 implementation, the agent MUST return an error code 798 'jtrBfrDepth' in 'pwTDMConfigError ' 800 NOTE: jitter buffers are a limited resource to 801 be managed. The actual size should be at least twice as big 802 as the value of pwTDMCfgJtrBfrDepth " 803 DEFVAL { 3000 } 805 ::= { pwTDMCfgEntry 7 } 807 pwTDMCfgPayloadSuppression OBJECT-TYPE 808 SYNTAX INTEGER 809 { 810 enable ( 1), 811 disable ( 2) 812 } 813 MAX-ACCESS read-create 814 STATUS current 815 DESCRIPTION 816 "Selecting 'enable' means: Payload suppression is allowed. 817 Payload MAY be omitted in order to conserve bandwidth. 818 Selecting 'disable' means: no suppresion under any 819 condition. 820 Object MAY be changed at any time." 821 DEFVAL { disable } 823 ::= { pwTDMCfgEntry 8 } 825 pwTDMCfgConsecPktsInSynch OBJECT-TYPE 826 SYNTAX Unsigned32 (1..10) 827 MAX-ACCESS read-create 828 STATUS current 829 DESCRIPTION 830 "The number of consecutive packets with sequential 831 sequence numbers that are required to exit the 832 LOPS state. 833 Object MAY be changed only when the related PW is 834 defined as not active." 835 REFERENCE 836 "SATOP" 837 DEFVAL { 2 } 838 ::= { pwTDMCfgEntry 9 } 840 pwTDMCfgConsecMissPktsOutSynch OBJECT-TYPE 841 SYNTAX Unsigned32 (1..15) 842 MAX-ACCESS read-create 843 STATUS current 844 DESCRIPTION 845 "The number of consecutive missing packets that are 846 required to enter the LOPS state. 847 Object MAY be changed only when the related PW is 848 defined as not active." 849 REFERENCE 850 "SATOP" 851 DEFVAL { 10 } 852 ::= { pwTDMCfgEntry 10 } 854 pwTDMCfgSetUp2SynchTimeOut OBJECT-TYPE 855 SYNTAX Unsigned32 856 UNITS "millisecond" 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "The amount of time the host should wait before declaring the 861 pseudo wire in down state, if the number of consecutive 862 TDM packets that have been received after changing the 863 adminstrative status to up and after finalization of 864 signaling (if supported) between the two PEs is smaller 865 than pwTDMCfgConsecPktsInSynch. Once the the pw has 866 OperStatus of 'up' this parameter is no longer valid. This 867 parameter is defined to ensure that the host does not 868 prematurely inform failure of the pw. In particular pw 'down' 869 notifications should not be sent before expiration of this 870 timer. This parameter is valid only after adminisrative 871 changes of the status of the pw. If the pw fails due to 872 network impairments a 'down' notification should be sent. 873 Object MAY be changed only when the related PW is 874 defined as not active." 875 DEFVAL {5000} 876 ::= { pwTDMCfgEntry 11 } 878 pwTDMCfgPktReplacePolicy OBJECT-TYPE 879 SYNTAX INTEGER 880 { 881 allOnes (1), 882 implementationSpecific(2), 883 filler (3) --user defined 884 } 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "This parameter determines the value to be played when CE bound 889 packets have over/underflow the jitter buffer, or are missing 890 for any reason. This byte pattern is sent(played)on 891 the TDM line. Selecting implementationSpecific(2) implies 892 agent specific algorithm. Selecting filler(3) requires setting 893 of pwTDMCfgPktFiller. 894 Object MAY be changed only when the related PW is 895 defined as not active." 896 DEFVAL { allOnes } -- Play AIS 897 ::= { pwTDMCfgEntry 12 } 899 pwTDMCfgAvePktLossTimeWindow OBJECT-TYPE 900 SYNTAX Integer32 901 UNITS "millisecond" 902 MAX-ACCESS read-create 903 STATUS current 904 DESCRIPTION 905 "The length of time over which the average packet 906 loss rate should be computed to detect Excessive packet 907 loss rate. 908 Object MAY be changed only when the related PW is 909 defined as not active." 910 ::= { pwTDMCfgEntry 13} 912 pwTDMCfgExcessivePktLossThreshold OBJECT-TYPE 913 SYNTAX Unsigned32 914 UNITS "Percent" 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "Excessive packet loss rate is detected by computing the 919 average packetloss rate over a pwTDMCfgAvePktLossTimeWindow 920 amount of time and comparing it with this threshold value. 921 The rate is expressed in precentage. 922 Object MAY be changed only when the related PW is 923 defined as not active." 924 ::= { pwTDMCfgEntry 14 } 926 pwTDMCfgAlarmThreshold OBJECT-TYPE 927 SYNTAX Unsigned32 928 UNITS "milisec" 929 MAX-ACCESS read-create 930 STATUS current 931 DESCRIPTION 932 "Alarms are only reported when the defect state persists 933 for the length of time specified by this object. 934 Object MAY be changed only when the related PW is 935 defined as not active." 936 DEFVAL { 2500 } 937 ::= { pwTDMCfgEntry 15 } 939 pwTDMCfgClearAlarmThreshold OBJECT-TYPE 940 SYNTAX Unsigned32 941 UNITS "milisec" 942 MAX-ACCESS read-create 943 STATUS current 944 DESCRIPTION 945 "Alarm MUST be cleared after the corresponding defect is 946 undetected for the amount of time specified by this object. 947 Object MAY be changed only when the related PW is 948 defined as not active." 949 DEFVAL { 10000 } 950 ::= { pwTDMCfgEntry 16 } 952 pwTDMCfgMissingPktsToSes OBJECT-TYPE 953 SYNTAX Unsigned32 954 UNITS "Percent" 955 MAX-ACCESS read-create 956 STATUS current 957 DESCRIPTION 958 "Percent of missing packets detected (consecutive or not) 959 within a 1 second window to cause a Severely Error 960 Second (SES) to be counted. 961 Object MAY be changed only when the related PW is 962 defined as not active." 963 DEFVAL { 30 } 964 ::= { pwTDMCfgEntry 17 } 966 pwTDMCfgTimestampMode OBJECT-TYPE 967 SYNTAX INTEGER 968 { 969 notApplicable (1), 970 absolute (2), 971 differential (3) 972 } 974 MAX-ACCESS read-create 975 STATUS current 976 DESCRIPTION 977 "Timestamp generation MAY be used in one of the following 978 modes: 979 1. Absolute mode: the PSN-bound IWF sets timestamps 980 using the clock recovered from the incoming TDM attachment 981 circuit. As a consequence, the timestamps are closely 982 correlated with the sequence numbers. All TDM implementations 983 that support usage of the RTP header MUST support this mode. 984 2. Differential mode: Both IWFs have access to a common high- 985 quality timing source, and this source is used for timestamp 986 generation. Support of this mode is OPTIONAL. 987 Object MAY be changed only when the related PW is 988 defined as not active." 990 ::= { pwTDMCfgEntry 18 } 992 pwTDMCfgStorageType OBJECT-TYPE 993 SYNTAX StorageType 994 MAX-ACCESS read-create 995 STATUS current 996 DESCRIPTION 997 "This variable indicates the storage type for this 998 row. Conceptual rows having the value permanent(4) must 999 allow write-access to all columnar objects." 1000 ::= { pwTDMCfgEntry 19 } 1002 pwTDMCfgPktFiller OBJECT-TYPE 1003 SYNTAX Unsigned32 (0..255) 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "Filler byte pattern played out on the TDM 1008 interface if pwTDMCfgPktReplacePolicy 1009 was set to filler(3). 1010 Object MAY be changed only when the related PW is 1011 defined as not active." 1012 DEFVAL 1013 { 255 } -- Play all ones, equal to AIS indications. 1014 ::= { pwTDMCfgEntry 20 } 1016 pwTDMCfgName OBJECT-TYPE 1017 SYNTAX SnmpAdminString 1018 MAX-ACCESS read-create 1019 STATUS current 1020 DESCRIPTION 1021 "A descriptive string, prefereably unique name, to an entry 1022 in this table. 1023 Object MAY be changed at any time." 1024 ::= { pwTDMCfgEntry 21 } 1026 -- End of Table 1028 -- The following counters work together to integrate 1029 -- errors and the lack of errors on the TDM PW. An error is 1030 -- caused by a missing packet. Missing packet can be a result 1031 -- of: packet loss in the network, (uncorrectable) packet out 1032 -- of sequence, packet length error, jitter buffer overflow, 1033 -- and jitter buffer underflow. The result is declaring whether 1034 -- or not the TDM PW is in Loss of Packet (LOPS) state. 1036 -- TDM PW Performance Current Table. 1038 pwTDMPerfCurrentTable OBJECT-TYPE 1039 SYNTAX SEQUENCE OF PwTDMPerfCurrentEntry 1040 MAX-ACCESS not-accessible 1041 STATUS current 1042 DESCRIPTION 1043 "The current 15 minute interval counts are in 1044 this table. 1046 This table provides per TDM PW performance information." 1048 ::= { pwTDMObjects 5 } 1050 pwTDMPerfCurrentEntry OBJECT-TYPE 1051 SYNTAX PwTDMPerfCurrentEntry 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "An entry in this table is created by the agent for every 1056 pwTDMTable entry. After 15 minutes, the contents of this 1057 table entry are copied to a new entry in the 1058 pwTDMPerfInterval table and the counts in this entry 1059 are reset to zero." 1061 INDEX { pwIndex } 1063 ::= { pwTDMPerfCurrentTable 1 } 1065 PwTDMPerfCurrentEntry ::= SEQUENCE { 1067 pwTDMPerfCurrentMissingPkts PerfCurrentCount, 1068 pwTDMPerfCurrentPktsReOrder PerfCurrentCount, 1069 pwTDMPerfCurrentJtrBfrUnderruns PerfCurrentCount, 1070 pwTDMPerfCurrentMisOrderDropped PerfCurrentCount, 1071 pwTDMPerfCurrentMalformedPkt PerfCurrentCount, 1073 pwTDMPerfCurrentESs PerfCurrentCount, 1074 pwTDMPerfCurrentSESs PerfCurrentCount, 1075 pwTDMPerfCurrentUASs PerfCurrentCount, 1076 pwTDMPerfCurrentFC PerfCurrentCount 1077 } 1079 pwTDMPerfCurrentMissingPkts OBJECT-TYPE 1080 SYNTAX PerfCurrentCount 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "Number of missing packets (as detected via control word 1085 sequence number gaps)." 1086 ::= { pwTDMPerfCurrentEntry 1 } 1088 pwTDMPerfCurrentPktsReOrder OBJECT-TYPE 1089 SYNTAX PerfCurrentCount 1090 MAX-ACCESS read-only 1091 STATUS current 1092 DESCRIPTION 1093 "Number of packets detected out of sequence (via control 1094 word sequence number), but successfully re-ordered. 1095 Note: some implementations may not support this Feature." 1096 ::= { pwTDMPerfCurrentEntry 2 } 1098 pwTDMPerfCurrentJtrBfrUnderruns OBJECT-TYPE 1099 SYNTAX PerfCurrentCount 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "Number of times a packet needed to be played 1104 out and the jitter buffer was empty." 1105 ::= { pwTDMPerfCurrentEntry 3 } 1107 pwTDMPerfCurrentMisOrderDropped OBJECT-TYPE 1108 SYNTAX PerfCurrentCount 1109 MAX-ACCESS read-only 1110 STATUS current 1111 DESCRIPTION 1112 "Number of packets detected out of order(via control word 1113 sequence numbers), and could not be re-ordered, or could 1114 not fit in the jitter buffer." 1115 ::= { pwTDMPerfCurrentEntry 4 } 1117 pwTDMPerfCurrentMalformedPkt OBJECT-TYPE 1118 SYNTAX PerfCurrentCount 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "Number of packets detected with unexpected size, or 1123 bad headers' stack" 1124 ::= { pwTDMPerfCurrentEntry 5 } 1126 pwTDMPerfCurrentESs OBJECT-TYPE 1127 SYNTAX PerfCurrentCount 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "The counter associated with the number of Error 1132 Seconds encountered. Any malformed packet, seq. error, LOPS 1133 and similar are considered as error second" 1134 ::= { pwTDMPerfCurrentEntry 6 } 1136 pwTDMPerfCurrentSESs OBJECT-TYPE 1137 SYNTAX PerfCurrentCount 1138 MAX-ACCESS read-only 1139 STATUS current 1140 DESCRIPTION 1141 "The counter associated with the number of 1142 Severely Error Seconds encountered. " 1143 ::= { pwTDMPerfCurrentEntry 7 } 1145 pwTDMPerfCurrentUASs OBJECT-TYPE 1146 SYNTAX PerfCurrentCount 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 "The counter associated with the number of 1151 Unavailable Seconds encountered. Any consequtive 1152 ten seconds of SES are counted as one UAS" 1153 ::= { pwTDMPerfCurrentEntry 8 } 1155 pwTDMPerfCurrentFC OBJECT-TYPE 1156 SYNTAX PerfCurrentCount 1157 MAX-ACCESS read-only 1158 STATUS current 1159 DESCRIPTION 1160 "TDM Failure Counts (FC-TDM). The number of TDM failure 1161 events. A failure event begins when the LOPS failure 1162 is declared, and ends when the failure is cleared. A 1163 failure event that begins in one period and ends in 1164 another period is counted only in the period in which 1165 it begins." 1166 ::= { pwTDMPerfCurrentEntry 9 } 1168 -- End TDM PW Performance Current Interval Table 1170 -- TDM PW Performance Interval Table. 1172 pwTDMPerfIntervalTable OBJECT-TYPE 1173 SYNTAX SEQUENCE OF PwTDMPerfIntervalEntry 1174 MAX-ACCESS not-accessible 1175 STATUS current 1176 DESCRIPTION 1177 "This table provides performance information per TDM PW 1178 similar to the pwTDMPerfCurrentTable above. However, 1179 these counts represent historical 15 minute intervals. 1180 Typically, this table will have a maximum of 96 entries 1181 for a 24 hour period, but is not limited to this. " 1182 ::= { pwTDMObjects 6 } 1184 pwTDMPerfIntervalEntry OBJECT-TYPE 1185 SYNTAX PwTDMPerfIntervalEntry 1186 MAX-ACCESS not-accessible 1187 STATUS current 1188 DESCRIPTION 1189 "An entry in this table is created by the agent for 1190 every pwTDMPerfCurrentEntry that is 15 minutes old. 1191 The contents of the Current entry are copied to the new 1192 entry here. The Current entry, then resets its counts 1193 to zero for the next current 15 minute interval. " 1195 INDEX { pwIndex, pwTDMPerfIntervalNumber } 1197 ::= { pwTDMPerfIntervalTable 1 } 1199 PwTDMPerfIntervalEntry ::= SEQUENCE { 1200 pwTDMPerfIntervalNumber Unsigned32, 1201 pwTDMPerfIntervalValidData TruthValue, 1202 pwTDMPerfIntervalDuration Unsigned32, 1204 pwTDMPerfIntervalMissingPkts PerfIntervalCount, 1205 pwTDMPerfIntervalPktsReOrder PerfIntervalCount, 1206 pwTDMPerfIntervalJtrBfrUnderruns PerfIntervalCount, 1207 pwTDMPerfIntervalMisOrderDropped PerfIntervalCount, 1208 pwTDMPerfIntervalMalformedPkt PerfIntervalCount, 1210 pwTDMPerfIntervalESs PerfIntervalCount, 1211 pwTDMPerfIntervalSESs PerfIntervalCount, 1212 pwTDMPerfIntervalUASs PerfIntervalCount, 1213 pwTDMPerfIntervalFC PerfIntervalCount 1214 } 1216 pwTDMPerfIntervalNumber OBJECT-TYPE 1217 SYNTAX Unsigned32 (1..96) 1218 MAX-ACCESS not-accessible 1219 STATUS current 1220 DESCRIPTION 1221 "A number (normally between 1 and 96 to cover a 24 hour 1222 period) which identifies the interval for which the set 1223 of statistics is available. The interval identified by 1 1224 is the most recently completed 15 minute interval, and 1225 the interval identified by N is the interval immediately 1226 preceding the one identified by N-1. The minimum range of 1227 N is 1 through 4. The default range is 1 through 32. The 1228 maximum value of N is 1 through 96." 1229 ::= { pwTDMPerfIntervalEntry 1 } 1231 pwTDMPerfIntervalValidData OBJECT-TYPE 1232 SYNTAX TruthValue 1233 MAX-ACCESS read-only 1234 STATUS current 1235 DESCRIPTION 1236 "This variable indicates if the data for this interval 1237 is valid." 1238 ::= { pwTDMPerfIntervalEntry 2 } 1240 pwTDMPerfIntervalDuration OBJECT-TYPE 1241 SYNTAX Unsigned32 1242 UNITS "seconds" 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "The duration of a particular interval in seconds, 1247 Adjustments in the system's time-of-day clock, may 1248 cause the interval to be greater or less than, the 1249 normal value. Therefore this actual interval value 1250 is provided." 1251 ::= { pwTDMPerfIntervalEntry 3 } 1253 pwTDMPerfIntervalMissingPkts OBJECT-TYPE 1254 SYNTAX PerfIntervalCount 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "Number of missing packets (as detected via control 1259 word sequence number gaps)." 1260 ::= { pwTDMPerfIntervalEntry 4 } 1262 pwTDMPerfIntervalPktsReOrder OBJECT-TYPE 1263 SYNTAX PerfIntervalCount 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "Number of packets detected out of sequence (via control 1268 word sequence number), but successfully re-ordered. 1269 Note: some implementations may not support this 1270 Feature." 1271 ::= { pwTDMPerfIntervalEntry 5 } 1273 pwTDMPerfIntervalJtrBfrUnderruns OBJECT-TYPE 1274 SYNTAX PerfIntervalCount 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "Number of times a packet needed to be played 1279 out and the jitter buffer was empty." 1280 ::= { pwTDMPerfIntervalEntry 6 } 1282 pwTDMPerfIntervalMisOrderDropped OBJECT-TYPE 1283 SYNTAX PerfIntervalCount 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Number of packets detected out of order(via control word 1288 sequence numbers), and could not be re-ordered, or could 1289 not fit in the jitter buffer." 1290 ::= { pwTDMPerfIntervalEntry 7 } 1292 pwTDMPerfIntervalMalformedPkt OBJECT-TYPE 1293 SYNTAX PerfIntervalCount 1294 MAX-ACCESS read-only 1295 STATUS current 1296 DESCRIPTION 1297 "Number of packets detected with unexpected size, or 1298 bad headers' stack" 1299 ::= { pwTDMPerfIntervalEntry 8 } 1301 pwTDMPerfIntervalESs OBJECT-TYPE 1302 SYNTAX PerfIntervalCount 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "The counter associated with the number of Error 1307 Seconds encountered." 1308 ::= { pwTDMPerfIntervalEntry 9 } 1310 pwTDMPerfIntervalSESs OBJECT-TYPE 1311 SYNTAX PerfIntervalCount 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "The counter associated with the number of 1316 Severely Error Seconds encountered." 1317 ::= { pwTDMPerfIntervalEntry 10 } 1319 pwTDMPerfIntervalUASs OBJECT-TYPE 1320 SYNTAX PerfIntervalCount 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "The counter associated with the number of 1325 Unavailable Seconds encountered." 1326 ::= { pwTDMPerfIntervalEntry 11 } 1328 pwTDMPerfIntervalFC OBJECT-TYPE 1329 SYNTAX PerfIntervalCount 1330 MAX-ACCESS read-only 1331 STATUS current 1332 DESCRIPTION 1333 "TDM Failure Counts (FC-TDM). The number of TDM failure 1334 events. A failure event begins when the LOPS failure 1335 is declared, and ends when the failure is cleared. A 1336 failure event that begins in one period and ends in 1337 another period is counted only in the period in which 1338 it begins." 1339 ::= { pwTDMPerfIntervalEntry 12 } 1341 -- End TDM PW Performance Interval Table 1343 -- TDM PW 1day Performance Table 1345 pwTDMPerf1DayIntervalTable OBJECT-TYPE 1346 SYNTAX SEQUENCE OF PwTDMPerf1DayIntervalEntry 1347 MAX-ACCESS not-accessible 1348 STATUS current 1349 DESCRIPTION 1350 "This table provides performance information per TDM PW 1351 similar to the pwTDMPerfIntervalTable above. However, 1352 these counters represent historical 1 day intervals up to 1353 one full month. The table consists of real time data, as 1354 such it is not persistence across re-boot." 1355 ::= { pwTDMObjects 7 } 1357 pwTDMPerf1DayIntervalEntry OBJECT-TYPE 1358 SYNTAX PwTDMPerf1DayIntervalEntry 1359 MAX-ACCESS not-accessible 1360 STATUS current 1361 DESCRIPTION 1362 "An entry is created in this table by the agent 1363 for every entry in the pwTDMTable table." 1365 INDEX { pwIndex,pwTDMPerf1DayIntervalNumber } 1367 ::= { pwTDMPerf1DayIntervalTable 1 } 1369 PwTDMPerf1DayIntervalEntry ::= SEQUENCE { 1370 pwTDMPerf1DayIntervalNumber Unsigned32, 1371 pwTDMPerf1DayIntervalValidData TruthValue, 1372 pwTDMPerf1DayIntervalDuration Unsigned32, 1373 pwTDMPerf1DayIntervalMissingPkts Counter32, 1374 pwTDMPerf1DayIntervalPktsReOrder Counter32, 1375 pwTDMPerf1DayIntervalJtrBfrUnderruns Counter32, 1376 pwTDMPerf1DayIntervalMisOrderDropped Counter32, 1377 pwTDMPerf1DayIntervalMalformedPkt Counter32, 1379 pwTDMPerf1DayIntervalESs Counter32, 1380 pwTDMPerf1DayIntervalSESs Counter32, 1381 pwTDMPerf1DayIntervalUASs Counter32, 1382 pwTDMPerf1DayIntervalFC Counter32 1383 } 1385 pwTDMPerf1DayIntervalNumber OBJECT-TYPE 1386 SYNTAX Unsigned32 (1..30) 1387 MAX-ACCESS not-accessible 1388 STATUS current 1389 DESCRIPTION 1390 "The number of interval, where 1 indicates current day 1391 measured period and 2 and above indicate previous days 1392 respectively" 1393 ::= { pwTDMPerf1DayIntervalEntry 1 } 1395 pwTDMPerf1DayIntervalValidData OBJECT-TYPE 1396 SYNTAX TruthValue 1397 MAX-ACCESS read-only 1398 STATUS current 1399 DESCRIPTION 1400 "This variable indicates if the data for this interval 1401 is valid." 1402 ::= { pwTDMPerf1DayIntervalEntry 2 } 1404 pwTDMPerf1DayIntervalDuration OBJECT-TYPE 1405 SYNTAX Unsigned32 1406 UNITS "seconds" 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "The duration of a particular interval in seconds, 1411 Adjustments in the system's time-of-day clock, may 1412 cause the interval to be greater or less than, the 1413 normal value. Therefore this actual interval value 1414 is provided." 1415 ::= { pwTDMPerf1DayIntervalEntry 3 } 1417 pwTDMPerf1DayIntervalMissingPkts OBJECT-TYPE 1418 SYNTAX Counter32 1419 MAX-ACCESS read-only 1420 STATUS current 1421 DESCRIPTION 1422 "Number of missing packets (as detected via control word 1423 sequence number gaps)." 1424 ::= { pwTDMPerf1DayIntervalEntry 4 } 1426 pwTDMPerf1DayIntervalPktsReOrder OBJECT-TYPE 1427 SYNTAX Counter32 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "Number of packets detected out of sequence (via control 1432 word sequence number), but successfully re-ordered. 1433 Note: some implementations may not support this 1434 feature." 1435 ::= { pwTDMPerf1DayIntervalEntry 5 } 1437 pwTDMPerf1DayIntervalJtrBfrUnderruns OBJECT-TYPE 1438 SYNTAX Counter32 1439 MAX-ACCESS read-only 1440 STATUS current 1441 DESCRIPTION 1442 "Number of times a packet needed to be played 1443 out and the jitter buffer was empty." 1444 ::= { pwTDMPerf1DayIntervalEntry 6 } 1446 pwTDMPerf1DayIntervalMisOrderDropped OBJECT-TYPE 1447 SYNTAX Counter32 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "Number of packets detected out of order(via control word 1452 sequence numbers), and could not be re-ordered, or could 1453 not fit in the jitter buffer." 1454 ::= { pwTDMPerf1DayIntervalEntry 7 } 1456 pwTDMPerf1DayIntervalMalformedPkt OBJECT-TYPE 1457 SYNTAX Counter32 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "Number of packets detected with unexpected size, or 1462 bad headers' stack." 1463 ::= { pwTDMPerf1DayIntervalEntry 8 } 1465 pwTDMPerf1DayIntervalESs OBJECT-TYPE 1466 SYNTAX Counter32 1467 MAX-ACCESS read-only 1468 STATUS current 1469 DESCRIPTION 1470 "The counter associated with the number of Error 1471 Seconds encountered." 1472 ::= { pwTDMPerf1DayIntervalEntry 9 } 1474 pwTDMPerf1DayIntervalSESs OBJECT-TYPE 1475 SYNTAX Counter32 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "The counter associated with the number of Severely 1480 Error Seconds." 1481 ::= { pwTDMPerf1DayIntervalEntry 10 } 1483 pwTDMPerf1DayIntervalUASs OBJECT-TYPE 1484 SYNTAX Counter32 1485 MAX-ACCESS read-only 1486 STATUS current 1487 DESCRIPTION 1488 "The counter associated with the number of 1489 UnAvailable Seconds. 1491 NOTE: When first entering the UAS state, the number 1492 of SES To UAS is added to this object, then as each 1493 additional UAS occurs, this object increments by one." 1495 ::= { pwTDMPerf1DayIntervalEntry 11 } 1497 pwTDMPerf1DayIntervalFC OBJECT-TYPE 1498 SYNTAX Counter32 1499 MAX-ACCESS read-only 1500 STATUS current 1501 DESCRIPTION 1502 "TDM Failure Counts (FC-TDM). The number of TDM failure 1503 events. A failure event begins when the LOPS failure 1504 is declared, and ends when the failure is cleared." 1505 ::= { pwTDMPerf1DayIntervalEntry 12 } 1507 -- End of PW TDM Performance table 1509 -- Conformance Information 1511 pwTDMCompliances OBJECT IDENTIFIER ::= { pwTDMConformance 1 } 1512 pwTDMGroups OBJECT IDENTIFIER ::= { pwTDMConformance 2 } 1514 pwTDMModuleCompliance MODULE-COMPLIANCE 1515 STATUS current 1516 DESCRIPTION 1517 "The compliance statement for agent that support TDM PW 1518 over PSN operation." 1520 MODULE -- this module 1521 MANDATORY-GROUPS { pwTDMGroup, 1522 pwTDMPerfCurrentGroup, 1523 pwTDMPerfIntervalGroup, 1524 pwTDMPerf1DayIntervalGroup 1525 } 1527 OBJECT pwGenTDMCfgIndex 1528 MIN-ACCESS read-only 1529 DESCRIPTION 1530 "The ability to set an index pointer 1531 is not required." 1533 OBJECT pwRelTDMCfgIndex 1534 MIN-ACCESS read-only 1535 DESCRIPTION 1536 "The ability to set the an index pointer 1537 is not required." 1539 OBJECT pwTDMCfgPktReorder 1540 MIN-ACCESS read-only 1541 DESCRIPTION 1542 "The ability to set the packet reordering 1543 is not required.If the feature is not 1544 supported, the value set by the agent MUST 1545 be FALSE" 1547 OBJECT pwTDMCfgRtpHdrUsed 1548 MIN-ACCESS read-only 1549 DESCRIPTION 1550 "The ability to set whether to use the 1551 RTP header or not is not required." 1553 OBJECT pwTDMCfgPayloadSuppression 1554 MIN-ACCESS read-only 1555 DESCRIPTION 1556 "The ability to set this object is not 1557 required." 1559 OBJECT pwTDMCfgPktReplacePolicy 1560 MIN-ACCESS read-only 1561 DESCRIPTION 1562 "The ability to set the replace policy 1563 is not required." 1565 OBJECT pwTDMCfgStorageType 1566 MIN-ACCESS read-only 1567 DESCRIPTION 1568 "The ability to set the storage type is 1569 not required." 1571 OBJECT pwTDMCfgPktFiller 1572 MIN-ACCESS read-only 1573 DESCRIPTION 1574 "The ability to set the Filler pattern 1575 is not required." 1577 OBJECT pwTDMCfgName 1578 MIN-ACCESS read-only 1579 DESCRIPTION 1580 "The ability to set the an Aliase 1581 is not required." 1583 ::= { pwTDMCompliances 1 } 1585 -- Units of conformance. 1587 pwTDMGroup OBJECT-GROUP 1588 OBJECTS { 1589 pwTDMRate, 1590 pwTDMIfIndex, 1591 pwGenTDMCfgIndex, 1592 pwRelTDMCfgIndex, 1593 pwTDMConfigError, 1594 pwTDMTimeElapsed, 1595 pwTDMValidIntervals, 1596 pwTDMValidDayIntervals, 1598 pwTDMLastEsTimeStamp, 1600 pwTDMCfgIndexNext, 1602 pwTDMCfgRowStatus, 1604 pwTDMCfgPayloadSize, 1605 pwTDMCfgPktReorder, 1606 pwTDMCfgRtpHdrUsed, 1607 pwTDMCfgJtrBfrDepth, 1608 pwTDMCfgPayloadSuppression, 1609 pwTDMCfgConsecPktsInSynch, 1610 pwTDMCfgConsecMissPktsOutSynch, 1611 pwTDMCfgSetUp2SynchTimeOut, 1613 pwTDMCfgPktReplacePolicy, 1615 pwTDMCfgAvePktLossTimeWindow , 1616 pwTDMCfgExcessivePktLossThreshold, 1618 pwTDMCfgAlarmThreshold , 1619 pwTDMCfgClearAlarmThreshold, 1620 pwTDMCfgMissingPktsToSes, 1622 pwTDMCfgTimestampMode, 1623 pwTDMCfgStorageType, 1624 pwTDMCfgPktFiller, 1625 pwTDMCfgName 1626 } 1627 STATUS current 1628 DESCRIPTION 1629 "Collection of objects for basic TDM PW config and 1630 status." 1631 ::= { pwTDMGroups 1 } 1633 pwTDMPerfCurrentGroup OBJECT-GROUP 1634 OBJECTS { 1635 pwTDMPerfCurrentMissingPkts, 1636 pwTDMPerfCurrentPktsReOrder, 1637 pwTDMPerfCurrentJtrBfrUnderruns, 1638 pwTDMPerfCurrentMisOrderDropped, 1639 pwTDMPerfCurrentMalformedPkt, 1641 pwTDMPerfCurrentESs, 1642 pwTDMPerfCurrentSESs, 1643 pwTDMPerfCurrentUASs, 1644 pwTDMPerfCurrentFC 1645 } 1646 STATUS current 1647 DESCRIPTION 1648 "Collection of current statistics objects for TDM PWs." 1649 ::= { pwTDMGroups 2 } 1651 pwTDMPerfIntervalGroup OBJECT-GROUP 1652 OBJECTS { 1653 pwTDMPerfIntervalValidData, 1654 pwTDMPerfIntervalDuration, 1656 pwTDMPerfIntervalMissingPkts, 1657 pwTDMPerfIntervalPktsReOrder, 1658 pwTDMPerfIntervalJtrBfrUnderruns, 1659 pwTDMPerfIntervalMisOrderDropped, 1660 pwTDMPerfIntervalMalformedPkt, 1662 pwTDMPerfIntervalESs, 1663 pwTDMPerfIntervalSESs, 1664 pwTDMPerfIntervalUASs, 1665 pwTDMPerfIntervalFC 1667 } 1668 STATUS current 1669 DESCRIPTION 1670 "Collection of Interval statistics objects for TDM PWs." 1671 ::= { pwTDMGroups 3 } 1673 pwTDMPerf1DayIntervalGroup OBJECT-GROUP 1674 OBJECTS { 1675 pwTDMPerf1DayIntervalValidData, 1676 pwTDMPerf1DayIntervalDuration, 1677 pwTDMPerf1DayIntervalMissingPkts, 1678 pwTDMPerf1DayIntervalPktsReOrder, 1679 pwTDMPerf1DayIntervalJtrBfrUnderruns, 1680 pwTDMPerf1DayIntervalMisOrderDropped, 1681 pwTDMPerf1DayIntervalMalformedPkt, 1683 pwTDMPerf1DayIntervalESs, 1684 pwTDMPerf1DayIntervalSESs, 1685 pwTDMPerf1DayIntervalUASs, 1686 pwTDMPerf1DayIntervalFC 1687 } 1688 STATUS current 1689 DESCRIPTION 1690 "Collection of Daily statistics objects for TDM PWs." 1691 ::= { pwTDMGroups 4 } 1693 END 1695 9. Security considerations 1697 It is clear that this MIB module is potentially useful for monitoring 1698 of TDM PWs. This MIB can also be used for configuration of certain 1699 objects, and anything that can be configured can be incorrectly 1700 configured, with potentially disastrous results. 1702 There are a number of management objects defined in this MIB module 1703 with a MAX-ACCESS clause of read-write and/or read-create. Such 1704 objects may be considered sensitive or vulnerable in some network 1705 environments. The support for SET operations in a non-secure 1706 environment without proper protection can have a negative effect on 1707 network operations. These are the tables and objects and their 1708 sensitivity/vulnerability: 1710 The pwTDMTable and pwTDMCfgTable contain objects of TDM PW parameters 1711 on a Provider Edge (PE) device. Unauthorized access to objects in 1712 these tables could result in disruption of traffic on the network. 1714 The use of stronger mechanisms such as SNMPv3 security should be 1715 considered where possible. Specifically, SNMPv3 VACM and USM MUST be 1716 used with any SNMPV3 agent, which implements this MIB module. 1718 Administrators should consider whether read access to these objects 1719 should be allowed, since read access may be undesirable under certain 1720 circumstances. 1722 Some of the readable objects in this MIB module (i.e., objects with a 1723 MAX-ACCESS other than not-accessible) may be considered sensitive or 1724 vulnerable in some network environments. It is thus important to 1725 control even GET and/or NOTIFY access to these objects and possibly 1726 to even encrypt the values of these objects when sending them over 1727 the network via SNMP. These are the tables and objects and their 1728 sensitivity/vulnerability: 1730 The pwTDMTable, pwTDMPerfCurrentTable, pwTDMPerfIntervalTable and 1731 pwTDMPerf1DayIntervalTable collectively show the TDM pseudo wire 1732 connectivity topology and its performance characteristics. 1734 If an Administrator does not want to reveal this information, then 1735 these tables should be considered sensitive/vulnerable. 1737 SNMP versions prior to SNMPv3 did not include adequate security. 1738 Even if the network itself is secure (for example by using IPsec), 1739 even then, there is no control as to who on the secure network is 1740 allowed to access and GET/SET (read/change/create/delete) the objects 1741 in this MIB module. 1743 It is RECOMMENDED that implementers consider the security features as 1744 provided by the SNMPv3 framework (see [RFC3410], section 8), 1745 including full support for the SNMPv3 cryptographic mechanisms (for 1746 authentication and privacy). 1748 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1749 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1750 enable cryptographic security. It is then a customer/operator 1751 responsibility to ensure that the SNMP entity giving access to an 1752 instance of this MIB module, is properly configured to give access to 1753 the objects only to those principals (users) that have legitimate 1754 rights to indeed GET or SET (change/create/delete) them. 1756 10. IANA considerations 1758 The MIB module in this document uses the following IANA-assigned 1759 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1761 Descriptor OBJECT IDENTIFIER value 1763 ---------- ----------------------- 1764 pwTDMMIB { mib-2 XXX } 1766 Editor's Note (to be removed prior to publication): the IANA is 1767 requested to assign a value for "XXX" under the mib-2 subtree and to 1768 record the assignment in the SMI Numbers registry. When the 1769 assignment has been made, the RFC Editor is asked to replace "XXX" 1770 (here and in the MIB module) with the assigned value and to remove 1771 this note. 1773 11. References 1775 11.1. Normative references 1777 [SATOP] Vainshtein A. ,Stein Y., "Structure-Agnostic TDM 1778 over Packet (SAToP)", RFC 4553, June 2006. 1780 [TDMCP-EXT] Vainshtein A, Stein Y., "Control Protocol Extensions 1781 for Setup of TDM Pseudowires", work-in-progress. 1783 [PWMIB] Zelig D., Nadeau T., "Pseudo Wire (PW) Management 1784 Information Base", work-in-progress. 1786 [PWTC] Nadeau, T., Zelig D. "Definitions for Textual 1787 Conventions and OBJECT-IDENTITIES for Pseudo-Wires 1788 Management", work-in-progress. 1790 [DS1MIB] Nicklass O. " Definitions of Managed Objects 1791 for the DS1, E1, DS2 and E2 Interface Types", RFC 4805, 1792 September 2004 1794 [DS3MIB] Nicklass O. "Definitions of Managed Objects for 1795 the DS3/E3 Interface Types", RFC 3896, September 2004 1797 [DS0MIB] Fowler, D., "Definitions of Managed Objects for 1798 the DS0 and DS0Bundle Interface Types", RFC 2494, 1799 January 1999. 1801 [IFMIB] McCloghrie, K. and F. Kastenholz, "The Interfaces 1802 Group MIB", RFC 2863, June 2000. 1804 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1805 J., Rose, M. and S. Waldbusser, "Structure of 1806 Management Information Version 2 (SMIv2)", STD 58, RFC 1807 2578, April 1999. 1809 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1810 J., Rose, M. and S. Waldbusser, "Textual Conventions 1811 for SMIv2", STD 58, RFC 2579, April 1999. 1813 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1814 J., Rose, M. and S. Waldbusser, "Conformance 1815 Statements for SMIv2", STD 58, RFC 2580, April 1999. 1817 [RFC3411] D. Harrington, R. Presuhn,B. Wijnen "An Architecture 1818 for Describing Simple Network Management Protocol 1819 (SNMP) Management Frameworks", RFC 3411, December 2002 1821 [BCP14] S. Bradner, "Key words for use in RFCs to Indicate 1822 Requirement Levels", RFC 2119 (BCP 14), March 1997 1824 11.2. Informative references 1826 [RFC4197] M. Riegel, et al, "Requirements for Edge-to-Edge 1827 Emulation of TDM Circuits over Packet Switching 1828 Networks (PSN)", RFC 4197,October 2005. 1830 [RFC3985] Bryant S., Pate P., "PWE3 Architecture", RFC 3985, 1831 March 2005. 1833 [TDMOIP] Y(J) Stein, Shashoua R., Insler, M. Anavi "TDM 1834 over IP", work in progress. 1836 [CESOPSN] Vainshtein A. et al, "Structured TDM Circuit 1837 Emulation Service over Packet Switched Network 1838 (CESoPSN)", work in progress. 1840 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1841 "Introduction and Applicability Statements for 1842 Internet-Standard Management Framework", RFC 3410, 1843 December 2002. 1845 12. Acknowledgements 1847 This document was produced by the PWE3 Working Group. Special thanks 1848 to Yaakov Stein, Doron Tzur, Sasha Vainshtein; and Ron Cohen; for 1849 close review and good suggestions. 1851 Author's Address 1853 Orly Nicklass 1854 RADVISION Ltd. 1855 24 Raul Wallenberg St. 1856 Tel Aviv 1857 ISRAEL 1859 Phone: +972 3 7679444 1860 Email: orlyn@radvision.com 1862 Full Copyright Statement 1864 Copyright (C) The IETF Trust (2008). 1866 This document is subject to the rights, licenses and restrictions 1867 contained in BCP 78, and except as set forth therein, the authors 1868 retain all their rights. 1870 This document and the information contained herein are provided on an 1871 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1872 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1873 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1874 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1875 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1876 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1878 Intellectual Property 1880 The IETF takes no position regarding the validity or scope of any 1881 Intellectual Property Rights or other rights that might be claimed to 1882 pertain to the implementation or use of the technology described in 1883 this document or the extent to which any license under such rights 1884 might or might not be available; nor does it represent that it has 1885 made any independent effort to identify any such rights. Information 1886 on the procedures with respect to rights in RFC documents can be 1887 found in BCP 78 and BCP 79. 1889 Copies of IPR disclosures made to the IETF Secretariat and any 1890 assurances of licenses to be made available, or the result of an 1891 attempt made to obtain a general license or permission for the use of 1892 such proprietary rights by implementers or users of this 1893 specification can be obtained from the IETF on-line IPR repository at 1894 http://www.ietf.org/ipr. 1896 The IETF invites any interested party to bring to its attention any 1897 copyrights, patents or patent applications, or other proprietary 1898 rights that may cover technology that may be required to implement 1899 this standard. Please address the information to the IETF at 1900 ietf-ipr@ietf.org.