ADSL MIB Working Group J.R. Turner Internet-Draft 2Wire, Inc. Expires: April 21, 2000 October 22, 1999 draft-turner-adslmib-cpeautoconf-00.txt Model for Auto-Provisioning CPE 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.. This Internet-Draft will expire on April 21, 2000. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Abstract This document proposes a method for the automatic provisioning of ADSL Customer Premise Equipment (CPE). The term "automatic" in this context implies that no end-user or customer intervention is required to configure and provision the CPE for broadband service. Further, the model suggested by this proposal enables automatic configuration of access network equipment utilizing "flow-through" provisioning techniques already introduced in other standards bodies. Turner Expires April 21, 2000 [Page 1] Internet-Draft Model for Auto-Provisioning CPE October 1999 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Enabling Technologies . . . . . . . . . . . . . . . . . . . . 5 3.1 Integrated Local Management Interface (ILMI) 4.0 . . . . . . . 5 3.2 Simple Network Management Protocol (SNMP) Version 3.0 . . . . 5 3.3 UDP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.4 Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . 5 4. Provisioning Model . . . . . . . . . . . . . . . . . . . . . . 6 5. Detailed Provisioning Procedure . . . . . . . . . . . . . . . 7 5.1 CPE Power-up Initialization . . . . . . . . . . . . . . . . . 7 5.2 Management Network Access . . . . . . . . . . . . . . . . . . 7 5.3 Provisioning MIB Access . . . . . . . . . . . . . . . . . . . 8 5.4 New or Modified Service Subscriptions . . . . . . . . . . . . 8 6. Service Discovery and Selection . . . . . . . . . . . . . . . 9 7. Provisioning Server Replication . . . . . . . . . . . . . . . 10 8. Scalability Issues . . . . . . . . . . . . . . . . . . . . . . 11 9. Security Considerations . . . . . . . . . . . . . . . . . . . 12 9.1 Subscriber authentication key(s) . . . . . . . . . . . . . . . 12 9.2 Service Information Notifications . . . . . . . . . . . . . . 12 9.3 Service-Specific Configuration . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 13 A. Draft Provisioning Server MIB . . . . . . . . . . . . . . . . 14 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 29 Turner Expires April 21, 2000 [Page 2] Internet-Draft Model for Auto-Provisioning CPE October 1999 1. Introduction The requirement for automatic provisioning exists because of potential scalability problems with manual, operator-assisted provisioning of mass-market DSL CPE. Critical to the success and economics of widespread deployment of DSL services is the ability for a particular network provider to easily install and maintain the broadband equipment for each customer, with little or no "hands-on" involvement by either the network provider or the customer. Utilizing existing protocol familiarity, this document attempts to combine several enabling technologies for automatic provisioning of DSL CPE. The methods employed should provide a secure and extensible environment that will scale readily as the success of broadband DSL access evolves. Turner Expires April 21, 2000 [Page 3] Internet-Draft Model for Auto-Provisioning CPE October 1999 2. Scope This proposal is limited to the provisioning of broadband service connectivity only. Within the context of this document, the term "service" is meant to imply applications such as "video-on-demand", "audio-on-demand", or other applicaton layer services. The provisioning capability discussed in this document only covers layer-2 and layer-3 connection establishment. This document does not address "service-specific" provisioning, wherein service-specific attributes are configured and managed. It is likely that individual applications will either be managed and configured using their own "in-band" techniques, or possibly through their own application-specific MIB. This doucment also does not address traditional network management of DSL physical layer or MIB-II information. Given that there are existing networks of DSLAMs and DSL modems currently deployed, fault management of physical layer DSL information is not addressed, and interface management that would normally be handled by MIB-II is also not duplicated (or rehashed). However, the model suggested by this proposal reuses many of the same protocol mechanisms that are used by traditional network management, so low-level management of DSL CPE is not precluded by this model Turner Expires April 21, 2000 [Page 4] Internet-Draft Model for Auto-Provisioning CPE October 1999 3. Enabling Technologies The configuration and provisioning methodology described in this proposal makes use of the following existing enabling technologies: 3.1 Integrated Local Management Interface (ILMI) 4.0 The proposed method utilizes ILMI [4] messages during the CPE bootstrap process. Specifically, the proposal accesses the auto-provisioning extensions [6] of the ILMI 4.0 MIB. 3.2 Simple Network Management Protocol (SNMP) Version 3.0 The proposed method utilizes SNMP Version 3 [5] as the primary network management protocol for both CPE and access network nodes. SNMP is widely deployed and understood by both CPE and telecommunications equipment vendors and customers. The SNMP capability is also leveraged by ILMI as well. Specifically, SNMP Version 3 contains robust security methods for both authentication of management clients, as well as support for confidentiality of the management information itself. SNMP Version 3 also updates earlier versions of SNMP with secure and reliable event notifications. This proposal uses the reliable notification capability to avoid burdensome polling rates by back-end network managment stations. 3.3 UDP/IP UDP/IP is the dominant transport for SNMP in internets and intranets, ILMI being a notable exception. Unlike ILMI and preconfigured point-to-point virtual circuits, the proposal emphasizes network management via IP connectivity, which allows access providers across all potential business model boundaries, the maximum freedom in determining access network management topology. 3.4 Dynamic Host Configuration Protocol (DHCP) DHCP [9[ is a very popular and well understood technology for automatic configuration of IP-based hosts in internets and intranets. DHCP uses a very complete and extensible set of attributes for automated network configuration. DHCP is widely deployed by service providers as a flexible means of IP address space management, as well as generic configuration of a wide variety of both IP and non-IP parameters. Turner Expires April 21, 2000 [Page 5] Internet-Draft Model for Auto-Provisioning CPE October 1999 4. Provisioning Model The provisioning model is based on an SNMP manager/agent paradigm, involving two management entities, the CPE itself, and a remote provisioning server that exists within the network. The provisioning server can either be a standalone host within the network, or it may be co-resident on the same system with another management capability. The provisioning server is a software abstraction within the context of this document. The relationship between CPE and provisioning server is not exactly client/server, since either CPE or provisioning server can temporarily serve as manager or agent. The manager and agent behavior between the two entities is context-sensitive. However, the nominal operating mode of the two entities is where the CPE acts in the role of SNMP manager, and the provisioning server contains an SNMP agent. The provisioning server contains all of the information related to CPE provisioning. The CPE accesses the provisioning server for it's service connectivity information. Turner Expires April 21, 2000 [Page 6] Internet-Draft Model for Auto-Provisioning CPE October 1999 5. Detailed Provisioning Procedure The following steps detail the proposed DSL CPE provisioning operations. 5.1 CPE Power-up Initialization During CPE initialization, the CPE SNMP manager will access the ILMI auto-provisioning MIB extension [6] within the network. The CPE will index the ILMI auto-provisioning service table for a virtual circuit (VC) associated with the access provider's management network. 5.2 Management Network Access Using the VC obtained via ILMI, the CPE will establish a PPP/LCP [7] connection to the network access server at the remote end of the VC. This network access server provides authenticated, secure access to the management network. The NAS may optionally employ RADIUS to enable this authentication step. Once an LCP session has successfully been established, an IPCP [8] session is then initiated over the PPP link to establish IP connectivity to the management network. Once IP has been successfully negotiated, the CPE will maintain this IP connectivity to the management network for as long as the CPE is powered up. This capability requires a dedicated VC to be available for CPE-to management network. Alternatively, the model supports the idea of SVC-based access to the management network, wherein both provisioning server and CPE know each other's ATM end system address and the virtual circuit (and associated resources) do not have to be allocated continously. Using IPCP, the CPE obtains an IP address that is valid within the management network domain. With IP connectivity established, the CPE subsequently issues DHCPINFORM requests to the management network attempting to locate a provisioning server on the management network. An administratively assigned DHCP server offers a set of available provisoning servers to the CPE. The CPE acknowledges the list of provisioning servers, and, through local policy, selects a particular provisioning server to use. One of the ways in which the "correct" provisioning server can be selected is through the CPE's use of the DHCP client identifier and/or DHCP user class specification in the DHCPINFORM request. If a particular access network maintains a particular provisioning server for each vendor of CPE supported, then the DHCP client identifier value could be used to return the specific provisioning server to use for the requesting CPE. Turner Expires April 21, 2000 [Page 7] Internet-Draft Model for Auto-Provisioning CPE October 1999 5.3 Provisioning MIB Access Using the IP address of the provisioning server, the CPE accesses the provisioning server MIB. The MIB is indexed according to a set of unique indices for the CPE (see MIB text in appendix A). The provisioning server MIB returns all services, and service-related connectivity parameters as part of the MIB access. All of the information necessary for the CPE to provision a network connection to the service provider is available within the CPE provisioning MIB. 5.4 New or Modified Service Subscriptions DSL CPE should not be required to poll the provisioning server for new services or service parameters. Instead, whenever new service subscriptions for a particular customer are added, or existing service subscription profile is modified, the CPE is notified immediately by the provisioning server. The provisioning MIB includes an SNMP notification type that is automatically generated whenever subscription information is altered in any way. The SNMP notification is an SNMPv3 inform message sent to the CPE by the provisioning server, indicating to the CPE that it should revalidate it's service information cache. The SNMPv3 inform is more robust than a traditional SNMP trap in that the "inform" notification type is reliable, and must be explicitly acknowledged by the CPE. Turner Expires April 21, 2000 [Page 8] Internet-Draft Model for Auto-Provisioning CPE October 1999 6. Service Discovery and Selection In addition to customer subscription information, the Provisioning Server MIB contains a service table that describes all services that are available to customers served by this management domain (which could be partitioned by business entity or geographic region). By accessing the service table, the CPE can make available to the customer, information regarding additional incremental service offerings. The service table contains information that allows a customer to shop for these additional services at their convenience, and even order these services online Turner Expires April 21, 2000 [Page 9] Internet-Draft Model for Auto-Provisioning CPE October 1999 7. Provisioning Server Replication It is strongly recommended that the network access provider maintain redundant provisioning servers within the network to prevent a single point of failure from impeding proper DSL service/CPE operation. Using multiple entries within the ILMI auto-discovery extensions MIB, an access provider can enable the DSL CPE to automatically switch provisioning servers during operation, should connectivity to an active server be in question. Likewise, the access network provider may also optimize provisioning server capacity through load balancing of CPE across a number of provisioning servers within the network. This can be done through optimal automatic configuration of ILMI MIB information. Specific policies and mechanisms for instrumentation of load balancing are outside the scope of this document. Turner Expires April 21, 2000 [Page 10] Internet-Draft Model for Auto-Provisioning CPE October 1999 8. Scalability Issues Where possible, it is recommended that bundles of PPP connections for management network connections be aggregated at a point early in the network (as close to the CPE as possible) in order to save switch resources in the allocation of permanent virtual circuits. The aggregation can utilize virtual path techniques or preferably Layer 2 Tunneling Protocol (L2TP). With the advent of switched virtual circuits, this problem becomes less and less a priority. Turner Expires April 21, 2000 [Page 11] Internet-Draft Model for Auto-Provisioning CPE October 1999 9. Security Considerations There are several issues regarding security that must be addressed in order to provide sufficient implementation of the model. Most, if not all, of the actual secure instrumentation of the model is provided for in the SNMP version 3 protocol. However, the following sub-sections detail some other issues regarding the security aspects of the model. 9.1 Subscriber authentication key(s) The subscriber authentication key is an opaque value used within the provisioning system to identify a CPE, and hence a particular subscriber premises. This authentication value should be made up of both CPE-derived information, as well as information derived by the network for the particular subscriber. The network-derived portion of the key should serve to prevent the overall authentication value from being "spoofed" 9.2 Service Information Notifications Previously, an SNMPv3 notification mechanism was described for notifying DSL CPE when service information for a subscriber is modified. Because the notification may contain information that modifies service-related connection information, the CPE should apply strict authentication on the notification so as to avoid being redirected to an unauthorized service. SNMP version 3 provides sufficient authentication capabilities via the "user-based" security model. Source IP addressing should not be used to authenticate the source of the notification since IP addresses can be spoofed. 9.3 Service-Specific Configuration As stated previously, both the provisioning server, as well as the DSL CPE, can assume either an SNMP manager or agent role, depending upon the type and context of communication. The model proposed by this document is primarily concerned with provisioning of layer-2 and layer-3 connectivity to specific service providers. However, once these circuits are established, one or more of these connections might be used by a service provider to manage their "service-specific" MIBs. Using SNMP version 3 user-based security, multiple service providers can independently manage their particular service- specific MIBs with a high degree of security. The SNMPv3 agent within the CPE will protect each service provider's MIB data from being accessed or modified by another service provider or untrusted third party. There will typically be only one instance of the SNMP agent within the CPE, so it is important that independent provider's service information is appropriately Turner Expires April 21, 2000 [Page 12] Internet-Draft Model for Auto-Provisioning CPE October 1999 protected. Author's Address Randy Turner 2Wire, Inc. 694 Tasman Dr. Milpitas, CA 95035 USA Phone: +1 408 895 1216 EMail: rturner@2wire.com URI: http://www.2wire.com Turner Expires April 21, 2000 [Page 13] Internet-Draft Model for Auto-Provisioning CPE October 1999 Appendix A. Draft Provisioning Server MIB RBBPROVISIONING-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, IpAddress, mib-2, enterprises FROM SNMPv2-SMI DisplayString, TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF InterfaceIndex, ifIndex FROM IF-MIB AtmAddr, AtmConnKind, AtmConnCastType, AtmServiceCategory, AtmTrafficDescrParamIndex, AtmVpIdentifier, AtmVcIdentifier FROM ATM-TC-MIB; rbbProvMIB MODULE-IDENTITY LAST-UPDATED "9909271200Z" ORGANIZATION "IETF ADSL MIB Working Group" CONTACT-INFO " Randy Turner Postal: 2Wire, Inc. 694 Tasman Dr. Milpitas, CA 95035 Tel: 408-895-1216 Fax: 408-428-9590 E-mail: rturner@2wire.com" DESCRIPTION "This is the MIB Module for provisioning of broadband customer premises equipment, specifically xDSL-related services. While not precluding other broadband technology, the MIB has been constructed around existing xDSL facilities, including ATM transports." ::= { enterprises 4839 32 } RBBServiceID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A globally unique OID that unambiguously specifies a particular service, and as much protocol and semantics as is necessary to access the service" Turner Expires April 21, 2000 [Page 14] Internet-Draft Model for Auto-Provisioning CPE October 1999 SYNTAX OBJECT IDENTIFIER RBBServiceName ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A string denoting the same information as RBBServiceOID, except this object is in human-readable form." SYNTAX DisplayString (SIZE(0..64)) RBBServiceProvider ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A human-readable string representing the name of the private or public entity that is making the service available. For a typical internet service provider (ISP), this would be the name of the ISP company itself" SYNTAX DisplayString (SIZE(0..64)) RBBServiceStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An enumeration representing the current state of a particular service availability or service subscription (i.e., up, down, enabled, etc.)" SYNTAX INTEGER { other(1), up(2), down(3), adminDown(4) } RBBURLType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An octet string containing a uniform resource locator (URL). The usage of this URL is object- context dependent. See individual object descriptions that reference this textual convention" SYNTAX DisplayString (SIZE(0..128)) RBBCPEAuthType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An opaque string used to identify a particular subscriber. Currently, this MIB does not specify how authentication strings are generated. This is still an open issue." SYNTAX OctetString (SIZE(0..64)) Turner Expires April 21, 2000 [Page 15] Internet-Draft Model for Auto-Provisioning CPE October 1999 RBBMailAddr ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The email address (user@domain) of a contact that is responsible for some entity that references this textual convention, such as the administrator for an access network, or the email address of the admin for a particular service provider" SYNTAX DisplayString (SIZE(0..64)) RBBCPESerialNumber ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Define the syntax of a product serial number" SYNTAX DisplayString (SIZE(0..32)) RBBVendorModel ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Define the syntax of a CPE vendor model" SYNTAX DisplayString (SIZE(0..64)) RowStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "" SYNTAX INTEGER { -- the following two values are states: -- these values may be read or written active(1), notInService(2), -- the following value is a state: -- this value may be read, but not written notReady(3), -- the following three values are -- actions: these values may be written, -- but are never read createAndGo(4), createAndWait(5), destroy(6) } rbbProvMIBObjects OBJECT IDENTIFIER ::= {rbbProvMIB 1} Turner Expires April 21, 2000 [Page 16] Internet-Draft Model for Auto-Provisioning CPE October 1999 rbbServicesGroup OBJECT IDENTIFIER ::= { rbbProvMIBObjects 1 } rbbSubGroup OBJECT IDENTIFIER ::= { rbbProvMIBObjects 2 } rbbCPEGroup OBJECT IDENTIFIER ::= { rbbProvMIBObjects 3 } rbbVendorGroup OBJECT IDENTIFIER ::= { rbbProvMIBObjects 4 } rbbNotifyGroup OBJECT IDENTIFIER ::= { rbbProvMIBObjects 12 } -- The MIB consists of five groups -- 1) The Services Group -- 2) The Subscription Group -- 3) The CPE Group -- 4) The Vendor-Equipment Group -- 5) and the Notification Group -- -- Define the Services Group -- srvServicesTable OBJECT-TYPE SYNTAX SEQUENCE OF SRVServiceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a sequence of rows where each row describes a particular service that is available to a broadband customer. The service availability expressed in this table is assumed to be valid only for customers served by this management infrastructure, and may differ on a regional basis, even within the same overall access network." ::= { rbbServicesGroup 1 } srvServiceEntry OBJECT-TYPE SYNTAX SRVServiceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object defines the individual rows in the SRV services table (srvServicesTable)" INDEX { srvServiceIdentifier } ::= { srvServicesTable 1} SRVServiceEntry ::= SEQUENCE { srvServiceIdentifier RBBServiceID, srvServiceName RBBServiceName, srvServiceProvider RBBServiceProvider, srvServiceStatus RBBServiceStatus, srvServiceConnType AtmConnKind, srvServiceQOSType INTEGER, Turner Expires April 21, 2000 [Page 17] Internet-Draft Model for Auto-Provisioning CPE October 1999 srvServiceSpeedReq INTEGER, srvServiceLatencyReq INTEGER, srvServiceURL RBBURLType, srvServiceDescr DisplayString, srvAdminContact RBBMailAddr, srvRowInfo RowStatus } srvServiceIdentifier OBJECT-TYPE SYNTAX RBBServiceID MAX-ACCESS read-create STATUS current DESCRIPTION "A unique object identifier (OID) value uniquely representing a particular service." ::= { srvServiceEntry 1 } srvServiceName OBJECT-TYPE SYNTAX RBBServiceName MAX-ACCESS read-create STATUS current DESCRIPTION "A human-readable name string that identifies a service to an end-user" ::= { srvServiceEntry 2 } srvServiceProvider OBJECT-TYPE SYNTAX RBBServiceProvider MAX-ACCESS read-create STATUS current DESCRIPTION "A human-readable name string that identifies the public or private sponsoring entity for a particular service." ::= { srvServiceEntry 3 } srvServiceStatus OBJECT-TYPE SYNTAX RBBServiceStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An INTEGER enumeration describing the current availability status of a particular service. NOTE: This status implies different semantics than that used by srvServiceSubrStatus" ::= { srvServiceEntry 4 } Turner Expires April 21, 2000 [Page 18] Internet-Draft Model for Auto-Provisioning CPE October 1999 srvServiceConnType OBJECT-TYPE SYNTAX AtmConnKind MAX-ACCESS read-create STATUS current DESCRIPTION "An enumerated value describing the type of endpoint address used to refer to a particular service, as well as whether the CPE should be an initiator or target during the connection." ::= { srvServiceEntry 5 } srvServiceQOSType OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-create STATUS current DESCRIPTION "The quality-of-service to be associated with a connection to a particular service." ::= { srvServiceEntry 6 } srvServiceSpeedReq OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-create STATUS current DESCRIPTION "The bandwidth or speed (in bits-per-second) necessary to realize a particular service" ::= { srvServiceEntry 7 } srvServiceLatencyReq OBJECT-TYPE SYNTAX INTEGER { high(1), med(2), low(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "An enumerated value that describes whether or not a particular service has special latency requirements associated to effectively realize the service." ::= { srvServiceEntry 8 } srvServiceURL OBJECT-TYPE SYNTAX RBBURLType MAX-ACCESS read-create STATUS current DESCRIPTION "A URL string associated with a particular service. A Turner Expires April 21, 2000 [Page 19] Internet-Draft Model for Auto-Provisioning CPE October 1999 service may be provisioned with an associated URL that can be used either as a provisioning link or as a potentially advertising source for the service." ::= { srvServiceEntry 9 } srvServiceDescr OBJECT-TYPE SYNTAX DisplayString (SIZE(0..256)) MAX-ACCESS read-create STATUS current DESCRIPTION "A human-readable string used to provide a brief description for a particular service." ::= { srvServiceEntry 10 } srvAdminContact OBJECT-TYPE SYNTAX RBBMailAddr MAX-ACCESS read-create STATUS current DESCRIPTION "A string representing the email address of an administrator contact for the particular service. This could either be a contact used to request new service or options associated with the service, OR, could be used as a support contact address for an existing subscription." ::= { srvServiceEntry 11 } srvRowInfo OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Maintains row status information for this table" ::= { srvServiceEntry 12 } -- -- Broadband Service Subscription Group -- rbbSubTable OBJECT-TYPE SYNTAX SEQUENCE OF RBBSubEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a sequence of rows where each row describes a particular service subscription between an end-user CPE and a particular service." ::= { rbbSubGroup 1 } Turner Expires April 21, 2000 [Page 20] Internet-Draft Model for Auto-Provisioning CPE October 1999 rbbSubEntry OBJECT-TYPE SYNTAX RBBSubEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object defines the individual rows in the subscription table (rbbSubTable)" INDEX { rbbSubVendor, rbbSubModel, rbbSubSerialNumber, rbbSubServiceIdentifier } ::= { rbbSubTable 1} RBBSubEntry ::= SEQUENCE { rbbSubVendor OBJECT IDENTIFIER, rbbSubModel RBBVendorModel, rbbSubSerialNumber DisplayString, rbbSubServiceIdentifier RBBServiceID, rbbSubVPI AtmVpIdentifier, rbbSubVCI AtmVcIdentifier, rbbSubAddr AtmAddr, rbbSubStatus RBBServiceStatus, rbbSubRowInfo RowStatus } rbbSubVendor OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The Vendor part of the index that uniquely identifies this CPE" ::= { rbbSubEntry 1 } rbbSubModel OBJECT-TYPE SYNTAX RBBVendorModel MAX-ACCESS read-create STATUS current DESCRIPTION "The Model part of the index that uniquely identifies a CPE" ::= { rbbSubEntry 3 } rbbSubSerialNumber OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-create STATUS current DESCRIPTION "The serial number part of the index that uniquely identifies a CPE" ::= { rbbSubEntry 4 } rbbSubServiceIdentifier OBJECT-TYPE SYNTAX RBBServiceID Turner Expires April 21, 2000 [Page 21] Internet-Draft Model for Auto-Provisioning CPE October 1999 MAX-ACCESS read-create STATUS current DESCRIPTION "An Index value referring to an entry in the rbbServicesTable. This is the service-side in the customer/service subscription association." ::= { rbbSubEntry 5 } rbbSubVPI OBJECT-TYPE SYNTAX AtmVpIdentifier MAX-ACCESS read-create STATUS current DESCRIPTION "The virtual path identifier to be used in the establishment of a PVC to a particular service, if the service is PVC- based." ::= { rbbSubEntry 6 } rbbSubVCI OBJECT-TYPE SYNTAX AtmVcIdentifier MAX-ACCESS read-create STATUS current DESCRIPTION "The virtual circuit identifier to be used in the establishment of a PVC to a particular service, if the service is PVC-based." ::= { rbbSubEntry 7 } rbbSubAddr OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS read-create STATUS current DESCRIPTION "The end-system address to be used in the establishment of an SVC to a particular service, if the service is SVC-based." ::= { rbbSubEntry 8 } rbbSubStatus OBJECT-TYPE SYNTAX RBBServiceStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The current status of this subscription, currently defined as up, down, or suspended." ::= { rbbSubEntry 9 } rbbSubRowInfo OBJECT-TYPE SYNTAX RowStatus Turner Expires April 21, 2000 [Page 22] Internet-Draft Model for Auto-Provisioning CPE October 1999 MAX-ACCESS read-create STATUS current DESCRIPTION "" ::= { rbbSubEntry 10 } -- -- Broadband CPE Group -- rbbCPETable OBJECT-TYPE SYNTAX SEQUENCE OF RBBCPEEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a sequence of rows where each row describes a particular CPE that has identified itself to the management framework." ::= { rbbCPEGroup 1 } rbbCPEEntry OBJECT-TYPE SYNTAX RBBCPEEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object defines the individual rows in the CPE table (rbbCPETable)" INDEX { rbbVendorOID, rbbVendorModel, rbbCPESerialNumber } ::= { rbbCPETable 1} RBBCPEEntry ::= SEQUENCE { rbbCPEAuthValue RBBCPEAuthType, rbbCPEVendorOID OBJECT IDENTIFIER, rbbCPEVendorModel RBBVendorModel, rbbCPEStatus INTEGER, rbbCPESubCount INTEGER, rbbCPESubAggrSpeed INTEGER, rbbCPECustContact RBBMailAddr, rbbCPESerialNumber RBBCPESerialNumber, rbbCPETrapEnable INTEGER, rbbCPECurrentImage RBBURLType, rbbCPEIpAddress IpAddress, rbbCPERowInfo RowStatus } rbbCPEAuthValue OBJECT-TYPE SYNTAX RBBCPEAuthType MAX-ACCESS read-create Turner Expires April 21, 2000 [Page 23] Internet-Draft Model for Auto-Provisioning CPE October 1999 STATUS current DESCRIPTION "A unique identifier that uniquely identifies a particular customer or end-user" ::= { rbbCPEEntry 1 } rbbCPEVendorOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "A unique object identifier that identifies a particular CPE vendor" ::= { rbbCPEEntry 2 } rbbCPEVendorModel OBJECT-TYPE SYNTAX RBBVendorModel MAX-ACCESS read-create STATUS current DESCRIPTION "" ::= { rbbCPEEntry 3 } rbbCPEStatus OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-create STATUS current DESCRIPTION "An integer enumeration that identifies the current status of the CPE device" ::= { rbbCPEEntry 4 } rbbCPESubCount OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-create STATUS current DESCRIPTION "An integer value representing the number of service subscriptions that exist in the subscription table for this customer" ::= { rbbCPEEntry 5 } rbbCPESubAggrSpeed OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-create STATUS current DESCRIPTION "The total aggregate bandwidth required by all active subscriptions for this CPE customer." Turner Expires April 21, 2000 [Page 24] Internet-Draft Model for Auto-Provisioning CPE October 1999 ::= { rbbCPEEntry 6 } rbbCPECustContact OBJECT-TYPE SYNTAX RBBMailAddr MAX-ACCESS read-create STATUS current DESCRIPTION "The email address for the individual at the customer premises that is responsible for the broadband service." ::= { rbbCPEEntry 7 } rbbCPESerialNumber OBJECT-TYPE SYNTAX RBBCPESerialNumber MAX-ACCESS read-create STATUS current DESCRIPTION "The unique hardware address or serial number associated with the CPE" ::= { rbbCPEEntry 8 } rbbCPETrapEnable OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-create STATUS current DESCRIPTION "A boolean value representing whether or not service-related traps are enabled or disabled for this CPE device." ::= { rbbCPEEntry 9 } rbbCPECurrentImage OBJECT-TYPE SYNTAX RBBURLType MAX-ACCESS read-create STATUS current DESCRIPTION "A URL string pointing to the current image that is installed in this particular CPE/customer site" ::= { rbbCPEEntry 10 } rbbCPEIpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "" ::= { rbbCPEEntry 11 } rbbCPERowInfo OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create Turner Expires April 21, 2000 [Page 25] Internet-Draft Model for Auto-Provisioning CPE October 1999 STATUS current DESCRIPTION "" ::= { rbbCPEEntry 12 } -- -- Vendor Group -- rbbVendorTable OBJECT-TYPE SYNTAX SEQUENCE OF RBBVendorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Vendor table describing types of CPE supported, and associated CPE management details." ::= { rbbVendorGroup 1 } rbbVendorEntry OBJECT-TYPE SYNTAX RBBVendorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each row describes a particular vendor model of CPE" INDEX { rbbVendorOID, rbbVendorModel } ::= { rbbVendorTable 1 } RBBVendorEntry ::= SEQUENCE { rbbVendorOID OBJECT IDENTIFIER, rbbVendorModel RBBVendorModel, rbbVendorImageURL RBBURLType, rbbVendorRowInfo RowStatus } rbbVendorOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "A unique object identifier value associated with a particular vendor of CPE" ::= { rbbVendorEntry 1 } rbbVendorModel OBJECT-TYPE SYNTAX RBBVendorModel MAX-ACCESS read-create STATUS current DESCRIPTION Turner Expires April 21, 2000 [Page 26] Internet-Draft Model for Auto-Provisioning CPE October 1999 "A human-readable string representing the model number for a particular vendor's CPE device" ::= { rbbVendorEntry 2 } rbbVendorImageURL OBJECT-TYPE SYNTAX RBBURLType MAX-ACCESS read-create STATUS current DESCRIPTION "A URL string representing the most current version of firmware available for this CPE model" ::= { rbbVendorEntry 3 } rbbVendorRowInfo OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "" ::= { rbbVendorEntry 4 } -- -- MIB Serial numbers. These serial numbers are incremented each time a change is made to one -- of the MIB groups. CPE devices can monitor these values to determine whether or not the CPE -- needs to re-synchronize its' provisioning information. There is one serial number for each -- group. -- rbbSrvGrpSerialNumber OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "" ::= { rbbProvMIBObjects 5 } rbbSubGrpSerialNumber OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "" ::= { rbbProvMIBObjects 6 } rbbCPEGrpSerialNumber OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION Turner Expires April 21, 2000 [Page 27] Internet-Draft Model for Auto-Provisioning CPE October 1999 "" ::= { rbbProvMIBObjects 7 } rbbVendorGrpSerialNumber OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "" ::= { rbbProvMIBObjects 8 } rbbSubNotify NOTIFICATION-TYPE OBJECTS { rbbSubVendor, rbbSubModel, rbbSubSerialNumber, rbbSubServiceIdentifier } STATUS current DESCRIPTION "This notification indicates that a new subscription has been added to, or when a subscription has been deleted from the rbbSubTable in the rbbSubGroup. The notification includes which specific index was added so that the manager does not have to implement a search for changes." ::= { rbbNotifyGroup 1 } rbbPowerUpNotify NOTIFICATION-TYPE OBJECTS { rbbCPEVendorOID, rbbCPEVendorModel, rbbCPESerialNumber } STATUS current DESCRIPTION "" ::= { rbbNotifyGroup 2 } END Turner Expires April 21, 2000 [Page 28] Internet-Draft Model for Auto-Provisioning CPE October 1999 Full Copyright Statement Copyright (C) The Internet Society (1999). 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 implmentation 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. Acknowledgement Funding for the RFC editor function is currently provided by the Internet Society. Turner Expires April 21, 2000 [Page 29]