Re: [v6ops] I-D Action: draft-colitti-v6ops-host-addr-availability-01.txt

Gert Doering <gert@space.net> Tue, 28 July 2015 15:16 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 35BF81AC42A for <v6ops@ietfa.amsl.com>; Tue, 28 Jul 2015 08:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 yB2ouTCoxc9o for <v6ops@ietfa.amsl.com>; Tue, 28 Jul 2015 08:16:19 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 0BA431AC446 for <v6ops@ietf.org>; Tue, 28 Jul 2015 08:16:18 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id C8C8F60758 for <v6ops@ietf.org>; Tue, 28 Jul 2015 17:16:16 +0200 (CEST)
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 8CFF660054 for <v6ops@ietf.org>; Tue, 28 Jul 2015 17:16:16 +0200 (CEST)
Received: (qmail 19738 invoked by uid 1007); 28 Jul 2015 17:16:16 +0200
Date: Tue, 28 Jul 2015 17:16:16 +0200
From: Gert Doering <gert@space.net>
To: Andrew ???? Yourtchenko <ayourtch@gmail.com>
Message-ID: <20150728151616.GG84167@Space.Net>
References: <55B1ED14.6030501@gmail.com> <m1ZIZ4w-0000CbC@stereo.hq.phicoh.net> <CAKD1Yr2z6T86gmQMPZwbgFB4mdt7=xWNuei5jaQg=vpG7-zLVg@mail.gmail.com> <m1ZJdjZ-0000CcC@stereo.hq.phicoh.net> <20150727091241.GL84167@Space.Net> <m1ZJfOr-0000CgC@stereo.hq.phicoh.net> <C9C3FBC4-44F3-45D2-B8C4-3725396E5D40@nominum.com> <CAPi140Mx96dBgeaCkrsDD+-J85OZDo5Di+gHTBiaGDzYK2us4w@mail.gmail.com> <20150728115944.GZ84167@Space.Net> <CAPi140PKh64L=nr96pv3dn7FO_Y9pW162YzBT8kZHSMsedGYtQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="bOC9TN0n4iVUZoxs"
Content-Disposition: inline
In-Reply-To: <CAPi140PKh64L=nr96pv3dn7FO_Y9pW162YzBT8kZHSMsedGYtQ@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/Xpw3iWgR3YGmwjKEV1hNurS_Rak>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-colitti-v6ops-host-addr-availability-01.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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 28 Jul 2015 15:16:21 -0000

Hi,

On Tue, Jul 28, 2015 at 03:58:04PM +0200, Andrew ????  Yourtchenko wrote:
> I did not look at it as a problem given that every mobile phone on
> IPv6 will already get a /64 per host, and the number of mobile phones
> is dramatically bigger than the number of fixed installations.

Bigger than then number of L2 *segments*, undoubtly.

But no way bigger than "the number of devices that could attach to
a L2 link" - as all these mobile phone also has wifi, so you have way
more devices that attach to "shared links".

Network structure is also way different - in mobile, all devices attach
to some sort of aggregation router (via 3G PDP tunnels etc) - while
in "classic" networking, you have a multitude of independent segments
that do not normally have aggregation infrastructure or provisioning
available.  Prefix mobility in a typical enterprise networks (where
you'd have enough devices in a L2 segment to start think about scaling)
isn't really there.

> But I pulled that assumption more or less out of my thumb, based on
> observed anecdata, so would be happy to be proven wrong.
> 
> If we say we want to absolutely avoid NAT, then something has to give,
> and I don't know which tradeoff is a better one, both can be argued
> for and against. I think we might need both.

If you want my opinion, I think DHCPv6-PD to single hosts (= not something
that does tethering) is not a reasonable approach.

If something does tethering, you need to decide what you're talking about,
"enterprise-ish", "mobile" or "homenet".  In mobile, DHCPv6-PD, or just
sharing the PDP /64.  In homenet, HNCP or DHCPv6-PD.  In the enterprise?  
No idea what can be implemented with the typical constraints on 
trackability, security, etc.  (like: if the device attaches to *this* 
network, it's permitted to go *there* by IP ACLs - whether or not this 
is a reasonable approach in itself anymore stands to be debated, but it 
will be with us for a long time).

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