Re: Prefix Delegation and hosts

joel jaeggli <joelja@bogus.com> Thu, 20 July 2017 11:55 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD15131C24 for <ipv6@ietfa.amsl.com>; Thu, 20 Jul 2017 04:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 KHxWokoQVRKx for <ipv6@ietfa.amsl.com>; Thu, 20 Jul 2017 04:55:12 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 45277131C17 for <ipv6@ietf.org>; Thu, 20 Jul 2017 04:55:10 -0700 (PDT)
Received: from mb.local ([IPv6:2001:67c:370:1998:2c41:3f29:8c4c:2b37]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v6KBt5Ew010707 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 20 Jul 2017 11:55:08 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2001:67c:370:1998:2c41:3f29:8c4c:2b37] claimed to be mb.local
Subject: Re: Prefix Delegation and hosts
To: Lorenzo Colitti <lorenzo@google.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
References: <382f4a7bed6d48bbb7156c74bad716d9@XCH15-06-08.nw.nos.boeing.com> <13f89708-ad07-4af6-c21c-76803dafba57@gmail.com> <CAKD1Yr39pYtw7A7z8Zixzvdky3v7Cy7f1fLfXi2+cKBP3aX1Lg@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <87915a3e-52a3-2fc4-6670-9cb2e2c89aed@bogus.com>
Date: Thu, 20 Jul 2017 13:55:04 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Thunderbird/55.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr39pYtw7A7z8Zixzvdky3v7Cy7f1fLfXi2+cKBP3aX1Lg@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="IxfoNow634P6AQBkxChMqeD3qfd9AfdA4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gGyZuF0SrDDf5_kEr7Yt3zJuUzI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 11:55:30 -0000

On 7/20/17 13:45, Lorenzo Colitti wrote:
> On Thu, Jul 20, 2017 at 4:37 AM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     If it gets a /64 and
>     and chooses to use DHCPv6-PD to hand out /80s to its friends, nobody
>     upstream will know (or care). Of course, SLAAC won't work for the
>     friends,
>     but nobody upstream will know that either. (It should be a small matter
>     of coding to make SLAAC work with 48 bit IIDs, so I've no doubt that
>     will show up in running code sometime.)
> 
>  
> Why pick /80 instead of something more familiar such as /120? The
> requesting router can even assign prefixes based on RFC1918 IPv4 /24
> prefixes and IIDs based on the late 8 bits of the IPv4 address. Skip a
> few steps in the race to the bottom.

Presumably if your goal is to allow downstream devices to futher segment
you will assign the shortest prefixes you can get away with in your
model. if your goal is micro-segmentation of things like for example for
containers or VMs, you'll probably assign as long as you can get away
with e.g. /126 /127 /128  which can be littered all over the address
space if you're so inclined.

> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list 
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>