Re: IPv6, was IPv10 (fwd)

Mark Andrews <marka@isc.org> Thu, 29 December 2016 23:59 UTC

Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C95C12987D for <ietf@ietfa.amsl.com>; Thu, 29 Dec 2016 15:59:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.001
X-Spam-Level:
X-Spam-Status: No, score=-10.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 q5zPELZy08LS for <ietf@ietfa.amsl.com>; Thu, 29 Dec 2016 15:59:49 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E5C0129555 for <ietf@ietf.org>; Thu, 29 Dec 2016 15:59:49 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 1FC323493C7; Thu, 29 Dec 2016 23:59:46 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 0B9C7160073; Thu, 29 Dec 2016 23:59:46 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id F0E3F16006B; Thu, 29 Dec 2016 23:59:45 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id b0ZiZAz5plRn; Thu, 29 Dec 2016 23:59:45 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 702AF16004F; Thu, 29 Dec 2016 23:59:45 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 943515E105E1; Fri, 30 Dec 2016 10:59:42 +1100 (EST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <alpine.OSX.2.11.1612291429570.37525@ary.qy> <930f3af3-09af-e3c5-f796-507047ab54a1@gmail.com>
Subject: Re: IPv6, was IPv10 (fwd)
In-reply-to: Your message of "Fri, 30 Dec 2016 08:54:40 +1300." <930f3af3-09af-e3c5-f796-507047ab54a1@gmail.com>
Date: Fri, 30 Dec 2016 10:59:42 +1100
Message-Id: <20161229235942.943515E105E1@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8pgMKw7OCl0hwxDqlX2hxYbYpb8>
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Dec 2016 23:59:51 -0000

In message <930f3af3-09af-e3c5-f796-507047ab54a1@gmail.com>om>, Brian E Carpenter writes:
> On 30/12/2016 08:30, John R Levine wrote:
> >>> I might be able to use ULAs but I have no idea how well ULAs actually work
> >>
> >> Exactly like any other global-scope IPv6 address. They just work. (I speak
> >> from experience.)
> > 
> > How do I tell my router that the ULAs on the home side of the router are 
> > different from ULAs on the cableco side?
> 
> Your ULAs are all in your ULA /48 prefix. I'm not clear why the cableco would
> be using ULAs, but if they do, those address will be in the cableco's ULA /48.
> No confusion is possible, and as a border router, it SHOULD drop outbound
> packets with source addresses in your ULA /48.

It should also be dropping incoming traffic from ULAs it is not
configured to pass.  That is the job of a border router.

> >> If you want static addresses on your servers, it's no different from any 
> >> other static address. But maybe I am not understanding your concern.
> > 
> > If I knew I had an address range that held still, I would use DHCPv6 and see 
> > how many of my devices handle it.  What happens if I have ULA addresses handed 
> > out by DHCPv6 and global addresses from SLAAC?  Do I have to turn off SLAAC?
> 
> In the router advertisements, the prefix information option for the ULA prefix
> would need its A flag turned off.
> 
> > (If this stuff is all written down somewhere, I would be thrilled to get 
> > the reference.)
> 
> This is more for v6ops or even ipv6-ops@lists.cluenet.de. To be honest I
> don't know if any of the IPv6 books covers this stuff in detail.
> 
>     Brian
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org