Re: [v6ops] ULA draft revision #2 Regarding isolated networks

sthaug@nethelp.no Wed, 28 May 2014 06:51 UTC

Return-Path: <sthaug@nethelp.no>
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 0FC621A037B for <v6ops@ietfa.amsl.com>; Tue, 27 May 2014 23:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 Hijx2r11Sr-5 for <v6ops@ietfa.amsl.com>; Tue, 27 May 2014 23:51:00 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 5F2D81A0372 for <v6ops@ietf.org>; Tue, 27 May 2014 23:50:58 -0700 (PDT)
Received: (qmail 14887 invoked from network); 28 May 2014 06:50:52 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 28 May 2014 06:50:52 -0000
Date: Wed, 28 May 2014 08:49:37 +0200
Message-Id: <20140528.084937.74738378.sthaug@nethelp.no>
To: randy@psg.com
From: sthaug@nethelp.no
In-Reply-To: <m2iooq4oqi.wl%randy@psg.com>
References: <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com> <5384937A.90409@foobar.org> <m2iooq4oqi.wl%randy@psg.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/nYi_8Z3_Co2E_m8K8_O13OIGN9c
Cc: v6ops@ietf.org
Subject: Re: [v6ops] ULA draft revision #2 Regarding isolated networks
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: Wed, 28 May 2014 06:51:02 -0000

> > or use NAT.  I'm not saying this in order to throw fuel on an existing
> > fire, but simply because this is the reality for many organisations in
> > the ipv4 world, and I see little reason why it will change for ipv6.
> > The IETF can make recommendations about whether it thinks this is a
> > good idea or not, but it is not productive to pretend that the
> > elephant isn't in the room.
> 
> so, bottom line here is, in its inimitable fashion, the ietf will push
> ULA and get NAT.  what a win!

IPv6 will get NAT no matter what the IETF does. Trying to reduce the
damage from NAT, for instance by having sensible rules for ULA, seems
like a good thing.

Steinar Haug, AS2116