BGP Assign AFI/SAFI numbers
draft-hares-bgp-assign-afisafi-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Susan Hares | ||
| Last updated | 2004-02-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 describes mechanisms for assigning the AFI/SAFI values for short-term use while BGP specifications are under development. These short-term AFI/SAFI values will be assigned for temporary use to a particular enterprise while BGP specifications are under development. After 1 year, if the BGP specification has been adopted as an IDR draft, the lease will be renewed. If the draft has not be adopted, the AFI/SAFI value returns to the pool of Enterprise AFI/SAFI. This draft a means to assign these short- term AFI/SAFI values.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)