Tunnel Endpoint Discovery
draft-fluhrer-ted-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Scott Fluhrer | ||
| Last updated | 2001-11-21 | ||
| 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-fluhrer-ted-00.txt
https://www.ietf.org/archive/id/draft-fluhrer-ted-00.txt
Abstract
The ISAKMP, IKE and IPSec DOI RFCs [RFC2408, RFC2409, RFC2407] specify how an IPSec tunnel is negotiated with an encrypting security gateway (peer), however, they do not specify how the initiator knows who the encrypting peer is. This document specifies a method where the initiator can find the appropriate peer, and also negotiate a mutually acceptable set of proxies.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)