RE: Updated IID length text

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 19 January 2017 22:04 UTC

Return-Path: <Fred.L.Templin@boeing.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 2CB10129632 for <ipv6@ietfa.amsl.com>; Thu, 19 Jan 2017 14:04:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 aj6uKsICZuan for <ipv6@ietfa.amsl.com>; Thu, 19 Jan 2017 14:04:12 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 8D3B712961F for <ipv6@ietf.org>; Thu, 19 Jan 2017 14:04:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v0JM4BvZ035034; Thu, 19 Jan 2017 15:04:12 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v0JM42Hj034885 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 19 Jan 2017 15:04:02 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 19 Jan 2017 14:04:01 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1178.000; Thu, 19 Jan 2017 14:04:01 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Updated IID length text
Thread-Topic: Updated IID length text
Thread-Index: AQHScp8Mid/NKuaNYkeeaZ/wu4YnU6FAWhGw
Date: Thu, 19 Jan 2017 22:04:01 +0000
Message-ID: <0af627fdc8a448e4a98d03e856ffe2fe@XCH15-06-08.nw.nos.boeing.com>
References: <148406593094.22166.2894840062954191477.idtracker@ietfa.amsl.com> <F6953234-3F85-4E28-9861-433ADD01A490@gmail.com> <m2wpdzhncn.wl-randy@psg.com> <82245ef2-cd34-9bd6-c04e-f262e285f983@gmail.com> <m2d1frhjfn.wl-randy@psg.com> <18e6e13c-e605-48ff-4906-2d5531624d64@gmail.com> <CAKD1Yr1cvZ8Y3+bHeML=Xwqr+YgDspZGnZi=jqQj4qe2kMc4zw@mail.gmail.com> <m2lguffnco.wl-randy@psg.com> <CAKD1Yr1TrTiPRdyutobmb_77XJ7guNzLrg=H_p7qi4BfQ8V=GA@mail.gmail.com> <m2d1frfm6m.wl-randy@psg.com> <CAKD1Yr2Njjd8_Mr+6TRFF6C5pdcX4yFgpFVyEkykDuytu2B8mg@mail.gmail.com> <2A5073777007277764473D78@PSB> <4596c3d4-a337-f08e-7909-f14270b7085f@gmail.com> <CAN-Dau06R3iYRpYLADhvHox4C9qdsJCuxFsJapRhOQcWT4qk_g@mail.gmail.com> <CAO42Z2weZcoHiBzN94QAQ9WGhWR16PmMMFNg=5YLmr_dhPjjpA@mail.gmail.com> <fcc7f136-b5da-527e-b495-5a2d7f7a3ce8@gmail.com> <CAKD1Yr2Y8yY5=E3VUNuJqPsxeEJ2AMJM2ShKyQhQJRiO7fq3HA@mail.gmail.com> <c1407e78-b1cc-65b6-fe5a-63688e08feb8@gmail.com> <1798bf13-b031-8ffc-78ea-7d01c4756dc9@gmail.com> <696433c7-e976-c334-1b67-edcf9ee45bcc@gmail.com>
In-Reply-To: <696433c7-e976-c334-1b67-edcf9ee45bcc@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/OEkRkt91Cqjh8zbF8m0iAesP9RQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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, 19 Jan 2017 22:04:17 -0000

Hi Alex,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> Sent: Thursday, January 19, 2017 1:57 PM
> To: ipv6@ietf.org
> Subject: Re: Updated IID length text
> 
> 
> 
> Le 19/01/2017 à 20:26, Brian E Carpenter a écrit :
> > On 19/01/2017 22:26, Alexandre Petrescu wrote: ...
> >> I do not agree with the part that says "IIDs are required be 64bit
> >> long".
> >
> > But they are, today. In the move to full Standard, we cannot actually
> > change that; we can only clarify the wording.
> >
> >> If IIDs are required to be 64bit long (even if only in the
> >> 000-prefixed space) then the network can not grow at the edges, at
> >> least not with SLAAC.
> >
> > That would be true if /64 prefixes were scarce. They are not.
> 
> The mobile network operators today make it look as if the /64
> prefixes were scarce.
> 
> Maybe they dont know these /64 are not scarce, or maybe they dont care
> about scarcity (just as it's not IPv4 scarcity making them deploy IPv6).
>   The end result is the same: end users get each a /64, i.e. one single
> subnet.
> 
> Spec-wise the IID len cant change, the Ethernet IID len cant change, the
> DHCPv6 PD is not deployed, the operators only give a /64 to end user...
> one is free to pick the reason, and again the end result is the same: no
> growth at the edge.

I have deployed DHCPv6 PD in my network, and use it all the time for
mobile devices.

Thanks - Fred

> The archi document is free to recognize reality.  If so, it should
> recognize it so in a paragraph: no growth at the edges.
> 
> Alex
> 
> > But that's why the proposed text is limited to currently allocated
> > unicast space - if we ever need to change this, it will be a new
> > tranche of unicast space. In any case, this is nothing to do with
> > progressing to full Standard.
> >
> > Brian
> >
> > --------------------------------------------------------------------
> >  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> > Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------