SPAN-A - Candidate A for the Pre-Midcom SPAN Protocol
draft-cordell-midcom-span-a-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Peter Cordell | ||
| Last updated | 2002-06-26 | ||
| 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
SPAN-A (pronounced 'spanner') is a candidate for the pre-midcom SPAN protocol. The scope of SPAN (Simple Protocol for Augmenting NATs) is to enable protocols involving multiple associated sessions to operate across NATs. Such protocols typically use transport addresses to identify associated sessions. This works well for environments where end-to-end addressing is in force, but is broken by the introduction of NATs. SPAN is intended to operate with symmetric NATs by using a relay outside the NAT. It complements STUN [STUN] which operates with various kinds of cone NAT.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)