idnits 2.17.1 draft-ietf-ipcdn-cable-gateway-tools-mib-00.txt: -(841): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(847): 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 7 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 ([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 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 435 has weird spacing: '...ress is speci...' == 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 7622 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 20 looks like a reference -- Missing reference section? '5' on line 52 looks like a reference -- Missing reference section? '6' on line 52 looks like a reference -- Missing reference section? '7' on line 96 looks like a reference -- Missing reference section? '2' on line 60 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? '21' on line 160 looks like a reference -- Missing reference section? '22' on line 111 looks like a reference -- Missing reference section? '23' on line 112 looks like a reference -- Missing reference section? '3' on line 733 looks like a reference -- Missing reference section? 'RFC3410' on line 756 looks like a reference Summary: 3 errors (**), 0 flaws (~~), 6 warnings (==), 15 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-tools-mib-00.txt K. Luehrs 4 Expires: December 2003 CableLabs 6 D. Mah 7 Linksys 9 D. Jones 10 YAS BBV 11 June 2003 13 Cable Gateway Tools 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 CableHome compliant WAN Gateway Devices and home 47 routers. Specifically, this MIB defines managed objects for both a 48 connection speed tool and an ICMP "ping" tool between the Gateway and 49 devices on the LAN. 51 This memo specifies a MIB module in a manner that is compliant to the 52 SNMP SMIv2 [5][6][7]. The set of objects is consistent with the SNMP 53 framework and existing SNMP standards. 55 Conventions used in this document 57 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 58 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 59 document are to be interpreted as described in RFC-2119 [2]. 61 Table of Contents 63 1. The Internet-Standard Management Framework.....................2 64 2. Glossary.......................................................3 65 2.1 CableHome Residential Gateway..............................3 66 2.2 Portal Services............................................3 67 2.3 LAN IP Device..............................................3 68 2.4 WAN Management (WAN-Man) Address...........................3 69 2.5 WAN Data (WAN-Data) Address................................3 70 2.6 LAN Translated (LAN-Trans) Address.........................4 71 2.7 LAN Passthrough (LAN-Pass) Address.........................4 72 3. Overview.......................................................4 73 3.1 Structure of the MIB.......................................4 74 4. MIB Definitions................................................4 75 5. Acknowledgements..............................................16 76 6. Formal Syntax.................................................16 77 7. Security Considerations.......................................16 78 8. Normative References..........................................17 79 9. Informative References........................................18 80 10. Intellectual Property........................................19 81 11. Author's Addresses...........................................19 82 12. Full Copyright Statement.....................................20 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 TFTP 112 server (RFC1350) [23], 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 144 LAN Translated Addresses are intended for subscriber application and 145 management traffic on the home network between LAN IP Devices and the 146 PS element. Typically, these addresses will reside in private IP 147 address space, and can typically be reused across subscribers. 149 2.7 LAN Passthrough (LAN-Pass) Address 151 LAN Passthrough Addresses are intended for subscriber application 152 traffic, such as traffic between LAN IP Devices and Internet hosts, 153 on the home network, the cable network, and beyond. Typically, these 154 addresses will reside in public IP address space. 156 3. Overview 158 This MIB provides a set of security objects required for the 159 management of CableHome compliant residential gateway devices. The 160 specification is derived from the CableHome 1.0 specification [21]. 162 3.1 Structure of the MIB 164 This MIB is structured into two groups: 166 The cabhCtpConnSpeed group contains objects needed to test the 167 connection speed between the Gateway and a LAN device. 169 The cabhCtpPing Group provides objects allowing the manager to send 170 an ICMP ping from the Gateway to a LAN device. 172 4. MIB Definitions 174 CABH-IETF-CTP-MIB DEFINITIONS ::= BEGIN 176 IMPORTS 177 MODULE-IDENTITY, 178 OBJECT-TYPE, 179 mib-2 FROM SNMPv2-SMI 181 TimeStamp, 182 TruthValue FROM SNMPv2-TC 184 OBJECT-GROUP, 185 MODULE-COMPLIANCE FROM SNMPv2-CONF 187 InetAddressType, 188 InetAddress FROM INET-ADDRESS-MIB; 190 cabhCtpMib MODULE-IDENTITY 191 LAST-UPDATED "200306210000Z" -- Jun 21, 2003 192 ORGANIZATION "IETF IPCDN Working Group" 193 CONTACT-INFO 194 "Kevin Luehrs 195 Postal: Cable Television Laboratories, Inc. 196 400 Centennial Parkway 197 Louisville, Colorado 80027-1266 198 U.S.A. 199 Phone: +1 303-661-9100 200 Fax: +1 303-661-9199 201 E-mail: k.luehrs@cablelabs.com; mibs@cablelabs.com 203 IETF IPCDN Working Group 204 General Discussion: ipcdn@ietf.org 205 Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn 206 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 207 Co-chairs: Richard Woundy, 208 Richard_Woundy@cable.comcast.com 209 Jean-Francois Mule, jf.mule@cablelabs.com" 210 DESCRIPTION 211 "This MIB module defines the diagnostic controls offered 212 by the CableHome Test Portal (CTP). 214 Copyright (C) The Internet Society (2003). This version 215 of this MIB module is part of RFC xxxx; see the RFC 216 itself for full legal notices." 217 REVISION "200306210000Z" -- Jun 21, 2003 218 DESCRIPTION 219 "Initial version, published as RFC xxxx." 220 -- RFC editor to assign xxxx 221 ::= { mib-2 xx } 222 -- xx to be assigned by IANA 224 -- Textual conventions 226 cabhCtpObjects OBJECT IDENTIFIER ::= { cabhCtpMib 1 } 227 cabhCtpBase OBJECT IDENTIFIER ::= { cabhCtpObjects 1 } 228 cabhCtpConnSpeed OBJECT IDENTIFIER ::= { cabhCtpObjects 2 } 229 cabhCtpPing OBJECT IDENTIFIER ::= { cabhCtpObjects 3 } 231 -- 232 -- The following group describes the base objects in the CableHome 233 -- Management Portal. 234 -- 235 cabhCtpSetToFactory OBJECT-TYPE 236 SYNTAX TruthValue 237 MAX-ACCESS read-write 238 STATUS current 239 DESCRIPTION 240 "Setting this object to true(1) causes all the tables in 241 the CTP MIB to be cleared, and all CTP MIB objects with 242 default values set back to those default values. 243 Reading this object always returns false(2)." 244 ::={cabhCtpBase 1} 246 cabhCtpLastSetToFactory OBJECT-TYPE 247 SYNTAX TimeStamp 248 MAX-ACCESS read-only 249 STATUS current 250 DESCRIPTION 251 "The value of sysUpTime when cabhCtpSetToFactory was 252 last set to true. Zero if never reset." 253 ::={cabhCtpBase 2} 255 -- 256 -- Parameter and results from Connection Speed Command 257 -- 259 cabhCtpConnSrcIpType OBJECT-TYPE 260 SYNTAX InetAddressType 261 MAX-ACCESS read-write 262 STATUS current 263 DESCRIPTION 264 "The IP Address type used as the source address for the 265 Connection Speed Test." 266 DEFVAL { ipv4 } 267 ::= { cabhCtpConnSpeed 1 } 269 cabhCtpConnSrcIp OBJECT-TYPE 270 SYNTAX InetAddress 271 MAX-ACCESS read-write 272 STATUS current 273 DESCRIPTION 274 "The IP Address used as the source address for the 275 Connection Speed Test. The type of this address is 276 specified by cabhCtpConnSrcIpType. The default value is 277 the value of cabhCdpServerRouter (192.168.0.1)." 278 REFERENCE 279 "CableHome Specification Section 6.4.4" 280 DEFVAL { 'c0a80001'h } -- 192.168.0.1 281 ::= { cabhCtpConnSpeed 2 } 283 cabhCtpConnDestIpType OBJECT-TYPE 284 SYNTAX InetAddressType 285 MAX-ACCESS read-write 286 STATUS current 287 DESCRIPTION 288 "The IP Address Type for the CTP Connection Speed Tool 289 destination address. " 290 DEFVAL { ipv4 } 291 ::={ cabhCtpConnSpeed 3 } 293 cabhCtpConnDestIp OBJECT-TYPE 294 SYNTAX InetAddress 295 MAX-ACCESS read-write 296 STATUS current 297 DESCRIPTION 298 "The IP Address used as the destination address for the 299 Connection Speed Test. The type of this address is 300 specified by cabhCtpConnDestIpType" 301 ::= { cabhCtpConnSpeed 4 } 303 cabhCtpConnProto OBJECT-TYPE 304 SYNTAX INTEGER { 305 udp(1), 306 tcp(2) 307 } 308 MAX-ACCESS read-write 309 STATUS current 310 DESCRIPTION 311 "The protocol used in the Connection Speed Test. 312 TCP testing is optional." 313 DEFVAL { udp } 314 ::= { cabhCtpConnSpeed 5 } 316 cabhCtpConnNumPkts OBJECT-TYPE 317 SYNTAX INTEGER (1..65535) 318 MAX-ACCESS read-write 319 STATUS current 320 DESCRIPTION 321 "The number of packets the CTP is to send when triggered 322 to execute the Connection Speed Tool." 323 DEFVAL { 100 } 324 ::= { cabhCtpConnSpeed 6 } 326 cabhCtpConnPktSize OBJECT-TYPE 327 SYNTAX INTEGER (64..1518) 328 MAX-ACCESS read-write 329 STATUS current 330 DESCRIPTION 331 "The size of the test frames." 332 REFERENCE 333 "" 334 DEFVAL { 1518 } 335 ::= { cabhCtpConnSpeed 7 } 337 cabhCtpConnTimeOut OBJECT-TYPE 338 SYNTAX INTEGER (0..600000) -- Max 10 minutes 339 UNITS "milliseconds" 340 MAX-ACCESS read-write 341 STATUS current 342 DESCRIPTION 343 "The timeout value for the response. A value of zero 344 indicates no time out and can be used for TCP only." 345 DEFVAL {30000} -- 30 seconds 346 ::= { cabhCtpConnSpeed 8 } 348 cabhCtpConnControl OBJECT-TYPE 349 SYNTAX INTEGER { 350 start(1), 351 abort(2) 352 } 353 MAX-ACCESS read-write 354 STATUS current 355 DESCRIPTION 356 "The control for the Connection Speed Tool. Setting this 357 object to start(1) causes the Connection Speed Tool to 358 execute. Setting this object to abort(2) causes the 359 Connection Speed Tool to stop running. 360 This parameter should only be set via SNMP." 361 DEFVAL {abort } 362 ::={ cabhCtpConnSpeed 9 } 364 cabhCtpConnStatus OBJECT-TYPE 365 SYNTAX INTEGER { 366 notRun(1), 367 running(2), 368 complete(3), 369 aborted(4), 370 timedOut(5) 371 } 372 MAX-ACCESS read-only 373 STATUS current 374 DESCRIPTION 375 "The status of the Connection Speed Tool." 376 DEFVAL { notRun } 377 ::={ cabhCtpConnSpeed 10 } 379 cabhCtpConnPktsSent OBJECT-TYPE 380 SYNTAX INTEGER (0..65535) 381 MAX-ACCESS read-only 382 STATUS current 383 DESCRIPTION 384 "The number of packets the CTP sent after it was 385 triggered to execute the Connection Speed Tool." 386 ::= { cabhCtpConnSpeed 11 } 388 cabhCtpConnPktsRecv OBJECT-TYPE 389 SYNTAX INTEGER (0..65535) 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The number of packets the CTP received after it 394 executed the Connection Speed Tool." 395 ::= { cabhCtpConnSpeed 12 } 397 cabhCtpConnRTT OBJECT-TYPE 398 SYNTAX INTEGER (0..600000) 399 UNITS "millisec" 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The resulting round trip time for the set of packets 404 sent to and received from the target LAN IP Device." 405 ::= { cabhCtpConnSpeed 13 } 407 cabhCtpConnThroughput OBJECT-TYPE 408 SYNTAX INTEGER (0..65535) 409 MAX-ACCESS read-only 410 STATUS current 411 DESCRIPTION 412 "The average round-trip throughput measured in kilobits 413 per second." 414 ::= { cabhCtpConnSpeed 14 } 416 -- 417 -- Parameters and Results for Ping Command 418 -- 420 cabhCtpPingSrcIpType OBJECT-TYPE 421 SYNTAX InetAddressType 422 MAX-ACCESS read-write 423 STATUS current 424 DESCRIPTION 425 "The IP Address Type for CTP Ping Tool source address." 426 DEFVAL { ipv4 } 427 ::={ cabhCtpPing 1 } 429 cabhCtpPingSrcIp OBJECT-TYPE 430 SYNTAX InetAddress 431 MAX-ACCESS read-write 432 STATUS current 433 DESCRIPTION 434 "The IP Address used as the source address for the Ping 435 Test. The type of this address is specified by 436 cabhCtpPingSrcIpType. The default value is the value of 437 CabhCdpServerRouter (192.168.0.1)." 438 REFERENCE 439 "CableHome 1.0 Specification Section 6.4.4" 440 DEFVAL { 'c0a80001'h } 441 ::= { cabhCtpPing 2 } 443 cabhCtpPingDestIpType OBJECT-TYPE 444 SYNTAX InetAddressType 445 MAX-ACCESS read-write 446 STATUS current 447 DESCRIPTION 448 "The IP Address Type for the CTP Ping Tool destination 449 address." 450 DEFVAL { ipv4 } 451 ::={ cabhCtpPing 3 } 453 cabhCtpPingDestIp OBJECT-TYPE 454 SYNTAX InetAddress 455 MAX-ACCESS read-write 456 STATUS current 457 DESCRIPTION 458 "The Destination IP Address used as the destination 459 address for the Ping Test." 460 ::= { cabhCtpPing 4 } 462 cabhCtpPingNumPkts OBJECT-TYPE 463 SYNTAX INTEGER (1..4) 464 MAX-ACCESS read-write 465 STATUS current 466 DESCRIPTION 467 "The number of packets to send to each host." 468 DEFVAL {1} 469 ::= { cabhCtpPing 5 } 471 cabhCtpPingPktSize OBJECT-TYPE 472 SYNTAX INTEGER (64..1518) 473 MAX-ACCESS read-write 474 STATUS current 475 DESCRIPTION 476 "The size of the test frames." 477 DEFVAL {64} 478 ::= { cabhCtpPing 6 } 480 cabhCtpPingTimeBetween OBJECT-TYPE 481 SYNTAX INTEGER (0..600000) 482 UNITS "milliseconds" 483 MAX-ACCESS read-write 484 STATUS current 485 DESCRIPTION 486 "The time between sending one ping and the next." 487 DEFVAL { 1000 } 488 ::= { cabhCtpPing 7 } 490 cabhCtpPingTimeOut OBJECT-TYPE 491 SYNTAX INTEGER (1..600000) 492 UNITS "milliseconds" 493 MAX-ACCESS read-write 494 STATUS current 495 DESCRIPTION 496 "The time out for ping response (ICMP reply) for a 497 single transmitted ping message (ICMP request)." 498 DEFVAL { 1000 } -- 1 second 499 ::={ cabhCtpPing 8 } 501 cabhCtpPingControl OBJECT-TYPE 502 SYNTAX INTEGER { 503 start(1), 504 abort(2) 505 } 506 MAX-ACCESS read-write 507 STATUS current 508 DESCRIPTION 509 "The control for the Ping Tool. Setting this object to 510 start(1) causes the Ping Tool to execute. Setting this 511 object to abort(2) causes the Ping Tool to stop running. 512 This parameter should only be set via SNMP." 513 DEFVAL {abort } 514 ::={ cabhCtpPing 9 } 516 cabhCtpPingStatus OBJECT-TYPE 517 SYNTAX INTEGER { 518 notRun(1), 519 running(2), 520 complete(3), 521 aborted(4), 522 timedOut(5) 523 } 524 MAX-ACCESS read-only 525 STATUS current 526 DESCRIPTION 527 "The status of the Ping Tool." 528 DEFVAL { notRun } 529 ::={ cabhCtpPing 10 } 531 cabhCtpPingNumSent OBJECT-TYPE 532 SYNTAX INTEGER (0..4) 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "The number of Pings sent" 537 ::={ cabhCtpPing 11 } 539 cabhCtpPingNumRecv OBJECT-TYPE 540 SYNTAX INTEGER (0..255) 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "The number of pings received." 545 ::= { cabhCtpPing 12 } 547 cabhCtpPingAvgRTT OBJECT-TYPE 548 SYNTAX INTEGER (0..600000) 549 UNITS "millisec" 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The resulting average of round trip times for 554 acknowledged packets." 555 ::= { cabhCtpPing 13 } 557 cabhCtpPingMaxRTT OBJECT-TYPE 558 SYNTAX INTEGER (0..600000) 559 UNITS "millisec" 560 MAX-ACCESS read-only 561 STATUS current 562 DESCRIPTION 563 "The resulting maximum of round trip times for 564 acknowledged packets." 565 ::= { cabhCtpPing 14 } 567 cabhCtpPingMinRTT OBJECT-TYPE 568 SYNTAX INTEGER (0..600000) 569 UNITS "millisec" 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "The resulting minimum of round trip times for 574 acknowledged packets." 575 ::= { cabhCtpPing 15 } 577 cabhCtpPingNumIcmpError OBJECT-TYPE 578 SYNTAX INTEGER (0..255) 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "Number of ICMP errors." 583 ::= { cabhCtpPing 16 } 585 cabhCtpPingIcmpError OBJECT-TYPE 586 SYNTAX INTEGER (0..255) 587 MAX-ACCESS read-only 588 STATUS current 589 DESCRIPTION 590 "The last ICMP error." 591 ::= { cabhCtpPing 17 } 593 --============================================================== 595 -- 596 -- notification group is for future extension. 597 -- 599 cabhCtpNotification OBJECT IDENTIFIER ::= { cabhCtpMib 2 } 600 cabhCtpNotifications OBJECT IDENTIFIER ::= { cabhCtpNotification 0 } 601 cabhCtpConformance OBJECT IDENTIFIER ::= { cabhCtpMib 3 } 602 cabhCtpCompliances OBJECT IDENTIFIER ::= { cabhCtpConformance 1 } 603 cabhCtpGroups OBJECT IDENTIFIER ::= { cabhCtpConformance 2 } 605 -- 606 -- Notification Group 607 -- 608 -- 609 -- compliance statements 611 cabhCtpBasicCompliance MODULE-COMPLIANCE 612 STATUS current 613 DESCRIPTION 614 "The compliance statement for devices that implement 615 Portal Service feature." 616 MODULE --cabhCtpMib 618 -- unconditionally mandatory groups 620 MANDATORY-GROUPS { 621 cabhCtpGroup 622 } 624 OBJECT cabhCtpConnSrcIpType 625 SYNTAX InetAddressType { ipv4(1) } 626 DESCRIPTION 627 "An implementation is only required to support IPv4 628 addresses." 630 OBJECT cabhCtpConnSrcIp 631 SYNTAX InetAddress (SIZE(4)) 632 DESCRIPTION 633 "An implementation is only required to support IPv4 634 addresses." 636 OBJECT cabhCtpConnDestIpType 637 SYNTAX InetAddressType { ipv4(1) } 638 DESCRIPTION 639 "An implementation is only required to support IPv4 640 addresses." 642 OBJECT cabhCtpConnDestIp 643 SYNTAX InetAddress (SIZE(4)) 644 DESCRIPTION 645 "An implementation is only required to support IPv4 646 addresses." 648 OBJECT cabhCtpPingSrcIpType 649 SYNTAX InetAddressType { ipv4(1) } 650 DESCRIPTION 651 "An implementation is only required to support IPv4 652 addresses." 654 OBJECT cabhCtpPingSrcIp 655 SYNTAX InetAddress (SIZE(4)) 656 DESCRIPTION 657 "An implementation is only required to support IPv4 658 addresses." 660 OBJECT cabhCtpPingDestIpType 661 SYNTAX InetAddressType { ipv4(1) } 662 DESCRIPTION 663 "An implementation is only required to support IPv4 664 addresses." 666 OBJECT cabhCtpPingDestIp 667 SYNTAX InetAddress (SIZE(4)) 668 DESCRIPTION 669 "An implementation is only required to support IPv4 670 addresses." 672 ::= { cabhCtpCompliances 3 } 674 cabhCtpGroup OBJECT-GROUP 675 OBJECTS { 677 cabhCtpSetToFactory, 678 cabhCtpLastSetToFactory, 679 cabhCtpConnSrcIpType, 680 cabhCtpConnSrcIp, 681 cabhCtpConnDestIpType, 682 cabhCtpConnDestIp, 683 cabhCtpConnProto, 684 cabhCtpConnNumPkts, 685 cabhCtpConnPktSize, 686 cabhCtpConnTimeOut, 687 cabhCtpConnControl, 688 cabhCtpConnStatus, 689 cabhCtpConnPktsSent, 690 cabhCtpConnPktsRecv, 691 cabhCtpConnRTT, 692 cabhCtpConnThroughput, 694 cabhCtpPingSrcIpType, 695 cabhCtpPingSrcIp, 696 cabhCtpPingDestIpType, 697 cabhCtpPingDestIp, 698 cabhCtpPingNumPkts, 699 cabhCtpPingPktSize, 700 cabhCtpPingTimeBetween, 701 cabhCtpPingTimeOut, 702 cabhCtpPingControl, 703 cabhCtpPingStatus, 704 cabhCtpPingNumSent, 705 cabhCtpPingNumRecv, 706 cabhCtpPingAvgRTT, 707 cabhCtpPingMinRTT, 708 cabhCtpPingMaxRTT, 709 cabhCtpPingNumIcmpError, 710 cabhCtpPingIcmpError 711 } 712 STATUS current 713 DESCRIPTION 714 "Group of objects for CableHome CTP MIB." 715 ::= { cabhCtpGroups 1 } 716 END 718 5. Acknowledgements 720 Roy Spitzer - Consultant 721 Mike Mannette - Consultant 722 Randy Dunton - Intel 723 Dmitrii Loukianov - Intel 724 Wes Peters - DoBox 725 Chris Zacker - Broadcom 727 Funding for the RFC Editor function is currently provided by the 728 Internet Society. 730 6. Formal Syntax 732 The following syntax specification uses the augmented Backus-Naur 733 Form (BNF) as described in RFC-2234 [3]. 735 7. Security Considerations 737 There are a number of management objects defined in this MIB that 738 have a MAX-ACCESS clause of read-write and/or read-create. Such 739 objects may be considered sensitive or vulnerable in some network 740 environments. The support for SET operations in a non-secure 741 environment without proper protection can have a negative effect on 742 network operations. 744 It is thus important to control even GET access to these objects and 745 possibly to even encrypt the values of these objects when sending 746 them over the network via SNMP. Not all versions of SNMP provide 747 features for such a secure environment. 749 SNMP versions prior to SNMPv3 did not include adequate security. 750 Even if the network itself is secure (for example by using IPSec), 751 even then, there is no control as to who on the secure network is 752 allowed to access and GET/SET (read/change/create/delete) the objects 753 in this MIB module. 755 It is RECOMMENDED that implementers consider the security features as 756 provided by the SNMPv3 framework (see [RFC3410], section 8), 757 including full support for the SNMPv3 cryptographic mechanisms (for 758 authentication and privacy). 760 Further, deployment of SNMP versions prior to SNMPv3 is NOT 761 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 762 enable cryptographic security. It is then a customer/operator 763 responsibility to ensure that the SNMP entity giving access to an 764 instance of this MIB module, is properly configured to give access to 765 the objects only to those principals (users) that have legitimate 766 rights to indeed GET or SET (change/create/delete) them. 768 8. Normative References 770 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 771 9, RFC 2026, October 1996. 773 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement 774 Levels", BCP 14, RFC 2119, March 1997 776 3 Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax 777 Specifications: ABNF", RFC 2234, Internet Mail Consortium and 778 Demon Internet Ltd., November 1997 780 4 Rose, M. and K. McCloghrie, "Structure and Identification of 781 Management Information for TCP/IP-based Internets", STD 16, RFC 782 1155, May 1990. 784 5 Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 785 1212, March 1991. 787 6 Rose, M., "A Convention for Defining Traps for use with the SNMP", 788 RFC 1215, March 1991. 790 7 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of 791 Management Information for Version 2 (SMIv2)", STD 58, RFC 2578, 792 April 1999. 794 8 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual 795 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 797 9 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance 798 Statements for SMIv2", STD 58, RFC 2580, April 1999. 800 10 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 801 Management Protocol", STD 15, RFC 1157, May 1990. 803 11 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 804 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 806 12 Case, J., Mundy, R., Partain, D, and B. Stewart, "Introduction and 807 Applicability Statements for Internet Standard Management 808 Framework", RFC 3410, December 2002. 810 13 Harrington D., Presuhn R. and B. Wijnen, "An Architecture for 811 Describing Simple Network Management Protocol (SNMP) Management 812 Frameworks", RFC 3411, December 2002. 814 14 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 815 Processing and Dispatching for the Simple Network Management 816 Protocol (SNMP)", RFC 3412, December 2002. 818 15 Levi, D., Meyer, P., and B. Stewart, �Simple Network Management 819 Protocol (SNMP) Applications", RFC 3413, December 2002. 821 16 Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for 822 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 823 3414, December 2002. 825 17 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 826 Control Model (VACM) for the Simple Network Management Protocol 827 (SNMP)", RFC 3415, December 2002. 829 18 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 830 "Version 2 of the Protocol Operations for the Simple Network 831 Management Protocol (SNMPv2)", RFC 3416, Decemeber 2002. 833 19 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 834 "Transport Mappings for the Simple Network Management Protocol 835 (SNMPv2)", RFC 3417, December 2002. 837 20 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 838 "Management Information Base (MIB) for the Simple Network 839 Management Protocol (SNMP)", RFC 3418, December 2002. 841 21 Cable Television Laboratories, �CableHome 1.0 Specification�, CH- 842 SP-I02-020920, September 2002, 843 http://www.cablelabs.com/projects/cablehome/specifications. 845 9. Informative References 847 22 Drums, R., �Dynamic Host Configuration Protocol�, RFC 2131, March 848 1997. 850 23 Sollins, K., �The TFTP Protocol (Revision 2)�, RFC 1350, July 851 1992. 853 24 Harrington, R., Presuhn, R., and B. Wijnen, �An Architecture for 854 Describing SNMP Management Frameworks�, RFC 2571, April 1999. 856 25 Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, 857 �Textual Contentions for Internet Network Addresses�, May 2002. 859 10. Intellectual Property 861 The IETF takes no position regarding the validity or scope of any 862 intellectual property or other rights that might be claimed to 863 pertain to the implementation or use of the technology described in 864 this document or the extent to which any license under such rights 865 might or might not be available; neither does it represent that it 866 has made any effort to identify any such rights. Information on the 867 IETF's procedures with respect to rights in standards-track and 868 standards-related documentation can be found in BCP-11. Copies of 869 claims of rights made available for publication and any assurances of 870 licenses to be made available, or the result of an attempt made to 871 obtain a general license or permission for the use of such 872 proprietary rights by implementers or users of this specification can 873 be obtained from the IETF Secretariat. 875 The IETF invites any interested party to bring to its attention any 876 copyrights, patents or patent applications, or other proprietary 877 rights which may cover technology that may be required to practice 878 this standard. Please address the information to the IETF Executive 879 Director. 881 11. Author's Addresses 883 Eduardo Cardona 884 Cable Television Laboratories 885 400 Centennial Parkway 886 Louisville, CO 80027 887 Phone: +1 303.661.9100 888 Email: e.cardona@cablelabs.com 890 Kevin Luehrs 891 Cable Television Laboratories 892 400 Centennial Parkway 893 Louisville, CO 80027 894 Phone: +1 303.661.9100 895 Email: k.luehrs@cablelabs.com 897 Donald Mah 898 Linksys 899 Phone: +1 949.784.1833 900 Email: donald.mah@linksys.com 901 Doug Jones 902 YAS Broadband Ventures 903 300 Brickstone Square 904 Andover, MA 01810 905 Phone: +1 303.661.3823 906 Email: doug@yas.com 908 12. Full Copyright Statement 910 Copyright (C) The Internet Society (2003). All Rights Reserved. 912 This document and translations of it may be copied and furnished to 913 others, and derivative works that comment on or otherwise explain it 914 or assist in its implementation may be prepared, copied, published 915 and distributed, in whole or in part, without restriction of any 916 kind, provided that the above copyright notice and this paragraph are 917 included on all such copies and derivative works. However, this 918 document itself may not be modified in any way, such as by removing 919 the copyright notice or references to the Internet Society or other 920 Internet organizations, except as needed for the purpose of 921 developing Internet standards in which case the procedures for 922 copyrights defined in the Internet Standards process must be 923 followed, or as required to translate it into languages other than 924 English. 926 The limited permissions granted above are perpetual and will not be 927 revoked by the Internet Society or its successors or assigns. 929 This document and the information contained herein is provided on an 930 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 931 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 932 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 933 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 934 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."