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

Document Type Active Internet-Draft (individual)
Last updated 2017-02-26
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        R. Van Rein
Internet-Draft                                         OpenFortress B.V.
Intended status: Informational                         February 27, 2017
Expires: August 31, 2017

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

Abstract

   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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Van Rein                 Expires August 31, 2017                [Page 1]
Internet-Draft                    6bed4                    February 2017

   This Internet-Draft will expire on August 31, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Wire Format of 6bed4 Frames . . . . . . . . . . . . . . . . .   5
   3.  6bed4-Prefixed Address Format . . . . . . . . . . . . . . . .   6
     3.1.  Invitations for Direct Connections  . . . . . . . . . . .   8
     3.2.  Interpretation of EUI-64 flag bits  . . . . . . . . . . .   8
   4.  6bed4 Infrastructure and Protocol Overview  . . . . . . . . .   9
   5.  NAT and Firewall Traversal  . . . . . . . . . . . . . . . . .  11
   6.  Filtering 6bed4 Traffic . . . . . . . . . . . . . . . . . . .  13
   7.  Routing 6bed4 Traffic . . . . . . . . . . . . . . . . . . . .  15
     7.1.  Network Endpoint Routing Options  . . . . . . . . . . . .  15
   8.  Opportunistic Peering . . . . . . . . . . . . . . . . . . . .  16
     8.1.  Abstract Framework for Direct Peering . . . . . . . . . .  16
     8.2.  Neighbor-Discovery-based Direct Peering . . . . . . . . .  17
     8.3.  Routing-based Direct Peering  . . . . . . . . . . . . . .  18
     8.4.  Invitation-based Direct Peering . . . . . . . . . . . . .  18
     8.5.  TCP-based Direct Peering  . . . . . . . . . . . . . . . .  18
     8.6.  SCTP-based Direct Peering . . . . . . . . . . . . . . . .  19
     8.7.  SIP-supported Direct Peering  . . . . . . . . . . . . . .  20
   9.  Support for Robust Header Compression . . . . . . . . . . . .  20
   10. Requirements for 6bed4 Infrastructure Components  . . . . . .  22
     10.1.  Requirements for 6bed4 Servers . . . . . . . . . . . . .  22
     10.2.  Requirements for 6bed4 Peers . . . . . . . . . . . . . .  23
   11. Implementation Considerations . . . . . . . . . . . . . . . .  25
Show full document text