BT Requirements for MPLS-TP features
draft-jenkins-mpls-tp-bt-requirements-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Ben Niven-Jenkins , Simon Fiddian | ||
| Last updated | 2009-07-03 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-jenkins-mpls-tp-bt-requirements-00.txt
Abstract
This document outlines BT's requirements for MPLS-TP features based on our current thinking for how we may utilise functionality being defined as part of the MPLS-TP standardisation effort within our existing deployed MPLS networks. This document is not intended to describe all future requirements for MPLS-TP features, only for those features that we have a currently defined requirement for today and which we would like to see priority be given to them when specifying and standardising MPLS-TP within IETF. These features are required in order to enable us to enhance live, revenue generating services.
Authors
Ben Niven-Jenkins
Simon Fiddian
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)