Requirements on the ASON UNI
draft-lin-mpls-ipo-ason-uni-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Zhi Lin | ||
| Last updated | 2000-11-17 | ||
| 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
Work already done on the automatic switched optical network (ASON) has identified several requirements and architectural features. In particular several interfaces have been identified, however there are no detailed requirements for these interfaces. This document presents our understanding of requirements from the point of view of what an ASON customer can be expected to do with ASON. These are mainly requirements at the Client Application Programming Interface (API). Note that the Client API is the logical interface between a network client (user domain) and the network server (service provider domain).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)