Internet-Draft E. Cardona
draft-jones-cable-gateway-tools-mib-01.txt CableLabs
Expires: July 2003
K. Luehrs
CableLabs
D. Jones
YAS BBV
January
2003
Cable Gateway Tools Management Information Base
for CableHome compliant Residential Gateways
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1].
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a basic set of managed objects for SNMP-
based management of CableHome compliant WAN Gateway Devices and home
routers. Specifically, this MIB defines managed objects for both a
Cardona/Luehrs/Jones Expires - July 2003 [Page 1]
Internet-Draft CableHome Gateway Tools MIB January 2003
connection speed tool and an ICMP "ping" tool between the Gateway and
devices on the LAN.
This memo specifies a MIB module in a manner that is compliant to the
SNMP SMIv2 [5][6][7]. The set of objects is consistent with the SNMP
framework and existing SNMP standards.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [2].
Table of Contents
1. The Internet-Standard Management Framework.....................2
2. Glossary.......................................................3
2.1 CableHome Residential Gateway..............................3
2.2 Portal Services............................................3
2.3 LAN IP Device..............................................3
2.4 WAN Management (WAN-Man) Address...........................3
2.5 WAN Data (WAN-Data) Address................................3
2.6 LAN Translated (LAN-Trans) Address.........................3
2.7 LAN Passthrough (LAN-Pass) Address.........................4
3. Overview.......................................................4
3.1 Structure of the MIB.......................................4
4. MIB Definitions................................................4
5. Formal Syntax.................................................15
6. Security Considerations.......................................15
7. References....................................................15
8. Intellectual Property.........................................17
9. Author's Addresses............................................18
10. Full Copyright Statement.....................................18
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [12].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [7], STD 58, RFC 2579 [8] and STD 58, RFC 2580 [9].
Cardona/Luehrs/Jones Expires - July 2003 [Page 2]
Internet-Draft CableHome Gateway Tools MIB January 2003
2. Glossary
The terms in this document are derived either from normal cable
system usage, from normal residential gateway operation, or from the
documents associated with the CableHome Specifications [21].
2.1 CableHome Residential Gateway
A CableHome Residential gateway passes data traffic between the cable
operator's broadband data network (the Wide Area Network, WAN) and
the Local Area Network (LAN) in the cable data service subscriber's
residence or business. In addition to passing traffic between the WAN
and LAN, the CableHome Residential Gateway provides several services
including a DHCP client and a DHCP server (RFC2131) [22], a TFTP
server (RFC1350) [23], management services as enabled by
SNMPv1/v2c/v3 agent compliant with the RFCs listed in Section 1, and
security services including stateful packet inspection firewall
functionality and software code image verification using techniques.
2.2 Portal Services
A logical element aggregating the set of CableHome-specified
functionality in a CableHome compliant cable gateway device.
2.3 LAN IP Device
A LAN IP Device is representative of a typical IP device expected to
reside on home networks, and is assumed to contain a TCP/IP stack as
well as a DHCP client.
2.4 WAN Management (WAN-Man) Address
WAN Management Addresses are intended for network management traffic
on the cable network between the network management system and the PS
element. Typically, these addresses will reside in private IP address
space.
2.5 WAN Data (WAN-Data) Address
WAN Data Addresses are intended for subscriber application traffic on
the cable network and beyond, such as traffic between LAN IP Devices
and Internet hosts. Typically, these addresses will reside in public
IP address space.
2.6 LAN Translated (LAN-Trans) Address
LAN Translated Addresses are intended for subscriber application and
management traffic on the home network between LAN IP Devices and the
Cardona/Luehrs/Jones Expires - July 2003 [Page 3]
Internet-Draft CableHome Gateway Tools MIB January 2003
PS element. Typically, these addresses will reside in private IP
address space, and can typically be reused across subscribers.
2.7 LAN Passthrough (LAN-Pass) Address
LAN Passthrough Addresses are intended for subscriber application
traffic, such as traffic between LAN IP Devices and Internet hosts,
on the home network, the cable network, and beyond. Typically, these
addresses will reside in public IP address space.
3. Overview
This MIB provides a set of security objects required for the
management of CableHome compliant residential gateway devices. The
specification is derived from the CableHome 1.0 specification [21].
3.1 Structure of the MIB
This MIB is structured into two groups:
The cabhCtpConnSpeed group contains objects needed to test the
connection speed between the Gateway and a LAN device.
The cabhCtpPing Group provides objects allowing the manager to send
an ICMP ping from the Gateway to a LAN device.
4. MIB Definitions
CABH-CTP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE FROM SNMPv2-SMI
TruthValue FROM SNMPv2-TC
OBJECT-GROUP,
MODULE-COMPLIANCE FROM SNMPv2-CONF
InetAddressType,
InetAddress FROM INET-ADDRESS-MIB
cabhDevMib FROM CABH-DEV-MIB;
Cardona/Luehrs/Jones Expires - July 2003 [Page 4]
Internet-Draft CableHome Gateway Tools MIB January 2003
--==============================================================
--
-- History:
--
-- Date Reason
-- 10/28/02 -00
-- 01/22/03 -01
--
--==============================================================
cabhCtpMib MODULE-IDENTITY
LAST-UPDATED "200301220000Z" -- January 22, 2003
ORGANIZATION "CableLabs Broadband Access Department"
CONTACT-INFO
"Kevin Luehrs
Postal: Cable Television Laboratories, Inc.
400 Centennial Parkway
Louisville, Colorado 80027-1266
U.S.A.
Phone: +1 303-661-9100
Fax: +1 303-661-9199
E-mail: k.luehrs@cablelabs.com"
DESCRIPTION
"This MIB module defines the diagnostic controls
offered by the CableHome Test Portal (CTP).
Acknowledgements:
Roy Spitzer - Consultant to CableLabs
Mike Mannette - Consultant to CableLabs
Randy Dunton - Intel
Dmitrii Loukianov - Intel
Wes Peters - DoBox, Inc.
Chris Zacker - Broadcom"
REVISION "200301220000Z" -- January 22, 2003
DESCRIPTION
"Initial version, published as RFC xxxx."
-- RFC editor to assign xxxx
::= { cabhDevMib 5}
-- Textual conventions
cabhCtpObjects OBJECT IDENTIFIER ::= { cabhCtpMib 1 }
cabhCtpBase OBJECT IDENTIFIER ::= { cabhCtpObjects 1 }
cabhCtpConnSpeed OBJECT IDENTIFIER ::= { cabhCtpObjects 2 }
cabhCtpPing OBJECT IDENTIFIER ::= { cabhCtpObjects 3 }
--
Cardona/Luehrs/Jones Expires - July 2003 [Page 5]
Internet-Draft CableHome Gateway Tools MIB January 2003
-- The following group describes the base objects in the CableHome
-- Management Portal.
--
cabhCtpSetToFactory OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to true(1) causes all the tables
in the CTP MIB to be cleared, and all CTP MIB objects
with default values set back to those default values.
Reading this object always returns false(2)."
::={cabhCtpBase 1}
--
-- Parameter and results from Connection Speed Command
--
cabhCtpConnSrcIpType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IP Address type used as the source address for
the Connection Speed Test."
DEFVAL { ipv4 }
::= { cabhCtpConnSpeed 1 }
cabhCtpConnSrcIp OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IP Address used as the source address for the
Connection Speed Test. The default value is the value
of cabhCdpServerRouter (192.168.0.1)."
REFERENCE
"CableHome Specification Section 6.4.4"
DEFVAL { 'c0a80001'h } -- 192.168.0.1
::= { cabhCtpConnSpeed 2 }
cabhCtpConnDestIpTypeOBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IP Address Type for the CTP Connection Speed Tool
destination address."
DEFVAL { ipv4 }
Cardona/Luehrs/Jones Expires - July 2003 [Page 6]
Internet-Draft CableHome Gateway Tools MIB January 2003
::={ cabhCtpConnSpeed 3 }
cabhCtpConnDestIp OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IP Address used as the destination address for
the Connection Speed Test."
::= { cabhCtpConnSpeed 4 }
cabhCtpConnProto OBJECT-TYPE
SYNTAX INTEGER {
udp (1),
tcp (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The protocol used in the Connection Speed Test.
TCP testing is optional."
DEFVAL { udp }
::= { cabhCtpConnSpeed 5 }
cabhCtpConnNumPktsOBJECT-TYPE
SYNTAX INTEGER (1..65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of packets the CTP is to send when
triggered to execute the Connection Speed Tool."
DEFVAL { 100 }
::= { cabhCtpConnSpeed 6 }
cabhCtpConnPktSizeOBJECT-TYPE
SYNTAX INTEGER (64..1518)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The size of the test frames."
REFERENCE
""
DEFVAL { 1518 }
::= { cabhCtpConnSpeed 7 }
cabhCtpConnTimeOutOBJECT-TYPE
Cardona/Luehrs/Jones Expires - July 2003 [Page 7]
Internet-Draft CableHome Gateway Tools MIB January 2003
SYNTAX INTEGER (0..600000) -- Max 10 minutes
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The timeout value for the response. A value of zero
indicates no time out and can be used for TCP only."
DEFVAL {30000} -- 30 seconds
::= { cabhCtpConnSpeed 8 }
cabhCtpConnControlOBJECT-TYPE
SYNTAX INTEGER {
start(1),
abort(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The control for the Connection Speed Tool. Setting
this object to start(1) causes the Connection Speed
Tool to execute. Setting this object to abort(2)
causes the Connection Speed Tool to stop running.
This parameter should only be set via SNMP."
DEFVAL {abort }
::={ cabhCtpConnSpeed 9 }
cabhCtpConnStatus OBJECT-TYPE
SYNTAX INTEGER {
notRun(1),
running(2),
complete(3),
aborted(4),
timedOut(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The status of the Connection Speed Tool."
DEFVAL { notRun }
::={ cabhCtpConnSpeed 10 }
cabhCtpConnPktsSent OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets the CTP sent after it was
Cardona/Luehrs/Jones Expires - July 2003 [Page 8]
Internet-Draft CableHome Gateway Tools MIB January 2003
triggered to execute the Connection Speed Tool."
::= { cabhCtpConnSpeed 11 }
cabhCtpConnPktsRecv OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets the CTP received after it
executed the Connection Speed Tool."
::= { cabhCtpConnSpeed 12 }
cabhCtpConnRTT OBJECT-TYPE
SYNTAX INTEGER (0..600000)
UNITS "millisec"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The resulting round trip time for the set of packets
sent to and received from the target LAN IP Device."
::= { cabhCtpConnSpeed 13 }
cabhCtpConnThroughputOBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The average round-trip throughput measured in
kilobits per second."
::= { cabhCtpConnSpeed 14 }
--
-- Parameters and Results for Ping Command
--
cabhCtpPingSrcIpType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IP Address Type for CTP Ping Tool source address."
DEFVAL { ipv4 }
::={ cabhCtpPing 1 }
cabhCtpPingSrcIp OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
Cardona/Luehrs/Jones Expires - July 2003 [Page 9]
Internet-Draft CableHome Gateway Tools MIB January 2003
DESCRIPTION
"The IP Address used as the source address for
the Ping Test. The default value is the value of
CabhCdpServerRouter (192.168.0.1)."
REFERENCE
"CableHome 1.0 Specification Section 6.4.4"
DEFVAL { 'c0a80001'h }
::= { cabhCtpPing 2 }
cabhCtpPingDestIpTypeOBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IP Address Type for the CTP Ping Tool
destination address."
DEFVAL { ipv4 }
::={ cabhCtpPing 3 }
cabhCtpPingDestIp OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The Destination IP Address used as the destination
address for the Ping Test."
::= { cabhCtpPing 4 }
cabhCtpPingNumPktsOBJECT-TYPE
SYNTAX INTEGER (1..4)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of packets to send to each host."
DEFVAL {1}
::= { cabhCtpPing 5 }
cabhCtpPingPktSizeOBJECT-TYPE
SYNTAX INTEGER (64..1518)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The size of the test frames."
DEFVAL {64}
::= { cabhCtpPing 6 }
cabhCtpPingTimeBetween OBJECT-TYPE
SYNTAX INTEGER (0..600000)
UNITS "milliseconds"
MAX-ACCESS read-write
Cardona/Luehrs/Jones Expires - July 2003 [Page 10]
Internet-Draft CableHome Gateway Tools MIB January 2003
STATUS current
DESCRIPTION
"The time between sending one ping and the next."
DEFVAL { 1000 }
::= { cabhCtpPing 7 }
cabhCtpPingTimeOut OBJECT-TYPE
SYNTAX INTEGER (1..600000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The time out for ping response (ICMP reply) for a
single transmitted ping message (ICMP request)."
DEFVAL { 1000 } -- 1 second
::={ cabhCtpPing 8 }
cabhCtpPingControlOBJECT-TYPE
SYNTAX INTEGER {
start(1),
abort(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The control for the Ping Tool. Setting this object to
start(1) causes the Ping Tool to execute. Setting this
object to abort(2) causes the Ping Tool to stop running.
This parameter should only be set via SNMP."
DEFVAL {abort }
::={ cabhCtpPing 9 }
cabhCtpPingStatus OBJECT-TYPE
SYNTAX INTEGER {
notRun(1),
running(2),
complete(3),
aborted(4),
timedOut(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The status of the Ping Tool."
DEFVAL { notRun }
::={ cabhCtpPing 10 }
Cardona/Luehrs/Jones Expires - July 2003 [Page 11]
Internet-Draft CableHome Gateway Tools MIB January 2003
cabhCtpPingNumSent OBJECT-TYPE
SYNTAX INTEGER (0..4)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Pings sent"
::={ cabhCtpPing 11 }
cabhCtpPingNumRecvOBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of pings received."
::= { cabhCtpPing 12 }
cabhCtpPingAvgRTT OBJECT-TYPE
SYNTAX INTEGER (0..600000)
UNITS "millisec"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The resulting average of round trip times for
acknowledged packets."
::= { cabhCtpPing 13 }
cabhCtpPingMaxRTT OBJECT-TYPE
SYNTAX INTEGER (0..600000)
UNITS "millisec"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The resulting maximum of round trip times for
acknowledged packets."
::= { cabhCtpPing 14 }
cabhCtpPingMinRTT OBJECT-TYPE
SYNTAX INTEGER (0..600000)
UNITS "millisec"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The resulting minimum of round trip times for
acknowledged packets."
::= { cabhCtpPing 15 }
cabhCtpPingNumIcmpError OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
Cardona/Luehrs/Jones Expires - July 2003 [Page 12]
Internet-Draft CableHome Gateway Tools MIB January 2003
STATUS current
DESCRIPTION
"Number of ICMP errors."
::= { cabhCtpPing 16 }
cabhCtpPingIcmpError OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The last ICMP error."
::= { cabhCtpPing 17 }
--==============================================================
--
-- notification group is for future extension.
--
cabhCtpNotification OBJECT IDENTIFIER ::= { cabhCtpMib 2 }
cabhCtpNotifications OBJECT IDENTIFIER ::= { cabhCtpNotification 0
}
cabhCtpConformance OBJECT IDENTIFIER ::= { cabhCtpMib 3 }
cabhCtpCompliances OBJECT IDENTIFIER ::= { cabhCtpConformance 1 }
cabhCtpGroups OBJECT IDENTIFIER ::= { cabhCtpConformance 2 }
--
-- Notification Group
--
--
-- compliance statements
cabhCtpBasicCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for devices that
implement Portal Service feature."
MODULE --cabhCtpMib
-- unconditionally mandatory groups
MANDATORY-GROUPS {
cabhCtpGroup
}
::= { cabhCtpCompliances 3 }
Cardona/Luehrs/Jones Expires - July 2003 [Page 13]
Internet-Draft CableHome Gateway Tools MIB January 2003
cabhCtpGroup OBJECT-GROUP
OBJECTS {
cabhCtpSetToFactory,
cabhCtpConnSrcIpType,
cabhCtpConnSrcIp,
cabhCtpConnDestIpType,
cabhCtpConnDestIp,
cabhCtpConnProto,
cabhCtpConnNumPkts,
cabhCtpConnPktSize,
cabhCtpConnTimeOut,
cabhCtpConnControl,
cabhCtpConnStatus,
cabhCtpConnPktsSent,
cabhCtpConnPktsRecv,
cabhCtpConnRTT,
cabhCtpConnThroughput,
cabhCtpPingSrcIpType,
cabhCtpPingSrcIp,
cabhCtpPingDestIpType,
cabhCtpPingDestIp,
cabhCtpPingNumPkts,
cabhCtpPingPktSize,
cabhCtpPingTimeBetween,
cabhCtpPingTimeOut,
cabhCtpPingControl,
cabhCtpPingStatus,
cabhCtpPingNumSent,
cabhCtpPingNumRecv,
cabhCtpPingAvgRTT,
cabhCtpPingMinRTT,
cabhCtpPingMaxRTT,
cabhCtpPingNumIcmpError,
cabhCtpPingIcmpError
}
STATUS current
DESCRIPTION
"Group of objects for CableHome CTP MIB."
::= { cabhCtpGroups 1 }
END
Cardona/Luehrs/Jones Expires - July 2003 [Page 14]
Internet-Draft CableHome Gateway Tools MIB January 2003
5. Formal Syntax
The following syntax specification uses the augmented Backus-Naur
Form (BNF) as described in RFC-2234 [3].
6. Security Considerations
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these objects when sending
them over the network via SNMP. Not all versions of SNMP provide
features for such a secure environment.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
7. References
1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
2 Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997
Cardona/Luehrs/Jones Expires - July 2003 [Page 15]
Internet-Draft CableHome Gateway Tools MIB January 2003
3 Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, Internet Mail Consortium and
Demon Internet Ltd., November 1997
4 Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.
5 Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC
1212, March 1991.
6 Rose, M., "A Convention for Defining Traps for use with the SNMP",
RFC 1215, March 1991.
7 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of
Management Information for Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
8 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999.
9 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
10 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network
Management Protocol", STD 15, RFC 1157, May 1990.
11 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January 1996.
12 Case, J., Mundy, R., Partain, D, and B. Stewart, "Introduction and
Applicability Statements for Internet Standard Management
Framework", RFC 3410, December 2002.
13 Harrington D., Presuhn R. and B. Wijnen, "An Architecture for
Describing Simple Network Management Protocol (SNMP) Management
Frameworks", RFC 3411, December 2002.
14 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 3412, December 2002.
15 Levi, D., Meyer, P., and B. Stewart, ôSimple Network Management
Protocol (SNMP) Applications", RFC 3413, December 2002.
Cardona/Luehrs/Jones Expires - July 2003 [Page 16]
Internet-Draft CableHome Gateway Tools MIB January 2003
16 Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
3414, December 2002.
17 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 3415, December 2002.
18 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Version 2 of the Protocol Operations for the Simple Network
Management Protocol (SNMPv2)", RFC 3416, Decemeber 2002.
19 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Transport Mappings for the Simple Network Management Protocol
(SNMPv2)", RFC 3417, December 2002.
20 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Management Information Base (MIB) for the Simple Network
Management Protocol (SNMP)", RFC 3418, December 2002.
21 Cable Television Laboratories, ôCableHome 1.0 Specificationö, CH-
SP-I02-020920, September 2002,
http://www.cablelabs.com/projects/cablehome/specifications.
22 Drums, R., ôDynamic Host Configuration Protocolö, RFC 2131, March
1997.
23 Sollins, K., ôThe TFTP Protocol (Revision 2)ö, RFC 1350, July
1992.
8. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can
be obtained from the IETF Secretariat.
Cardona/Luehrs/Jones Expires - July 2003 [Page 17]
Internet-Draft CableHome Gateway Tools MIB January 2003
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
9. Author's Addresses
Eduardo Cardona
Cable Television Laboratories
400 Centennial Parkway
Louisville, CO 80027
Phone: +1 303.661.9100
Email: e.cardona@cablelabs.com
Kevin Luehrs
Cable Television Laboratories
Louisville, CO 80027
Phone: +1 303.661.9100
Email: k.luehrs@cablelabs.com
Doug Jones
YAS Broadband Ventures
300 Brickstone Square
Andover, MA 01810
Phone: +1 303.661.3823
Email: doug@yas.com
10. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
Cardona/Luehrs/Jones Expires - July 2003 [Page 18]
Internet-Draft CableHome Gateway Tools MIB January 2003
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
Cardona/Luehrs/Jones Expires - July 2003 [Page 19]