6bed4: Peer-to-Peer IPv6 on Any Internetwork

Document Type Expired Internet-Draft (individual)
Last updated 2017-08-30 (latest revision 2017-02-26)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html 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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The purpose of 6bed4 is to support IPv6-only applications, even on IPv4-only networks. A specific and new [RFC7059] area of concern is that of peer-to-peer protocols such as SIP or file sharing during a chat session. Applications for such protocols are designed to run in arbitrary environments, which means that they can neither rely on native IPv6 for themselves, nor for their peers. The 6bed4 tunnel mechanism ensures that IPv6 can be assumed on all peers. This has a positive impact on the ability to initiate direct exchanges between such peers. The 6bed4 mechanism is meant as a fallback mechanism for IPv6 connectivity on networks that do not support it natively, by running a tunnel over UDP and IPv4. The IPv4 address is used to support traceability of the traffic originator, which means that no user account or other configuration is needed. The tunnel mechanism encapsulates IPv6 in UDP/IPv4 and builds on the existing IPv6 discovery mechanisms of Stateless Address Autoconfiguration [RFC4862] to setup an IPv6 address on a 6bed4 Peer, and of Neighbor Discovery [RFC4861] to verify if a direct route to a remote 6bed4 Peer is achievable.


Rick van Rein (rick@openfortress.nl)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)