Request to Move RFC1265 to Historic Status
draft-meyer-rfc1265-historic-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | David Meyer | ||
| Last updated | 2003-01-29 | ||
| 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) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-meyer-rfc1265-historic-00.txt
https://www.ietf.org/archive/id/draft-meyer-rfc1265-historic-00.txt
Abstract
RFC1265 [RFC1265], 'BGP protocol Analysis' documents how the requirements for advancing a routing protocl to Draft Standard have been satisfied by a BGP-3, a technology which is no longer commonly used. This document requests that RFC 1265 be moved to historic status.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)