idnits 2.17.1 draft-ietf-ipcdn-tri-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 26 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 27 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 13 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** 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. RFC 2119 keyword, line 128: '...hony Return CMTS MUST support the obje...' RFC 2119 keyword, line 131: '... MAY use the Modem Management Inform...' RFC 2119 keyword, line 509: '...d to indicate CM MUST authenticate DHC...' RFC 2119 keyword, line 521: '...ain. TRAC RADIUS MUST proxy requests t...' RFC 2119 keyword, line 525: '...IUS Realm-String MUST be correlated by...' (3 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 329 has weird spacing: '...age and sets ...' == Line 343 has weird spacing: '...mber of times...' == Line 347 has weird spacing: '...essages if un...' == Line 541 has weird spacing: '...onds of netwo...' == Line 715 has weird spacing: '...onds of netwo...' == (4 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 (July 30, 1998) is 9401 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: 'BER' is mentioned on line 112, but not defined == Unused Reference: '2' is defined on line 1117, but no explicit reference was found in the text == Unused Reference: 'RFC1213' is defined on line 1146, but no explicit reference was found in the text == Unused Reference: 'RFC1573' is defined on line 1152, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' == Outdated reference: A later version (-07) exists of draft-ietf-ipcdn-rf-interface-mib-04 == Outdated reference: A later version (-08) exists of draft-ietf-ipcdn-cable-device-mib-04 -- Possible downref: Non-RFC (?) normative reference: ref. '5' -- Possible downref: Non-RFC (?) normative reference: ref. '6' ** Obsolete normative reference: RFC 1573 (Obsoleted by RFC 2233) ** Downref: Normative reference to an Historic RFC: RFC 1696 Summary: 13 errors (**), 0 flaws (~~), 15 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT DOCSIS Telephony-Return MIB July 30, 3 1998 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 July 30, 1998 16 Status of this Memo 18 This document is an Internet Draft. Internet Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its Areas, 20 and its Working Groups. Note that other groups may also distribute 21 working documents as Internet Drafts. 23 Internet Drafts are draft documents valid for a maximum of six 24 months. Internet Drafts may be updated, replaced, or obsoleted by 25 other documents at any time. It is not appropriate to use Internet 26 Drafts as reference material or to cite them other than as a "working 27 draft" or "work in progress." 29 Please check the I-D abstract listing contained in each Internet 30 Draft directory to learn the current status of this or any Internet 31 Draft. Distribution of this document is unlimited. 33 Abstract 35 This memo defines an experimental portion of the Management 36 Information Base (MIB) for use with network management protocols in 37 the Internet community. In particular, it defines a basic set of 38 managed objects for SNMP-based management of MCNS compliant Cable 39 Modems and Cable Modem Termination Systems. This memo specifies a 40 MIB module in a manner that is compliant to the SNMPv2 SMI. The set 41 of objects is consistent with the SNMP framework and existing SNMP 42 standards. This memo does not specify a standard for the Internet 43 community. This memo is a product of the IPCDN working group within 44 the Internet Engineering Task Force. Comments are solicited and 45 should be addressed to the working group's mailing list at 46 ipcdn@terayon.com and/or the author. 48 1. Introduction 49 1.1 The Network Management Framework 50 The Internet-standard Network Management Framework consists of three 51 components. They are: 53 RFC 1155 which defines the SMI, the mechanisms used for describing 54 and naming objects for the purpose of management. RFC 1212 defines a 55 more concise description mechanism, which is wholly consistent with 56 the SMI. 58 RFC 1156 which defines MIB-I, the core set of managed objects for the 59 Internet suite of protocols. RFC 1213, defines MIB-II, an evolution 60 of MIB-I based on implementation experience and new operational 61 requirements. 63 RFC 1157 which defines the SNMP, the protocol used for network access 64 to managed objects. 66 The Framework permits new objects to be defined for the purpose of 67 experimentation and evaluation. 69 The SNMPv2 Network Management Framework consists of four major 70 components. They are: 72 0 RFC 1442 which defines the SMI, the mechanisms used 73 for describing and naming objects for the purpose of 74 management. 76 0 STD 17, RFC 1213 defines MIB-II, the core set of 77 managed objects for the Internet suite of protocols. 79 0 RFC 1445 which defines the administrative and other 80 architectural aspects of the framework. 82 0 RFC 1448 which defines the protocol used for network 83 access to managed objects. 85 The Framework permits new objects to be defined for the purpose of 86 experimentation and evaluation. 88 2.0 Objects 90 Managed objects are accessed via a virtual information store, termed 91 the Management Information Base or MIB. Objects in the MIB are 92 defined using the subset of Abstract Syntax Notation One (ASN.1) [1, 93 and 2] defined in the SMI. In particular, each object has a name, a 94 syntax, and an encoding. The name is an object identifier, an 95 administratively assigned name, which specifies an object type. The 96 object type together with an object instance serves to uniquely 97 identify a specific instantiation of the object. For human 98 convenience, we often use a textual string, termed the OBJECT 99 DESCRIPTOR, to also refer to the object type. 101 The syntax of an object type defines the abstract data structure 102 corresponding to that object type. The ASN.1 language is used for 103 this purpose. However, the SMI [RFC1155] purposely restricts the 104 ASN.1 constructs which may be used. These restrictions are 105 explicitly made for simplicity. 107 The encoding of an object type is simply how that object type is 108 represented using the object type's syntax. Implicitly tied to the 109 notion of an object type's syntax and encoding is how the object type 110 is represented when being transmitted on the network. 112 The SMI specifies the use of the basic encoding rules of ASN.1 [BER] 113 subject to the additional requirements imposed by the SNMP. 115 2.2 Format of Definitions 117 Section 5 contains contains the specification of all object types 118 contained in this MIB module. The object types are defined using the 119 conventions defined in the SMI, as amended by the extensions 120 specified in [RFC1212] 122 3.0 Discussion 124 The data-over-cable-system telephony return interface specification 125 is documented in [5]. The management requirements of this interface 126 are detailed in that specification. Specific inferences to other 127 controls are itemized in the following list: The Telephony Return CM 128 and telephony Return CMTS MUST support the objects in the IPCDN RFI 129 MIB [3] and Cable Device MIB [4] that are applicable to downstream 130 only. In a Telephony Return CM, the management of the telephony modem 131 MAY use the Modem Management Information Base (MIB) using SMIv2 132 [RFC1696]. These objects generally require proprietary handling to 133 address the telephony modems serial AT command interface. It is not 134 reasonable to require MIB support for all third party dial modems. 135 However, if a dial modem is integrated within a cable modem product, 136 using a subset of the RFC1696 Modem MIB objects to control the dial 137 modem is practical and reasonable. Guidelines for dial modem 138 physical capabilities are provided in [5]. Guidelines for specific 139 applicability of [3], [4], and [RFC1696] for telephony return systems 140 are provided in [6]. 142 4.0 Management Requirements 144 4.1 Handling Of Service Provider Descriptor (SPD) Updates 146 The Cable Modem service provider option process is documented in [5]. 147 An operator creates service provider descriptors (SPDs) that the CMTS 148 will send to all CMs in its domain. The operator must signify one 149 entry as factory default for initial dial-in service for a 150 subscriber. An external telco-return modem may have objects within 151 the selected SPD modified by changing corresponding scalar objects on 152 a CM using the network management station. 154 One reason for the SNMP-initiated SPD update is to allow loading of 155 permanent Telephone Numbers, Login Usernames and Login Passwords 156 without requiring individualized configuration files on a per CM 157 basis. For example the operator MAY: 159 o set docsTrTsSPDphoneNum1 to dial a temporary access Telephone 160 Number. A factory default CM user may then be given some limited 161 access by using default values for all other SPD objects. 163 o Temporary system access may be upgraded after an undefined 164 operator specified authentication. The operator may then set 165 docsTrTsSPDphoneNum1, docsTrTsSPDuserName, docsTrTsSPDuserPassword 166 (phone/login/password) or any other CM SPD objects to individualized 167 settings. 169 o These settings remain in effect unless changed by Telephone 170 Settings Options in the CMs TFTP configuration file. 172 o The operator may want to change individual Telephone Settings 173 Options for CMs sharing a global TFTP configuration file. For 174 example, the DHCP Server (ip address) can be changed for all CMs 175 sharing a configuration file without affecting any other active SPD 176 settings by having just DHCP server parameter set in the file. All 177 other MIB modified SPD parameters would remain active (excepting 178 docsTrTsSPDdhcpAddress MIB object) if docsTrCmSPDpersistEnable is 179 TRUE. 181 5.0 Definitions 182 TelcoReturnCABLE-DEVICE-MIB DEFINITIONS ::= BEGIN 184 IMPORTS 185 MODULE-IDENTITY, OBJECT-TYPE, 186 Integer32, IpAddress, Unsigned32 187 FROM SNMPv2-SMI 188 DisplayString, DateAndTime, TruthValue, RowStatus 189 FROM SNMPv2-TC 190 OBJECT-GROUP, MODULE-COMPLIANCE 191 FROM SNMPv2-CONF 192 InterfaceIndexOrZero 193 FROM DOCS-IF-MIB 194 transmission 195 FROM RFC1213-MIB 196 ; 198 docsTrCmMIB MODULE-IDENTITY 199 LAST-UPDATED "9807280920Z" 200 ORGANIZATION "3Com - Cable Access" 201 CONTACT-INFO " Jack Fijolek/Srinivyasa Murthy Adiraju 202 Postal: 3Com 203 3800 Golf Road 204 Rolling Meadows, IL 60008 205 Tel: +1 847 2622201 +1 847 2622205 206 Fax: +1 847 2620258 207 E-mail: Srinivyasa_Adiraju@3Com.com" 208 DESCRIPTION 209 "TELCO Return MIB for Data Over Cable Access modems and 210 termination systems" 211 ::= { transmission 128 } 213 docsTrCmMIBObjects OBJECT IDENTIFIER ::= {docsTrCmMIB 1} 214 docsTrCmBase OBJECT IDENTIFIER ::= { docsTrCmMIBObjects 1} 216 docsTrCmCapability OBJECT-TYPE 217 SYNTAX INTEGER { 218 other(1), 219 telcoReturn(2), 220 twoWay(3), 221 threeWay(4) 222 } 223 MAX-ACCESS read-only 224 STATUS current 225 DESCRIPTION 226 "This object represents the CM Capability. A CM may be 227 'TelcoReturn(2)', or 'TwoWay(3)', or as a Three Way Capable 228 'ThreeWay(4).' 229 or Other e.g., undefined" 230 ::= { docsTrCmBase 1 } 232 docsTrCmMode OBJECT-TYPE 233 SYNTAX INTEGER { 234 other(1), 235 telcoReturn(2), 236 twoWay(3) 238 } 239 MAX-ACCESS read-write 240 STATUS current 241 DESCRIPTION 242 "This object represents the CM Operating Mode. A CM may be 243 operating 244 as 245 'TelcoReturn(2)', or 'TwoWay(3)', or Other e.g, undefined" 246 ::= { docsTrCmBase 2 } 248 docsTrMsgBase OBJECT IDENTIFIER ::= { docsTrCmMIBObjects 2} 250 docsTrMsgBaseTable OBJECT-TYPE 251 SYNTAX SEQUENCE OF DocsTrMsgBaseEntry 252 MAX-ACCESS not-accessible 253 STATUS current 254 DESCRIPTION 255 "Telco Return Message Base Table" 256 ::= { docsTrMsgBase 1 } 258 docsTrMsgBaseEntry OBJECT-TYPE 259 SYNTAX DocsTrMsgBaseEntry 260 MAX-ACCESS not-accessible 261 STATUS current 262 DESCRIPTION 263 "This table contains the information about 264 TCD/TSI 265 and 266 USRbackOff for 267 Each interface" 268 INDEX { docsTrMsgIfIndex } 269 ::= { docsTrMsgBaseTable 1 } 271 DocsTrMsgBaseEntry ::= SEQUENCE { 272 docsTrMsgIfIndex InterfaceIndexOrZero, 273 docsTrMsgTCDInterval INTEGER, 274 docsTrMsgTSIInterval INTEGER, 275 docsTrMsgUSRBackOff Unsigned32, 276 docsTrMsgRowValue RowStatus 277 } 279 docsTrMsgIfIndex OBJECT-TYPE 280 SYNTAX InterfaceIndexOrZero 281 MAX-ACCESS not-accessible 282 STATUS current 283 DESCRIPTION 284 "The value corresponds to ifIndex for either a 285 CATV 286 MAC 287 or other network interface. In Cable Modems, the 288 default 289 value is the customer side interface. In Cable 290 Modem 291 Termination Systems, this object has to be 292 specified 293 to create a row in this table." 294 ::= { docsTrMsgBaseEntry 1 } 296 docsTrMsgTCDInterval OBJECT-TYPE 297 SYNTAX INTEGER (500..2000) 298 UNITS "Milliseconds" 299 MAX-ACCESS read-write 300 STATUS current 301 DESCRIPTION 302 "The interval between CMTS transmission of successive 303 Telephony 304 Channel Descriptor (TCD) messages at this interface. This is 305 also the 306 time interval a CM minimally scans on a specific channel for 307 TCD 308 message. " 309 REFERENCE 310 "Data Over Cable Telephony Return Interface Specification, 311 [1], TCD Interval." 312 DEFVAL { 2000 } 313 ::= { docsTrMsgBaseEntry 2 } 315 docsTrMsgTSIInterval OBJECT-TYPE 316 SYNTAX INTEGER (1000..4000) 317 UNITS "Milliseconds" 318 MAX-ACCESS read-write 319 STATUS current 320 DESCRIPTION 321 "The interval between CMTS transmission of successive 322 Termination 323 System Interface (TSI) messages for a downstream channel at 324 this 325 interface. 326 This is also the time interval a CM should scan on a specific 328 channel 329 for a TSI message and sets the frequency the CM monitors the 330 CMTS 331 epoch counter. " 332 REFERENCE 333 "Data Over Cable Telephony Return Interface Specification, 334 [6], TSI Interval." 335 DEFVAL { 4000 } 336 ::= { docsTrMsgBaseEntry 3 } 338 docsTrMsgUSRBackOff OBJECT-TYPE 339 SYNTAX Unsigned32 340 MAX-ACCESS read-write 341 STATUS current 342 DESCRIPTION 343 " This object represents the number of times CMTS will 344 resend 345 User 346 Station Reset 347 messages if unacknowledged by CM; Number of duplicate reset 348 requests 349 CM may receive" 350 DEFVAL{4} 351 --REFERENCE 352 --"Data Over Cable Telephony Return Interface Specification, 353 --[6], USR Backoff ." 354 ::= { docsTrMsgBaseEntry 4 } 356 docsTrMsgRowValue OBJECT-TYPE 357 SYNTAX RowStatus 358 MAX-ACCESS read-write 359 STATUS current 360 DESCRIPTION 361 " Controls and reflects the status of rows in this table " 362 ::= { docsTrMsgBaseEntry 5 } 364 docsTrTsSPD OBJECT IDENTIFIER ::= { docsTrCmMIBObjects 3} 366 docsTrTsSPDTable OBJECT-TYPE 367 SYNTAX SEQUENCE OF DocsTrTsSPDEntry 368 MAX-ACCESS not-accessible 369 STATUS current 370 DESCRIPTION 371 " A table of all the SPD messages that get sent out" 372 ::= { docsTrTsSPD 1 } 374 docsTrTsSPDEntry OBJECT-TYPE 375 SYNTAX DocsTrTsSPDEntry 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "This an entry in the SPD table which is one of the SPD that 380 get sent out to the cable modems" 381 INDEX {docsTrTsSPDindex} 382 ::= {docsTrTsSPDTable 1} 384 DocsTrTsSPDEntry ::= SEQUENCE { 385 docsTrTsSPDindex INTEGER, 386 docsTrTsSPDname DisplayString, 387 docsTrTsSPDphoneNum1 DisplayString, 388 docsTrTsSPDphoneNum2 DisplayString, 389 docsTrTsSPDphoneNum3 DisplayString, 390 docsTrTsSPDConnThreshold Integer32, 391 docsTrTsSPDuserName DisplayString, 392 docsTrTsSPDuserPassword OCTET STRING, 393 docsTrTsSPDpppAuth INTEGER, 394 docsTrTsSPDdhcpAuth INTEGER, 395 docsTrTsSPDradiusRealm DisplayString, 396 docsTrTsDemandDialTimer Unsigned32, 397 docsTrTsSPDdhcpAddress IpAddress, 398 docsTrTsSPDfactoryDef INTEGER, 399 docsTrTsSPDstatus INTEGER 401 } 403 docsTrTsSPDindex OBJECT-TYPE 404 SYNTAX INTEGER(1..16383) 405 MAX-ACCESS not-accessible 406 STATUS current 407 DESCRIPTION 408 "The unique number which identifies the Service Provider 409 Descriptor in the SPD Table" 410 ::= { docsTrTsSPDEntry 1} 412 docsTrTsSPDname OBJECT-TYPE 413 SYNTAX DisplayString (SIZE(1..128)) 414 MAX-ACCESS read-create 415 STATUS current 416 DESCRIPTION 417 "The name of the Service Provider. A value of null string 418 means no name" 419 DEFVAL { "" } 420 ::= { docsTrTsSPDEntry 2 } 422 docsTrTsSPDphoneNum1 OBJECT-TYPE 423 SYNTAX DisplayString (SIZE (1..128)) 424 MAX-ACCESS read-create 425 STATUS current 426 DESCRIPTION 427 "The first phone number to try when trying to reach the 428 service 429 provider. A value of null string means no phone number" 430 DEFVAL { "" } 431 ::= { docsTrTsSPDEntry 3 } 433 docsTrTsSPDphoneNum2 OBJECT-TYPE 434 SYNTAX DisplayString (SIZE (1..128)) 435 MAX-ACCESS read-create 436 STATUS current 437 DESCRIPTION 438 "The second phone number to try to reach the service provider 439 when the first number fails. A value of null string means no phone 440 number" 441 DEFVAL { "" } 442 ::= { docsTrTsSPDEntry 4 } 444 docsTrTsSPDphoneNum3 OBJECT-TYPE 445 SYNTAX DisplayString (SIZE (1..128)) 446 MAX-ACCESS read-create 447 STATUS current 448 DESCRIPTION 449 "The third phone number to try in case the 1st and 2nd 450 numbers 451 fail. A value of null string means no phone number" 452 DEFVAL { "" } 453 ::= { docsTrTsSPDEntry 5 } 455 docsTrTsSPDConnThreshold OBJECT-TYPE 456 SYNTAX Integer32 (1..10) 457 MAX-ACCESS read-create 458 STATUS current 459 DESCRIPTION 460 "The number of sequential connection try failures before 461 indicating connection failure. " 462 DEFVAL { 1 } 463 ::= { docsTrTsSPDEntry 6 } 465 docsTrTsSPDuserName OBJECT-TYPE 466 SYNTAX DisplayString (SIZE (1..32)) 467 MAX-ACCESS read-create 468 STATUS current 469 DESCRIPTION 470 "The username the CM will use during PAP or CHAP 471 authentication 472 over telco link during the initialization procedure." 473 DEFVAL { "guest" } 474 ::= { docsTrTsSPDEntry 7 } 476 docsTrTsSPDuserPassword OBJECT-TYPE 477 SYNTAX OCTET STRING (SIZE (1..15)) 478 MAX-ACCESS read-create 479 STATUS current 480 DESCRIPTION 481 "The password that the CM will use during the PAP or CHAP 482 authentication over the telco link during the initialization 483 procedure." 484 DEFVAL { "" } 485 ::= { docsTrTsSPDEntry 8 } 487 docsTrTsSPDpppAuth OBJECT-TYPE 488 SYNTAX INTEGER { other(1), 489 uNegotiate(1), 490 uPAP(2), 491 uCHAP(3) 492 } 493 MAX-ACCESS read-create 494 STATUS current 495 DESCRIPTION 496 "This instructs the telco return modem of the authentication 497 procedure to perform over the telco link." 498 DEFVAL { uNegotiate } 499 ::= { docsTrTsSPDEntry 9 } 501 docsTrTsSPDdhcpAuth OBJECT-TYPE 502 SYNTAX INTEGER { other(1), 503 disable(2), 504 enable(3) 505 } 506 MAX-ACCESS read-create 507 STATUS current 508 DESCRIPTION 509 "Boolean value reserved to indicate CM MUST authenticate DHCP 510 messages when enable." 511 DEFVAL { disable } 512 ::= { docsTrTsSPDEntry 10 } 514 docsTrTsSPDradiusRealm OBJECT-TYPE 515 SYNTAX DisplayString (SIZE(0..128)) 516 MAX-ACCESS read-create 517 STATUS current 518 DESCRIPTION 519 "The realm name contains the ASCII string which defines a 520 RADIUS 521 server domain. TRAC RADIUS MUST proxy requests to a server 522 realm. 523 RADIUS syntax is to address login name as Username- 524 String@Realm-String 525 - RADIUS Realm-String MUST be correlated by the TRAC RADIUS 526 to 527 the 528 IP address of a RADIUS server to be proxied to for the 529 designated 530 RADIUS user profile. If the TRAC RADIUS is the server for 531 designated 532 user profile,the default value is the null string." 533 DEFVAL { "" } 534 ::= { docsTrTsSPDEntry 11 } 536 docsTrTsDemandDialTimer OBJECT-TYPE 537 SYNTAX Unsigned32 538 MAX-ACCESS read-write 539 STATUS current 540 DESCRIPTION 541 " This object represents the number of seconds of networking 542 inactivity allowed before hang-up, the default zero indicates 543 demand 544 dial is not enabled. Demand dial is desirable to allow the 545 traffic 546 engineering of dial-in ports. Networking activity monitoring 547 is 548 a 549 vendor specific implementation" 550 DEFVAL{ 0 } 551 ::= { docsTrTsSPDEntry 12 } 553 docsTrTsSPDdhcpAddress OBJECT-TYPE 554 SYNTAX IpAddress 555 MAX-ACCESS read-create 556 STATUS current 557 DESCRIPTION 558 " The ip address of the DHCP server." 559 ::= { docsTrTsSPDEntry 13 } 561 docsTrTsSPDfactoryDef OBJECT-TYPE 562 SYNTAX TruthValue 563 MAX-ACCESS read-create 564 STATUS current 565 DESCRIPTION 566 "boolean value, if true, indicates the SPD which SHOULD be 567 used 568 by the CM during factory default procedure." 569 ::= { docsTrTsSPDEntry 14 } 571 docsTrTsSPDstatus OBJECT-TYPE 572 SYNTAX INTEGER { 573 disabled(1), 574 enabled(2), 575 deleted(3) 576 } 577 MAX-ACCESS read-create 578 STATUS current 579 DESCRIPTION 580 "When the status is set to disabled, that 581 corresponding SPD entry will be disabled from the CMTS. 582 When 583 the status is set to enabled, that corresponding SPD entry 584 will be enabled in the CMTS. When the status is set to 585 deleted, that corresponding SPD entry will be deleted from 586 the CMTS. At least one SPD entry must be present and 587 enabled 588 in a CMTS" 590 ::= { docsTrTsSPDEntry 15 } 592 docsTrCmSPDBase OBJECT IDENTIFIER ::= { docsTrCmMIBObjects 4} 594 docsTrCmSPDpersistEnable OBJECT-TYPE 595 SYNTAX TruthValue 596 MAX-ACCESS read-write 597 STATUS current 598 DESCRIPTION 599 "truth value contains interpretation of the SPD MIB objects 600 for the CM local ISP selection method. If 601 docsTrCmSPDpersistEnable 602 is false (2), no SPD MIB objects persist in an active SPD if 603 ANY 604 SPD parameters are set in a TFTP configuration 605 file. In such a case the CM MUST use only configuration file 606 SPD 607 settings and defaults to construct the active SPD. 609 When docsTrCmSPDpersistEnable is true(1), SPD MIB objects 610 persist in an active SPD except where specific SPD 611 parameters in a 612 TFTP configuration file override their corresponding 613 specific SPD MIB 614 objects. In such a case the CM MUST first use the 615 configuration file 616 SPD settings, then use ANY SPD MIB object previously set 617 where TFTP 618 configuration file parameters are not present, lastly, 619 appropriate 620 defaults defined in [6] to construct the active SPD. The 621 initial 622 setting is false(2)." 623 ::= { docsTrCmSPDBase 1 } 625 docsTrCmSPDname OBJECT-TYPE 626 SYNTAX DisplayString 627 MAX-ACCESS read-write 628 STATUS current 629 DESCRIPTION 630 " This object contains the service provider Name" 631 ::= { docsTrCmSPDBase 2 } 633 docsTrCmISPphoneNum1 OBJECT-TYPE 634 SYNTAX DisplayString 635 MAX-ACCESS read-write 636 STATUS current 637 DESCRIPTION 638 " This object contains the Primary ISP Phone number 1" 639 ::= { docsTrCmSPDBase 3 } 641 docsTrCmISPphoneNum2 OBJECT-TYPE 642 SYNTAX DisplayString 643 MAX-ACCESS read-write 644 STATUS current 645 DESCRIPTION 646 " This object contains the Backup Phone number 2 " 647 ::= { docsTrCmSPDBase 4 } 649 docsTrCmISPphoneNum3 OBJECT-TYPE 650 SYNTAX DisplayString 651 MAX-ACCESS read-write 652 STATUS current 653 DESCRIPTION 654 " This object contains the Backup Phone number 3" 655 ::= { docsTrCmSPDBase 5 } 657 docsTrCmconnThreshold OBJECT-TYPE 658 SYNTAX Integer32 (1..10) 659 MAX-ACCESS read-write 660 STATUS current 661 DESCRIPTION 662 "The number of sequential connection try failures before 663 indicating connection failure." 664 ::= { docsTrCmSPDBase 6 } 666 docsTrCmPPPloginName OBJECT-TYPE 667 SYNTAX DisplayString 668 MAX-ACCESS read-write 669 STATUS current 670 DESCRIPTION 671 " This object contains the PPP Login Name" 672 ::= { docsTrCmSPDBase 7 } 674 docsTrCmPPPpassword OBJECT-TYPE 675 SYNTAX DisplayString 676 MAX-ACCESS read-write 677 STATUS current 678 DESCRIPTION 679 " This object contains the PPP Password" 680 ::= { docsTrCmSPDBase 8 } 682 docsTrCmPPPauth OBJECT-TYPE 683 SYNTAX INTEGER{ 684 none(1), 685 pap(2), 686 chap(3) 687 } 688 MAX-ACCESS read-write 689 STATUS current 690 DESCRIPTION 691 " This object contains the secure login verification method" 692 ::= { docsTrCmSPDBase 9 } 694 docsTrCmDHCPauth OBJECT-TYPE 695 SYNTAX IpAddress 696 MAX-ACCESS read-write 697 STATUS current 698 DESCRIPTION 699 "This object contains the DHCP Server IP Address" 700 ::= { docsTrCmSPDBase 10 } 702 docsTrCmradiusRealm OBJECT-TYPE 703 SYNTAX DisplayString 704 MAX-ACCESS read-write 705 STATUS current 706 DESCRIPTION 707 " This object contains the RADIUS Cable Access Realm Name" 708 ::= { docsTrCmSPDBase 11 } 710 docsTrCmdemandDialTimer OBJECT-TYPE 711 SYNTAX Unsigned32 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 " This object represents the number of seconds of networking 716 inactivity allowed before hang-up, the default zero indicates 717 demand 718 dial is not enabled. Demand dial is desirable to allow the 719 traffic 720 engineering of dial-in ports. Networking activity monitoring 721 is 722 a 723 vendor specific implementation" 724 ::= { docsTrCmSPDBase 12 } 726 docsTrCmDHCPserver OBJECT-TYPE 727 SYNTAX IpAddress 728 MAX-ACCESS read-write 729 STATUS current 730 DESCRIPTION 731 "This object contains the DHCP Server IP Address" 732 ::= { docsTrCmSPDBase 13 } 734 docsTrCmSessionBase OBJECT IDENTIFIER ::= { docsTrCmMIBObjects 5} 736 docsTrCmPingAuth OBJECT-TYPE 737 SYNTAX TruthValue 738 MAX-ACCESS read-write 739 STATUS current 740 DESCRIPTION 741 "This object has a value of 'true(1)' if CPE is allowed to 742 generate 743 ping (ICMP request) across the network, 'false(2)' if 744 otherwise. 745 A CM 746 may be on a demand dial inactivity timer where restricting 747 CPE 748 ping 749 may not be allowed to hold the port connection" 750 ::= { docsTrCmSessionBase 1 } 752 docsTrCmTerminateOnOffHook OBJECT-TYPE 753 SYNTAX TruthValue 754 MAX-ACCESS read-write 755 STATUS current 756 DESCRIPTION 757 "This object has a value of 'true(1)' if CM must terminate 758 data 759 session on off hook/voice call events, 'false(2)' if 760 otherwise. 761 " 762 ::= { docsTrCmSessionBase 2 } 764 docsTrCmCMType OBJECT-TYPE 765 SYNTAX INTEGER { 766 extGeneric(1), 767 extRouted(2), 768 internalISA(3), 769 internalPCI(4), 770 internalMAC(5), 771 internalSBUS(6), 772 internalUSB(7), 773 internalOther(8) 774 } 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "This object represents the CM configured type. A CM may be 779 configured as an MCNS bridge 'ExtGeneric(1)', 780 as an IP forwarder 'ExtRouted(2)', 781 or as a single host 'InternalXXX(3-8). " 782 ::= { docsTrCmSessionBase 3 } 784 docsTrCmRingNoAns OBJECT-TYPE 785 SYNTAX INTEGER 786 MAX-ACCESS read-write 787 STATUS current 788 DESCRIPTION 789 "This object defines the number of rings before answer a CM 790 should 791 allow (ring threshold) before failing the connection as NO 792 ANSWER" 793 ::= { docsTrCmSessionBase 4 } 795 docsTrCmWaitInterval OBJECT-TYPE 796 SYNTAX Unsigned32 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "This object defines the number of seconds of time CM should 801 wait 802 for a call to ring after dialing" 803 ::= { docsTrCmSessionBase 5 } 805 -- The telephony return modem Command group addresses scripting 806 for dial-modem 807 -- where a command and result are processed to allow a 808 management station to 809 -- communicate without apriori mapping of a given AT command 810 set. This process 811 -- is provided to allow some degree of control over non- 812 integrated dial modems 813 -- by external telephony return cable modems. Internal (to host) 814 cable modems 815 -- have OS specific vehicles available to handle dial-up. 816 Integrated telephone 817 -- and cable solutions should have specific source to deal with 818 dial initialization 819 -- and modem commands of bundled hardware. 821 docsTrCmCommand OBJECT IDENTIFIER ::= { docsTrCmMIBObjects 6 822 } 824 docsTrCmCdCode OBJECT-TYPE 825 SYNTAX INTEGER{ 826 noError(1), 827 unable(2), 828 unrecognizedCommand(3), 829 noResponse(4), 830 notConnected(5), 831 connected(6), 832 onLine(7), 833 unsupportedCommand(8), 834 deviceDisabled(9), 835 deviceInTestMode(10), 836 testFailed(11), 837 deviceInSecurityMode(12), 838 noRTS(13), 839 noDTR(14), 840 wrongLoopbackSpeed(15), 841 noLoopbackInARQ(16), 842 pendingSoftwareDownload(17), 843 invalidFrequency(18), 844 noLoopCurrent(19), 845 noDialTone(20), 846 noLineDetected(21) 847 } 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "The value of this object indicates a further description 853 of what went wrong when a command fails." 854 ::= { docsTrCmCommand 1 } 856 docsTrCmCdMgtStationId OBJECT-TYPE 857 SYNTAX OCTET STRING (SIZE(0..8)) 858 MAX-ACCESS read-write 859 STATUS current 860 DESCRIPTION 861 "This object is a generic read-write variable that a 862 Management Station (MS) can use to guarantee that the 863 results from a given command are the results of a command 864 issued by that specific MS. Each MS must SET a unique 865 value to this object when doing commands and GET the value 866 of this object together with docsTrCmCdResult and 867 docsTrCmCdReqId to detect interference from other MSs." 868 ::= { docsTrCmCommand 2 } 870 docsTrCmCdReqId OBJECT-TYPE 871 SYNTAX INTEGER 872 MAX-ACCESS read-write 873 STATUS current 874 DESCRIPTION 875 "This object contains the request ID field of the SNMP PDU 876 which 877 invoked the most recent command on the telephony return 878 modem, 879 if the request-id is unknown or undefined, the object 880 contains 881 the 882 value zero " 883 ::= { docsTrCmCommand 3} 885 docsTrCmCdResult OBJECT-TYPE 886 SYNTAX OCTET STRING (SIZE(0..64000)) 887 MAX-ACCESS read-write 888 STATUS current 889 DESCRIPTION 890 "This object can contain parameters that are raw results to 891 the 892 particular command being issued. " 893 ::= { docsTrCmCommand 4 } 895 docsTrCmCdForce OBJECT-TYPE 896 SYNTAX TruthValue 897 MAX-ACCESS read-write 898 STATUS current 899 DESCRIPTION 900 "In certain cases the telephony return modem may be in 901 a state where certain commands could adversely affect 902 connections. 903 In such cases, a command request with this object not present 904 or 905 set to 'false(2)' will result in a warning. If the operator 906 elects to ignore such warnings, this object can be set to 907 force 'true(1)' in a subsequent request to cause the command 908 to 909 be 910 carried out regardless of the potentially hazardous effect." 911 ::= { docsTrCmCommand 5 } 913 docsTrCmCdScript OBJECT-TYPE 914 SYNTAX OCTET STRING (SIZE(0..64000)) 915 MAX-ACCESS read-write 916 STATUS current 917 DESCRIPTION 918 "This object can contain parameters that specifically define 919 a 920 particular command or series of commands being issued 921 directly to the dial modem. Script execution depends 922 upon the inclusion in this string of a suitable escape 923 sequence 924 (usually +++) to enter a dial modem into a command mode." 925 ::= { docsTrCmCommand 6 } 927 docsTrCmCdStatus OBJECT-TYPE 928 SYNTAX INTEGER{ 929 none(1), 930 success(2), 931 inProgress(3), 932 notSupported(4), 933 unAbleToRun(5), 934 aborted(6), 935 failed(7) 936 } 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "This object contains the result of the most recently 941 requested command or test, or the value none(1) if no 942 commands have been requested since last reset." 943 ::= { docsTrCmCommand 7 } 945 -- 947 -- Conformance Statements 948 -- 950 docsTrCmConformance OBJECT IDENTIFIER ::= { docsTrCmMIB 2 } 951 docsTrCmGroups OBJECT IDENTIFIER ::= { 952 docsTrCmConformance 1 953 } 954 docsTrCmCompliances OBJECT IDENTIFIER ::= { 955 docsTrCmConformance 956 2 } 958 docsCmBasicCompliance MODULE-COMPLIANCE 959 STATUS current 960 DESCRIPTION 961 "The compliance statement for MCNS Telephony Return Cable 962 Modems and Cable Modem Termination Systems" 964 MODULE -- This module 965 MANDATORY-GROUPS { docsTrCmBaseGroup } 967 -- conditionally mandatory groups 969 GROUP docsTrCmBaseGroup 970 DESCRIPTION 971 "Must be implemented on CMs, not implemented 972 on 973 CMTSs." 975 GROUP docsTrMsgBaseGroup 976 DESCRIPTION 977 "Must be implemented on CMTSs and Optional on 978 CMs." 980 GROUP docsTrTsSPDBaseGroup 981 DESCRIPTION 982 "Must be implemented on CMTSs, not 983 implemented 984 on Cable Modems." 986 GROUP docsTrCmSessionSPDBaseGroup 987 DESCRIPTION 988 "Must be implemented on Cable Modems, not 989 implemented on CMTSs." 991 GROUP docsTrCmSessionBaseGroup 992 DESCRIPTION 993 "Must be implemented on Cable Modems, not 994 implemented on CMTSs." 996 GROUP docsTrCmCommandGroup 997 DESCRIPTION 998 "Optional on Cable Modems, not implemented on 999 CMTSs." 1000 ::= { docsTrCmCompliances 1 } 1002 docsTrCmBaseGroup OBJECT-GROUP 1003 OBJECTS { 1004 docsTrCmCapability , 1005 docsTrCmMode 1006 } 1007 STATUS current 1008 DESCRIPTION 1009 "A collection of objects providing CM base parameters" 1010 ::= { docsTrCmGroups 1} 1012 docsTrMsgBaseGroup OBJECT-GROUP 1013 OBJECTS { 1014 docsTrMsgTCDInterval , 1015 docsTrMsgTSIInterval , 1016 docsTrMsgUSRBackOff , 1017 docsTrMsgRowValue 1018 } 1019 STATUS current 1020 DESCRIPTION 1021 "A collection of objects providing CM and CMTS message 1022 configured parameters" 1023 ::= { docsTrCmGroups 2} 1025 docsTrTsSPDGroup OBJECT-GROUP 1026 OBJECTS { 1027 docsTrTsSPDname , 1028 docsTrTsSPDphoneNum1 , 1029 docsTrTsSPDphoneNum2 , 1030 docsTrTsSPDphoneNum3 , 1031 docsTrTsSPDConnThreshold , 1032 docsTrTsSPDuserName , 1033 docsTrTsSPDuserPassword , 1034 docsTrTsSPDpppAuth , 1035 docsTrTsSPDdhcpAuth , 1036 docsTrTsSPDradiusRealm , 1037 docsTrTsDemandDialTimer, 1038 docsTrTsSPDdhcpAddress , 1039 docsTrTsSPDstatus , 1040 docsTrTsSPDfactoryDef 1041 } 1042 STATUS current 1043 DESCRIPTION 1044 "A collection of objects global SPD configured parameters 1045 for CMTS" 1046 ::= { docsTrCmGroups 3} 1048 docsTrCmSPDBaseGroup OBJECT-GROUP 1049 OBJECTS { 1050 docsTrCmSPDname , 1051 docsTrCmISPphoneNum1 , 1052 docsTrCmISPphoneNum2 , 1053 docsTrCmISPphoneNum3 , 1054 docsTrCmconnThreshold , 1055 docsTrCmPPPloginName , 1056 docsTrCmPPPpassword , 1057 docsTrCmPPPauth , 1058 docsTrCmDHCPauth , 1059 docsTrCmradiusRealm , 1060 docsTrCmdemandDialTimer, 1061 docsTrCmDHCPserver 1062 } 1063 STATUS current 1064 DESCRIPTION 1065 "A collection of objects providing local SPD parameters 1066 for 1067 a CM" 1068 ::= { docsTrCmGroups 4} 1070 docsTrCmSessionBaseGroup OBJECT-GROUP 1071 OBJECTS { 1072 docsTrCmPingAuth , 1073 docsTrCmTerminateOnOffHook, 1074 docsTrCmCMType, 1075 docsTrCmRingNoAns, 1076 docsTrCmWaitInterval 1077 } 1078 STATUS current 1079 DESCRIPTION 1080 "A collection of objects providing session based 1081 parameters 1082 for 1083 dial modem" 1084 ::= { docsTrCmGroups 5} 1086 docsTrCmCommandGroup OBJECT-GROUP 1087 OBJECTS { 1088 docsTrCmCdCode, 1089 docsTrCmCdMgtStationId, 1090 docsTrCmCdReqId, 1091 docsTrCmCdForce, 1092 docsTrCmCdResult , 1093 docsTrCmCdScript, 1094 docsTrCmCdStatus 1095 } 1096 STATUS current 1098 DESCRIPTION 1099 "A collection of objects providing a command script 1100 interface 1101 to the serial dial modem device" 1102 ::= { docsTrCmGroups 6 } 1104 END 1106 7.0 Security 1108 Security is not specifically addressed in this memo. 1110 8.0 References 1112 [1] Information processing systems - Open Systems Interconnection 1113 Specification of Abstract Syntax Notation One (ASN.1), 1114 International Organization for Standardization, International 1115 Standard 8824, December 1987. 1117 [2] Information processing systems - Open Systems Interconnection 1118 Specification of Basic Encoding Rules for Abstract Notation 1119 One (ASN.1), International Organization for Standardization, 1120 International Standard 8825, December 1987. 1122 [3] G. Roeck,draft-ietf-ipcdn-rf-interface-mib-04.txt, 1123 Radio Frequency (RF) Interface Management Information Base for 1124 MCNS compliant RF interfaces", May 1998. 1126 [4] G. Roeck, draft-ietf-ipcdn-cable-device-mib-04.txt, 1127 Cable Device Management Information Base for MCNS compliant 1128 Cable Modems and Cable Modem Termination Systems", May 1998. 1130 [5] MCNS Data Over Cable Services Cable Modem Telephony Return 1131 Interface Specification SP-CMTRI-I01-970804, MCNS, August 1997. 1133 [6] MCNS Data Over Cable Services Interface Specification Operations 1134 Support System Interface Specification Telephony Return MIB, 1135 SP-OSSI-TRD03-980209, MCNS, February 1998. 1137 [RFC1155] Rose M., and K. McCloghrie, "Structure and Identification 1138 of Management Information for TCP/IP-based internets", RFC 1155, 1139 Performance Systems International, Hughes LAN Systems, May 1140 1990. 1142 [RFC1212] Rose, M., and K. McCloghrie, Editors, "Concise MIB 1143 Definitions", RFC 1212, Performance Systems International, 1144 Hughes LAN Systems, March 1991. 1146 [RFC1213] Rose M., Editor, "Management Information Base for Network 1147 Management of TCP/IP-based internets: MIB-II", RFC 1213, 1148 - 26 - 1150 Performance Systems International, March 1991. 1152 [RFC1573] K. McCloghrie, F. Kastenholz, "Evolution of the 1153 Interfaces Group of MIB-II", RFC1573, 01/20/1994. 1155 [RFC1696] J. Barnes et al., Modem Management Information Base (MIB) 1156 using SMIv2, IETF RFC-1696, August 1994. 1158 Author's Address 1160 Jack Fijolek 1161 3Com Corporation 1162 Cable Access Division 1163 3800 Golf Road 1164 Rolling Meadows, IL 60008 1166 Phone: (847) 262-2201 1168 EMail: Jack_Fijolek@3COM.COM