IETF Logo Mail Archive

Re: [v6ops] I-D Action: draft-ietf-v6ops-ula-usage-recommendations-02.txt

Gert Doering <gert@space.net> Thu, 20 February 2014 21:45 UTC

Return-Path: <gert@Space.Net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1AC1A02A5 for <v6ops@ietfa.amsl.com>; Thu, 20 Feb 2014 13:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jm-SA6BgNBxI for <v6ops@ietfa.amsl.com>; Thu, 20 Feb 2014 13:45:02 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) by ietfa.amsl.com (Postfix) with ESMTP id 115101A0150 for <v6ops@ietf.org>; Thu, 20 Feb 2014 13:45:01 -0800 (PST)
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 8513160AE9 for <v6ops@ietf.org>; Thu, 20 Feb 2014 22:44:56 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 4CE0560AE7 for <v6ops@ietf.org>; Thu, 20 Feb 2014 22:44:56 +0100 (CET)
Received: (qmail 47128 invoked by uid 1007); 20 Feb 2014 22:44:56 +0100
Date: Thu, 20 Feb 2014 22:44:56 +0100
From: Gert Doering <gert@space.net>
To: Lorenzo Colitti <lorenzo@google.com>
Message-ID: <20140220214456.GC75390@Space.Net>
References: <530242C3.4070108@bogus.com> <E91E49CA-7BA6-4DA3-B4F3-46BB0F25F8F1@delong.com> <5303CD3E.1010907@gmail.com> <m2a9dnr4vk.wl%randy@psg.com> <5304BAAF.60608@gmail.com> <53052B43.2070904@gmail.com> <CAKD1Yr2fyZ9FezX5dh=P-PiruiOqKBKO9f5hroD-CHDJS+ZMQQ@mail.gmail.com> <5305FFFD.5090708@foobar.org> <530606FB.9020707@umn.edu> <CAKD1Yr11Zs=zQsVeHyFexRYchsf6DazpGoK6n0NJvMRvpDyd9w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAKD1Yr11Zs=zQsVeHyFexRYchsf6DazpGoK6n0NJvMRvpDyd9w@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/hB5c79U-qMBtENpuJpL4pkPyEWI
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ula-usage-recommendations-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 21:45:05 -0000

Hi,

On Thu, Feb 20, 2014 at 11:58:14PM +0900, Lorenzo Colitti wrote:
> We don't know what the use cases for ULAs are, because nobody has actually
> used them in real deployments. 

I have.  To reach other people's RFC1918 IPv4 networks over VPNs...

We assign a /64 out of "our" ULA /48 to each VPN partner, and NAT64
the last 32 bits at our IPSEC gateway into IPv4.  So it really doesn't 
matter what they use inside their network, we can reach the full IPv4 
range in there, nicely isolated into a single collision free prefix on 
our side...

Now I agree that using ULAs as life support for IPv4 might not be the
*best* use case, but you were asking for "real deployment".

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

v2.23.0 | Report a Bug | By Email