"This document specifies the functionality offered by an Access Provider (AP) that, when combined with an Ethernet Access (E-Access) Service, allows a Service Provider (SP) to monitor and configure selected objects associated with a given UNI and one or more OVC End Points at that UNI in the AP’s network. The effect is that the AP provides functionality similar to what would otherwise require the SP to place a Network Interface Device (NID) at the customer’s location. Hence, the AP is said to be providing “virtual NID (vNID)” functionality to the E-Access Service that the SP has purchased. This is accomplished via the SP communicating over a Remote Management Interface (RMI) Connection to the AP, using an RMI Protocol.
The content of this document can be divided into two types.
Requirements on the AP network: There are behaviors required across UNI and ENNI interfaces. This is the focus of this document; to define a known, standard service that SPs can buy from APs that provide access service having vNID functionality.
Functionality of the SP network: SP functions will be discussed as information to provide guidance for vendors and suppliers in an informational appendix (see Section Appendix B).
The above imply requirements for devices that provide the needed functionality. This document does not specify which device must implement which functions.
In addition, this document provides guidance, where necessary, on how the SP and AP should interact to configure and manage these capabilities. This framework is presented to explain the assumptions of what interactions between the SP and AP need to be supported via the RMI Protocol, and what interactions are assumed to be supported via the Service Order process."