datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

6bed4: Peer-to-Peer IPv6 on Any Internetwork
draft-vanrein-v6ops-6bed4-01

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-09-12 (latest revision 2012-03-11)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-vanrein-v6ops-6bed4

Abstract

The intention of 6bed4 is to support IPv6-only applications, even on IPv4-only networks. A specific area of concern is that of peer-to- peer protocols such as SIP or document exchange during a chat session. Such protocols are designed to run in any environment, which means that they cannot rely on IPv6 for themselves, or their peers. The 6bed4 tunnel mechanism ensures that IPv6 can be assumed on all peers, without a need to configure it explicitly. 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 builds on existing IPv6 mechanisms; it employs Stateless Address Autoconfiguration [RFC4862] to setup an IPv6 address on a 6bed4 Peer, and Neighbor Discovery [RFC4861] to find the most direct route to a remote 6bed4 Peer.

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)