idnits 2.17.1 draft-ietf-ipcdn-cable-gateway-config-mib-00.txt: -(195): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(272): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(644): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(648): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1090): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1923): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1929): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding 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: ---------------------------------------------------------------------------- == There are 67 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard 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 abstract seems to contain references ([21], [22], [5], [6], [7]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 8 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 365 has weird spacing: '...reshold setti...' == Line 443 has weird spacing: '...ameters incl...' == Line 823 has weird spacing: '...ssigned above...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2003) is 7621 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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? '1' on line 20 looks like a reference -- Missing reference section? '22' on line 111 looks like a reference -- Missing reference section? '21' on line 546 looks like a reference -- Missing reference section? '5' on line 50 looks like a reference -- Missing reference section? '6' on line 50 looks like a reference -- Missing reference section? '7' on line 96 looks like a reference -- Missing reference section? '2' on line 58 looks like a reference -- Missing reference section? '12' on line 88 looks like a reference -- Missing reference section? '8' on line 96 looks like a reference -- Missing reference section? '9' on line 96 looks like a reference -- Missing reference section? '24' on line 112 looks like a reference -- Missing reference section? 'RFC 2131' on line 473 looks like a reference -- Missing reference section? 'RFC 2132' on line 526 looks like a reference -- Missing reference section? '3' on line 1815 looks like a reference -- Missing reference section? 'RFC3410' on line 1838 looks like a reference Summary: 3 errors (**), 0 flaws (~~), 9 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft E. Cardona 3 draft-ietf-ipcdn-cable-gateway-config-mib-00.txt K. Luehrs 4 Expires: December 2003 CableLabs 6 D. Mazzola 7 Texas Instruments 9 D. Jones 10 YAS BBV 11 June 2003 13 Cable Gateway Configuration Management Information Base 14 for CableHome� compliant Residential Gateways 16 Status of this Memo 18 This document is an Internet-Draft and is subject to all provisions 19 of Section 10 of RFC2026 [1]. 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 Copyright Notice 39 Copyright (C) The Internet Society (2003). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it defines a basic set of managed objects for SNMP- 46 based management of DHCP [22] functionality within a CableHome 47 compliant [21] residential gateway. 49 This memo specifies a MIB module in a manner that is compliant to the 50 SNMP SMIv2 [5][6][7]. The set of objects is consistent with the SNMP 51 framework and existing SNMP standards. 53 Conventions used in this document 55 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 56 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 57 document are to be interpreted as described in RFC-2119 [2]. 59 Table of Contents 61 1. The Internet-Standard Management Framework.....................2 62 2. Glossary.......................................................3 63 2.1 CableHome Residential Gateway..............................3 64 2.2 Portal Services............................................3 65 2.3 LAN IP Device..............................................3 66 2.4 WAN Management (WAN-Man) Address...........................3 67 2.5 WAN Data (WAN-Data) Address................................3 68 2.6 LAN Translated (LAN-Trans) Address.........................3 69 2.7 LAN Passthrough (LAN-Pass) Address.........................4 70 2.8 Cable Gateway DHCP Portal (CDP)............................4 71 3. Overview.......................................................4 72 3.1 Structure of the MIB.......................................5 73 3.2 Cable Gateway Configuration System Description.............5 74 4. MIB Definitions...............................................16 75 5. Acknowlegements...............................................38 76 6. Formal Syntax.................................................39 77 7. Security Considerations.......................................39 78 8. Normative References..........................................40 79 9. Informative References........................................41 80 10. Intellectual Property........................................42 81 11. Author's Addresses...........................................42 82 12. Full Copyright Statement.....................................43 84 1. The Internet-Standard Management Framework 86 For a detailed overview of the documents that describe the current 87 Internet-Standard Management Framework, please refer to section 7 of 88 RFC 3410 [12]. 90 Managed objects are accessed via a virtual information store, termed 91 the Management Information Base or MIB. MIB objects are generally 92 accessed through the Simple Network Management Protocol (SNMP). 93 Objects in the MIB are defined using the mechanisms defined in the 94 Structure of Management Information (SMI). This memo specifies a MIB 95 module that is compliant to the SMIv2, which is described in STD 58, 96 RFC 2578 [7], STD 58, RFC 2579 [8] and STD 58, RFC 2580 [9]. 98 2. Glossary 100 The terms in this document are derived either from normal cable 101 system usage, from normal residential gateway operation, or from the 102 documents associated with the CableHome Specifications [21]. 104 2.1 CableHome Residential Gateway 106 A CableHome Residential gateway passes data traffic between the cable 107 operator's broadband data network (the Wide Area Network, WAN) and 108 the Local Area Network (LAN) in the cable data service subscriber's 109 residence or business. In addition to passing traffic between the WAN 110 and LAN, the CableHome Residential Gateway provides several services 111 including a DHCP client and a DHCP server (RFC2131) [22], a DNS 112 server (RFC 3467) [24], management services as enabled by 113 SNMPv1/v2c/v3 agent compliant with the RFCs listed in Section 1, and 114 security services including stateful packet inspection firewall 115 functionality and software code image verification using techniques. 117 2.2 Portal Services 119 A logical element aggregating the set of CableHome-specified 120 functionality in a CableHome compliant cable gateway device. 122 2.3 LAN IP Device 124 A LAN IP Device is representative of a typical IP device expected to 125 reside on home networks, and is assumed to contain a TCP/IP stack as 126 well as a DHCP client. 128 2.4 WAN Management (WAN-Man) Address 130 WAN Management Addresses are intended for network management traffic 131 on the cable network between the network management system and the PS 132 element. Typically, these addresses will reside in private IP address 133 space. 135 2.5 WAN Data (WAN-Data) Address 137 WAN Data Addresses are intended for subscriber application traffic on 138 the cable network and beyond, such as traffic between LAN IP Devices 139 and Internet hosts. Typically, these addresses will reside in public 140 IP address space. 142 2.6 LAN Translated (LAN-Trans) Address 143 LAN Translated Addresses are intended for subscriber application and 144 management traffic on the home network between LAN IP Devices and the 145 PS element. Typically, these addresses will reside in private IP 146 address space, and can typically be reused across subscribers. 148 2.7 LAN Passthrough (LAN-Pass) Address 150 LAN Passthrough Addresses are intended for subscriber application 151 traffic, such as traffic between LAN IP Devices and Internet hosts, 152 on the home network, the cable network, and beyond. Typically, these 153 addresses will reside in public IP address space. 155 2.8 Cable Gateway DHCP Portal (CDP) 157 A logical element residing within the PS that encapsulates DHCP 158 functionality within a Cable Gateway Device. This includes both DHCP 159 client as well as DHCP server capabilities. 161 3. Overview 163 This MIB provides a set of objects required for the management of 164 DHCP client and server functionality within CableHome compliant 165 Residential Gateways (RG). The specification is derived from the 166 CableHome Specification [21]. 168 The DHCP client within a Cable Gateway will acquire one or more 169 addresses from WAN based DHCP servers. Collectively, these are known 170 as WAN addresses. These addresses are used for both management 171 traffic (WAN management addresses) and data traffic (WAN data 172 addresses) to and from the WAN side of the residential gateway. 174 The DHCP server within a Cable Gateway will provide private addresses 175 to LAN IP Devices. These addresses will be translated to and from one 176 of the WAN IP addresses for traffic that enters or exits the LAN, and 177 are and collectively known as LAN Translated Addresses. 179 There are a number of logical functional elements used to describe 180 Cable Gateway configuration functionality. 182 � The Portal Services (PS) logical element is the functional entity 183 that aggregates all specified Cable Gateway capabilities. 185 � The Cable Gateway DHCP Portal (CDP) logical element is the 186 functional entity that embodies the Cable Gateway DHCP 187 capabilities. 189 � 191 3.1 Structure of the MIB 193 This MIB is structured into three groups: 195 � The cabhCdpBase group provides baseline and information for RG DHCP 196 client and server functionality, including reset information, 197 counts for WAN addresses acquired, and counts for LAN addresses 198 served. 200 � The cabhCdpAddr group provides information about dynamically 201 acquired and served addresses within the RG, and includes the 202 following tables: 204 o cabhCdpLanAddrTable: information and reservations for addresses 205 served to the LAN 206 o cabhCdpWanDataAddrTable: WAN address acquisition information 207 o cabhCdpWanDataAddrServerTable: WAN based DNS server information 209 � The cabhCdpServer group provides information about the RG DHCP 210 service (address pool range, subnet information, RG Based server 211 info, etc). 213 3.2 Cable Gateway Configuration System Description 215 The functional element that encapsulates DHCP functionality within 216 the Cable Gateway is known as the Cable Gateway DHCP Portal (CDP). 218 The CDP operating assumptions include: 220 � LAN IP Devices implement a DHCP client as defined by [RFC 2131]. 222 � The cable network provisioning system implements a DHCP server as 223 defined by [RFC 2131]. 225 � If the cable network provisioning system's DHCP server supports 226 DHCP Option 61 (client identifier option),the WAN-Man and all WAN- 227 Data IP interfaces can share a common MAC address. 229 � LAN IP Devices may support various DHCP Options and BOOTP Vendor 230 Extensions, allowed by [RFC 2132] (23). 232 The following design guidelines drive the capabilities defined for 233 the CDP: 235 � CableHome addressing mechanisms will be MSO controlled, and will 236 provide MSO knowledge of and accessibility to CableHome network 237 elements and LAN IP Devices. 239 � CableHome address acquisition and management processes will not 240 require human intervention (assuming that a user/household account 241 has already been established). 243 � CableHome address acquisition and management will be scalable to 244 support the expected increase in the number of LAN IP devices. 246 � It is preferable for LAN IP Device addresses to remain the same 247 after events such as a power cycle or Internet Service Provider 248 switch. 250 � CableHome will provide a mechanism by which the number of LAN IP 251 Devices in the LAN-Trans realm can be monitored and controlled. 253 � In home communication will continue to work as provisioned during 254 periods of Headend address server outage. Addressing support will 255 be provided for newly added LAN IP Devices and address expirations 256 during remote address server outages. 258 � IP addresses will be conserved when possible (both globally 259 routable addresses and private cable network management addresses). 261 3.2.1 Cable Gateway DHCP Portal (CDP) System Description 263 The Cable Gateway DHCP Portal is the logical entity that is 264 responsible for CableHome addressing activities. The CDP address 265 request and address allocation responsibilities within the CableHome 266 environment include: 268 � IP address assignment, IP address maintenance, and the delivery of 269 configuration parameters (via DHCP) to LAN IP Devices in the LAN- 270 Trans Address Realm. 272 � Acquisition of a WAN-Man and zero or more WAN-Data IP addresses and 273 associated DHCP configuration parameters for the Portal Services 274 (PS) element. 276 � Provide information to the CableHome Name Portal (CNP) in support 277 of LAN IP Device host name services. 279 The PS maintains two hardware addresses, one of which is to be used 280 to acquire an IP address for management purpose, the other could be 281 used for the acquisition of one or more IP address(es) for data. To 282 prevent hardware address spoofing, the PS does not allow either of 283 the two hardware addresses to be modified. 285 The Portal Services element requires an IP Address on the home LAN 286 for its role on the LAN as a router (see Section 8 in [21], Packet 287 Handling and Address Translation), DHCP Server (CDS), and DNS 288 Server). For each of these three Portal Service Element server and 289 router functions, a LAN IP address is saved in the PS database. Each 290 can be accessed via a different MIB object, which are listed below: 292 � Router (default gateway) Address cabhCdpServerRouter 293 � Domain Name Server (DNS) Address cabhCdpServerDnsAddress 294 � Dynamic Host Configuration Server (DHCP) (CDS) Address 295 cabhCdpServerDhcpAddress 297 The default value of cabhCdpServerRouter is 192.168.0.1. The default 298 values of cabhCdpServerDnsAddress and cabhCdpServerDhcpAddress are 299 equal to the value of cabhCdpServerRouter. The CDP capabilities are 300 embodied by two functional elements residing within the CDP: 302 � the Cable Gateway DHCP Server (CDS) 303 � the Cable Gateway DHCP Client (CDC). 305 The CDC exchanges DHCP messages with the DHCP server in the cable 306 network (WAN-Management address realm) to acquire an IP address and 307 DHCP options for the PS, for management purposes. The CDC could also 308 exchange DHCP messages with the DHCP server in the cable network 309 (WAN-Data address realm) to acquire zero or more IP address(es) on 310 behalf of LAN IP Devices in the LAN-Trans realm. The CDS exchanges 311 DHCP messages with LAN IP Devices in the LAN-Trans realm, and assigns 312 private IP addresses, grants leases to, and could provide DHCP 313 options to DHCP clients within those LAN IP Devices. LAN IP Devices 314 in the LAN-Pass realm receive their IP addresses, leases, and DHCP 315 options directly from the DHCP server in the cable network. The CDP 316 simply bridges DHCP messages between the DHCP server in the cable 317 network and LAN IP Devices in the LAN-Pass realm. Figure 1 318 illustrates these concepts. 320 +---------------------+ 321 | Cable Gateway | 322 | | 323 | /-----------------\ | 324 Wan-Data | | CDP | | Lan-Pass 325 SERVICE Realm | | | | Realm 326 PROVIDER--------*-----------------------------------------LAN IP Dev 327 \ | | | | 328 \ | | /*****\ /*****\ | | 329 \--------- | | | | 330 CABLE | | | CDC | | CDS | | | 331 NETWORK---------------------- | | --------------------LAN IP Dev 332 Wan-Man | | | | | | | | Lan-Trans 333 Realm | | | | | | | | Realm 334 | | \*****/ \*****/ | | 335 | | | | 336 | \-----------------/ | 337 | | 338 +---------------------+ 340 Figure 1 342 3.2.1.1 Cable Gateway DHCP Server (CDS) System Description 344 The CDS is a standard DHCP server as defined in [RFC 2131], and 345 responsibilities include: 347 � The CDS assigns addresses to and delivers DHCP configuration 348 parameters to LAN IP Devices receiving an address in the LAN-Trans 349 address realm. The CDS learns DHCP options from the NMS system and 350 provides these DHCP options to LAN IP Devices. If DHCP options have 351 not been provided by the NMS system (for example when the PS boots 352 during a cable outage), the CDS relies on built-in default values 353 (DefVals) for required options. 355 � The CDS is able to provide DHCP addressing services to LAN IP 356 Devices, independent of the WAN connectivity state. 358 � The number of addresses supplied by the CDS to LAN IP Devices is 359 controllable by the NMS system. The behavior of the CDS when a 360 cable operator settable limit is exceeded is also configurable via 361 the NMS. Possible CDS actions when the limit is exceeded include 362 (1) assign a LAN-Trans IP address and treat the WAN to LAN 363 interconnection as would normally occur if the limit had not been 364 exceeded and (2) do not assign an address to requesting LAN IP 365 devices. An address threshold setting of 0 indicates the maximum 366 threshold possible for the LAN-Trans IP address pool defined by the 367 pool "start" (cabhCdpLanPoolStart) and "end" (cabhCdpLanPoolEnd) 368 values. 370 � In the absence of time of day information from the Time of Day 371 (ToD) server, the CDS uses the PS default starting time of 0 372 (January 1, 1970), updates the Expire Time for any active leases in 373 the LAN-Trans realm to re-synchronize with DHCP clients in LAN IP 374 Devices, and maintains leases based on that starting point until 375 the PS synchronizes with the Time of Day server in the cable 376 network. 378 � During the PS Boot process, the CDS remains inactive until 379 activated by the PS. 381 � If the PS Primary Packet-handling mode [21] has been set to 382 Passthrough AND the PS provisioning process has completed, then the 383 CDS is disabled. 385 LAN IP Devices may receive addresses that reside in the LAN-Pass 386 realm. As shown in Figure 7-2 [21], LAN-Pass address requests are 387 served by the WAN addressing infrastructure, not the PS. LAN-Pass 388 addressing processes will occur when the PS is configured to operate 389 in Passthrough Mode or Mixed Bridging/Routing Mode. In these cases, 390 DHCP interactions will take place directly between LAN IP Devices 391 and Headend servers, and CableHome does not specify the process. 393 Throughout this document, the terms Dynamic Allocation and Manual 394 Allocation are used as defined in [RFC 2131]. The CDS Provisioned 395 DHCP Options, cabhCdpServer objects in the CDP MIB, are DHCP Options 396 that can be provisioned by the NMS, and are offered by the CDS to LAN 397 IP devices assigned a LAN-Trans address. CDS Provisioned DHCP 398 Options, cabhCdpServer objects, persist after a PS power cycle and 399 the NMS system can establish, read, write and delete these objects. 400 CDS Provisioned DHCP Options, cabhCdpServer objects, are retained 401 during periods of cable outage and these objects are offered to LAN 402 IP devices assigned a LAN-Trans address during periods of cable 403 outage. The CDC persistent storage of DHCP options is consistent with 404 [RFC 2131] section 2.1. The default values of CDS Provisioned DHCP 405 Options, cabhCdpServer objects, are defined and the NMS can reset the 406 CDS Provisioned DHCP Options, cabhCdpServer objects, to their default 407 values, by writing to the cabhCdpSetToFactory MIB object. 409 The CDS Address Threshold (cabhCdpLanTrans) objects contain the event 410 control parameters used by the CDS to cause a notification to be sent 411 to the Headend management system, when the number of LAN-Trans 412 addresses assigned by the CDS exceeds the preset threshold. 414 The Address Count (cabhCdpLanTransCurCount) object is a value 415 indicating the number of LAN-Trans addresses assigned by the CDS that 416 have active DHCP leases. 418 The Address Threshold (cabhCdpLanTransThreshold) object is a value 419 indicating when a notification is generated to the Headend management 420 system. The notification is generated when the CDS assigns an address 421 to the LAN IP Device that causes the Address Count 422 (cabhCdpLanTransCurCount) to exceed the Address Threshold 423 (cabhCdpLanTransThreshold). 425 The Threshold Exceeded Action (cabhCdpLanTransAction) is the action 426 taken by the CDS while the Address Count (cabhCdpLanTransCurCount) 427 exceeds the Address Threshold (cabhCdpLanTransThreshold). If the 428 Threshold Exceeded Action (cabhCdpLanTransAction) allows address 429 assignments after the count is exceeded, the notification is 430 generated each time an address is assigned. The defined actions are 431 a) assign a LAN-Trans address as normal, and b) do not assign an 432 address to the next requesting LAN IP Device. 434 The Address Count (cabhCdpLanTransCurCount) continues to be updated 435 during periods of cable outage. The CDS MIB also contains the Address 436 Pool Start (cabhCdpLanPoolStart) and Address Pool End 437 (cabhCdpLanPoolEnd) parameters. These parameters indicate the range 438 of addresses in the LAN-Trans realm that can be assigned by the CDS 439 to LAN IP Devices. 441 The CDP LAN Address Table (cabhCdpLanAddrTable) contains the list of 442 parameters associated with addresses allocated to LAN IP Devices with 443 LAN-Trans addresses. These parameters include: 445 � The Client Identifiers [RFC 2132] section 9.14 446 (cabhCdpLanAddrClientID) 448 � The LAN IP address assigned to the client (cabhCdpLanAddrIp) 450 � An indication that the address was allocated either manually or 451 dynamically (via the CDP)(cabhCdpLanAddrConfig) 453 The CDS stores information about the identification of a LAN IP 454 Device in the object cabhCdpLanAddrClientID. The first priority for 455 the value to be stored in this object is the Client ID value passed 456 by the LAN IP Device in DHCP Option 61, Client Identifier. If no 457 value is passed in Option 61, the CDS stores the value passed in the 458 chaddr field of the DHCP DISCOVER message issued by the LAN IP 459 Device. 461 The CDS creates a CDP Table (cabhCdpLanAddrTable) entry when it 462 allocates an IP address to a LAN IP Device. The CDS can create CDP 463 Table (cabhCdpLanAddrTable) entries during periods of cable outage. 465 The CDP Table (cabhCdpLanAddrTable) maintains a DHCP lease time for 466 each LAN IP Device. 468 NMS-provisioned CDP Table (cabhCdpLanAddrTable) entries are retained 469 during periods of cable outage and persist across a PS power-cycle. 471 3.2.1.2 Cable Gateway DHCP Client (CDC) System Description 473 The CDC is a standard DHCP client as defined in [RFC 2131], and 474 responsibilities include: 476 � The CDC makes requests to Headend DHCP servers for the acquisition 477 of addresses in the WAN-Man and may make requests to Headend DHCP 478 servers for the acquisition of addresses in the WAN-Data address 479 realms. The CDC also understands and acts upon a number of 480 CableHome DHCP configuration parameters. 482 � The CDC supports acquisition of one WAN-Man IP address and zero or 483 more WAN-Data IP addresses. 485 � The CDC supports the Vendor Class Identifier Option (DHCP option 486 60), the Vendor Specific Information option (DHCP Option 43), and 487 the Client Identifier Option (DHCP option 61). 489 � In the default case, the CDC will acquire a single IP address for 490 simultaneous use by the WAN-Man and WAN-Data IP interfaces. In 491 order to minimize changes needed to existing Headend DHCP servers, 492 the use of a Client Identifier (DHCP option 61) by the CDC is not 493 required in this default case. 495 The CDP supports various DHCP Options and BOOTP Vendor Extensions, 496 allowed by [RFC 2132]. 498 The Vendor Class Identifier Option (DHCP option 60) defines a 499 CableLabs device class. For CableHome 1.0, the Vendor Class 500 Identifier Option will contain the string "CableHome1.0", to identify 501 a CableHome 1.0 Portal Services (PS) logical element, whenever the 502 CDC requests a WAN-Man or WAN-Data address. 504 The Vendor Specific Information option (DHCP Option 43) further 505 identifies the type of device and its capabilities. It describes the 506 type of component that is making the request (embedded or standalone, 507 CM or PS), the components that are contained in the device (CM, MTA, 508 PS, etc.), the device serial number, and also allows device specific 509 parameters. {add reference to CH spec and the DHCP options table} 511 The WAN-Data IP Address count parameter of the CDP MIB 512 (cabhCdpWanDataIpAddrCount) is the number of IP address leases the 513 CDC is required to attempt to acquire for the WAN side of NAT and 514 NAPT mappings. The default value of cabhCdpWanDataIpAddrCount is 515 zero, which means that, by default, the CDC will acquire only a WAN- 516 Man IP address. 518 3.2.1.2.1 Cable Gateway DHCP Client Option 61 520 The CableHome PS element can have one or more WAN IP addresses 521 associated with a one or more link layer (e.g. MAC) interfaces. 522 Therefore, the CDC cannot rely solely on a MAC address as a unique 523 client identifier value. 525 CableHome allows for the use of the Client Identifier Option (DHCP 526 option 61), [RFC 2132] section 9.14, to uniquely identify the logical 527 WAN interface associated with a particular IP address. 529 The PS is required to have two hardware addresses: one to be used to 530 uniquely identify the logical WAN interface associated with the WAN- 531 Man IP address (WAN-Man hardware address) and the other to be used to 532 uniquely identify the logical WAN interface associated with WAN-Data 533 IP addresses (WAN-Data hardware address). 535 3.2.1.2.2 WAN Address Modes 537 In order to enable compatibility with as many cable operator 538 provisioning systems as possible, the CDC will support the following 539 configurable WAN Address Modes: 541 � WAN Address Mode 0: The PS Element makes use of a single WAN IP 542 Address, acquired via DHCP using the WAN-Man hardware address. The 543 PS Element has one WAN-Man IP Interface and zero WAN-Data IP 544 Interfaces. This Address Mode is only applicable when the PS 545 Primary Packet-handling Mode (cabhCapPrimaryMode) is set to 546 Passthrough (refer to [21] Section 8.3.2). The cable operator's 547 Headend DHCP server typically needs no software modifications to 548 support this Address Mode. In WAN Address Mode 0, the value of 549 cabhCdpWanDataIpAddrCount is zero. 551 � WAN Address Mode 1: The PS Element makes use of a single WAN IP 552 Address, acquired via DHCP using the WAN-Man hardware address. The 553 PS Element has one WAN-Man IP Interface and one WAN-Data IP 554 Interface. These two Interfaces share a single, common IP address. 555 This Address Mode is only applicable when the PS Primary Packet- 556 handling Mode (cabhCapPrimaryMode) is set to NAPT. The cable 557 operator's Headend DHCP server typically needs no software 558 modifications to support this Address Mode. In WAN Address Mode 1, 559 the value of cabhCdpWanDataIpAddrCount is zero. 561 � WAN Address Mode 2: The PS Element acquires a WAN-Man IP address 562 using the unique WAN-Man hardware address, and is subsequently 563 configured by the NMS to request one or more unique WAN-Data IP 564 Address(es). The PS Element will have one WAN-Man and one or more 565 WAN-Data IP Interface(s). All WAN-Data IP addresses will share a 566 common hardware address that is unique from the WAN- Man hardware 567 address. The two or more Interfaces (one WAN-Man and one or more 568 WAN-Data) each has its own, unshared IP address. The CDP is 569 configured by the cable operator to operate in WAN Address Mode 2 570 by writing a nonzero value to cabhCdpWanDataIpAddrCount, via the PS 571 Configuration File or an SNMP set-request. This Address Mode is 572 applicable when the PS Primary Packet-handling Mode 573 (cabhCapPrimaryMode) is set to NAPT or NAT. The cable operator's 574 Headend DHCP server might need software modification to include 575 support for Client IDs (DHCP Option 61) so that it can assign 576 multiple IP addresses to the single WAN-Data hardware address. 578 There are four potential scenarios for WAN-Data IP addresses: 580 1. The PS is configured to request zero WAN-Data IP addresses. No 581 WAN-Data Client IDs are needed. 583 2. The PS is configured to request one or more WAN-Data IP addresses 584 and there are no MSO-configured cabhCdpWanDataAddrClientId entries in 585 the CDP MIB. The PS is required to auto-generate as many unique WAN- 586 Data Client IDs as the value of cabhCdpWanDataIpAddrCount. 588 3. The PS is configured to request one or more WAN-Data IP addresses 589 and there are at least as many MSO configured 590 cabhCdpWanDataAddrClientId entries as the value of 591 cabhCdpWanDataIpAddrCount, i.e., the MSO has provisioned enough WAN- 592 Data Client ID values. The PS does not auto-generate any Client IDs. 594 4. The PS is configured to request one or more WAN-Data IP addresses 595 and there are fewer MSO-configured cabhCdpWanDataAddrClientId entries 596 than the value of cabhCdpWanDataIpAddrCount, i.e., the MSO has 597 provisioned some but not provisioned enough WAN-Data Client ID 598 values. The PS is required to auto-generate enough additional unique 599 WAN-Data Client IDs to bring the total number of unique WAN-Data 600 Client IDs to the value of cabhCdpWanDataIpAddrCount. 602 If the cable operator desires for the PS to acquire one or more WAN- 603 Data IP addresses, that are distinct from the WAN-Man IP address, the 604 procedure is as follows. For all WAN Address Modes, the PS first 605 requests a WAN-Man IP address using the WAN-Man hardware address. The 606 procedure described below assumes the PS has already acquired a WAN- 607 Man IP address: 609 1. The cable operator optionally provisions the PS with unique 610 specific Client IDs, by writing values to the 611 cabhCdpWanDataAddrClientId entries of the CDP MIB 612 cabhCdpWanDataAddrTable, via the PS Configuration File or SNMP set- 613 request message(s). 615 2. The cable operator configures the CDP to operate in WAN Address 616 Mode 2 by writing cabhCdpWanDataIpAddrCount to a nonzero value 617 through the PS Configuration File or SNMP set-request message. 619 3. After the CDP has been configured to operate in WAN Address Mode 2 620 as described in step 2), the PS checks to see if Client ID values 621 have been provisioned by the NMS as described in step 1). If a number 622 of Client ID values greater than or equal to the value of 623 cabhCdpWanDataIpAddrCount have been provisioned, the PS uses these 624 values in DHCP Option 61 when requesting the WAN-Data IP address(es). 625 If Client ID values have not been provisioned, i.e., if the 626 cabhCdpWanDataAddrClientId entries do not exist, or if the number of 627 Client ID values provisioned is less than the value of 628 cabhCdpWanDataIpAddrCount, the PS generates a number of unique Client 629 ID values such that, in combination with the provisioned Client IDs, 630 the total number of unique Client IDs equals the value of 631 cabhCdpWanDataIpAddrCount. The PS generates Client ID values by using 632 the WAN-Data hardware address alone for the first requested WAN-Data 633 IP address, and by concatenating the WAN- Data hardware address with 634 a count that is 8 bits in length for the second and all subsequent 635 WAN-Data IP addresses. If no Client IDs have been provisioned by the 636 NMS, the first 8-bit Count value is 0x02 (indicating the second 637 requested WAN-Data IP address), the second count value is 0x03, and 638 so on. 640 The following is an example for the case when no Client IDs have been 641 provisioned by the network management system. Given WAN-Data 642 hardware address 0xCDCDCDCDCDCD: 644 � PS-generated Client ID for the first requested WAN-Data IP address: 645 0xCDCDCDCDCDCD 646 � PS-generated Client ID for the second requested WAN-Data IP 647 address: 0xCDCDCDCDCDCD02 648 � PS-generated Client ID for the third requested WAN-Data IP address: 649 0xCDCDCDCDCDCD03 650 � PS-generated Client ID for the nth requested WAN-Data IP address: 651 0xCDCDCDCDCDCDn (n=<0xFF) 653 If some Client IDs have been provisioned by the NMS but the number is 654 less than the value of cabhCdpWanDataIpAddrCount, the PS generates 655 additional Client IDs as needed to bring the total number of Client 656 IDs to the value of cabhCdpWanDataIpAddrCount. The PS will generate 657 these additional Client IDs values by appending an 8-bit count value 658 to the WAN-Data hardware address, starting with 0x02, unless that 659 would duplicate a provisioned Client ID. If the Client IDs 660 provisioned by the NMS follow the same format (hardware address with 661 8-bit count value), the PS is required to use a unique count value so 662 as to not duplicate a provisioned Client ID. 664 Example for the case when Client IDs have been provisioned by the NMS 665 (three provisioned Client ID values, cabhCdpWanDataIpAddrCount = 5). 666 Given WAN-Data hardware address 0xCDCDCDCDCDCD: 668 � First provisioned Client ID for the first WAN-Data IP address: 669 0x0A0A0A0A0A1A 670 � Second provisioned Client ID for the second WAN-Data IP address: 671 0x0A0A0A0A0A2A 672 � Third provisioned Client ID for the third WAN-Data IP address: 673 0x0A0A0A0A0A3A 674 � First Client ID generated by the PS for the fourth requested WAN- 675 Data IP address: 0xCDCDCDCDCDCD02 676 � Second Client ID generated by the PS for the fifth requested WAN- 677 Data IP address: 0xCDCDCDCDCDCD03 679 4. The PS adds the Client ID values it generates as 680 cabhCdpWanDataAddrClientId entries to the end of the 681 cabhCdpWanDataAddrTable. 683 5. The PS (CDC) requests (repeating the DHCP DISCOVER process as 684 needed) as many unique WAN-Data IP addresses as the value of 685 cabhCdpWanDataIpAddrCount specifies, using the WAN-Data hardware 686 address in the chaddr field of the DHCP message and the Client ID 687 value(s) from step 3) in DHCP Option 61, beginning with the first 688 cabhCdpWanDataAddrClientId entry of the cabhCdpWanDataAddrTable. The 689 CDC is not permitted to request more WAN-Data IP addresses than the 690 value of cabhCdpWanDataIpAddrCount, even if the number of provisioned 691 Client IDs is greater than the value of cabhCdpWanDataAddrTable. 693 4. MIB Definitions 695 CABH-IETF-CDP-MIB DEFINITIONS ::= BEGIN 697 IMPORTS 698 MODULE-IDENTITY, 699 OBJECT-TYPE, 700 Integer32, 701 Unsigned32, 702 mib-2 FROM SNMPv2-SMI 703 MacAddress, 704 TruthValue, 705 TimeStamp, 706 DateAndTime, 707 RowStatus FROM SNMPv2-TC -- RFC2579 708 OBJECT-GROUP, 709 MODULE-COMPLIANCE FROM SNMPv2-CONF -- RFC2580 710 InetAddressType, 711 InetAddress FROM INET-ADDRESS-MIB -- RFC3291 712 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; -- RFC2571 714 cabhCdpMib MODULE-IDENTITY 715 LAST-UPDATED "200306210000Z" -- Jun 21, 2003 716 ORGANIZATION "IETF IPCDN Working Group" 717 CONTACT-INFO 718 "Kevin Luehrs 719 Postal: Cable Television Laboratories, Inc. 720 400 Centennial Parkway 721 Louisville, Colorado 80027-1266 722 U.S.A. 723 Phone: +1 303-661-9100 724 Fax: +1 303-661-9199 725 E-mail: k.luehrs@cablelabs.com; mibs@cablelabs.com 727 IETF IPCDN Working Group 728 General Discussion: ipcdn@ietf.org 729 Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn 730 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 731 Co-chairs: Richard Woundy, 732 Richard_Woundy@cable.comcast.com 733 Jean-Francois Mule, jf.mule@cablelabs.com" 734 DESCRIPTION 735 "This MIB module supplies the basic management objects 736 for the CableHome DHCP Portal (CDP) portion of the PS 737 database. 739 Copyright (C) The Internet Society (2003). This version 740 of this MIB module is part of RFC xxxx; see the RFC 741 itself for full legal notices." 742 REVISION "200306210000Z" -- Jun 21, 2003 743 DESCRIPTION 744 "Initial version, published as RFC xxxx." 745 -- RFC editor to assign xxxx 746 ::= { mib-2 xx } 747 -- xx to be assigned by IANA 749 cabhCdpObjects OBJECT IDENTIFIER ::= { cabhCdpMib 1 } 750 cabhCdpBase OBJECT IDENTIFIER ::= { cabhCdpObjects 1 } 751 cabhCdpAddr OBJECT IDENTIFIER ::= { cabhCdpObjects 2 } 752 cabhCdpServer OBJECT IDENTIFIER ::= { cabhCdpObjects 3 } 754 -- 755 -- The following group describes the base objects in the CableHome 756 -- DHCP Portal. The rest of this group deals addresses defined on 757 -- the LAN side. 758 -- 760 cabhCdpSetToFactory OBJECT-TYPE 761 SYNTAX TruthValue 762 MAX-ACCESS read-write 763 STATUS current 764 DESCRIPTION 765 "Reading this object always returns false(2). When the 766 cabhCdpSetToFactory object is set to true(1), the PS 767 must take the following actions: 769 1. Clear all cabhCdpLanAddrEntries in the CDP LAN Address 770 Table. 771 2. The CDS must offer the factory default DHCP options at 772 the next lease renewal time. 773 3. Reset the following objects to their factory default 774 values: 776 cabhCdpLanTransThreshold, 777 cabhCdpLanTransAction, 778 cabhCdpWanDataIpAddrCount, 779 cabhCdpLanPoolStartType, 780 cabhCdpLanPoolStart, 781 cabhCdpLanPoolEndType, 782 cabhCdpLanPoolEnd, 783 cabhCdpServerNetworkNumberType, 784 cabhCdpServerNetworkNumber, 785 cabhCdpServerSubnetMaskType, 786 cabhCdpServerSubnetMask, 787 cabhCdpServerTimeOffset, 788 cabhCdpServerRouterType, 789 cabhCdpServerRouter, 790 cabhCdpServerDnsAddressType, 791 cabhCdpServerDnsAddress, 792 cabhCdpServerSyslogAddressType, 793 cabhCdpServerSyslogAddress, 794 cabhCdpServerDomainName, 795 cabhCdpServerTTL, 796 cabhCdpServerInterfaceMTU, 797 cabhCdpServerVendorSpecific, 798 cabhCdpServerLeaseTime, 799 cabhCdpServerDhcpAddressType, 800 cabhCdpServerDhcpAddress, 801 cabhCdpServerCommitStatus" 802 ::= { cabhCdpBase 1 } 804 cabhCdpLanTransCurCount OBJECT-TYPE 805 SYNTAX Unsigned32 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "The current number of active leases in the 810 cabhCdpLanAddrTable (the number of row entries in the 811 table that have a cabhCdpLanAddrMethod value of 812 reservationActive(2) or dynamicActive (4)). This count 813 does not include expired leases or reservations not 814 associated with a current lease." 815 ::= { cabhCdpBase 2 } 817 cabhCdpLanTransThreshold OBJECT-TYPE 818 SYNTAX INTEGER (0..65533) 819 MAX-ACCESS read-write 820 STATUS current 821 DESCRIPTION 822 "The threshold number of LAN-Trans IP addresses allocated 823 or assigned above which the PS generates an alarm 824 condition. Whenever an attempt is made to allocate a 825 LAN-Trans IP address when cabhCdpLanTransCurCount is 826 greater than or equal to cabhCdpLanTransThreshold, an 827 event is generated. A value of 0 indicates that the CDP 828 sets the threshold at the highest number of addresses in 829 the LAN address pool." 830 DEFVAL { 0 } 831 ::= { cabhCdpBase 3 } 833 cabhCdpLanTransAction OBJECT-TYPE 834 SYNTAX INTEGER { 835 normal(1), 836 noAssignment(2) 837 } 839 MAX-ACCESS read-write 840 STATUS current 841 DESCRIPTION 842 "The action taken when the CDS assigns a LAN-Trans 843 address and the number of LAN-Trans addresses assigned 844 (cabhCdpLanTransCurCount) is greater than the threshold 845 (cabhCdpLanTransThreshold). The actions are as follows: 847 normal - assign a LAN-Trans IP address as would normally 848 occur if the threshold was not exceed. 850 noAssignment - do not assign a LAN-Trans IP address" 851 DEFVAL { normal } 852 ::= { cabhCdpBase 4 } 854 cabhCdpWanDataIpAddrCount OBJECT-TYPE 855 SYNTAX INTEGER ( 0..63 ) 856 MAX-ACCESS read-write 857 STATUS current 858 DESCRIPTION 859 "This is the number of WAN-Data IP addresses the PS's CDC 860 must attempt to acquire via DHCP." 861 DEFVAL { 0 } 862 ::= { cabhCdpBase 5 } 864 cabhCdpLastSetToFactory OBJECT-TYPE 865 SYNTAX TimeStamp 866 MAX-ACCESS read-only 867 STATUS current 868 DESCRIPTION 869 "The value of sysUpTime when cabhCdpSetToFactory was 870 last set to true. Zero if never reset." 871 ::= { cabhCdpBase 6 } 873 -- 874 -- CDP Address Management Tables 875 -- 876 --============================================================== 877 -- 878 -- cabhCdpLanAddrTable (CDP LAN Address Table) 879 -- 880 -- The cabhCdpLanAddrTable contains the DHCP parameters 881 -- for each IP address served to the LAN-Trans realm. 882 -- 883 -- This table contains a list of entries for the LAN side CDP 884 -- parameters. These parameters can be set either by the CDP or 885 -- by the cable operator through the CMP. 886 -- 887 --================================================================ 888 cabhCdpLanAddrTable OBJECT-TYPE 889 SYNTAX SEQUENCE OF CabhCdpLanAddrEntry 890 MAX-ACCESS not-accessible 891 STATUS current 892 DESCRIPTION 893 "This table is a list of LAN-Trans realm parameters. 894 This table has one row entry for each allocated LAN-Trans 895 IP address. Each row must have at least a valid 896 cabhCdpLanAddrMethod, a cabhCdpLanAddrIpType, a unique 897 cabhCdpLanAddrIp, and a unique cabhCdpLanAddrClientId 898 value. 900 Static/Manual address assignment: To create a new DHCP 901 address reservation, the NMS creates a row with: an index 902 comprised of a new cabhCdpLanAddrIp and its 903 cabhCdpLanAddrIpType, a new unique cabhCdpLanAddrClientID 904 (an empty LeaseCreateTime and empty LeaseExpireTime,) 905 and a cabhCdpLanDataAddrRowStatus of createAndGo(4). 906 If the syntax and values of the new row - indicating a 907 reservation - are valid, the PS must set 908 cabhCdpLanAddrMethod to reservationInactive(1) and 909 cabhCdpLanDataAddrRowStatus to active(1). When the PS 910 grants a lease for a reserved IP, it must set the 911 cabhCdpLanAddrMethod object for that row to 912 reservationActive(2). When a lease for a reserved IP 913 expires, the PS must set the corresponding row�s 914 cabhCdpLanAddrMethod object to reservationInactive(1). 915 For row entries that represent lease reservations - rows 916 in which the cabhCdpLanAddrMethod object has a value of 917 either reservationInactive(1) or reservationActive(2) - 918 the cabhCdpLanAddrIpType, cabhCdpLanAddrIp, 919 cabhCdpLanAddrClientID, cabhCdpLanAddrMethod, and 920 cabhCdpLanAddrHostName object values must persist across 921 PS reboots. 923 Dynamic address assignment: When the PS grants a lease 924 for a non-reserved IP, it must set the 925 cabhCdpLanAddrMethod object for that row to 926 dynamicActive(4). When a lease for a non-reserved IP 927 expires, the PS must set the corresponding row�s 928 cabhCdpLanAddrMethod object to dynamicInactive(3). 929 The PS must create new row entries using 930 cabhCdpLanAddrIp values that are unique to this table. 932 If all cabhCdpLanAddrIp values in the range defined by 933 cabhCdpLanPoolStart and cabhCdpLanPoolEnd are in use in 934 this table, the PS may overwrite the 935 cabhCdpLanAddrClientId of a row that has a 936 cabhCdpLanAddrMethod object with a value of 937 dynamicInactive(3) with a new cabhCdpLanAddrClientId 938 value and use that cabhCdpLanAddrIp as part of a new 939 lease. For row entries that represent active leases - 940 rows in which the cabhCdpLanAddrMethod object has a value 941 of dynamicActive(4) - the cabhCdpLanAddrIpType, 942 cabhCdpLanAddrIp, cabhCdpLanAddrClientID, 943 cabhCdpLanAddrMethod, and cabhCdpLanAddrHostName object 944 values must persist across PS reboots." 946 ::= { cabhCdpAddr 1 } 948 cabhCdpLanAddrEntry OBJECT-TYPE 949 SYNTAX CabhCdpLanAddrEntry 950 MAX-ACCESS not-accessible 951 STATUS current 952 DESCRIPTION 953 "List of general parameters pertaining to LAN-Trans IP 954 address reservations and leases. 956 Implementors need to be aware that if the size 957 of cabhCdpLanAddrIp exceeds 115 octets then OIDs 958 of column instances in this table will have more 959 than 128 sub-identifiers and cannot be accessed 960 using SNMPv1, SNMPv2c, or SNMPv3." 961 INDEX { cabhCdpLanAddrIpType, cabhCdpLanAddrIp } 962 ::= { cabhCdpLanAddrTable 1 } 964 CabhCdpLanAddrEntry ::= SEQUENCE { 965 cabhCdpLanAddrIpType InetAddressType, 966 cabhCdpLanAddrIp InetAddress, 967 cabhCdpLanAddrClientID MacAddress, 968 cabhCdpLanAddrLeaseCreateTime DateAndTime, 969 cabhCdpLanAddrLeaseExpireTime DateAndTime, 970 cabhCdpLanAddrMethod INTEGER, 971 cabhCdpLanAddrHostName SnmpAdminString, 972 cabhCdpLanAddrRowStatus RowStatus 973 } 975 cabhCdpLanAddrIpType OBJECT-TYPE 976 SYNTAX InetAddressType 977 MAX-ACCESS not-accessible 978 STATUS current 979 DESCRIPTION 980 "The type of IP address assigned to the LAN IP Device in 981 the LAN-Trans Realm." 983 ::= { cabhCdpLanAddrEntry 1 } 985 cabhCdpLanAddrIp OBJECT-TYPE 986 SYNTAX InetAddress 987 MAX-ACCESS not-accessible 988 STATUS current 989 DESCRIPTION 990 "The address assigned to the LAN IP Device. This 991 parameter is entered by the CDP when the CDS grants a 992 lease to a LAN IP Device in the LAN-Trans realm and 993 creates a row in this table. 994 Alternatively, this parameter can be entered by the NMS 995 through the CMP, when the NMS creates a new DHCP address 996 reservation. 997 Each cabhCdpLanAddrIp in the table must fall within the 998 range of IPs defined inclusively by cabhCdpLanPoolStart 999 and cabhCdpLanPoolEnd. The PS must return an 1000 inconsistentValue error if the NMS attempts to create a 1001 row entry with a cabhCdpLanAddrIP value that falls 1002 outside of this range or is not unique fom all existing 1003 cabhCdpLanAddrIP entries in this table. The address type 1004 of this object is specified by cabhCdpLanAddrIpType." 1006 ::= { cabhCdpLanAddrEntry 2 } 1008 cabhCdpLanAddrClientID OBJECT-TYPE 1009 SYNTAX MacAddress 1010 MAX-ACCESS read-create 1011 STATUS current 1012 DESCRIPTION 1013 "The client's (i.e., LAN IP Device's) hardware address 1014 as indicated in the chaddr field of its DHCP REQUEST 1015 message. There is a one-to-one relationship between the 1016 hardware address and the LAN IP Device. This parameter 1017 is entered by the PS (CDP) when the CDS grants a lease 1018 to a LAN IP Device in the LAN-Trans realm and creates a 1019 row in this table. Alternatively this parameter can be 1020 created by the NMS through the CMP, when the NMS creates 1021 a new DHCP address reservation by accessing the 1022 cabhCdpLanDataAddrRowStatus object with an index 1023 comprised of a unique cabhCdpLanAddrIp and creating a 1024 row with a unique cabhCdpLanAddrClientID." 1025 ::= { cabhCdpLanAddrEntry 3 } 1027 cabhCdpLanAddrLeaseCreateTime OBJECT-TYPE 1028 SYNTAX DateAndTime 1029 MAX-ACCESS read-only 1030 STATUS current 1031 DESCRIPTION 1032 "This is the date and time that the LAN-Trans lease 1033 was created (if it has not yet been renewed) or last 1034 renewed." 1036 ::= { cabhCdpLanAddrEntry 4 } 1038 cabhCdpLanAddrLeaseExpireTime OBJECT-TYPE 1039 SYNTAX DateAndTime 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "This is the date and time that the LAN-trans lease expired 1044 or will expire." 1045 ::= { cabhCdpLanAddrEntry 5 } 1047 cabhCdpLanAddrMethod OBJECT-TYPE 1048 SYNTAX INTEGER { 1049 reservationInactive(1), 1050 reservationActive(2), 1051 dynamicInactive(3), 1052 dynamicActive(4) 1053 } 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "The IP allocation method indicated by this row. 1058 reservationInactive(1) indicates a reserved IP that has 1059 not yet been leased or that has an expired lease. 1060 reservationActive(2) indicates a reserved IP that has 1061 an active lease. 1062 dynamicInactive(3) indicates an IP that was once 1063 dynamically assigned to a LAN-Trans device but currently 1064 has an expired lease. 1065 dynamicActive(4) indicates an IP that was dynamically 1066 assigned to a LAN-Trans device that has a current lease." 1067 ::= { cabhCdpLanAddrEntry 6 } 1069 cabhCdpLanAddrHostName OBJECT-TYPE 1070 SYNTAX SnmpAdminString(SIZE(0..80)) 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "This is the Host Name of the LAN IP address, based on 1075 DHCP option 12." 1076 ::= { cabhCdpLanAddrEntry 7 } 1078 cabhCdpLanAddrRowStatus OBJECT-TYPE 1079 SYNTAX RowStatus 1080 MAX-ACCESS read-create 1081 STATUS current 1082 DESCRIPTION 1083 "The RowStatus interlock for creation and deletion of 1084 row entries. The PS must not allow the NMS to set 1085 RowStatus to notInService(2). The PS must assign a 1086 RowStatus of notInService(2) to any new row entry 1087 created with a non-unique cabhCdpLanAddrClientID value. 1088 The PS must assign a RowStatus of notReady(3) to any new 1089 row entry created without a cabhCdpLanAddrClientID. The 1090 PS will prevent modification of this table�s columns and 1091 return an inconsistentValue error, if the NMS attempts 1092 to make such modifications while the RowStatus is 1093 active(1)." 1094 ::= { cabhCdpLanAddrEntry 8 } 1096 --============================================================== 1097 -- 1098 -- cabhCdpWanDataAddrTable (CDP WAN-Data Address Table) 1099 -- 1100 -- The cabhCdpWanDataAddrTable contains the configuration or DHCP 1101 -- parameters for each IP address mapping per WAN-Data IP Address. 1102 -- 1103 --============================================================== 1105 cabhCdpWanDataAddrTable OBJECT-TYPE 1106 SYNTAX SEQUENCE OF CabhCdpWanDataAddrEntry 1107 MAX-ACCESS not-accessible 1108 STATUS current 1109 DESCRIPTION 1110 "This table contains WAN-Data address realm information." 1111 ::= { cabhCdpAddr 2 } 1113 cabhCdpWanDataAddrEntry OBJECT-TYPE 1114 SYNTAX CabhCdpWanDataAddrEntry 1115 MAX-ACCESS not-accessible 1116 STATUS current 1117 DESCRIPTION 1118 "List of general parameter for CDP WAN-Data address 1119 realm." 1120 INDEX { cabhCdpWanDataAddrIndex } 1121 ::= { cabhCdpWanDataAddrTable 1 } 1123 CabhCdpWanDataAddrEntry ::= SEQUENCE { 1124 cabhCdpWanDataAddrIndex INTEGER, 1125 cabhCdpWanDataAddrClientId OCTET STRING, 1126 cabhCdpWanDataAddrIpType InetAddressType, 1127 cabhCdpWanDataAddrIp InetAddress, 1128 cabhCdpWanDataAddrRenewalTime Integer32, 1129 cabhCdpWanDataAddrRowStatus RowStatus 1130 } 1132 cabhCdpWanDataAddrIndex OBJECT-TYPE 1133 SYNTAX INTEGER (1..65535) 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION 1137 "Index into table." 1138 ::= { cabhCdpWanDataAddrEntry 1 } 1140 cabhCdpWanDataAddrClientId OBJECT-TYPE 1141 SYNTAX OCTET STRING (SIZE (1..80)) 1142 MAX-ACCESS read-create 1143 STATUS current 1144 DESCRIPTION 1145 "A unique WAN-Data ClientID used when attempting the 1146 acquire a WAN-Data IP Address via DHCP." 1147 ::= { cabhCdpWanDataAddrEntry 2 } 1149 cabhCdpWanDataAddrIpType OBJECT-TYPE 1150 SYNTAX InetAddressType 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "The address type assigned on the WAN-Data side." 1155 DEFVAL { ipv4 } 1156 ::= { cabhCdpWanDataAddrEntry 3 } 1158 cabhCdpWanDataAddrIp OBJECT-TYPE 1159 SYNTAX InetAddress 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "The address assigned on the WAN-Data side." 1164 ::= { cabhCdpWanDataAddrEntry 4 } 1166 cabhCdpWanDataAddrRenewalTime OBJECT-TYPE 1167 SYNTAX Integer32 1168 MAX-ACCESS read-only 1169 STATUS current 1170 DESCRIPTION 1171 "This is the time remaining before the lease expires. 1172 This is based on DHCP Option 51." 1173 ::= { cabhCdpWanDataAddrEntry 5 } 1175 cabhCdpWanDataAddrRowStatus OBJECT-TYPE 1176 SYNTAX RowStatus 1177 MAX-ACCESS read-create 1178 STATUS current 1179 DESCRIPTION 1180 "The RowStatus interlock for creation and deletion of 1181 row entries. Any writable object in a row can be 1182 modified at any time while the row is active(1). The PS 1183 must assign a RowStatus of notInService(2) to any new 1184 row entry created with a cabhCdpWanDataAddrClientId that 1185 is not unique within this table." 1186 ::= { cabhCdpWanDataAddrEntry 6 } 1188 --============================================================== 1189 -- 1190 -- cabhCdpWanDnsServerTable (CDP WAN DNS Server Table) 1191 -- 1192 -- The cabhCdpWanDnsServerTable is a table of 3 cable network 1193 -- and Internet DNS Servers. 1194 -- 1195 --============================================================== 1197 cabhCdpWanDnsServerTable OBJECT-TYPE 1198 SYNTAX SEQUENCE OF CabhCdpWanDnsServerEntry 1199 MAX-ACCESS not-accessible 1200 STATUS current 1201 DESCRIPTION 1202 "This table contains the IP addresses of cable network 1203 and Internet DNS servers, in the order of preference in 1204 which the PS�s CNP will query them, when it cannot 1205 resolve a DNS query using local information. Entries in 1206 this table are updated with the information contained in 1207 DHCP Option 6, received during both the WAN-Man and 1208 WAN-Data IP acquisition processes." 1209 ::= { cabhCdpAddr 3 } 1211 cabhCdpWanDnsServerEntry OBJECT-TYPE 1212 SYNTAX CabhCdpWanDnsServerEntry 1213 MAX-ACCESS not-accessible 1214 STATUS current 1215 DESCRIPTION 1216 "List of cable network and Internet DNS servers." 1217 INDEX { cabhCdpWanDnsServerOrder } 1218 ::= { cabhCdpWanDnsServerTable 1 } 1220 CabhCdpWanDnsServerEntry ::= SEQUENCE { 1221 cabhCdpWanDnsServerOrder INTEGER, 1222 cabhCdpWanDnsServerIpType InetAddressType, 1223 cabhCdpWanDnsServerIp InetAddress 1224 } 1226 cabhCdpWanDnsServerOrder OBJECT-TYPE 1227 SYNTAX INTEGER { 1228 primary(1), 1229 secondary(2), 1230 tertiary(3) 1231 } 1233 MAX-ACCESS not-accessible 1234 STATUS current 1235 DESCRIPTION 1236 "The order of preference for cable network and Internet 1237 DNS servers, as listed in DHCP option 6 (Domain Server). 1238 Any time the CDC receives valid IP address information 1239 within DHCP Option 6, as part of lease acquisition or 1240 renewal of a WAN-Man or WAN-Data IP, it must update this 1241 information into this table. As entries in DHCP Option 6 1242 are listed in order of preference the highest priority 1243 entry in DHCP Option 6 must correspond to the row with a 1244 cabhCdpWanDataAddrDnsOrder equal to 1. If DHCP Option 6 1245 contains 2 valid IP addresses, the PS must update the 1246 rows with cabhCdpWanDataAddrDnsOrder values of 1 and 2. 1247 If DHCP Option 6 contains 3 valid IP addresses, the PS 1248 must update rows with cabhCdpWanDataAddrDnsOrder values 1249 of 1, 2, and 3. Any DNS server information included in 1250 DHCP Option 6 beyond primary, secondary and tertiary 1251 will not be represented in this table." 1252 ::= { cabhCdpWanDnsServerEntry 1 } 1254 cabhCdpWanDnsServerIpType OBJECT-TYPE 1255 SYNTAX InetAddressType 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "This parameter indicates the IP address Type of a WAN 1260 DNS server." 1261 DEFVAL { ipv4 } 1262 ::= { cabhCdpWanDnsServerEntry 2 } 1264 cabhCdpWanDnsServerIp OBJECT-TYPE 1265 SYNTAX InetAddress 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "This parameter indicates the IP address of the WAN DNS 1270 server. The type of this address is specified by 1271 cabhCdpWanDnsServerIpType." 1272 ::= { cabhCdpWanDnsServerEntry 3 } 1274 -- 1275 -- DHCP Server Side (CDS) Option Values for the LAN-Trans realm 1276 -- 1278 cabhCdpLanPoolStartType OBJECT-TYPE 1279 SYNTAX InetAddressType 1280 MAX-ACCESS read-write 1281 STATUS current 1282 DESCRIPTION 1283 "The Address type of the start of range LAN Trans IP 1284 Addresses." 1285 DEFVAL { ipv4 } 1286 ::= { cabhCdpServer 1 } 1288 cabhCdpLanPoolStart OBJECT-TYPE 1289 SYNTAX InetAddress 1290 MAX-ACCESS read-write 1291 STATUS current 1292 DESCRIPTION 1293 "The start of range LAN Trans IP Addresses. The type of 1294 this address is specified by cabhCdpLanPoolStartType." 1295 DEFVAL { 'c0a8000a'h } -- 192.168.0.10 1296 --192.168.0.0 is the network number 1297 -- 192.168.0.255 is broadcast 1298 -- address and 192.168.0.1 1299 -- is reserved for the router 1300 ::= { cabhCdpServer 2 } 1302 cabhCdpLanPoolEndType OBJECT-TYPE 1303 SYNTAX InetAddressType 1304 MAX-ACCESS read-write 1305 STATUS current 1306 DESCRIPTION 1307 "The Address type of the end of range LAN Trans IP 1308 Addresses." 1309 DEFVAL { ipv4 } 1310 ::= { cabhCdpServer 3 } 1312 cabhCdpLanPoolEnd OBJECT-TYPE 1313 SYNTAX InetAddress 1314 MAX-ACCESS read-write 1315 STATUS current 1316 DESCRIPTION 1317 "The end of range for LAN-Trans IP Addresses. The type 1318 of this address is specified by cabhCdpLanPoolEndType." 1319 DEFVAL { 'c0a800fe'h } -- 192.168.0.254 1320 ::= { cabhCdpServer 4 } 1322 cabhCdpServerNetworkNumberType OBJECT-TYPE 1323 SYNTAX InetAddressType 1324 MAX-ACCESS read-write 1325 STATUS current 1326 DESCRIPTION 1327 "The IP address type of the LAN-Trans network number." 1328 DEFVAL { ipv4 } 1329 ::= { cabhCdpServer 5 } 1330 cabhCdpServerNetworkNumber OBJECT-TYPE 1331 SYNTAX InetAddress 1332 MAX-ACCESS read-write 1333 STATUS current 1334 DESCRIPTION 1335 "The LAN-Trans network number. The type of this address 1336 is specified by cabhCdpServerNetworkNumberType." 1337 DEFVAL { 'c0a80000'h } 1338 ::= { cabhCdpServer 6 } 1340 cabhCdpServerSubnetMaskType OBJECT-TYPE 1341 SYNTAX InetAddressType 1342 MAX-ACCESS read-write 1343 STATUS current 1344 DESCRIPTION 1345 "Type of LAN-Trans Subnet Mask." 1346 DEFVAL { ipv4 } 1347 ::= { cabhCdpServer 7 } 1349 cabhCdpServerSubnetMask OBJECT-TYPE 1350 SYNTAX InetAddress 1351 MAX-ACCESS read-write 1352 STATUS current 1353 DESCRIPTION 1354 "Option value 1 - Value of LAN-Trans Subnet Mask." 1355 DEFVAL { 'ffffff00'h } -- 255.255.255.0 1356 ::= { cabhCdpServer 8 } 1358 cabhCdpServerTimeOffset OBJECT-TYPE 1359 SYNTAX Integer32 (-86400..86400) --0 to 24 hours(in seconds) 1360 UNITS "seconds" 1361 MAX-ACCESS read-write 1362 STATUS current 1363 DESCRIPTION 1364 "Option value 2 - Value of LAN-Trans Time Offset from 1365 Coordinated Universal Time (UTC)." 1366 DEFVAL { 0 } -- UTC 1367 ::= { cabhCdpServer 9 } 1369 cabhCdpServerRouterType OBJECT-TYPE 1370 SYNTAX InetAddressType 1371 MAX-ACCESS read-write 1372 STATUS current 1373 DESCRIPTION 1374 "Type of Address, Router for the LAN-Trans address 1375 realm." 1376 DEFVAL { ipv4 } 1377 ::= { cabhCdpServer 10 } 1379 cabhCdpServerRouter OBJECT-TYPE 1380 SYNTAX InetAddress 1381 MAX-ACCESS read-write 1382 STATUS current 1383 DESCRIPTION 1384 "Option value 3 - Router for the LAN-Trans address realm. 1385 The type of this address is specified by 1386 cabhCdpServerRouterType." 1387 DEFVAL { 'c0a80001'h } -- 192.168.0.1 1388 ::= { cabhCdpServer 11 } 1390 cabhCdpServerDnsAddressType OBJECT-TYPE 1391 SYNTAX InetAddressType 1392 MAX-ACCESS read-write 1393 STATUS current 1394 DESCRIPTION 1395 "The Type of IP Addresses of the LAN-Trans address realm 1396 DNS servers." 1397 DEFVAL { ipv4 } 1398 ::= { cabhCdpServer 12 } 1400 cabhCdpServerDnsAddress OBJECT-TYPE 1401 SYNTAX InetAddress 1402 MAX-ACCESS read-write 1403 STATUS current 1404 DESCRIPTION 1405 "The IP Addresses of the LAN-Trans address realm DNS 1406 servers. As a default there is only one DNS server and 1407 it is the address specified in Option Value 3 - 1408 cabhCdpServerRouter. Only one address is specified. The 1409 type of this address is specified by 1410 cabhCdpServerDnsAddressType." 1411 DEFVAL { 'c0a80001'h } -- 192.168.0.1 1412 ::= { cabhCdpServer 13 } 1414 cabhCdpServerSyslogAddressType OBJECT-TYPE 1415 SYNTAX InetAddressType 1416 MAX-ACCESS read-write 1417 STATUS current 1418 DESCRIPTION 1419 "The Type of IP Address of the LAN-Trans SYSLOG servers." 1420 DEFVAL { ipv4 } 1421 ::= { cabhCdpServer 14 } 1423 cabhCdpServerSyslogAddress OBJECT-TYPE 1424 SYNTAX InetAddress 1425 MAX-ACCESS read-write 1426 STATUS current 1427 DESCRIPTION 1428 "The IP Addresses of the LAN-Trans SYSLOG servers. 1429 As a default there are no SYSLOG Servers. The factory 1430 defaults contains the indication of no Syslog Server 1431 value equals (0.0.0.0)." 1432 DEFVAL { '00000000'h } -- 0.0.0.0 1433 ::= { cabhCdpServer 15 } 1435 cabhCdpServerDomainName OBJECT-TYPE 1436 SYNTAX SnmpAdminString(SIZE(0..128)) 1437 MAX-ACCESS read-write 1438 STATUS current 1439 DESCRIPTION 1440 "Option value 15 - Domain name of LAN-Trans address 1441 realm." 1442 DEFVAL {""} 1443 ::= { cabhCdpServer 16 } 1445 cabhCdpServerTTL OBJECT-TYPE 1446 SYNTAX INTEGER (0..255) 1447 MAX-ACCESS read-write 1448 STATUS current 1449 DESCRIPTION 1450 "Option value 23 - LAN-Trans Time to Live." 1451 DEFVAL { 64 } 1452 ::= { cabhCdpServer 17 } 1454 cabhCdpServerInterfaceMTU OBJECT-TYPE 1455 SYNTAX INTEGER (0| 68..4096) 1456 MAX-ACCESS read-write 1457 STATUS current 1458 DESCRIPTION 1459 "Option value 26 - LAN-Trans Interface MTU. if the value 1460 of this object is 0, the PS must not include this option 1461 in its DHCP offer or DHCP Ack messages to LAN IP devices" 1462 DEFVAL { 0 } 1463 ::= { cabhCdpServer 18 } 1465 cabhCdpServerVendorSpecific OBJECT-TYPE 1466 SYNTAX OCTET STRING (SIZE(0..255)) 1467 MAX-ACCESS read-write 1468 STATUS current 1469 DESCRIPTION 1470 "Option value 43 - Vendor Specific Options." 1471 DEFVAL { ''h } 1472 ::= { cabhCdpServer 19 } 1474 cabhCdpServerLeaseTime OBJECT-TYPE 1475 SYNTAX Unsigned32 1476 UNITS "seconds" 1477 MAX-ACCESS read-write 1478 STATUS current 1479 DESCRIPTION 1480 "Option value 51 �Lease Time for LAN IP Devices in the 1481 LAN-Trans realm (seconds)." 1482 DEFVAL { 3600 } 1483 ::= { cabhCdpServer 20 } 1485 cabhCdpServerDhcpAddressType OBJECT-TYPE 1486 SYNTAX InetAddressType 1487 MAX-ACCESS read-write 1488 STATUS current 1489 DESCRIPTION 1490 "Option value 54 - Type of LAN-Trans DHCP server IP 1491 address." 1492 DEFVAL { ipv4 } 1493 ::= { cabhCdpServer 21 } 1495 cabhCdpServerDhcpAddress OBJECT-TYPE 1496 SYNTAX InetAddress 1497 MAX-ACCESS read-write 1498 STATUS current 1499 DESCRIPTION 1500 "Option value 54 - LAN-Trans DHCP server IP address. 1501 It defaults to the router address as specified in 1502 cabhCdpServerRouter. Alternatively a vendor may want to 1503 separate CDS address from router address. The type of 1504 this address is specified by 1505 cabhCdpServerDhcpAddressType." 1506 DEFVAL { 'c0a80001'h } -- 192.168.0.1 1507 ::= { cabhCdpServer 22 } 1509 cabhCdpServerControl OBJECT-TYPE 1510 SYNTAX INTEGER { 1511 restoreConfig(1), 1512 commitConfig(2) 1513 } 1514 MAX-ACCESS read-write 1515 STATUS current 1516 DESCRIPTION 1517 "The control for the CDS (DHCP Server) configuration. 1518 All changes to the cabhCdpServer mib objects are 1519 reflected when reading the value of the mib objects; 1520 however, those changes are NOT applied to the running 1521 configuration of the CDS until they are successfully 1522 committed via use of the cabhCdpServerControl object. 1523 If changes are made to the cabhCdpServer mib objects 1524 which are not yet successfully committed to the CDS, 1525 the cabhCdpServerControl object can be used to rollback 1526 all changes to the last valid CDS configuration and 1527 discard all intermediate changes. 1529 restoreConfig - Setting cabhCdpServerControl to this 1530 value will cause any changes to the 1531 cabhCdpServer objects not yet committed 1532 be reset to the values from the current 1533 running configuration of the CDS. 1534 commitConfig � Setting cabhCdpServerControl to this 1535 value will cause the CDS to validate and 1536 apply the valid cabhCdpServer mib 1537 settings to its running configuration. 1538 The cabhCdpServerCommitStatus object 1539 will detail the status of this 1540 operation." 1541 DEFVAL { restoreConfig } 1542 ::= { cabhCdpServer 23 } 1544 cabhCdpServerCommitStatus OBJECT-TYPE 1545 SYNTAX INTEGER { 1546 commitSucceeded (1), 1547 commitNeeded (2), 1548 commitFailed (3) 1549 } 1550 MAX-ACCESS read-only 1551 STATUS current 1552 DESCRIPTION 1553 "Indicates the status of commiting the current 1554 cabhCdpServer mib object values to the running 1555 configuration of the CDS (DHCP Server). 1557 commitSucceeded - indicates the current cabhCdpServer mib 1558 object values are valid and have been 1559 successfully committed to the running 1560 configuration of the CDS. 1562 commitNeeded - indicates that the value of one or 1563 more objects in cabhCdpServer mib group 1564 have been changed but not yet committed 1565 to the running configuration of the 1566 CDS. 1568 commitFailed � indicates the PS was unable to commit 1569 the cabhCdpServer mib object values to 1570 the running configuration of the CDS 1571 due to conflicts in those values." 1572 DEFVAL { commitSucceeded } 1573 ::= { cabhCdpServer 24 } 1574 -- 1575 -- notification group is for future extension. 1576 -- 1578 cabhCdpNotification OBJECT IDENTIFIER ::= { cabhCdpMib 2 } 1579 cabhCdpNotifications OBJECT IDENTIFIER ::= { cabhCdpNotification 0 } 1580 cabhCdpConformance OBJECT IDENTIFIER ::= { cabhCdpMib 3 } 1581 cabhCdpCompliances OBJECT IDENTIFIER ::= { cabhCdpConformance 1 } 1582 cabhCdpGroups OBJECT IDENTIFIER ::= { cabhCdpConformance 2 } 1584 -- 1585 -- Notification Group 1586 -- 1588 -- compliance statements 1590 cabhCdpBasicCompliance MODULE-COMPLIANCE 1591 STATUS current 1592 DESCRIPTION 1593 "The compliance statement for devices that implement the 1594 CableHome Portal Services functionality." 1595 MODULE --cabhCdpMib 1597 -- unconditionally mandatory groups 1599 MANDATORY-GROUPS { 1600 cabhCdpGroup 1601 } 1603 OBJECT cabhCdpLanAddrIpType 1604 SYNTAX InetAddressType { ipv4(1) } 1605 DESCRIPTION 1606 "An implementation is only required to support IPv4 1607 addresses." 1609 OBJECT cabhCdpLanAddrIp 1610 SYNTAX InetAddress (SIZE(4)) 1611 DESCRIPTION 1612 "An implementation is only required to support IPv4 1613 addresses." 1615 OBJECT cabhCdpWanDataAddrIpType 1616 SYNTAX InetAddressType { ipv4(1) } 1617 DESCRIPTION 1618 "An implementation is only required to support IPv4 1619 addresses." 1621 OBJECT cabhCdpWanDataAddrIp 1622 SYNTAX InetAddress (SIZE(4)) 1623 DESCRIPTION 1624 "An implementation is only required to support IPv4 1625 addresses." 1627 OBJECT cabhCdpWanDnsServerIpType 1628 SYNTAX InetAddressType { ipv4(1) } 1629 DESCRIPTION 1630 "An implementation is only required to support IPv4 1631 addresses." 1633 OBJECT cabhCdpWanDnsServerIp 1634 SYNTAX InetAddress (SIZE(4)) 1635 DESCRIPTION 1636 "An implementation is only required to support IPv4 1637 addresses." 1639 OBJECT cabhCdpLanPoolStartType 1640 SYNTAX InetAddressType { ipv4(1) } 1641 DESCRIPTION 1642 "An implementation is only required to support IPv4 1643 addresses." 1645 OBJECT cabhCdpLanPoolStart 1646 SYNTAX InetAddress (SIZE(4)) 1647 DESCRIPTION 1648 "An implementation is only required to support IPv4 1649 addresses." 1651 OBJECT cabhCdpLanPoolEndType 1652 SYNTAX InetAddressType { ipv4(1) } 1653 DESCRIPTION 1654 "An implementation is only required to support IPv4 1655 addresses." 1657 OBJECT cabhCdpLanPoolEnd 1658 SYNTAX InetAddress (SIZE(4)) 1659 DESCRIPTION 1660 "An implementation is only required to support IPv4 1661 addresses." 1663 OBJECT cabhCdpServerNetworkNumberType 1664 SYNTAX InetAddressType { ipv4(1) } 1665 DESCRIPTION 1666 "An implementation is only required to support IPv4 1667 addresses." 1669 OBJECT cabhCdpServerNetworkNumber 1670 SYNTAX InetAddress (SIZE(4)) 1671 DESCRIPTION 1672 "An implementation is only required to support IPv4 1673 addresses." 1675 OBJECT cabhCdpServerSubnetMaskType 1676 SYNTAX InetAddressType { ipv4(1) } 1677 DESCRIPTION 1678 "An implementation is only required to support IPv4 1679 addresses." 1681 OBJECT cabhCdpServerSubnetMask 1682 SYNTAX InetAddress (SIZE(4)) 1683 DESCRIPTION 1684 "An implementation is only required to support IPv4 1685 addresses." 1687 OBJECT cabhCdpServerRouterType 1688 SYNTAX InetAddressType { ipv4(1) } 1689 DESCRIPTION 1690 "An implementation is only required to support IPv4 1691 addresses." 1693 OBJECT cabhCdpServerRouter 1694 SYNTAX InetAddress (SIZE(4)) 1695 DESCRIPTION 1696 "An implementation is only required to support IPv4 1697 addresses." 1699 OBJECT cabhCdpServerDnsAddressType 1700 SYNTAX InetAddressType { ipv4(1) } 1701 DESCRIPTION 1702 "An implementation is only required to support IPv4 1703 addresses." 1705 OBJECT cabhCdpServerDnsAddress 1706 SYNTAX InetAddress (SIZE(4)) 1707 DESCRIPTION 1708 "An implementation is only required to support IPv4 1709 addresses." 1711 OBJECT cabhCdpServerSyslogAddressType 1712 SYNTAX InetAddressType { ipv4(1) } 1713 DESCRIPTION 1714 "An implementation is only required to support IPv4 1715 addresses." 1717 OBJECT cabhCdpServerSyslogAddress 1718 SYNTAX InetAddress (SIZE(4)) 1719 DESCRIPTION 1720 "An implementation is only required to support IPv4 1721 addresses." 1723 OBJECT cabhCdpServerDhcpAddressType 1724 SYNTAX InetAddressType { ipv4(1) } 1725 DESCRIPTION 1726 "An implementation is only required to support IPv4 1727 addresses." 1729 OBJECT cabhCdpServerDhcpAddress 1730 SYNTAX InetAddress (SIZE(4)) 1731 DESCRIPTION 1732 "An implementation is only required to support IPv4 1733 addresses." 1735 ::= { cabhCdpCompliances 3 } 1737 cabhCdpGroup OBJECT-GROUP 1739 OBJECTS { 1741 cabhCdpSetToFactory, 1742 cabhCdpLanTransCurCount, 1743 cabhCdpLanTransThreshold, 1744 cabhCdpLanTransAction, 1745 cabhCdpWanDataIpAddrCount, 1746 cabhCdpLastSetToFactory, 1748 cabhCdpLanAddrClientID, 1749 cabhCdpLanAddrLeaseCreateTime, 1750 cabhCdpLanAddrLeaseExpireTime, 1751 cabhCdpLanAddrMethod, 1752 cabhCdpLanAddrHostName, 1753 cabhCdpLanAddrRowStatus, 1755 cabhCdpWanDataAddrClientId, 1756 cabhCdpWanDataAddrIpType, 1757 cabhCdpWanDataAddrIp, 1758 cabhCdpWanDataAddrRenewalTime, 1759 cabhCdpWanDataAddrRowStatus, 1761 cabhCdpWanDnsServerIpType, 1762 cabhCdpWanDnsServerIp, 1764 cabhCdpLanPoolStartType, 1765 cabhCdpLanPoolStart, 1766 cabhCdpLanPoolEndType, 1767 cabhCdpLanPoolEnd, 1768 cabhCdpServerNetworkNumberType, 1769 cabhCdpServerNetworkNumber, 1770 cabhCdpServerSubnetMaskType, 1771 cabhCdpServerSubnetMask, 1772 cabhCdpServerTimeOffset, 1774 cabhCdpServerRouterType, 1775 cabhCdpServerRouter, 1777 cabhCdpServerDnsAddressType, 1778 cabhCdpServerDnsAddress, 1779 cabhCdpServerSyslogAddressType, 1780 cabhCdpServerSyslogAddress, 1781 cabhCdpServerDomainName, 1782 cabhCdpServerTTL, 1783 cabhCdpServerInterfaceMTU, 1784 cabhCdpServerVendorSpecific, 1785 cabhCdpServerLeaseTime, 1786 cabhCdpServerDhcpAddressType, 1787 cabhCdpServerDhcpAddress, 1788 cabhCdpServerControl, 1789 cabhCdpServerCommitStatus 1790 } 1791 STATUS current 1792 DESCRIPTION 1793 "Group of objects for CableHome CDP MIB." 1794 ::= { cabhCdpGroups 1 } 1796 END 1798 5. Acknowlegements 1800 Roy Spitzer - Consultant 1801 Mike Mannette - Consultant 1802 Randy Dunton - Intel 1803 Dmitrii Loukianov - Intel 1804 Itay Sherman - Texas Instruments 1805 Chris Zacker - Broadcom 1806 Rick Vetter - Consultant 1807 John Bevilacqua - YAS Broadband Ventures 1809 Funding for the RFC Editor function is currently provided by the 1810 Internet Society. 1812 6. Formal Syntax 1814 The following syntax specification uses the augmented Backus-Naur 1815 Form (BNF) as described in RFC-2234 [3]. 1817 7. Security Considerations 1819 There are a number of management objects defined in this MIB that 1820 have a MAX-ACCESS clause of read-write and/or read-create. Such 1821 objects may be considered sensitive or vulnerable in some network 1822 environments. The support for SET operations in a non-secure 1823 environment without proper protection can have a negative effect on 1824 network operations. 1826 It is thus important to control even GET access to these objects and 1827 possibly to even encrypt the values of these objects when sending 1828 them over the network via SNMP. Not all versions of SNMP provide 1829 features for such a secure environment. 1831 SNMP versions prior to SNMPv3 did not include adequate security. 1832 Even if the network itself is secure (for example by using IPSec), 1833 even then, there is no control as to who on the secure network is 1834 allowed to access and GET/SET (read/change/create/delete) the objects 1835 in this MIB module. 1837 It is RECOMMENDED that implementers consider the security features as 1838 provided by the SNMPv3 framework (see [RFC3410], section 8), 1839 including full support for the SNMPv3 cryptographic mechanisms (for 1840 authentication and privacy). 1842 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1843 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1844 enable cryptographic security. It is then a customer/operator 1845 responsibility to ensure that the SNMP entity giving access to an 1846 instance of this MIB module, is properly configured to give access to 1847 the objects only to those principals (users) that have legitimate 1848 rights to indeed GET or SET (change/create/delete) them. 1850 8. Normative References 1852 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 1853 9, RFC 2026, October 1996. 1855 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement 1856 Levels", BCP 14, RFC 2119, March 1997 1858 3 Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax 1859 Specifications: ABNF", RFC 2234, Internet Mail Consortium and 1860 Demon Internet Ltd., November 1997 1862 4 Rose, M. and K. McCloghrie, "Structure and Identification of 1863 Management Information for TCP/IP-based Internets", STD 16, RFC 1864 1155, May 1990. 1866 5 Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1867 1212, March 1991. 1869 6 Rose, M., "A Convention for Defining Traps for use with the SNMP", 1870 RFC 1215, March 1991. 1872 7 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of 1873 Management Information for Version 2 (SMIv2)", STD 58, RFC 2578, 1874 April 1999. 1876 8 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual 1877 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 1879 9 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance 1880 Statements for SMIv2", STD 58, RFC 2580, April 1999. 1882 10 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 1883 Management Protocol", STD 15, RFC 1157, May 1990. 1885 11 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1886 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1888 12 Case, J., Mundy, R., Partain, D, and B. Stewart, "Introduction and 1889 Applicability Statements for Internet Standard Management 1890 Framework", RFC 3410, December 2002. 1892 13 Harrington D., Presuhn R. and B. Wijnen, "An Architecture for 1893 Describing Simple Network Management Protocol (SNMP) Management 1894 Frameworks", RFC 3411, December 2002. 1896 14 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1897 Processing and Dispatching for the Simple Network Management 1898 Protocol (SNMP)", RFC 3412, December 2002. 1900 15 Levi, D., Meyer, P., and B. Stewart, �Simple Network Management 1901 Protocol (SNMP) Applications", RFC 3413, December 2002. 1903 16 Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for 1904 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1905 3414, December 2002. 1907 17 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 1908 Control Model (VACM) for the Simple Network Management Protocol 1909 (SNMP)", RFC 3415, December 2002. 1911 18 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1912 "Version 2 of the Protocol Operations for the Simple Network 1913 Management Protocol (SNMPv2)", RFC 3416, Decemeber 2002. 1915 19 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1916 "Transport Mappings for the Simple Network Management Protocol 1917 (SNMPv2)", RFC 3417, December 2002. 1919 20 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1920 "Management Information Base (MIB) for the Simple Network 1921 Management Protocol (SNMP)", RFC 3418, December 2002. 1923 21 Cable Television Laboratories, �CableHome 1.0 Specification�, CH- 1924 SP-I02-020920, September 2002, 1925 http://www.cablelabs.com/projects/cablehome/specifications. 1927 9. Informative References 1929 22 Drums, R., �Dynamic Host Configuration Protocol�, RFC 2131, March 1930 1997. 1932 23 Alesander, S. and R. Droms, �DHCP Options and Bootp Vendor 1933 Extensions�, RFC 2132, March 1997. 1935 24 Klensin, J., �Role of the Domain Name System (DNS)�, RFC 3467, 1936 February 2003. 1938 25 Harrington, R., Presuhn, R., and B. Wijnen, �An Architecture for 1939 Describing SNMP Management Frameworks�, RFC 2571, April 1999. 1941 26 Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, 1942 �Textual Contentions for Internet Network Addresses�, May 2002. 1944 10. Intellectual Property 1946 The IETF takes no position regarding the validity or scope of any 1947 intellectual property or other rights that might be claimed to 1948 pertain to the implementation or use of the technology described in 1949 this document or the extent to which any license under such rights 1950 might or might not be available; neither does it represent that it 1951 has made any effort to identify any such rights. Information on the 1952 IETF's procedures with respect to rights in standards-track and 1953 standards-related documentation can be found in BCP-11. Copies of 1954 claims of rights made available for publication and any assurances of 1955 licenses to be made available, or the result of an attempt made to 1956 obtain a general license or permission for the use of such 1957 proprietary rights by implementers or users of this specification can 1958 be obtained from the IETF Secretariat. 1960 The IETF invites any interested party to bring to its attention any 1961 copyrights, patents or patent applications, or other proprietary 1962 rights which may cover technology that may be required to practice 1963 this standard. Please address the information to the IETF Executive 1964 Director. 1966 11. Author's Addresses 1968 Eduardo Cardona 1969 Cable Television Laboratories 1970 400 Centennial Parkway 1971 Louisville, CO 80027 1972 Phone: +1 303.661.9100 1973 Email: e.cardona@cablelabs.com 1975 Kevin Luehrs 1976 Cable Television Laboratories 1977 Louisville, CO 80027 1978 Phone: +1 303.661.9100 1979 Email: k.luehrs@cablelabs.com 1981 Diego Mazzola 1982 Texas Instruments 1983 12500 TI Blvd MS 8669 1984 Dallas, TX 75243 1985 Phone: +1 303.661.3310 1986 Email: d-mazzola1@ti.com 1987 Doug Jones 1988 YAS Broadband Ventures 1989 300 Brickstone Square 1990 Andover, MA 01810 1991 Phone: +1 303.661.3823 1992 Email: doug@yas.com 1994 12. Full Copyright Statement 1996 Copyright (C) The Internet Society (2003). All Rights Reserved. 1998 This document and translations of it may be copied and furnished to 1999 others, and derivative works that comment on or otherwise explain it 2000 or assist in its implementation may be prepared, copied, published 2001 and distributed, in whole or in part, without restriction of any 2002 kind, provided that the above copyright notice and this paragraph are 2003 included on all such copies and derivative works. However, this 2004 document itself may not be modified in any way, such as by removing 2005 the copyright notice or references to the Internet Society or other 2006 Internet organizations, except as needed for the purpose of 2007 developing Internet standards in which case the procedures for 2008 copyrights defined in the Internet Standards process must be 2009 followed, or as required to translate it into languages other than 2010 English. 2012 The limited permissions granted above are perpetual and will not be 2013 revoked by the Internet Society or its successors or assigns. 2015 This document and the information contained herein is provided on an 2016 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2017 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2018 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2019 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2020 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."