Loose End Message Routing Method for NATFW NSLP
draft-stiemerling-nsis-natfw-mrm-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Stiemerling | ||
| Last updated | 2005-07-19 | ||
| 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 memo describes the use cases and solution for a new NTLP message routing method (MRM) that is used by the NATFW NSLP protocol to locate Network Address Translators (NAT) on the upstream data path. This message routing method is used by NSIS NATFW nodes behind a NAT to allocate a public reachable IP address and/or port number. The current way to do so has been named as "signaling the wrong way" and should be replaced by the proposed message routing method. The scope of this memo is limited to the usage of locating upstream Network Address Translator.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)