Additional functions for OSPFv2 extensions for ASON routing
draft-theillaud-gmpls-ason-routing-add-fcts-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Remi Theillaud , Lyndon Ong | ||
| Last updated | 2009-10-26 | ||
| 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
[OSPF-ASON] defines OSPFv2 extensions to fulfill the requirements defined in [RFC4258]. In OIF discussion of ASON routing, OIF members have noted that some additional functionality beyond that defined in [OSPF-ASON] would be useful for deployment of ASON routing by OIF carriers. The purpose of this document is to list such additional functionalities, so that CCAMP experts study whether such functionalities can be fulfilled by existing GMPLS mechanisms, or whether extensions to [OSPF-ASON] are required. Some proposals for potential extensions are provided for review by IETF CCAMP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)