Operational Concerns and Considerations for Routing Protocol Design -- Risk, Interference, and Fit (RIFT)
draft-ietf-grow-rift-01
Document | Type |
Expired Internet-Draft
(grow WG)
Expired & archived
|
|
---|---|---|---|
Author | David Meyer | ||
Last updated | 2004-02-05 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
The Risk, Interference, and Fit (RIFT) design team was formed to document the concerns and considerations surrounding the use of Internet routing protocols for functions not directly related to routing of IP packets within the Internet and IP networks. This document is the output of that activity.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)