IPCDN Working Group Doug Jones
Internet Draft YAS Broadband
Expires April 2003 October 2002
Cable Gateway Address Mapping Management Information Base
for CableHome compliant Residential Gateways
draft-jones-cable-gateway-addressing-00
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
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 (2002). 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 Network Address Translation and transparent
bridging functionality within CableHome 1.0 and 1.1 compliant
residential gateways.
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.
Jones Expires April 2003 [Page 1]
Internet Draft Cable Gateway Address Mapping MIB October 2002
Table of Contents
1 The SNMP Management Framework ................................... 2
2 Glossary ........................................................ 3
3 Overview ........................................................ 4
3.1 Structure of the MIB .......................................... 4
3.2 Management requirements ....................................... 5
4 Definitions ..................................................... 5
5 Acknowledgments ................................................ 13
6 References ..................................................... 13
7 Security Considerations ........................................ 15
8 Intellectual Property .......................................... 15
9 Author's Address ............................................... 15
10 Full Copyright Statement ...................................... 16
1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in STD
16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
second version, called SMIv2, is described in STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [8]. A second version of the SNMP
message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
1906 [10]. The third version of the message protocol is called
SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [8]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2575
[15].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
Jones Expires March 2003 [Page 2]
Internet Draft Cable Gateway Address Mapping MIB October 2002
This memo specifies a MIB module that is compliant to the SMIv2.
A MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
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 1.0 Specifications.
2.1 CATV
Originally "Community Antenna Television", now used to refer to any
cable or hybrid fiber and cable system used to deliver video signals
to a community.
2.2 Cable Gateway Device
A cable gateway device 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 cable gateway device provides several services
including a DHCP client and a DHCP server [RFC2131], a TFTP server
[RFC1350], 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.3 Portal Services
A logical element aggregating the set of CableHome-specified
functionality in a CableHome compliant cable gateway device.
2.4 CAP
CableHome Address Portal - The logical function within the Cable
Gateway Device which provides the NAT/NAPT routing and
transparent bridging functions.
Jones Expires March 2003 [Page 3]
Internet Draft Cable Gateway Address Mapping MIB October 2002
3. Overview
This MIB provides a set of objects required for the management of
CAP NAT/NAPT and transparent bridging functions within CableHome
compliant Residential Gateways (RG). The MIB is derived from the
CableHome 1.0 & 1.1 Specifications [XXX].
Depending on the configuration of the CAP, a CableHome RG will
perform either standard NAT Network Address Translation or NAPT
Network Address Port Translation. It is also possible to
configure the CableHome RG to provide only NAT/NAPT functions,
transparent bridging functions, or a combination of the two.
The NAT/NAPT function of the CableHome RG generally translates
traffic to and from privately addressed devices in the home
network to one (NAPT) or more (NAT) public addresses that are
provisioned into the RG for this purpose.
In order for the CableHome RG to support devices and applications
that are NAT/NAPT intolerant, the RG also supports a type of
transparent bridging, which we call Passthrough, by configuring
the RG to bridge traffic for all devices on the home network or
to bridge traffic to and from particular hardware addresses on
the home network.
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 [16].
3.1. Structure of the MIB
This MIB is structured into two groups:
The cabhCapBase group provides a mechanism to define the
inactivity timeouts for TCP, UDP, and ICMP traffic types.
It also provides a mechanism to set the Primary Packet-handling
Mode of the RG - either NAT, NAPT, or Passthrough. Finally,
this group provides a means to reset most MIB values defined
in this MIB to their factory defaults.
The cabhCapMap group contains information pertaining to the
NAT/NAPT routing and transparent bridging (Passthrough)
functions of the RG. The cabhCapMap group consists of two
tables:
- cabhCapMappingTable: Allows for creating and
monitoring static and dynamic NAT and NAPT
mappings.
Jones Expires March 2003 [Page 4]
Internet Draft Cable Gateway Address Mapping MIB October 2002
- cabhCapPassthroughTable: Allows for configuring the
RG to transparently bridge traffic based on
hardware addresses of devices on the home
network.
3.2 Management requirements
In addition to the explicit requirements in this specification,
the Cable Gateway MUST support all applicable CableHome and IETF
requirements and MIB objects.
4. Definitions
CABH-CAP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Unsigned32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
TruthValue,
RowStatus,
PhysAddress FROM SNMPv2-TC
OBJECT-GROUP,
MODULE-COMPLIANCE FROM SNMPv2-CONF
InetAddressType,
InetAddress,
InetPortNumber FROM INET-ADDRESS-MIB
clabProjCableHome FROM CLAB-DEF-MIB;
--===================================================================
--
-- History:
--
-- Date Modified by Reason
-- 04/05/02 Issued I01
-- 09/20/02 Issued I02
--
--===================================================================
cabhCapMib MODULE-IDENTITY
LAST-UPDATED "200210250000Z" -- October 25, 2002
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 supplies the basic management objects for
the CableHome Addressing Portal (CAP) portion of the PS.
Jones Expires March 2003 [Page 5]
Internet Draft Cable Gateway Address Mapping MIB October 2002
Acknowledgements:
Roy Spitzer - Consultant to CableLabs
Mike Mannette - Consultant to Cable Labs
Randy Dunton - Intel
Dmitrii Loukianov - Intel
Itay Sherman - Texas Instruments
Chris Zacker - Broadcom
Rick Vetter - Consultant to Cable Labs
John Bevilacqua - YAS"
::= { clabProjCableHome 3 }
-- Textual conventions
CabhCapPacketMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The data type established when
a binding/mapping is established."
SYNTAX INTEGER {
napt (1), -- NAT with port translation
nat (2), -- Basic NAT
passthrough (3) -- Passthrough Address
}
cabhCapObjects OBJECT IDENTIFIER ::= { cabhCapMib 1 }
cabhCapBase OBJECT IDENTIFIER ::= { cabhCapObjects 1 }
cabhCapMap OBJECT IDENTIFIER ::= { cabhCapObjects 2 }
--===================================================================
--
-- General CAP Parameters
--
--===================================================================
cabhCapTcpTimeWait OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is the maximum inactivity time to wait before
assuming TCP session is terminated. It has no relation to
the TCP session TIME_WAIT state referred to in [RFC793]"
DEFVAL { 300 }
::= { cabhCapBase 1 }
Jones Expires March 2003 [Page 6]
Internet Draft Cable Gateway Address Mapping MIB October 2002
cabhCapUdpTimeWait OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The inactivity time to wait before destroying CAP
mappings for UDP."
DEFVAL { 300 } -- 5 minutes
::={ cabhCapBase 2 }
cabhCapIcmpTimeWait OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The inactivity time to wait before destroying CAP
mappings for ICMP."
DEFVAL { 300 } -- 5 minutes
::= { cabhCapBase 3 }
cabhCapPrimaryMode OBJECT-TYPE
SYNTAX CabhCapPacketMode
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The Primary Packet Handling Mode to be used."
DEFVAL { napt }
::= { cabhCapBase 4 }
cabhCapSetToFactory OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to true(1) causes the all the tables
in the CAP to be cleared, and all CAP objects with
defaults to be reset back to their default values.
The objects to set to factory default values when this
object is set to 'true' are listed below:
cabhCapTcpTimeWait,
cabhCapUdpTimeWait,
cabhCapIcmpTimeWait,
cabhCapPrimaryMode,
cabhCapMappingWanAddrType,
cabhCapMappingWanPort,
Jones Expires March 2003 [Page 7]
Internet Draft Cable Gateway Address Mapping MIB October 2002
cabhCapMappingLanAddrType,
cabhCapMappingLanPort
"
::= { cabhCapBase 5 }
--===================================================================
--
-- cabhCapMappingTable (CAP Mapping Table)
--
-- The cabhCapMappingTable contains the info for all CAP mappings.
--
--===================================================================
cabhCapMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF CabhCapMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains IP address mapping for all CAP
mappings."
::= { cabhCapMap 1 }
cabhCapMappingEntry OBJECT-TYPE
SYNTAX CabhCapMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"List of CAP IP mappings."
INDEX { cabhCapMappingIndex }
::= { cabhCapMappingTable 1 }
CabhCapMappingEntry ::= SEQUENCE {
cabhCapMappingWanAddrType InetAddressType,
cabhCapMappingIndex INTEGER,
cabhCapMappingWanAddr InetAddress,
cabhCapMappingWanPort InetPortNumber,
cabhCapMappingLanAddrType InetAddressType,
cabhCapMappingLanAddr InetAddress,
cabhCapMappingLanPort InetPortNumber,
cabhCapMappingMethod INTEGER,
cabhCapMappingProtocol INTEGER,
cabhCapMappingRowStatus RowStatus
}
cabhCapMappingIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Index into the CAP Mapping Table."
::= { cabhCapMappingEntry 1 }
Jones Expires March 2003 [Page 8]
Internet Draft Cable Gateway Address Mapping MIB October 2002
cabhCapMappingWanAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address type assigned on the WAN side. IP version 4
is typically used."
DEFVAL { ipv4 }
::= { cabhCapMappingEntry 2 }
cabhCapMappingWanAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address assigned on the WAN side. IP version 4 is
typically used."
::= { cabhCapMappingEntry 3 }
cabhCapMappingWanPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The TCP/UDP port number or ICMP sequence number on the WAN
side. A port number of 0 indicates a NAT mapping. A
non-zero port number indicates an NAPT mapping."
DEFVAL { 0 }
::= { cabhCapMappingEntry 4 }
cabhCapMappingLanAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address type assigned on the LAN side. IP version 4
is typically used."
DEFVAL { ipv4 }
::= { cabhCapMappingEntry 5 }
cabhCapMappingLanAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address assigned on the LAN side. IP version 4 is
typically used."
::= { cabhCapMappingEntry 6 }
Jones Expires March 2003 [Page 9]
Internet Draft Cable Gateway Address Mapping MIB October 2002
cabhCapMappingLanPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The TCP/UDP port number or ICMP sequence number on the LAN
side. A port number of 0 indicates a NAT mapping. A non-zero
port number indicates an NAPT mapping."
DEFVAL { 0 }
::= { cabhCapMappingEntry 7 }
cabhCapMappingMethod OBJECT-TYPE
SYNTAX INTEGER {
static (1),
dynamic (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates how this mapping was created. Static means that it
was provisioned, and dynamic means that it was handled by the
PS itself."
::= { cabhCapMappingEntry 8 }
cabhCapMappingProtocol OBJECT-TYPE
SYNTAX INTEGER {
other (1), -- not specified
icmp (2),
udp (3),
tcp (4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The protocol for this mapping."
::= { cabhCapMappingEntry 9 }
cabhCapMappingRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The RowStatus interlock for the creation and deletion of a
cabhCapMappingTable entry. Changing the value of the IP
address or port number columns of the CAP Mapping Table may
have an effect on active traffic, so the CMP will prevent
modification of this table's columns when the
cabhCapMappingRowStatus object is in the active state."
::={ cabhCapMappingEntry 10 }
Jones Expires March 2003 [Page 10]
Internet Draft Cable Gateway Address Mapping MIB October 2002
--===================================================================
--
-- cabhCapPassthroughTable (CAP Passthrough Table)
--
-- The cabhCapPassthroughTable contains the MAC Addresses for
-- all LAN-IP Devices, which will be configured as passthrough.
--
--===================================================================
cabhCapPassthroughTable OBJECT-TYPE
SYNTAX SEQUENCE OF CabhCapPassthroughEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains MAC addresses for LAN-IP Devices which
are configured as passthrough mode."
::= { cabhCapMap 2 }
cabhCapPassthroughEntry OBJECT-TYPE
SYNTAX CabhCapPassthroughEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"List of hardware addresses of LAN IP Devices which are
configured for passthrough mode."
INDEX {cabhCapPassthroughIndex}
::= {cabhCapPassthroughTable 1}
CabhCapPassthroughEntry::=SEQUENCE {
cabhCapPassthroughIndex INTEGER,
cabhCapPassthroughMacAddr PhysAddress,
cabhCapPassthroughRowStatus RowStatus
}
cabhCapPassthroughIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index into the CAP Passthrough Table."
::= { cabhCapPassthroughEntry 1 }
cabhCapPassthroughMacAddr OBJECT-TYPE
SYNTAX PhysAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Hardware address of the LAN-IP Device to be configured
as passthrough mode."
Jones Expires March 2003 [Page 11]
Internet Draft Cable Gateway Address Mapping MIB October 2002
::={cabhCapPassthroughEntry 2}
cabhCapPassthroughRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The RowStatus interlock for the creation and deletion
of a cabhCapPassthroughTable entry. There are no
restrictions on setting the read-create column of this
table (i.e., cabhCapPassthroughMacAddr ) when the status
of cabhCapPassthroughRowStatus is active."
::= { cabhCapPassthroughEntry 3 }
--
-- notification group is for future extension.
--
cabhCapNotification OBJECT IDENTIFIER ::= { cabhCapMib 2 0 }
cabhCapConformance OBJECT IDENTIFIER ::= { cabhCapMib 3 }
cabhCapCompliances OBJECT IDENTIFIER ::= { cabhCapConformance 1 }
cabhCapGroups OBJECT IDENTIFIER ::= { cabhCapConformance 2 }
--
-- Notification Group
--
-- compliance statements
cabhCapBasicCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for devices that implement
MTA feature."
MODULE --cabhCapMib
-- unconditionally mandatory groups
MANDATORY-GROUPS {
cabhCapGroup
}
::= { cabhCapCompliances 1 }
Jones Expires March 2003 [Page 12]
Internet Draft Cable Gateway Address Mapping MIB October 2002
cabhCapGroup OBJECT-GROUP
OBJECTS {
cabhCapTcpTimeWait,
cabhCapUdpTimeWait,
cabhCapIcmpTimeWait,
cabhCapPrimaryMode,
cabhCapSetToFactory,
cabhCapMappingWanAddrType,
cabhCapMappingWanAddr,
cabhCapMappingWanPort,
cabhCapMappingLanAddrType,
cabhCapMappingLanAddr,
cabhCapMappingLanPort,
cabhCapMappingMethod,
cabhCapMappingProtocol,
cabhCapMappingRowStatus,
cabhCapPassthroughMacAddr,
cabhCapPassthroughRowStatus
}
STATUS current
DESCRIPTION
"Group of objects for CableHome CAP MIB."
::= { cabhCapGroups 1 }
END
5. Acknowledgments
6. References
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
Jones Expires March 2003 [Page 13]
Internet Draft Cable Gateway Address Mapping MIB October 2002
[4] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of
Management Information for Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[6] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[7] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC
2573, April 1999.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999.
[16] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
Jones Expires March 2003 [Page 14]
Internet Draft Cable Gateway Address Mapping MIB October 2002
7. 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 object when
sending them over the network via SNMP. Not all versions of
SNMP provide features for such a secure environment.
SNMPv1 by itself is not a secure environment.
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.
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.
Jones Expires March 2003 [Page 15]
Internet Draft Cable Gateway Address Mapping MIB October 2002
9. Author's Address
Doug Jones
YAS BBV
400 Centennial Parkway
Louisville, CO 80027 USA
Phone: +1 303 661 6823
Email: doug@yas.com
10. Full Copyright Statement
Copyright (C) The Internet Society (2002). 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.
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.
Jones Expires March 2003 [Page 16]