Evaluation of RSIP against MIDCOM requirements
draft-renkel-rsip-midcom-eval-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jim Renkel | ||
| Last updated | 2002-05-13 | ||
| 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 provides an evaluation of the RSIP (Realm Specific IP) framework and protocol against the evaluation criteria provided by the MIDCOM working group for the evaluation of middle box control protocols. RSIP is defined in experimental RFCs 3102 (Realm Specific IP: Framework) [3] and 3103 (Realm Specific IP: Protocol Specification) [4]; see also RFCs 3104 (RSIP Support for End-to-end IPsec) [5] and 3105 (Finding an RSIP Server with SLP) [6] for more information on RSIP. The document has been updated based on comments made on the MIDCOM mailing list since the previous version of this document was distributed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)