Definitions of Managed Objects for Open Provisioning Standard (OPS) in the Loop Access Environment
draft-anda-ops-mib-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ray Jamp , Yu-Jen Hsiao | ||
Last updated | 2000-10-11 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies an Open Provisioning Standard (OPS) that addresses the needs of an Integrated Communications Network (ICN) for remote and automatic service turn-up and for the simplification of monitoring and fault management across multiple network elements within the Loop Access environment and within the Customer Premises Environment (CPE) environment. OPS extends the standard Simple Network Management Protocol (SNMP) Management Information Base (MIB) by defining voice/data integration and flow-through provisioning capabilities for the various devices within the ICN, such as Integrated Access Devices (IADs). OPS enables Carriers or Service Providers to control their Integrated Access Services (IAS) from the network management system in the Network Operation Center (NOC). Flow-through provisioning allows administrators to send provisioning commands to multiple network elements across the ICN. The provisioning commands are used to define or modify a customer's services and to turn those services on and off. Similarly, customer-initiated service requests as well as performance and fault management information for existing services can flow back to the carrier or service provider.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)