[Softwires] draft-despres-softwire-sam-01

Rémi Després <remi.despres@free.fr> Fri, 16 July 2010 14:07 UTC

Return-Path: <remi.despres@free.fr>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E241F3A6A2B for <softwires@core3.amsl.com>; Fri, 16 Jul 2010 07:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.251
X-Spam-Level: *
X-Spam-Status: No, score=1.251 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, J_CHICKENPOX_31=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEA3RNlo2J4a for <softwires@core3.amsl.com>; Fri, 16 Jul 2010 07:07:20 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.11]) by core3.amsl.com (Postfix) with ESMTP id B789C3A69D2 for <softwires@ietf.org>; Fri, 16 Jul 2010 07:07:19 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2206.sfr.fr (SMTP Server) with ESMTP id BDB5C70000A7 for <softwires@ietf.org>; Fri, 16 Jul 2010 16:07:30 +0200 (CEST)
Received: from [192.168.1.29] (unknown [89.170.204.182]) by msfrf2206.sfr.fr (SMTP Server) with ESMTP id 7E9C67000091 for <softwires@ietf.org>; Fri, 16 Jul 2010 16:07:30 +0200 (CEST)
X-SFR-UUID: 20100716140730518.7E9C67000091@msfrf2206.sfr.fr
From: Rémi Després <remi.despres@free.fr>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 16 Jul 2010 16:07:29 +0200
Message-Id: <C061DC98-18F5-41ED-808E-BF495BA8CB38@free.fr>
To: Softwires <softwires@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [Softwires] draft-despres-softwire-sam-01
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 14:07:21 -0000

Hi,

draft-despres-softwire-sam-01 has been posted.
 
No time slot is planned at this IETF meeting to present it, but:
- Questions and comments are welcome at any time 
- It is in part a complement to draft-despres-softwire-6rdplus-00 for which a time slot is expected.

Regards, 
RD



Abstract:

Stateless Address Mapping (SAM) is a generic mechanism to statelessly
establish tunnels, point-to-multipoint, for packets of an address
family that traverse domains whose routing is in another address
family (mesh softwires).  It extends tunneling principles of [6rd] to
other address-family combination than IPv6 across IPv4 domains.  It
thus introduces, for a variety of use cases, a simpler mesh-softwire
model than that of [RFC5565].

Among SAM use cases, some are solutions to previously unsolved
problems: native IPv6 across IPv4 NATs, with optimized paths;
multihoming with independent CPEs and provider-aggregatable prefixes;
public IPv4 addresses across IPv6-only domains with optimized paths;
static sharing of IPv4 addresses, without impact on routing
information bases.

Table of Contents:

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  The SAM model  . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
     2.2.  C-SAM and P-SAM Parameters -  Mapping Rules  . . . . . . .  6
     2.3.  Encapsulation and Fragmentation Considerations . . . . . .  7
     2.4.  Port sets of IPv4E prefixes  . . . . . . . . . . . . . . .  8
     2.5.  Acquisition of Parameters by P-SAMs and C-SAMs . . . . . .  9
   3.  Use-Case examples  . . . . . . . . . . . . . . . . . . . . . .  9
     3.1.  Native IPv6 across NAT44 CPEs (6rd+) . . . . . . . . . . .  9
     3.2.  Public IPv4 addresses and IPv4E prefixes across
           IPv6-only Domains (4rd)  . . . . . . . . . . . . . . . . . 10
     3.3.  Multihoming and Renumbering with PA Prefixes . . . . . . . 12
     3.4.  An Experiment at Telecom Bretagne  . . . . . . . . . . . . 13
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 16
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 17
   6.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 18
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 18
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 18
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20