idnits 2.17.1 draft-ietf-ipcdn-tri-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 25 longer pages, the longest (page 2) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 26 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 3. Overview' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 7. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 93 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 30 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references ([20], [15], [2], [21], [16], [3], [22], [4], [23], [5], [24], [19], [6], [7], [8], [9], [10], [11], [12], [18,20], [13], [14], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 176: '...hony Return CMTS MUST support the obje...' RFC 2119 keyword, line 179: '... telephony modem MAY use the Modem Man...' RFC 2119 keyword, line 541: '...alue reserved to indicate CM MUST...' RFC 2119 keyword, line 552: '...rver domain. TRAC RADIUS MUST proxy...' RFC 2119 keyword, line 555: '... String MUST be correlated by the ...' (3 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 279 has weird spacing: '... may be'Tel...' == Line 294 has weird spacing: '... may be opera...' == Line 314 has weird spacing: '...ins the infor...' == Line 333 has weird spacing: '... either a CA...' == Line 335 has weird spacing: '..., this objec...' == (88 more instances...) -- 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 (April 2, 1999) is 9155 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 section? '5' on line 193 looks like a reference -- Missing reference section? '6' on line 384 looks like a reference -- Missing reference section? '7' on line 86 looks like a reference -- Missing reference section? '1' on line 80 looks like a reference -- Missing reference section? '2' on line 85 looks like a reference -- Missing reference section? '3' on line 85 looks like a reference -- Missing reference section? '4' on line 85 looks like a reference -- Missing reference section? '8' on line 98 looks like a reference -- Missing reference section? '9' on line 92 looks like a reference -- Missing reference section? '10' on line 94 looks like a reference -- Missing reference section? '11' on line 94 looks like a reference -- Missing reference section? '12' on line 94 looks like a reference -- Missing reference section? '13' on line 99 looks like a reference -- Missing reference section? '14' on line 101 looks like a reference -- Missing reference section? '15' on line 102 looks like a reference -- Missing reference section? '16' on line 164 looks like a reference -- Missing reference section? '19' on line 169 looks like a reference -- Missing reference section? '20' on line 635 looks like a reference -- Missing reference section? '21' on line 187 looks like a reference -- Missing reference section? '22' on line 187 looks like a reference -- Missing reference section? '23' on line 187 looks like a reference -- Missing reference section? '24' on line 188 looks like a reference -- Missing reference section? '18' on line 635 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 9 warnings (==), 25 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT DOCSIS Telephony-Return MIB April 2, 3 1999 5 Telephony-Return Interface (TRI) Management Information Base 6 for DOCSIS-compliant Telephony-Return Cable Modems and 7 Cable Modem Termination Systems 8 10 S. Adiraju 11 J. Fijolek 12 Jack_Fijolek@3Com.com 13 3Com Corp 14 April 2, 1999 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with 19 all provisions of Section 10 of RFC2026. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Abstract 39 This memo defines an experimental portion of the Management 40 Information Base (MIB) for use with network management protocols in 41 the Internet community. In particular, it defines a basic set of 42 managed objects for SNMP-based management of DOCSIS compliant Cable 43 Modems and Cable Modem Termination Systems. This memo specifies a 44 MIB module in a manner that is compliant to the SNMP SMIv2[5][6][7]. 45 The set of objects is consistent with the SNMP framework and existing 46 SNMP standards. This memo is a product of the IPCDN working group 47 within the Internet Engineering Task Force. Comments are solicited 48 and should be addressed to the working group's mailing list at 49 ipcdn@terayon.com and/or the author. 51 Table of Contents 53 1 The SNMP Management Framework ...................................1 54 2 Glossary ........................................................2 55 2.1 CATV ..........................................................2 56 2.2 CM ............................................................2 57 2.3 CMTS ..........................................................2 58 2.4 DOCSIS ........................................................2 59 2.5 Downstream ....................................................2 60 2.6 Head-end ......................................................3 61 2.7 MAC Packet ....................................................3 62 2.8 MCNS ..........................................................3 63 2.9 RF ............................................................3 64 2.10 Upstream .....................................................3 65 3 Overview ........................................................3 66 3.1 Discussion ....................................................3 67 3.2 Management requirements .......................................4 68 3.2.1 Handling of Service Provider Descriptor (SPD) Updates .......4 69 4 Definitions .....................................................5 70 5 Acknowledgments .................................................23 71 6 References ......................................................23 72 7 Security Considerations .........................................25 73 8 Intellectual Property ...........................................25 74 9 Copyright Section ...............................................25 75 10 Author's Address ...............................................26 77 1. The SNMP Management Framework 78 The SNMP Management Framework presently consists of five major 79 components: 80 An overall architecture, described in RFC 2271 [1]. 82 o Mechanisms for describing and naming objects and events for the 83 purpose of management. The first version of this Structure of 84 Management Information (SMI) is called SMIv1 and described in RFC 85 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 86 SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. 88 o Message protocols for transferring management information. The 89 first version of the SNMP message protocol is called SNMPv1 and 90 described in RFC 1157 [8]. A second version of the SNMP message 91 protocol, which is not an Internet standards track protocol, is 92 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The 93 third version of the message protocol is called SNMPv3 and 94 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 96 o Protocol operations for accessing management information. The first 97 set of protocol operations and associated PDU formats is described 98 in RFC 1157 [8]. A second set of protocol operations and associated 99 PDU formats is described in RFC 1905 [13]. 101 o A set of fundamental applications described in RFC 2273 [14] and 102 the view-based access control mechanism described in RFC 2275 [15]. 103 Managed objects are accessed via a virtual information store, termed 104 the Management Information Base or MIB. Objects in the MIB are 105 defined using the mechanisms defined in the SMI. 106 This memo specifies a MIB module that is compliant to the SMIv2. A 107 MIB conforming to the SMIv1 can be produced through the appropriate 108 translations. The resulting translated MIB must be semantically 109 equivalent, except where objects or events are omitted because no 110 translation is possible (use of Counter64). Some machine readable 111 information in SMIv2 will be converted into textual descriptions in 112 SMIv1 during the translation process. However, this loss of machine 113 readable information is not considered to change the semantics of the 114 MIB. 116 2. Glossary 117 The terms in this document are derived either from normal cable 118 system usage, or from the documents associated with the Data Over 119 Cable Service Interface Specification process. 120 2.1 CATV 122 Originally "Community Antenna Television", now used to refer to any 123 cable or hybrid fiber and cable system used to deliver video signals 124 to a community. 126 2.2 CM 128 Cable Modem. A CM acts as a "slave" station in a DOCSIS compliant 129 cable data system. 131 2.3 CMTS 133 Cable Modem Termination System. A generic term covering a cable 134 bridge or cable router in a head-end. A CMTS acts as the master 135 station in a DOCSIS compliant cable data system. It is the only 136 station that transmits downstream, and it controls the scheduling of 137 upstream transmissions by its associated CMs. 139 2.4 DOCSIS 141 Data Over Cable System Interface Specifications 143 2.5 Downstream 144 From the head-end towards the subscriber. 146 2.6 Head-end 148 The origination point in most cable systems of the subscriber video 149 signals. Generally also the location of the CMTS equipment. 151 2.7 RF 153 Radio Frequency. 155 2.8 Upstream 157 From the subscriber towards the headend via PSTN. 159 3. Overview 161 This MIB provides a set of objects required for the management of 162 DOCSIS compliant Cable Modems (CM) and Cable Modem Termination 163 Systems (CMTS). The specification is derived from the DOCSIS Radio 164 Frequency Interface specification [16]. 166 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 167 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 168 document are to be interpreted as described in [19] 170 3.1 Discussion 172 The data-over-cable-system telephony return interface specification 173 is documented in [20]. The management requirements of this interface 174 are detailed in that specification. Specific inferences to other 175 controls are itemized in the following list: The Telephony Return CM 176 and telephony Return CMTS MUST support the objects in the DOCSIS 177 Cable Device MIB [21] and DOCSIS RFI MIB [22] that are applicable to 178 downstream only. In a Telephony Return CM, the management of the 179 telephony modem MAY use the Modem Management Information Base (MIB) 180 using SMIv2 [23]. These objects generally require proprietary 181 handling to address the telephony modems serial AT command interface. 182 It is not reasonable to require MIB support for all third party dial 183 modems. However, if a dial modem is integrated within a cable modem 184 product, using a subset of the RFC1696 Modem MIB objects to control 185 the dial modem is practical and reasonable. Guidelines for dial 186 modem physical capabilities are provided in [20]. Guidelines for 187 specific applicability of [21], [22], and [23] for telephony return 188 systems are provided in [24]. 190 3.2 Management Requirements 191 3.2.1 Handling Of Service Provider Descriptor (SPD) Updates 193 The Cable Modem service provider option process is documented in [5]. 194 An operator creates service provider descriptors (SPDs) that the CMTS 195 will send to all CMs in its domain. The operator must signify one 196 entry as factory default for initial dial-in service for a 197 subscriber. An external telco-return modem may have objects within 198 the selected SPD modified by changing corresponding scalar objects on 199 a CM using the network management station. 200 One reason for the SNMP-initiated SPD update is to allow loading of 201 permanent Telephone Numbers, Login Usernames and Login Passwords 202 without requiring individualized configuration files on a per CM 203 basis. 205 For example the operator MAY: 207 o set docsTrTsSPDphoneNum1 to dial a temporary access Telephone 208 Number. A factory default CM user may then be given some limited 209 access by using default values for all other SPD objects. 211 o Temporary system access may be upgraded after an undefined operator 212 specified authentication. The operator may then set 213 docsTrTsSPDphoneNum1, docsTrTsSPDuserName, docsTrTsSPDuserPassword 214 (phone/login/password) or any other CM SPD objects to 215 individualized settings. 217 o These settings remain in effect unless changed by Telephone 218 Settings Options in the CMs TFTP configuration file. 220 o The operator may want to change individual Telephone Settings 221 Options for CMs sharing a global TFTP configuration file. For 222 example, the DHCP Server (ip address) can be changed for all CMs 223 sharing a configuration file without affecting any other active SPD 224 settings by having just DHCP server parameter set in the file. All 225 other MIB modified SPD parameters would remain active (excepting 226 docsTrTsSPDdhcpAddress MIB object) if docsTrCmSPDpersistEnable is 227 TRUE. 229 4. Definitions 231 TelcoReturnCABLE-DEVICE-MIB DEFINITIONS ::= BEGIN 233 IMPORTS 234 MODULE-IDENTITY, OBJECT-TYPE, 235 Integer32, IpAddress, Unsigned32 236 FROM SNMPv2-SMI 237 DisplayString, DateAndTime, TruthValue, RowStatus 238 FROM SNMPv2-TC 239 OBJECT-GROUP, MODULE-COMPLIANCE 240 FROM SNMPv2-CONF 241 InterfaceIndexOrZero 242 FROM DOCS-IF-MIB 243 transmission 244 FROM RFC1213-MIB 245 ; 247 docsTrCmMIB MODULE-IDENTITY 248 LAST-UPDATED "9904020720Z" 249 ORGANIZATION "3Com - Cable Access" 250 CONTACT-INFO " Jack Fijolek/Srinivyasa Murthy 251 Adiraju 252 Postal: 3Com 253 3800 Golf Road 254 Rolling Meadows, IL 60008 255 Tel: +1 847 2622201 +1 847 2622205 256 Fax: +1 847 2620258 257 E-mail: Srinivyasa_Adiraju@3Com.com" 258 DESCRIPTION 259 "TELCO Return MIB for Data Over Cable Access 260 modems and termination systems" 261 ::= { transmission 128 } 263 docsTrCmMIBObjects OBJECT IDENTIFIER ::= 264 {docsTrCmMIB 1} 265 docsTrCmBase OBJECT IDENTIFIER ::= { 266 docsTrCmMIBObjects 1} 268 docsTrCmCapability OBJECT-TYPE 269 SYNTAX INTEGER { 270 other(1), 271 telcoReturn(2), 272 twoWay(3), 273 threeWay(4) 274 } 275 MAX-ACCESS read-only 276 STATUS current 277 DESCRIPTION 278 "This object represents the CM Capability. A CM 279 may be'TelcoReturn(2)', or 'TwoWay(3)', or Other e.g., 280 undefined" 281 ::= { docsTrCmBase 1 } 283 docsTrCmMode OBJECT-TYPE 284 SYNTAX INTEGER { 285 other(1), 286 telcoReturn(2), 287 twoWay(3) 289 } 290 MAX-ACCESS read-write 291 STATUS current 292 DESCRIPTION 293 "This object represents the CM Operating Mode. A 294 CM may be operating as'TelcoReturn(2)', or 'TwoWay(3)', or 295 Other e.g, undefined" 296 ::= { docsTrCmBase 2 } 298 docsTrMsgBase OBJECT IDENTIFIER ::= { 299 docsTrCmMIBObjects 2} 301 docsTrMsgBaseTable OBJECT-TYPE 302 SYNTAX SEQUENCE OF DocsTrMsgBaseEntry 303 MAX-ACCESS not-accessible 304 STATUS current 305 DESCRIPTION 306 "Telco Return Message Base Table" 307 ::= { docsTrMsgBase 1 } 309 docsTrMsgBaseEntry OBJECT-TYPE 310 SYNTAX DocsTrMsgBaseEntry 311 MAX-ACCESS not-accessible 312 STATUS current 313 DESCRIPTION 314 "This table contains the information 315 about TCD/TSI and USRbackOff for each interface" 316 INDEX { docsTrMsgIfIndex } 317 ::= { docsTrMsgBaseTable 1 } 319 DocsTrMsgBaseEntry ::= SEQUENCE { 320 docsTrMsgIfIndex InterfaceIndexOrZero, 321 docsTrMsgTCDInterval INTEGER, 322 docsTrMsgTSIInterval INTEGER, 323 docsTrMsgUSRBackOff Unsigned32, 324 docsTrMsgRowValue RowStatus 325 } 327 docsTrMsgIfIndex OBJECT-TYPE 328 SYNTAX InterfaceIndexOrZero 329 MAX-ACCESS not-accessible 330 STATUS current 331 DESCRIPTION 332 "The value corresponds to ifIndex for 333 either a CATV MAC or other network interface. In Cable 334 Modems, the default value is the customer side interface. In 335 Cable Modem Termination Systems, this object has to be 336 specified to create a row in this table." 337 ::= { docsTrMsgBaseEntry 1 } 339 docsTrMsgTCDInterval OBJECT-TYPE 340 SYNTAX INTEGER (500..2000) 341 UNITS "Milliseconds" 342 MAX-ACCESS read-write 343 STATUS current 344 DESCRIPTION 345 "The interval between CMTS transmission of 346 successive Telephony Channel Descriptor (TCD) messages at 347 this interface." 348 REFERENCE 349 "Data Over Cable Telephony Return Interface 350 Specification,[1], TCD Interval." 351 DEFVAL { 2000 } 352 ::= { docsTrMsgBaseEntry 2 } 354 docsTrMsgTSIInterval OBJECT-TYPE 355 SYNTAX INTEGER (1000..4000) 356 UNITS "Milliseconds" 357 MAX-ACCESS read-write 358 STATUS current 359 DESCRIPTION 360 "The interval between CMTS transmission of 361 successive Termination System Interface (TSI) messages for a 362 downstream channel at this interface.This is also the time 363 interval a CM should scan on a specific channel for a TSI 364 message and sets the frequency the CM monitors the CMTS 365 epoch counter. " 366 REFERENCE 367 "Data Over Cable Telephony Return Interface 368 Specification,[6], TSI Interval." 369 DEFVAL { 4000 } 370 ::= { docsTrMsgBaseEntry 3 } 372 docsTrMsgUSRBackOff OBJECT-TYPE 373 SYNTAX Unsigned32 374 MAX-ACCESS read-write 375 STATUS current 376 DESCRIPTION 377 " This object represents the number of times 378 CMTS will resend User Station Reset messages if 379 unacknowledged by CM; Number of duplicate reset requests CM 380 may receive" 381 DEFVAL{4} 382 REFERENCE 383 "Data Over Cable Telephony Return Interface 384 Specification, [6], USR Backoff ." 385 ::= { docsTrMsgBaseEntry 4 } 387 docsTrMsgRowValue OBJECT-TYPE 388 SYNTAX RowStatus 389 MAX-ACCESS read-write 390 STATUS current 391 DESCRIPTION 392 " Controls and reflects the status of rows in 393 this table " 394 ::= { docsTrMsgBaseEntry 5 } 396 docsTrTsSPD OBJECT IDENTIFIER ::= { docsTrCmMIBObjects 397 3} 399 docsTrTsSPDTable OBJECT-TYPE 400 SYNTAX SEQUENCE OF DocsTrTsSPDEntry 401 MAX-ACCESS not-accessible 402 STATUS current 403 DESCRIPTION 404 " A table of all the SPD messages that get sent 405 out" 406 ::= { docsTrTsSPD 1 } 408 docsTrTsSPDEntry OBJECT-TYPE 409 SYNTAX DocsTrTsSPDEntry 410 MAX-ACCESS not-accessible 411 STATUS current 412 DESCRIPTION 413 "This an entry in the SPD table which is one of 414 the SPD that get sent outto the cable modems" 415 INDEX {docsTrTsSPDindex} 416 ::= {docsTrTsSPDTable 1} 418 DocsTrTsSPDEntry ::= SEQUENCE { 419 docsTrTsSPDindex INTEGER, 420 docsTrTsSPDname DisplayString, 421 docsTrTsSPDphoneNum1 DisplayString, 422 docsTrTsSPDphoneNum2 DisplayString, 423 docsTrTsSPDphoneNum3 DisplayString, 424 docsTrTsSPDConnThreshold Integer32, 425 docsTrTsSPDuserName DisplayString, 426 docsTrTsSPDuserPassword OCTET STRING, 427 docsTrTsSPDpppAuth INTEGER, 428 docsTrTsSPDdhcpAuth INTEGER, 429 docsTrTsSPDradiusRealm DisplayString, 430 docsTrTsDemandDialTimer Unsigned32, 431 docsTrTsSPDdhcpAddress IpAddress, 432 docsTrTsSPDfactoryDef INTEGER, 433 docsTrTsSPDstatus INTEGER 435 } 437 docsTrTsSPDindex OBJECT-TYPE 438 SYNTAX INTEGER(1..16383) 439 MAX-ACCESS not-accessible 440 STATUS current 441 DESCRIPTION 442 "The unique number which identifies the Service 443 Provider Descriptor in the SPDTable" 444 ::= { docsTrTsSPDEntry 1} 446 docsTrTsSPDname OBJECT-TYPE 447 SYNTAX DisplayString (SIZE(1..128)) 448 MAX-ACCESS read-create 449 STATUS current 450 DESCRIPTION 451 "The name of the Service Provider. A value of 452 null string means no name" 453 DEFVAL { "" } 454 ::= { docsTrTsSPDEntry 2 } 456 docsTrTsSPDphoneNum1 OBJECT-TYPE 457 SYNTAX DisplayString (SIZE (1..128)) 458 MAX-ACCESS read-create 459 STATUS current 460 DESCRIPTION 461 "The first phone number to try when trying to 462 reach the service provider. A value of null string means no 463 phone number" 464 DEFVAL { "" } 465 ::= { docsTrTsSPDEntry 3 } 467 docsTrTsSPDphoneNum2 OBJECT-TYPE 468 SYNTAX DisplayString (SIZE (1..128)) 469 MAX-ACCESS read-create 470 STATUS current 471 DESCRIPTION 472 "The second phone number to try to reach the 473 service provider when the first number fails. A value of 474 null string means no phone number" 475 DEFVAL { "" } 476 ::= { docsTrTsSPDEntry 4 } 478 docsTrTsSPDphoneNum3 OBJECT-TYPE 479 SYNTAX DisplayString (SIZE (1..128)) 480 MAX-ACCESS read-create 481 STATUS current 482 DESCRIPTION 483 "The third phone number to try in case the 1st 484 and 2nd numbers fail. A value of null string means no phone 485 number" 486 DEFVAL { "" } 487 ::= { docsTrTsSPDEntry 5 } 489 docsTrTsSPDConnThreshold OBJECT-TYPE 490 SYNTAX Integer32 (1..10) 491 MAX-ACCESS read-create 492 STATUS current 493 DESCRIPTION 494 "The number of sequential connection try failures 495 before indicating connection failure. " 496 DEFVAL { 1 } 497 ::= { docsTrTsSPDEntry 6 } 499 docsTrTsSPDuserName OBJECT-TYPE 500 SYNTAX DisplayString (SIZE (1..32)) 501 MAX-ACCESS read-create 502 STATUS current 503 DESCRIPTION 504 "The username the CM will use during PAP or CHAP 505 authentication over telco link during the initialization 506 procedure." 507 DEFVAL { "guest" } 508 ::= { docsTrTsSPDEntry 7 } 510 docsTrTsSPDuserPassword OBJECT-TYPE 511 SYNTAX OCTET STRING (SIZE (1..15)) 512 MAX-ACCESS read-create 513 STATUS current 514 DESCRIPTION 515 "The password that the CM will use during the PAP 516 or CHAP authentication over the telco link during the 517 initialization procedure." 518 DEFVAL { "" } 519 ::= { docsTrTsSPDEntry 8 } 521 docsTrTsSPDpppAuth OBJECT-TYPE 522 SYNTAX INTEGER { 523 other(1), 524 uNegotiate(2), 525 uPAP(3), 526 uCHAP(4) 527 } 528 MAX-ACCESS read-create 529 STATUS current 530 DESCRIPTION 531 "This instructs the telco return modem of the 532 authentication procedure to perform over the telco link." 533 DEFVAL { uNegotiate } 534 ::= { docsTrTsSPDEntry 9 } 536 docsTrTsSPDdhcpAuth OBJECT-TYPE 537 SYNTAX TruthValue 538 MAX-ACCESS read-create 539 STATUS current 540 DESCRIPTION 541 "Boolean value reserved to indicate CM MUST 542 authenticate DHCP messages when enable." 543 DEFVAL { False } 544 ::= { docsTrTsSPDEntry 10 } 546 docsTrTsSPDradiusRealm OBJECT-TYPE 547 SYNTAX DisplayString (SIZE(0..128)) 548 MAX-ACCESS read-create 549 STATUS current 550 DESCRIPTION 551 "The realm name contains the ASCII string which 552 defines a RADIUS server domain. TRAC RADIUS MUST proxy 553 requests to a server realm. RADIUS syntax is to address 554 login name as Username- String@Realm-String - RADIUS Realm- 555 String MUST be correlated by the TRAC RADIUS to the IP 556 address of a RADIUS server to be proxied to for the 557 designated RADIUS user profile. If the TRAC RADIUS is the 558 server for designated user profile,the default value is the 559 null string." 560 DEFVAL { "" } 561 ::= { docsTrTsSPDEntry 11 } 563 docsTrTsDemandDialTimer OBJECT-TYPE 564 SYNTAX Unsigned32 565 MAX-ACCESS read-write 566 STATUS current 567 DESCRIPTION 568 " This object represents the number of seconds of 569 networking inactivity allowed before hang-up, the default 570 zero indicates demand dial is not enabled. Demand dial is 571 desirable to allow the traffic engineering of dial-in ports. 572 Networking activity monitoring is a vendor specific 573 implementation" 574 DEFVAL{ 0 } 575 ::= { docsTrTsSPDEntry 12 } 577 docsTrTsSPDdhcpAddress OBJECT-TYPE 578 SYNTAX IpAddress 579 MAX-ACCESS read-create 580 STATUS current 581 DESCRIPTION 582 " The ip address of the DHCP server." 583 ::= { docsTrTsSPDEntry 13 } 585 docsTrTsSPDfactoryDef OBJECT-TYPE 586 SYNTAX TruthValue 587 MAX-ACCESS read-create 588 STATUS current 589 DESCRIPTION 590 "boolean value, if true, indicates the SPD which 591 SHOULD be used by the CM during factory default procedure." 592 ::= { docsTrTsSPDEntry 14 } 594 docsTrTsSPDstatus OBJECT-TYPE 595 SYNTAX INTEGER { 596 disabled(1), 597 enabled(2), 598 deleted(3) 599 } 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "When the status is set to disabled, that 604 corresponding SPD entry will be disabled from the CMTS. When 605 the status is set to enabled, that corresponding SPD entry 606 will be enabled in the CMTS. When the status is set to 607 deleted, that corresponding SPD entry will be deleted from 608 the CMTS. At least one SPD entry must be present and enabled 609 in a CMTS" 611 ::= { docsTrTsSPDEntry 15 } 613 docsTrCmSPDBase OBJECT IDENTIFIER ::= { 615 docsTrCmMIBObjects 4} 617 docsTrCmSPDpersistEnable OBJECT-TYPE 618 SYNTAX TruthValue 619 MAX-ACCESS read-write 620 STATUS current 621 DESCRIPTION 622 "truth value contains interpretation of the SPD 623 MIB objects for the CM local ISP selection method. If 624 docsTrCmSPDpersistEnable is false (2), no SPD MIB objects 625 persist in an active SPD if ANY SPD parameters are set in a 626 TFTP configuration file. In such a case the CM MUST use only 627 configuration file SPD settings and defaults to construct 628 the active SPD. When docsTrCmSPDpersistEnable is true(1), 629 SPD MIB objects persist in an active SPD except where 630 specific SPD parameters in a TFTP configuration file 631 override their corresponding specific SPD MIB objects. In 632 such a case the CM MUST first use the configuration file SPD 633 settings, then use ANY SPD MIB object previously set where 634 TFTP configuration file parameters are not present, lastly, 635 appropriate defaults defined in [18,20] to construct the 636 active SPD. The initial setting is false(2)." 637 ::= { docsTrCmSPDBase 1 } 639 docsTrCmSPDname OBJECT-TYPE 640 SYNTAX DisplayString 641 MAX-ACCESS read-write 642 STATUS current 643 DESCRIPTION 644 " This object contains the service provider Name" 645 ::= { docsTrCmSPDBase 2 } 647 docsTrCmISPphoneNum1 OBJECT-TYPE 648 SYNTAX DisplayString 649 MAX-ACCESS read-write 650 STATUS current 651 DESCRIPTION 652 " This object contains the Primary ISP Phone 653 number 1" 654 ::= { docsTrCmSPDBase 3 } 656 docsTrCmISPphoneNum2 OBJECT-TYPE 657 SYNTAX DisplayString 658 MAX-ACCESS read-write 659 STATUS current 660 DESCRIPTION 661 " This object contains the Backup Phone number 2 662 " 663 ::= { docsTrCmSPDBase 4 } 665 docsTrCmISPphoneNum3 OBJECT-TYPE 666 SYNTAX DisplayString 667 MAX-ACCESS read-write 668 STATUS current 669 DESCRIPTION 670 " This object contains the Backup Phone number 671 3" 672 ::= { docsTrCmSPDBase 5 } 674 docsTrCmconnThreshold OBJECT-TYPE 675 SYNTAX Integer32 (1..10) 676 MAX-ACCESS read-write 677 STATUS current 678 DESCRIPTION 679 "The number of sequential connection try failures 680 before indicating connection failure." 681 ::= { docsTrCmSPDBase 6 } 683 docsTrCmPPPloginName OBJECT-TYPE 684 SYNTAX DisplayString 685 MAX-ACCESS read-write 686 STATUS current 687 DESCRIPTION 688 " This object contains the PPP Login Name" 689 ::= { docsTrCmSPDBase 7 } 691 docsTrCmPPPpassword OBJECT-TYPE 692 SYNTAX DisplayString 693 MAX-ACCESS read-write 694 STATUS current 695 DESCRIPTION 696 " This object contains the PPP Password" 697 ::= { docsTrCmSPDBase 8 } 699 docsTrCmPPPauth OBJECT-TYPE 700 SYNTAX INTEGER{ 701 none(1), 702 pap(2), 703 chap(3) 704 } 705 MAX-ACCESS read-write 706 STATUS current 707 DESCRIPTION 708 " This object contains the secure login 709 verification method" 710 ::= { docsTrCmSPDBase 9 } 712 docsTrCmDHCPauth OBJECT-TYPE 713 SYNTAX IpAddress 714 MAX-ACCESS read-write 715 STATUS current 716 DESCRIPTION 717 "This object contains the DHCP Server IP Address" 718 ::= { docsTrCmSPDBase 10 } 720 docsTrCmradiusRealm OBJECT-TYPE 721 SYNTAX DisplayString 722 MAX-ACCESS read-write 723 STATUS current 724 DESCRIPTION 725 " This object contains the RADIUS Cable Access 726 Realm Name" 727 ::= { docsTrCmSPDBase 11 } 729 docsTrCmdemandDialTimer OBJECT-TYPE 730 SYNTAX Unsigned32 731 MAX-ACCESS read-write 732 STATUS current 733 DESCRIPTION 734 " This object represents the number of seconds of 735 networking inactivity allowed before hang-up, the default 736 zero indicates demand dial is not enabled. Demand dial is 737 desirable to allow the traffic engineering of dial-in ports. 738 Networking activity monitoring is a vendor specific 739 implementation" 740 ::= { docsTrCmSPDBase 12 } 742 docsTrCmDHCPserver OBJECT-TYPE 743 SYNTAX IpAddress 744 MAX-ACCESS read-write 745 STATUS current 746 DESCRIPTION 747 "This object contains the DHCP Server IP Address" 748 ::= { docsTrCmSPDBase 13 } 750 docsTrCmSessionBase OBJECT IDENTIFIER ::= { 751 docsTrCmMIBObjects 5} 753 docsTrCmPingAuth OBJECT-TYPE 754 SYNTAX TruthValue 755 MAX-ACCESS read-write 756 STATUS current 757 DESCRIPTION 758 "This object has a value of 'true(1)' if CPE is 759 allowed to generate ping (ICMP request) across the network, 760 CPE." 761 ::= { docsTrCmSessionBase 1 } 763 docsTrCmTerminateOnOffHook OBJECT-TYPE 764 SYNTAX TruthValue 765 MAX-ACCESS read-write 766 STATUS current 767 DESCRIPTION 768 "This object has a value of 'true(1)' if CM must 769 terminate data session on off hook/voice call events, 770 ::= { docsTrCmSessionBase 2 } 772 docsTrCmCMType OBJECT-TYPE 773 SYNTAX INTEGER { 774 extGeneric(1), 775 extRouted(2), 776 internalOther(3), 777 internalISA(4), 778 internalPCI(5), 779 internalMAC(6), 780 internalSBUS(7), 781 internalUSB(8) 783 } 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "This object represents the CM configured type. A 788 CM may be configured as a DOCSIS bridge 'ExtGeneric(1)', as 789 a telephony return IP forwarder 'ExtRouted(2)', or as a 790 single host 'InternalXXX(3-8). " 791 ::= { docsTrCmSessionBase 3 } 793 docsTrCmRingNoAns OBJECT-TYPE 794 SYNTAX INTEGER 795 MAX-ACCESS read-write 796 STATUS current 797 DESCRIPTION 798 "This object defines the number of rings before 799 answer a CM should allow (ring threshold) before failing the 800 connection as NO ANSWER" 801 ::= { docsTrCmSessionBase 4 } 803 docsTrCmWaitInterval OBJECT-TYPE 804 SYNTAX Unsigned32 805 MAX-ACCESS read-only 806 STATUS current 807 DESCRIPTION 808 "This object defines the number of seconds of 809 time CM should wait for a call to ring after dialing" 810 ::= { docsTrCmSessionBase 5 } 812 -- The telephony return modem Command group addresses 813 -- scripting for dial-modem where a command and result 814 -- are processed to allow a management station to 815 -- communicate without apriori mapping of a given AT 816 -- command set. This process is provided to allow some 817 -- degree of control over non-integrated dial modems 818 -- by external telephony return cable modems. Internal 819 -- (to host) cable modems have OS specific vehicles 820 -- available to handle dial-up. Integrated telephone 821 -- and cable solutions should have specific source to 822 -- deal with dial initialization and modem commands of 823 -- bundled hardware. 825 docsTrCmCommand OBJECT IDENTIFIER ::= { 826 docsTrCmMIBObjects 6 } 828 docsTrCmCdCode OBJECT-TYPE 829 SYNTAX INTEGER{ 830 noError(1), 831 unable(2), 832 unrecognizedCommand(3), 833 noResponse(4), 834 notConnected(5), 835 connected(6), 836 onLine(7), 837 unsupportedCommand(8), 838 deviceDisabled(9), 839 deviceInTestMode(10), 840 testFailed(11), 841 deviceInSecurityMode(12), 842 noRTS(13), 843 noDTR(14), 844 wrongLoopbackSpeed(15), 845 noLoopbackInARQ(16), 846 pendingSoftwareDownload(17), 847 invalidFrequency(18), 848 noLoopCurrent(19), 849 noDialTone(20), 850 noLineDetected(21) 851 } 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "The value of this object indicates a further 856 description of what went wrong when a command fails." 857 ::= { docsTrCmCommand 1 } 859 docsTrCmCdMgtStationId OBJECT-TYPE 860 SYNTAX OCTET STRING (SIZE(0..8)) 861 MAX-ACCESS read-write 862 STATUS current 863 DESCRIPTION 864 "This object is a generic read-write variable 865 that a Management Station (MS) can use to guarantee that the 866 results from a given command are the results of a command 867 issued by that specific MS. Each MS must SET a unique value 868 to this object when doing commands and GET the value of this 869 object together with docsTrCmCdResult and docsTrCmCdReqId 870 to detect interference from other MSs." 871 ::= { docsTrCmCommand 2 } 873 docsTrCmCdReqId OBJECT-TYPE 874 SYNTAX INTEGER 875 MAX-ACCESS read-write 876 STATUS current 877 DESCRIPTION 878 "This object contains the request ID field of the 879 SNMP PDU which invoked the most recent command on the 880 telephony return modem, if the request-id is unknown or 881 undefined, the object contains the value zero " 882 ::= { docsTrCmCommand 3} 884 docsTrCmCdResult OBJECT-TYPE 885 SYNTAX OCTET STRING (SIZE(0..64000)) 886 MAX-ACCESS read-write 887 STATUS current 888 DESCRIPTION 889 "This object can contain parameters that are raw 890 results to the particular command being issued. " 891 ::= { docsTrCmCommand 4 } 893 docsTrCmCdForce OBJECT-TYPE 894 SYNTAX TruthValue 895 MAX-ACCESS read-write 896 STATUS current 897 DESCRIPTION 898 "In certain cases the telephony return modem may 899 be in a state where certain commands could adversely affect 900 connections. In such cases, a command request with this 901 object not present or set to 'false(2)' will result in a 902 warning. If the operator elects to ignore such warnings, 903 this object can be set to force 'true(1)' in a subsequent 904 request to cause the command to be carried out regardless of 905 the potentially hazardous effect." 906 ::= { docsTrCmCommand 5 } 908 docsTrCmCdScript OBJECT-TYPE 909 SYNTAX OCTET STRING (SIZE(0..64000)) 910 MAX-ACCESS read-write 911 STATUS current 912 DESCRIPTION 913 "This object can contain parameters that 914 specifically define a particular command or series of 915 commands being issued directly to the dial modem. Script 916 execution depends upon the inclusion in this string of a 917 suitable escape sequence (usually +++) to enter a dial modem 918 into a command mode." 919 ::= { docsTrCmCommand 6 } 921 docsTrCmCdStatus OBJECT-TYPE 922 SYNTAX INTEGER{ 923 none(1), 924 success(2), 925 inProgress(3), 926 notSupported(4), 927 unAbleToRun(5), 928 aborted(6), 929 failed(7) 930 } 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "This object contains the result of the most 935 recently requested command or test, or the value none(1) if 936 no commands have been requested since last reset." 937 ::= { docsTrCmCommand 7 } 938 -- 939 -- Conformance Statements 940 -- 942 docsTrCmConformance OBJECT IDENTIFIER ::= { 943 docsTrCmMIB 2 } 944 docsTrCmGroups OBJECT IDENTIFIER ::= { 945 docsTrCmConformance 1 946 } 947 docsTrCmCompliances OBJECT IDENTIFIER ::= { 949 docsTrCmConformance 950 2 } 952 docsCmBasicCompliance MODULE-COMPLIANCE 953 STATUS current 954 DESCRIPTION 955 "The compliance statement for DOCSIS Telephony 956 Return Cable Modems and Cable Modem Termination Systems" 958 MODULE -- This module 959 MANDATORY-GROUPS { docsTrCmBaseGroup } 961 -- conditionally mandatory groups 963 GROUP docsTrCmBaseGroup 964 DESCRIPTION 965 "Must be implemented on CMs, not 966 implemented on 967 CMTSs." 969 GROUP docsTrMsgBaseGroup 970 DESCRIPTION 971 "Must be implemented on CMTSs and 972 Optional on CMs." 974 GROUP docsTrTsSPDBaseGroup 975 DESCRIPTION 976 "Must be implemented on CMTSs, 977 not implemented on Cable Modems." 979 GROUP docsTrCmSessionSPDBaseGroup 980 DESCRIPTION 981 "Must be implemented on Cable 982 Modems, not implemented on CMTSs." 984 GROUP docsTrCmSessionBaseGroup 985 DESCRIPTION 986 "Must be implemented on Cable 987 Modems, not implemented on CMTSs." 989 GROUP docsTrCmCommandGroup 990 DESCRIPTION 991 "Optional on Cable Modems, not 992 implemented on CMTSs." 993 ::= { docsTrCmCompliances 1 } 995 docsTrCmBaseGroup OBJECT-GROUP 996 OBJECTS { 997 docsTrCmCapability , 998 docsTrCmMode 999 } 1000 STATUS current 1001 DESCRIPTION 1002 "A collection of objects providing CM base 1003 parameters" 1004 ::= { docsTrCmGroups 1} 1006 docsTrMsgBaseGroup OBJECT-GROUP 1007 OBJECTS { 1008 docsTrMsgTCDInterval , 1009 docsTrMsgTSIInterval , 1010 docsTrMsgUSRBackOff , 1011 docsTrMsgRowValue 1012 } 1013 STATUS current 1014 DESCRIPTION 1015 "A collection of objects providing CM and 1016 CMTS message configured parameters" 1017 ::= { docsTrCmGroups 2} 1019 docsTrTsSPDGroup OBJECT-GROUP 1020 OBJECTS { 1021 docsTrTsSPDname , 1022 docsTrTsSPDphoneNum1 , 1023 docsTrTsSPDphoneNum2 , 1024 docsTrTsSPDphoneNum3 , 1025 docsTrTsSPDConnThreshold , 1026 docsTrTsSPDuserName , 1027 docsTrTsSPDuserPassword , 1028 docsTrTsSPDpppAuth , 1029 docsTrTsSPDdhcpAuth , 1030 docsTrTsSPDradiusRealm , 1031 docsTrTsDemandDialTimer, 1032 docsTrTsSPDdhcpAddress , 1033 docsTrTsSPDstatus , 1034 docsTrTsSPDfactoryDef 1035 } 1036 STATUS current 1037 DESCRIPTION 1038 "A collection of objects global SPD 1039 configured parameters for CMTS" 1040 ::= { docsTrCmGroups 3} 1042 docsTrCmSPDBaseGroup OBJECT-GROUP 1043 OBJECTS { 1044 docsTrCmSPDname , 1045 docsTrCmISPphoneNum1 , 1046 docsTrCmISPphoneNum2 , 1047 docsTrCmISPphoneNum3 , 1048 docsTrCmconnThreshold , 1049 docsTrCmPPPloginName , 1050 docsTrCmPPPpassword , 1051 docsTrCmPPPauth , 1052 docsTrCmDHCPauth , 1053 docsTrCmradiusRealm , 1054 docsTrCmdemandDialTimer, 1055 docsTrCmDHCPserver 1056 } 1057 STATUS current 1058 DESCRIPTION 1059 "A collection of objects providing local SPD 1060 parameters for a CM" 1061 ::= { docsTrCmGroups 4} 1063 docsTrCmSessionBaseGroup OBJECT-GROUP 1064 OBJECTS { 1065 docsTrCmPingAuth , 1066 docsTrCmTerminateOnOffHook, 1067 docsTrCmCMType, 1068 docsTrCmRingNoAns, 1069 docsTrCmWaitInterval 1070 } 1071 STATUS current 1072 DESCRIPTION 1073 "A collection of objects providing session 1074 based parameters for dial modem" 1075 ::= { docsTrCmGroups 5} 1077 docsTrCmCommandGroup OBJECT-GROUP 1078 OBJECTS { 1079 docsTrCmCdCode, 1080 docsTrCmCdMgtStationId, 1081 docsTrCmCdReqId, 1082 docsTrCmCdForce, 1083 docsTrCmCdResult , 1084 docsTrCmCdScript, 1085 docsTrCmCdStatus 1086 } 1087 STATUS current 1089 DESCRIPTION 1090 "A collection of objects providing a command 1092 script interface to the serial dial modem device" 1093 ::= { docsTrCmGroups 6 } 1095 END 1097 5. Acknowledgments 1099 This document was produced by the IPCDN Working Group. Useful 1100 comments from Guenter Roerck and Poornima Lalwani are incorporated. 1102 6. References 1104 1. Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1105 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1106 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1107 January 1998 1109 2. Rose, M., and K. McCloghrie, "Structure and Identification of 1110 Management Information for TCP/IP-based Internets", RFC 1155, 1111 Performance Systems International, Hughes LAN Systems, May 1990 1113 3. Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1114 1212,Performance Systems International, Hughes LAN Systems, March 1115 1991 1117 4. M. Rose, "A Convention for Defining Traps for use with the SNMP", 1118 RFC 1215, Performance Systems International, March 1991 1120 5. Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 1121 of Management Information for Version 2 of the Simple Network 1122 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 1123 Systems, Inc., Dover Beach Consulting, Inc., International Network 1124 Services, January 1996. 1126 6. Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1127 Conventions for Version 2 of the Simple Network Management 1128 Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, 1129 Inc., Dover Beach Consulting, Inc., International Network 1130 Services, January 1996. 1132 7. Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1133 "Conformance Statements for Version 2 of the Simple Network 1134 Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., 1135 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1136 Network Services, January 1996. 1138 8. Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1139 Network Management Protocol", RFC 1157, SNMP Research, Performance 1140 Systems International, Performance Systems International, MIT 1141 Laboratory for Computer Science, May 1990. 1143 9. Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1144 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1145 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1146 International Network Services, January 1996. 1148 10. Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1149 Mappings for Version 2 of the Simple Network Management Protocol 1150 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1151 Dover Beach Consulting, Inc., International Network Services, 1152 January 1996. 1154 11. Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1155 Processing and Dispatching for the Simple Network Management 1156 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron 1157 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1158 January 1998. 1160 12. Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1161 for version 3 of the Simple Network Management Protocol (SNMPv3)", 1162 RFC 2274, IBM T. J. Watson Research, January 1998. 1164 13. Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1165 Operations for Version 2 of the Simple Network Management Protocol 1166 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1167 Dover Beach Consulting, Inc., International Network Services, 1168 January 1996. 1170 14. Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1171 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1172 Systems, January 1998 1174 15. Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1175 Control Model (VACM) for the Simple Network Management Protocol 1176 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 1177 Cisco Systems, Inc., January 1998 1179 16. "Data-Over-Cable Service Interface Specifications: Cable Modem 1180 Radio Frequency Interface Specification SP-RFI-I04-980724", 1181 DOCSIS, July 1998, 1182 http://www.cablemodem.com/public/pubtechspec/SP-RFI-I04- 1183 980724.pdf. 1185 17. L. Steinberg, "Techniques for Managing Asynchronously Generated 1186 Alerts", RFC 1224, May 1991. 1188 18. "Data-Over-Cable Service Interface Specifications: Operations 1189 Support System Interface Specification RF Interface SP-OSSI-RF- 1190 I02-980410", DOCSIS, April 1998, 1191 http://www.cablemodem.com/public/pubtechspec/ossi/sp-ossi.PDF. 1193 19. Bradner, S., "Key words for use in RFCs to Indicate Requirement 1194 Levels", RFC2119, Harvard University, March 1997 1196 20. "Data-Over-Cable Service Interface Specifications: Interface 1197 Specification SP-BPI-I01-970922", DOCSIS, August 1997, 1198 http://www.cablemodem.com/public/pubtechspec/ss/SP-CMTRI-I01- 1199 970804.pdf 1201 21. M. St. Johns, draft-ietf-ipcdn-cable-device-mib-07.txt, Cable 1202 Device Management Information Base for DOCSIS compliant Cable 1203 Modems and Cable Modem Termination Systems", February 1999 1205 22. M. St. Johns, draft-ietf-ipcdn-rf-interface-mib-07.txt, Radio 1206 Frequency (RF) Interface Management Information Base for 1207 MCNS/DOCSIS compliant RF Interfaces", February 1999 1209 23. J. Barnes et al., Modem Management Information Base (MIB)using 1210 SMIv2, IETF RFC-1696, August 1994. 1212 24. J. Fijolek, DOCSIS Data Over Cable Services Interface 1213 Specification Operations Support System Interface Specification 1214 Telephony Return MIB, SP-OSSI-TRD03-980209, DOCSIS, February 1998 1216 7. Security Considerations 1218 This MIB relates to a system which will provide metropolitan public 1219 internet access. As such, improper manipulation of the objects 1220 represented by this MIB may result in denial of service to a large 1221 number of end-users. 1223 8. Intellectual Property 1225 The IETF takes no position regarding the validity or scope of any 1226 intellectual property or other rights that might be claimed to 1227 pertain to the implementation or use of the technology described in 1228 this document or the extent to which any license under such rights 1229 might or might not be available; neither does it represent that it 1230 has made any effort to identify any such rights. Information on the 1231 IETF's procedures with respect to rights in standards-track and 1232 standards- related documentation can be found in BCP-11. Copies of 1233 claims of rights made available for publication and any assurances of 1234 licenses to be made available, or the result of an attempt made to 1235 obtain a general license or permission for the use of such 1236 proprietary rights by implementors or users of this specification can 1237 be obtained from the IETF Secretariat. 1238 The IETF invites any interested party to bring to its attention any 1239 copyrights, patents or patent applications, or other proprietary 1240 rights which may cover technology that may be required to practice 1241 this standard. Please address the information to the IETF Executive 1242 Director. 1243 This document and translations of it may be copied and furnished to 1244 others, and derivative works that comment on or otherwise explain it 1245 or assist in its implmentation may be prepared, copied, published and 1246 distributed, in whole or in part, without restriction of any kind, 1247 provided that the above copyright notice and this paragraph are 1248 included on all such copies and derivative works. However, this 1249 document itself may not be modified in any way, such as by removing 1250 the copyright notice or references to the Internet Society or other 1251 Internet organizations, except as needed for the purpose of 1252 developing Internet standards in which case the procedures for 1253 copyrights defined in the Internet Standards process must be 1254 followed, or as required to translate it into languages other than 1255 English. 1256 The limited permissions granted above are perpetual and will not be 1257 revoked by the Internet Society or its successors or assigns. 1258 This document and the information contained herein is provided on an 1259 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1260 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1261 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1262 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1263 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1265 9. Author's Address 1267 Jack Fijolek 1268 3Com Corporation 1269 Cable Access Division 1270 3800 Golf Road 1271 Rolling Meadows, IL 60008 1273 Phone: (847) 262-2201 1275 EMail: Jack_Fijolek@3COM.COM