Tunnel Endpoint Discovery Problem Statement
draft-yamamoto-tun-dis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Shu Yamamoto | ||
| Last updated | 2007-02-27 | ||
| 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
Tunnel Endpoint Discovery is an enhancement to the Softwire feature. Defining a dynamic tunnel endpoint map allows you to be able to dynamically determine a Tunnel Broker peer; however, only the receiving client has this ability. This document frets out the problem scope as well as the motivation for specifying such a feature within the Softwire protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)