6bed4: IPv6 Anywhere in support of Reliable Peering
draft-vanrein-6bed4-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Rick van Rein | ||
| Last updated | 2021-01-10 (latest revision 2020-07-09) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-vanrein-6bed4-04.txt
Abstract
The purpose of 6bed4 is to support IPv6-only networks, hosts and applications. It passes IPv6 frames over UDP between IPv4 sites. Peers connected over 6bed4 can switch to direct routes over UDP/IPv4 after deducing that this will be reliable. 6bed4 lets peer-to-peer applications benefit from transparant addressing in IPv6 and delegates NAPT concerns to 6bed4. It is possible to use 6bed4 as a fallback for IPv6, or as an additional route. Servers can be setup as IPv6-only servers with NAT64 for IPv4-only customers who only need client-server facilities, and add a 6bed4router to also facilitate reliable peer-to-peer protocols.
Authors
Rick van Rein (rick@openfortress.nl)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)