6bed4: IPv6 Anywhere in support of Reliable Peering
draft-vanrein-6bed4-04

Document Type Active Internet-Draft (individual)
Last updated 2020-07-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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                              July 9, 2020
Expires: January 10, 2021

          6bed4: IPv6 Anywhere in support of Reliable Peering
                         draft-vanrein-6bed4-04

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.

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 https://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."

   This Internet-Draft will expire on January 10, 2021.

Copyright Notice

   Copyright (c) 2020 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
   (https://trustee.ietf.org/license-info) in effect on the date of

Van Rein                Expires January 10, 2021                [Page 1]
Internet-Draft                    6bed4                        July 2020

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Address Format  . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Protocol Description  . . . . . . . . . . . . . . . . . .   4
     2.3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  6bed4 Network Components  . . . . . . . . . . . . . . . . . .   6
     3.1.  IPv6 Address Validation . . . . . . . . . . . . . . . . .   6
     3.2.  Router Solicitation and Advertisement . . . . . . . . . .   6
     3.3.  Network Prefixes  . . . . . . . . . . . . . . . . . . . .   7
       3.3.1.  Native /64 Prefixes . . . . . . . . . . . . . . . . .   8
       3.3.2.  Locally Routed fc00::/7 Prefixes  . . . . . . . . . .   8
       3.3.3.  The 6bed4 fc64::/16 and TBD1::/32 Prefixes  . . . . .   9
   4.  The 6bed4peer Component . . . . . . . . . . . . . . . . . . .  10
     4.1.  6bed4peer Forwarding  . . . . . . . . . . . . . . . . . .  10
     4.2.  6bed4peer Filtering . . . . . . . . . . . . . . . . . . .  12
   5.  The 6bed4router Component . . . . . . . . . . . . . . . . . .  13
     5.1.  6bed4router Filtering . . . . . . . . . . . . . . . . . .  14
     5.2.  6bed4router Forwarding  . . . . . . . . . . . . . . . . .  15
     5.3.  Combining 6bed4peer and 6bed4router Functions . . . . . .  16
   6.  Peering Policies  . . . . . . . . . . . . . . . . . . . . . .  16
   7.  Reliable Peering  . . . . . . . . . . . . . . . . . . . . . .  19
     7.1.  Reliable 6bed4router Uplinks  . . . . . . . . . . . . . .  19
     7.2.  Probing for Direct Peering  . . . . . . . . . . . . . . .  20
     7.3.  Sending and Receiving the Seen Flag . . . . . . . . . . .  20
     7.4.  Peer NAPT State . . . . . . . . . . . . . . . . . . . . .  21
     7.5.  State/Timer Diagram . . . . . . . . . . . . . . . . . . .  22
     7.6.  Differentiation through Peering Policies  . . . . . . . .  23
     7.7.  Bindable Local Prefix . . . . . . . . . . . . . . . . . .  24
     7.8.  Benefiting from Adaptive Flags  . . . . . . . . . . . . .  25
   8.  Global Routing of TBD1::/32 . . . . . . . . . . . . . . . . .  26
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  26
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  27
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  28
Show full document text