
From nobody Wed Apr  1 01:28:15 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A73791A8A75 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 01:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 K1dARQ-AxVX8 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 01:28:12 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A3471A8A6A for <dhcwg@ietf.org>; Wed,  1 Apr 2015 01:28:11 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t318S9I7007381 for <dhcwg@ietf.org>; Wed, 1 Apr 2015 10:28:09 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 44440204313 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 10:29:03 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 329852043C1 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 10:29:03 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t318S77B017484 for <dhcwg@ietf.org>; Wed, 1 Apr 2015 10:28:09 +0200
Message-ID: <551BAC15.3020700@gmail.com>
Date: Wed, 01 Apr 2015 10:28:05 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com>
In-Reply-To: <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/LlR0Cc7tezKMpfPz_sFh98IpIfw>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 08:28:13 -0000

Le 01/04/2015 04:07, Ted Lemon a écrit :
> On Mar 31, 2015, at 8:42 PM, Lorenzo Colitti <lorenzo@google.com>
> wrote:
>> Addresses received via DHCPv6 do not have any associated
>> reachability information. In order avoid the problems described in
>> [RFC4943], hosts MUST NOT assume that any IPv6 addresses are
>> reachable on-link as a result of receiving an IA_NA or IA_TA; IPv6
>> addresses obtained from IA_NA or IA_TA MUST NOT be configured with
>> any prefix length except /128.
>
> This looks okay,

To me it does not look very much ok; it looks as an intention to tell to 
not use DHCPv6 to allocate addresses.

Why would a Client configure an unreachable /128 on its interface?

Alex


From nobody Wed Apr  1 03:58:21 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23F8A1A0275 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 03:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level: 
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_24=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=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 3ysZlgff-i7v for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 03:58:18 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 181091A026A for <dhcwg@ietf.org>; Wed,  1 Apr 2015 03:58:17 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 1DE781BC3E for <dhcwg@ietf.org>; Wed,  1 Apr 2015 10:58:13 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <551BAC15.3020700@gmail.com>
Date: Wed, 1 Apr 2015 11:58:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/wjWzol9tBGz8j6cH1ZpLAv1iqzA>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 10:58:20 -0000

On 1 Apr 2015, at 09:28, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:

> Le 01/04/2015 04:07, Ted Lemon a =E9crit :
>> On Mar 31, 2015, at 8:42 PM, Lorenzo Colitti <lorenzo@google.com>
>> wrote:
>>> Addresses received via DHCPv6 do not have any associated
>>> reachability information. In order avoid the problems described in
>>> [RFC4943], hosts MUST NOT assume that any IPv6 addresses are
>>> reachable on-link as a result of receiving an IA_NA or IA_TA; IPv6
>>> addresses obtained from IA_NA or IA_TA MUST NOT be configured with
>>> any prefix length except /128.
>>=20
>> This looks okay,

+1, looks clear, concise and not open to misinterpretation.


> To me it does not look very much ok; it looks as an intention to tell =
to not use DHCPv6 to allocate addresses.
>=20
> Why would a Client configure an unreachable /128 on its interface?

No and "it doesn't"

It looks like your problem is that you have not yet managed the jump in =
mindset from the IPv4 world (all IPs have an associated subnet, and =
IP+mask =3D=3D reachability information) to the IPv6 world where an =
address is an address<period>. I took me some time, and it was only =
after a similar discussion here that the penny dropped for me. IMO =
that's part of the adoption problem - lots of people have become =
"familiar" (even if not technically competent !) with IPv4, and the jump =
to IPv6 isn't just a matter of adding a few bits to the address.


In the IPv4 world, you get an address and subnet mask. =46rom that you =
work out the range of addresses in the same subnet, and from that you =
infer reachability information. Ie (in the absence of further =
configuration), if the address is in the same subnet you infer "on link" =
and do local discovery (ARP), if the address isn't in the same subnet =
you infer "not local" and send the packet via a router.


In the IPv6 world it's somewhat different.
You get one or more addresses by various means - self assigned link =
local, self assigned from range in advertised prefix  from a router, =
assigned by DHCP, manually configured. Specifically, the address(es) you =
have should not (apart from the link local etc prefixes) be used to =
infer reachability of other devices).
=46rom separate sources, you get one or more prefixes that are active on =
your network. Note that for example, you could get a number of prefixes =
from more than one router - eg you have two routers, two internet =
services, two prefixes.
When you want to send a packet, the only consideration (over =
simplification, but go with it) is "is the other device on the local =
link ?" You answer that by the simple question : is the destination IP =
within one of the prefixes I've been told is on this link (and I'm =
allowed to use ND to find) ? If the answer is yes then you can use ND to =
find the other device - it does not matter one jot whether the IP =
address you decide to use is a /128, a /64, or something else. I assume =
(I'm no expert) that if A can talk to B using ND to locate it, then that =
infers that B is allowed to use the fact that A directly contacted it to =
infer that A is directly contactable - I'll leave that for one of the =
experts to clarify.

As I was corrected earlier, the RA may indicate that a prefix is not to =
be treated as "on link". It may well be that the network doesn't support =
device-device communications directly - access networks (eg ADSL) come =
to mind where each user has a point-point link back to the central hub =
and ND may not be supported to find other nodes on other links. Thus =
using "address + mask" to infer direct reachability is just wrong.


From nobody Wed Apr  1 04:20:32 2015
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E80B51A1A54 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 04:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_24=0.6, SPF_PASS=-0.001] autolearn=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 4n9df10ypr9I for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 04:20:29 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 154891A1A43 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 04:20:29 -0700 (PDT)
Received: by qgfa8 with SMTP id a8so39048679qgf.0 for <dhcwg@ietf.org>; Wed, 01 Apr 2015 04:20:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:mime-version:subject :message-id:date:references:in-reply-to:to; bh=FTqmJsPlYOweM+1a0oAJsMMCEO9Gu2CtMl3Xt1WYafY=; b=B1a08CWIaumU8Dt/Tmrz18WFRHGwDDBQjyM4YuYtVq53NXEv1xRDiYp/Fl7y5PXhlF rrxDPxEBjvjbbZIoGspgq5r+PnyjBwQ7tFlhl2SgL/eKUxFKWpdE/gJMa9I2WqeX4CPR m2hoSm+QPq1YgRM6jWMzdhRKgGY8MeB7lN2h1/BtSuQiakI8ZsiwvXn2e/qAio6NPH7f UX9klv5GLOxDkXNDCXiknvHWWEkUts6vBRIOyh1jssbgVyT+YCi6E0DO5B9opa07NUIo B57NxyJA6eg/i1Fa9YnFEiFFs455djggeYaQM1YmRALVlgznnR2+rbmdB4kp2QKQzZc5 MwTg==
X-Received: by 10.55.55.12 with SMTP id e12mr90131754qka.50.1427887228329; Wed, 01 Apr 2015 04:20:28 -0700 (PDT)
Received: from [10.86.254.234] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id w130sm1027083qha.25.2015.04.01.04.20.27 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 04:20:27 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Message-Id: <84C5FC49-3E7B-4A86-A33D-63FDB68553B3@gmail.com>
Date: Wed, 1 Apr 2015 07:20:26 -0400
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk>
In-Reply-To: <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: iPad Mail (12D508)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/YVwwbxs8dpSrExQ_8V61oQydS4A>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 11:20:31 -0000

> On Apr 1, 2015, at 6:58 AM, Simon Hobson <linux@thehobsons.co.uk> wrote:
>=20
>=20
>> On 1 Apr 2015, at 09:28, Alexandru Petrescu <alexandru.petrescu@gmail.com=
> wrote:
>>=20
>> Le 01/04/2015 04:07, Ted Lemon a =C3=A9crit :
>>> On Mar 31, 2015, at 8:42 PM, Lorenzo Colitti <lorenzo@google.com>
>>> wrote:
>>>> Addresses received via DHCPv6 do not have any associated
>>>> reachability information. In order avoid the problems described in
>>>> [RFC4943], hosts MUST NOT assume that any IPv6 addresses are
>>>> reachable on-link as a result of receiving an IA_NA or IA_TA; IPv6
>>>> addresses obtained from IA_NA or IA_TA MUST NOT be configured with
>>>> any prefix length except /128.
>>>=20
>>> This looks okay,
>=20
> +1, looks clear, concise and not open to misinterpretation.

In my opinion, "IPv6 addresses obtained from IA_NA or IA_TA MUST NOT be conf=
igured with any prefix length except /128." Is unnecessary and should be eli=
ded (see below)

>> To me it does not look very much ok; it looks as an intention to tell to n=
ot use DHCPv6 to allocate addresses.
>>=20
>> Why would a Client configure an unreachable /128 on its interface?
>=20
> No and "it doesn't"
>=20
> It looks like your problem is that you have not yet managed the jump in mi=
ndset from the IPv4 world (all IPs have an associated subnet, and IP+mask =3D=
=3D reachability information) to the IPv6 world where an address is an addre=
ss<period>. I took me some time, and it was only after a similar discussion h=
ere that the penny dropped for me. IMO that's part of the adoption problem -=
 lots of people have become "familiar" (even if not technically competent !)=
 with IPv4, and the jump to IPv6 isn't just a matter of adding a few bits to=
 the address.

Seems to me those words I suggest should be dropped encourage this linkage b=
etween an IPv6 address and a prefix length.  As Simon points out, The concep=
t of configuring an address with a prefix length is a holdover from IPv4 and=
 this text should not perpetuate the misconception.

We've been around this discussion before, and I understand some operating sy=
stem CLIs incorrectly require a prefix length when an IPv6 address is config=
ured.  It may even be the case that some stacks associate a prefix length wi=
th an assigned address rather than keeping reach ability separate from addre=
ss assignment.  If text about prefix length with an assigned address is incl=
uded in the text, additional words explaining this critical detail should be=
 included.

- Ralph


> In the IPv4 world, you get an address and subnet mask. =46rom that you wor=
k out the range of addresses in the same subnet, and from that you infer rea=
chability information. Ie (in the absence of further configuration), if the a=
ddress is in the same subnet you infer "on link" and do local discovery (ARP=
), if the address isn't in the same subnet you infer "not local" and send th=
e packet via a router.
>=20
>=20
> In the IPv6 world it's somewhat different.
> You get one or more addresses by various means - self assigned link local,=
 self assigned from range in advertised prefix  from a router, assigned by D=
HCP, manually configured. Specifically, the address(es) you have should not (=
apart from the link local etc prefixes) be used to infer reachability of oth=
er devices).
> =46rom separate sources, you get one or more prefixes that are active on y=
our network. Note that for example, you could get a number of prefixes from m=
ore than one router - eg you have two routers, two internet services, two pr=
efixes.
> When you want to send a packet, the only consideration (over simplificatio=
n, but go with it) is "is the other device on the local link ?" You answer t=
hat by the simple question : is the destination IP within one of the prefixe=
s I've been told is on this link (and I'm allowed to use ND to find) ? If th=
e answer is yes then you can use ND to find the other device - it does not m=
atter one jot whether the IP address you decide to use is a /128, a /64, or s=
omething else. I assume (I'm no expert) that if A can talk to B using ND to l=
ocate it, then that infers that B is allowed to use the fact that A directly=
 contacted it to infer that A is directly contactable - I'll leave that for o=
ne of the experts to clarify.
>=20
> As I was corrected earlier, the RA may indicate that a prefix is not to be=
 treated as "on link". It may well be that the network doesn't support devic=
e-device communications directly - access networks (eg ADSL) come to mind wh=
ere each user has a point-point link back to the central hub and ND may not b=
e supported to find other nodes on other links. Thus using "address + mask" t=
o infer direct reachability is just wrong.
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Wed Apr  1 04:29:03 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E701A1B3F for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 04:29:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.383
X-Spam-Level: 
X-Spam-Status: No, score=-4.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, J_CHICKENPOX_24=0.6, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 VdhMMyT_jiXd for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 04:29:00 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F31331A1A6B for <dhcwg@ietf.org>; Wed,  1 Apr 2015 04:28:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t31BSvD7029835 for <dhcwg@ietf.org>; Wed, 1 Apr 2015 13:28:57 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 64213204663 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 13:29:51 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 5B3902042BE for <dhcwg@ietf.org>; Wed,  1 Apr 2015 13:29:51 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t31BSqGQ018822 for <dhcwg@ietf.org>; Wed, 1 Apr 2015 13:28:57 +0200
Message-ID: <551BD674.1040301@gmail.com>
Date: Wed, 01 Apr 2015 13:28:52 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk>
In-Reply-To: <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/0QgeqLk3eVzu_81IYXNSEUpa3zI>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 11:29:02 -0000

Simon,

Reading you I think I misunderstood what is meant by 'reachable' and
'unreachable'.  You seem to imply that 'reachable' is a neighbor,
whereas I think 'reachable'  is from a neighbor or from the Internet
(like when we say that a 192. address is not reachable/contactable,
whereas a Globally Unique Address GUA _is_ reachable).

In that sense, maybe the text could be clarified to say: "Addresses
received via DHCPv6 are typically absent from the Neighbor Cache"
(instead of "not have reachability informnation".)

BTW, 'reachability' was absent last time I checked in a paper dictionary.

For clarification see below.

Alex

Le 01/04/2015 12:58, Simon Hobson a écrit :
>
> On 1 Apr 2015, at 09:28, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>
>> Le 01/04/2015 04:07, Ted Lemon a écrit :
>>> On Mar 31, 2015, at 8:42 PM, Lorenzo Colitti <lorenzo@google.com>
>>> wrote:
>>>> Addresses received via DHCPv6 do not have any associated
>>>> reachability information. In order avoid the problems
>>>> described in [RFC4943], hosts MUST NOT assume that any IPv6
>>>> addresses are reachable on-link as a result of receiving an
>>>> IA_NA or IA_TA; IPv6 addresses obtained from IA_NA or IA_TA
>>>> MUST NOT be configured with any prefix length except /128.
>>>
>>> This looks okay,
>
> +1, looks clear, concise and not open to misinterpretation.

To me it plainly negates any usefulness of DHCP-allocated addresses by
stating they are unreachable.

>> To me it does not look very much ok; it looks as an intention to
>> tell to not use DHCPv6 to allocate addresses.
>>
>> Why would a Client configure an unreachable /128 on its interface?
>
> No and "it doesn't"
>
> It looks like your problem is that you have not yet managed the jump
> in mindset from the IPv4 world (all IPs have an associated subnet,
> and IP+mask == reachability information) to the IPv6 world where an
> address is an address<period>.
>
> I took me some time, and it was only after a similar discussion here
>  that the penny dropped for me. IMO that's part of the adoption
> problem - lots of people have become "familiar" (even if not
> technically competent !) with IPv4, and the jump to IPv6 isn't just a
> matter of adding a few bits to the address.

That is a fault in the IPv6 specification, not in the IPv4-skilled'
thoughts.

Ideally they were perfectly similiar modulo the 96 bits.

> In the IPv4 world, you get an address and subnet mask. From that you
> work out the range of addresses in the same subnet, and from that you
> infer reachability information.

So that is meant by 'reachability'?  The neighbor reachability?  I
thought it is Internet reachability.

> Ie (in the absence of further configuration), if the address is in
> the same subnet you infer "on link" and do local discovery (ARP), if
> the address isn't in the same subnet you infer "not local" and send
> the packet via a router.

So that is also 'reachable', but not neighbor.

> In the IPv6 world it's somewhat different. You get one or more
> addresses by various means - self assigned link local, self assigned
> from range in advertised prefix  from a router, assigned by DHCP,
> manually configured. Specifically, the address(es) you have should
> not (apart from the link local etc prefixes) be used to infer
> reachability of other devices).

This is again neighbor-reachability (not Internet reachability) right?

>> From separate sources, you get one or more prefixes that are
>> active on your network. Note that for example, you could get a
>> number of prefixes from more than one router - eg you have two
>> routers, two internet services, two prefixes.
>
> When you want to send a packet, the only consideration (over
> simplification, but go with it) is "is the other device on the local
> link ?" You answer that by the simple question : is the destination
> IP within one of the prefixes I've been told is on this link (and I'm
> allowed to use ND to find) ? If the answer is yes then you can use ND
> to find the other device - it does not matter one jot whether the IP
> address you decide to use is a /128, a /64, or something

Distinction: ok for /64, but if it's a /128 then it wouldn't have
neighbors (/128 can only be on one end, and that something can't be a link).

On another hand, a /128 on an interface is ok as long as there is an
corresponding /128 in the routing tables.  There is reachability from
everyone who gets there through such routers: on the same Ethernet
("link"?) or across the Internet.  In this respect it's precisely like
with IPv4 /32s.

> else. I assume (I'm no expert) that if A can talk to B using ND to
> locate it, then that infers that B is allowed to use the fact that A
>  directly contacted it to infer that A is directly contactable - I'll
>  leave that for one of the experts to clarify.

SO this contactable would be the reachable we talk about.

> As I was corrected earlier, the RA may indicate that a prefix is not
> to be treated as "on link".

That is another artifact that is artificial.  Indeed RAs have this
on-link and off-link flag for a prefix, but it sounds unnatural.  If
it's not on a link then it's on a what.

> It may well be that the network doesn't support device-device
> communications directly - access networks (eg ADSL) come to mind
> where each user has a point-point link back to the central hub and
> ND may not be supported to find other nodes on other links. Thus
> using "address + mask" to infer direct reachability is just wrong.

So, one would not think an unreachable address is of any use at all. (be
its reachability inferred solely from address or from both address/mask)

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr  1 06:22:02 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B631A90CB for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 06:22:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 g58yzd2RMQPI for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 06:21:58 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 0589E1A90C4 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 06:21:56 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 8F4491BC3E for <dhcwg@ietf.org>; Wed,  1 Apr 2015 13:21:51 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <551BD674.1040301@gmail.com>
Date: Wed, 1 Apr 2015 14:21:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/YEYvOxiURcup7fu-W7aMHvClCKM>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 13:22:00 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> Reading you I think I misunderstood what is meant by 'reachable' and
> 'unreachable'.  You seem to imply that 'reachable' is a neighbor,
> whereas I think 'reachable'  is from a neighbor or from the Internet
> (like when we say that a 192. address is not reachable/contactable,
> whereas a Globally Unique Address GUA _is_ reachable).

You make a good point there. Yes, I've been using "reachable" as meaning =
"I can directly send a packet to that device".

>> I took me some time, and it was only after a similar discussion here
>> that the penny dropped for me. IMO that's part of the adoption
>> problem - lots of people have become "familiar" (even if not
>> technically competent !) with IPv4, and the jump to IPv6 isn't just a
>> matter of adding a few bits to the address.
>=20
> That is a fault in the IPv6 specification, not in the IPv4-skilled'
> thoughts.
>=20
> Ideally they were perfectly similiar modulo the 96 bits.

I disagree.
There are many things "wrong" in IPv4 - or at least very suboptimal. =
AIUI it was never intended to be used as it ended up being used when it =
was first defined. While it can certainly be argued that IPv6 is "too =
complicated", the decision was taken (rightly IMO) to take the =
transition as an opportunity to engineer a "new" protocol that takes =
into account the decades of experience - does some things "better", does =
some things "differently", and does a fair few things that were =
difficult before.

>> In the IPv4 world, you get an address and subnet mask. =46rom that =
you
>> work out the range of addresses in the same subnet, and from that you
>> infer reachability information.
>=20
> So that is meant by 'reachability'?  The neighbor reachability?  I
> thought it is Internet reachability.
>=20
>> Ie (in the absence of further configuration), if the address is in
>> the same subnet you infer "on link" and do local discovery (ARP), if
>> the address isn't in the same subnet you infer "not local" and send
>> the packet via a router.
>=20
> So that is also 'reachable', but not neighbor.

But it may well be a neighbour. It's not that uncommon to have multiple =
IPv4 subnets on one link. To handle this means either sending all =
inter-subnet traffic through a router, or configuring additional routing =
table entries on each device.

>> In the IPv6 world it's somewhat different. You get one or more
>> addresses by various means - self assigned link local, self assigned
>> from range in advertised prefix  from a router, assigned by DHCP,
>> manually configured. Specifically, the address(es) you have should
>> not (apart from the link local etc prefixes) be used to infer
>> reachability of other devices).
>=20
> This is again neighbor-reachability (not Internet reachability) right?

Yes

>>> =46rom separate sources, you get one or more prefixes that are
>>> active on your network. Note that for example, you could get a
>>> number of prefixes from more than one router - eg you have two
>>> routers, two internet services, two prefixes.
>>=20
>> When you want to send a packet, the only consideration (over
>> simplification, but go with it) is "is the other device on the local
>> link ?" You answer that by the simple question : is the destination
>> IP within one of the prefixes I've been told is on this link (and I'm
>> allowed to use ND to find) ? If the answer is yes then you can use ND
>> to find the other device - it does not matter one jot whether the IP
>> address you decide to use is a /128, a /64, or something
>=20
> Distinction: ok for /64, but if it's a /128 then it wouldn't have
> neighbors (/128 can only be on one end, and that something can't be a =
link).

NO You **CAN** have a "/128" and have neighbours. Well actually, the =
"/128" is an artificial construct required to work around the =
implementations which (incorrectly) require every address to have a =
subnet mask. If correctly implemented, you have "an address" (or =
multiple addresses, but lets just consider one for now).

Separately to any address(es) you have, you have a table of how to send =
packets to other addresses. Your own address does not have to be in that =
list.

It's been mentioned that one thread originated from a comment in some =
code along the lines of "what do I use for a prefix length - until =
someone comes up with something I'll use 64". That's an implementation =
issue - and I think it'll be a long time before the Linux world manages =
to unravel several decades of built in logic to separate addresses and =
prefixes/reachability information.

>> It may well be that the network doesn't support device-device
>> communications directly - access networks (eg ADSL) come to mind
>> where each user has a point-point link back to the central hub and
>> ND may not be supported to find other nodes on other links. Thus
>> using "address + mask" to infer direct reachability is just wrong.
>=20
> So, one would not think an unreachable address is of any use at all. =
(be
> its reachability inferred solely from address or from both =
address/mask)

You've probably highlighted the main issue - one of terminology, and I =
think I'm as guilty as anyone of being a bit sloppy. I *think* the =
terminology is "on-link" meaning you can directly communicate with that =
other device (use ND to find it's physical address, MAC in ethernet like =
networks), and "off-link" meaning that you cannot directly communicate =
with it and must go via a router.

It would probably help if one of the experts clarified this.

On an ethernet network, two devices with completely unrelated addresses =
may directly communicate as long as they have a means of finding out =
about each other. This is where the RA provided prefix lists (with their =
on-link flag) come in - by configuring the routing tables. Note that a =
prefix only needs one table entry, whether you have 1, 100, 100,000 =
addresses on the interface.

On the other hand, there are probably networks where the end-points all =
have addresses which are in the same prefix, but which cannot directly =
communicate end-point to end-point without going via the hub. Granted =
these probably all use a /64 prefix for each link, that's my experience =
so far in getting connected (via my ISPs trial, and currently via a =
Hurricane Electric tunnel).
It may not be a fundamental feature of the underlying technology - I =
manage some wireless kit at work which has the option of enforcing =
client separation (preventing end-points from directly communicating =
with each other). It's quite conceivable that someone may use such a =
feature for security - prevent direct node-node communications, but =
allow indirect communications via some security appliance. Again, using =
"address+prefix" to infer that you can directly contact a node will =
produce incorrect results.


From nobody Wed Apr  1 09:28:36 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9979A1AC3F8; Wed,  1 Apr 2015 09:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 btjxkuJwBUiV; Wed,  1 Apr 2015 09:28:32 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9024A1A0AFE; Wed,  1 Apr 2015 09:28:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <dhcwg@ietf.org>, <dhc-chairs@ietf.org>, <tomasz.mrugalski@eti.pg.gda.pl>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150401162832.444.74331.idtracker@ietfa.amsl.com>
Date: Wed, 01 Apr 2015 09:28:32 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/KoGo-0d0RB53vIafQOApNeeEzrk>
Subject: [dhcwg] ID Tracker State Update Notice: <draft-ietf-dhc-sedhcpv6-07.txt>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 16:28:33 -0000

IESG state changed to AD is watching from Publication Requested
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-dhc-sedhcpv6/


From nobody Wed Apr  1 10:21:59 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1632F1A0099 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 10:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 BxTvvD_B0w8S for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 10:21:55 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC5D41A00B5 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 10:21:53 -0700 (PDT)
Received: by igcau2 with SMTP id au2so54465004igc.0 for <dhcwg@ietf.org>; Wed, 01 Apr 2015 10:21:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=vGZpIB5A5qRjDE/pmCP53t67LXagYklYg3LG1CUhxLU=; b=fhqrad6IbjCV1EctMr9dFbsg0DxIKvO4TdN9vJjdUtGQRe0on3AuL7Spj2ZNDb8iDf eMpPE60hLZsPA7FxuT4Y6awFD3JemXroGC97nX/NeNZsa26FB/BoYxHxlZS40W3Z380u gL7jD7Br0rFUIoqcygoTo6Ao397HPKDcti7pSEJYRc9KCdBukKDbTzhpIgd+xR3taqB8 +Zi8htF3rnzWEr+ruZHSg85D/t3OHI170C6dYgwW7phllZ9PCA9FoU81yeGeMdbEf9bg o+CljBalZbBLVLGY5C5Er4H6KIDzAp0kBgBSf9SEQ9qX0AvuMwcv3D2ihphtewVusig5 9r8w==
MIME-Version: 1.0
X-Received: by 10.43.163.71 with SMTP id mn7mr73983581icc.72.1427908913296; Wed, 01 Apr 2015 10:21:53 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.21.3 with HTTP; Wed, 1 Apr 2015 10:21:53 -0700 (PDT)
In-Reply-To: <201503271613.t2RGDdLn061234@givry.fdupont.fr>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr>
Date: Wed, 1 Apr 2015 10:21:53 -0700
X-Google-Sender-Auth: XKn2RK675egemmO_mQ0nqGY5bzA
Message-ID: <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Q9gibHTJvpW_URhqrJgImYyMoz8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 17:21:57 -0000

At Fri, 27 Mar 2015 17:13:39 +0100,
Francis Dupont <Francis.Dupont@fdupont.fr> wrote:

> >  Why is it useless? I have successfully had devices that had a /128 on the
> >  interface (IA_NA) and a default route (from RA). This works just fine.
> >  It's a legitimate deployment scenario.
>
> => the key is in "and a default route (from RA)". Alone the IA_NA
> doesn't provide enough information, and in the common case the prefix
> length (got from RA) is known and the prefix on-line the /128 is bad.
>
> I discussed a bit with Lorenzo: we don't disagree about the problem
> (i.e., DHCPv6 provides the address and nothing about the prefix) but
> about the wording for its solution in the 3315bis:
>  - say nothing (RFC 3315): doesn't really hide the problem and
>   for sure doesn't help
>  - say use /64: it works well in the current real world but be serious,
>   it is clearly *not* an option for 3315bis! Nor a long term solution.
>  - say use /128 (Lorenzo): IMHO far to be enough (or with other words
>   it relies on a separation between address and route which is not
>   the common way things are implemented).
>  - explain the problem and give /128 as the default/fallback: the thing
>   to do. Now there are some text to write...

One other, radical option, mainly for food for thoughts (or rants):

- deprecate RFC4943: if the client employed the "on-link assumption",
  /128 without default router would work perfectly.  While RFC4943
  discusses several different problems, my understanding is that the
  principal issue was that we could introduce annoying delay on a dual
  stack host with a global IPv6 address but without a default router
  until it falls back to a reachable IPv4 destination.  But the latest
  practice is that just killing the on-link assumption wasn't enough
  and we need something more sophisticated (or uglier) techniques like
  the happy eyeball.  With such latest practice, I wonder whether the
  "on-link assumption" might not be as bad as when RFC4943 was
  written.

Assuming this is too radical/controversial/bad to be accepted, though,
I'll then focus on the text Lorenzo proposed (later in this thread):

  Addresses received via DHCPv6 do not have any associated reachability
  information. In order to avoid the problems described in [RFC4943],
  hosts MUST NOT assume that any IPv6 addresses are reachable on-link
  as a result of receiving an IA_NA or IA_TA; IPv6 addresses obtained
  from IA_NA or IA_TA MUST NOT be configured with any prefix length
  except /128.

I agree with this statement per se, but I think this is not
sufficient, since it doesn't (clearly) answer the question of what the
operator should do if they want to use DHCPv6-based address assignment
in an isolated single-link (or "subnet") network.  The
"architecturally correct" answer will be that they should deploy a
node (which would probably be collocated on the same node as the
DHCPv6 server) that sends RAs with router lifetime being 0 and with
appropriate on-link prefix(es).  This may be obvious for those
protocol-savvy people, but I suspect it's too subtle and should be
explained explicitly for many ordinary people.  Whether this should be
in 3315bis or some other DHCPv6-related document is a different
question, though.

--
JINMEI, Tatuya


From nobody Wed Apr  1 10:30:55 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BE51A0084 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 10:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 WICv8317FSmD for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 10:30:52 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C8331A0271 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 10:30:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9594; q=dns/txt; s=iport; t=1427909452; x=1429119052; h=from:to:cc:subject:date:message-id:mime-version; bh=V4DvAqFUVTr3jq1CiUjtgIFAXeR1YfC0HkMUdyNf1ik=; b=RgcsYxUB/+T17NZ2Dv5490mICLjdf9L5MLpaLJnZki5LCJeC0rZXwwB0 jzXoYB0ELiNkkadgHsdv4qOdFNH/XigQsacG8lNka+QSeefhRWr6JgBsN 6vwaKve6re5qbP2EIdt+tRp5sr64GeiSHJN4pG/+tTSc2g3xyxF6LRN7f A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CjBACNKhxV/4ENJK1cgkNDUmHEAwaHQwKBRDgUAQEBAQEBAXyEFgEEJwZMEgEqViYBBA4NiCfOegEBAQEBAQEBAQEBAQEBAQEBAQEBARePVxoxgx6BFgWQY542IoNugjN/AQEB
X-IronPort-AV: E=Sophos;i="5.11,504,1422921600";  d="scan'208,217";a="137303442"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP; 01 Apr 2015 17:30:51 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t31HUp3J029518 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 17:30:51 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 12:30:51 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work?
Thread-Index: AdBsoYwybwOljCs3QqmPfiy3wPAzEA==
Date: Wed, 1 Apr 2015 17:30:50 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.137]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1CA32071xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SkqzXDdvLNAkOttdTQk7fCIDn4M>
Subject: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 17:30:54 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1CA32071xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:

To the WG and co-authors of this document, as a follow up from the Dallas (=
IETF-92) DHC WG meeting, there is the question as to next step(s) for draft=
-ietf-dhc-stable-privacy-addresses.

In thinking about this some, my feeling is:

-          Drop the work. There is little reason for defining this for DHCP=
v6 servers as there are no "interoperability" issues.

o   If there are multiple servers operating on a link and they aren't coord=
inating activities in some way (i.e. perhaps DHCPv6 failover or some common=
 database), they will likely not be able to lease from the same pool of add=
resses anyway.

o   Sure, if you change the server to a different server implementation, it=
 may have different a algorithm, but does this really matter (and it is fai=
rly rare in the first place)?

o   And, there are also issues with the "range of addresses" model if the r=
ange is expanded or reduced, since this causes a change to the "stable" add=
resses.

o   So, do we really need this?

-          If people do feel that the work should continue (and eventually =
advance), the document should not be a "Standards Track" but "Informational=
".

So, I will propose that the DHC WG "drop this work" (mark the ID as dead). =
Objections? Comments?


-          Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1CA32071xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:977488445;
	mso-list-type:hybrid;
	mso-list-template-ids:-1840993312 -883547850 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">To the WG and co-authors of this document, as a foll=
ow up from the Dallas (IETF-92) DHC WG meeting, there is the question as to=
 next step(s) for draft-ietf-dhc-stable-privacy-addresses.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In thinking about this some, my feeling is:<o:p></o:=
p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Drop the work. There is little reason for defining =
this for DHCPv6 servers as there are no &#8220;interoperability&#8221; issu=
es.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>If there are multiple servers operating on a=
 link and they aren&#8217;t coordinating activities in some way (i.e. perha=
ps DHCPv6 failover or some common database), they will likely not be able t=
o lease from the same pool of addresses
 anyway.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>Sure, if you change the server to a differen=
t server implementation, it may have different a algorithm, but does this r=
eally matter (and it is fairly rare in the first place)?<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>And, there are also issues with the &#8220;r=
ange of addresses&#8221; model if the range is expanded or reduced, since t=
his causes a change to the &#8220;stable&#8221; addresses.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-family:&quot;Courier New&quot;"><s=
pan style=3D"mso-list:Ignore">o<span style=3D"font:7.0pt &quot;Times New Ro=
man&quot;">&nbsp;&nbsp;
</span></span></span><![endif]>So, do we really need this?<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>If people do feel that the work should continue (an=
d eventually advance), the document should not be a &#8220;Standards Track&=
#8221; but &#8220;Informational&#8221;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So, I will propose that the DHC WG &#8220;drop this =
work&#8221; (mark the ID as dead). Objections? Comments?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1CA32071xmbrcdx04ciscoc_--


From nobody Wed Apr  1 10:56:10 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A73521A1A6F for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 10:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ifL19_VnWepH for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 10:55:59 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 971181A0270 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 10:55:43 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 81CCDDA00BD; Wed,  1 Apr 2015 17:55:43 +0000 (UTC)
Received: from [10.0.1.158] (24.91.92.74) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 1 Apr 2015 10:55:37 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
Date: Wed, 1 Apr 2015 13:55:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [24.91.92.74]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/A-FmNwEbSr-IOlm8yMVolgXSils>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 17:56:08 -0000

On Apr 1, 2015, at 1:30 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> So, I will propose that the DHC WG =93drop this work=94 (mark the ID =
as dead). Objections? Comments?

I think that it is worth doing if use of IA_NA is going to be =
widespread, because otherwise we're going to have implementors who =
simply don't think to take user privacy into account.

This actually reminds me of another issue that came up in conversation =
in Dallas: what should the applicability be for IA_NA address assignment =
anyway?   It's fairly clear to me that it's more constrained than the =
applicability for IPv4 address allocation, and it might be worth giving =
some guidance in 3315bis.

As a starting point, I think we can pretty definitively say that IA_NA =
is _never_ appropriate in a home gateway DHCP server.  It's probably not =
appropriate in hotspot settings either.   It probably does make sense in =
an enterprise setting, and possibly for infrastructure devices.

Thotz?   It's possible that the set of places where IA_NA is applicable =
is sufficiently constrained that we don't _need_ DHCP servers to support =
stable privacy addresses.


From nobody Wed Apr  1 12:07:16 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 718001A872F for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 12:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 3FqUOUvdQIG1 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 12:07:12 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D9411A1A65 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 12:07:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2793; q=dns/txt; s=iport; t=1427915232; x=1429124832; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=lTNPdoyaD9PofoPcGgeH2ISwEVajlKOTmYsaOmncAU4=; b=ScOoI5VqRv9I959UWtIT62TxFcvUNja1JIYSxu2Kaoce5Ei0PYPSlSEt MrFPkEFACHSGCgpaG1ISCW6CRnKlT3Rzymodbe//8DLhCHasBvzCESQw7 rWTs++LE3VlOvMijbnOmB1gr5Svevikh3kys50RpAuyFkbSlpLsQGmYeE 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ClBADAQBxV/5pdJa1cgwaBLgW0Co99BodDAoFHOBQBAQEBAQEBfIQUAQEBBCcTPwwEAgEIEQQBAQEKCwkFBAcyFAkIAgQOBQiIJ85eAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sphC4aJgsHBgSDDYEWAQSQY5U3iH8igjKBPG+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,505,1422921600"; d="scan'208";a="137403094"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-3.cisco.com with ESMTP; 01 Apr 2015 19:07:11 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t31J7BjA024678 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 19:07:11 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 14:07:11 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUWByZTAVuV8ESYM5tVpMLK4p04ge2A
Date: Wed, 1 Apr 2015 19:07:10 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com>
In-Reply-To: <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.137]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ovOENlw09rKYS5-73sDaEg38Tgg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 19:07:15 -0000

My Thotz:

I'm not sure what document is the target of this IA_NA usage model (the sta=
ble-privacy-addresses? Or the anonymity profiles? Or DHCPv6bis? I would pre=
fer not to get into that in DHCPv6bis).

Why are stable privacy addresses useful when using DHCPv6? First, DHCPv6 ad=
dresses are probably random and there are usually ways to configure servers=
 to 'retain' a binding for a period of time beyond the "normal" end of the =
lease (at least our server has two techniques - grace periods and affinity =
periods). Yes, these have a larger cost than calculating them on the fly, b=
ut they are also more likely to be stable for the intended period (no issue=
s of collisions). Some servers may also remember the 'last' client to use a=
n address that has expired and give the client back that same address (many=
 DHCPv4 servers do this). And, then most servers also allow you to reserve =
addresses for a specific client (which is a stable address when you're conn=
ected to the same place).

And for when you write "I think that it is worth doing if use of IA_NA is g=
oing to be widespread, because otherwise we're going to have implementors w=
ho simply don't think to take user privacy into account.", how are "stable =
privacy addresses" more private than randomly assigned addresses?

- Bernie=20

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Wednesday, April 01, 2015 1:56 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-address=
es -> abandon work? / IA_NA applicability

On Apr 1, 2015, at 1:30 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> So, I will propose that the DHC WG "drop this work" (mark the ID as dead)=
. Objections? Comments?

I think that it is worth doing if use of IA_NA is going to be widespread, b=
ecause otherwise we're going to have implementors who simply don't think to=
 take user privacy into account.

This actually reminds me of another issue that came up in conversation in D=
allas: what should the applicability be for IA_NA address assignment anyway=
?   It's fairly clear to me that it's more constrained than the applicabili=
ty for IPv4 address allocation, and it might be worth giving some guidance =
in 3315bis.

As a starting point, I think we can pretty definitively say that IA_NA is _=
never_ appropriate in a home gateway DHCP server.  It's probably not approp=
riate in hotspot settings either.   It probably does make sense in an enter=
prise setting, and possibly for infrastructure devices.

Thotz?   It's possible that the set of places where IA_NA is applicable is =
sufficiently constrained that we don't _need_ DHCP servers to support stabl=
e privacy addresses.


From nobody Wed Apr  1 12:18:59 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5908A1A8A76 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 12:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 w0gSOtHQN9un for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 12:18:56 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 8E2D51A88B6 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 12:18:56 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 76F3DDA00BD; Wed,  1 Apr 2015 19:18:56 +0000 (UTC)
Received: from [10.0.1.158] (24.91.92.74) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 1 Apr 2015 12:18:56 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com>
Date: Wed, 1 Apr 2015 15:18:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [24.91.92.74]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jpSyXzCm-fFQTDOB1Pff6QzRLTQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 19:18:58 -0000

On Apr 1, 2015, at 3:07 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I'm not sure what document is the target of this IA_NA usage model =
(the stable-privacy-addresses? Or the anonymity profiles? Or DHCPv6bis? =
I would prefer not to get into that in DHCPv6bis).

It pretty much has to be DHCPv6bis, since that's where the protocol is =
defined, and you want the applicability statement to be with the =
protocol.

> Why are stable privacy addresses useful when using DHCPv6? First, =
DHCPv6 addresses are probably random and there are usually ways to =
configure servers to 'retain' a binding for a period of time beyond the =
"normal" end of the lease (at least our server has two techniques - =
grace periods and affinity periods).

If it's not specified that they are random, they can't be assumed to be =
random.   E.g., what if the DHCP server just uses your EUI64?

> And for when you write "I think that it is worth doing if use of IA_NA =
is going to be widespread, because otherwise we're going to have =
implementors who simply don't think to take user privacy into account.", =
how are "stable privacy addresses" more private than randomly assigned =
addresses?

Depends what it says in the spec.   If the spec doesn't say how the =
address is generated, then we can't assume that the way it's generated =
will result in privacy for the host.   So depending on the applicability =
of IA_NA, this could be an issue worth being specific about.


From nobody Wed Apr  1 12:52:37 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEC271A902C for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 12:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 g9BLcA9I2gxz for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 12:52:32 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2944E1A900B for <dhcwg@ietf.org>; Wed,  1 Apr 2015 12:52:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3300; q=dns/txt; s=iport; t=1427917952; x=1429127552; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=A81abn9Q/s94A3wlJgAp+aZxzLPZVlyV4X8hUdygYuM=; b=Jy/hHPR4n4vBI/j3p0lJm3ZqA4Avm4tNMc6fvykNCUqQmvCDaxVxc35z zPozZn/TVoH7hxmwB7qHuSXDSUoKpliK2BZywKh1BoYShY5MM6gg1A6Vb ynftHw1+85JGswwPruCaUi/jRCvnuBLyn56UJT0hBTvEjSrRpLXzv+smp c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A6BQDASxxV/5JdJa1cgwaBLgW0CpdGAoFHTAEBAQEBAX2EFAEBAQMBJxM/BQcEAgEIEQQBAQEKCwkFBAcyFAkIAgQOBQiIHwjOfgEBAQEBAQEBAQEBAQEBAQEBAQEBAReLKYQuGiYLBwYEgw2BFgEEkGOLE4okhTeDSCKCMoE8b4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,505,1422921600"; d="scan'208";a="137449503"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-2.cisco.com with ESMTP; 01 Apr 2015 19:52:31 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t31JqVED019213 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 19:52:31 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 14:52:31 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUWByZTAVuV8ESYM5tVpMLK4p04ge2AgABZ+YD//7DXMA==
Date: Wed, 1 Apr 2015 19:52:30 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com>
In-Reply-To: <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.137]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/NGv3a5sj__KD96oolwshx7E1lUo>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 19:52:36 -0000

By default, our server assignment is random which does NOT make use of any =
client information (but yes, there is a way you can make use of EUI-64 if y=
ou like).

Yes, having a privacy considerations about address assignment is certainly =
within DHCPv6bis work - we likely should think about what to add there (ref=
erences to privacy documents and perhaps server considerations). But, I thi=
nk saying what devices should or should not use IA_NA is not within its bou=
nds as that may change over time.

But this all is different than having a "stable-privacy-addresses" document=
. The discussion is good and we need to factor this into the privacy work a=
nd also into DHCPv6bis. I suspect the privacy documents will be out well be=
fore DHCPv6bis, so referencing those might be sufficient and adding a secti=
on on Server Privacy Considerations to those privacy documents is a good id=
ea - such as to mention that address assignment (and prefix delegation?) sh=
ould NOT make use of client specific information to generate the address --=
 at least in such a way where it is not hashed (which is what privacy-stabl=
e-addresses does).

So, we're back to the question as to whether draft-ietf-dhc-stable-privacy-=
addresses document is needed (and if it is, whether it is Informational). I=
f you really like the algorithm and want to suggest to server implementers =
here is one you can use, that's fine but it should be Informational then. I=
 don't see this as required to implement.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Wednesday, April 01, 2015 3:19 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-address=
es -> abandon work? / IA_NA applicability

On Apr 1, 2015, at 3:07 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I'm not sure what document is the target of this IA_NA usage model (the s=
table-privacy-addresses? Or the anonymity profiles? Or DHCPv6bis? I would p=
refer not to get into that in DHCPv6bis).

It pretty much has to be DHCPv6bis, since that's where the protocol is defi=
ned, and you want the applicability statement to be with the protocol.

> Why are stable privacy addresses useful when using DHCPv6? First, DHCPv6 =
addresses are probably random and there are usually ways to configure serve=
rs to 'retain' a binding for a period of time beyond the "normal" end of th=
e lease (at least our server has two techniques - grace periods and affinit=
y periods).

If it's not specified that they are random, they can't be assumed to be ran=
dom.   E.g., what if the DHCP server just uses your EUI64?

> And for when you write "I think that it is worth doing if use of IA_NA is=
 going to be widespread, because otherwise we're going to have implementors=
 who simply don't think to take user privacy into account.", how are "stabl=
e privacy addresses" more private than randomly assigned addresses?

Depends what it says in the spec.   If the spec doesn't say how the address=
 is generated, then we can't assume that the way it's generated will result=
 in privacy for the host.   So depending on the applicability of IA_NA, thi=
s could be an issue worth being specific about.


From nobody Wed Apr  1 13:32:58 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6725C1A913E for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 13:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 dLRk9eupmRRJ for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 13:32:45 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F1CE1A8825 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 13:29:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3957; q=dns/txt; s=iport; t=1427920160; x=1429129760; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=aS4peKRkAbVqxLOmgLgmyBiVU0aDz+5aQ/h4Nosdvko=; b=b850EhQpjHGhmDrJcGd2+CwtICst+Rr5meZr9LW+OtlhAGJfxTLN/eKX 4ewOwxsQz9ur8HCN59lpPmlEFqsF00JagTFCATkrQ5jdEfd4pgS7e9Bsm 6eqoZs+ZeJBNnRIz4DIV4QZrVkydgu4dwOLBQVTRGTF9rH/XxhlgASh0W Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A+BQD0UxxV/4QNJK1cgwZSXAW0CpFJDIVxAoFHTAEBAQEBAX2EFAEBAQMBAQEBJBM0CwUHBAIBCBEEAQEBCgsJBQQHJwsUCQgCBA4FCIgfCA3OagEBAQEBAQEBAQEBAQEBAQEBAQEBARMEiymELhomCwcGBIMNgRYFkGODcochiiSFN4NIIoIygTxvAYFDfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,506,1422921600"; d="scan'208";a="408499841"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-6.cisco.com with ESMTP; 01 Apr 2015 20:29:19 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t31KTISd026023 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Apr 2015 20:29:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 15:29:18 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUWByZTAVuV8ESYM5tVpMLK4p04ge2AgABZ+YD//7DXMIAADkcA
Date: Wed, 1 Apr 2015 20:29:18 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA3230D@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.137]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/kMT-EuE288H3t63FtTyS0paIifQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 20:32:50 -0000

BTW: Section 4.3 of draft-ietf-dhc-dhcpv6-privacy already covers "allocatio=
n strategies" -- see https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-priv=
acy-00#section-4.3. So, "it is already in there".

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, April 01, 2015 3:53 PM
To: Ted Lemon
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-address=
es -> abandon work? / IA_NA applicability

By default, our server assignment is random which does NOT make use of any =
client information (but yes, there is a way you can make use of EUI-64 if y=
ou like).

Yes, having a privacy considerations about address assignment is certainly =
within DHCPv6bis work - we likely should think about what to add there (ref=
erences to privacy documents and perhaps server considerations). But, I thi=
nk saying what devices should or should not use IA_NA is not within its bou=
nds as that may change over time.

But this all is different than having a "stable-privacy-addresses" document=
. The discussion is good and we need to factor this into the privacy work a=
nd also into DHCPv6bis. I suspect the privacy documents will be out well be=
fore DHCPv6bis, so referencing those might be sufficient and adding a secti=
on on Server Privacy Considerations to those privacy documents is a good id=
ea - such as to mention that address assignment (and prefix delegation?) sh=
ould NOT make use of client specific information to generate the address --=
 at least in such a way where it is not hashed (which is what privacy-stabl=
e-addresses does).

So, we're back to the question as to whether draft-ietf-dhc-stable-privacy-=
addresses document is needed (and if it is, whether it is Informational). I=
f you really like the algorithm and want to suggest to server implementers =
here is one you can use, that's fine but it should be Informational then. I=
 don't see this as required to implement.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Wednesday, April 01, 2015 3:19 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-address=
es -> abandon work? / IA_NA applicability

On Apr 1, 2015, at 3:07 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I'm not sure what document is the target of this IA_NA usage model (the s=
table-privacy-addresses? Or the anonymity profiles? Or DHCPv6bis? I would p=
refer not to get into that in DHCPv6bis).

It pretty much has to be DHCPv6bis, since that's where the protocol is defi=
ned, and you want the applicability statement to be with the protocol.

> Why are stable privacy addresses useful when using DHCPv6? First, DHCPv6 =
addresses are probably random and there are usually ways to configure serve=
rs to 'retain' a binding for a period of time beyond the "normal" end of th=
e lease (at least our server has two techniques - grace periods and affinit=
y periods).

If it's not specified that they are random, they can't be assumed to be ran=
dom.   E.g., what if the DHCP server just uses your EUI64?

> And for when you write "I think that it is worth doing if use of IA_NA is=
 going to be widespread, because otherwise we're going to have implementors=
 who simply don't think to take user privacy into account.", how are "stabl=
e privacy addresses" more private than randomly assigned addresses?

Depends what it says in the spec.   If the spec doesn't say how the address=
 is generated, then we can't assume that the way it's generated will result=
 in privacy for the host.   So depending on the applicability of IA_NA, thi=
s could be an issue worth being specific about.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Wed Apr  1 13:47:17 2015
Return-Path: <bs7652@att.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1449B1A913E for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 13:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Q2nvP1X0Gni8 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 13:47:14 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2CD31A9114 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 13:47:14 -0700 (PDT)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id 2595c155.2b8218853940.3264472.00-2409.8426320.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Wed, 01 Apr 2015 20:47:14 +0000 (UTC)
X-MXL-Hash: 551c59527a9949a0-6265c9bf44e51affdcee9387fb707c684cd4b4f3
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id e495c155.0.3264436.00-2242.8426177.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Wed, 01 Apr 2015 20:47:13 +0000 (UTC)
X-MXL-Hash: 551c5951133f8b9f-c079f138b6cca2969c365d5b37d5006d93c14136
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t31KlA4g027668; Wed, 1 Apr 2015 16:47:10 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t31Kl5TG027551 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Apr 2015 16:47:07 -0400
Received: from GAALPA1MSGHUBAA.ITServices.sbc.com (GAALPA1MSGHUBAA.itservices.sbc.com [130.8.218.150]) by alpi132.aldc.att.com (RSA Interceptor); Wed, 1 Apr 2015 20:46:43 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.35]) by GAALPA1MSGHUBAA.ITServices.sbc.com ([130.8.218.150]) with mapi id 14.03.0224.002; Wed, 1 Apr 2015 16:46:42 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUpBEO5qtIOqUebZ+gro6dcx504nrYg
Date: Wed, 1 Apr 2015 20:46:42 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130F968CD@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com>
In-Reply-To: <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.240.90]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=DqThDhD+ c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=NwmGxOAsepEA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP]
X-AnalysisOut: [7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=e9J7MTPGsLIA:10 a=U1707hq01]
X-AnalysisOut: [Vk31v0BaKIA:9 a=CjuIK1q_8ugA:10]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.229.23]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/c69HvwYqQP9gQwaN0iPoIGPEHfE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 20:47:16 -0000

> As a starting point, I think we can pretty definitively say that IA_NA is
> _never_ appropriate in a home gateway DHCP server

I'm aware of a number of ISPs who are considering having IA_NA supplied by =
an ISP-provided CE router's DHCPv6 server to the ISP's IPTV set-top boxes i=
nside the home network. Many ISPs also consider IA_NA appropriate for addre=
ssing of other ISP-supplied devices (e.g., femto access point, home automat=
ion/monitoring devices, etc.) behind ISP-supplied CE routers. These are ISP=
-managed devices. Often the home network segments they are attached to are =
also ISP-managed. Often, the only points on the Internet that these devices=
 communicate with are the ISP servers. I'm unconvinced as to the value of "=
privacy" addresses in this case.
Barbara


From nobody Wed Apr  1 16:29:11 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D578F1ACC86 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 16:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 9Kf45ksXxwUV for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 16:29:08 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AC311ACCF3 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 16:29:05 -0700 (PDT)
Received: by igbud6 with SMTP id ud6so62637099igb.1 for <dhcwg@ietf.org>; Wed, 01 Apr 2015 16:29:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7mDqlx6ad4GvOb8kOIBhq1Akqc8NaywWXaEJq1y+pVo=; b=n4sNfunuejHZga0pFOfGcuZEWpmiIQoWZviRY5qOvRCfBTRyHYEKo2pg+9lOhHKq6t E6Iop4eUDBilEvDg5WFRrKN9ZScMLPgJ7JySoXz07JoFqlSaVkXi3X9FvXbcanoSAKdw pU2ryyIwFX5VnQGJgche8V/mNzcOQf6eWBVhazfuk9txNvQxTX1LOo52w4AI10LvfE9u 3/mp66SNX54WyM5jdvam+avP5ZrMyoGk+c8yXZYg58kgrEQOilwZyxyvD666FiEswztJ J3t2nJFoPJyjAtXFfI7jzCuvaH3dY6O2290Ro1Kyr5qi4UNpRjWMdbYnAp+XEBG7WEw9 e0MQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=7mDqlx6ad4GvOb8kOIBhq1Akqc8NaywWXaEJq1y+pVo=; b=gljwMR0N2TEqjqm/86qgTLqfP9clitxLHvj3IYcXPIc8W5TlWtoyqCS/srkf1M8Mr5 ciPgmzCYB7rD3+IoeyjknpMd1LFmIAEt69ZB3G/iTr9/h+qCfRuJ0zHKs+pgCq86V63G cS7EQ6PhIMUQj/Ut64UDVQ+KyJ/zdGzlOcqihH/+p3O6mjvVBr3/7uzUrmM1FS1XSGcX VmgzVCG8YGdFWY+IdXpLWkXRwwz9ba0+UkK0mxBYxWZlE2TzpT9XPC4C77f9tlwRV5Ih dKODLWZpLgs5+oacDD7WjUiC/2BNrwiPBi5KRVUGzwkSfAzqCRODBDEntkqWji4MgGvY l66Q==
X-Gm-Message-State: ALoCoQlIG3oWoSzMSDpbSjKVO9M9aUhiLrr7brQFlZYOVDhD3isZohBOD4HbMzS4oYlk9Dp605z1
X-Received: by 10.107.134.9 with SMTP id i9mr66445896iod.90.1427930945402; Wed, 01 Apr 2015 16:29:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 1 Apr 2015 16:28:45 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 2 Apr 2015 08:28:45 +0900
Message-ID: <CAKD1Yr0_WEbR20ghJNx8n5fPf=Yrqp=wZz_Q_7J2L7c5xDzVcg@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary=001a113ecae0c3dbbf0512b21497
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Gpbk6cGef78J7g9CBh-4jFWfYQc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 23:29:10 -0000

--001a113ecae0c3dbbf0512b21497
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 2, 2015 at 4:52 AM, Bernie Volz (volz) <volz@cisco.com> wrote:

> So, we're back to the question as to whether
> draft-ietf-dhc-stable-privacy-addresses document is needed (and if it is,
> whether it is Informational). If you really like the algorithm and want to
> suggest to server implementers here is one you can use, that's fine but it
> should be Informational then. I don't see this as required to implement.
>

+1. draft-ietf-dhc-stable-privacy-addresses does not really provide much
value on top of assigning addresses randomly. Address assignment via IA_NA
is fundamentally stateful, so I don't see a lot of gain in making it
"deterministic unpredictable" as opposed to "random unpredictable".

If what we want is provide guidance to implementors to use unpredictable
addresses, then we should do that without specifying a particular algorithm.

--001a113ecae0c3dbbf0512b21497
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 2, 2015 at 4:52 AM, Bernie Volz (volz) <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex">So, we&#39;re back to the question as to whethe=
r draft-ietf-dhc-stable-privacy-addresses document is needed (and if it is,=
 whether it is Informational). If you really like the algorithm and want to=
 suggest to server implementers here is one you can use, that&#39;s fine bu=
t it should be Informational then. I don&#39;t see this as required to impl=
ement.<br></blockquote><div><br></div><div>+1. draft-ietf-dhc-stable-privac=
y-addresses=C2=A0does not really provide much value on top of assigning add=
resses=C2=A0randomly. Address assignment via IA_NA is fundamentally statefu=
l, so I don&#39;t see a lot of gain in making it &quot;deterministic unpred=
ictable&quot; as opposed to &quot;random unpredictable&quot;.</div><div><br=
></div><div>If what we want is provide guidance to implementors to use unpr=
edictable addresses, then we should do that without specifying a particular=
 algorithm.</div></div></div></div>

--001a113ecae0c3dbbf0512b21497--


From nobody Wed Apr  1 16:37:09 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3610F1A1DE2 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 16:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 VXXDOOm1PjmA for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 16:37:06 -0700 (PDT)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37F281A00E0 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 16:37:06 -0700 (PDT)
Received: by ignm3 with SMTP id m3so40212755ign.0 for <dhcwg@ietf.org>; Wed, 01 Apr 2015 16:37:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Sv15IOBhjLjDbBdt4xcx3r45xDLtDBxeCIUZLVQNBdY=; b=GTuZltNquxOc+cpHnDeWauBNU+/oor3jI8X07sNFh+clp8nnl3kdQ1tMR86qntz3yr as/FzlcqY/YPwzutOFRW77QaPMTpWPFIM6sfcwfdSuPXzAsMxM5sHo5dS6GEyn9jsD2X K/DUQgu/exuro0XHiFa9VYTFyD0FU3ZesvG1BQDLF4YASJh3VfEBDjW2Tm6FgArtXNiz XaCpWYYryyrQSZgApp9Y2ZnQAhmvn640CF5pJ6gtq5YH+kKYN8pWcd1wVonZ+pkzjKIT kn4fEuFq/i/Obaw7F67D+VdcToYIDVGXo5KF27Jg5DJxd8CQcaibNbCF9J0Ss8umLMVR 9LuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Sv15IOBhjLjDbBdt4xcx3r45xDLtDBxeCIUZLVQNBdY=; b=U1cEm4PFV2jtua6C0r6xFDHAPCJBpOmgEZQabXg3w69VhWexDBJf6XMx7m0WMpV4MS 63H+NFfl3+M6l6698poPMFe1pQugMjtLp03E8AfMDeLOBbQqPCtqiGtJrAiQZdmbyZ7U Vh6BCpRH4p0+MYwjd4HGXL1kv/hq30j2nYcIguuoYkT4kT/vM7pXOw7zcVt0odN7dm57 /Rv3PPEyFWu4zndRMRmXqnyCoWegsY7QD9a8kM0WgzT3jdTDTCLmTvYUq2w+u5Euc8Ja y3px4sGrZHERzh6PYTm1FLEjWbfXPWW8GMqR5yIKig1a1fb31N8jpENg6f2EhLJS22dV lAIg==
X-Gm-Message-State: ALoCoQmOtocRfODvveHMQuvhraQ4wfFmMkfxlJrrFVYZLW3z5dn2+ipjpLlmCikRkwobjFCLtKoE
X-Received: by 10.50.61.175 with SMTP id q15mr15984405igr.34.1427931425620; Wed, 01 Apr 2015 16:37:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 1 Apr 2015 16:36:45 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 2 Apr 2015 08:36:45 +0900
Message-ID: <CAKD1Yr1qZr9o21q7WR=7zUogTf92+qHXLy2Aug10V_Bt4FiZmA@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary=047d7bdc1c206360ca0512b231c1
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/xSIJJK-nER7QSq1A6gXTmcNJNmE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 23:37:07 -0000

--047d7bdc1c206360ca0512b231c1
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 2, 2015 at 4:52 AM, Bernie Volz (volz) <volz@cisco.com> wrote:

> But, I think saying what devices should or should not use IA_NA is not
> within its bounds as that may change over time.
>

But we can certainly say what types of scenarios are appropriate for use of
address assignment via IA_NA. For example, any scenario that requires
changing client IPv6 prefixes dynamically and does not use server failover
cannot be reliably implemented using IA_NA. Even if the client supports
reconfigure, a server crash makes it impossible to change the client's IP
address, even if there is another server.

This limitation is not obvious to someone used to DHCPv4, because in IPv4
clients typically never need to change addresses because the network uses
NAT.

--047d7bdc1c206360ca0512b231c1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 2, 2015 at 4:52 AM, Bernie Volz (volz) <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">But, I think saying what devices =
should or should not use IA_NA is not within its bounds as that may change =
over time.<br></blockquote><div><br></div><div>But we can certainly say wha=
t types of scenarios are appropriate for use of address assignment via IA_N=
A. For example, any scenario that requires changing client IPv6 prefixes dy=
namically and does not use server failover cannot be reliably implemented u=
sing IA_NA. Even if the client supports reconfigure, a server crash makes i=
t impossible to change the client&#39;s IP address, even if there is anothe=
r server.</div><div><br></div><div>This limitation is not obvious to someon=
e used to DHCPv4, because in IPv4 clients typically never need to change ad=
dresses because the network uses NAT.</div></div></div></div>

--047d7bdc1c206360ca0512b231c1--


From nobody Wed Apr  1 16:53:10 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 753351A1B61 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 16:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 sGlQSpdgqvmx for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 16:53:07 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 4B50B1A1A47 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 16:53:07 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 050BFDA00CE; Wed,  1 Apr 2015 23:53:07 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 1 Apr 2015 16:53:00 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA3230D@xmb-rcd-x04.cisco.com>
Date: Wed, 1 Apr 2015 19:52:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <E9A1A551-6B12-4383-B65C-4DC974CC3A7A@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA3230D@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/krEx938pP4gzcvm26-_ebG81jAU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 23:53:08 -0000

On Apr 1, 2015, at 4:29 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> BTW: Section 4.3 of draft-ietf-dhc-dhcpv6-privacy already covers =
"allocation strategies" -- see =
https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-privacy-00#section-4.3. =
So, "it is already in there".

That's not normative.


From nobody Wed Apr  1 16:55:39 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF40C1ACE01 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 16:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 gNIHTT08KLjo for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 16:55:36 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 7FF351ACE06 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 16:55:36 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 6D658DA00CE; Wed,  1 Apr 2015 23:55:36 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 1 Apr 2015 16:55:36 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E61130F968CD@GAALPA1MSGUSRBF.ITServices.sbc.com>
Date: Wed, 1 Apr 2015 19:55:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <4215054D-5FBF-4A86-8207-8B8EC286E190@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <2D09D61DDFA73D4C884805CC7865E61130F968CD@GAALPA1MSGUSRBF.ITServices.sbc.com>
To: "STARK, BARBARA H" <bs7652@att.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Q4a4z2HcEjNqvbysSw-8FJl6tUo>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 23:55:38 -0000

On Apr 1, 2015, at 4:46 PM, STARK, BARBARA H <bs7652@att.com> wrote:
> I'm aware of a number of ISPs who are considering having IA_NA =
supplied by an ISP-provided CE router's DHCPv6 server to the ISP's IPTV =
set-top boxes inside the home network. Many ISPs also consider IA_NA =
appropriate for addressing of other ISP-supplied devices (e.g., femto =
access point, home automation/monitoring devices, etc.) behind =
ISP-supplied CE routers. These are ISP-managed devices. Often the home =
network segments they are attached to are also ISP-managed. Often, the =
only points on the Internet that these devices communicate with are the =
ISP servers. I'm unconvinced as to the value of "privacy" addresses in =
this case.

That's infrastructure.   I agree that this is a valid use case.   What I =
mean when I propose that HGs shouldn't do IA_NA is that they shouldn't =
assign IP addresses on customer networks to customer devices using =
IA_NA.   It would be actively bad if a CE of the sort you are describing =
started requiring devices on the home network to do DHCPv6 in order to =
connect to the Internet.   So it's good that we had this talk!   :)


From nobody Wed Apr  1 19:20:07 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4151A6F39 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 19:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 hcrYUnTl2llv for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 19:20:01 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 318871A1B12 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 19:20:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=591; q=dns/txt; s=iport; t=1427941201; x=1429150801; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=955S5ZGVOrRFBncQd1lr4XQg2r1PtdzbFgeDRpOFsj8=; b=m8pHz9WSmDbkh449D5Rz5Yn3wRXMsBzj4V3leCc0/B0xcIYRpt68byVh qjxTnmXoAa3JtfNWyq7c7OFRbTI8IJRCn1Ad4iZNDYUtj8H8+K3IqvIEw 2HMHe57gWxP1itQcvRF/9ucQmEfrF5LCM8qn0TA59v7gHrUUZqM0U8TgD g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BDBQDtphxV/4sNJK1cgwhSXMVkhXECgUdMAQEBAQEBfoQeAQEBAwEnEz8FCwIBCBgdAQULMiUCBA4FiCcIDc0dAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSLKYQuGDMHgxeBFgEEkGSDcoYEi0KIfyKCMoE8bwGCQgEBAQ
X-IronPort-AV: E=Sophos;i="5.11,507,1422921600"; d="scan'208";a="137542438"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-7.cisco.com with ESMTP; 02 Apr 2015 02:20:00 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t322K07Q024723 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 02:20:00 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 21:20:00 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUWByZTAVuV8ESYM5tVpMLK4p04ge2AgABZ+YD//7DXMIAADkcAgACNd4D//9VELA==
Date: Thu, 2 Apr 2015 02:20:00 +0000
Message-ID: <BC8728E9-7370-447B-99EE-0B3DE1D59CC0@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA3230D@xmb-rcd-x04.cisco.com>, <E9A1A551-6B12-4383-B65C-4DC974CC3A7A@nominum.com>
In-Reply-To: <E9A1A551-6B12-4383-B65C-4DC974CC3A7A@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/GJKRFi_bMUDQ1YwXiT0y97V7wLY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 02:20:03 -0000

I don't see this as required to be normative. It creates no interop issues.=
 The market can decide what they want server (& client) implementers to pro=
vide.

- Bernie (from iPhone)

> On Apr 1, 2015, at 7:53 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>=20
>> On Apr 1, 2015, at 4:29 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
>> BTW: Section 4.3 of draft-ietf-dhc-dhcpv6-privacy already covers "alloca=
tion strategies" -- see https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-p=
rivacy-00#section-4.3. So, "it is already in there".
>=20
> That's not normative.
>=20


From nobody Wed Apr  1 19:22:43 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE3C1A6EF9 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 19:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 1QMWQLcZyc77 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 19:22:41 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 3DED11A1B12 for <dhcwg@ietf.org>; Wed,  1 Apr 2015 19:22:41 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id BD5CFDA00D1; Thu,  2 Apr 2015 02:22:40 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 1 Apr 2015 19:22:34 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <BC8728E9-7370-447B-99EE-0B3DE1D59CC0@cisco.com>
Date: Wed, 1 Apr 2015 22:22:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <21088A8D-BB84-427F-BACB-1A8AD5896F58@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA3230D@xmb-rcd-x04.cisco.com>, <E9A1A551-6B12-4383-B65C-4DC974CC3A7A@nominum.com> <BC8728E9-7370-447B-99EE-0B3DE1D59CC0@cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/f_Sgu87JvTMuxYld7pRfRqrCzk4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 02:22:42 -0000

On Apr 1, 2015, at 10:20 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I don't see this as required to be normative. It creates no interop =
issues. The market can decide what they want server (& client) =
implementers to provide.

BCPs are normative.   I don't think "let the market decide" is really an =
appropriate answer here.   I think your privacy considerations approach =
in 3315bis is fine.=


From nobody Wed Apr  1 19:59:01 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A4A1A01F9 for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 19:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 JmFK1u1K_ELM for <dhcwg@ietfa.amsl.com>; Wed,  1 Apr 2015 19:58:58 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 991BB1A01EC for <dhcwg@ietf.org>; Wed,  1 Apr 2015 19:58:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=727; q=dns/txt; s=iport; t=1427943538; x=1429153138; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=n6uSpzCf1JOsXt1ISGtC216JLO06ljid2SwtY4g5uJM=; b=IPERLtDlJdsZtH5bbigwZtP4+73KSxaRTmQqZh0YrSwRiRIrceA1cv4l r5tLBOiG/qiF9vWRA8yIYLEr0MAyd8Bt4b2Drv9K2bbwYeE/DiwcvjqcE btUC4Tby0RF5OnufvxYnxdkLsgmTw19siS4qJw4Cc7tcGKfL1qbQ0ZiJZ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BBBQCcrxxV/4MNJK1cgwhSXMVkhXGBSUwBAQEBAQF+hB8CBDpRAQg1AUImAQQBG4gmDc0nAQEBAQYBAQEBAQEBG4sphEaDUYEWBZBkiXaLTohzIoNubwGCQgEBAQ
X-IronPort-AV: E=Sophos;i="5.11,507,1422921600"; d="scan'208";a="408577445"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-6.cisco.com with ESMTP; 02 Apr 2015 02:58:58 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t322wvlK030833 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 02:58:57 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Wed, 1 Apr 2015 21:58:57 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "<ian. farrer@telekom. de>" <ian.farrer@telekom.de>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Request for DHC review of draft-fsc-softwire-dhcp4o6-saddr-opt
Thread-Index: AdBs8PZCPjy+vYKRR8OF76Dh+IQq/A==
Date: Thu, 2 Apr 2015 02:58:57 +0000
Message-ID: <8A147681-EB41-4864-B1AB-A6CA14262DC1@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <120C510813A45041AEB03C3D5B49DDA6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SFC5vqUxU_0xAwOn2I59QR5R1iM>
Subject: Re: [dhcwg] Request for DHC review of draft-fsc-softwire-dhcp4o6-saddr-opt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 02:59:00 -0000

Ian:

Back in December you requested a review. Not sure if anyone else in the WG =
has looked at it & commented, but here's my comments.

The document seems fine though you should remove the "sub-option" wording a=
nd replace with just option or encapsulated option. See RFC 7227 for more. =
Calling these sub-options is not good as that implies a unique numbering sp=
ace.

Also, the IANA section should be a bit more explicit (provide registry URL,=
 http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml)=
 to avoid any possible issues. See another recent document that defined new=
 options for an example.

Very minor - fix formatting of figure in section 5.1.

- Bernie (from iPad)=


From nobody Thu Apr  2 00:02:51 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 908021B2B68 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 U69YtI0OME6T for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:02:48 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F16C1A891D for <dhcwg@ietf.org>; Thu,  2 Apr 2015 00:02:47 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3272kGo020544 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 09:02:46 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DB347205CE4 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 09:03:40 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id CF92720124C for <dhcwg@ietf.org>; Thu,  2 Apr 2015 09:03:40 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3272Mtd020753 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 09:02:45 +0200
Message-ID: <551CE97E.4020504@gmail.com>
Date: Thu, 02 Apr 2015 09:02:22 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk>
In-Reply-To: <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/e6s7AdRY9rB0uO0PF-x86893wH4>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 07:02:50 -0000

Le 01/04/2015 15:21, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>> Reading you I think I misunderstood what is meant by 'reachable'
>> and 'unreachable'.  You seem to imply that 'reachable' is a
>> neighbor, whereas I think 'reachable'  is from a neighbor or from
>> the Internet (like when we say that a 192. address is not
>> reachable/contactable, whereas a Globally Unique Address GUA _is_
>> reachable).
>
> You make a good point there. Yes, I've been using "reachable" as
> meaning "I can directly send a packet to that device".

Ok, directly meaning to not go through a router, be on same link.  It
may to invoke ND for it, though.  So this NC absence for a /128 is not
necessarily explaining your directly.

[...]
>> So that is also 'reachable', but not neighbor.
>
> But it may well be a neighbour. It's not that uncommon to have
> multiple IPv4 subnets on one link. To handle this means either
> sending all inter-subnet traffic through a router, or configuring
> additional routing table entries on each device.

So that is is a neighbor in Ethernet terms, but is not a neighbor in ND
terms.

[...]
>> Distinction: ok for /64, but if it's a /128 then it wouldn't have
>> neighbors (/128 can only be on one end, and that something can't be
>> a link).
>
> NO You **CAN** have a "/128" and have neighbours.

These are Ethernet neighbors, but they are not ND neighbors.  ND works
with a multicast scope.  Whoever is in that scope is a neighbor,
otherwise it is not a neighbor.  Ethernet neighbors are all people
present on a VLAN or a on a hub and there may be multiple
distinguishable IP multicast scopes there, although a single Ethernet
multicast scope is in a VLAN (or in a hub).

> Well actually, the "/128" is an artificial construct required to
> work around the implementations which (incorrectly) require every
> address to have a subnet mask. If correctly implemented, you have
> "an address" (or multiple addresses, but lets just consider one for
> now).
>
> Separately to any address(es) you have, you have a table of how to
> send packets to other addresses. Your own address does not have to be
> in that list.

Ok.


> It's been mentioned that one thread originated from a comment in some
> code along the lines of "what do I use for a prefix length - until
> someone comes up with something I'll use 64".

That is a DHCP client suite - the guy does not know what to put there,
he needs help.  Until that help arrives he puts 64, and it works.

That 64 is something not good at all because it forbids CIDR in IPv6.
We are not there yet to sense how CIDR is important in IPv6, but as this
IPv6 started it looks as CIDR is going to be important.

> That's an implementation issue - and I think it'll be a long time
> before the Linux world manages to unravel several decades of built in
> logic to separate addresses and prefixes/reachability information.

I tend to agree.  Other times things may move really fast.

>>> It may well be that the network doesn't support device-device
>>> communications directly - access networks (eg ADSL) come to mind
>>> where each user has a point-point link back to the central hub
>>> and ND may not be supported to find other nodes on other links.
>>> Thus using "address + mask" to infer direct reachability is just
>>>  wrong.
>>
>> So, one would not think an unreachable address is of any use at
>> all. (be its reachability inferred solely from address or from both
>> address/mask)
>
> You've probably highlighted the main issue - one of terminology, and
>  I think I'm as guilty as anyone of being a bit sloppy. I *think* the
>  terminology is "on-link" meaning you can directly communicate with
> that other device (use ND to find it's physical address, MAC in
> ethernet like networks), and "off-link" meaning that you cannot
> directly communicate with it and must go via a router.

SO why is RA talking at all about off-link information on this link?  I
thought RAs are not allowed to talk about other things than what's
happening on this link.

For example, there is no means to inform a Router that a certain prefix
is active on this link and should inform this directly-attached other
link about its prefix.

There is no means to propagate a prefix received in an RA (or any other
information in an RA) to other networks.

What's the use of this 'off-link' in RA?  (other than telling Hosts to
not care about it).

> It would probably help if one of the experts clarified this.

I agree.

Alex

>
> On an ethernet network, two devices with completely unrelated
> addresses may directly communicate as long as they have a means of
> finding out about each other. This is where the RA provided prefix
> lists (with their on-link flag) come in - by configuring the routing
>  tables. Note that a prefix only needs one table entry, whether you
> have 1, 100, 100,000 addresses on the interface.
>
> On the other hand, there are probably networks where the end-points
> all have addresses which are in the same prefix, but which cannot
> directly communicate end-point to end-point without going via the
> hub. Granted these probably all use a /64 prefix for each link,
> that's my experience so far in getting connected (via my ISPs trial,
>  and currently via a Hurricane Electric tunnel). It may not be a
> fundamental feature of the underlying technology - I manage some
> wireless kit at work which has the option of enforcing client
> separation (preventing end-points from directly communicating with
> each other). It's quite conceivable that someone may use such a
> feature for security - prevent direct node-node communications, but
> allow indirect communications via some security appliance. Again,
> using "address+prefix" to infer that you can directly contact a node
>  will produce incorrect results.
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Thu Apr  2 00:14:02 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDE61B2B82 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 UH2s0tr9AmZt for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:13:59 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B9331B2B81 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 00:13:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t327DvLk007920 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 09:13:57 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E0217205C8A for <dhcwg@ietf.org>; Thu,  2 Apr 2015 09:14:51 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id D85F6205A1B for <dhcwg@ietf.org>; Thu,  2 Apr 2015 09:14:51 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t327DZTh029367 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 09:13:56 +0200
Message-ID: <551CEC1F.3070006@gmail.com>
Date: Thu, 02 Apr 2015 09:13:35 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com>
In-Reply-To: <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pEuEiQp0G5ZCvmbydFNEAotmjow>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 07:14:01 -0000

Le 01/04/2015 19:21, ç¥žæ˜Žé�”å“‰ a Ã©crit :
> At Fri, 27 Mar 2015 17:13:39 +0100,
> Francis Dupont <Francis.Dupont@fdupont.fr> wrote:
>
>>>   Why is it useless? I have successfully had devices that had a /128 on the
>>>   interface (IA_NA) and a default route (from RA). This works just fine.
>>>   It's a legitimate deployment scenario.
>>
>> => the key is in "and a default route (from RA)". Alone the IA_NA
>> doesn't provide enough information, and in the common case the prefix
>> length (got from RA) is known and the prefix on-line the /128 is bad.
>>
>> I discussed a bit with Lorenzo: we don't disagree about the problem
>> (i.e., DHCPv6 provides the address and nothing about the prefix) but
>> about the wording for its solution in the 3315bis:
>>   - say nothing (RFC 3315): doesn't really hide the problem and
>>    for sure doesn't help
>>   - say use /64: it works well in the current real world but be serious,
>>    it is clearly *not* an option for 3315bis! Nor a long term solution.
>>   - say use /128 (Lorenzo): IMHO far to be enough (or with other words
>>    it relies on a separation between address and route which is not
>>    the common way things are implemented).
>>   - explain the problem and give /128 as the default/fallback: the thing
>>    to do. Now there are some text to write...
>
> One other, radical option, mainly for food for thoughts (or rants):
>
> - deprecate RFC4943: if the client employed the "on-link assumption",
>    /128 without default router would work perfectly.  While RFC4943
>    discusses several different problems, my understanding is that the
>    principal issue was that we could introduce annoying delay on a dual
>    stack host with a global IPv6 address but without a default router
>    until it falls back to a reachable IPv4 destination.  But the latest
>    practice is that just killing the on-link assumption wasn't enough
>    and we need something more sophisticated (or uglier) techniques like
>    the happy eyeball.  With such latest practice, I wonder whether the
>    "on-link assumption" might not be as bad as when RFC4943 was
>    written.
>
> Assuming this is too radical/controversial/bad to be accepted, though,
> I'll then focus on the text Lorenzo proposed (later in this thread):
>
>    Addresses received via DHCPv6 do not have any associated reachability
>    information. In order to avoid the problems described in [RFC4943],
>    hosts MUST NOT assume that any IPv6 addresses are reachable on-link
>    as a result of receiving an IA_NA or IA_TA; IPv6 addresses obtained
>    from IA_NA or IA_TA MUST NOT be configured with any prefix length
>    except /128.
>
> I agree with this statement per se, but I think this is not
> sufficient, since it doesn't (clearly) answer the question of what the
> operator should do if they want to use DHCPv6-based address assignment
> in an isolated single-link (or "subnet") network.  The
> "architecturally correct" answer will be that they should deploy a
> node (which would probably be collocated on the same node as the
> DHCPv6 server) that sends RAs with router lifetime being 0 and with
> appropriate on-link prefix(es).

I agree that a recommendation should be given about - if - the DHCPv6 is
used to allocate addresses. Currently neither spec nor deployment is
functioning correctly when DHCPv6 is in place.

But, a Router-DHCPv6Server with router lifetime 0 and on-link prefix
will make think the Host this is not a default router and it should
SLAAC its address (maybe in addition to requesting one from DHCPv6). Is
this what is meant by the above?

Another suggestion on another hand is to have DHCPv6 deliver a prefix
length together with the address, and a default route. That'd be a form
of independence, and avoid '/64' CIDR-breaking assumptions.

Or maybe just add prefixlen to DHCPv6 and see how deployment goes, and
check back later.

Alex



   This may be obvious for those
> protocol-savvy people, but I suspect it's too subtle and should be
> explained explicitly for many ordinary people.  Whether this should be
> in 3315bis or some other DHCPv6-related document is a different
> question, though.
>
> --
> JINMEI, Tatuya
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Thu Apr  2 00:20:56 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235151B2B96 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 tFzRnMBm6oib for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:20:46 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 57D211B2B94 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 00:20:46 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.61] (88-111-169-158.dynamic.dsl.as9105.com [88.111.169.158]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 456B11BC3E for <dhcwg@ietf.org>; Thu,  2 Apr 2015 07:20:42 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <551CE97E.4020504@gmail.com>
Date: Thu, 2 Apr 2015 08:20:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/9h095yD7AoyLz39kZpnlJj9qDno>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 07:20:55 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>>> So that is also 'reachable', but not neighbor.
>>=20
>> But it may well be a neighbour. It's not that uncommon to have
>> multiple IPv4 subnets on one link. To handle this means either
>> sending all inter-subnet traffic through a router, or configuring
>> additional routing table entries on each device.
>=20
> So that is is a neighbor in Ethernet terms, but is not a neighbor in =
ND
> terms.

Eh ?
How is it not a neighbour in ND terms ?


> [...]
>>> Distinction: ok for /64, but if it's a /128 then it wouldn't have
>>> neighbors (/128 can only be on one end, and that something can't be
>>> a link).
>>=20
>> NO You **CAN** have a "/128" and have neighbours.
>=20
> These are Ethernet neighbors, but they are not ND neighbors.  ND works
> with a multicast scope.  Whoever is in that scope is a neighbor,
> otherwise it is not a neighbor.

OK, so you send out your multicast packet, it arrives at another node, =
that node responds. How is that not a neighbour ?

>> It would probably help if one of the experts clarified this.
>=20
> I agree.

At this point, I've been looking at RFC 4861  =
http://tools.ietf.org/html/rfc4861
Here are a couple of definitions from it which might clear things up a =
little, terminology wise :-)

   reachability
               - whether or not the one-way "forward" path to a neighbor
                 is functioning properly.  In particular, whether
                 packets sent to a neighbor are reaching the IP layer on
                 the neighboring machine and are being processed
                 properly by the receiving IP layer.  For neighboring
                 routers, reachability means that packets sent by a
                 node's IP layer are delivered to the router's IP layer,
                 and the router is indeed forwarding packets (i.e., it
                 is configured as a router, not a host).  For hosts,
                 reachability means that packets sent by a node's IP
                 layer are delivered to the neighbor host's IP layer.

That pretty much seems to me to be saying that for nodes, reachability =
means "I can send a packet on this link and it will arrive at the =
neighbour without the help of a router".

   on-link     - an address that is assigned to an interface on a
                 specified link.  A node considers an address to be on-
                 link if:

                    - it is covered by one of the link's prefixes (e.g.,
                      as indicated by the on-link flag in the Prefix
                      Information option), or

                    - a neighboring router specifies the address as the
                      target of a Redirect message, or

                    - a Neighbor Advertisement message is received for
                      the (target) address, or

                    - any Neighbor Discovery message is received from
                      the address.

   off-link    - the opposite of "on-link"; an address that is not
                 assigned to any interfaces on the specified link.

Which again seems to be saying that if an address is in any prefix given =
to me in an RA with the right flag set, OR if I hear from another node =
via ND, then the address is on-link.


From nobody Thu Apr  2 00:27:07 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF4BD1B2B9A for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 xjrDsQqxnX2Z for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:27:04 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D00341B2B99 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 00:27:04 -0700 (PDT)
Received: by iebmp1 with SMTP id mp1so55442249ieb.0 for <dhcwg@ietf.org>; Thu, 02 Apr 2015 00:27:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Kea2efzYTbGI9wRaLGJE6fbDdHORzuwv26dewpj7FBQ=; b=lMS3wzSQ1UMVb7sQr5sOlV4jUhlUkPIJZAUUu0jSLFD+ejeKpQFpEs3ZoiFodgKIBX KVmTvjZ8Vqsz90KlC16DQfEv610OK8UP1C2QgCvPNRE59fBWqZnPKcT+lSDYpvH3jFF6 aTyArVAk7z61//7jf9wv+u3/zGboUzmdi4iLy2HvBAIUWKMsGC1b/oA2q8+gq2o+E7DB LjbaCJl8IEmUOMFxmJZunkFg9xNdjOhv9N/W5pkRpC91PT/k5GXUoZ3OrTa2oXQgWRuY wvdwLKTF3i2EtdffV0E6KnK8MNNZ/f7O05Sisjdas6Jonx6QWmb70inqrJcgOlQssjMx HuGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Kea2efzYTbGI9wRaLGJE6fbDdHORzuwv26dewpj7FBQ=; b=a7bg5bvAm19l8vbrrecJZBENHBK1W/e/krV7EdcEI3XYtM3uuciai7U8OMk9E6tfmD ChLQKr0r6ViU3W2rOdyGVXMAQkF4tZe7we37nSjAKBOQ4Enzyh6iR62TClNuGhu6USVR zWWiBuyvvY9IWxezxhqqP0CnFX+qT4hKimyei25hXFyKDDj5f6wobZuoxQyGeEcJ3qpG OfzlNXnL95a2ADg6UzvP6q2TV1/2ZDMyz9EvOYoTqUwrDzqexloXr/+SqqtG437NzNsC uaavdH4/4UV1MpMBXO3B9ug1hNSQ1pHUxWJ0PtPtDL85RjhvOImYJgPeNLYMqPgO1AzV f8eQ==
X-Gm-Message-State: ALoCoQkeicl/8pNtEUkliDYBMaINMJ+IIU1qM1Qk53JuVsOf+bXu4QTvePmFTeg4mRq0C8XsPmqn
X-Received: by 10.107.12.96 with SMTP id w93mr35848268ioi.10.1427959624240; Thu, 02 Apr 2015 00:27:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Thu, 2 Apr 2015 00:26:43 -0700 (PDT)
In-Reply-To: <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 2 Apr 2015 16:26:43 +0900
Message-ID: <CAKD1Yr2srz1Cc=HzXBmF=7na6MHzmjzUKCVOiaMePtXpJcw-CA@mail.gmail.com>
To: Simon Hobson <linux@thehobsons.co.uk>
Content-Type: multipart/alternative; boundary=001a113ecb8c2834c60512b8c2a1
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/P2RsjfQrdT68RiFtN-CKdlQT5CU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 07:27:06 -0000

--001a113ecb8c2834c60512b8c2a1
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 1, 2015 at 10:21 PM, Simon Hobson <linux@thehobsons.co.uk>
wrote:

> Well actually, the "/128" is an artificial construct required to work
> around the implementations which (incorrectly) require every address to
> have a subnet mask. If correctly implemented, you have "an address" (or
> multiple addresses, but lets just consider one for now).
>

Actually, I don't see it as incorrect, but rather as a convenience.
"2001:db8::1/64" is a compact notation that allows one string to express
both an address (2001:db8::1) and a directly-connected route
(2001:db8::/64). The special case "2001:db8::1/128" a special case that
expresses only the address.

--001a113ecb8c2834c60512b8c2a1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 1, 2015 at 10:21 PM, Simon Hobson <span dir=3D"ltr">&lt;<a href=3D"=
mailto:linux@thehobsons.co.uk" target=3D"_blank">linux@thehobsons.co.uk</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bor=
der-left-style:solid;padding-left:1ex">Well actually, the &quot;/128&quot; =
is an artificial construct required to work around the implementations whic=
h (incorrectly) require every address to have a subnet mask. If correctly i=
mplemented, you have &quot;an address&quot; (or multiple addresses, but let=
s just consider one for now).<br></blockquote><div><br></div><div>Actually,=
 I don&#39;t see it as incorrect, but rather as a convenience. &quot;2001:d=
b8::1/64&quot; is a compact notation that allows one string to express both=
 an address (2001:db8::1) and a directly-connected route (2001:db8::/64). T=
he special case &quot;2001:db8::1/128&quot; a special case that expresses o=
nly the address.</div></div></div></div>

--001a113ecb8c2834c60512b8c2a1--


From nobody Thu Apr  2 00:37:33 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB4FE1A8961 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 pb-OlkFdSqK2 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 00:37:31 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5036D1A895E for <dhcwg@ietf.org>; Thu,  2 Apr 2015 00:37:30 -0700 (PDT)
Received: by iedfl3 with SMTP id fl3so70355434ied.1 for <dhcwg@ietf.org>; Thu, 02 Apr 2015 00:37:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GR8BuHE9BozPo3OC+HzsUPIu2yghPZjOJWyjP9jtWoc=; b=gzpJxH7eMhFxTpSbegafjBR7WXmRJL5evSWBEfz9bHuQGKT3IdG/+PrHGWDea3r3Vb sbRRcIyv2n7Wn4F8gcr1XwrLn2xfNTp1NK/uAWJZNMh8YCIxpjdWdRD66+lDZl3Ymrfl /PYh2jlxn19OuT02IJPdXwdGLyaW8D7Dc9AA0+t0T6E5iYPDUGZdK67usnE+UH8v7YHO QMaaWZXfKBC/C3i8M4yRhcIi+0rq7CeNRVRzKpkVtMevz/rV5OJKUzSxI97f9ki2nPsD 61qvdsaf6kd5dttxzJHDi0gldHcIN4gKNyTSu5K+9FNAoB9yDk4kSEOADwxda3Gu9OLG FAvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=GR8BuHE9BozPo3OC+HzsUPIu2yghPZjOJWyjP9jtWoc=; b=VA6j/ZEEmPYD7cxaiLWfvkjGekiv5ESKIAQo8Wr+1oWwQcgdmM1egPauQaaZUoffqL Qy5nPP9do8qSYiLhTiWvY9q/DvCJzj1xPbgF8eyX+dKYJES4fRHwIpjwSpF4GCFu3rHl c1Q6BsdRF6P6z0DLKY3kSDZP/4R43XP8DvSn839CyNaYUwu4Ho+fG9iiuFYMyniRNuvb e1TyNy2db92NCUE41/PtV2rUkBjzU1rKZnUd9OuXVyxEo4+rU1IDAn1dGz5EOB/jzSlH 798wx1zXkFIZ2ba3DD8fZGbf9uxrmhEUQkIkO+dPVftiXYvMEMIALuBIlxObEAJ9ooaX iLjQ==
X-Gm-Message-State: ALoCoQmgzyibpGmz3Nj76Flgqe0VMUD+ScbQS2uX3uhwZFfCoD3QheQ6s3tfMAF+J6kPc1Dz96gI
X-Received: by 10.43.64.203 with SMTP id xj11mr80898586icb.54.1427960249499; Thu, 02 Apr 2015 00:37:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Thu, 2 Apr 2015 00:37:09 -0700 (PDT)
In-Reply-To: <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 2 Apr 2015 16:37:09 +0900
Message-ID: <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary=bcaec51b1ef36d073c0512b8e7a3
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/bcRHZA9TNRI0PkYmx1M0uGtpivE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 07:37:32 -0000

--bcaec51b1ef36d073c0512b8e7a3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 2, 2015 at 2:21 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinme=
i@wide.ad.jp> wrote:
>
> it doesn't (clearly) answer the question of what the
> operator should do if they want to use DHCPv6-based address assignment
> in an isolated single-link (or "subnet") network.  The
> "architecturally correct" answer will be that they should deploy a
> node (which would probably be collocated on the same node as the
> DHCPv6 server) that sends RAs with router lifetime being 0 and with
> appropriate on-link prefix(es).


That is the correct answer, yes. By itself, an IPv6 address assigned via
IA_NA or IA_TA cannot be used for anything. Perhaps we can just clarify it
here by noting the following:

Addresses received via DHCPv6 do not have any associated reachability
information. In order avoid the problems described in [RFC4943], hosts MUST
NOT assume that any IPv6 destinations are reachable on-link as a result of
receiving an IA_NA or IA_TA. In order to communicate to any destination
that is not a link-local address, the host must also have obtained
reachability information by other means such as a Router Advertisement or
manual configuration.

--bcaec51b1ef36d073c0512b8e7a3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 2, 2015 at 2:21 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jinmei@wide.ad.jp" target=3D"_blank">jinmei@=
wide.ad.jp</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">it doesn&#39;t (clearly) a=
nswer the question of what the<br>
operator should do if they want to use DHCPv6-based address assignment<br>
in an isolated single-link (or &quot;subnet&quot;) network.=C2=A0 The<br>
&quot;architecturally correct&quot; answer will be that they should deploy =
a<br>
node (which would probably be collocated on the same node as the<br>
DHCPv6 server) that sends RAs with router lifetime being 0 and with<br>
appropriate on-link prefix(es).</blockquote><div><br></div><div>That is the=
 correct answer, yes. By itself, an IPv6 address assigned via IA_NA or IA_T=
A cannot be used for anything. Perhaps we can just clarify it here by notin=
g the following:</div><div><br></div><div><div>Addresses received via DHCPv=
6 do not have any associated reachability information. In order avoid the p=
roblems described in [RFC4943], hosts MUST NOT assume that any IPv6 destina=
tions are reachable on-link as a result of receiving an IA_NA or IA_TA. In =
order to communicate to any destination that is not a link-local address, t=
he host must also have obtained reachability information by other means suc=
h as a Router Advertisement or manual configuration.</div></div></div></div=
></div>

--bcaec51b1ef36d073c0512b8e7a3--


From nobody Thu Apr  2 02:09:50 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 916371B2C11 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 02:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 DgRbLeNIhUP1 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 02:09:48 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 79E041B2C10 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 02:09:48 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id A34BB1BC3E for <dhcwg@ietf.org>; Thu,  2 Apr 2015 09:09:44 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com>
Date: Thu, 2 Apr 2015 10:09:44 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/6NAbZwEo7Z7N3a3_WRYm3IytJFk>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 09:09:49 -0000

Something has just occurred to me ...
=46rom memory (and I stand to be corrected), (IPv6) clients don't use =
DHCP unless they get RAs with the managed flag set ?
So if there are no routers, there'll be no RAs, so no managed flag, so =
clients won't use DHCP to get addresses.

Does that therefore mean that the case mentioned earlier - how to use =
DHCP assigned addresses without any prefix information from RAs - is =
moot since the absence of routers implies that DHCP won't get used ?


From nobody Thu Apr  2 02:14:57 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A70A1B2C15 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 02:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 NRcc46o_jxAL for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 02:14:52 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E55A1B2C11 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 02:14:51 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t329EmwM005018 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 11:14:48 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 48D6E205EEC for <dhcwg@ietf.org>; Thu,  2 Apr 2015 11:15:43 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 40B83205EB5 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 11:15:43 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t329EDlf002631 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 11:14:48 +0200
Message-ID: <551D0865.9070308@gmail.com>
Date: Thu, 02 Apr 2015 11:14:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk>
In-Reply-To: <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/tip9LDYtw5g6fNymtYOjF67QFdI>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 09:14:56 -0000

Le 02/04/2015 09:20, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>>> So that is also 'reachable', but not neighbor.
>>>
>>> But it may well be a neighbour. It's not that uncommon to have
>>> multiple IPv4 subnets on one link. To handle this means either
>>> sending all inter-subnet traffic through a router, or
>>> configuring additional routing table entries on each device.
>>
>> So that is is a neighbor in Ethernet terms, but is not a neighbor
>> in ND terms.
>
> Eh ? How is it not a neighbour in ND terms ?

Right, I think I was wrong on that.

>
>
>> [...]
>>>> Distinction: ok for /64, but if it's a /128 then it wouldn't
>>>> have neighbors (/128 can only be on one end, and that something
>>>> can't be a link).
>>>
>>> NO You **CAN** have a "/128" and have neighbours.
>>
>> These are Ethernet neighbors, but they are not ND neighbors.  ND
>> works with a multicast scope.  Whoever is in that scope is a
>> neighbor, otherwise it is not a neighbor.
>
> OK, so you send out your multicast packet, it arrives at another
> node, that node responds. How is that not a neighbour ?

Right.

I think I meant to say they are not neighbors on the same subnet,
although yes they are neighbors in ND terms and neighbors in the same
Ethernet.

In that sense, one can't have an address with prefixlen /128 and have
any neighbor in that /128 subnet, there is no place left.  Someone with
a /127 could have only one other neighbor (these are the point to point
links).

One could say that one has an address A with prefix length /128, and be
in a /64 subnet.  But that would make little sense if any to have a
prefix length /128 and be in a /64 subnet, because 128!=64.

>>> It would probably help if one of the experts clarified this.
>>
>> I agree.
>
> At this point, I've been looking at RFC 4861
> http://tools.ietf.org/html/rfc4861 Here are a couple of definitions
> from it which might clear things up a little, terminology wise :-)
>
> reachability - whether or not the one-way "forward" path to a
> neighbor is functioning properly.

Thanks for the pointer.  I can tell that this is not what is meant by
reachability in other contexts, like in Mobile IP.

A "forward" path to a neighbor makes little sense because that path is
0-hop away, forward is same as backward in most links, although some
assymmetry in bandwidth may be felt on wireless links.

> In particular, whether packets sent to a neighbor are reaching the IP
> layer on the neighboring machine and are being processed properly by
> the receiving IP layer. For neighboring routers, reachability means
> that packets sent by a node's IP layer are delivered to the router's
> IP layer, and the router is indeed forwarding packets (i.e., it is
> configured as a router, not a host).

I think it means routers that specifically are IP neighbors to that
Host, not just arbitrary neighboring routers.

I think "node's IP layer" is actually meant to say "Host's IP layer",
because a "node" can be either a "Router" or a "Host" or both (RFC ref).

> For hosts, reachability means that packets sent by a node's IP layer
> are delivered to the neighbor host's IP layer.

And unreachability means that node's IP layer are _not_ delivered to the
neighbor host's IP layer?

> That pretty much seems to me to be saying that for nodes,
> reachability means "I can send a packet on this link and it will
> arrive at the neighbour without the help of a router".

The help of a router could happen in at least two ways: forward and ICMP
redirect: which one do you think?  Second, do you think that when a
router _is_ involved then we can call the two neighbors to be "unreachable"?

>
> on-link     - an address that is assigned to an interface on a
> specified link.  A node considers an address to be on- link if:
>
> - it is covered by one of the link's prefixes (e.g., as indicated by
>  the on-link flag in the Prefix Information option), or
>
> - a neighboring router specifies the address as the target of a
> Redirect message, or
>
> - a Neighbor Advertisement message is received for the (target)
> address, or
>
> - any Neighbor Discovery message is received from the address.
>
> off-link    - the opposite of "on-link"; an address that is not
> assigned to any interfaces on the specified link.

This off-link definition is not self-contained - it does not use a
"specified link."

We never say that address A-and-link1 is off-link.

Saying A is off-link is not a correct use of the definion above because
it does not specify the "specified link".

> Which again seems to be saying that if an address is in any prefix
> given to me in an RA with the right flag set, OR if I hear from
> another node via ND, then the address is on-link.

This is just an appearance.

The term off-link is used several times throughout RFC4861 without 
actually respecting its own definition in that RFC proper.

For example, the RFC says:
> A router acting on behalf of a mobile node that has moved off-link
> could potentially act as a proxy for the mobile node.

The term "off-link" is used, but the "specified link" (per definition) 
is not present.  Moreover, the definition tells "off-link" is an 
"address", whereas in this use this "off-link" is simply a qualifier of 
the mouvement.

We can understand the phrase, the node moved out of the link, off of the 
link; but the term "off-link" is not well defined.

Furthe, RFC says:
>     L              1-bit on-link flag.  When set, indicates that this
>                      prefix can be used for on-link determination.  When
>                      not set the advertisement makes no statement about
>                      on-link or off-link properties of the prefix.  In
>                      other words, if the L flag is not set a host MUST
>                      NOT conclude that an address derived from the
>                      prefix is off-link.  That is, it MUST NOT update a
>                      previous indication that the address is on-link.

This definition means that it means nothing.  It gives no indication. 
It's just like the M flag.

If L then something, otherwise nothing.  This is not what me as 
implementer would like to see.

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Thu Apr  2 04:52:35 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50F4D1B2C7F for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 04:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 8-pTWkS0m25Q for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 04:52:31 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 244B31B2C7C for <dhcwg@ietf.org>; Thu,  2 Apr 2015 04:52:30 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id B22881BC3E for <dhcwg@ietf.org>; Thu,  2 Apr 2015 11:52:24 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <551D0865.9070308@gmail.com>
Date: Thu, 2 Apr 2015 12:52:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/R_tuTry_TIjW1FWVVsOOWoWooiE>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 11:52:34 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>>>>> Distinction: ok for /64, but if it's a /128 then it wouldn't
>>>>> have neighbors (/128 can only be on one end, and that something
>>>>> can't be a link).
>>>>=20
>>>> NO You **CAN** have a "/128" and have neighbours.
>>>=20
>>> These are Ethernet neighbors, but they are not ND neighbors.  ND
>>> works with a multicast scope.  Whoever is in that scope is a
>>> neighbor, otherwise it is not a neighbor.
>>=20
>> OK, so you send out your multicast packet, it arrives at another
>> node, that node responds. How is that not a neighbour ?
>=20
> Right.
>=20
> I think I meant to say they are not neighbors on the same subnet,
> although yes they are neighbors in ND terms and neighbors in the same
> Ethernet.
>=20
> In that sense, one can't have an address with prefixlen /128 and have
> any neighbor in that /128 subnet, there is no place left.

That's correct, but it doesn't really matter.
What matters is "can we find the other node" and "can the other node =
find us". For example, I could come up with a rather bizarre network =
where every device has a random address but I assign no prefixes to it. =
Each device will (initially) have no concept of what other devices may =
be "local" to it - so every connection will have to be made via a router =
- ie to start off with, every other address but our own is "off-link".
Assuming the router knows about the other devices, when we open a =
connection by sending packets to the router, the router can tell us (via =
a redirect) about the other node being on-link. At this point, we then =
know to use ND to find the other node and it becomes on-link to us for =
as long as the neighbour information is kept active. This doesn't need =
*ANY* prefix information at all - only knowledge of a router we can use =
to send our packets out.

As I say, that's a rather contrived situation. For something a bit more =
run of the mill ... lets consider two subnets on the same link. When =
determining if the destination is on-link, we only need the destination =
address and a list of prefixes - our own address does not matter. If the =
destination address is within any of the prefixes we've been told is =
on-link, then we use ND to find it and talk to it. Once we've contacted =
that other device, it now knows that we're here - regardless of whether =
we are even in any of the prefixes.



>> on-link     - an address that is assigned to an interface on a
>> specified link.  A node considers an address to be on- link if:
>>=20
>> - it is covered by one of the link's prefixes (e.g., as indicated by
>> the on-link flag in the Prefix Information option), or
>>=20
>> - a neighboring router specifies the address as the target of a
>> Redirect message, or
>>=20
>> - a Neighbor Advertisement message is received for the (target)
>> address, or
>>=20
>> - any Neighbor Discovery message is received from the address.
>>=20
>> off-link    - the opposite of "on-link"; an address that is not
>> assigned to any interfaces on the specified link.
>=20
> This off-link definition is not self-contained - it does not use a
> "specified link."
>=20
> We never say that address A-and-link1 is off-link.
>=20
> Saying A is off-link is not a correct use of the definion above =
because
> it does not specify the "specified link".

I'm not quite sure what you're saying here. Any on/off-link =
determination has to be done per link. For a multihomed device, there =
will be other nodes that are on-link for one interface and off-link for =
another.
So we should in fact be saying things like "A is on-link for interface =
foo" and "A is off-link for interface bar". However, I think most of us =
are used to omitting certain information when working at higher levels - =
eg if I type "ping  <some address>" I normally won't specify an =
interface (link) to be used - I let the system work that out. So my only =
consideration would be "Is A on-link for any of my interfaces, or is it =
off-link for all of them". Of course there are times when it does =
matter, and then I'll specify either an interface or source address*.

* I actually tend to do that a lot on our own internal networks (mix of =
public and RFC1918) - for "historical reasons" we have some not very =
complicated but very irritating restrictions.

>> Which again seems to be saying that if an address is in any prefix
>> given to me in an RA with the right flag set, OR if I hear from
>> another node via ND, then the address is on-link.
>=20
> This is just an appearance.
>=20
> The term off-link is used several times throughout RFC4861 without =
actually respecting its own definition in that RFC proper.
>=20
> For example, the RFC says:
>> A router acting on behalf of a mobile node that has moved off-link
>> could potentially act as a proxy for the mobile node.
>=20
> The term "off-link" is used, but the "specified link" (per definition) =
is not present.  Moreover, the definition tells "off-link" is an =
"address", whereas in this use this "off-link" is simply a qualifier of =
the mouvement.
>=20
> We can understand the phrase, the node moved out of the link, off of =
the link; but the term "off-link" is not well defined.

Again, I think context is everything. For something that's "moved =
off-link", we can infer that it's no longer on the link it used to be =
on. If it were to appear "on-link" for some other link then that =
complicates matters, but I don't think that in context it is wrong.

> Furthe, RFC says:
>>    L              1-bit on-link flag.  When set, indicates that this
>>                     prefix can be used for on-link determination.  =
When
>>                     not set the advertisement makes no statement =
about
>>                     on-link or off-link properties of the prefix.  In
>>                     other words, if the L flag is not set a host MUST
>>                     NOT conclude that an address derived from the
>>                     prefix is off-link.  That is, it MUST NOT update =
a
>>                     previous indication that the address is on-link.
>=20
> This definition means that it means nothing.  It gives no indication. =
It's just like the M flag.
>=20
> If L then something, otherwise nothing.  This is not what me as =
implementer would like to see.

I can only see one issue - and without having digested the RFC I don't =
know if it's addressed.
If an RA sets the L bit, and then unsets it later, the above says that =
we carry on treating the prefix as local. How often is this likely to =
happen in practice ? I'm not sure I can envisage a network where it =
supports ND, but then changes (without any host links going down) into =
one where ND no longer works.

What comes to mind is if an RA from one router sets it, another router =
sends RA with it unset, and then the first router goes/has the prefix =
removed/whatever. Does a node keep track of which RAs it got from each =
router, does it then say that the prefix is now not local because the RA =
that set it as local has stopped and there's no other RA that has it set =
?
Conversely, if the above said that getting an RA with the L bit clear =
means you have to update the prefix information, the next question would =
be "what about multiple RAs for the same prefix with different states =
for the L bit ?"

As for "do nothing" being untenable - isn't that what a lot of =
programming is about ? Ie "if <condition> then do <something>". In this =
case it seems simple enough - if we get an RA with L set, and we already =
have a prefix in the table (for that link) with it unset, then set it in =
our table". The mechanism for it getting unset is for the prefix to get =
removed from the table =3D which will happen if the link "goes down", or =
if we stop getting any RAs with the prefix. As above, I can't think of =
any situation (other than admin cock-up !) where there would be any need =
to unset the local flag in the prefix table.


From nobody Thu Apr  2 05:20:55 2015
Return-Path: <kauer@biplane.com.au>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD681B2C32 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 02:52:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 Qxojg9V6HD1d for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 02:52:28 -0700 (PDT)
Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by ietfa.amsl.com (Postfix) with ESMTP id 92D201B2C30 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 02:52:27 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2CIBAANEB1V/7t/ZZYNT4NaVwWDFcJHhXcCR4FJAQEBAQEBhR0BAQQjZgsYAgImAgJXGYg3s35wmC0BAQEHAgEfgSGKCIUAFoJSgUUFlF+HYoxDBoYogiQcgWRbgkMBAQE
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.196]) ([150.101.127.187]) by ipmail04.adl6.internode.on.net with ESMTP; 02 Apr 2015 20:22:25 +1030
Message-ID: <1427968340.2822.53.camel@karl>
From: Karl Auer <kauer@biplane.com.au>
To: dhcwg@ietf.org
Date: Thu, 02 Apr 2015 20:52:20 +1100
In-Reply-To: <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4-0ubuntu2 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/PqV6ucZdq-rMQmhg_y0cyc2_vdo>
X-Mailman-Approved-At: Thu, 02 Apr 2015 05:20:54 -0700
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 09:52:31 -0000

On Thu, 2015-04-02 at 10:09 +0100, Simon Hobson wrote:
> From memory (and I stand to be corrected), (IPv6) clients don't use DHCP unless they get RAs with the managed flag set ?
> So if there are no routers, there'll be no RAs, so no managed flag, so clients won't use DHCP to get addresses.

I think people have been working on that for a bit, but my reading of
the RFC says that's wrong. The managed bit is informative only -
"addresses are available for this link via DHCP". There is no obligation
on the host to use DHCP to obtain an address. Same for the "O" flag - it
simply informs hosts on the link that ancillary information is available
via DHCP, there is no obligation on a host to obtain ancillary
information via DHCP.

Others have interpreted it as you did - that the presence of the M and O
flags impose a requirement that hosts use DHCP to obtain addresses and
ancillary information, I think that is wrong, because it leaves open
what the *absence* of those flags means. If an RA comes past with no M
flag, does a host have to drop it's DHCP-acquired address(es)
immediately? Or should it let them die naturally, i.e. wait out the
preferred and valid lifetimes it obtained with the addresses? What
should a host do if it obtained (say) nameserver information via DHCP
and an RA comes past with no M and no O flag? Should it forget its
nameserver information?

Treating the DHCP flags as informative avoids all those questions - once
an address is obtained via DHCP, you follow the rules - time it out
according to the preferred and valid lifetimes, just like any other
address.

Interpreting those flags as anything other than informative opens a
major can of worms. But TBH I have not been following recent discussion
on the matter, so maybe the worms have been tamed.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: 3C41 82BE A9E7 99A1 B931 5AE7 7638 0147 2C3C 2AC4
Old fingerprint: EC67 61E2 C2F6 EB55 884B E129 072B 0AF0 72AA 9882



From nobody Thu Apr  2 07:00:58 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E375B1A905D for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 07:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 rXGSSyGif6tT for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 07:00:55 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 74BD91A9057 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 07:00:55 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 2DD3C1BC3E for <dhcwg@ietf.org>; Thu,  2 Apr 2015 14:00:49 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <1427968340.2822.53.camel@karl>
Date: Thu, 2 Apr 2015 15:00:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/k0m8C8X2b5-G9meXMTrMlW3MTVc>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 14:00:57 -0000

On 2 Apr 2015, at 10:52, Karl Auer <kauer@biplane.com.au> wrote:

> On Thu, 2015-04-02 at 10:09 +0100, Simon Hobson wrote:
>> =46rom memory (and I stand to be corrected), (IPv6) clients don't use =
DHCP unless they get RAs with the managed flag set ?
>> So if there are no routers, there'll be no RAs, so no managed flag, =
so clients won't use DHCP to get addresses.
>=20
> I think people have been working on that for a bit, but my reading of
> the RFC says that's wrong. The managed bit is informative only -
> "addresses are available for this link via DHCP". There is no =
obligation
> on the host to use DHCP to obtain an address.

I was assuming it's the other way round - unless you see an RA with a =
managed flag, then DHCP isn't available or isn't to be used. I'll =
confess that other than a very brief attempt some time ago, I've not =
tried DHCPv6 - when I tried it, devices* didn't seem to get an address =
and from watching discussion on other lists I put 2+2 together and got =
the answer 5, you need the managed flag in an RA for a node to use DHCP.

* In particular my Mac which didn't even seem to attempt to get an =
address.

That was a while ago, and I've not had the time to try it again since - =
home is working, and lets just say there's little enthusiasm for IPv6 at =
work :-(


However, where I am uneasy is the concept of "information" like this. A =
node can figure out whether there's a DHCP server present or not. Having =
a flag that says DCHP is available but you don't have to use it is not =
very meaningful IMO - it doesn't say anything more than what can be =
inferred by the presence of a DHCP server.
Or have I missed something ?


From nobody Thu Apr  2 08:01:15 2015
Return-Path: <rdroms@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B9B1B2CE0 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 08:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 14N9ClSstU1G for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 08:01:12 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 622A11B2C8D for <dhcwg@ietf.org>; Thu,  2 Apr 2015 08:01:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2292; q=dns/txt; s=iport; t=1427986872; x=1429196472; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=7XC3t23fMCkFSBu+4Nfq5a2EyRcagr+Ft2oK3CLhe70=; b=EjlBWTrh/HHFKOQ4rby1AKjuneRiEkojOKIhK7s3L/sJWlBT01ao7poH mNOkEEsi+2u+z1cWPaQ5sGStXDxQs9WQTbZ3+SP0fasWvGR7xbDYrAogD IODfLzqQnDuLk74tEtUf5Deg1LJyKX+Hpg1aeR+HNbw5CCqxPLXKrPxii I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AbDgDVWB1V/4YNJK1cgwhSXAXFUwqFcwJHfkwBAQEBAQF+hB4BAQEDAQEBATc0CwULAgEIDgoeECcLJQIEDgWIJwgNzhIBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIsphC4YMweDF4EWBZBqigCBHYM0j3cig25vgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.11,511,1422921600"; d="scan'208";a="405587055"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-1.cisco.com with ESMTP; 02 Apr 2015 15:01:11 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t32F1BwY030824 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 15:01:11 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.86]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0195.001; Thu, 2 Apr 2015 10:01:11 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: Simon Hobson <linux@thehobsons.co.uk>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQaKj80muBJGbcNkGotfXc7mP6I504wzCAgADu9oCAABneAIAAC+cAgABFaoCAABDfAA==
Date: Thu, 2 Apr 2015 15:01:10 +0000
Message-ID: <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk>
In-Reply-To: <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.214.60]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <284B6F97C131D34CB50A11EC2DA1B04F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ZWWOOrio85Ihbtc8VirogVOv8tE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 15:01:14 -0000

> On Apr 2, 2015, at 10:00 AM 4/2/15, Simon Hobson <linux@thehobsons.co.uk>=
 wrote:
>=20
>=20
> On 2 Apr 2015, at 10:52, Karl Auer <kauer@biplane.com.au> wrote:
>=20
>> On Thu, 2015-04-02 at 10:09 +0100, Simon Hobson wrote:
>>> From memory (and I stand to be corrected), (IPv6) clients don't use DHC=
P unless they get RAs with the managed flag set ?
>>> So if there are no routers, there'll be no RAs, so no managed flag, so =
clients won't use DHCP to get addresses.
>>=20
>> I think people have been working on that for a bit, but my reading of
>> the RFC says that's wrong. The managed bit is informative only -
>> "addresses are available for this link via DHCP". There is no obligation
>> on the host to use DHCP to obtain an address.
>=20
> I was assuming it's the other way round - unless you see an RA with a man=
aged flag, then DHCP isn't available or isn't to be used. I'll confess that=
 other than a very brief attempt some time ago, I've not tried DHCPv6 - whe=
n I tried it, devices* didn't seem to get an address and from watching disc=
ussion on other lists I put 2+2 together and got the answer 5, you need the=
 managed flag in an RA for a node to use DHCP.
>=20
> * In particular my Mac which didn't even seem to attempt to get an addres=
s.

The semantics of the M/O bits - and, please, let's not revisit that /dev/nu=
ll discussion? - are, at this point, informative only.  RFC 7084, for examp=
le, specifies that a CE router uses DHCPv6 on its WAN link regardless of wh=
ether or not it receives an RA with the M bit set.

- Ralph

>=20
> That was a while ago, and I've not had the time to try it again since - h=
ome is working, and lets just say there's little enthusiasm for IPv6 at wor=
k :-(
>=20
>=20
> However, where I am uneasy is the concept of "information" like this. A n=
ode can figure out whether there's a DHCP server present or not. Having a f=
lag that says DCHP is available but you don't have to use it is not very me=
aningful IMO - it doesn't say anything more than what can be inferred by th=
e presence of a DHCP server.
> Or have I missed something ?
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Thu Apr  2 10:23:51 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57DCF1AD289 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 10:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 0hDPUXlY6r7O for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 10:23:47 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B6D91A1B48 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 10:23:46 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t32HNifp003697 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 19:23:44 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E169E207558 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 19:24:39 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id D96FD207486 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 19:24:39 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t32HNMuF029417 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 19:23:44 +0200
Message-ID: <551D7B09.5000601@gmail.com>
Date: Thu, 02 Apr 2015 19:23:21 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk>
In-Reply-To: <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ZABp0T6H9oBrwbMQrRqOcS_cxmo>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 17:23:50 -0000

Le 02/04/2015 13:52, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>>>>> Distinction: ok for /64, but if it's a /128 then it
>>>>>> wouldn't have neighbors (/128 can only be on one end, and
>>>>>> that something can't be a link).
>>>>>
>>>>> NO You **CAN** have a "/128" and have neighbours.
>>>>
>>>> These are Ethernet neighbors, but they are not ND neighbors.
>>>> ND works with a multicast scope.  Whoever is in that scope is
>>>> a neighbor, otherwise it is not a neighbor.
>>>
>>> OK, so you send out your multicast packet, it arrives at another
>>> node, that node responds. How is that not a neighbour ?
>>
>> Right.
>>
>> I think I meant to say they are not neighbors on the same subnet,
>> although yes they are neighbors in ND terms and neighbors in the
>> same Ethernet.
>>
>> In that sense, one can't have an address with prefixlen /128 and
>> have any neighbor in that /128 subnet, there is no place left.
>
> That's correct, but it doesn't really matter. What matters is "can we
> find the other node" and "can the other node find us".

Ok, so.

> For example, I could come up with a rather bizarre network where
> every device has a random address but I assign no prefixes to it.

Ok.

> Each device will (initially) have no concept of what other devices
> may be "local" to it - so every connection will have to be made via
> a router - ie to start off with, every other address but our own is
> "off-link".

This is too tortuous to my mind.  It means that the address is not on
any link and it is not "off-link" in that RFC's terms either.

It could have better been "off subnet" or "out of any subnet".

> Assuming the router knows about the other devices, when we open a
> connection by sending packets to the router, the router can tell us
> (via a redirect) about the other node being on-link. At this point,
> we then know to use ND to find the other node and it becomes on-link
>  to us for as long as the neighbour information is kept active. This
>  doesn't need *ANY* prefix information at all - only knowledge of a
> router we can use to send our packets out.

Well, yes and no.

Yes in that it can work as you describe.  And that prefix lengths must
be there during that operation.  The lenghts involves are /128 and /0.
If they are not there it does not work.  In this sense: yes, a DHCPv6
/128 allocation to a Client can easily mean that Client _is_ reachable. 
  (this is how some point-to-point links work anyways).

No in that Redirect does not tell whether somebody is onlink or not, it
just redirects to a better first-hop router, which will presumably be
that other neighbor-on-link (but not neighbor-on-same-subnet):
RFC says:
>
> 4.5. Redirect Message Format
>
>
> Routers send Redirect packets to inform a host of a better first-hop
> node on the path to a destination.  Hosts can be redirected to a
> better first-hop router but can also be informed by a redirect that
> the destination is in fact a neighbor.

"in fact a neighbor"?  It is a neighbor on the same link, but it is not
a neighbour in the same subnet, because there is no subnet.  Is a 
neighbor "on-link"?  We dont know.

In fact, this entire terminology of "on-link determination" is not
described anywhere.  You have some bits here and there about who
contributes to it, but there is no section telling that is the on-link
determination operation.  With hands empty you  can only  suppose what
it is, and implement in a certain manner (longest match dst to rt table
entries, if found then ND dst and send packet to that MAC otherwise ND
the default router's IP address and send packet to that other MAC
address).  That's how I believe it should be but no document tells how
it should be.  It just says "on-link determination".

> As I say, that's a rather contrived situation. For something a bit
> more run of the mill ... lets consider two subnets on the same link.
>  When determining if the destination is on-link, we only need the
> destination address and a list of prefixes - our own address does not
> matter. If the destination address is within any of the prefixes
> we've been told is on-link,

When I type "route -6" there are some routes but there is not one that
says "this is on-link, this is not on-link".

> then we use ND to find it and talk to it. Once we've contacted that
> other device, it now knows that we're here - regardless of whether we
> are even in any of the prefixes.

Yes.

>
>
>
>>> on-link     - an address that is assigned to an interface on a
>>> specified link.  A node considers an address to be on- link if:
>>>
>>> - it is covered by one of the link's prefixes (e.g., as indicated
>>> by the on-link flag in the Prefix Information option), or
>>>
>>> - a neighboring router specifies the address as the target of a
>>> Redirect message, or
>>>
>>> - a Neighbor Advertisement message is received for the (target)
>>> address, or
>>>
>>> - any Neighbor Discovery message is received from the address.
>>>
>>> off-link    - the opposite of "on-link"; an address that is not
>>> assigned to any interfaces on the specified link.
>>
>> This off-link definition is not self-contained - it does not use a
>> "specified link."
>>
>> We never say that address A-and-link1 is off-link.
>>
>> Saying A is off-link is not a correct use of the definion above
>> because it does not specify the "specified link".
>
> I'm not quite sure what you're saying here. Any on/off-link
> determination has to be done per link.

What is precisely the "on-link determination"? (some RFC section titled 
so that I missed?)

> For a multihomed device, there will be other nodes that are on-link
> for one interface and off-link for another. So we should in fact be
> saying things like "A is on-link for interface foo" and "A is
> off-link for interface bar".

Ok.

> However, I think most of us are used to omitting certain information
>  when working at higher levels - eg if I type "ping  <some address>"
> I normally won't specify an interface (link) to be used - I let the
> system work that out.

And, of course, it can figure it out only if it is not link-local.  If
you ping an LL address you have to say a -I iface because the computer 
can't determine the interface from its rt table (it has an fe80::/10 
entry for each interface).

> So my only consideration would be "Is A on-link for any of my
> interfaces, or is it off-link for all of them". Of course there are
> times when it does matter, and then I'll specify either an interface
> or source address*.

I can understand your interpretation in your setting.

In my setting I avoid saying something is "on-link" or "off-link",
because I know people have different understandings for each.

>
> * I actually tend to do that a lot on our own internal networks (mix
>  of public and RFC1918) - for "historical reasons" we have some not
> very complicated but very irritating restrictions.
>
>>> Which again seems to be saying that if an address is in any
>>> prefix given to me in an RA with the right flag set, OR if I hear
>>> from another node via ND, then the address is on-link.
>>
>> This is just an appearance.
>>
>> The term off-link is used several times throughout RFC4861 without
>>  actually respecting its own definition in that RFC proper.
>>
>> For example, the RFC says:
>>> A router acting on behalf of a mobile node that has moved
>>> off-link could potentially act as a proxy for the mobile node.
>>
>> The term "off-link" is used, but the "specified link" (per
>> definition) is not present.  Moreover, the definition tells
>> "off-link" is an "address", whereas in this use this "off-link" is
>>  simply a qualifier of the mouvement.
>>
>> We can understand the phrase, the node moved out of the link, off
>> of the link; but the term "off-link" is not well defined.
>
> Again, I think context is everything. For something that's "moved
> off-link", we can infer that it's no longer on the link it used to be
> on. If it were to appear "on-link" for some other link then that
> complicates matters, but I don't think that in context it is wrong.

It is not wrong, it is just misleading and not self-containing; it is
not implementable in an interoperable manner.

>
>> Furthe, RFC says:
>>> L              1-bit on-link flag.  When set, indicates that
>>> this prefix can be used for on-link determination.  When not set
>>> the advertisement makes no statement about on-link or off-link
>>> properties of the prefix.  In other words, if the L flag is not
>>> set a host MUST NOT conclude that an address derived from the
>>> prefix is off-link.  That is, it MUST NOT update a previous
>>> indication that the address is on-link.
>>
>> This definition means that it means nothing.  It gives no
>> indication. It's just like the M flag.
>>
>> If L then something, otherwise nothing.  This is not what me as
>> implementer would like to see.
>
> I can only see one issue - and without having digested the RFC I
> don't know if it's addressed. If an RA sets the L bit, and then
> unsets it later, the above says that we carry on treating the prefix
>  as local. How often is this likely to happen in practice ? I'm not
> sure I can envisage a network where it supports ND, but then changes
>  (without any host links going down) into one where ND no longer
> works.
>
> What comes to mind is if an RA from one router sets it, another
> router sends RA with it unset, and then the first router goes/has the
> prefix removed/whatever. Does a node keep track of which RAs it got
> from each router, does it then say that the prefix is now not local
> because the RA that set it as local has stopped and there's no other
> RA that has it set ? Conversely, if the above said that getting an RA
> with the L bit clear means you have to update the prefix information,
> the next question would be "what about multiple RAs for the same
> prefix with different states for the L bit ?"

Right, the dynamics of the L bit are hardly known.  I dont see it, and I
dont set it.

>
> As for "do nothing" being untenable - isn't that what a lot of
> programming is about ?

Right, sorry, I miss-wrote that if statement.

I meant to say that when L is unset we dont know what to do (we dont
know whether that is onlink or offlink).  As such it's sent for no
reason and should be ignored.

> Ie "if <condition> then do <something>". In this case it seems simple
> enough - if we get an RA with L set, and we already have a prefix in
> the table (for that link) with it unset, then set it in our table".

But the spec does not tell that you should do it that way.  It says if L
is unset then you dont know.

 > The mechanism for it getting unset is
> for the prefix to get removed from the table = which will happen if
> the link "goes down", or if we stop getting any RAs with the prefix.
> As above, I can't think of any situation (other than admin cock-up
> !) where there would be any need to unset the local flag in the
> prefix table.

There is no reason for that.  Entries will expire by themselves anyways, 
no need to announce going down.  Expiration can be planned be quicker by 
using shorter lifetimes, too.

Sorry for bashing too much at this.  I remember a long discussion about 
the L bit and the conclusion is so inconclusive that since then I still 
do not see the L bit unset.

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Thu Apr  2 10:38:43 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED0B1B2D65 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 10:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 0M3GyOuSiPkt for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 10:38:38 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98A021A01E7 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 10:38:38 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t32Hcbg1007582 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 19:38:37 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 863B820768D for <dhcwg@ietf.org>; Thu,  2 Apr 2015 19:39:32 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 7E19D205B8B for <dhcwg@ietf.org>; Thu,  2 Apr 2015 19:39:32 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t32HcBsh012793 for <dhcwg@ietf.org>; Thu, 2 Apr 2015 19:38:36 +0200
Message-ID: <551D7E83.1050704@gmail.com>
Date: Thu, 02 Apr 2015 19:38:11 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk>
In-Reply-To: <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/zAElIKLYhwhd1UvH7FZXhApE_Uc>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 17:38:41 -0000

Le 02/04/2015 16:00, Simon Hobson a écrit :
>
> On 2 Apr 2015, at 10:52, Karl Auer <kauer@biplane.com.au> wrote:
>
>> On Thu, 2015-04-02 at 10:09 +0100, Simon Hobson wrote:
>>> From memory (and I stand to be corrected), (IPv6) clients don't
>>> use DHCP unless they get RAs with the managed flag set ? So if
>>> there are no routers, there'll be no RAs, so no managed flag, so
>>> clients won't use DHCP to get addresses.
>>
>> I think people have been working on that for a bit, but my reading
>> of the RFC says that's wrong. The managed bit is informative only -
>> "addresses are available for this link via DHCP". There is no
>> obligation on the host to use DHCP to obtain an address.
>
> I was assuming it's the other way round - unless you see an RA with
> a managed flag, then DHCP isn't available or isn't to be used.

The way I see it is  like this: if M flag is set then there is no prefix
in RA, and DHCPv6 is there.  This makes sense, and it is implemented in
a cellular system.

There are still problems with this (def route missing, prefixlen
missing, DNS missing, etc), and I keep complaining about it at both
places: IETF and to operator.  IETF made 'M' unclear, made
DHCPv6-defroute to be architecturally wrong; Operator puts little trust
in DHCPv6' future.  That's how the situation stands.

> I'll confess that other than a very brief attempt some time ago, I've
> not tried DHCPv6 - when I tried it, devices* didn't seem to get an
> address and from watching discussion on other lists

I can say that with linux and bsd there are multiple opensource DHCPv6
implementations maintained and advancing.  I even heard of a new one
called kea.

> I put 2+2 together and got the answer 5, you need the managed flag
> in an RA for a node to use DHCP.

Right.  And I know RA implemementations that do.

>
> * In particular my Mac which didn't even seem to attempt to get an
> address.

Is there a DHCPv6 client for MAC?

> That was a while ago, and I've not had the time to try it again
> since - home is working, and lets just say there's little enthusiasm
> for IPv6 at work :-(

Right.  At other places there is much enthusiasm for DHCPv6 because it
ressembles to DHCPv4 for its controlling features.  Also,  since a /64
prefix surprisingly means much less than 2^64 addresses, and means one
and single subnet - only DHCPv6 can solve that.

> However, where I am uneasy is the concept of "information" like
> this. A node can figure out whether there's a DHCP server present or
> not. Having a flag that says DCHP is available but you don't have to
> use it is not very meaningful IMO - it doesn't say anything more
> than what can be inferred by the presence of a DHCP server.

I agree.

Certainly just like RS discovers routers the DHCPv6 Solicit discovers
DHCPv6 Servers, there is no difference.  I guess an M/O flag should be
removed altogether.

Alex

  Or have I
> missed something ?
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Thu Apr  2 11:05:59 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460981B2D9B for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 11:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 jvUD2FnyoHMc for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 11:05:57 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2633D1B2D8A for <dhcwg@ietf.org>; Thu,  2 Apr 2015 11:05:57 -0700 (PDT)
Received: by iebmp1 with SMTP id mp1so68079195ieb.0 for <dhcwg@ietf.org>; Thu, 02 Apr 2015 11:05:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UE+rc48Kt9Bqcwx6NTBu4BSkFBXJo8qgL5na7FcQo1Q=; b=bYp3Rb9KS7YkDQ1OPdDOkE6BZDYvVks+4Kf6Xig/6LLkey6rZzNMRKAVwjzNG4ckrA nfM2BR3dxrH8gyDlGF9QvQPGW42T6g59DZCEY02F7sPWuNrBF0PrPo4WLNElkv8HNTqI DMV5m7cJTg4T4umwM3OwRKTMpbqjkUeSAwMDK4TKx4hzD2kYUgvNIaqLgbf4GSB9XawM /F82f017lSRw5vLzfvIaqcEJQ7hBepJtp01C+T4NwefbBvONrA6X27L8DF0rp2nWHXwH vki8yEnLIxInWYtECJ2w+bRGRhafBLqDVW0Ef1y13IWfCheEq5Nyy/C7IaQM5vWrzoat h5Ow==
MIME-Version: 1.0
X-Received: by 10.50.18.49 with SMTP id t17mr21876019igd.3.1427997956432; Thu, 02 Apr 2015 11:05:56 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.21.3 with HTTP; Thu, 2 Apr 2015 11:05:56 -0700 (PDT)
In-Reply-To: <551CEC1F.3070006@gmail.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <551CEC1F.3070006@gmail.com>
Date: Thu, 2 Apr 2015 11:05:56 -0700
X-Google-Sender-Auth: nsGqIFTDj2yXoOl-9ZuPU7nlnCs
Message-ID: <CAJE_bqfAmTFJwVL3VTK+w6rSu_TPPPrmWet2nmi-YfcKyts3PA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/lvRqYOUC9mYtaYgd6lylhVYz8rs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 18:05:58 -0000

At Thu, 02 Apr 2015 09:13:35 +0200,
Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> > I agree with this statement per se, but I think this is not
> > sufficient, since it doesn't (clearly) answer the question of what the
> > operator should do if they want to use DHCPv6-based address assignment
> > in an isolated single-link (or "subnet") network.  The
> > "architecturally correct" answer will be that they should deploy a
> > node (which would probably be collocated on the same node as the
> > DHCPv6 server) that sends RAs with router lifetime being 0 and with
> > appropriate on-link prefix(es).
[...]
> But, a Router-DHCPv6Server with router lifetime 0 and on-link prefix
> will make think the Host this is not a default router and it should
> SLAAC its address (maybe in addition to requesting one from DHCPv6). Is
> this what is meant by the above?

Not at all.  I didn't mean to say anything about SLAAC in the above
"architecturally correct answer".

> Another suggestion on another hand is to have DHCPv6 deliver a prefix
> length together with the address, and a default route. That'd be a form
> of independence, and avoid '/64' CIDR-breaking assumptions.

That would lead to a long standing debate of whether DHCPv6 should
propagate on-link prefix and/or default route information, and I tried
to avoid that part of discussion as I knew it would never converge:-)
In any case if we really want to discuss it again, it would be better
to do it outside the scope of 3315bis.

--
jinmei


From nobody Thu Apr  2 11:14:00 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10CF01A0271 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 11:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 oUt6qCNs4NrO for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 11:13:58 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1B671A026C for <dhcwg@ietf.org>; Thu,  2 Apr 2015 11:13:57 -0700 (PDT)
Received: by ignm3 with SMTP id m3so53568714ign.0 for <dhcwg@ietf.org>; Thu, 02 Apr 2015 11:13:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fJfr1OmpncQUDYkIlVDP/LA/BkXf7f0GnOZzR0AX05M=; b=dyyu+0YPcuu2jLn/XSllisoyhpLZwQtFDP4qQ+a8hBHRr+AP5dq4KJsRQxzX8gkN+7 kMVmhTkCoolXHtTdC12GUwCNo1g0DQSdD7OPPChpg/yVqesQtABoogO0yiBlOQyG9E91 bxMCEfuEEIcJq87qzS1WKBE/XrZHd3uDswGBlbljZ9ESpKGwqaBPLIkPgJ3TsXNYWqjU 4LWV3W4mz6+5i6dGZhoqD+KdIaIdMk/kPCl4DEGGzoINcmZGbRCCbQ0yiSfQdUcPAndE Fj0Y2dgniBbKvU8PhONVrrJiuViTgTY+IPaMPdysr8ItjiLamh0q3w/c1Lma+l+hlPar DKNQ==
MIME-Version: 1.0
X-Received: by 10.107.128.3 with SMTP id b3mr18576956iod.24.1427998437480; Thu, 02 Apr 2015 11:13:57 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.21.3 with HTTP; Thu, 2 Apr 2015 11:13:57 -0700 (PDT)
In-Reply-To: <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com>
Date: Thu, 2 Apr 2015 11:13:57 -0700
X-Google-Sender-Auth: wdV54Lh8oPrpGqiLO3Lw0m_9JCs
Message-ID: <CAJE_bqdmS+f_osMdP+mSeNnpJL-Pus+-ERa=qT8Fd=OEsvd5ng@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/IBWr7AZoHTTvREx6EX3YzgvgtfY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 18:13:59 -0000

At Thu, 2 Apr 2015 16:37:09 +0900,
Lorenzo Colitti <lorenzo@google.com> wrote:

> That is the correct answer, yes. By itself, an IPv6 address assigned via
> IA_NA or IA_TA cannot be used for anything. Perhaps we can just clarify it
> here by noting the following:
>
> Addresses received via DHCPv6 do not have any associated reachability
> information. In order avoid the problems described in [RFC4943], hosts MUST
                       ^ missing 'to' again:-)
> NOT assume that any IPv6 destinations are reachable on-link as a result of
> receiving an IA_NA or IA_TA. In order to communicate to any destination
> that is not a link-local address, the host must also have obtained
> reachability information by other means such as a Router Advertisement or
> manual configuration.

It looks good to me.  I think a paragraph like this is good enough for
the purpose of rfc3315bis.  Anything beyond that (including the
never-ending discussion of whether DHCPv6 should provide on-link
prefix information) should better be discussed separately, outside the
scope of 3315bis; otherwise the rfc3315bis work will never be complete.

--
JINMEI, Tatuya


From nobody Thu Apr  2 11:15:47 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99DEB1A0389 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 11:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.683
X-Spam-Level: 
X-Spam-Status: No, score=-4.683 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 1VMbPv_oT-mL for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 11:15:42 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45EAE1A0276 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 11:15:42 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t32IFeGJ017494; Thu, 2 Apr 2015 20:15:40 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 959952076BA; Thu,  2 Apr 2015 20:16:35 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8A0672076AF; Thu,  2 Apr 2015 20:16:35 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t32IFbOM024950; Thu, 2 Apr 2015 20:15:39 +0200
Message-ID: <551D8749.6090907@gmail.com>
Date: Thu, 02 Apr 2015 20:15:37 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se>	<201503271613.t2RGDdLn061234@givry.fdupont.fr>	<CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com>	<551CEC1F.3070006@gmail.com> <CAJE_bqfAmTFJwVL3VTK+w6rSu_TPPPrmWet2nmi-YfcKyts3PA@mail.gmail.com>
In-Reply-To: <CAJE_bqfAmTFJwVL3VTK+w6rSu_TPPPrmWet2nmi-YfcKyts3PA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ySHAvnEgyYDfzI6f2vdhvUsrTe0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 18:15:44 -0000

Le 02/04/2015 20:05, ç¥žæ˜Žé�”å“‰ a Ã©crit :
> At Thu, 02 Apr 2015 09:13:35 +0200, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>
>>> I agree with this statement per se, but I think this is not
>>> sufficient, since it doesn't (clearly) answer the question of
>>> what the operator should do if they want to use DHCPv6-based
>>> address assignment in an isolated single-link (or "subnet")
>>> network.  The "architecturally correct" answer will be that they
>>> should deploy a node (which would probably be collocated on the
>>> same node as the DHCPv6 server) that sends RAs with router
>>> lifetime being 0 and with appropriate on-link prefix(es).
> [...]
>> But, a Router-DHCPv6Server with router lifetime 0 and on-link
>> prefix will make think the Host this is not a default router and it
>> should SLAAC its address (maybe in addition to requesting one from
>> DHCPv6). Is this what is meant by the above?
>
> Not at all.  I didn't mean to say anything about SLAAC in the above
> "architecturally correct answer".

I misread then, sorry.

>> Another suggestion on another hand is to have DHCPv6 deliver a
>> prefix length together with the address, and a default route.
>> That'd be a form of independence, and avoid '/64' CIDR-breaking
>> assumptions.
>
> That would lead to a long standing debate of whether DHCPv6 should
> propagate on-link prefix and/or default route information, and I
> tried to avoid that part of discussion as I knew it would never
> converge:-)

Ok.

> In any case if we really want to discuss it again, it would be
> better to do it outside the scope of 3315bis.

I am not really saying we'd need to discuss it, unless we really want it
and it's simple to achieve.

It would be very simple to achieve having prefixlen in DHCPv6 address
allocations, be it just an option.

Alex


>
> -- jinmei
>
>



From nobody Thu Apr  2 11:27:24 2015
Return-Path: <rdroms@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 676821A016C for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 11:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 22PRMoOLZohA for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 11:27:22 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4EED1A014E for <dhcwg@ietf.org>; Thu,  2 Apr 2015 11:27:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3470; q=dns/txt; s=iport; t=1427999241; x=1429208841; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+GCPUK7lShehmTWJPsREzQUyKzU9Q6VBrxTYjEdgf10=; b=GSSqFq3a14ETLrpiUyDQw+hNSTtBiufjxvCz7Yj3g0kUz7EfMevi+mzl 55WUAby0JwaDONoYyYh2NpEHcGR/hsTLbx+Ubfh/tqu3e72ldtG86YJI5 nsJkhf0BzOV+MI7xaqHqsZDd6o2hgKll2IrjAipaMaChb9k4wgGzhsTlt Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AzBQCSiR1V/4kNJK1cgwhSXAWDEMJHCoV9AhyBL0wBAQEBAQF+hB4BAQEDAQEBASAROgsFCwIBBgIYAgImAgICHwYLFRACBA4FiBsDCQgNmGCcf5JWDYVEAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSBIYoIgkeBZxgYGweCaC+BFgEEkGqIM4FNjhmGLyKDb2+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,512,1422921600"; d="scan'208";a="137773765"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-7.cisco.com with ESMTP; 02 Apr 2015 18:27:20 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t32IRK7b026013 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 18:27:20 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.86]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.03.0195.001; Thu, 2 Apr 2015 13:27:20 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQaKj80muBJGbcNkGotfXc7mP6I504wzCAgADoYICAALZEAIAAArSAgAADRYA=
Date: Thu, 2 Apr 2015 18:27:20 +0000
Message-ID: <F30838AF-E1A1-40D1-BC7E-B5993E388344@cisco.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <551CEC1F.3070006@gmail.com> <CAJE_bqfAmTFJwVL3VTK+w6rSu_TPPPrmWet2nmi-YfcKyts3PA@mail.gmail.com> <551D8749.6090907@gmail.com>
In-Reply-To: <551D8749.6090907@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.214.60]
Content-Type: text/plain; charset="utf-8"
Content-ID: <24C4DC7878CD644AA534815E47B7A93B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/91tKJZDeuih5NgLQbklyhfKpuPU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 18:27:23 -0000

DQo+IE9uIEFwciAyLCAyMDE1LCBhdCAyOjE1IFBNIDQvMi8xNSwgQWxleGFuZHJ1IFBldHJlc2N1
IDxhbGV4YW5kcnUucGV0cmVzY3VAZ21haWwuY29tPiB3cm90ZToNCj4gDQo+IExlIDAyLzA0LzIw
MTUgMjA6MDUsIOelnuaYjumBlOWTiSBhIMOpY3JpdCA6DQo+PiBBdCBUaHUsIDAyIEFwciAyMDE1
IDA5OjEzOjM1ICswMjAwLCBBbGV4YW5kcnUgUGV0cmVzY3UNCj4+IDxhbGV4YW5kcnUucGV0cmVz
Y3VAZ21haWwuY29tPiB3cm90ZToNCj4+IA0KPj4+PiBJIGFncmVlIHdpdGggdGhpcyBzdGF0ZW1l
bnQgcGVyIHNlLCBidXQgSSB0aGluayB0aGlzIGlzIG5vdA0KPj4+PiBzdWZmaWNpZW50LCBzaW5j
ZSBpdCBkb2Vzbid0IChjbGVhcmx5KSBhbnN3ZXIgdGhlIHF1ZXN0aW9uIG9mDQo+Pj4+IHdoYXQg
dGhlIG9wZXJhdG9yIHNob3VsZCBkbyBpZiB0aGV5IHdhbnQgdG8gdXNlIERIQ1B2Ni1iYXNlZA0K
Pj4+PiBhZGRyZXNzIGFzc2lnbm1lbnQgaW4gYW4gaXNvbGF0ZWQgc2luZ2xlLWxpbmsgKG9yICJz
dWJuZXQiKQ0KPj4+PiBuZXR3b3JrLiAgVGhlICJhcmNoaXRlY3R1cmFsbHkgY29ycmVjdCIgYW5z
d2VyIHdpbGwgYmUgdGhhdCB0aGV5DQo+Pj4+IHNob3VsZCBkZXBsb3kgYSBub2RlICh3aGljaCB3
b3VsZCBwcm9iYWJseSBiZSBjb2xsb2NhdGVkIG9uIHRoZQ0KPj4+PiBzYW1lIG5vZGUgYXMgdGhl
IERIQ1B2NiBzZXJ2ZXIpIHRoYXQgc2VuZHMgUkFzIHdpdGggcm91dGVyDQo+Pj4+IGxpZmV0aW1l
IGJlaW5nIDAgYW5kIHdpdGggYXBwcm9wcmlhdGUgb24tbGluayBwcmVmaXgoZXMpLg0KPj4gWy4u
Ll0NCj4+PiBCdXQsIGEgUm91dGVyLURIQ1B2NlNlcnZlciB3aXRoIHJvdXRlciBsaWZldGltZSAw
IGFuZCBvbi1saW5rDQo+Pj4gcHJlZml4IHdpbGwgbWFrZSB0aGluayB0aGUgSG9zdCB0aGlzIGlz
IG5vdCBhIGRlZmF1bHQgcm91dGVyIGFuZCBpdA0KPj4+IHNob3VsZCBTTEFBQyBpdHMgYWRkcmVz
cyAobWF5YmUgaW4gYWRkaXRpb24gdG8gcmVxdWVzdGluZyBvbmUgZnJvbQ0KPj4+IERIQ1B2Niku
IElzIHRoaXMgd2hhdCBpcyBtZWFudCBieSB0aGUgYWJvdmU/DQo+PiANCj4+IE5vdCBhdCBhbGwu
ICBJIGRpZG4ndCBtZWFuIHRvIHNheSBhbnl0aGluZyBhYm91dCBTTEFBQyBpbiB0aGUgYWJvdmUN
Cj4+ICJhcmNoaXRlY3R1cmFsbHkgY29ycmVjdCBhbnN3ZXIiLg0KPiANCj4gSSBtaXNyZWFkIHRo
ZW4sIHNvcnJ5Lg0KPiANCj4+PiBBbm90aGVyIHN1Z2dlc3Rpb24gb24gYW5vdGhlciBoYW5kIGlz
IHRvIGhhdmUgREhDUHY2IGRlbGl2ZXIgYQ0KPj4+IHByZWZpeCBsZW5ndGggdG9nZXRoZXIgd2l0
aCB0aGUgYWRkcmVzcywgYW5kIGEgZGVmYXVsdCByb3V0ZS4NCj4+PiBUaGF0J2QgYmUgYSBmb3Jt
IG9mIGluZGVwZW5kZW5jZSwgYW5kIGF2b2lkICcvNjQnIENJRFItYnJlYWtpbmcNCj4+PiBhc3N1
bXB0aW9ucy4NCj4+IA0KPj4gVGhhdCB3b3VsZCBsZWFkIHRvIGEgbG9uZyBzdGFuZGluZyBkZWJh
dGUgb2Ygd2hldGhlciBESENQdjYgc2hvdWxkDQo+PiBwcm9wYWdhdGUgb24tbGluayBwcmVmaXgg
YW5kL29yIGRlZmF1bHQgcm91dGUgaW5mb3JtYXRpb24sIGFuZCBJDQo+PiB0cmllZCB0byBhdm9p
ZCB0aGF0IHBhcnQgb2YgZGlzY3Vzc2lvbiBhcyBJIGtuZXcgaXQgd291bGQgbmV2ZXINCj4+IGNv
bnZlcmdlOi0pDQo+IA0KPiBPay4NCj4gDQo+PiBJbiBhbnkgY2FzZSBpZiB3ZSByZWFsbHkgd2Fu
dCB0byBkaXNjdXNzIGl0IGFnYWluLCBpdCB3b3VsZCBiZQ0KPj4gYmV0dGVyIHRvIGRvIGl0IG91
dHNpZGUgdGhlIHNjb3BlIG9mIDMzMTViaXMuDQo+IA0KPiBJIGFtIG5vdCByZWFsbHkgc2F5aW5n
IHdlJ2QgbmVlZCB0byBkaXNjdXNzIGl0LCB1bmxlc3Mgd2UgcmVhbGx5IHdhbnQgaXQNCj4gYW5k
IGl0J3Mgc2ltcGxlIHRvIGFjaGlldmUuDQo+IA0KPiBJdCB3b3VsZCBiZSB2ZXJ5IHNpbXBsZSB0
byBhY2hpZXZlIGhhdmluZyBwcmVmaXhsZW4gaW4gREhDUHY2IGFkZHJlc3MNCj4gYWxsb2NhdGlv
bnMsIGJlIGl0IGp1c3QgYW4gb3B0aW9uLg0KDQpOby4gIFRoZXJlIGlzIG5vIHN1Y2ggdGhpbmcg
YXMgYSBwcmVmaXggbGVuZ3RoIG9uIGFuIGFkZHJlc3MuDQoNCklmIERIQ1B2NiB3ZXJlIHRvIGNh
cnJ5IHJlYWNoYWJpbGl0eSBpbmZvcm1hdGlvbiAtIGFuZCB0aGF0IGlzIGFuIHVubGlrZWx5IGh5
cG90aGV0aWNhbCB0aGF0IEkgKnJlYWxseSogZG9uJ3QgY2FyZSB0byBkaXNjdXNzIGhlcmUgLSBp
dCBtdXN0IGJlIGluIHRoZSBmb3JtIG9mIGEgbGlzdCBvZiBvbi1saW5rIHByZWZpeGVzLCBlbnRp
cmVseSBkaXNqb2ludCBmcm9tIGFueSBhc3NpZ25lZCBhZGRyZXNzZXMuDQoNCi0gUmFscGgNCg0K
PiANCj4gQWxleA0KPiANCj4gDQo+PiANCj4+IC0tIGppbm1laQ0KPj4gDQo+PiANCj4gDQo+IA0K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBkaGN3
ZyBtYWlsaW5nIGxpc3QNCj4gZGhjd2dAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9kaGN3Zw0KDQo=


From nobody Thu Apr  2 12:06:28 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 545AA1A0364 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 12:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ekMIEoIuZVzC for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 12:06:23 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 1842C1A0113 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 12:06:23 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id EAD15DA00C9; Thu,  2 Apr 2015 19:06:22 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 2 Apr 2015 12:06:22 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com>
Date: Thu, 2 Apr 2015 15:06:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/I7ch7AYQ9W-kiWcmZOMtKKa7kvc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 19:06:27 -0000

On Apr 2, 2015, at 11:01 AM, Ralph Droms (rdroms) <rdroms@cisco.com> =
wrote:
> The semantics of the M/O bits - and, please, let's not revisit that =
/dev/null discussion? - are, at this point, informative only.  RFC 7084, =
for example, specifies that a CE router uses DHCPv6 on its WAN link =
regardless of whether or not it receives an RA with the M bit set.

Hm, but it still depends on the RA for reachability information, =
correct?


From nobody Thu Apr  2 13:42:55 2015
Return-Path: <rdroms@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CFC11A1A83 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 13:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 bVDISrwP2CZo for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 13:42:51 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D03D1A1A78 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 13:42:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=589; q=dns/txt; s=iport; t=1428007370; x=1429216970; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LlNYCvHQcg/OXHw9C+rFFEUZn+5cLO9Fel2XRPIj48I=; b=Gjwnuk0BfolEVnlpACKy14UCQMx60TpUWRrb8lwTZVW4axvInZFV77gE PURs+6SBIxdd+NYhY1tFfubJPIRp6wbugSCzPYjFnWx8r9Cqu5IaGOU7y 7/vXjCnNUEv3jbY5XTYfXB6huOnUst0fANwXgj//SXG6xmVbhbxXmEC31 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AtBQA3qR1V/51dJa1cgwiBLgXLYQKBTEwBAQEBAQF+hB4BAQEDATo/BQsCAQgYHhAyJQIEDgWIJwjOBAEBAQEBAQEBAQEBAQEBAQEBAQEBAReLKYRGMwcCgxWBFgEEkGqKAIEdgzSPdyKDb2+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,512,1422921600"; d="scan'208";a="405689982"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 02 Apr 2015 20:42:49 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t32KgnS0022177 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 20:42:49 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.86]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Thu, 2 Apr 2015 15:42:49 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQaKj80muBJGbcNkGotfXc7mP6I504wzCAgADu9oCAABneAIAAC+cAgABFaoCAABDfAIAARH4AgAAa9YA=
Date: Thu, 2 Apr 2015 20:42:49 +0000
Message-ID: <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com>
In-Reply-To: <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.38.137]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6583931C51739844899DBB1D7CB26833@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/iUuha1i0jg8A0L9JRZ8DdT-xXYQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 20:42:53 -0000

> On Apr 2, 2015, at 3:06 PM 4/2/15, Ted Lemon <Ted.Lemon@nominum.com> wrot=
e:
>=20
> On Apr 2, 2015, at 11:01 AM, Ralph Droms (rdroms) <rdroms@cisco.com> wrot=
e:
>> The semantics of the M/O bits - and, please, let's not revisit that /dev=
/null discussion? - are, at this point, informative only.  RFC 7084, for ex=
ample, specifies that a CE router uses DHCPv6 on its WAN link regardless of=
 whether or not it receives an RA with the M bit set.
>=20
> Hm, but it still depends on the RA for reachability information, correct?

As far as I know, yes.

- Ralph

>=20


From nobody Thu Apr  2 13:47:31 2015
Return-Path: <shemant@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 734481A1A99 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 13:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 QDArcXCVYL6c for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 13:47:29 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7430A1A1A6A for <dhcwg@ietf.org>; Thu,  2 Apr 2015 13:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1053; q=dns/txt; s=iport; t=1428007648; x=1429217248; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+mIx0AaTHgA5HZjldYAYBWw9RyttqOptKy0TraS8dNQ=; b=E+XOqcZ7AqCDIv7lowD8I6ODrfef/nlzQcM9KUyqxWiRhUG4BVq1IJjz VVGwEqlluyGrRLrG8Vv3xjI5bQ0GCvFKt7OrG2vwxvffzrz1Ev7f/Z/+8 ws/DdqM3DGXvZcVP1lso+l3P1TXRG5zT5se28eh6fFA/yYsmjJ8i71YHR 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AxBQBeqh1V/5hdJa1cgwhSXAXFWgqFfQKBTEwBAQEBAQF+hB4BAQEDAQEBATc0CwUHBAIBCBEEAQEBChQJBycLFAkIAgQBDQUIiB8IDc1nAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSLKYRIBisHAgSDEYEWAQSQaosdgzSCXo0ZIoNvb4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,512,1422921600"; d="scan'208";a="137810769"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-7.cisco.com with ESMTP; 02 Apr 2015 20:47:27 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t32KlRRS010604 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 20:47:27 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0195.001; Thu, 2 Apr 2015 15:47:27 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQaKj8INk+f2Ge0U+xrfWR5Xce+p04wzCAgADu9oCAABneAIAAC+cAgABFaoCAABDfAIAARH4AgAAa94D//60c8A==
Date: Thu, 2 Apr 2015 20:47:26 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com>
In-Reply-To: <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.71.118]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SsIH2Ma9rrU1SIJtPcttXRdgHOg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 20:47:30 -0000

Folks should read RFC5942.  See section 4, bullet 1.=20

Hemant

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ralph Droms (rdrom=
s)
Sent: Thursday, April 02, 2015 4:43 PM
To: Ted Lemon
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length


> On Apr 2, 2015, at 3:06 PM 4/2/15, Ted Lemon <Ted.Lemon@nominum.com> wrot=
e:
>=20
> On Apr 2, 2015, at 11:01 AM, Ralph Droms (rdroms) <rdroms@cisco.com> wrot=
e:
>> The semantics of the M/O bits - and, please, let's not revisit that /dev=
/null discussion? - are, at this point, informative only.  RFC 7084, for ex=
ample, specifies that a CE router uses DHCPv6 on its WAN link regardless of=
 whether or not it receives an RA with the M bit set.
>=20
> Hm, but it still depends on the RA for reachability information, correct?

As far as I know, yes.

- Ralph

>=20

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Thu Apr  2 14:01:46 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E04C1A1B86 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 14:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 fUGEQ2v4KOaD for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 14:01:43 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 3F37E1A1B57 for <dhcwg@ietf.org>; Thu,  2 Apr 2015 14:01:43 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 1EE61DA00D2; Thu,  2 Apr 2015 21:01:43 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 2 Apr 2015 14:01:36 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com>
Date: Thu, 2 Apr 2015 17:01:32 -0400
Content-Transfer-Encoding: 7bit
Message-ID: <8ABDADC6-F81D-4301-8416-527801651B89@nominum.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/z3e1C2OyzBHT_YxgkeW6KRYFL8U>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 21:01:44 -0000

On Apr 2, 2015, at 4:47 PM, Hemant Singh (shemant) <shemant@cisco.com> wrote:
> Folks should read RFC5942.  See section 4, bullet 1. 

Oh, nice.   That might be a better reference to use.


From nobody Thu Apr  2 14:13:27 2015
Return-Path: <rdroms@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A36FC1A00E4 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 14:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 OkGOeBphzbgW for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 14:13:25 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B49A1A1ADB for <dhcwg@ietf.org>; Thu,  2 Apr 2015 14:13:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=315; q=dns/txt; s=iport; t=1428009205; x=1429218805; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=XfeIDMp/l5X3pR9v0yQTw7UV+e4ba5I1Y0I1emGuPUE=; b=BzAjB4n/Yw3ZuHmLKRlg2chUAT4zM3N+gEO0ju9qniNaSW8l5odOfkXj A3bHim6FCP9Nimfcv46X/yHeSXi0RucSn6GolrGN6teeWuPScECotG2T7 sk4MYnzQJcBIVYOKF+BvGemDfq4YLye1gOpbi33Q0Px1MEeI+MniVojbs I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AtBQBzsB1V/4cNJK1cgwiBLgXLYQKBTEwBAQEBAQF+hB4BAQEDATo/BQsCAQgYHhAyJQIEDgWIJwjOAAEBAQEBAQEBAQEBAQEBAQEBAQEBAReLKYRGMweDF4EWAQSOW4IPigCBHYYSjRkig29vgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.11,513,1422921600"; d="scan'208";a="137815174"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-6.cisco.com with ESMTP; 02 Apr 2015 21:13:24 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t32LDOVV027223 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 21:13:24 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.86]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0195.001; Thu, 2 Apr 2015 16:13:24 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQaKj80muBJGbcNkGotfXc7mP6I504wzCAgADu9oCAABneAIAAC+cAgABFaoCAABDfAIAARH4AgAAa9YCAAAFMAIAAA/EAgAADTgA=
Date: Thu, 2 Apr 2015 21:13:24 +0000
Message-ID: <02697D5C-8E31-48B8-A3DB-11903CF7BC41@cisco.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com> <8ABDADC6-F81D-4301-8416-527801651B89@nominum.com>
In-Reply-To: <8ABDADC6-F81D-4301-8416-527801651B89@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.214.60]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <67D87477FF1336429FA4D6CBB98C894E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/bhLUFprtIdoN7eQFiCge7X0DxV8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 21:13:26 -0000

> On Apr 2, 2015, at 5:01 PM 4/2/15, Ted Lemon <Ted.Lemon@nominum.com> wrot=
e:
>=20
> On Apr 2, 2015, at 4:47 PM, Hemant Singh (shemant) <shemant@cisco.com> wr=
ote:
>> Folks should read RFC5942.  See section 4, bullet 1.=20
>=20
> Oh, nice.   That might be a better reference to use.

Agreed.

>=20


From nobody Thu Apr  2 14:40:34 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69DDB1A6F29 for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 14:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 bMxtDzWgUOeD for <dhcwg@ietfa.amsl.com>; Thu,  2 Apr 2015 14:40:30 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE441A6FFB for <dhcwg@ietf.org>; Thu,  2 Apr 2015 14:40:29 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.61] (88-111-169-158.dynamic.dsl.as9105.com [88.111.169.158]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 0DB551BC3E for <dhcwg@ietf.org>; Thu,  2 Apr 2015 21:40:24 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <551D7B09.5000601@gmail.com>
Date: Thu, 2 Apr 2015 22:40:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/uRZUhA8TJuNSxUeTgw77dFHukvo>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 21:40:33 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> Assuming the router knows about the other devices, when we open a
>> connection by sending packets to the router, the router can tell us
>> (via a redirect) about the other node being on-link. At this point,
>> we then know to use ND to find the other node and it becomes on-link
>> to us for as long as the neighbour information is kept active. This
>> doesn't need *ANY* prefix information at all - only knowledge of a
>> router we can use to send our packets out.
>=20
> Well, yes and no.
>=20
> Yes in that it can work as you describe.  And that prefix lengths must
> be there during that operation.

Why ? What is a prefix doing for us in this scenario ? We can work with =
absolutely no prefix list whatsoever as long as the router redirects =
tell us about neighbours that are directly reachable.

> If they are not there it does not work.

Yes it will. We don't need a prefix to talk to the router, and we don't =
need one to talk about a neighbour we've already found.

> No in that Redirect does not tell whether somebody is onlink or not, =
it
> just redirects to a better first-hop router, which will presumably be
> that other neighbor-on-link (but not neighbor-on-same-subnet):
> RFC says:
>>=20
>> 4.5. Redirect Message Format
>>=20
>>=20
>> Routers send Redirect packets to inform a host of a better first-hop
>> node on the path to a destination.  Hosts can be redirected to a
>> better first-hop router but can also be informed by a redirect that
>> the destination is in fact a neighbor.
>=20
> "in fact a neighbor"?  It is a neighbor on the same link, but it is =
not
> a neighbour in the same subnet, because there is no subnet.  Is a =
neighbor "on-link"?  We dont know.

Yes we do. See RFC4681 again.

   on-link     - an address that is assigned to an interface on a
                 specified link.  A node considers an address to be on-
                 link if:

...

                    - a neighboring router specifies the address as the
                      target of a Redirect message, or

And see Sec 4.5 that you quoted - the router can tell us that a host is =
local to us - it on-link.

> In fact, this entire terminology of "on-link determination" is not
> described anywhere.

RFC4681

> You have some bits here and there about who
> contributes to it, but there is no section telling that is the on-link
> determination operation.  With hands empty you  can only  suppose what
> it is, and implement in a certain manner (longest match dst to rt =
table
> entries, if found then ND dst and send packet to that MAC otherwise ND
> the default router's IP address and send packet to that other MAC
> address).  That's how I believe it should be but no document tells how
> it should be.

So you want the standard to say how it should be done, not just what =
should be done ?
There's no "longest match" requirement - if the address is within any =
prefix marked as local then the address is considered on-link. You can =
do the "run down the list thing" and just stop at the first match - no =
need to find multiple matches, do longest match, etc.

> When I type "route -6" there are some routes but there is not one that
> says "this is on-link, this is not on-link".

That's showing the result of a specific implementation which may or may =
not reflect the internal tables directly - and for which I believe we =
have already identified does not "do things correctly". On my systems, I =
see entries for "my own address" /128, and for the subnet prefix /64 =
which since I stopped radvd will have come from adding the interface =
IPv6 address.

>>>> on-link     - an address that is assigned to an interface on a
>>>> specified link.  A node considers an address to be on- link if:
>>>>=20
>>>> - it is covered by one of the link's prefixes (e.g., as indicated
>>>> by the on-link flag in the Prefix Information option), or
>>>>=20
>>>> - a neighboring router specifies the address as the target of a
>>>> Redirect message, or
>>>>=20
>>>> - a Neighbor Advertisement message is received for the (target)
>>>> address, or
>>>>=20
>>>> - any Neighbor Discovery message is received from the address.
...
> What is precisely the "on-link determination"? (some RFC section =
titled so that I missed?)

The section already quoted ?

> And, of course, it can figure it out only if it is not link-local.  If
> you ping an LL address you have to say a -I iface because the computer =
can't determine the interface from its rt table (it has an fe80::/10 =
entry for each interface).

Yes, I think we all agree that link-local addresses are a special case - =
and not relevant to this thread.

>> So my only consideration would be "Is A on-link for any of my
>> interfaces, or is it off-link for all of them". Of course there are
>> times when it does matter, and then I'll specify either an interface
>> or source address*.
>=20
> I can understand your interpretation in your setting.
>=20
> In my setting I avoid saying something is "on-link" or "off-link",
> because I know people have different understandings for each.

But surely the correct thing to do is to use the same terminology as =
specified in the RFC ? The RFC where both terms are defined.

>>> For example, the RFC says:
>>>> A router acting on behalf of a mobile node that has moved
>>>> off-link could potentially act as a proxy for the mobile node.
>>>=20
>>> The term "off-link" is used, but the "specified link" (per
>>> definition) is not present.  Moreover, the definition tells
>>> "off-link" is an "address", whereas in this use this "off-link" is
>>> simply a qualifier of the mouvement.
>>>=20
>>> We can understand the phrase, the node moved out of the link, off
>>> of the link; but the term "off-link" is not well defined.
>>=20
>> Again, I think context is everything. For something that's "moved
>> off-link", we can infer that it's no longer on the link it used to be
>> on. If it were to appear "on-link" for some other link then that
>> complicates matters, but I don't think that in context it is wrong.
>=20
> It is not wrong, it is just misleading and not self-containing; it is
> not implementable in an interoperable manner.

I disagree.
It's merely stating that a router could proxy for a mobile device that's =
left the network.
Operation of mobility is defined elsewhere - and it does not in any way =
affect the topic of this thread. As far as our node is concerned, if a =
router is proxying for a mobile device, then we treat it the same was as =
we'd treat the device it's proxying for. The same questions apply to =
determine if it's on-link - so I think it's a non-problem. There simply =
is nothing whatsoever to implement (on a general node that isn't taking =
part in mobility) to cater for this.


>>> Furthe, RFC says:
>>>> L              1-bit on-link flag.  When set, indicates that
>>>> this prefix can be used for on-link determination.  When not set
>>>> the advertisement makes no statement about on-link or off-link
>>>> properties of the prefix.  In other words, if the L flag is not
>>>> set a host MUST NOT conclude that an address derived from the
>>>> prefix is off-link.  That is, it MUST NOT update a previous
>>>> indication that the address is on-link.
>>>=20
>>> This definition means that it means nothing.  It gives no
>>> indication. It's just like the M flag.
>>>=20
>>> If L then something, otherwise nothing.  This is not what me as
>>> implementer would like to see.
>>=20
>> I can only see one issue - and without having digested the RFC I
>> don't know if it's addressed. If an RA sets the L bit, and then
>> unsets it later, the above says that we carry on treating the prefix
>> as local. How often is this likely to happen in practice ? I'm not
>> sure I can envisage a network where it supports ND, but then changes
>> (without any host links going down) into one where ND no longer
>> works.
>>=20
>> What comes to mind is if an RA from one router sets it, another
>> router sends RA with it unset, and then the first router goes/has the
>> prefix removed/whatever. Does a node keep track of which RAs it got
>> from each router, does it then say that the prefix is now not local
>> because the RA that set it as local has stopped and there's no other
>> RA that has it set ? Conversely, if the above said that getting an RA
>> with the L bit clear means you have to update the prefix information,
>> the next question would be "what about multiple RAs for the same
>> prefix with different states for the L bit ?"

> I meant to say that when L is unset we dont know what to do (we dont
> know whether that is onlink or offlink).  As such it's sent for no
> reason and should be ignored.

Look at it this way. If the flag is set then you do something. If it's =
not set then you just leave existing settings alone. I'm afraid I can't =
see what the problem is with that.

>>  The mechanism for it getting unset is
>> for the prefix to get removed from the table =3D which will happen if
>> the link "goes down", or if we stop getting any RAs with the prefix.
>> As above, I can't think of any situation (other than admin cock-up
>> !) where there would be any need to unset the local flag in the
>> prefix table.
>=20
> There is no reason for that.  Entries will expire by themselves =
anyways, no need to announce going down.  Expiration can be planned be =
quicker by using shorter lifetimes, too.

Unless the RAs are still advertising the prefix - in that case an entry =
won't expire, so there is no mechanism for unsetting the local flag in =
the node's prefix table. But as I said, other than an admin having =
accidentally set it when it shouldn't be, I can't see a situation where =
a prefix could legitimately change from local to not local without some =
event (such as interface going down momentarily) happening that causes =
the prefix table for that link to be flushed.
In the same way, i can't really see it changing the other way either - =
other than by having two routers and one of them is incorrectly =
configured.

So in reality, the process is going to be as simple as get an RA, add =
the prefix(es) or refresh the timer if it already exists. And if the L =
flag is set, then make sure it's set in our table. Unless someone comes =
up with something else, I believe that really is it.


From nobody Fri Apr  3 15:33:25 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4EBC1A1E0E for <dhcwg@ietfa.amsl.com>; Fri,  3 Apr 2015 15:33:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level: 
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_42=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 c1c9k0eWoWJw for <dhcwg@ietfa.amsl.com>; Fri,  3 Apr 2015 15:33:23 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 E4B001A1C06 for <dhcwg@ietf.org>; Fri,  3 Apr 2015 15:33:22 -0700 (PDT)
Received: from [2a02:2028:61b:e301:2dfe:84c0:387:26ab] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YeA9N-00012l-Fr; Sat, 04 Apr 2015 00:33:17 +0200
Message-ID: <551F14BA.2000702@si6networks.com>
Date: Sat, 04 Apr 2015 00:31:22 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/O-4Tm-a4z8o1P5sxYhu14euWclE>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 22:33:25 -0000

Hi, Bernie,

I'm kind of surprised about the question :-), since my mental model of
this I-D as that it should be WGLC'ed rather than  abandoned.

Regarding your thoughts, please find my comments in-line...

On 04/01/2015 07:30 PM, Bernie Volz (volz) wrote:
> 
> To the WG and co-authors of this document, as a follow up from the
> Dallas (IETF-92) DHC WG meeting, there is the question as to next
> step(s) for draft-ietf-dhc-stable-privacy-addresses.
> 
> In thinking about this some, my feeling is:
> 
> -          Drop the work. There is little reason for defining this for
> DHCPv6 servers as there are no “interoperability” issues.

If you look at the RFC series, there are plenty of documents that
specify policies that do not necessarily result in interoperability
issues: e.g., RFC4086, RFC1948, RFC6056. RFC7217.

In many cases, there are underlying requirements to prevent
interoperability issues. And some of the possible choices have other
implications (e.g., security-related). Hence having guidance or
providing good implementation approaches is more than valuable.



> o   If there are multiple servers operating on a link and they aren’t
> coordinating activities in some way (i.e. perhaps DHCPv6 failover or
> some common database), they will likely not be able to lease from the
> same pool of addresses anyway.

Actually, an approach such as that pecified by this document is
mentioned in RFC7031 itself. e.g.:

"  Also, the typical large address space (close to 2^64 addresses on /64
   prefixes expected to be available on most networks) may make managing
   address assignment significantly different from DHCPv4 failover.  In
   DHCPv4, it was not possible to use a hash or calculated technique to
   divide the significantly more limited address space, and therefore,
   much of the protocol that deals with pool balancing and rebalancing
   might not be necessary and can be done mathematically."

So this is indeed and algorithmic approach for coordinating the databases.



> o   Sure, if you change the server to a different server implementation,
> it may have different a algorithm, but does this really matter (and it
> is fairly rare in the first place)?

If stability is an issue, yes.



> o   And, there are also issues with the “range of addresses” model if
> the range is expanded or reduced, since this causes a change to the
> “stable” addresses.

This was already fixed (in the version that I didn't post because of the
I-D cutoff). We even discussed how to solve this issue on-list.




> o   So, do we really need this?
> 
> -          If people do feel that the work should continue (and
> eventually advance), the document should not be a “Standards Track” but
> “Informational”.

Wasn't this an implicit question in the wg call for adoption?



> So, I will propose that the DHC WG “drop this work” (mark the ID as
> dead). Objections? Comments?

Me, I object to that. :-). My comments and rationale can be found above.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Apr  3 17:40:48 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B2DC1A88BA for <dhcwg@ietfa.amsl.com>; Fri,  3 Apr 2015 17:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 wVQICzDGlRqs for <dhcwg@ietfa.amsl.com>; Fri,  3 Apr 2015 17:40:44 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2E2A1A88B1 for <dhcwg@ietf.org>; Fri,  3 Apr 2015 17:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3868; q=dns/txt; s=iport; t=1428108045; x=1429317645; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=cdgGymJLz0leCqOJH55r/E83YgM1qRFJCNUdqu0+Guw=; b=nJbmRUhHqkSy4kf9kxop0ah3IdYTD0MsIg/0e2qkgH9395MpM1Nx/6Wa iQZwHnFCahJK9hOH+6IZp6xU/7NZEgCS1D6zRY/QvQqQqglPNMik52d7d bQCgJKfJswlgCr8KTJt+3MF0fesEfxGxj0Yk2j1EZoTm93pVTifTMQ2n4 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AhBQB+Mh9V/5FdJa1cgwuBLstwAoErTAEBAQEBAX6EHgEBAQMBHQpSBQsCAQgOCi4yJQEBBA4FiCcIzFIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXiymEIA4YMweDF4EWBZBrigCBHYM1iH2DNYNIIoICHYFQb4ECgUEBAQE
X-IronPort-AV: E=Sophos;i="5.11,521,1422921600"; d="scan'208";a="409105263"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-6.cisco.com with ESMTP; 04 Apr 2015 00:40:43 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t340egIg028235 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 4 Apr 2015 00:40:43 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0195.001; Fri, 3 Apr 2015 19:40:42 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Fernando Gont <fgont@si6networks.com>
Thread-Topic: Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work?
Thread-Index: AdBsoYwybwOljCs3QqmPfiy3wPAzEAB5kYAA///QUV8=
Date: Sat, 4 Apr 2015 00:40:42 +0000
Message-ID: <6AEC7FB1-3985-47D9-A0FE-63409A6A06A2@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>,  <551F14BA.2000702@si6networks.com>
In-Reply-To: <551F14BA.2000702@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/xku8lMH2Tv39v1eJXaLxyqIq30o>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 00:40:46 -0000

These are questions / issues for the WG to reach consensus on. So let's see=
 what others have to say & if people actually have use cases where they wou=
ld want to make use of this (or close to it) algorithm.

I would recommend you publish a pending update if you have it.

- Bernie (from iPad)

> On Apr 3, 2015, at 6:33 PM, Fernando Gont <fgont@si6networks.com> wrote:
>=20
> Hi, Bernie,
>=20
> I'm kind of surprised about the question :-), since my mental model of
> this I-D as that it should be WGLC'ed rather than  abandoned.
>=20
> Regarding your thoughts, please find my comments in-line...
>=20
>> On 04/01/2015 07:30 PM, Bernie Volz (volz) wrote:
>>=20
>> To the WG and co-authors of this document, as a follow up from the
>> Dallas (IETF-92) DHC WG meeting, there is the question as to next
>> step(s) for draft-ietf-dhc-stable-privacy-addresses.
>>=20
>> In thinking about this some, my feeling is:
>>=20
>> -          Drop the work. There is little reason for defining this for
>> DHCPv6 servers as there are no =93interoperability=94 issues.
>=20
> If you look at the RFC series, there are plenty of documents that
> specify policies that do not necessarily result in interoperability
> issues: e.g., RFC4086, RFC1948, RFC6056. RFC7217.
>=20
> In many cases, there are underlying requirements to prevent
> interoperability issues. And some of the possible choices have other
> implications (e.g., security-related). Hence having guidance or
> providing good implementation approaches is more than valuable.
>=20
>=20
>=20
>> o   If there are multiple servers operating on a link and they aren=92t
>> coordinating activities in some way (i.e. perhaps DHCPv6 failover or
>> some common database), they will likely not be able to lease from the
>> same pool of addresses anyway.
>=20
> Actually, an approach such as that pecified by this document is
> mentioned in RFC7031 itself. e.g.:
>=20
> "  Also, the typical large address space (close to 2^64 addresses on /64
>   prefixes expected to be available on most networks) may make managing
>   address assignment significantly different from DHCPv4 failover.  In
>   DHCPv4, it was not possible to use a hash or calculated technique to
>   divide the significantly more limited address space, and therefore,
>   much of the protocol that deals with pool balancing and rebalancing
>   might not be necessary and can be done mathematically."
>=20
> So this is indeed and algorithmic approach for coordinating the databases=
.
>=20
>=20
>=20
>> o   Sure, if you change the server to a different server implementation,
>> it may have different a algorithm, but does this really matter (and it
>> is fairly rare in the first place)?
>=20
> If stability is an issue, yes.
>=20
>=20
>=20
>> o   And, there are also issues with the =93range of addresses=94 model i=
f
>> the range is expanded or reduced, since this causes a change to the
>> =93stable=94 addresses.
>=20
> This was already fixed (in the version that I didn't post because of the
> I-D cutoff). We even discussed how to solve this issue on-list.
>=20
>=20
>=20
>=20
>> o   So, do we really need this?
>>=20
>> -          If people do feel that the work should continue (and
>> eventually advance), the document should not be a =93Standards Track=94 =
but
>> =93Informational=94.
>=20
> Wasn't this an implicit question in the wg call for adoption?
>=20
>=20
>=20
>> So, I will propose that the DHC WG =93drop this work=94 (mark the ID as
>> dead). Objections? Comments?
>=20
> Me, I object to that. :-). My comments and rationale can be found above.
>=20
> Thanks!
>=20
> Cheers,
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20


From nobody Fri Apr  3 19:39:20 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB50E1A88D8 for <dhcwg@ietfa.amsl.com>; Fri,  3 Apr 2015 19:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 stsgOg8ELdTS for <dhcwg@ietfa.amsl.com>; Fri,  3 Apr 2015 19:39:17 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7DBD1A88D6 for <dhcwg@ietf.org>; Fri,  3 Apr 2015 19:39:16 -0700 (PDT)
Received: by iebmp1 with SMTP id mp1so94179789ieb.0 for <dhcwg@ietf.org>; Fri, 03 Apr 2015 19:39:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1K+c7kUiWatiPpBIC3Rc6fkoY5gNUdu//OjVb/01q8Q=; b=ot1Md4JTkrLXHdW0QXdjdyYFLYr23SVfolRirDS1FJGGDUXXyfox4Nk7mBS428TBXX aUw3+jxL1Ondsaqm2NgGtS9eYBF4YPVgpScVJeRDURO+IN8Oh0UrtsgqEEbuDCRbjaxf T8gFKjHpYF+bPAtflxXjlNKe+KYYkyNrxN6h7Zgp4fcae0NEHI4VjUoTuYdVSeQdlv/O ZyxuUZEEP0k6N2j5HhxCmj9VGvOgmWFO2z94V/pOjyIiv4W+T/McRvnj3XPlOEnz6NNR KvIholVl/HiM1og5AINuc4gTByIsJzRuIKtI/sAb9GuBr2MUjn8I2UfcQEy0R81X4nOX P3sQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=1K+c7kUiWatiPpBIC3Rc6fkoY5gNUdu//OjVb/01q8Q=; b=SN0iTKE/GF/Gjh5IlkeRfvpPkHsrcOGO6tnkg/NSKSfOF6aDGUy7wbW5PNIoFdTYvL 1iZR80sG9x6P3ZzFxni/88pZQHYIeiB/0ORV/vLuu9J0HhmF1Bo6pElf0EumENNy7EZk YWTQjxDAGDx89WNNrmr8SRshz9WcZIImSFDHVcoODO/Ym5OjzoVLzzrus8+npaG7aWst EpGXKu1vWiO8zRMumWovFMnkKCVL5gEyzts7hJ/djmu3uuZzNxDZJoeIypniaUltqcFY s4KGVtv40z6IglFpFIA31r+I8Xl/9t0bIGdpBnjru1zYPEcK0Cx8gbSl0V+Gy6T/mx6p L4gA==
X-Gm-Message-State: ALoCoQnu8XFNYQrUBm8p9W1/vtwLaXJNZ1KQ428NwIKx9tXanI0nHlzjX9fHoAt/KJv5NHjjIkd4
X-Received: by 10.107.34.210 with SMTP id i201mr7892833ioi.1.1428115156178; Fri, 03 Apr 2015 19:39:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Fri, 3 Apr 2015 19:38:55 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 4 Apr 2015 11:38:55 +0900
Message-ID: <CAKD1Yr3AAM1SQoTgKDwHakjE790fnmtgBwm631+a_2KRZqwcMw@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary=001a114031a09544a10512dcf892
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Y09G6YyNCyCSiCES_zqlDSGBYzM>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Apr 2015 02:39:17 -0000

--001a114031a09544a10512dcf892
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 2, 2015 at 2:30 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
>
> So, I will propose that the DHC WG =E2=80=9Cdrop this work=E2=80=9D (mark=
 the ID as dead).
> Objections? Comments?
>

Seems reasonable to me. We should definitely address the question of
privacy, but that should be done without dictating implementation.

--001a114031a09544a10512dcf892
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 2, 2015 at 2:30 AM, Bernie Volz (volz) <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&gt;</span>=
 wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vli=
nk=3D"purple"><div>
<p class=3D"MsoNormal">So, I will propose that the DHC WG =E2=80=9Cdrop thi=
s work=E2=80=9D (mark the ID as dead). Objections? Comments?</p></div></div=
></blockquote><div><br></div><div>Seems reasonable to me. We should definit=
ely address the question of privacy, but that should be done without dictat=
ing implementation.=C2=A0<br></div></div></div></div>

--001a114031a09544a10512dcf892--


From nobody Sun Apr  5 03:57:22 2015
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF2261AC417 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 03:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.562
X-Spam-Level: 
X-Spam-Status: No, score=-1.562 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 OD45Elg8BC8V for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 03:57:21 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF9DA1AC416 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 03:57:20 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t35AugSN081830; Sun, 5 Apr 2015 12:56:42 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201504051056.t35AugSN081830@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Lorenzo Colitti <lorenzo@google.com>
In-reply-to: Your message of Wed, 01 Apr 2015 09:42:50 +0900. <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> 
Date: Sun, 05 Apr 2015 12:56:42 +0200
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Qp0rRRdVK1_tDC1brTarbHIOjLg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 10:57:22 -0000

 In your previous mail you wrote:

>  Right. Perhaps we should leave the details to the RFCs where they are
>  specified? Proposed text:
>  
>  Addresses received via DHCPv6 do not have any associated reachability
>  information. In order avoid the problems described in [RFC4943], hosts MUST
>  NOT assume that any IPv6 addresses are reachable on-link as a result of
>  receiving an IA_NA or IA_TA; IPv6 addresses obtained from IA_NA or IA_TA
>  MUST NOT be configured with any prefix length except /128.

=> I fully disagree about the second part (second MUST NOT), in particular
for IA_NA's, because if DHCPv6 doesn't provide the info this doesn't
mean this is not available.

Regards

Francis.Dupont@fdupont.fr


From nobody Sun Apr  5 05:12:37 2015
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382BC1A1B8A for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 05:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.562
X-Spam-Level: 
X-Spam-Status: No, score=-1.562 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 VVIa6pFpCd-n for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 05:12:35 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A61471A1B76 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 05:12:34 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t35CBvv9086687; Sun, 5 Apr 2015 14:11:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201504051211.t35CBvv9086687@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Simon Hobson <linux@thehobsons.co.uk>
In-reply-to: Your message of Wed, 01 Apr 2015 11:58:11 BST. <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> 
Date: Sun, 05 Apr 2015 14:11:57 +0200
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/GjIee-rHMaNmB7SWUXyiLah6yKA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 12:12:36 -0000

 In your previous mail you wrote:

>  >> This looks okay,
>  
>  +1, looks clear, concise and not open to misinterpretation.

=> -1 (just because it simply doesn't work in the real world).

>  > Why would a Client configure an unreachable /128 on its interface?

=> good question (:-).

> In the IPv4 world, you get an address and subnet mask. From that you
> work ou ut the range of addresses in the same subnet, and from that
> you infer reachability information. Ie (in the absence of further
> configuration), if the address is in the same subnet you infer "on
> link" and do local discovery (ARP), if the address isn't in the
> same subnet you infer "not local" and send the packet via a router.

=> even I share your "IPv6 is not IPv4 with longer addresses" idea
IMHO you missed 2 critical points:
 - many IPv6 tools are just derived from the corresponding IPv4 versions
  so you can't say the IPv4 way is just plainly wrong and must be
  ignored. BTW older versions of Linuxes had the same problem...

 - most users of DHCPv6 adopted it because they use(d) DHCPv4 so
  I am afraid your argument is not the best one for the intented
  people (:-).

>  In the IPv6 world it's somewhat different.

=> IMHO you are simply reopening the SLAAC vs DHCPv6 issues in the
worst possible way. Please be a bit more flexible and help (vs.
be dogmatic and explain you have the truth and all others are wrong :-).

Regards

Francis.Dupont@fdupont.fr


From nobody Sun Apr  5 05:49:14 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8B471A86EB for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 05:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 yeVQc0CtX24K for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 05:49:11 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id EEBEF1A86E8 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 05:49:10 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.61] (88-111-169-158.dynamic.dsl.as9105.com [88.111.169.158]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 68DB61BC3E for <dhcwg@ietf.org>; Sun,  5 Apr 2015 12:49:06 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <201504051211.t35CBvv9086687@givry.fdupont.fr>
Date: Sun, 5 Apr 2015 13:49:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CB1C775-0954-461E-8964-E3E4CA4443D0@thehobsons.co.uk>
References: <201504051211.t35CBvv9086687@givry.fdupont.fr>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/-z1rXS_Xr4TgiUxLT1_jPP76FNQ>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 12:49:13 -0000

Francis Dupont <Francis.Dupont@fdupont.fr> wrote:

>> In the IPv6 world it's somewhat different.
>=20
> =3D> IMHO you are simply reopening the SLAAC vs DHCPv6 issues in the
> worst possible way. Please be a bit more flexible and help (vs.
> be dogmatic and explain you have the truth and all others are wrong =
:-).

I've not mentioned SLAAC (other than in passing), and I've certainly =
made no suggestion either way as to the relative merits of any approach =
to configuring addresses. If you are going to criticise someone, then =
please get your facts right when doing it.


Francis Dupont <Francis.Dupont@fdupont.fr> wrote:

>> Addresses received via DHCPv6 do not have any associated reachability
>> information. In order avoid the problems described in [RFC4943], =
hosts MUST
>> NOT assume that any IPv6 addresses are reachable on-link as a result =
of
>> receiving an IA_NA or IA_TA; IPv6 addresses obtained from IA_NA or =
IA_TA
>> MUST NOT be configured with any prefix length except /128.
>=20
> =3D> I fully disagree about the second part (second MUST NOT), in =
particular
> for IA_NA's, because if DHCPv6 doesn't provide the info this doesn't
> mean this is not available.

What you appear to be saying is that we can throw the DHCP derived info =
in a pot with <unspecified other info> to derive something that isn't =
needed. And it appears a big driver behind that is the "we've always had =
a subnet with an address, several implementations have done it that way, =
and so it's the only way to do it regardless of whether it's the best =
way or not".

Or, that's the way we've always done it and we're not prepared to =
change.

Is that not inflexible dogma ?


So now, (off list) I've been accused of applying "this implementation is =
the only way to do it" and (on list) being dogmatic against that way of =
doing it.


From nobody Sun Apr  5 05:59:32 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B401A878A for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 05:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 6lhhk4lycvUl for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 05:59:30 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 21FB11A8789 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 05:59:30 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id D1443DA00BC; Sun,  5 Apr 2015 12:59:29 +0000 (UTC)
Received: from [10.0.20.174] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sun, 5 Apr 2015 05:59:23 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <201504051056.t35AugSN081830@givry.fdupont.fr>
Date: Sun, 5 Apr 2015 08:59:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <008C494E-6E84-4EB8-B188-15FC202D619F@nominum.com>
References: <201504051056.t35AugSN081830@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/XTlrhxXx9YdymwLeqdTGd5_BGpc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 12:59:31 -0000

On Apr 5, 2015, at 6:56 AM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:
>> Addresses received via DHCPv6 do not have any associated reachability
>> information. In order avoid the problems described in [RFC4943], =
hosts MUST
>> NOT assume that any IPv6 addresses are reachable on-link as a result =
of
>> receiving an IA_NA or IA_TA; IPv6 addresses obtained from IA_NA or =
IA_TA
>> MUST NOT be configured with any prefix length except /128.
>=20
> =3D> I fully disagree about the second part (second MUST NOT), in =
particular
> for IA_NA's, because if DHCPv6 doesn't provide the info this doesn't
> mean this is not available.

So:

Addresses received via DHCPv6 do not have any associated reachability
information. In order avoid the problems described in [RFC4943], hosts =
MUST
NOT assume that any IPv6 addresses are reachable on-link as a result of
receiving an IA_NA or IA_TA. IPv6 addresses obtained from IA_NA or IA_TA
MUST NOT be used to form an implicit prefix with a length other than =
128.


From nobody Sun Apr  5 07:27:45 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA6A1A8A62 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 DDstD_lQsNV5 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:27:40 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 95CBD1A896B for <dhcwg@ietf.org>; Sun,  5 Apr 2015 07:27:40 -0700 (PDT)
Received: from tmo-113-142.customers.d1-online.com ([80.187.113.142] helo=[10.0.0.189]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YelWT-0002RY-Tn; Sun, 05 Apr 2015 16:27:37 +0200
Message-ID: <55214589.3080409@si6networks.com>
Date: Sun, 05 Apr 2015 16:24:09 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>,  "Bernie Volz (volz)" <volz@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <CAKD1Yr3AAM1SQoTgKDwHakjE790fnmtgBwm631+a_2KRZqwcMw@mail.gmail.com>
In-Reply-To: <CAKD1Yr3AAM1SQoTgKDwHakjE790fnmtgBwm631+a_2KRZqwcMw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/9K4_AkXSN-XSxD7yr7PoxEC6uy0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 14:27:42 -0000

On 04/04/2015 04:38 AM, Lorenzo Colitti wrote:
> On Thu, Apr 2, 2015 at 2:30 AM, Bernie Volz (volz) <volz@cisco.com
> <mailto:volz@cisco.com>> wrote:
> 
>     So, I will propose that the DHC WG “drop this work” (mark the ID as
>     dead). Objections? Comments?
> 
> 
> Seems reasonable to me. We should definitely address the question of
> privacy, but that should be done without dictating implementation. 

We're not dictating implementation. Why do you think so?

We're specifying one way to do it. But no one is mandating that you
should do it this way. For instance, this document does not update any
existing RFC.

(and the next revision of default-iids will be clear in this respect).

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Apr  5 07:35:30 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 068471A8A8A for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 k85IvDQPDD-v for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:35:27 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 19C0E1A8A82 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 07:35:26 -0700 (PDT)
Received: from tmo-113-142.customers.d1-online.com ([80.187.113.142] helo=[10.0.0.189]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Yele0-0002T6-Is; Sun, 05 Apr 2015 16:35:24 +0200
Message-ID: <552146B4.7050405@si6networks.com>
Date: Sun, 05 Apr 2015 16:29:08 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>, Bernie Volz <volz@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com>
In-Reply-To: <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Q3ZaRJcCID4CIrI1zJz6SnZSifg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 14:35:28 -0000

On 04/01/2015 09:18 PM, Ted Lemon wrote:
>> Why are stable privacy addresses useful when using DHCPv6? First,
>> DHCPv6 addresses are probably random and there are usually ways to
>> configure servers to 'retain' a binding for a period of time beyond
>> the "normal" end of the lease (at least our server has two
>> techniques - grace periods and affinity periods).
> 
> If it's not specified that they are random, they can't be assumed to
> be random.   E.g., what if the DHCP server just uses your EUI64?

Exactly (and we all know what they say about "assumptions"). The next
rev of 6man's default-iids I-D wil have words in this respect.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Apr  5 07:35:38 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B851D1A8A9A for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 vDfE_9JowaJN for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:35:29 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 9A8F61A8A82 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 07:35:29 -0700 (PDT)
Received: from tmo-113-142.customers.d1-online.com ([80.187.113.142] helo=[10.0.0.189]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Yele3-0002TC-KP; Sun, 05 Apr 2015 16:35:28 +0200
Message-ID: <55214802.1070305@si6networks.com>
Date: Sun, 05 Apr 2015 16:34:42 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Q35SanGNDhIfsk3S5HasqlAjYtw>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 14:35:30 -0000

On 04/01/2015 09:52 PM, Bernie Volz (volz) wrote:
> 
> So, we're back to the question as to whether
> draft-ietf-dhc-stable-privacy-addresses document is needed (and if it
> is, whether it is Informational). If you really like the algorithm
> and want to suggest to server implementers here is one you can use,
> that's fine but it should be Informational then. I don't see this as
> required to implement.

I think there's some misunderstanding wrt what a Std Track RFC means.
The fact that an RFC is published in Standards Track does not mean (by
itself), that you have to implement it (for instance, that's why we have
e.g. RFC1122, RFC1812, and IPv6's Node Requirements RFC).

Rather, it means "If you're going to implement this, this is how you
should do it. A DHCPv6-server vendor is 100% free to *not* implement
this document. But if they want the feature, the document says how to
implement it.

The reason for which the document is Std Track is because there are
requirements for the mechanism to work as expected. If you use e.g.
different algorithms in different servers (on the same subnet), the
mechanism will not work as expected. That's it.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Apr  5 07:49:12 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F13881A8AF0 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 E3xsUNgEGQBd for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:49:09 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 E8B7C1A8ADE for <dhcwg@ietf.org>; Sun,  5 Apr 2015 07:49:08 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YelrF-0002VY-4a; Sun, 05 Apr 2015 16:49:07 +0200
Message-ID: <552148F4.9000406@si6networks.com>
Date: Sun, 05 Apr 2015 16:38:44 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA3230D@xmb-rcd-x04.cisco.com>, <E9A1A551-6B12-4383-B65C-4DC974CC3A7A@nominum.com> <BC8728E9-7370-447B-99EE-0B3DE1D59CC0@cisco.com>
In-Reply-To: <BC8728E9-7370-447B-99EE-0B3DE1D59CC0@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/2cRkJ0THeKPlfcWSsd_KKxARcT0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 14:49:11 -0000

On 04/02/2015 04:20 AM, Bernie Volz (volz) wrote:
> I don't see this as required to be normative. It creates no interop issues. The market can decide what they want server (& client) implementers to provide.

Exactly: No one forces you or mandates that you implement this document.
That's why it doesn't update the core DHCPv6 RFC.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Apr  5 07:56:35 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7BFC1A8AF4 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 N68xBqMAkJts for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 07:56:33 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 515561A8BB2 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 07:56:30 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YelyM-0002Wm-Ip; Sun, 05 Apr 2015 16:56:27 +0200
Message-ID: <55214D0E.3030404@si6networks.com>
Date: Sun, 05 Apr 2015 16:56:14 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>,  "Bernie Volz (volz)" <volz@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <CAKD1Yr0_WEbR20ghJNx8n5fPf=Yrqp=wZz_Q_7J2L7c5xDzVcg@mail.gmail.com>
In-Reply-To: <CAKD1Yr0_WEbR20ghJNx8n5fPf=Yrqp=wZz_Q_7J2L7c5xDzVcg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/kV1lTGPoqGgKYwe65_QBDgLrCYQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 14:56:34 -0000

On 04/02/2015 01:28 AM, Lorenzo Colitti wrote:
> On Thu, Apr 2, 2015 at 4:52 AM, Bernie Volz (volz) <volz@cisco.com
> <mailto:volz@cisco.com>> wrote:
> 
>     So, we're back to the question as to whether
>     draft-ietf-dhc-stable-privacy-addresses document is needed (and if
>     it is, whether it is Informational). If you really like the
>     algorithm and want to suggest to server implementers here is one you
>     can use, that's fine but it should be Informational then. I don't
>     see this as required to implement.
> 
> +1. draft-ietf-dhc-stable-privacy-addresses does not really provide much
> value on top of assigning addresses randomly. Address assignment via
> IA_NA is fundamentally stateful, so I don't see a lot of gain in making
> it "deterministic unpredictable" as opposed to "random unpredictable".

You get stability of the address, even in scenarios in which you have
multiple DHCPv6 servers, without the need of an additional protocol for
synchronizing the address leases database. An approach such as that
specified by this document is mentioned in RFC7031 itself. e.g.:

"  Also, the typical large address space (close to 2^64 addresses on /64
   prefixes expected to be available on most networks) may make managing
   address assignment significantly different from DHCPv4 failover.  In
   DHCPv4, it was not possible to use a hash or calculated technique to
   divide the significantly more limited address space, and therefore,
   much of the protocol that deals with pool balancing and rebalancing
   might not be necessary and can be done mathematically."

If you think the extra value is worth its implementation, you implement
it. If you don't, you don't.

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Apr  5 08:27:28 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BBD91AC82C for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 08:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 QRXC5HntB5RA for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 08:27:26 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 142F61AC7E7 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 08:27:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2506; q=dns/txt; s=iport; t=1428247646; x=1429457246; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=A6bl9MjZvOrMyHNmhpt0hWoy0PgjvKHIdv1Uwzh8s/k=; b=JPJ3MXqgPi89mKo7Db/s/1hRkVeG7+YUMA8BxNK2IBuzGmy2KlQnfHD3 YprQGhNRrX4B+ZK9yOLkCR+9hLTcWcJos0Q6m2EOD39FlTVirtRvSer5i DzjMY/G5kJm46KiFXyy5PadOrxl0HJRz84rd2XMH2EUjpx5GxcNZo+7t1 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AaBQAQVCFV/51dJa1cgwiBLgXLKQKBFkwBAQEBAQF+hB4BAQEEJxM/DAQCAQgOAwQBAQEKFAUEBzIUCQgCBAENBQiIJ8p8AQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sphC4aJgsHBoMRgRYBBJBrix+GGIQYiQcigjOBPG+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,527,1422921600"; d="scan'208";a="409442875"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 05 Apr 2015 15:27:03 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t35FR2Te013718 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 5 Apr 2015 15:27:02 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Sun, 5 Apr 2015 10:27:02 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Fernando Gont <fgont@si6networks.com>, Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUWByZTAVuV8ESYM5tVpMLK4p04ge2AgABZ+YD//7DXMIAGSRkA//+4kTA=
Date: Sun, 5 Apr 2015 15:27:01 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA3DB05@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com>
In-Reply-To: <55214802.1070305@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.194]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/RQt8ELQQpn4Go8ESKUS7tmX1lMU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 15:27:27 -0000

No, I do not misunderstand. What I meant was that a standards track documen=
t has much more "weight" than an informational document. And, as there are =
other ways with DHCP to provide for stability and "random" addresses, this =
is just one technique.

You and I can debate the merits of this document back and forth all we want=
, but that won't help us reach consensus. We really need to hear from other=
s. Silence is difficult to read as it may mean almost anything.

We may have to wait until Prague to get at least an "in-room" consensus as =
we can then ask what people want to do (with confirmation of the result on =
the list). We can ask:
1. Do you want to move the document forward as Standards Track?
2. Do you want to move the document forward as Informational?
3. Do you want to not move this document forward?

- Bernie

-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com]=20
Sent: Sunday, April 05, 2015 10:35 AM
To: Bernie Volz (volz); Ted Lemon
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-address=
es -> abandon work? / IA_NA applicability

On 04/01/2015 09:52 PM, Bernie Volz (volz) wrote:
>=20
> So, we're back to the question as to whether=20
> draft-ietf-dhc-stable-privacy-addresses document is needed (and if it=20
> is, whether it is Informational). If you really like the algorithm and=20
> want to suggest to server implementers here is one you can use, that's=20
> fine but it should be Informational then. I don't see this as required=20
> to implement.

I think there's some misunderstanding wrt what a Std Track RFC means.
The fact that an RFC is published in Standards Track does not mean (by itse=
lf), that you have to implement it (for instance, that's why we have e.g. R=
FC1122, RFC1812, and IPv6's Node Requirements RFC).

Rather, it means "If you're going to implement this, this is how you should=
 do it. A DHCPv6-server vendor is 100% free to *not* implement this documen=
t. But if they want the feature, the document says how to implement it.

The reason for which the document is Std Track is because there are require=
ments for the mechanism to work as expected. If you use e.g.
different algorithms in different servers (on the same subnet), the mechani=
sm will not work as expected. That's it.

Thanks,
--
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Apr  5 12:29:54 2015
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBAD1ACE01 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 12:29:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.562
X-Spam-Level: 
X-Spam-Status: No, score=-1.562 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 vCPDOFTYU-4Q for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 12:29:52 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 226491ACE00 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 12:29:51 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t35JTBHv015532; Sun, 5 Apr 2015 21:29:11 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201504051929.t35JTBHv015532@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Lorenzo Colitti <lorenzo@google.com>
In-reply-to: Your message of Thu, 02 Apr 2015 16:37:09 +0900. <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> 
Date: Sun, 05 Apr 2015 21:29:11 +0200
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/k-qRpU199TaAw44QPRGWPEZeALs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 19:29:53 -0000

 In your previous mail you wrote:

>  Addresses received via DHCPv6 do not have any associated reachability
>  information. In order avoid the problems described in [RFC4943], hosts MUST
>  NOT assume that any IPv6 destinations are reachable on-link as a result of
>  receiving an IA_NA or IA_TA. In order to communicate to any destination
>  that is not a link-local address, the host must also have obtained
>  reachability information by other means such as a Router Advertisement or
>  manual configuration.

=> far better than previous second MUST NOT proposal... If you still want
a /128 in the text it should be enough to add a "without reachability
information" condition.

Regards

Francis.Dupont@fdupont.fr

PS: the reference for "reachability information" is RFC 4861. It is where
one can get definitions for a prefix, on/off-link, reachability itself,
etc. And BTW the answer to the address which belongs to 2 prefixes problem
(longest prefix match, section 2.1).


From nobody Sun Apr  5 12:55:28 2015
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 683771ACE23 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 12:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.262
X-Spam-Level: 
X-Spam-Status: No, score=-1.262 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 lVuuJX3QiOwq for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 12:55:26 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87E911ACE1F for <dhcwg@ietf.org>; Sun,  5 Apr 2015 12:55:26 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t35JslFj017249; Sun, 5 Apr 2015 21:54:47 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201504051954.t35JslFj017249@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
In-reply-to: Your message of Thu, 02 Apr 2015 11:05:56 PDT. <CAJE_bqfAmTFJwVL3VTK+w6rSu_TPPPrmWet2nmi-YfcKyts3PA@mail.gmail.com> 
Date: Sun, 05 Apr 2015 21:54:47 +0200
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/DjjrvA1jy_2lJ4UVjnsLgi-Dko0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 19:55:27 -0000

 In your previous mail you wrote:

>  That would lead to a long standing debate of whether DHCPv6 should
>  propagate on-link prefix and/or default route information, and I tried
>  to avoid that part of discussion as I knew it would never converge:-)
>  In any case if we really want to discuss it again, it would be better
>  to do it outside the scope of 3315bis.

=> +1

Francis.Dupont@fdupont.fr


From nobody Sun Apr  5 13:08:03 2015
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F313F1ACE2D for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 13:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.562
X-Spam-Level: 
X-Spam-Status: No, score=-1.562 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 eaxMzTrx-v2M for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 13:08:00 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6CCE1ACE2E for <dhcwg@ietf.org>; Sun,  5 Apr 2015 13:07:59 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t35K7GQE018372; Sun, 5 Apr 2015 22:07:16 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201504052007.t35K7GQE018372@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-reply-to: Your message of Thu, 02 Apr 2015 20:47:26 -0000. <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com> 
Date: Sun, 05 Apr 2015 22:07:16 +0200
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/W9UHhWsnocb7GtphLHyN7bk-HjM>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2015 20:08:01 -0000

 In your previous mail you wrote:

>  Folks should read RFC5942.  See section 4, bullet 1. 

=> good catch!

Thanks

Francis.Dupont@fdupont.fr


From nobody Sun Apr  5 17:33:26 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 838DD1ACE8D for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 17:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 EEhVSHO8j6f6 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 17:33:24 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D0D01ACE87 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 17:33:24 -0700 (PDT)
Received: by igbqf9 with SMTP id qf9so10509806igb.1 for <dhcwg@ietf.org>; Sun, 05 Apr 2015 17:33:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bvsrsgvUD5DwyovFIkO1GYzuBH5ls8tpAePowQ4aPyU=; b=Jb1BJylya3tW/EVAk1hr4fg700gIsvkUvo5uMwYUssU+xtWyspw2i5azKjMtbTG3Ft gyvqoyGClTE6/uEWh/GU3iDtm1gaYzfw7KoQ6kfzHwQr2b5keFrng/MqLZHR6GYm7e2j acN17oZ787cUuH7Mgv+pUMGDxyBLpZboRywMnRyxCPGz7wVquNMWpHi7aoFpm6COCPp/ y9cmu1xeIK+Mon6px6yCH2Wr+aRsNYHnLIN4KT6J63OmkIkgcThMoNZSm3WlR1ku2IJy jCNjQWXDVSpUBWM0YR4LX379bD6U9H8UiCzRlefuUDmCZSE5V0IWSyY4BETRpjtZDqwl AEEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=bvsrsgvUD5DwyovFIkO1GYzuBH5ls8tpAePowQ4aPyU=; b=aSQnHqhRmK4aMLoeTz1kDtoK8FvgRu7bWB2XIHJPY/m2Cmlz3oT94B1oaI+dV12+sH RbEcaMQDER8TeIJRadPc4yr0horZlavoqMS237c3llh2X6nU5IoYxF9AKdNfqK60ie97 IhM4zK6/oBm2cZVIbrDEWHr7aeEt4L/YzD/WxAZc8aOp1kiTgQaSm0vHVN7ScJEU9vDS Ga+fpqFEDxxIU/KO9pbsEOm0iw8L7xsyBU5F2O66fijeYEZM4OT9lWo1uNumh1vm6G/E nLvNrDU2zWsUC73BSK1iMyJiVFtodyBpwlCRWWg4mPpLl0AdnQITRk8ghhIB4rzVnKuI o5tA==
X-Gm-Message-State: ALoCoQlj8jtYnJz1kxkXt96MLMlR4dDmCTLIYo0EBXBxLNMdhYTqNdvr9O8iEaD879e/fXwi4PAB
X-Received: by 10.50.4.97 with SMTP id j1mr19515875igj.46.1428280403743; Sun, 05 Apr 2015 17:33:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Sun, 5 Apr 2015 17:33:03 -0700 (PDT)
In-Reply-To: <008C494E-6E84-4EB8-B188-15FC202D619F@nominum.com>
References: <201504051056.t35AugSN081830@givry.fdupont.fr> <008C494E-6E84-4EB8-B188-15FC202D619F@nominum.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 6 Apr 2015 09:33:03 +0900
Message-ID: <CAKD1Yr2GTC4O_sdykas87SjCGZgX-+_hB3anYUth7TqL-ezTFA@mail.gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c2cd4e1b07c9051303724d
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/qTWr4LsvS5m2Fyf1dgn3BPZwUUI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2015 00:33:25 -0000

--001a11c2cd4e1b07c9051303724d
Content-Type: text/plain; charset=UTF-8

On Sun, Apr 5, 2015 at 9:59 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> Addresses received via DHCPv6 do not have any associated reachability
> information. In order avoid the problems described in [RFC4943], hosts MUST
> NOT assume that any IPv6 addresses are reachable on-link as a result of
> receiving an IA_NA or IA_TA. IPv6 addresses obtained from IA_NA or IA_TA
> MUST NOT be used to form an implicit prefix with a length other than 128.
>

LGTM, except as Hemant says, I'd replace the "In order avoid the problems
described in [RFC4943]," with "As specified by [RFC5942] section 4,"

--001a11c2cd4e1b07c9051303724d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
un, Apr 5, 2015 at 9:59 PM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mail=
to:Ted.Lemon@nominum.com" target=3D"_blank">Ted.Lemon@nominum.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-le=
ft-style:solid;padding-left:1ex"><span class=3D"">Addresses received via DH=
CPv6 do not have any associated reachability<br>
information. In order avoid the problems described in [RFC4943], hosts MUST=
<br>
NOT assume that any IPv6 addresses are reachable on-link as a result of<br>
</span>receiving an IA_NA or IA_TA. IPv6 addresses obtained from IA_NA or I=
A_TA<br>
MUST NOT be used to form an implicit prefix with a length other than 128.<b=
r></blockquote><div><br></div><div>LGTM, except as Hemant says, I&#39;d rep=
lace the &quot;In order avoid the problems described in [RFC4943],&quot; wi=
th &quot;As specified by [RFC5942] section 4,&quot;</div></div></div></div>

--001a11c2cd4e1b07c9051303724d--


From nobody Sun Apr  5 17:40:34 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F261ACE99 for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 17:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 I-_tdxDATVdo for <dhcwg@ietfa.amsl.com>; Sun,  5 Apr 2015 17:40:32 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 284501ACE95 for <dhcwg@ietf.org>; Sun,  5 Apr 2015 17:40:29 -0700 (PDT)
Received: by iebrs15 with SMTP id rs15so11560937ieb.3 for <dhcwg@ietf.org>; Sun, 05 Apr 2015 17:40:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xLObjzRiF8UH/ZQGCtdwQnSpqlaTZCMzgriTMHVoOjs=; b=T83A51i4HOeu5lKiip+C62GalPsyohsQyIqWbxagz8ab12CIvvsI0UY7FlFO8glbBG wIcQT5GxAHSQ6ZbATP8oA8LlzfYB6kLCn4YYWODAv+vz7FBtOQJCTbjqsSZ821acI3Sl nWoRvgNF5eDvdX6dxmbTSA9IErGYTte8WvqEj/gO4+dO9/c3eCLHXTehRruj6jIDHX19 x03RHJ2eZcGp9zM07oaE1zbOuRqOKmVBh+ypYl/g6udFE+O5Qix+aTSwV7PX5xOC/EV4 TF2wWCoSKBQwPAbVP1tN952FS3uPNGyUTcua63gT93AnqYF4NYUQ5W2xOl71BvpWBXmq EFkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=xLObjzRiF8UH/ZQGCtdwQnSpqlaTZCMzgriTMHVoOjs=; b=c2Y81XZjmZkfHFl/X3FsAtxPeYBiirvZhnDF4NGGnD5y/F6E1ST7yK/vo4Xn3p9QyL CyOOaL+wWx4UTbQfE8QBOKGHdl0BGS9kGf0DgL3/INewpViIO/QKg6urwYpPUTqpGjDo jMuYOERIgw9qHqqw1Lrk/91/M2JIkQY3eMXiKjtCq8sLF36hwVPK6oDuDr+KnCZ8LUrL 69HEbbenn2yUgpLiKTK5XY1lm+4RUl6QdOyebK5RaYmpZGmVDfhvFED1PO/1hSA52/Xv TSRNNbFKTdL6oaYL2HTBjdKYg8jp/dHt+D7mXZ9e5oqC0GBYNk5Jxj8NvS/50PA0jTLa GOVw==
X-Gm-Message-State: ALoCoQni9JgpQXzeWrANL0Z0P2zVt7rIWc9p+ukK3Kmkqc2W2T6Qzdy0KjRCuUv9atQ8+x+808Bp
X-Received: by 10.107.46.155 with SMTP id u27mr18256522iou.87.1428280828517; Sun, 05 Apr 2015 17:40:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Sun, 5 Apr 2015 17:40:08 -0700 (PDT)
In-Reply-To: <55214802.1070305@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 6 Apr 2015 09:40:08 +0900
Message-ID: <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a113ac5b66c7dd20513038b9d
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/rqY30itUYnNyzQku2ckDhvCaos0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2015 00:40:33 -0000

--001a113ac5b66c7dd20513038b9d
Content-Type: text/plain; charset=UTF-8

On Sun, Apr 5, 2015 at 11:34 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> Rather, it means "If you're going to implement this, this is how you
> should do it. A DHCPv6-server vendor is 100% free to *not* implement
> this document. But if they want the feature, the document says how to
> implement it.
>

I don't think it's a good idea for the IETF to make a statement that "if
you want to provide stable addresses using DHCP, this is the way you have
to do it". There are other ways to implement stable addressing than the
algorithm proposed in this draft.

--001a113ac5b66c7dd20513038b9d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
un, Apr 5, 2015 at 11:34 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bord=
er-left-style:solid;padding-left:1ex">Rather, it means &quot;If you&#39;re =
going to implement this, this is how you<br>
should do it. A DHCPv6-server vendor is 100% free to *not* implement<br>
this document. But if they want the feature, the document says how to<br>
implement it.<br></blockquote><div><br></div><div>I don&#39;t think it&#39;=
s a good idea for the IETF to make a statement that &quot;if you want to pr=
ovide stable addresses using DHCP, this is the way you have to do it&quot;.=
 There are other ways to implement stable addressing than the algorithm pro=
posed in this draft.</div></div></div></div>

--001a113ac5b66c7dd20513038b9d--


From nobody Mon Apr  6 11:46:55 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8140C1A90BD for <dhcwg@ietfa.amsl.com>; Mon,  6 Apr 2015 11:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 NApJ7eiVyiIK for <dhcwg@ietfa.amsl.com>; Mon,  6 Apr 2015 11:46:52 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 354931A90BC for <dhcwg@ietf.org>; Mon,  6 Apr 2015 11:46:52 -0700 (PDT)
Received: by igbqf9 with SMTP id qf9so26566545igb.1 for <dhcwg@ietf.org>; Mon, 06 Apr 2015 11:46:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=LOe8lliAion+k0N/ntRwfYy7tGAPrk4qol+/NIdwqrw=; b=0RrwOEHw/3lyPQ7M8bOzqnaq///riIAv6RztGMMm6vsjhQlj6Jv9sRtDjjQD6GIMbz B9uXLFRbQ3VQAf6bNFWeWPQc8N2DeEjqfPe7zOsYpOqUh3k3rWKdlJpLjCjJVUUZYz7E GP/Ebp2GVPlFF1bC0cmIVQWtN/tsFTxcwUgmmiUq8/YICokFsbiTtPkl6o+hnU0vS/49 3PuoGj5fjQ8tP8Xbg/GrHCcOvm6vmqv0y4vvhQHkVmcJVxB1Sd/JYId/C+4EO0VoWYKK iOArDZJP7lyjbwNE8hBH7eqi+jDSMmO8b9DJLPpe1eOU6qO+zHPylbtIoZRe8tkIKWw3 nyqA==
MIME-Version: 1.0
X-Received: by 10.50.254.99 with SMTP id ah3mr48821016igd.12.1428346011722; Mon, 06 Apr 2015 11:46:51 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.21.3 with HTTP; Mon, 6 Apr 2015 11:46:51 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com>
Date: Mon, 6 Apr 2015 11:46:51 -0700
X-Google-Sender-Auth: 06g9ruOObR6AOmJmF6cqcrN5QJ0
Message-ID: <CAJE_bqck8KzSJuDWLucZn61g61Lvf9NQTLV0hUECdem5p3fswQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/PfFh1IsHvWa_0sEZsBpvrs6Qnjs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2015 18:46:53 -0000

At Wed, 1 Apr 2015 17:30:50 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> To the WG and co-authors of this document, as a follow up from the
> Dallas (IETF-92) DHC WG meeting, there is the question as to next
> step(s) for draft-ietf-dhc-stable-privacy-addresses.

[...]

> So, I will propose that the DHC WG "drop this work" (mark the ID as
> dead). Objections? Comments?

I have no objection to abandoning it.  But I wouldn't be opposed to
publishing it either.  In that case Informational seems to be a good
choice.  My reasons follow:

As far as I understand it, the main value of this approach is:

1. allow DHCPv6-assigned addresses to be (much) less predicable, AND
2. make sure the same address is assigned to the same host in the same
   particular link over multiple DHCPv6 sessions

I guess we generally agree on the need for #1, especially for some
kind of deployment.  I also think value #2 would be considered very
useful, even if not critical - it will be convenient if I can get the
same address on my laptop or smart phone or tablet when I get back to
home.

So the question is whether this specific approach to achieve these
goals is worth an RFC.

As you pointed out, (unlike SLAAC) it would be much easier to do this
in the case of DHCPv6 *in practice*: just assign addresses randomly
for the first time but remember and reuse the binding beyond a single
DHCPv6 session as much/long as possible.  This approach is less
reliable than dhc-stable-privacy-addresses since the server could
discard the binding for some reason (storage/memory requirement, etc),
but it's probably good enough in practice (it at least provides the
same level of stability as that we have today for DHCPv4).  It will
also not work if the server is replaced with a new one, but again you
pointed out, such events would be rare enough in practice.  It may
also be difficult to achieve these goals with failover cases, but,
once again, failover itself is probably a less frequent event
(otherwise the network has a more serious issue than address
stability), and the operational cost with dhc-stable-privacy-addresses
to make this case work also seems to be non-negligible.

So, I tend to agree that the advantage of this particular proposal is
not so strong.  In that sense I have no objection to abandoning the
work.

Whether we still want to publish it would depend on whether we want to
show a solution that provides the value #1 and #2 above and that 100%
works without relying on server state or replacement.  Personally, I
don't see a strong need for that (practically good solution seems to
be enough), but if some other people want to have it, I wouldn't be
opposed to that desire.

In that case, I think it's better to publish it as an RFC (rather than
a personal blog or white paper or something like that) since one major
benefit of this approach is that it works even when we replace the
server, and to make it work different server implementations will have
to use the same algorithm.  And, in this case, I don't have a strong
opinion on which standard level is the best simply because I'm not a
standard-level police, but Informational seems to be good enough.
This approach does not affect protocol interoperability in its strict
sense, and unlike the SLAAC counterpart (RFC7217, to which the same
argument applies) we have a reasonable alternative for the expected
goal.  So the standard truck is probably too much for it.

--
JINMEI, Tatuya


From nobody Tue Apr  7 12:45:55 2015
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A811B3B8C for <dhcwg@ietfa.amsl.com>; Tue,  7 Apr 2015 12:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 SwoOOTdoHAiO for <dhcwg@ietfa.amsl.com>; Tue,  7 Apr 2015 12:45:53 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2B761B3B8B for <dhcwg@ietf.org>; Tue,  7 Apr 2015 12:45:52 -0700 (PDT)
Received: by lbcga7 with SMTP id ga7so1270311lbc.1 for <dhcwg@ietf.org>; Tue, 07 Apr 2015 12:45:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Q8kWywNsde3ND21XSVIiRL7DbYmZje241JjuXpdPdTI=; b=qf2gNtubhblZ/ZCT1TaKkw+BxkJXPrDaUeqqTJdNrspZzS39iDq2t7LSTFiz+RSDoo v3nxlA6s11uejMJyR96uCcvfEqaMB4r4ipJTa3OFJLFgu3ZBVNf5SlGgLyEgh8EjrtNf yAvSt7drEYFEIeGwX9L3+0DSCYk/V5ynPdYUhM8TWXF9jX0dZRjFV6jt/m+OkmqdtfBb fU/lFSt+tu59Eyp+0q26SjBPfI8OonEhq9DKUuqKT9qhqM1Qdl/bVIpYJIm9HA28gKiq /BbmLZuwd1MMvgSto8Xbb0VbewbTG1y+Q/pNCYCgwwSZM6zU1W/UkbdZrlaXvpOtcyEO IZCw==
X-Received: by 10.112.145.230 with SMTP id sx6mr19712251lbb.70.1428435951151;  Tue, 07 Apr 2015 12:45:51 -0700 (PDT)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id ej5sm1345122lad.5.2015.04.07.12.45.49 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Apr 2015 12:45:50 -0700 (PDT)
Message-ID: <552433E9.2010106@gmail.com>
Date: Tue, 07 Apr 2015 21:45:45 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1CA38753@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA38753@xmb-rcd-x04.cisco.com>
X-TagToolbar-Keys: D20150407214545754
X-Forwarded-Message-Id: <489D13FBFA9B3E41812EA89F188F018E1CA38753@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/mtwkvSNNJLLJEu1KEblox1p1404>
Subject: [dhcwg] Summary of the 3315bis discussions in Dallas
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 19:45:55 -0000

These are the notes from the DHC WG meeting in Dallas that are related
to 3315bis work. They reflect what was the general consensus in the
room. If you didn't participate and have a different opinion, please
speak up. If we don't hear any objections, we'll assume that the
consensus on those topics was reached and the changes will be applied in
the 3315bis draft.

During the DHC WG session at the Dallas IETF-92 meeting, several
DHCPv6bis issues were discussed. We are posting this summary to the list
to confirm that (a) our summary of each issue is correct, and (b) that
no one has any objections to the intended actions. The issue ticket
numbers referenced can be viewed at
http://trac.tools.ietf.org/group/dhcpv6bis/report. The slides used are
at http://www.ietf.org/proceedings/92/slides/slides-92-dhc-9.pdf. This
is to continue work on http://tools.ietf.org/html/draft-ietf-dhc-rfc3315bis.

#142 - Reorganize server/client behavior? (Slide 5)
– No objections

#144 – Clarify unknown options handling (Slide 6)
 – No objections

#81 – Should protocol options be included in ORO? (Slide 7)
– Ted suggested we might want to request IANA to add a new column to the
options table as to whether it MUST be in ORO for the client to receive.
This seemed like a good way to solve this problem. The default needs to
be “YES” unless the option definition document says otherwise. Perhaps
this should be done as a separate draft (Bernie’s suggestion while
working on this summary).

#18 – Is ORO mandatory? (Slide 8)
– Servers MUST accept messages without an ORO. SOL_MAX_RT MUST be in
ORO, if ORO is included, for Solicit/Request/Renew/Rebind (INF_MAX_RT
MAY be). INF_MAX_RT MUST be in ORO, if ORO is included, for
Information-Request (SOL_MAX_RT MAY be).

#68 – Prefix Length of Addresses (Slide 9)
– Yes, this should be documented. See DHC WG discussion thread starting
with http://www.ietf.org/mail-archive/web/dhcwg/current/msg16391.html.

#82 – IA_ADDR with :: Address (Slide 10)
– Discourage use of IA_ADDR and IA_PREFIX with all 0s (no hints or
requested address/prefix).

Ted suggested we document how clients get new addresses – by using a new
IA_ID with an IA_NA or IA_TA.

#114 – Clarify “hints” (Slide 11)
– This has to do with clients requesting a prefix delegation prefix
length. Bernie to send an email to WG to clarify issues and suggest text
changes.

#70 – Validate addresses in IA (Slide 12)
– The participants felt that there was no need to add anything more or
otherwise make changes in this area.

#86 – Information-request in Delayed Authentication Protocol (DAP)
(Slide 13)
– Ted suggested we remove DAP from DHCPv6bis as it is not
known to have been deployed by anyone. As far as we can tell, there's
only one implementation. (Tomek comment added during writing those
minutes: I did implement it in Dibbler. The mechanism, including option
formats, was underspecified and I had to make judgement decisions that
would likely prevent interop. I'm not aware of any other implementations
or deployments that use DAP in Dibbler).

Reconfiguration Key Auth. Protocol will be retained. This seemed like a
good way to solve this issue and reduce the size / complexity of the
document.

Tomek's comment while editing those notes. I strongly support this
proposal. That is especially important if our original plan to promote
DHCPv6 to Internet Standard still applies. In particular, RFC6410,
section 2.2 defines the maturity requirements for a standard. Note item 3:

   (3) There are no unused features in the specification that greatly
       increase implementation complexity.

Delayed Authentication Protocol matches this description. It is unused
(has anyone heard about anyone deploying this feature beyond lab tests?
I haven't.) and it has significant implementation complexity. Since
nobody deployed it in 11 years, then it's not usable. Let's get rid of it.

Tomek & Bernie


From nobody Wed Apr  8 02:44:21 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 491091B2EC1 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 02:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 O-oaYCOzZYP5 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 02:44:18 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 19D0F1B2EC0 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 02:44:18 -0700 (PDT)
Received: from [186.134.76.56] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YfmWs-0004Gi-0n; Wed, 08 Apr 2015 11:44:14 +0200
Message-ID: <5524D09B.3090706@si6networks.com>
Date: Wed, 08 Apr 2015 03:54:19 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/IB7inj-1pq6by7H7zf2ilPmFQbc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 09:44:20 -0000

Lorenzo,

On 04/05/2015 09:40 PM, Lorenzo Colitti wrote:
> On Sun, Apr 5, 2015 at 11:34 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     Rather, it means "If you're going to implement this, this is how you
>     should do it. A DHCPv6-server vendor is 100% free to *not* implement
>     this document. But if they want the feature, the document says how to
>     implement it.
> 
> I don't think it's a good idea for the IETF to make a statement that "if
> you want to provide stable addresses using DHCP, this is the way you
> have to do it". There are other ways to implement stable addressing than
> the algorithm proposed in this draft.

This is not what this document is about.

This document specifies *one* possible algorithm for producing stable
privacy-enhanced addresses. Nowhere does it say that it is the only way
to do it, and nowhere does it mandate that you support stable
privacy-enhanced addresses in the first place (or that, if you do, you
do it with this algorithm).

A vendor can assess himself whether this is an interesting feature, and
a user can enable this feature (if this algorithm is supported) if he
thinks its of value.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Apr  8 02:44:31 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C568F1B2EC9; Wed,  8 Apr 2015 02:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 eExW_ky7m3gN; Wed,  8 Apr 2015 02:44:27 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BECF41B2EC5; Wed,  8 Apr 2015 02:44:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150408094426.29609.28707.idtracker@ietfa.amsl.com>
Date: Wed, 08 Apr 2015 02:44:26 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SvMu23x-ykcitjGz9ndvZN3IZ4E>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-stable-privacy-addresses-02.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 09:44:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : A Method for Generating Semantically Opaque Interface Identifiers with Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
        Authors         : Fernando Gont
                          Will(Shucheng) Liu
	Filename        : draft-ietf-dhc-stable-privacy-addresses-02.txt
	Pages           : 10
	Date            : 2015-04-08

Abstract:
   This document specifies a method for selecting IPv6 Interface
   Identifiers, to be employed by Dynamic Host Configuration Protocol
   for IPv6 (DHCPv6) servers when leasing non-temporary IPv6 addresses
   to DHCPv6 clients.  This method is a DHCPv6 server side algorithm,
   that does not require any updates to the existing DHCPv6
   specifications.  The aforementioned method results in stable
   addresses within each subnet, even in the presence of multiple DHCPv6
   servers or DHCPv6 server reinstallments.  It is a DHCPv6-variant of
   the method specified in RFC 7217 for IPv6 Stateless Address
   Autoconfiguration.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-stable-privacy-addresses/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-stable-privacy-addresses-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-stable-privacy-addresses-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Apr  8 03:29:57 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8408C1B2F2E for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 PxMECOSnujUB for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:29:54 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3D941B2F28 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 03:29:54 -0700 (PDT)
Received: by igbqf9 with SMTP id qf9so34467863igb.1 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 03:29:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1baJ2m27IZsp9flrTvxvTMC46Bjj7o1rIU5wJBZ6D4o=; b=lLRcyovPyrAJLNVd0NMweRvd74Vd02J94iGV8PUMaIzFx5WgEPyMA9qzgdlrZYK6K7 4Zx5Jq/VVOeVFx0g+9mq0o6+uwX13JjWHRcTzvkzHS6uoee9tpNoY5R43NzG/sRQq1Uh ZJDjBVnacmwyyxiwmEypJJ+862kFnM0jeftBH9XmlygYOWe03m4qYi9c69QwjUnR0ET2 2re2c+jykb28CRh+dmyVbpty/R6xoZPm6w4LAwBMeeSW6f8uyNQOunMyCkyj2eWpd4sp V/CqGKi5H2SajZPpMmtq/p14MiGMnLriW+9SuH68QQvHMAlcbMRtHRjh5CkZ+PJ82cdX dWUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=1baJ2m27IZsp9flrTvxvTMC46Bjj7o1rIU5wJBZ6D4o=; b=mc/Z1X7VqWyoD5eKk6MPYSR7YB/W1w6ey6uTCNqT/7GePzvovNuDCmek9qceB4C/ib QfCYFnFx4MGBHmSaTBGP0FEOcemNmj2R2waWAuzcbZzkhOcx0N2Ad8FYJNlq7zdvc7fy ziAk2cJx7saW1IA918pzonuVbMRhjhbkDlrknUPTO86qQCzanEWFgwVCVSXjpBrEReYW LfdW0LrpPRpIYu3jYDC2aW7SdYmF3trZyZ99QLyev2y/E3oIQqVGLtWm4X0IOVy7T6xY 4uejx7UiUbgLXDHU7c3rKfI1a3l6czm8wLihWpognlTMfgEaTfj6wfREHx8FCw4QPLGu ZUfw==
X-Gm-Message-State: ALoCoQksixKN3qWKexpAp6/YSn0ukD24RkNk6X51Ma+ZGFi4gUyAX8rDcm2Ib5OzZlF8HvVcXGtZ
X-Received: by 10.107.46.155 with SMTP id u27mr36448205iou.87.1428488994061; Wed, 08 Apr 2015 03:29:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 03:29:33 -0700 (PDT)
In-Reply-To: <5524D09B.3090706@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 8 Apr 2015 19:29:33 +0900
Message-ID: <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a113ac5b60eae930513340388
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pxnQhweBrt9gR7QzfEw05YZCERc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 10:29:56 -0000

--001a113ac5b60eae930513340388
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 8, 2015 at 3:54 PM, Fernando Gont <fgont@si6networks.com> wrote:

> Nowhere does it say that it is the only way
> to do it, and nowhere does it mandate that you support stable
> privacy-enhanced addresses in the first place (or that, if you do, you
> do it with this algorithm).
>

Actually it does. For example:

   DHCPv6 server implementations conforming to this specification MUST
   generate non-temporary IPv6 addresses using the algorithm specified
   in this section.

and:

   A DHCPv6 server implementing this specification must select the IPv6
   addresses to be leased with the following algorithm:

--001a113ac5b60eae930513340388
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 8, 2015 at 3:54 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D"=
mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);borde=
r-left-style:solid;padding-left:1ex">Nowhere does it say that it is the onl=
y way<br>
to do it, and nowhere does it mandate that you support stable<br>
privacy-enhanced addresses in the first place (or that, if you do, you<br>
do it with this algorithm).<br></blockquote><div><br></div><div>Actually it=
 does. For example:</div><div><br></div><div><div>=C2=A0 =C2=A0DHCPv6 serve=
r implementations conforming to this specification MUST</div><div>=C2=A0 =
=C2=A0generate non-temporary IPv6 addresses using the algorithm specified</=
div><div>=C2=A0 =C2=A0in this section.</div></div><div><br></div><div>and:<=
/div><div><br></div><div><div>=C2=A0 =C2=A0A DHCPv6 server implementing thi=
s specification must select the IPv6</div><div>=C2=A0 =C2=A0addresses to be=
 leased with the following algorithm:</div></div></div></div></div>

--001a113ac5b60eae930513340388--


From nobody Wed Apr  8 03:31:22 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E477B1B2F30 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:31:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 nnqNh_6z4oUA for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:31:18 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ABC11B2F2F for <dhcwg@ietf.org>; Wed,  8 Apr 2015 03:31:18 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t38AVDkr029545; Wed, 8 Apr 2015 12:31:13 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8130D2067A5; Wed,  8 Apr 2015 12:32:17 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 736EE2067A1; Wed,  8 Apr 2015 12:32:17 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t38AUkZP018667; Wed, 8 Apr 2015 12:31:13 +0200
Message-ID: <55250356.9030303@gmail.com>
Date: Wed, 08 Apr 2015 12:30:46 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <551CEC1F.3070006@gmail.com> <CAJE_bqfAmTFJwVL3VTK+w6rSu_TPPPrmWet2nmi-YfcKyts3PA@mail.gmail.com> <551D8749.6090907@gmail.com> <F30838AF-E1A1-40D1-BC7E-B5993E388344@cisco.com>
In-Reply-To: <F30838AF-E1A1-40D1-BC7E-B5993E388344@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/5DpHaXzzKWhOp-JZGAhwcNH7QDI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 10:31:21 -0000

Le 02/04/2015 20:27, Ralph Droms (rdroms) a Ã©crit :
>
>> On Apr 2, 2015, at 2:15 PM 4/2/15, Alexandru Petrescu
>> <alexandru.petrescu@gmail.com> wrote:
>>
>> Le 02/04/2015 20:05, ç¥žæ˜Žé�”å“‰ a Ã©crit :
>>> At Thu, 02 Apr 2015 09:13:35 +0200, Alexandru Petrescu
>>> <alexandru.petrescu@gmail.com> wrote:
>>>
>>>>> I agree with this statement per se, but I think this is not
>>>>> sufficient, since it doesn't (clearly) answer the question of
>>>>> what the operator should do if they want to use DHCPv6-based
>>>>> address assignment in an isolated single-link (or "subnet")
>>>>> network.  The "architecturally correct" answer will be that
>>>>> they should deploy a node (which would probably be collocated
>>>>> on the same node as the DHCPv6 server) that sends RAs with
>>>>> router lifetime being 0 and with appropriate on-link
>>>>> prefix(es).
>>> [...]
>>>> But, a Router-DHCPv6Server with router lifetime 0 and on-link
>>>> prefix will make think the Host this is not a default router
>>>> and it should SLAAC its address (maybe in addition to
>>>> requesting one from DHCPv6). Is this what is meant by the
>>>> above?
>>>
>>> Not at all.  I didn't mean to say anything about SLAAC in the
>>> above "architecturally correct answer".
>>
>> I misread then, sorry.
>>
>>>> Another suggestion on another hand is to have DHCPv6 deliver a
>>>>  prefix length together with the address, and a default route.
>>>>  That'd be a form of independence, and avoid '/64'
>>>> CIDR-breaking assumptions.
>>>
>>> That would lead to a long standing debate of whether DHCPv6
>>> should propagate on-link prefix and/or default route
>>> information, and I tried to avoid that part of discussion as I
>>> knew it would never converge:-)
>>
>> Ok.
>>
>>> In any case if we really want to discuss it again, it would be
>>> better to do it outside the scope of 3315bis.
>>
>> I am not really saying we'd need to discuss it, unless we really
>> want it and it's simple to achieve.
>>
>> It would be very simple to achieve having prefixlen in DHCPv6
>> address allocations, be it just an option.
>
> No.  There is no such thing as a prefix length on an address.
>
> If DHCPv6 were to carry reachability information - and that is an
> unlikely hypothetical that I *really* don't care to discuss here -
> it must be in the form of a list of on-link prefixes, entirely
> disjoint from any assigned addresses.

That is a flexible way.  We can imagine that Server could tell client 1
or more prefixes to be 'on-link', almost in the same  way as the RA
tells it so.

On another hand, this will continue the difficulty for the Client to
decide which address belongs to which prefix.  This is a complex operation.

Were the server to indicate precisely which allocated address 'belong'
to which prefix then task would be easier to the Client.

Alex

>
> - Ralph
>
>>
>> Alex
>>
>>
>>>
>>> -- jinmei
>>>
>>>
>>
>>
>> _______________________________________________ dhcwg mailing list
>>  dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>



From nobody Wed Apr  8 03:35:21 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F131B2F3D for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 u-d0kP3jpRIY for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:35:17 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F7461B2F3C for <dhcwg@ietf.org>; Wed,  8 Apr 2015 03:35:17 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t38AZFUo013250 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 12:35:15 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 453A0206969 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 12:36:19 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3B7F92067A5 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 12:36:19 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t38AZAYb024260 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 12:35:15 +0200
Message-ID: <5525045B.5050204@gmail.com>
Date: Wed, 08 Apr 2015 12:35:07 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com>
In-Reply-To: <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/yXviqKOmXDnCiEcPVJxaj-7BBak>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 10:35:20 -0000

Le 02/04/2015 22:47, Hemant Singh (shemant) a écrit :
> Folks should read RFC5942.  See section 4, bullet 1.

The section says:
> 4. Host Rules
>
>
>    A correctly implemented IPv6 host MUST adhere to the following rules:
>
>    1.  The assignment of an IPv6 address -- whether through IPv6
>        stateless address autoconfiguration [RFC4862], DHCPv6 [RFC3315],
>        or manual configuration -- MUST NOT implicitly cause a prefix
>        derived from that address to be treated as on-link and added to
>        the Prefix List.  A host considers a prefix to be on-link only
>        through explicit means, such as those specified in the on-link
>        definition in the Terminology section of [RFC4861] (as modified
>        by this document) or via manual configuration.  Note that the
>        requirement for manually configured addresses is not explicitly
>        mentioned in [RFC4861].

Well, the linux stack implementation does not act that way. Adding an
address on an interface implies a routing table entry is added too.

When the above paragraph was written - which flavor of IP stack was 
considered?

Alex


>
> Hemant
>
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ralph Droms (rdroms)
> Sent: Thursday, April 02, 2015 4:43 PM
> To: Ted Lemon
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
>
>
>> On Apr 2, 2015, at 3:06 PM 4/2/15, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>>
>> On Apr 2, 2015, at 11:01 AM, Ralph Droms (rdroms) <rdroms@cisco.com> wrote:
>>> The semantics of the M/O bits - and, please, let's not revisit that /dev/null discussion? - are, at this point, informative only.  RFC 7084, for example, specifies that a CE router uses DHCPv6 on its WAN link regardless of whether or not it receives an RA with the M bit set.
>>
>> Hm, but it still depends on the RA for reachability information, correct?
>
> As far as I know, yes.
>
> - Ralph
>
>>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr  8 03:37:34 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C73D41A1B66 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 Dczz5K7GVsSj for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:37:28 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12D9A1A1B65 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 03:37:27 -0700 (PDT)
Received: by iget9 with SMTP id t9so26655044ige.1 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 03:37:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=8ZHO8Me456VGuaL865vl/dnW92XTNwaNHq5HBIpcHFU=; b=JD0LE3CIy/SeE+hLhiG0auRhC1n6HozSyLDUfu0j4t0mIJpw8DO5JeuD441ZytsugD wF3pRcF01ClW5eXf8OtoONjmoUAplLAIWheJvRMd95yH6vMoBrOVePy7BBwucRBdCm0E Bhjbsor6plBqltxXP02IrN8fvrK88oISNlthkRgXb5dlvyqpEOzUYyIUdv/5S6ItCL4J PDN/XAOyJ2ZSHx1gNZBnp+AOvh8wlrVEEgM7bk1OJxu9cVnmLomz6qzeLn9cE74eMj/R D8QvOgFid6LKKIWJXX7d07WfMYcnWUvL5+ohZZU/vwZUmitUbIA3FihBe4jyGSr6ZABL fw1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=8ZHO8Me456VGuaL865vl/dnW92XTNwaNHq5HBIpcHFU=; b=WaI7ztG69ZqF4Ki4C1Bx0rygEmJva17dLX/2sn4wIQdXDKX721gnTeOOBDYmZXmyG6 Pi0zrUYnhMBkT6WjAdzYGHA3go0fDkAih4XO/0AnGJbfbmTdti/gwxZWHZJI7/xYtMGd ekvfG7vCBNqWo6oBuYNdsOihE4kXNv/lZvV16a8AXuFTMSy6xcG0tpJzLuZfY8zJ+5q0 yLjt5Of0HcshnjKnFQKJ24PemHc8hrUmCeEsYHSUh0CUQRuRyfID5S0xs06XraJ9EXU1 p3VMZboG7LpvWzX6X8D+6EDjP6/hoTIjM7ujaDMXmt7V1Cl/Z33Xal+9sZ2jYPZFNAAk /eXA==
X-Gm-Message-State: ALoCoQlKmlpjhzUNO/ZR6ZPepIOhlq5X9f5hS7fQC8hVm/j+AhJqH5/Q09kzUsB0vmBKFhABnz9Q
X-Received: by 10.43.119.196 with SMTP id fv4mr5105496icc.83.1428489447488; Wed, 08 Apr 2015 03:37:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 03:37:06 -0700 (PDT)
In-Reply-To: <5525045B.5050204@gmail.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com> <5525045B.5050204@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 8 Apr 2015 19:37:06 +0900
Message-ID: <CAKD1Yr3=ZGmxPsuOVf4++tp0Rh=ZTYK6ecc5Hy_HoGnc3OqXOA@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec517cdec1566830513341e84
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ZXj-H6-eCiIfp1kHNDK6DxaYnX4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 10:37:33 -0000

--bcaec517cdec1566830513341e84
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 8, 2015 at 7:35 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> Well, the linux stack implementation does not act that way. Adding an
> address on an interface implies a routing table entry is added too.
>

Not true. It acts that way if you specify a prefix length of 128.

--bcaec517cdec1566830513341e84
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 8, 2015 at 7:35 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petre=
scu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well,=
 the linux stack implementation does not act that way. Adding an<br>
address on an interface implies a routing table entry is added too.<br></bl=
ockquote><div><br></div><div>Not true. It acts that way if you specify a pr=
efix length of 128.</div></div></div></div>

--bcaec517cdec1566830513341e84--


From nobody Wed Apr  8 03:55:36 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40F081B2F7C for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 W5qk8egoYILv for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:55:32 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 63C0F1B2F52 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 03:55:32 -0700 (PDT)
Received: from [186.134.76.56] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Yfndl-0004Tw-LY; Wed, 08 Apr 2015 12:55:26 +0200
Message-ID: <5524FF6A.3050305@si6networks.com>
Date: Wed, 08 Apr 2015 07:14:02 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>,  "Will Liu (Shucheng)" <liushucheng@huawei.com>
References: <20150408094426.29609.99720.idtracker@ietfa.amsl.com>
In-Reply-To: <20150408094426.29609.99720.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/xyS65kjx7cJ1T9Xde4zJpQ4zsVE>
Subject: Re: [dhcwg] New Version Notification for draft-ietf-dhc-stable-privacy-addresses-02.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 10:55:35 -0000

Folks,

This is the pending rev I had in my queue.

This version incorporates the aforementioned changes:

* The expression includes the IPv6 Prefix (and the address pool range).
The selected address is subsequently adjusted (if needed). This way a
change in the DHCPv6 address pool range does not affect the leased
addresses.

* We have incorporated a section entitled "Applicability and Design
Goals", in response to the recent discussion.

Any comments will be welcome.

Thanks!

Best regards,
Fernando




On 04/08/2015 06:44 AM, internet-drafts@ietf.org wrote:
> 
> A new version of I-D, draft-ietf-dhc-stable-privacy-addresses-02.txt
> has been successfully submitted by Fernando Gont and posted to the
> IETF repository.
> 
> Name:		draft-ietf-dhc-stable-privacy-addresses
> Revision:	02
> Title:		A Method for Generating Semantically Opaque Interface Identifiers with Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
> Document date:	2015-04-08
> Group:		dhc
> Pages:		10
> URL:            http://www.ietf.org/internet-drafts/draft-ietf-dhc-stable-privacy-addresses-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-dhc-stable-privacy-addresses/
> Htmlized:       http://tools.ietf.org/html/draft-ietf-dhc-stable-privacy-addresses-02
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-stable-privacy-addresses-02
> 
> Abstract:
>    This document specifies a method for selecting IPv6 Interface
>    Identifiers, to be employed by Dynamic Host Configuration Protocol
>    for IPv6 (DHCPv6) servers when leasing non-temporary IPv6 addresses
>    to DHCPv6 clients.  This method is a DHCPv6 server side algorithm,
>    that does not require any updates to the existing DHCPv6
>    specifications.  The aforementioned method results in stable
>    addresses within each subnet, even in the presence of multiple DHCPv6
>    servers or DHCPv6 server reinstallments.  It is a DHCPv6-variant of
>    the method specified in RFC 7217 for IPv6 Stateless Address
>    Autoconfiguration.
> 
>                                                                                   
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Apr  8 03:55:46 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF98C1B2F80 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 zPjbXiWa7ofh for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:55:35 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 9AC501B2F52 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 03:55:35 -0700 (PDT)
Received: from [186.134.76.56] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Yfndt-0004Tz-8n; Wed, 08 Apr 2015 12:55:33 +0200
Message-ID: <55250911.30100@si6networks.com>
Date: Wed, 08 Apr 2015 07:55:13 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/uJ73wEp_SuIiMPrOMlldFWrMMdQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 10:55:37 -0000

On 04/08/2015 07:29 AM, Lorenzo Colitti wrote:
> On Wed, Apr 8, 2015 at 3:54 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     Nowhere does it say that it is the only way
>     to do it, and nowhere does it mandate that you support stable
>     privacy-enhanced addresses in the first place (or that, if you do, you
>     do it with this algorithm).
> 
> 
> Actually it does. For example:
> 
>    DHCPv6 server implementations conforming to this specification MUST
>    generate non-temporary IPv6 addresses using the algorithm specified
>    in this section.
> 
> and:
> 
>    A DHCPv6 server implementing this specification must select the IPv6
>    addresses to be leased with the following algorithm:

Huh?

The text says "...*conforming to this specification*" and
"..*implementing* this specification". That means: "if you want to
implement this scheme, this is what you must do".

Nowhere does it say "DHCPv6 implementations must generate IPv6 addresses
as specified in this document". And the new "Applicability..." section
hopefully makes that even more explicit.

Is there anything I'm missing?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Apr  8 03:58:39 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D5CB1B2F86 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:58:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 32ap-WhqvNpE for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 03:58:37 -0700 (PDT)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E2F61B2F84 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 03:58:36 -0700 (PDT)
Received: by ignm3 with SMTP id m3so26952431ign.0 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 03:58:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=cIeXJ6TLaJp2sS4DcpOV3YZlh+dTWU8cnx3uhFwWEuo=; b=P8XGYhjofG+q354TKFyEROf47t05Dny/Aej6W3zt7uED7DH7BBK3UmvxBmAUpT5hGL 96u4Mzr3hms0fMLZy+J9evcgWYl0egVh/WLP4AbMsgdQjMQv7kzc7g6+HEmDpQ3qTgHu bZAafDjbuAnNCtDKuId6Eg1d3qdJ0SMg2aaQRlCTmDQHjJYF/Z3CXqbdzIH61dq5iUX5 00SoFQejD2gxr2fOhGlLw6cEchSiocNdYzc9OXUY+E3Dv35j9EgmuQMFuHe9gP7ELYlv EKLDClby1O2WC957ebp7IH8Zus3TmC8nSsHONzX4YWVbSeh69RnXdLU2vbrumLZMu1iW StFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=cIeXJ6TLaJp2sS4DcpOV3YZlh+dTWU8cnx3uhFwWEuo=; b=kbx0STF1phFAHEa7Lpn972JIMCRVSBsi2qRd4bDkZHw2KNQhIviXxIsZwMRhHPPJvu fPl/OFzQujIAtvQF0iyC7kMMPMkHucxwKxbC0TAzxzar/62sTqE5jRGjEP8pMzQ4uidS ilmaCK7xQRjZF7RRpP4nRHBYNe0vGn8Vs22tugkLcTuYwIPvzstLDHmsMFOwHIFoVMdy maj3m4KxAx2CSlXrDRvYrnadZqCS7jleDb6bLtCzdwh1lAgSo3T+GnAQ6CXMI160wZ59 a077sgSrxcVcuACSs2NdpAIfXxY2WIU52Q92JQ4RIZR6mBipZh0/Pf7lUeID51pIqst1 7qVg==
X-Gm-Message-State: ALoCoQlUioz3rWTQUN+G4S2v10p5rzoV6dj5lz08TORoTgYOZfo0JmByk65UPgiY21TRb0AScaqH
X-Received: by 10.50.79.197 with SMTP id l5mr10929604igx.39.1428490716290; Wed, 08 Apr 2015 03:58:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 03:58:15 -0700 (PDT)
In-Reply-To: <55250911.30100@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 8 Apr 2015 19:58:15 +0900
Message-ID: <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=089e013cc168b5c7fe0513346921
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Myg1MEo3ukA62ylrQ5symUikCTM>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 10:58:38 -0000

--089e013cc168b5c7fe0513346921
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 8, 2015 at 7:55 PM, Fernando Gont <fgont@si6networks.com> wrote:

> > Actually it does. For example:
> >
> >    DHCPv6 server implementations conforming to this specification MUST
> >    generate non-temporary IPv6 addresses using the algorithm specified
> >    in this section.
> >
> > and:
> >
> >    A DHCPv6 server implementing this specification must select the IPv6
> >    addresses to be leased with the following algorithm:
>
> Huh?
>
> The text says "...*conforming to this specification*" and
> "..*implementing* this specification". That means: "if you want to
> implement this scheme, this is what you must do".
>
> Nowhere does it say "DHCPv6 implementations must generate IPv6 addresses
> as specified in this document". And the new "Applicability..." section
> hopefully makes that even more explicit.
>
> Is there anything I'm missing?


Yes. You're missing that a DHCP server that implements your specification
must be able to choose a different method to "generate non-temporary IPv6
addresses".

Your document doesn't allow that, because the text says "DHCPv6 server
implementations conforming to this specification MUST generate
non-temporary IPv6 addresses using the algorithm specified in this section."

--089e013cc168b5c7fe0513346921
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 8, 2015 at 7:55 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D"=
mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);borde=
r-left-style:solid;padding-left:1ex"><div><div class=3D"h5">&gt; Actually i=
t does. For example:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 DHCPv6 server implementations conforming to this specific=
ation MUST<br>
&gt;=C2=A0 =C2=A0 generate non-temporary IPv6 addresses using the algorithm=
 specified<br>
&gt;=C2=A0 =C2=A0 in this section.<br>
&gt;<br>
&gt; and:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 A DHCPv6 server implementing this specification must sele=
ct the IPv6<br>
&gt;=C2=A0 =C2=A0 addresses to be leased with the following algorithm:<br>
<br>
</div></div>Huh?<br>
<br>
The text says &quot;...*conforming to this specification*&quot; and<br>
&quot;..*implementing* this specification&quot;. That means: &quot;if you w=
ant to<br>
implement this scheme, this is what you must do&quot;.<br>
<br>
Nowhere does it say &quot;DHCPv6 implementations must generate IPv6 address=
es<br>
as specified in this document&quot;. And the new &quot;Applicability...&quo=
t; section<br>
hopefully makes that even more explicit.<br>
<br>
Is there anything I&#39;m missing?</blockquote><div><br></div><div>Yes. You=
&#39;re missing that a DHCP server that implements your specification must =
be able to choose a different method to &quot;generate non-temporary IPv6 a=
ddresses&quot;.<br><br></div><div>Your document doesn&#39;t allow that, bec=
ause the text says &quot;DHCPv6 server implementations conforming to this s=
pecification MUST generate non-temporary IPv6 addresses using the algorithm=
 specified in this section.&quot;</div></div></div></div>

--089e013cc168b5c7fe0513346921--


From nobody Wed Apr  8 04:04:11 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AACB81B2F8F for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 uT_0Ijhf0U8o for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:04:05 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 554A41B2F8E for <dhcwg@ietf.org>; Wed,  8 Apr 2015 04:04:05 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t38B43Ud006675 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 13:04:03 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 331C62069A7 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 13:05:07 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 2B038206981 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 13:05:07 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t38B3XjS030540 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 13:04:03 +0200
Message-ID: <55250B05.8040600@gmail.com>
Date: Wed, 08 Apr 2015 13:03:33 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk>
In-Reply-To: <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SesDjJB-y4dDNeKLyQvXYSbEmkg>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 11:04:09 -0000

Le 02/04/2015 23:40, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>> Assuming the router knows about the other devices, when we open
>>> a connection by sending packets to the router, the router can
>>> tell us (via a redirect) about the other node being on-link. At
>>> this point, we then know to use ND to find the other node and it
>>>  becomes on-link to us for as long as the neighbour information
>>> is kept active. This doesn't need *ANY* prefix information at all
>>> - only knowledge of a router we can use to send our packets out.
>>
>> Well, yes and no.
>>
>> Yes in that it can work as you describe.  And that prefix lengths
>> must be there during that operation.
>
> Why ?

I meant a prefix length, not just a prefix.

This is what you seemed to say as well: use prefix length value 128.

> What is a prefix doing for us in this scenario ? We can work with
> absolutely no prefix list whatsoever as long as the router redirects
> tell us about neighbours that are directly reachable.

I agree.

>> If they are not there it does not work.
>
> Yes it will. We don't need a prefix to talk to the router, and we
> don't need one to talk about a neighbour we've already found.

But we need the prefix length value to be there, and valued at 128.

>> No in that Redirect does not tell whether somebody is onlink or
>> not, it just redirects to a better first-hop router, which will
>> presumably be that other neighbor-on-link (but not
>> neighbor-on-same-subnet): RFC says:
>>>
>>> 4.5. Redirect Message Format
>>>
>>>
>>> Routers send Redirect packets to inform a host of a better
>>> first-hop node on the path to a destination.  Hosts can be
>>> redirected to a better first-hop router but can also be informed
>>>  by a redirect that the destination is in fact a neighbor.
>>
>> "in fact a neighbor"?  It is a neighbor on the same link, but it is
>> not a neighbour in the same subnet, because there is no subnet. Is
>> a neighbor "on-link"?  We dont know.
>
> Yes we do. See RFC4861 again.
>
> on-link     - an address that is assigned to an interface on a
> specified link.  A node considers an address to be on- link if:
>
> ...
>
> - a neighboring router specifies the address as the target of a
> Redirect message, or
>
> And see Sec 4.5 that you quoted - the router can tell us that a host
>  is local to us - it on-link.

We have no definition that tells that a 'neighbor' is 'on-link' and
moreover, 'on the same link'.

We know intuitively from IPv4, that a neighbor is in the same subnet as
self, i.e in the same prefix/prefixlen.

We know several subnets (prefixes) can be on the same link.

So, two neighbors on the same link are also neighbors on the same subnet?

>> In fact, this entire terminology of "on-link determination" is not
>> described anywhere.
>
> RFC4861

There is no section in that RFC4861 that tells how to implement "on-link
determination".  You have some bits here and there, but it is not enough
and at times unclear.

(compare, for example, with DAD which is fully specified in its own
unique place in rfc4862 section 5.4 titled "DAD").

>> You have some bits here and there about who contributes to it, but
>>  there is no section telling that is the on-link determination
>> operation.  With hands empty you  can only  suppose what it is, and
>> implement in a certain manner (longest match dst to rt table
>> entries, if found then ND dst and send packet to that MAC otherwise
>> ND the default router's IP address and send packet to that other
>> MAC address).  That's how I believe it should be but no document
>> tells how it should be.
>
> So you want the standard to say how it should be done, not just what
>  should be done ?

Yes, like DAD.

> There's no "longest match" requirement - if the address is within
> any prefix marked as local then the address is considered on-link.

What does it mean to be within?

> You can do the "run down the list thing" and just stop at the first
> match - no need to find multiple matches, do longest match, etc.

What is a match?

>> When I type "route -6" there are some routes but there is not one
>> that says "this is on-link, this is not on-link".
>
> That's showing the result of a specific implementation which may or
> may not reflect the internal tables directly - and for which I
> believe we have already identified does not "do things correctly".

Ah?  I didnt know that?  Deprecating the 'route' command now after all
these years?  Serious?

> On my systems, I see entries for "my own address" /128, and for the
> subnet prefix /64 which since I stopped radvd will have come from
> adding the interface IPv6 address.

Yes.

>>>>> on-link     - an address that is assigned to an interface on
>>>>>  a specified link.  A node considers an address to be on-
>>>>> link if:
>>>>>
>>>>> - it is covered by one of the link's prefixes (e.g., as
>>>>> indicated by the on-link flag in the Prefix Information
>>>>> option), or
>>>>>
>>>>> - a neighboring router specifies the address as the target of
>>>>> a Redirect message, or
>>>>>
>>>>> - a Neighbor Advertisement message is received for the
>>>>> (target) address, or
>>>>>
>>>>> - any Neighbor Discovery message is received from the
>>>>> address.
> ...
>> What is precisely the "on-link determination"? (some RFC section
>> titled so that I missed?)
>
> The section already quoted ?

Sorry, I dont see.  There are several paragraphs in RFC4861 which talk
'on-link determination', but are not grouped together.

[...]
>> In my setting I avoid saying something is "on-link" or "off-link",
>> because I know people have different understandings for each.
>
> But surely the correct thing to do is to use the same terminology as
>  specified in the RFC ? The RFC where both terms are defined.

They are wrong.  They don't say 'subnet'.  And 'subnet' is what people use.

>>>> For example, the RFC says:
>>>>> A router acting on behalf of a mobile node that has moved
>>>>> off-link could potentially act as a proxy for the mobile
>>>>> node.
>>>>
>>>> The term "off-link" is used, but the "specified link" (per
>>>> definition) is not present.  Moreover, the definition tells
>>>> "off-link" is an "address", whereas in this use this "off-link"
>>>> is simply a qualifier of the mouvement.
>>>>
>>>> We can understand the phrase, the node moved out of the link,
>>>> off of the link; but the term "off-link" is not well defined.
>>>
>>> Again, I think context is everything. For something that's
>>> "moved off-link", we can infer that it's no longer on the link it
>>> used to be on. If it were to appear "on-link" for some other link
>>> then that complicates matters, but I don't think that in context
>>> it is wrong.
>>
>> It is not wrong, it is just misleading and not self-containing; it
>>  is not implementable in an interoperable manner.
>
> I disagree. It's merely stating that a router could proxy for a
> mobile device that's left the network. Operation of mobility is
> defined elsewhere - and it does not in any way affect the topic of
> this thread.

This is little right as well.

The mobility operation (Mobile IPv6) has it that the proxying operation
is done by somebody else than the Router.  And that RFC defining
mobility never says 'off-link'.

(besides, as simply as 'proxying' may seem, there are at least two:
- 'proxy ND RFC4389' means to pass through an untouched and an
   otherwise link-scoped message like an NS.
- 'proxy ND RFC6275' means to set somebody else's IP address in an NA
   containing the MAC address of self.)

> As far as our node is concerned, if a router is proxying for a mobile
> device, then we treat it the same was as we'd treat the device it's
> proxying for. The same questions apply to determine if it's on-link -
> so I think it's a non-problem. There simply is nothing whatsoever to
> implement (on a general node that isn't taking part in mobility) to
> cater for this.

The problem is in the use of the term 'off-link'.

You seem to assume that 'off-link' only qualifies a movement.

But other people believe 'off-link' means something else.  I.e. one
could have an RA containing a prefix that is 'off-link'.  That has
nothing to do with movement, because when the node moved the prefix is
still on-link.

>>>> Furthe, RFC says:
>>>>> L              1-bit on-link flag.  When set, indicates that
>>>>> this prefix can be used for on-link determination.  When not
>>>>> set the advertisement makes no statement about on-link or
>>>>> off-link properties of the prefix.  In other words, if the L
>>>>> flag is not set a host MUST NOT conclude that an address
>>>>> derived from the prefix is off-link.  That is, it MUST NOT
>>>>> update a previous indication that the address is on-link.
>>>>
>>>> This definition means that it means nothing.  It gives no
>>>> indication. It's just like the M flag.
>>>>
>>>> If L then something, otherwise nothing.  This is not what me
>>>> as implementer would like to see.
>>>
>>> I can only see one issue - and without having digested the RFC I
>>> don't know if it's addressed. If an RA sets the L bit, and then
>>> unsets it later, the above says that we carry on treating the
>>> prefix as local. How often is this likely to happen in practice ?
>>> I'm not sure I can envisage a network where it supports ND, but
>>> then changes (without any host links going down) into one where
>>> ND no longer works.
>>>
>>> What comes to mind is if an RA from one router sets it, another
>>> router sends RA with it unset, and then the first router goes/has
>>> the prefix removed/whatever. Does a node keep track of which RAs
>>> it got from each router, does it then say that the prefix is now
>>> not local because the RA that set it as local has stopped and
>>> there's no other RA that has it set ? Conversely, if the above
>>> said that getting an RA with the L bit clear means you have to
>>> update the prefix information, the next question would be "what
>>> about multiple RAs for the same prefix with different states for
>>> the L bit ?"
>
>> I meant to say that when L is unset we dont know what to do (we
>> dont know whether that is onlink or offlink).  As such it's sent
>> for no reason and should be ignored.
>
> Look at it this way. If the flag is set then you do something. If
> it's not

If the flag is not set you dont know whether you have to do something or
not.

What should the stack do with the 'off-link' prefix received in an RA?
If it has a particular meaning ('off-link') then the stack should
off-link-something.  Otherwise it doesnt mean anything.

> set then you just leave existing settings alone. I'm afraid I can't
> see what the problem is with that.

The problem is that a bit is defined that is not used and always
transported.

>>> The mechanism for it getting unset is for the prefix to get
>>> removed from the table = which will happen if the link "goes
>>> down", or if we stop getting any RAs with the prefix. As above, I
>>> can't think of any situation (other than admin cock-up !) where
>>> there would be any need to unset the local flag in the prefix
>>> table.
>>
>> There is no reason for that.  Entries will expire by themselves
>> anyways, no need to announce going down.  Expiration can be planned
>> be quicker by using shorter lifetimes, too.
>
> Unless the RAs are still advertising the prefix - in that case an
> entry won't expire, so there is no mechanism for unsetting the local
>  flag in the node's prefix table.

If you want to make a prefix disappear set the respective router's
lifetime to a smaller value and after that time stop advertising it.  IT
will disappear from everyone else's caches.

Advertising it 'off-link' is not the right way to achieve disappearance.

> But as I said, other than an admin having accidentally set it when it
> shouldn't be, I can't see a situation where a prefix could
> legitimately change from local to not local without some event (such
>  as interface going down momentarily)

I agree.

> happening that causes the prefix table for that link to be flushed.
> In the same way, i can't really see it changing the other way either
> - other than by having two routers and one of them is incorrectly
> configured.
>
> So in reality, the process is going to be as simple as get an RA, add
> the prefix(es) or refresh the timer if it already exists. And if the
> L flag is set, then make sure it's set in our table. Unless someone
> comes up with something else, I believe that really is it.

Sure, we can see.

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr  8 04:13:05 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0CA1B2FB9 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 XHUcdacJ2TJm for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:13:02 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC77A1B2FB5 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 04:13:01 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t38BCxD0012537 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 13:12:59 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5C5EE2065ED for <dhcwg@ietf.org>; Wed,  8 Apr 2015 13:14:03 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 54D2320692F for <dhcwg@ietf.org>; Wed,  8 Apr 2015 13:14:03 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t38BCd1N003482 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 13:12:59 +0200
Message-ID: <55250D27.6060902@gmail.com>
Date: Wed, 08 Apr 2015 13:12:39 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <201504051929.t35JTBHv015532@givry.fdupont.fr>
In-Reply-To: <201504051929.t35JTBHv015532@givry.fdupont.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/3tAxKIJu9rLkNrSyEjGTb3qi9Yw>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 11:13:04 -0000

Le 05/04/2015 21:29, Francis Dupont a écrit :
> In your previous mail you wrote:
>
>> Addresses received via DHCPv6 do not have any associated
>> reachability information. In order avoid the problems described in
>> [RFC4943], hosts MUST NOT assume that any IPv6 destinations are
>> reachable on-link as a result of receiving an IA_NA or IA_TA. In
>> order to communicate to any destination that is not a link-local
>> address, the host must also have obtained reachability information
>> by other means such as a Router Advertisement or manual
>> configuration.
>
> => far better than previous second MUST NOT proposal... If you still
> want a /128 in the text it should be enough to add a "without
> reachability information" condition.
>
> Regards
>
> Francis.Dupont@fdupont.fr
>
> PS: the reference for "reachability information" is RFC 4861. It is
> where one can get definitions for a prefix, on/off-link, reachability
> itself, etc. And BTW the answer to the address which belongs to 2
> prefixes problem (longest prefix match, section 2.1).

That section says:
> longest prefix match - the process of determining which prefix (if
> any) in a set of prefixes covers a target address.  A target address
> is covered by a prefix if all of the bits in the prefix match the
> left-most bits of the target address.  When multiple prefixes cover
> an address, the longest prefix is the one that matches.

Except that it does not say what happens when multiple prefixes have the
same length (the common '64'); it does not say how to do when prefix
lengths are absent; it does not say how to use ancillary parameters such
next-hop gw or iface.

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr  8 04:16:27 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57B791B2FC8 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 Q9SeQDEN69Ti for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:16:24 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 451A81B2FC6 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 04:16:24 -0700 (PDT)
Received: from [186.134.76.56] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Yfny1-0004Xm-Lp; Wed, 08 Apr 2015 13:16:22 +0200
Message-ID: <55250DF2.8050001@si6networks.com>
Date: Wed, 08 Apr 2015 08:16:02 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com>
In-Reply-To: <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/GPZVABirI0NagBAM4YODEXD_Yd4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 11:16:26 -0000

On 04/08/2015 07:58 AM, Lorenzo Colitti wrote:
>     Huh?
> 
>     The text says "...*conforming to this specification*" and
>     "..*implementing* this specification". That means: "if you want to
>     implement this scheme, this is what you must do".
> 
>     Nowhere does it say "DHCPv6 implementations must generate IPv6 addresses
>     as specified in this document". And the new "Applicability..." section
>     hopefully makes that even more explicit.
> 
>     Is there anything I'm missing?
> 
> 
> Yes. You're missing that a DHCP server that implements your
> specification must be able to choose a different method to "generate
> non-temporary IPv6 addresses".
> 
> Your document doesn't allow that, because the text says "DHCPv6 server
> implementations conforming to this specification MUST generate
> non-temporary IPv6 addresses using the algorithm specified in this section."

This is certainly a wording issue, that I guess is fixed by, e.g.,
s/conforming/employing/?

(For instance, there's text that suggests that if you implement this
method, you provide a knob such that you can control whether to use this
method or not:

"   Implementations conforming to this specification SHOULD provide the
   means for a system administrator to enable or disable the use of this
   algorithm for generating IPv6 addresses."

)

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Apr  8 04:36:06 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15EFB1B3027 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:36:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 a6-NVZyCxYkT for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:36:03 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFF611B3025 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 04:36:03 -0700 (PDT)
Received: by iebrs15 with SMTP id rs15so71179100ieb.3 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 04:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bu38Pe/hTjqY++459EVqjUhzKtyOXeDmmEdNhoAqBr4=; b=QNnmXUrVNTKScVrYx+akRXPAlOattmqCHevlTq+WwxozxeFZWWsUCYVJ/KQ1qkz3wQ 3JEtMuGVBDeNcIBHeG8Pfa7YzwomVJcDCG8fkqyQdZBZZrHTD1AeZ5vbnU4ilJz+21Ky AXaAv2TEoZ8Rj9Cmvz627H5IaN71IZDfBcxelXb/jB7fsMX6nbtikXtpvsmrtd4Yjn/U 2bvpYRM0ftLUk93PIoqnbXdB3aBhuxzhgRYGz1vk/cGvUcBKX6Ii2l/TFem00Bt7tZNY Vp/xu4abXzSyityCnX34Uicbhnw8cVMVysgYS1FDa1BqUH3hxVfH6P62JPwjlzpioAQL tXSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=bu38Pe/hTjqY++459EVqjUhzKtyOXeDmmEdNhoAqBr4=; b=Tyf/cBd1Uh2oAZxSFg9Ve2UM6ABNYLKaXxcXT6vhGI20EmCS+MfwLS0vQvthTsbMC0 mWvh6Q9sSHadOeVMw5qsPro0Y4/kTSgIfdcHFQaf4Z2OhGFwFTtoq9xUWGrg+XbuG9xT wd7dNI3lMfjI9NaISqT/zZqhVRmYMSuzAeL7YSo54wBiqd1xDJ5qBoJM+TkX71sme+JX u35AyIF4PIeX7f+99fauq18Z0JzzEM0ZlLfdSdTi+g9QVmSal/TiwlYZcapjUM4kA/4g EwKowfxWis6RTsD4w6Y4Y4FtWCG6797sCT4TRoZ+jHGFMu52Rz1sqbCGD4SI22lSn809 Iw5Q==
X-Gm-Message-State: ALoCoQlY28+fGe8WHgzp1ChEhRUAY+EhpBTD/9TUlbE2B6xHcsTflBwF01WHtuIwD9K2QNsGEXy/
X-Received: by 10.43.119.196 with SMTP id fv4mr5383997icc.83.1428492963237; Wed, 08 Apr 2015 04:36:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 04:35:42 -0700 (PDT)
In-Reply-To: <55250DF2.8050001@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 8 Apr 2015 20:35:42 +0900
Message-ID: <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=bcaec517cdeca384f4051334ef99
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/yNfQvlTV9OmUVodqoaTvMJIVp_Y>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 11:36:05 -0000

--bcaec517cdeca384f4051334ef99
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 8, 2015 at 8:16 PM, Fernando Gont <fgont@si6networks.com> wrote:

> "   Implementations conforming to this specification SHOULD provide the
>    means for a system administrator to enable or disable the use of this
>    algorithm for generating IPv6 addresses."


That just changes the question to "what happens if the server uses both
this type of address and other types of address".

More in general: if you're serious about this document being "just one
possible way of generating IPv6 IIDs", then you'll need to make it clear
what is required for it to coexist with other ways of generating IPv6 IIDs.
If not, then you'll need to make it clear that it cannot coexist with other
ways of generating addresses.

Another issue I see is that the document says that the addresses are stable
and stateless, but they're not, because the value of counter for every
lease needs to be shared between the servers. For example, if the client
sends a DECLINE because it fails DAD, what do you do? The address is no
longer stable.

Another issue: if the addresses are stable and stateless, then that means
you can replace a server and have the client keep the same address. What
modifications are needed on the server side for that to work? If the client
sends a renew unicast to the new server, will this just work?

Again, I think this is best left unspecified and I don't see the value in
publishing this document. But I think that if you want to publish it,
you'll need to provide serious answers to the questions above.

--bcaec517cdeca384f4051334ef99
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 8, 2015 at 8:16 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D"=
mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">&quot;=C2=A0 =C2=A0Imple=
mentations conforming to this specification SHOULD provide the<br>
=C2=A0 =C2=A0means for a system administrator to enable or disable the use =
of this<br>
=C2=A0 =C2=A0algorithm for generating IPv6 addresses.&quot;</blockquote><di=
v><br></div><div>That just changes the question to &quot;what happens if th=
e server uses both this type of address and other types of address&quot;.</=
div><div><br></div><div>More in general: if you&#39;re serious about this d=
ocument being &quot;just one possible way of generating IPv6 IIDs&quot;, th=
en you&#39;ll need to make it clear what is required for it to coexist with=
 other ways of generating IPv6 IIDs. If not, then you&#39;ll need to make i=
t clear that it cannot coexist with other ways of generating addresses.</di=
v><div><br></div><div>Another issue I see is that the document says that th=
e addresses are stable and stateless, but they&#39;re not, because the valu=
e of counter for every lease needs to be shared between the servers. For ex=
ample, if the client sends a DECLINE because it fails DAD, what do you do? =
The address is no longer stable.</div><div><br></div><div>Another issue: if=
 the addresses are stable and stateless, then that means you can replace a =
server and have the client keep the same address. What modifications are ne=
eded on the server side for that to work? If the client sends a renew unica=
st to the new server, will this just work?</div><div><br></div><div>Again, =
I think this is best left unspecified and I don&#39;t see the value in publ=
ishing this document. But I think that if you want to publish it, you&#39;l=
l need to provide serious answers to the questions above.</div></div></div>=
</div>

--bcaec517cdeca384f4051334ef99--


From nobody Wed Apr  8 04:38:44 2015
Return-Path: <rdroms@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3371B3029 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 tx9v-Hguk2jw for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:38:41 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 575561B302C for <dhcwg@ietf.org>; Wed,  8 Apr 2015 04:38:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5046; q=dns/txt; s=iport; t=1428493121; x=1429702721; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=c45sVTtGVSevDQAk/SMUwUht3lXCulFJnCFh5NyzhU0=; b=KJ/3jQLyD7PAAmcwfzuNVx9Ma+IoRZ/BLvZgheEQ0Cvezl8mWF4ke38b DskoGvYje1HMq/tTFZZOd/Au+PS/n/S9J0/SoaxgLtMV2js3yVsDmMqFG aFJEeuGLCjfw0uQrYn4U6nEgNAl++xWCY7d6Dv+RU1fPbSk1cXLzkyfpJ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BQBAADEiVV/4UNJK1cgwiBLgWDEMBZCYdPAhyBETgUAQEBAQEBAX2EHwEBAQMBIxFFBQsCAQYCGAICJgICAh8RFRACBA4FiBYDCQiXfJx/kR4NhTYBAQEBAQEBAQEBAQEBAQEBAQEBAQEXgSGKCoJIgWkYGBsHgmgvgRYBBJB0hEuDb4FNgR2NC4YzIoNvb4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,544,1422921600"; d="scan'208";a="139299009"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-7.cisco.com with ESMTP; 08 Apr 2015 11:38:40 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t38BceYt006168 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Apr 2015 11:38:40 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.86]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Wed, 8 Apr 2015 06:38:40 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQaKj80muBJGbcNkGotfXc7mP6I504wzCAgADoYICAALZEAIAAArSAgAADRYCACOjYAIAAEvsA
Date: Wed, 8 Apr 2015 11:38:39 +0000
Message-ID: <0FE0303A-7138-47CF-999F-0D0729C3621F@cisco.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <551CEC1F.3070006@gmail.com> <CAJE_bqfAmTFJwVL3VTK+w6rSu_TPPPrmWet2nmi-YfcKyts3PA@mail.gmail.com> <551D8749.6090907@gmail.com> <F30838AF-E1A1-40D1-BC7E-B5993E388344@cisco.com> <55250356.9030303@gmail.com>
In-Reply-To: <55250356.9030303@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.253.207]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A882D8BC03F1304091A753C43FC28439@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/a3WEtGNzi7wJnr3cmXaW0B-5zwA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 11:38:43 -0000

DQo+IE9uIEFwciA4LCAyMDE1LCBhdCA2OjMwIEFNIDQvOC8xNSwgQWxleGFuZHJ1IFBldHJlc2N1
IDxhbGV4YW5kcnUucGV0cmVzY3VAZ21haWwuY29tPiB3cm90ZToNCj4gDQo+IExlIDAyLzA0LzIw
MTUgMjA6MjcsIFJhbHBoIERyb21zIChyZHJvbXMpIGEgw6ljcml0IDoNCj4+IA0KPj4+IE9uIEFw
ciAyLCAyMDE1LCBhdCAyOjE1IFBNIDQvMi8xNSwgQWxleGFuZHJ1IFBldHJlc2N1DQo+Pj4gPGFs
ZXhhbmRydS5wZXRyZXNjdUBnbWFpbC5jb20+IHdyb3RlOg0KPj4+IA0KPj4+IExlIDAyLzA0LzIw
MTUgMjA6MDUsIOelnuaYjumBlOWTiSBhIMOpY3JpdCA6DQo+Pj4+IEF0IFRodSwgMDIgQXByIDIw
MTUgMDk6MTM6MzUgKzAyMDAsIEFsZXhhbmRydSBQZXRyZXNjdQ0KPj4+PiA8YWxleGFuZHJ1LnBl
dHJlc2N1QGdtYWlsLmNvbT4gd3JvdGU6DQo+Pj4+IA0KPj4+Pj4+IEkgYWdyZWUgd2l0aCB0aGlz
IHN0YXRlbWVudCBwZXIgc2UsIGJ1dCBJIHRoaW5rIHRoaXMgaXMgbm90DQo+Pj4+Pj4gc3VmZmlj
aWVudCwgc2luY2UgaXQgZG9lc24ndCAoY2xlYXJseSkgYW5zd2VyIHRoZSBxdWVzdGlvbiBvZg0K
Pj4+Pj4+IHdoYXQgdGhlIG9wZXJhdG9yIHNob3VsZCBkbyBpZiB0aGV5IHdhbnQgdG8gdXNlIERI
Q1B2Ni1iYXNlZA0KPj4+Pj4+IGFkZHJlc3MgYXNzaWdubWVudCBpbiBhbiBpc29sYXRlZCBzaW5n
bGUtbGluayAob3IgInN1Ym5ldCIpDQo+Pj4+Pj4gbmV0d29yay4gIFRoZSAiYXJjaGl0ZWN0dXJh
bGx5IGNvcnJlY3QiIGFuc3dlciB3aWxsIGJlIHRoYXQNCj4+Pj4+PiB0aGV5IHNob3VsZCBkZXBs
b3kgYSBub2RlICh3aGljaCB3b3VsZCBwcm9iYWJseSBiZSBjb2xsb2NhdGVkDQo+Pj4+Pj4gb24g
dGhlIHNhbWUgbm9kZSBhcyB0aGUgREhDUHY2IHNlcnZlcikgdGhhdCBzZW5kcyBSQXMgd2l0aA0K
Pj4+Pj4+IHJvdXRlciBsaWZldGltZSBiZWluZyAwIGFuZCB3aXRoIGFwcHJvcHJpYXRlIG9uLWxp
bmsNCj4+Pj4+PiBwcmVmaXgoZXMpLg0KPj4+PiBbLi4uXQ0KPj4+Pj4gQnV0LCBhIFJvdXRlci1E
SENQdjZTZXJ2ZXIgd2l0aCByb3V0ZXIgbGlmZXRpbWUgMCBhbmQgb24tbGluaw0KPj4+Pj4gcHJl
Zml4IHdpbGwgbWFrZSB0aGluayB0aGUgSG9zdCB0aGlzIGlzIG5vdCBhIGRlZmF1bHQgcm91dGVy
DQo+Pj4+PiBhbmQgaXQgc2hvdWxkIFNMQUFDIGl0cyBhZGRyZXNzIChtYXliZSBpbiBhZGRpdGlv
biB0bw0KPj4+Pj4gcmVxdWVzdGluZyBvbmUgZnJvbSBESENQdjYpLiBJcyB0aGlzIHdoYXQgaXMg
bWVhbnQgYnkgdGhlDQo+Pj4+PiBhYm92ZT8NCj4+Pj4gDQo+Pj4+IE5vdCBhdCBhbGwuICBJIGRp
ZG4ndCBtZWFuIHRvIHNheSBhbnl0aGluZyBhYm91dCBTTEFBQyBpbiB0aGUNCj4+Pj4gYWJvdmUg
ImFyY2hpdGVjdHVyYWxseSBjb3JyZWN0IGFuc3dlciIuDQo+Pj4gDQo+Pj4gSSBtaXNyZWFkIHRo
ZW4sIHNvcnJ5Lg0KPj4+IA0KPj4+Pj4gQW5vdGhlciBzdWdnZXN0aW9uIG9uIGFub3RoZXIgaGFu
ZCBpcyB0byBoYXZlIERIQ1B2NiBkZWxpdmVyIGENCj4+Pj4+IHByZWZpeCBsZW5ndGggdG9nZXRo
ZXIgd2l0aCB0aGUgYWRkcmVzcywgYW5kIGEgZGVmYXVsdCByb3V0ZS4NCj4+Pj4+IFRoYXQnZCBi
ZSBhIGZvcm0gb2YgaW5kZXBlbmRlbmNlLCBhbmQgYXZvaWQgJy82NCcNCj4+Pj4+IENJRFItYnJl
YWtpbmcgYXNzdW1wdGlvbnMuDQo+Pj4+IA0KPj4+PiBUaGF0IHdvdWxkIGxlYWQgdG8gYSBsb25n
IHN0YW5kaW5nIGRlYmF0ZSBvZiB3aGV0aGVyIERIQ1B2Ng0KPj4+PiBzaG91bGQgcHJvcGFnYXRl
IG9uLWxpbmsgcHJlZml4IGFuZC9vciBkZWZhdWx0IHJvdXRlDQo+Pj4+IGluZm9ybWF0aW9uLCBh
bmQgSSB0cmllZCB0byBhdm9pZCB0aGF0IHBhcnQgb2YgZGlzY3Vzc2lvbiBhcyBJDQo+Pj4+IGtu
ZXcgaXQgd291bGQgbmV2ZXIgY29udmVyZ2U6LSkNCj4+PiANCj4+PiBPay4NCj4+PiANCj4+Pj4g
SW4gYW55IGNhc2UgaWYgd2UgcmVhbGx5IHdhbnQgdG8gZGlzY3VzcyBpdCBhZ2FpbiwgaXQgd291
bGQgYmUNCj4+Pj4gYmV0dGVyIHRvIGRvIGl0IG91dHNpZGUgdGhlIHNjb3BlIG9mIDMzMTViaXMu
DQo+Pj4gDQo+Pj4gSSBhbSBub3QgcmVhbGx5IHNheWluZyB3ZSdkIG5lZWQgdG8gZGlzY3VzcyBp
dCwgdW5sZXNzIHdlIHJlYWxseQ0KPj4+IHdhbnQgaXQgYW5kIGl0J3Mgc2ltcGxlIHRvIGFjaGll
dmUuDQo+Pj4gDQo+Pj4gSXQgd291bGQgYmUgdmVyeSBzaW1wbGUgdG8gYWNoaWV2ZSBoYXZpbmcg
cHJlZml4bGVuIGluIERIQ1B2Ng0KPj4+IGFkZHJlc3MgYWxsb2NhdGlvbnMsIGJlIGl0IGp1c3Qg
YW4gb3B0aW9uLg0KPj4gDQo+PiBOby4gIFRoZXJlIGlzIG5vIHN1Y2ggdGhpbmcgYXMgYSBwcmVm
aXggbGVuZ3RoIG9uIGFuIGFkZHJlc3MuDQo+PiANCj4+IElmIERIQ1B2NiB3ZXJlIHRvIGNhcnJ5
IHJlYWNoYWJpbGl0eSBpbmZvcm1hdGlvbiAtIGFuZCB0aGF0IGlzIGFuDQo+PiB1bmxpa2VseSBo
eXBvdGhldGljYWwgdGhhdCBJICpyZWFsbHkqIGRvbid0IGNhcmUgdG8gZGlzY3VzcyBoZXJlIC0N
Cj4+IGl0IG11c3QgYmUgaW4gdGhlIGZvcm0gb2YgYSBsaXN0IG9mIG9uLWxpbmsgcHJlZml4ZXMs
IGVudGlyZWx5DQo+PiBkaXNqb2ludCBmcm9tIGFueSBhc3NpZ25lZCBhZGRyZXNzZXMuDQo+IA0K
PiBUaGF0IGlzIGEgZmxleGlibGUgd2F5LiAgV2UgY2FuIGltYWdpbmUgdGhhdCBTZXJ2ZXIgY291
bGQgdGVsbCBjbGllbnQgMQ0KPiBvciBtb3JlIHByZWZpeGVzIHRvIGJlICdvbi1saW5rJywgYWxt
b3N0IGluIHRoZSBzYW1lICB3YXkgYXMgdGhlIFJBDQo+IHRlbGxzIGl0IHNvLg0KDQpJdCBpcyB0
aGUgY29ycmVjdCB3YXkgdG8gaW5mb3JtIGFuIElQdjYgc3RhY2sgb2Ygb24tbGluayBwcmVmaXhl
cyBhbmQgYXNzaWduZWQgYWRkcmVzc2VzLCBleGFjdGx5IGFzIGFuIFJBIGluZm9ybXMgYW4gSVB2
NiBzdGFjayBvZiBvbi1saW5rIHByZWZpeGVzLg0KDQo+IE9uIGFub3RoZXIgaGFuZCwgdGhpcyB3
aWxsIGNvbnRpbnVlIHRoZSBkaWZmaWN1bHR5IGZvciB0aGUgQ2xpZW50IHRvDQo+IGRlY2lkZSB3
aGljaCBhZGRyZXNzIGJlbG9uZ3MgdG8gd2hpY2ggcHJlZml4LiAgVGhpcyBpcyBhIGNvbXBsZXgg
b3BlcmF0aW9uLg0KDQpJdCBpcyBhIHJlcXVpcmVkIG9wZXJhdGlvbi4gIFRoZSBkZXNpZ24gb2Yg
SVB2NiBpcyB0aGF0IHRoZSBzdGFjayBtYXRjaGVzIGEgZGVzdGluYXRpb24gYWRkcmVzcyBhZ2Fp
bnN0IGEgbGlzdCBvZiBwcmVmaXhlcywgZWFjaCBvZiB3aGljaCBoYXMgYW4gYXNzb2NpYXRlZCBs
ZW5ndGgsIHRvIGRldGVybWluZSB0aGUgbG9uZ2VzdCBtYXRjaC4NCg0KPiBXZXJlIHRoZSBzZXJ2
ZXIgdG8gaW5kaWNhdGUgcHJlY2lzZWx5IHdoaWNoIGFsbG9jYXRlZCBhZGRyZXNzICdiZWxvbmcn
DQo+IHRvIHdoaWNoIHByZWZpeCB0aGVuIHRhc2sgd291bGQgYmUgZWFzaWVyIHRvIHRoZSBDbGll
bnQuDQoNCkl0IGlzIGFuIGluY29ycmVjdCBzaG9ydGN1dCB0byBkZXJpdmUgYSBwcmVmaXggZnJv
bSBhIGxlbmd0aCBhc3NvY2lhdGVkIHdpdGggYW4gYWRkcmVzcy4NCg0KLSBSYWxwaA0KDQpQUyBU
aGlzIG1lc3NhZ2UgaXMgbGlrZWx5IG15IGxhc3QgcG9zdCBvbiB0aGUgbWF0dGVyLCB3aGljaCBp
cyBub3cgcmV2aXNpdGluZyB2ZXJ5IG9sZCB0b3BpY3MgdGhhdCBoYXZlIGJlZW4gZGlzY3Vzc2Vk
IGF0IGxlbmd0aCBpbiA2bWFuIGFuZCBlbHNld2hlcmUuDQoNCg==


From nobody Wed Apr  8 04:46:18 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3478D1B3040 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 JWgRhGeHgjOS for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 04:46:14 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB761B303F for <dhcwg@ietf.org>; Wed,  8 Apr 2015 04:46:14 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 2A2781BC3E for <dhcwg@ietf.org>; Wed,  8 Apr 2015 11:46:09 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <55250B05.8040600@gmail.com>
Date: Wed, 8 Apr 2015 12:46:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/kbud6wREQypf_0EGy40mFbV_LPc>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 11:46:16 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> Yes it will. We don't need a prefix to talk to the router, and we
>> don't need one to talk about a neighbour we've already found.
>=20
> But we need the prefix length value to be there, and valued at 128.

This, IMO, is where the problem lies. If you have a mindset that an =
address always has a [ subnet length | prefix length ] then there's =
always a problem with having an address without one. Part of this is =
that "we've always linked them", and I suspect it's rather heavily =
embedded in implementations that you can't have one without the other.
Ie, we're used (in the IPv4 world) to configuring an IP address, with =
it's subnet mask/length, and having a routing table entry automatically =
created.

But if for a moment you can ignore what current implementations do and =
what we've been used to - then we don't need a prefix attached to an =
address, we only need a list of prefixes we know how to reach directly =
and a list of routers to use for addresses that aren't within the first =
list.

So I take your statement to really mean "our current implementations =
can't cope without a prefix length, so we'll simulate not having one by =
using /128". I can agree with that if expressed in those terms, for the =
simple reason that we're not going to rework decades of code development =
overnight - so in the meantime we need to shoehorn one thing (addresses =
without prefixes) into another (structures that marry a prefix with =
every address).

Since I'm very much "not an expert" in IPv6 (especially it's history), I =
really don't know how much was implementations leading the standards (ie =
was all this specified before the implementations were done), or =
implementations going down the road of "it's IPv4 with more bits" due to =
lack of knowledge of the differences, or implementations going down the =
road of "we need to do it the old way or it's too much work to do it at =
all".


From nobody Wed Apr  8 05:39:12 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D5FC1A1A9A for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 05:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 KzE5nUe5Bij8 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 05:39:08 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 3E02C1A1A97 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 05:39:08 -0700 (PDT)
Received: from [186.134.76.56] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YfpG5-0004lv-QA; Wed, 08 Apr 2015 14:39:06 +0200
Message-ID: <55251EFA.4000204@si6networks.com>
Date: Wed, 08 Apr 2015 09:28:42 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com>
In-Reply-To: <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/YWdusXtZniPzI-dHAdRCTaX1k4k>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 12:39:11 -0000

Hi, Lorenzo,

On 04/08/2015 08:35 AM, Lorenzo Colitti wrote:
> On Wed, Apr 8, 2015 at 8:16 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     "   Implementations conforming to this specification SHOULD provide the
>        means for a system administrator to enable or disable the use of this
>        algorithm for generating IPv6 addresses."
> 
> That just changes the question to "what happens if the server uses both
> this type of address and other types of address".

The intent is that if you're going to use this scheme, for leasing
addreses, you use this scheme for all prefixes: at the end of the day,
if *one* of your addresses is predictable, that's enough for the
attacker to track you or scan you.


> More in general: if you're serious about this document being "just one
> possible way of generating IPv6 IIDs", 

I certainly am: I would have included an "Updates RFC3315" in the I-D,
otherwise.


> then you'll need to make it clear
> what is required for it to coexist with other ways of generating IPv6
> IIDs. If not, then you'll need to make it clear that it cannot coexist
> with other ways of generating addresses.

Other ways of generating IIDs for the same prefix, or for other prefixes?

For other prefixes, the idea is that if you use a weak scheme for other
prefixes, you're toast. For the same prefix, if you employ multple
schemes you won't achieve address stability.

Is this what you were referring to?



> Another issue I see is that the document says that the addresses are
> stable and stateless, but they're not, because the value of counter for
> every lease needs to be shared between the servers. For example, if the
> client sends a DECLINE because it fails DAD, what do you do? The address
> is no longer stable.

IMO, I see the counter as mostly an "optional" parameter, which allows
to recover from address collisions (rather than a mandatory field). If
you do employ the Counter, but do not store it, then whether the
addresses are stable or not depends on the order in which systems are
bootstrapped.



> Another issue: if the addresses are stable and stateless, then that
> means you can replace a server and have the client keep the same
> address. What modifications are needed on the server side for that to
> work? If the client sends a renew unicast to the new server, will this
> just work?

This deserves a clarification, indeed.

Of th top of my head:

* Address stability can be achieved 100% stateless-ly, but need not.
e.g., you can generate addresses as specified in this document, but
still keep an address lease database. In that case, the server would
employ this algorithm for generating the addresses in the first place,
but the address lease would be recorded in the lease database. After
that, things would work as for any other DHCPv6 address generation
scheme. If the server is replaced (same IP address, same server DUID),
renew/rebind itself would "fail" but then but then the same address
would be leased again (when the algorithm is applied ot generate a "new"
IPv6 address). For failover to a different server this doesn't really
matter, as a renew is sent to the same server, nt just ot "any server".


For a 100% stateless operation, then the server should check whether the
address t be renewed is the result of applying the expression in the
I-D. If it is, that'd be the same as having an entry in the lease
database. Otherwise, it's a "no binding" scenario. For the case where
one wants to cope with possible address clollisions, one might (MAY) the
server to try to expression (incrementing Counter) up to "MaxRetries"
(which should be the same value that the server should use when trying
to come up with a unique address but collissions are found).

Does (some version of) this sound reasonable?

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Apr  8 05:46:05 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F0B01A1AC1 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 05:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 tD8TBJm5bZsw for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 05:46:01 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 579CC1A0276 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 05:46:01 -0700 (PDT)
Received: by ignm3 with SMTP id m3so28460111ign.0 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 05:46:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=AfMSt9KONKcbmhzWtvKkb3QTQ2rBFbkhb7Mcr7FtuEM=; b=aNXsXXfsHfBnJ8EXWXX+seN2G6th5r+EGbgaxLrD5yDtJ2dBIpYCIZpeeCRzLHCkIS vIE+y84eXBCj/QGeN3RzRfNY4SK8JT7S9Vn7iiH7/6A2cGNeqoryH3wHC8in9/Q6TOe+ 7XvDk6Gw7n4AKiLVSX1h1wHHhuXXygneh2NLT4lkLpA0zn8TpNzJKPQa02/x3HJM6y3d j/6XZ+OM/vadlTXVRZgZVDOffX43Upoj3v1/8d5qfVSZ/eCT2+7qicuGAbYySIliGAYl 23oT6IliiHyOra5ajdBlrWmecUU/H28pa1a1KQYy6Xf/VLT/gLjC4zOjVZ8nVJ8Mv7di UFXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=AfMSt9KONKcbmhzWtvKkb3QTQ2rBFbkhb7Mcr7FtuEM=; b=LyVdphW0keYrWDVopW8461lOtGpLIpW6yLHs7cnt5RKc7feq59qhLjEQDR04LD4leo CSeFWXjZ+ozyWn95Zue24xBXEziLUh2gMqv2rnWaP9h0sy/w1mINFEzSKVVg7u1xf3Ef 8BqTbFUi+TjMhiwN/3rHrhkawbXydiE2MV5VQNO9j12eSEq95W67gqf6wkJLJX5zbaOL 0uDHtt+KXjZu0UACnwSnrh3MB+6wj0a+OO/JFO/Hi/YLH6wAyAPKeswuMdnhBVv3kbFa +do55p8VoqJlW1/m45hQZydSkyqBagwduOJVWzoysXI+eVkX31120r9cE6qHEJQaYcDM qrOA==
X-Gm-Message-State: ALoCoQl4cNTQxAZBB12Cy/kup5dft0l7c3y/JoCSTSygeGXiiiHdaWOK7iY8D8BGMjcKQXQncGsE
X-Received: by 10.50.77.13 with SMTP id o13mr488226igw.39.1428497160799; Wed, 08 Apr 2015 05:46:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 05:45:40 -0700 (PDT)
In-Reply-To: <55251EFA.4000204@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 8 Apr 2015 21:45:40 +0900
Message-ID: <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=047d7bdc110ad53ea8051335e9fc
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/yOLg6PYYkT1Etnactr8pvvbm9so>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 12:46:03 -0000

--047d7bdc110ad53ea8051335e9fc
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 8, 2015 at 9:28 PM, Fernando Gont <fgont@si6networks.com> wrote:

> > That just changes the question to "what happens if the server uses both
> > this type of address and other types of address".
>
> The intent is that if you're going to use this scheme, for leasing
> addreses, you use this scheme for all prefixes: at the end of the day,
> if *one* of your addresses is predictable, that's enough for the
> attacker to track you or scan you.
>

No, it's not enough. The attacker can only track or scan you if you use a
stupid algorithm to generate the IIDs. Yours is not stupid, but neither are
many others such as "random". You can perfectly well use random assignment
on some subnets and your algorithm on other subnets.

Regardless - if that's the intent, then the draft should say so.


> > then you'll need to make it clear
> > what is required for it to coexist with other ways of generating IPv6
> > IIDs. If not, then you'll need to make it clear that it cannot coexist
> > with other ways of generating addresses.
>
> Other ways of generating IIDs for the same prefix, or for other prefixes?
>
> For other prefixes, the idea is that if you use a weak scheme for other
> prefixes, you're toast. For the same prefix, if you employ multple
> schemes you won't achieve address stability.
>
> Is this what you were referring to?
>

I was referring to the lack of any such statement in the draft, yes.


> > Another issue I see is that the document says that the addresses are
> > stable and stateless, but they're not, because the value of counter for
> > every lease needs to be shared between the servers. For example, if the
> > client sends a DECLINE because it fails DAD, what do you do? The address
> > is no longer stable.
>
> IMO, I see the counter as mostly an "optional" parameter, which allows
> to recover from address collisions (rather than a mandatory field). If
> you do employ the Counter, but do not store it, then whether the
> addresses are stable or not depends on the order in which systems are
> bootstrapped.
>

Then the draft needs to say what the server needs to do if it doesn't use
the counter and the client sends a decline. Does the client get no address?


> > Another issue: if the addresses are stable and stateless, then that
> > means you can replace a server and have the client keep the same
> > address. What modifications are needed on the server side for that to
> > work? If the client sends a renew unicast to the new server, will this
> > just work?
>
> This deserves a clarification, indeed.
>
> Of th top of my head:
>
> * Address stability can be achieved 100% stateless-ly, but need not.
> e.g., you can generate addresses as specified in this document, but
> still keep an address lease database. In that case, the server would
> employ this algorithm for generating the addresses in the first place,
> but the address lease would be recorded in the lease database. After
> that, things would work as for any other DHCPv6 address generation
> scheme. If the server is replaced (same IP address, same server DUID),
> renew/rebind itself would "fail" but then but then the same address
> would be leased again (when the algorithm is applied ot generate a "new"
> IPv6 address). For failover to a different server this doesn't really
> matter, as a renew is sent to the same server, nt just ot "any server".
>
>
> For a 100% stateless operation, then the server should check whether the
> address t be renewed is the result of applying the expression in the
> I-D. If it is, that'd be the same as having an entry in the lease
> database. Otherwise, it's a "no binding" scenario. For the case where
> one wants to cope with possible address clollisions, one might (MAY) the
> server to try to expression (incrementing Counter) up to "MaxRetries"
> (which should be the same value that the server should use when trying
> to come up with a unique address but collissions are found).
>
> Does (some version of) this sound reasonable?
>

Perhaps. But you have to document this, and if you document this and it
turns out that you need server-side behaviour changes, then you need to
update RFC 3315.

Again, I don't think it's worth it.

--047d7bdc110ad53ea8051335e9fc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 8, 2015 at 9:28 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D"=
mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&g=
t;</span> wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><span class=3D"">&gt; That just changes the question to &quot;what=
 happens if the server uses both<br>
&gt; this type of address and other types of address&quot;.<br>
<br>
</span>The intent is that if you&#39;re going to use this scheme, for leasi=
ng<br>
addreses, you use this scheme for all prefixes: at the end of the day,<br>
if *one* of your addresses is predictable, that&#39;s enough for the<br>
attacker to track you or scan you.<br></blockquote><div><br></div><div>No, =
it&#39;s not enough. The attacker can only track or scan you if you use a s=
tupid algorithm to generate the IIDs. Yours is not stupid, but neither are =
many others such as &quot;random&quot;. You can perfectly well use random a=
ssignment on some subnets and your algorithm on other subnets.</div><div><b=
r></div><div>Regardless - if that&#39;s the intent, then the draft should s=
ay so.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"=
">&gt; then you&#39;ll need to make it clear<br>
&gt; what is required for it to coexist with other ways of generating IPv6<=
br>
&gt; IIDs. If not, then you&#39;ll need to make it clear that it cannot coe=
xist<br>
&gt; with other ways of generating addresses.<br>
<br>
</span>Other ways of generating IIDs for the same prefix, or for other pref=
ixes?<br>
<br>
For other prefixes, the idea is that if you use a weak scheme for other<br>
prefixes, you&#39;re toast. For the same prefix, if you employ multple<br>
schemes you won&#39;t achieve address stability.<br>
<br>
Is this what you were referring to?<br></blockquote><div><br></div><div>I w=
as referring to the lack of any such statement in the draft, yes.</div><div=
>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; Another i=
ssue I see is that the document says that the addresses are<br>
&gt; stable and stateless, but they&#39;re not, because the value of counte=
r for<br>
&gt; every lease needs to be shared between the servers. For example, if th=
e<br>
&gt; client sends a DECLINE because it fails DAD, what do you do? The addre=
ss<br>
&gt; is no longer stable.<br>
<br>
</span>IMO, I see the counter as mostly an &quot;optional&quot; parameter, =
which allows<br>
to recover from address collisions (rather than a mandatory field). If<br>
you do employ the Counter, but do not store it, then whether the<br>
addresses are stable or not depends on the order in which systems are<br>
bootstrapped.<br></blockquote><div><br></div><div>Then the draft needs to s=
ay what the server needs to do if it doesn&#39;t use the counter and the cl=
ient sends a decline. Does the client get no address?</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><span class=3D"">&gt; Another issue: if the=
 addresses are stable and stateless, then that<br>
&gt; means you can replace a server and have the client keep the same<br>
&gt; address. What modifications are needed on the server side for that to<=
br>
&gt; work? If the client sends a renew unicast to the new server, will this=
<br>
&gt; just work?<br>
<br>
</span>This deserves a clarification, indeed.<br>
<br>
Of th top of my head:<br>
<br>
* Address stability can be achieved 100% stateless-ly, but need not.<br>
e.g., you can generate addresses as specified in this document, but<br>
still keep an address lease database. In that case, the server would<br>
employ this algorithm for generating the addresses in the first place,<br>
but the address lease would be recorded in the lease database. After<br>
that, things would work as for any other DHCPv6 address generation<br>
scheme. If the server is replaced (same IP address, same server DUID),<br>
renew/rebind itself would &quot;fail&quot; but then but then the same addre=
ss<br>
would be leased again (when the algorithm is applied ot generate a &quot;ne=
w&quot;<br>
IPv6 address). For failover to a different server this doesn&#39;t really<b=
r>
matter, as a renew is sent to the same server, nt just ot &quot;any server&=
quot;.<br>
<br>
<br>
For a 100% stateless operation, then the server should check whether the<br=
>
address t be renewed is the result of applying the expression in the<br>
I-D. If it is, that&#39;d be the same as having an entry in the lease<br>
database. Otherwise, it&#39;s a &quot;no binding&quot; scenario. For the ca=
se where<br>
one wants to cope with possible address clollisions, one might (MAY) the<br=
>
server to try to expression (incrementing Counter) up to &quot;MaxRetries&q=
uot;<br>
(which should be the same value that the server should use when trying<br>
to come up with a unique address but collissions are found).<br>
<br>
Does (some version of) this sound reasonable?<br></blockquote><div><br></di=
v><div>Perhaps. But you have to document this, and if you document this and=
 it turns out that you need server-side behaviour changes, then you need to=
 update RFC 3315.</div><div><br></div><div>Again, I don&#39;t think it&#39;=
s worth it.</div></div></div></div>

--047d7bdc110ad53ea8051335e9fc--


From nobody Wed Apr  8 06:38:07 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 808851A8712 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 06:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=unavailable
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 vQxk48iAMYyk for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 06:37:55 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4E891A8700 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 06:37:55 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id AB7CF880D1 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 06:37:55 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 6D2CA13682CA for <dhcwg@ietf.org>; Wed,  8 Apr 2015 06:37:55 -0700 (PDT)
Message-ID: <55252F2C.1030402@innovationslab.net>
Date: Wed, 08 Apr 2015 09:37:48 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com> <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk>
In-Reply-To: <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UGWRVnVRN6KGV0WxCGr7nWmaHUCXgxtuH"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/4eRBzNYd6fd4QIIKI2sujzRE_AI>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 13:38:06 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--UGWRVnVRN6KGV0WxCGr7nWmaHUCXgxtuH
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable



On 4/8/15 7:46 AM, Simon Hobson wrote:
>=20
> Since I'm very much "not an expert" in IPv6 (especially it's
> history), I really don't know how much was implementations leading
> the standards (ie was all this specified before the implementations
> were done), or implementations going down the road of "it's IPv4 with
> more bits" due to lack of knowledge of the differences, or
> implementations going down the road of "we need to do it the old way
> or it's too much work to do it at all".
>=20

I will take my AD hat off and show my gray hair...

During much of the early IPv6 standardization work, a variety of groups
were pumping out implementations as the specs were being written.  I am
aware of at least two different groups that were trying to minimize code
development by taking existing IPv4 stack software, copying data
structures/functions/libraries, and then modifying them to handle IPv6.
 This caused some IPv6 implementations to inherit the IPv4
mindset/paradigm.  I can very much see that situation re-occurring here
with the prefix length discussion.

IMO, DHCPv6 allocates a 128-bit IPv6 address to a node's interface.  The
RAs on that link will tell the node the prefixes in use on the link and
routers to use to reach addresses off the link.

Regards,
Brian


--UGWRVnVRN6KGV0WxCGr7nWmaHUCXgxtuH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVJS8tAAoJEBOZRqCi7goqbq0H/3jVPsialnAuXo5SS0wIV3Ig
niFfoo6KCZzS4bKagvjvOLsGaWiWYRLf9GMpUBCe7Fl30ypJJRSEo50RYWRVSX2H
VryK3HHmuvwhF4Q+F2+LEohoxnOMyPLYaC/km5A8j8ggYpyagY6adUPk20kdVA/r
ekaF/lDgANBkSFjQNe6TesM87c5MgUjBR7osfpSwKGxBcj40570h7fsplXZUiiv+
3SRdq1A2uocKhIe3dXo4IlA7g/cQJ/1vCMEWS/hm4H2t24gFHaChLyhBbVRhr1vb
NfDMShK8OR2ht0pTQU3OuOjtYRbRmpZOknTGXoSRiNJeEp/vOSKUT0i/ijV6Z3Q=
=LQxl
-----END PGP SIGNATURE-----

--UGWRVnVRN6KGV0WxCGr7nWmaHUCXgxtuH--


From nobody Wed Apr  8 06:53:39 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6DB91A8782 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 06:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 BPs0LR8AqNMH for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 06:53:36 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B56E01A873D for <dhcwg@ietf.org>; Wed,  8 Apr 2015 06:53:36 -0700 (PDT)
Received: by iget9 with SMTP id t9so29584545ige.1 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 06:53:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RDXufEIvBos/FywuGzy27zRzjYHecpZLovULGkJ3cJs=; b=DefM9qBvThq6lhBMLJCq5pOIgu8LO66JfXW8g9pt9/g/Hp3kPHbiAYrRSnS4b3G3Iz 4dIfBG0m/hxkd7+UYdB3G5PVSZltJV5n951/zQjLrJXvXYg7zPW9/ggTW/O2NB2zqfPX nibJDMmpvFcuChf4QTXM2451xLENgp36SGEdJ0JM3euKwLJJH9dDJ6oPClHUQQ9GgodN jrqgihnTp6o9cNNrTDFejyh9UOuB/Uys0FKczB+t2k34vPsvcd9YqCaCp3v7IEuJH5gQ FsSRrfrqeeRk+JdJkWuvyhXJkKLfvO/1+wfOUUQ0DcZiL5c1glxHwCyR2ZSkS+gpVLje iZ3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=RDXufEIvBos/FywuGzy27zRzjYHecpZLovULGkJ3cJs=; b=aPlCDkZ8jnc0MMNDGSszMgDIOYB7lgS1zx66poCUDNF/96jzdO2yQN6togx/ysKuz6 7gOxv0fcFHAXCEv5JvebCyTY+hb7K2zWdR8DqzHCIxW1Z91+M59SHQXJcwfzTqYrDb1K TR3ueD5U6BDtZPJV+LnaBht6RCxt6tAfojwY16O/eBsfufXvGwTt3XiQvLLTaqdoFvty otd4/0cC2EQ2iFUxyOGVJknSv+5eg85mCLg++oe4d3roeCqvGNGjvHpknEeV0NY7x1Bi lQXmeyzB8P6+54UdxkOJCaZejA40L/giegJzGn7cf411mQ3GJ1L7jOtfAB5aRvliElOt KbHQ==
X-Gm-Message-State: ALoCoQkzuLpZqvF2HUh3TmYYGU1KZkIrkcF65Z38e2dNAMAL76dfIG95wDrPW/Gxaj+Z7cvOaCYs
X-Received: by 10.107.46.155 with SMTP id u27mr37737762iou.87.1428501216214; Wed, 08 Apr 2015 06:53:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 06:53:15 -0700 (PDT)
In-Reply-To: <55252F2C.1030402@innovationslab.net>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com> <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk> <55252F2C.1030402@innovationslab.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 8 Apr 2015 22:53:15 +0900
Message-ID: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/alternative; boundary=001a113ac5b68de918051336dbf6
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pKs0O5TemeiU_sTY2HbzzeeoXAk>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 13:53:38 -0000

--001a113ac5b68de918051336dbf6
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 8, 2015 at 10:37 PM, Brian Haberman <brian@innovationslab.net>
wrote:

> IMO, DHCPv6 allocates a 128-bit IPv6 address to a node's interface.  The
> RAs on that link will tell the node the prefixes in use on the link and
> routers to use to reach addresses off the link.
>

What he said.

--001a113ac5b68de918051336dbf6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 8, 2015 at 10:37 PM, Brian Haberman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:brian@innovationslab.net" target=3D"_blank">brian@innovationslab=
.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">IMO, DHCPv6 al=
locates a 128-bit IPv6 address to a node&#39;s interface.=C2=A0 The<br>
RAs on that link will tell the node the prefixes in use on the link and<br>
routers to use to reach addresses off the link.<br></blockquote><div><br></=
div><div>What he said.</div></div></div></div>

--001a113ac5b68de918051336dbf6--


From nobody Wed Apr  8 07:46:20 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B52221B318B for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 07:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 S7aXrXuwxZMX for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 07:46:17 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 EDD3F1B318E for <dhcwg@ietf.org>; Wed,  8 Apr 2015 07:46:16 -0700 (PDT)
Received: from [186.134.76.56] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YfrF6-0005A9-OI; Wed, 08 Apr 2015 16:46:13 +0200
Message-ID: <55253F14.6000706@si6networks.com>
Date: Wed, 08 Apr 2015 11:45:40 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/zouOmA-0a7i4EZpVo9_uFEi682c>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 14:46:19 -0000

Hi, Lorenzo,

On 04/08/2015 09:45 AM, Lorenzo Colitti wrote:
> On Wed, Apr 8, 2015 at 9:28 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > That just changes the question to "what happens if the server uses both
>     > this type of address and other types of address".
> 
>     The intent is that if you're going to use this scheme, for leasing
>     addreses, you use this scheme for all prefixes: at the end of the day,
>     if *one* of your addresses is predictable, that's enough for the
>     attacker to track you or scan you.
> 
> 
> No, it's not enough. The attacker can only track or scan you if you use
> a stupid algorithm to generate the IIDs. Yours is not stupid, but
> neither are many others such as "random". You can perfectly well use
> random assignment on some subnets and your algorithm on other subnets.

The intent is that, for a given subnet, all IIDs have the same property.

But, in any case, as far as I recall this I-D does not say "you must
employ this algorithm for all of the prefixes from which you lease
addresses", anyway.

If you have any suggested text that would address your concern, please
do let us know.


> Regardless - if that's the intent, then the draft should say so.

mm.. how about changing this:

---- cut here ----
   DHCPv6 server implementations conforming to this specification MUST
   generate non-temporary IPv6 addresses using the algorithm specified
   in this section.

   Implementations conforming to this specification SHOULD provide the
   means for a system administrator to enable or disable the use of this
   algorithm for generating IPv6 addresses.

   All of the parameters included in the expression below MUST be
   included when generating an IPv6 address.

   A DHCPv6 server implementing this specification must select the IPv6
   addresses to be leased with the following algorithm:
---- cut here ----

to to this:

---- cut here ----
   A DHCPv6 server implementation employing this specification MUST
   generate non-temporary IPv6 addresses for the corresponding prefix
   by means of the algorithm specified in this section.

   Implementations conforming to this specification SHOULD provide the
   means for a system administrator to enable or disable the use of this
   algorithm for generating IPv6 addresses.

   Unless otherwise noted, all of the parameters included in the
   expression below MUST be included when generating an IPv6 address.

   A DHCPv6 server employing this specification must select the IPv6
   addresses to be leased from the corresponding prefix with the
   following algorithm:
---- cut here ----

?




>     > then you'll need to make it clear
>     > what is required for it to coexist with other ways of generating IPv6
>     > IIDs. If not, then you'll need to make it clear that it cannot coexist
>     > with other ways of generating addresses.
> 
>     Other ways of generating IIDs for the same prefix, or for other
>     prefixes?
> 
>     For other prefixes, the idea is that if you use a weak scheme for other
>     prefixes, you're toast. For the same prefix, if you employ multple
>     schemes you won't achieve address stability.
> 
>     Is this what you were referring to?
> 
> 
> I was referring to the lack of any such statement in the draft, yes.

Ok, how about adding something along these lines:

---- cut here ----
In order to achieve the goals described in Section 3 of this document,
all of the DHCPv6 servers leasing addresses from a given IPv6 address
range must employ this algorithm. If different DHCPv6 servers leasing
addresses from the same IPv6 address range employ different algorithms,
address stability will not be achieved.

DHCPv6 servers leasing addresses from different IPv6 address ranges may
employ other algorithms for selecting the IPv6 addresses to be leased.
We note, however, that security-unwise algorithm is employed for
selecting addresses from a different IPv6 address range on the same
subnet, the benefits of the algorithm specified in this document may be
reduced. For example, if a DHCPv6 server employs this algorithm for
selecting addresses from a given address range, and another server on
the same subnet selects address incrementally for a different address
range on the same subnet, a node that is leased addresses from both
address ranges will still be vulnerable to address scans attacks.
---- cut here ----

?


>     > Another issue I see is that the document says that the addresses are
>     > stable and stateless, but they're not, because the value of counter for
>     > every lease needs to be shared between the servers. For example, if the
>     > client sends a DECLINE because it fails DAD, what do you do? The address
>     > is no longer stable.
> 
>     IMO, I see the counter as mostly an "optional" parameter, which allows
>     to recover from address collisions (rather than a mandatory field). If
>     you do employ the Counter, but do not store it, then whether the
>     addresses are stable or not depends on the order in which systems are
>     bootstrapped.
> 
> 
> Then the draft needs to say what the server needs to do if it doesn't
> use the counter and the client sends a decline. Does the client get no
> address?

If you don't use the counter at all, yes. However, I'd expect
implementations not to include the counter, but not to record it's
contents (if they don't record the address lease) -- (yes, sorry, my
previous response was confusing).

I'll craft text about this and send it to the list for review.



>     > Another issue: if the addresses are stable and stateless, then that
>     > means you can replace a server and have the client keep the same
>     > address. What modifications are needed on the server side for that to
>     > work? If the client sends a renew unicast to the new server, will this
>     > just work?
> 
>     This deserves a clarification, indeed.
> 
>     Of th top of my head:
> 
>     * Address stability can be achieved 100% stateless-ly, but need not.
>     e.g., you can generate addresses as specified in this document, but
>     still keep an address lease database. In that case, the server would
>     employ this algorithm for generating the addresses in the first place,
[....[
> 
>     Does (some version of) this sound reasonable?
> 
> Perhaps. But you have to document this, and if you document this and it
> turns out that you need server-side behaviour changes, then you need to
> update RFC 3315.
> 
> Again, I don't think it's worth it.

For the time being, I think we should not consider the 100% stateless
version of this. After all, the man goal of this document is an address
selection scheme for DHCPv6, rather than an improvement in terms of "now
DHCPv6 can be fully stateless".

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Apr  8 08:03:37 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9EC21B31EF for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 08:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 GJPiLxTpaX3t for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 08:03:31 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3F2C1A888B for <dhcwg@ietf.org>; Wed,  8 Apr 2015 08:03:30 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t38F3Rp4029183; Wed, 8 Apr 2015 17:03:27 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7A79F2096F6; Wed,  8 Apr 2015 17:04:31 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 6E49E20971E; Wed,  8 Apr 2015 17:04:31 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t38F39TK028332; Wed, 8 Apr 2015 17:03:27 +0200
Message-ID: <5525432D.1020907@gmail.com>
Date: Wed, 08 Apr 2015 17:03:09 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com> <5525045B.5050204@gmail.com> <CAKD1Yr3=ZGmxPsuOVf4++tp0Rh=ZTYK6ecc5Hy_HoGnc3OqXOA@mail.gmail.com>
In-Reply-To: <CAKD1Yr3=ZGmxPsuOVf4++tp0Rh=ZTYK6ecc5Hy_HoGnc3OqXOA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/UUUqOdoOpI7EypBivg3DPDXH0gI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 15:03:35 -0000

Le 08/04/2015 12:37, Lorenzo Colitti a Ã©crit :
> On Wed, Apr 8, 2015 at 7:35 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>>
> wrote:
>
> Well, the linux stack implementation does not act that way. Adding an
> address on an interface implies a routing table entry is added too.
>
>
> Not true. It acts that way if you specify a prefix length of 128.

YEs and no.

Yes: if you add an address on an interface by using ifconfig and don't
specify a prefix length, the prefix length will be 128 by programmer's wish.

No: if you do specify a prefixlen, or if you dont specify a prefix
length, an entry will be added anyways in the routing table (the
specified preflen in the first case, /128 in the 2nd case).

That is to say that even if specifications (RFC5942 section 4 bullet1
"Host Rule number 1" tells that Host "MUST NOT implicitly cause a prefix
derived from that address to be treated as on-link and added to the
Prefix List." is not implemented.

If a programmer implements that Rule then programmer has no means to
write a coherent "longest prefix match", because there is no prefix length.

Moreover, a programmer porting an IPv4 implementation to IPv6 will have
no means to put something in the "subnet mask" fields, if the prefixlen
is absent.

Alex



From nobody Wed Apr  8 08:16:27 2015
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE941B322F for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 08:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 vY_HbHeincIh for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 08:16:25 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 394231B322B for <dhcwg@ietf.org>; Wed,  8 Apr 2015 08:16:25 -0700 (PDT)
Received: by qkhg7 with SMTP id g7so87352118qkh.2 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 08:16:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=8gsOxYJ4vAsJtVte1S2eoia69jgdOsqIo9zUxp9RP7M=; b=Dd4MogJfmpOOusc+gFJhFoVLH+mChQlvcuOLGjZQtmOrXouPVwoeMyf1+uHMiQNANr EdIvDRDWXSfCB4atAKMGlxa0K0l2CD7B0CUOL/PiDWzp54SEGvmT03ToDw1XlO9vHJ1/ BBxlqLwu2BArHwllFSahJr3/nxhU23JJAOr5bLKQPnyQayWk7cJOXFE2a9HH7POK5N55 02LqW9T4No/0Zhf/7mK/pTMg0Ou2xc7gwOl3UBACxWhy7Ifj1sSvAZ4FZiqJcGBzj+0z /YrpYtb92geGxQaqWZ4XTlk7jVA6y7I8AYwwOkZuObl3BT2cvhS6SGBd/4CtGjKAftQf jSuQ==
X-Received: by 10.55.55.7 with SMTP id e7mr49706574qka.52.1428506184561; Wed, 08 Apr 2015 08:16:24 -0700 (PDT)
Received: from [192.168.1.118] ([73.186.127.35]) by mx.google.com with ESMTPSA id f64sm7667279qhc.37.2015.04.08.08.16.23 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Apr 2015 08:16:23 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com>
Date: Wed, 8 Apr 2015 11:16:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <D1DBAF21-7254-4ADA-A932-D38278131328@cisco.com> <55199583.9050605@gmail.com> <6CE5CC94-327D-4B83-A330-A06C6BFF4C9B@thehobsons.co.uk> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com> <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk> <55252F2C.1030402@innovationslab.net> <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/oOWqDmhSUuXGJwtrR4he7KIBnd0>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 15:16:26 -0000

> On Apr 8, 2015, at 9:53 AM 4/8/15, Lorenzo Colitti =
<lorenzo@google.com> wrote:
>=20
> On Wed, Apr 8, 2015 at 10:37 PM, Brian Haberman =
<brian@innovationslab.net> wrote:
> IMO, DHCPv6 allocates a 128-bit IPv6 address to a node's interface.  =
The
> RAs on that link will tell the node the prefixes in use on the link =
and
> routers to use to reach addresses off the link.
>=20
> What he said.

Agreed ... precisely and concisely correct.

- Ralph


From nobody Wed Apr  8 08:39:30 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754E31B324B for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 08:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 4Gvv1IHj1uW3 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 08:39:26 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9A01B32BD for <dhcwg@ietf.org>; Wed,  8 Apr 2015 08:39:04 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 3DD421BC3E for <dhcwg@ietf.org>; Wed,  8 Apr 2015 15:39:00 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5525432D.1020907@gmail.com>
Date: Wed, 8 Apr 2015 16:38:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com> <5525045B.5050204@gmail.com> <CAKD1Yr3=ZGmxPsuOVf4++tp0Rh=ZTYK6ecc5Hy_HoGnc3OqXOA@mail.gmail.com> <5525432D.1020907@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/r8QL-vmes-nKcsBGXB0cyIqXW_k>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 15:39:28 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> If a programmer implements that Rule then programmer has no means to
> write a coherent "longest prefix match", because there is no prefix =
length.

But there is - the stack will have a list of prefixes which are to be =
considered local to this link. Any address configured on this interface =
does **NOT** have to be within one of those prefixes.

Put another way, you do not need a prefix associated with a configured =
address on your own interface to work out if a completely unrelated =
address (that of the destination for a new connection) is within a list =
of prefixes associated with that interface.


> Moreover, a programmer porting an IPv4 implementation to IPv6 will =
have
> no means to put something in the "subnet mask" fields, if the =
prefixlen
> is absent.

That is indeed an issue - but then there are many other things a =
programmer must do when writing/porting an application for IPv6.
For many, just "making the fields bigger" will do - and then (as =
previously discussed) a workaround might be to just use /128 as a dummy =
value. For an application that accepts incoming connections on multiple =
interfaces and address, then replies using the same address, I imagine =
the IPv6 stack will deal with the technicalities of getting the reply =
back to the right place*.

Even for applications making outbound connections, I assume they'll just =
use the default address unless told otherwise, and the stack will take =
care of the routing.

* I'm thinking about details like "if the source address is in prefix X, =
then send it via router Y which provided the RA containing prefix X". =
Particularly important for networks with multiple internet connections =
(and separate provider aggregated prefixes).


From nobody Wed Apr  8 08:59:02 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD81C1A88B4 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 08:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 QwXG2SpNxm8D for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 08:58:56 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA04F1A890A for <dhcwg@ietf.org>; Wed,  8 Apr 2015 08:55:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t38FtlLp014616 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 17:55:48 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 31F56209787 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 17:56:52 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 2A016209773 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 17:56:52 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t38FtMxG028395 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 17:55:47 +0200
Message-ID: <55254F6A.4020005@gmail.com>
Date: Wed, 08 Apr 2015 17:55:22 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com> <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk> <55252F2C.1030402@innovationslab.net> <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com>
In-Reply-To: <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/YZ15_LKOP_fsJf4FjbHD1cpCBPs>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 15:59:01 -0000

Le 08/04/2015 17:16, Ralph Droms a écrit :
>
>> On Apr 8, 2015, at 9:53 AM 4/8/15, Lorenzo Colitti
>> <lorenzo@google.com> wrote:
>>
>> On Wed, Apr 8, 2015 at 10:37 PM, Brian Haberman
>> <brian@innovationslab.net> wrote: IMO, DHCPv6 allocates a 128-bit
>> IPv6 address to a node's interface.  The RAs on that link will
>> tell the node the prefixes in use on the link and routers to use
>> to reach addresses off the link.
>>
>> What he said.
>
> Agreed ... precisely and concisely correct.

I disagree.  Almost entirely.

There must be a way for DHCP to work by itself, without assistance from RA.

A particular network I connect to tries to satisfy everyone (RA and
DHCP) and the result is... not beautiful: there are two routers on the
link: one sends the RA the other serves DHCP.

This result (have two routers on same link - one for RA, one for DHCP)
was not the goal of a RA-w-DHCP discussion, I guess.

Alex


From nobody Wed Apr  8 09:02:55 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61EFE1A896E for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 09:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 5HgDj_4pcuhd for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 09:02:53 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 602301B3308 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 09:00:43 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 829F01BC3E for <dhcwg@ietf.org>; Wed,  8 Apr 2015 16:00:39 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk>
Date: Wed, 8 Apr 2015 17:00:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com> <5525045B.5050204@gmail.com> <CAKD1Yr3=ZGmxPsuOVf4++tp0Rh=ZTYK6ecc5Hy_HoGnc3OqXOA@mail.gmail.com> <5525432D.1020907@gmail.com> <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SK-0g-rLA0ke6YqhUs1ybasuc4Y>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 16:02:54 -0000

I wrote:

>> If a programmer implements that Rule then programmer has no means to
>> write a coherent "longest prefix match", because there is no prefix =
length.
>=20
> But there is - the stack will have a list of prefixes which are to be =
considered local to this link. Any address configured on this interface =
does **NOT** have to be within one of those prefixes.
>=20
> Put another way, you do not need a prefix associated with a configured =
address on your own interface to work out if a completely unrelated =
address (that of the destination for a new connection) is within a list =
of prefixes associated with that interface.

As an example, if you wish to send a packet to 2001:DB8:1::1 and you are =
told (via an RA) that 2001:DB8:1::/48 is on-link, then do you have =
enough information to determine if the destination address is on-link ?
Answer - yes you do.
All you need to do is the simple logical operations we're familiar with =
from the IPv4 world - mask the address with the prefix length derived =
subnet mask, if the result matches then the address is "in" the prefix. =
Logical AND 2001:DB8::1 with ffff:ffff:ffff:: and you get 2001:DB8::, =
compare 2001:DB8:1:: with 2001:DB8:1:: and you'll find that it matches.

Note that I didn't tell you what source address I was assuming - because =
it doesn't matter. It may or may not be in this prefix, or indeed any =
prefix advertised as being on-link for this interface. It could, for =
example, be 2001:DB8:1234::5678 which is *not* in the same prefix as the =
destination address.


From nobody Wed Apr  8 09:07:43 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5F91B3271 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 09:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 EgTyOO45mxqG for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 09:07:40 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 6389A1B2AFD for <dhcwg@ietf.org>; Wed,  8 Apr 2015 09:07:40 -0700 (PDT)
X-Quarantine-ID: <sR1zHDFBdIGo>
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
X-Amavis-Alert: BAD HEADER SECTION, Header line longer than 998 characters: References: <al[...]
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id E4AF61BC3E for <dhcwg@ietf.org>; Wed,  8 Apr 2015 16:07:36 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <55254F6A.4020005@gmail.com>
Date: Wed, 8 Apr 2015 17:07:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA5EB635-8D89-48A6-9320-50F5C8C67479@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <CAPi140O2dY3rry+ssK6zvbE6QGv3sLdb0R6ms4b2u7B6HtHqyQ@mail.gmail.com> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com> <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk> <55252F2C.1030402@innovationslab.net> <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gm ail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pcnrebERdTi9dqOVVlsolWmkKI0>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 16:07:41 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> There must be a way for DHCP to work by itself, without assistance =
from RA.

I agree. I don't recall seeing anything that says a device can fall back =
to assuming everything is local (and hence find it by ND) if there are =
no RA provided prefixes - or more importantly, no routers present. As =
previously mentioned, the network will work fine without any prefixes if =
the router(s) either forward the packets or provide redirects informing =
the hosts that the other host they are talking to is on-link.

> A particular network I connect to tries to satisfy everyone (RA and
> DHCP) and the result is... not beautiful: there are two routers on the
> link: one sends the RA the other serves DHCP.
>=20
> This result (have two routers on same link - one for RA, one for DHCP)
> was not the goal of a RA-w-DHCP discussion, I guess.

Err, what ?

You have described *ONE* router and *ONE* server. The two could be on =
the same device - there is no fundamental reason why the router =
(offering RAs) cannot be on the same device as the DHCP server.
If you have **CHOSEN** to run two devices to provide the services then =
that is up to you - it is not imposed by the standards.


From nobody Wed Apr  8 09:19:10 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59CF11B33C8 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 09:19:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 qwUCokHAnXiL for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 09:19:06 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6358F1B33BB for <dhcwg@ietf.org>; Wed,  8 Apr 2015 09:19:03 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t38GJ16V016878 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 18:19:01 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B71E02097D6 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 18:20:05 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B0875206774 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 18:20:05 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t38GISfx024053 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 18:19:01 +0200
Message-ID: <552554D4.5000304@gmail.com>
Date: Wed, 08 Apr 2015 18:18:28 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com> <5525045B.5050204@gmail.com> <CAKD1Yr3=ZGmxPsuOVf4++tp0Rh=ZTYK6ecc5Hy_HoGnc3OqXOA@mail.gmail.com> <5525432D.1020907@gmail.com> <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk> <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk>
In-Reply-To: <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/lYLxLXOXcJijjJBPsXozw6XMuT4>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 16:19:08 -0000

Le 08/04/2015 18:00, Simon Hobson a écrit :
> I wrote:
>
>>> If a programmer implements that Rule then programmer has no means
>>> to write a coherent "longest prefix match", because there is no
>>> prefix length.
>>
>> But there is - the stack will have a list of prefixes which are to
>>  be considered local to this link. Any address configured on this
>> interface does **NOT** have to be within one of those prefixes.
>>
>> Put another way, you do not need a prefix associated with a
>> configured address on your own interface to work out if a
>> completely unrelated address (that of the destination for a new
>> connection) is within a list of prefixes associated with that
>> interface.
>
> As an example, if you wish to send a packet to 2001:DB8:1::1 and you
>  are told (via an RA) that 2001:DB8:1::/48 is on-link, then do you
> have enough information to determine if the destination address is
> on-link ? Answer - yes you do.

YEs you do, I agree.

> All you need to do is the simple logical operations we're familiar
> with from the IPv4 world - mask the address with the prefix length
> derived subnet mask, if the result matches then the address is "in"
> the prefix. Logical AND 2001:DB8::1 with ffff:ffff:ffff:: and you
> get 2001:DB8::, compare 2001:DB8:1:: with 2001:DB8:1:: and you'll
> find that it matches.

YEs, it works because you have that prefixlen from the RA.

> Note that I didn't tell you what source address I was assuming -
> because it doesn't matter. It may or may not be in this prefix, or
> indeed any prefix advertised as being on-link for this interface. It
>  could, for example, be 2001:DB8:1234::5678 which is *not* in the
> same prefix as the destination address.

Right.

But let me reply with another example: it should be possible to manually
assign an address on an interface, manually assign the default route,
have no RA at all, and still be able to ping the Internet.

If this manual operation (assign address, default route) does not work,
one depends a lot on that RA be there and be correct.  Configuring RAs
on routers is an additional operation which rarely exists in IPv4; it
has its own quirks different enough to fear.

Alex
PS: I am also a supporter of IPv4 RAs without which some other context
wont work (mobility).

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr  8 09:22:41 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 873781A894E; Wed,  8 Apr 2015 09:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 U5p3N5mAQ4Ed; Wed,  8 Apr 2015 09:22:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 304061B33D5; Wed,  8 Apr 2015 09:22:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <draft-ietf-dhc-dynamic-shared-v4allocation.ad@ietf.org>, <volz@cisco.com>, <dhc-chairs@ietf.org>, <draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org>, <dhcwg@ietf.org>,  <draft-ietf-dhc-dynamic-shared-v4allocation.shepherd@ietf.org>, 
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150408162233.9744.25872.idtracker@ietfa.amsl.com>
Date: Wed, 08 Apr 2015 09:22:33 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SA8D3QpkXUfUZ20G5JaaCnyBgUM>
Subject: [dhcwg] ID Tracker State Update Notice: <draft-ietf-dhc-dynamic-shared-v4allocation-05.txt>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 16:22:40 -0000

IESG state changed to AD Evaluation from Publication Requested
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/


From nobody Wed Apr  8 09:23:12 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28EE51B3339; Wed,  8 Apr 2015 09:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 yj3hVu1Bh_d8; Wed,  8 Apr 2015 09:23:10 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CED4F1B3337; Wed,  8 Apr 2015 09:22:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <dhc-chairs@ietf.org>, <draft-ietf-dhc-access-network-identifier.shepherd@ietf.org>,  <draft-ietf-dhc-access-network-identifier.ad@ietf.org>,  <dhcwg@ietf.org>, <draft-ietf-dhc-access-network-identifier@ietf.org>, <jiangsheng@huawei.com>, 
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150408162250.11678.99266.idtracker@ietfa.amsl.com>
Date: Wed, 08 Apr 2015 09:22:50 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/OCnEC2Tef0mE6FR26zaNSfJtqYI>
Subject: [dhcwg] ID Tracker State Update Notice: <draft-ietf-dhc-access-network-identifier-06.txt>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 16:23:11 -0000

IESG state changed to AD Evaluation from Publication Requested
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-dhc-access-network-identifier/


From nobody Wed Apr  8 09:24:05 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64C951A88EF for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 09:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 l2eE1UUQImRK for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 09:24:02 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 847491A88BF for <dhcwg@ietf.org>; Wed,  8 Apr 2015 09:24:01 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t38GNxnf023025 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 18:23:59 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0276E2097A8 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 18:25:04 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id EE95E2096F0 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 18:25:03 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t38GNuUk008996 for <dhcwg@ietf.org>; Wed, 8 Apr 2015 18:23:59 +0200
Message-ID: <5525561C.2030002@gmail.com>
Date: Wed, 08 Apr 2015 18:23:56 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com> <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk> <55252F2C.1030402@innovationslab.net> <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gm ail.com> <DA5EB635-8D89-48A6-9320-50F5C8C67479@thehobsons.c! o.uk>
In-Reply-To: <DA5EB635-8D89-48A6-9320-50F5C8C67479@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/fabo7Ifx2Rls4jEWOWz2I-amo5A>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 16:24:04 -0000

Le 08/04/2015 18:07, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>> There must be a way for DHCP to work by itself, without assistance
>>  from RA.
>
> I agree. I don't recall seeing anything that says a device can fall
> back to assuming everything is local (and hence find it by ND) if
> there are no RA provided prefixes - or more importantly, no routers
> present. As previously mentioned, the network will work fine without
>  any prefixes if the router(s) either forward the packets or provide
>  redirects informing the hosts that the other host they are talking
> to is on-link.

Or if sysadmin manually decides who's on link (insert entries in routing
table).

>> A particular network I connect to tries to satisfy everyone (RA
>> and DHCP) and the result is... not beautiful: there are two routers
>> on the link: one sends the RA the other serves DHCP.
>>
>> This result (have two routers on same link - one for RA, one for
>> DHCP) was not the goal of a RA-w-DHCP discussion, I guess.
>
> Err, what ?
>
> You have described *ONE* router and *ONE* server.

Ok, it's two MAchines: one sends the RA the other sends the DHCP
Advertise.  It's a point-to-point link (cellular).

> The two could be on the same device - there is no fundamental reason
> why the router (offering RAs) cannot be on the same device as the
> DHCP server.

There are two different src addresses in the RA and in the DHCP
Advertise.  Why would the DHCP server use a different src address than
the Router sending the RA if not because there were two different
machines on the same link?

> If you have **CHOSEN** to run two devices to provide the services
> then that is up to you - it is not imposed by the standards.

But no, this is wrong.  If you want to provide reliability with RAs
there are ways  for two Routers on same link send same RA in a reliable
manner.  If you want reliability with DHCP there are ways to have
multiple reliable DHCP servers on same link.

But there is no way to achieve reliability between RA and DHCP.  If the
RA machine falls down the DHCP server can not provide same information
(not as of today, some parameters are still RA-only whereas others are
still DHCP-only).

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr  8 12:13:23 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BABC1B351A for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 12:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 To4uB67O2qNU for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 12:13:19 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 8042B1B3518 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 12:13:19 -0700 (PDT)
X-Quarantine-ID: <7IDgZjFW4sJr>
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
X-Amavis-Alert: BAD HEADER SECTION, Header line longer than 998 characters: References: <al[...]
Received: from [192.168.1.61] (88-111-162-175.dynamic.dsl.as9105.com [88.111.162.175]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 146981BC3E for <dhcwg@ietf.org>; Wed,  8 Apr 2015 19:13:14 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5525561C.2030002@gmail.com>
Date: Wed, 8 Apr 2015 20:13:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2DCE91D-3F51-4F21-8895-A4F5BC4AEB86@thehobsons.co.uk>
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <46259D0E-E4E9-4304-9E56-E0907B6F07F3@thehobsons.co.uk> <CAKD1Yr35okmNbS94vCKwP5eNqJvKfegUbu9PFE8KB1dPcWkexw@mail.gmail.com> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com> <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk> <55252F2C.1030402@innovationslab.net> <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gm ail.com> <DA5EB635-8D89-48A6-9320-50F5C8C67479@thehobsons.c! o.uk> < 5525561C.2030002@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/RmnwEUt6fQXbm5pSGbvgUlqFZzY>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 19:13:22 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> But let me reply with another example: it should be possible to =
manually
> assign an address on an interface, manually assign the default route,
> have no RA at all, and still be able to ping the Internet.

I don't recall reading anywhere that you cannot do that - but as I say, =
I'm no expert. But that still does not mean you need to provide the =
prefix as part of the address. So to do those three things, you'd do =
three things :
add an address
add a prefix (if needed)
add a router (again, I don't know if manually configuring routes is =
considered unsupported or not, but I know it works in Debian and I can't =
see any reason not to allow it even if it is the hardest way to =
configure a network (in the general case))

But the discussion was specifically about DHCP - so manual configuration =
is out of the scope of the thread.


Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>>> A particular network I connect to tries to satisfy everyone (RA
>>> and DHCP) and the result is... not beautiful: there are two routers
>>> on the link: one sends the RA the other serves DHCP.
>>>=20
>>> This result (have two routers on same link - one for RA, one for
>>> DHCP) was not the goal of a RA-w-DHCP discussion, I guess.
>>=20
>> Err, what ?
>>=20
>> You have described *ONE* router and *ONE* server.
>=20
> Ok, it's two MAchines: one sends the RA the other sends the DHCP
> Advertise.  It's a point-to-point link (cellular).

But you miss the point. There is nothing to stop both services being =
part of one appliance - if they aren't then it's because for whatever =
reason the architect of that network decided to make them separate.

>> The two could be on the same device - there is no fundamental reason
>> why the router (offering RAs) cannot be on the same device as the
>> DHCP server.
>=20
> There are two different src addresses in the RA and in the DHCP
> Advertise.  Why would the DHCP server use a different src address than
> the Router sending the RA if not because there were two different
> machines on the same link?

There are some good reasons to do that. One is to make services more =
portable.
Eg, if you run a machine with multiple services, then you might run each =
service on a different IP. That way, should you decide to move one =
service, you take the IP away to the new home for the service and leave =
the rest of the services as is - saves all the *fun* of getting all the =
users to be using the same updated DNS entries from the moment you move =
the service. Switchover takes only as long as the router needs to update =
it's ARP/neighbour cache.

>> If you have **CHOSEN** to run two devices to provide the services
>> then that is up to you - it is not imposed by the standards.
>=20
> But no, this is wrong.  If you want to provide reliability with RAs
> there are ways  for two Routers on same link send same RA in a =
reliable
> manner.  If you want reliability with DHCP there are ways to have
> multiple reliable DHCP servers on same link.
>=20
> But there is no way to achieve reliability between RA and DHCP.  If =
the
> RA machine falls down the DHCP server can not provide same information
> (not as of today, some parameters are still RA-only whereas others are
> still DHCP-only).

I don't quite follow there - but it's by design that the information =
provided by RAs and DHCP are different, specifically that DHCP doesn't =
provide the prefix information.

Wether you have one router & one DHCP server, or multiple routers and =
multiple DHCP servers - there is (of course) the issue of co-ordinating =
them so that if one of your internet connections goes down, you stop =
giving clients addresses in a prefix that's only usable via that =
connection. That's not really any different to the IPv4 world when using =
public addresses.
But if the routers are redundant in that they both provide routing for =
the same prefix(es), then I see no issue.

Perhaps you could clarify what the perceived issue is ?


From nobody Wed Apr  8 14:32:31 2015
Return-Path: <huitema@microsoft.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF8211B36D8 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 14:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.602
X-Spam-Level: 
X-Spam-Status: No, score=-0.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_ILLEGAL_IP=1.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 d3cAkkEUf62Y for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 14:32:28 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0102.outbound.protection.outlook.com [207.46.100.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 672DD1B36D2 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 14:32:28 -0700 (PDT)
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com (0.160.96.17) by DM2PR0301MB0656.namprd03.prod.outlook.com (0.160.96.18) with Microsoft SMTP Server (TLS) id 15.1.130.23; Wed, 8 Apr 2015 21:32:24 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com ([0.160.96.17]) by DM2PR0301MB0655.namprd03.prod.outlook.com ([0.160.96.17]) with mapi id 15.01.0130.020; Wed, 8 Apr 2015 21:32:24 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>, Lorenzo Colitti <lorenzo@google.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUoMJbTD1bZXk+QhGz7q11ugZ04hNEAgAADQ4CAAAlnAIAF8IkAgACpKACAA401gIAAPCOAgAAHLICAAADYgIAABPgAgAAFfwCAAA7PAIAABL4AgAAhhwCAAGz3QA==
Date: Wed, 8 Apr 2015 21:32:24 +0000
Message-ID: <DM2PR0301MB0655FDB31066DE7E1CA809A4A8FC0@DM2PR0301MB0655.namprd03.prod.outlook.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com>
In-Reply-To: <55253F14.6000706@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e0:ee43::4]
authentication-results: si6networks.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0656;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(377454003)(479174004)(24454002)(230783001)(99286002)(76176999)(33656002)(50986999)(2656002)(54356999)(87936001)(2900100001)(2950100001)(74316001)(86362001)(106116001)(40100003)(92566002)(46102003)(93886004)(62966003)(76576001)(102836002)(19580395003)(122556002)(77156002)(19580405001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0656; H:DM2PR0301MB0655.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <DM2PR0301MB065650A0F26B8A0024C270A9A8FC0@DM2PR0301MB0656.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:DM2PR0301MB0656; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0656; 
x-forefront-prvs: 0540846A1D
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2015 21:32:24.6552 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0656
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/-nfTg5T2SNyXuTf-Jdg4ePOxE4Y>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 21:32:29 -0000

To comment further on this discussion between Fernando and Lorenzo

> On 04/08/2015 09:45 AM, Lorenzo Colitti wrote:
> > On Wed, Apr 8, 2015 at 9:28 PM, Fernando Gont <fgont@si6networks.com
> > <mailto:fgont@si6networks.com>> wrote:
> >
> >     ...
> >     The intent is that if you're going to use this scheme, for leasing
> >     addreses, you use this scheme for all prefixes: at the end of the d=
ay,
> >     if *one* of your addresses is predictable, that's enough for the
> >     attacker to track you or scan you.
> >
> >
> > No, it's not enough. The attacker can only track or scan you if you
> > use a stupid algorithm to generate the IIDs. Yours is not stupid, but
> > neither are many others such as "random". You can perfectly well use
> > random assignment on some subnets and your algorithm on other subnets.

I think there is value in having some part of the DHCPv6 spec specify the "=
don't be stupid" logic. My personal preference would be to add the list of =
privacy attacks in the "security considerations" of DHCPv6bis. Something li=
ke:

Some address allocation schemes are known to be harmful, because they facil=
itate scanning, allow for information leakage, or fail to maintain the addr=
ess stability required by many applications. In particular:
* Assigning addresses using some kind of sequential algorithm (prefix::1, p=
refix:2, prefix::3,...) greatly facilitate scanning of the network;
* Deriving the IID part of addresses from the link layer address of the cli=
ent exposes information about the client hardware and enables tracking the =
client across multiple subnets;
* Using memory-less random allocation schemes fails to maintain enough stab=
ility for many applications;
The algorithm presented in [RFC7217] provides a solution to this problem fo=
r nodes using IPv6 Stateless Address Autoconfiguration. Similar algorithms =
could be used by DHCPv6 servers to avoid the aforementioned issues.

If we added that to the main DHCPv6 spec, there would be no need for a sepa=
rate RFC presenting a variant of the 7217 algorithm.

-- Christian Huitema



From nobody Wed Apr  8 14:48:29 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C581A89AF for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 14:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 FcZuiN-sbkrz for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 14:48:26 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE1091A89A7 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 14:48:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3199; q=dns/txt; s=iport; t=1428529701; x=1429739301; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=8Vgsa4sJqVW/4LRaQTTUEngSW5KvUX4xyZqtiaE9xHg=; b=FBwXgtvtkj6dfnmEaIET1cdul78Y2FiuWqAFeH1o85Y4Kbk7FH1AKFus LY3Fzzz+DLI0GjmOcvtSp4JDlhIyb2Y/ulr82mRf9cQiBAl9TOC2N6BY+ Yj6lGhS/Nu7FiE1xM455OVcwxJSmV++ew6bwa4ju+E1PJXbHKBF2ZI6cb A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B6BAA3oSVV/5BdJa1cgwhSXAXDZwmBUoV9AoEuOBQBAQEBAQEBfYQfAQEBAwEnEz8FBwQCAQgRBAEBAQoUBQQHMhQJCAIEAQ0FCBOIBwgNzSMBAQEBAQEBAQEBAQEBAQEBAQEBAQEXiyuEMQYUJgsHBoMRgRYFhRCLZIN4hyw6iXqFQINKIoIDHBSBPG8BgUN/AQEB
X-IronPort-AV: E=Sophos;i="5.11,546,1422921600"; d="scan'208";a="139486143"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-6.cisco.com with ESMTP; 08 Apr 2015 21:48:21 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t38LmKSP021633 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Apr 2015 21:48:20 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Wed, 8 Apr 2015 16:48:20 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Christian Huitema <huitema@microsoft.com>, Fernando Gont <fgont@si6networks.com>, Lorenzo Colitti <lorenzo@google.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUWByZTAVuV8ESYM5tVpMLK4p04ge2AgABZ+YD//7DXMIAKWypfgABgb4CAAAcrgIAAANmAgAAE+ACAAAV/AIAADs8AgAAEvQCAACGHAIAAcaQA//+u96A=
Date: Wed, 8 Apr 2015 21:48:20 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA45882@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <DM2PR0301MB0655FDB31066DE7E1CA809A4A8FC0@DM2PR0301MB0655.namprd03.prod.outlook.com>
In-Reply-To: <DM2PR0301MB0655FDB31066DE7E1CA809A4A8FC0@DM2PR0301MB0655.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.114]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/G22MDYWdgPldjPmykel2DQWXYAA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 21:48:28 -0000

There is already some text in draft-ietf-dhc-dhcpv6-privacy, section 4.3, o=
n DHCP server allocation strategies, so it the question is whether that is =
sufficient or whether perhaps something is needed in the draft-huitema-dhc-=
anonymity-profile ... though I think that is more focused on the client. If=
 there was existing text, the 3315bis document can refer to it in the Secur=
ity/Privacy Considerations section. Note that I suspect that these privacy =
documents will be RFCs long before 3315bis will be.

I think your text is fine. And, it is recorded in the ticket on this issue,=
 http://trac.tools.ietf.org/group/dhcpv6bis/ticket/145.

I also think your conclusion is fine :).

- Bernie

-----Original Message-----
From: Christian Huitema [mailto:huitema@microsoft.com]=20
Sent: Wednesday, April 08, 2015 5:32 PM
To: Fernando Gont; Lorenzo Colitti
Cc: dhcwg@ietf.org; Bernie Volz (volz); Ted Lemon
Subject: RE: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-address=
es -> abandon work? / IA_NA applicability

To comment further on this discussion between Fernando and Lorenzo

> On 04/08/2015 09:45 AM, Lorenzo Colitti wrote:
> > On Wed, Apr 8, 2015 at 9:28 PM, Fernando Gont <fgont@si6networks.com=20
> > <mailto:fgont@si6networks.com>> wrote:
> >
> >     ...
> >     The intent is that if you're going to use this scheme, for leasing
> >     addreses, you use this scheme for all prefixes: at the end of the d=
ay,
> >     if *one* of your addresses is predictable, that's enough for the
> >     attacker to track you or scan you.
> >
> >
> > No, it's not enough. The attacker can only track or scan you if you=20
> > use a stupid algorithm to generate the IIDs. Yours is not stupid,=20
> > but neither are many others such as "random". You can perfectly well=20
> > use random assignment on some subnets and your algorithm on other subne=
ts.

I think there is value in having some part of the DHCPv6 spec specify the "=
don't be stupid" logic. My personal preference would be to add the list of =
privacy attacks in the "security considerations" of DHCPv6bis. Something li=
ke:

Some address allocation schemes are known to be harmful, because they facil=
itate scanning, allow for information leakage, or fail to maintain the addr=
ess stability required by many applications. In particular:
* Assigning addresses using some kind of sequential algorithm (prefix::1, p=
refix:2, prefix::3,...) greatly facilitate scanning of the network;
* Deriving the IID part of addresses from the link layer address of the cli=
ent exposes information about the client hardware and enables tracking the =
client across multiple subnets;
* Using memory-less random allocation schemes fails to maintain enough stab=
ility for many applications; The algorithm presented in [RFC7217] provides =
a solution to this problem for nodes using IPv6 Stateless Address Autoconfi=
guration. Similar algorithms could be used by DHCPv6 servers to avoid the a=
forementioned issues.

If we added that to the main DHCPv6 spec, there would be no need for a sepa=
rate RFC presenting a variant of the 7217 algorithm.

-- Christian Huitema



From nobody Wed Apr  8 17:18:37 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0BEA1A6FEB for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 17:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 6Bf4jZgZ1WEa for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 17:18:35 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 715061A6FE7 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 17:18:35 -0700 (PDT)
Received: by igblo3 with SMTP id lo3so54137557igb.1 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 17:18:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CA6occccY7zJdQvGGiwuSSylpB7DgGFqRw/CVk+MMtc=; b=bzyiJ1X3s+9VwA2XmEf9NXek2u97KLqn9cvgI5172TTjoQnQZmUAkp0hyPcTgaMYMU jJ3d78Mc4TmZJ/SA+uFzjHZPDDjMPcLKrnTBUFtXCQg6JbuY6GvwtGZU38HIPVZhBzZ0 RWE0E8ECXqSL5egJ8mLmjwYiGS9tBsgsMWHgGkl+Isc5ldmmH3GGw0pYGtF8fImpoylp npSlueUSHMA9n/OFeCc2LdzDTqeC0MNF3DAk1mvNbm4KepxQKtc/nS0+YZs3f59ecwfF kbaTVIStOFzY9DKRIzNiECkk0z+7M/IgG4a2dmDlMPvvNKyHOrH/d2TxMycPzIugJJpP Mj5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=CA6occccY7zJdQvGGiwuSSylpB7DgGFqRw/CVk+MMtc=; b=lU+G1AI+fOyE/2AwACPGB5ztPBeYeNsUmklZlLbXEhVMg15vRD2HZZEe3eU5ahj5Cc TV6fyLCMOqoTy4kV/Pxn1q8xgRSmW7kHYrjO41ACEHU7Nb5x9kVQeCaZ24dNFHKtExL4 5WMiizWnOUvph3Trewuwmyd6R8IfA4jSVLLnyhLMhv8tUL9O8LZVJKr4wM/lksRIsfmf e6UsSMaZ+k6t3cfmE0Hn6fDyV0Fll+LlWMlCLg2x261vHzfkzEa685AWOr8lMTSVFObg jrcxTrCFPz+jqhPyyqSl/QAdtjRIFqMvTJU5sjW3KNiXTuKCqZvYZ3zEczk+xV7tvRVe OpOQ==
X-Gm-Message-State: ALoCoQl3vRBul+Jtr65uINUrPZ+47av/8P9vwt6BTEyQnyhW+4GtWu89lOsxZPSYDCQyoZQKHzXP
X-Received: by 10.50.43.162 with SMTP id x2mr16019181igl.46.1428538714689; Wed, 08 Apr 2015 17:18:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 17:18:14 -0700 (PDT)
In-Reply-To: <55253F14.6000706@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Apr 2015 09:18:14 +0900
Message-ID: <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=089e0103e4cea34ebb05133f9659
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Y_NjdutJ_VdnZU3xU8F8wyxdf-o>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 00:18:37 -0000

--089e0103e4cea34ebb05133f9659
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 8, 2015 at 11:45 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> But, in any case, as far as I recall this I-D does not say "you must
> employ this algorithm for all of the prefixes from which you lease
> addresses", anyway.
>
> If you have any suggested text that would address your concern, please
> do let us know.
>

Well, as you know my suggestion is to leave this up to implementers and not
standardize this algorithm at all :-)


> >     * Address stability can be achieved 100% stateless-ly, but need not.
> >     e.g., you can generate addresses as specified in this document, but
> >     still keep an address lease database. In that case, the server would
> >     employ this algorithm for generating the addresses in the first
> place,
> [....[
> >
> >     Does (some version of) this sound reasonable?
> >
> > Perhaps. But you have to document this, and if you document this and it
> > turns out that you need server-side behaviour changes, then you need to
> > update RFC 3315.
> >
> > Again, I don't think it's worth it.
>
> For the time being, I think we should not consider the 100% stateless
> version of this. After all, the man goal of this document is an address
> selection scheme for DHCPv6, rather than an improvement in terms of "now
> DHCPv6 can be fully stateless".


If this algorithm does not allow stateless operation, and still requires
keeping (and synchronizing) a lease database, then I really don't see the
point of specifying this algorithm at all, as it provides no advantages
over stateful random assignment.

--089e0103e4cea34ebb05133f9659
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 8, 2015 at 11:45 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But, in any case, as fa=
r as I recall this I-D does not say &quot;you must<br>
employ this algorithm for all of the prefixes from which you lease<br>
addresses&quot;, anyway.<br>
<br>
If you have any suggested text that would address your concern, please<br>
do let us know.<br></blockquote><div><br></div><div>Well, as you know my su=
ggestion is to leave this up to implementers and not standardize this algor=
ithm at all :-)</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span =
class=3D"">&gt;=C2=A0 =C2=A0 =C2=A0* Address stability can be achieved 100%=
 stateless-ly, but need not.<br>
&gt;=C2=A0 =C2=A0 =C2=A0e.g., you can generate addresses as specified in th=
is document, but<br>
&gt;=C2=A0 =C2=A0 =C2=A0still keep an address lease database. In that case,=
 the server would<br>
&gt;=C2=A0 =C2=A0 =C2=A0employ this algorithm for generating the addresses =
in the first place,<br>
</span>[....[<br>
<span class=3D"">&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Does (some version of) this sound reasonable?<br>
&gt;<br>
&gt; Perhaps. But you have to document this, and if you document this and i=
t<br>
&gt; turns out that you need server-side behaviour changes, then you need t=
o<br>
&gt; update RFC 3315.<br>
&gt;<br>
&gt; Again, I don&#39;t think it&#39;s worth it.<br>
<br>
</span>For the time being, I think we should not consider the 100% stateles=
s<br>
version of this. After all, the man goal of this document is an address<br>
selection scheme for DHCPv6, rather than an improvement in terms of &quot;n=
ow<br>
DHCPv6 can be fully stateless&quot;.</blockquote><div><br></div><div>If thi=
s algorithm does not allow stateless operation, and still requires keeping =
(and synchronizing) a lease database, then I really don&#39;t see the point=
 of specifying this algorithm at all, as it provides no advantages over sta=
teful random assignment.</div></div></div></div>

--089e0103e4cea34ebb05133f9659--


From nobody Wed Apr  8 21:51:19 2015
Return-Path: <sthaug@nethelp.no>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECB4D1ACE7B for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 21:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 t4wg39tjZQRx for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 21:51:15 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id D30AB1A7002 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 21:46:58 -0700 (PDT)
Received: (qmail 63157 invoked from network); 9 Apr 2015 04:46:56 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 9 Apr 2015 04:46:56 -0000
Date: Thu, 09 Apr 2015 06:46:56 +0200 (CEST)
Message-Id: <20150409.064656.74691916.sthaug@nethelp.no>
To: alexandru.petrescu@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <552554D4.5000304@gmail.com>
References: <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk> <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk> <552554D4.5000304@gmail.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/dhcwg/UyInYWJGN6V4R-TQS1-hxvvswz4>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 04:51:18 -0000

> But let me reply with another example: it should be possible to manually
> assign an address on an interface, manually assign the default route,
> have no RA at all, and still be able to ping the Internet.

Of course. And a sensible OS (e.g. FreeBSD) will indeed let you do that. 

Steinar Haug, AS 2116


From nobody Wed Apr  8 22:12:43 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1CC1AD0CB for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 EUKPNz3M6II7 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:12:41 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E04241B2AE6 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 22:12:31 -0700 (PDT)
Received: by ignm3 with SMTP id m3so42435513ign.0 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 22:12:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=I3xg722u0im558iI0DnYDeZqr+brk1x6LI8jlT+8GK8=; b=QeM6RKm1QXKh+TCU8bePShC2F/FURUPNjrBq8Eu1siV/jQuayhq3mtdXC/W9RRKB5y 7Q34LSNSMngPtzc2CGSu75H+UE9Lj0/onucRTVe1WVDfCqGxZ18vGjQHc2Htd7gcLkdu wyJkmOvny0uftY0j/TKqJ3vO4V10XRm+K/BLcVK0bjPykA8LDgC5fANBqcp6c5KePiNo VkPa+iQN3srZ2VOTwt5V9wLejTVSpZ5un9IcD/4V+waM8ZO1HHLStvXZwJTtKcNsWsgC SFMlVisdfi6b4ZQHXPU8rPSdKVSbwc8f91TwV4mDx+nHdMJp3TI5CFwUTJnx9VU7yQrt Iivw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=I3xg722u0im558iI0DnYDeZqr+brk1x6LI8jlT+8GK8=; b=kpCLll76cEjP6/RHRgZaMyREJnpeC5eUY4VW1qK4u7Om4YnW3SN/+oIhC6hfKjRKKk ZT4yTH7ayWBO0dmdJDdAtHWaVq+q7u96h9AzavDgplx4z/64aT+gV9Dg4O7EMG+RACe5 NVp3h2a8XfWdyUMZwIca4lQZ1NNJdUqWCi5NoJQ98nfGz7kgdfZl3GClzAC+6JPI4LYQ 0y+yj9L2k40h66Zt3Kw2lnoI+wpO34ZfKhZESqQfKFysBRhHu7YsKElkE8Mui10l44of Z86S70C/bVjnkeq097j2yEBsAznwXpojiQ1A72/AzncmZkVcRP+xx5Ayo142mZUk+Iz1 mmuw==
X-Gm-Message-State: ALoCoQlJBqGTF90GDO9zwnL12i10ERXXffm5Apzl06rLoV0YAMLn0M07P9ep+CbZKxDGZjU97MEt
MIME-Version: 1.0
X-Received: by 10.107.130.145 with SMTP id m17mr42426590ioi.89.1428556351271;  Wed, 08 Apr 2015 22:12:31 -0700 (PDT)
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 22:12:30 -0700 (PDT)
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 22:12:30 -0700 (PDT)
In-Reply-To: <20150409.064656.74691916.sthaug@nethelp.no>
References: <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk> <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk> <552554D4.5000304@gmail.com> <20150409.064656.74691916.sthaug@nethelp.no>
Date: Thu, 9 Apr 2015 14:12:30 +0900
Message-ID: <CAKD1Yr2e3c0Q8_NTyv=RUyS7Ex-2tHPgN4hg3-neVwbK-Fxiag@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
To: sthaug@nethelp.no
Content-Type: multipart/alternative; boundary=001a113ed02adc1bb5051343b1ef
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/JzfBjCr7pCOK-Q5Pk_wwXk3x0XY>
Cc: dhcwg@ietf.org, Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 05:12:43 -0000

--001a113ed02adc1bb5051343b1ef
Content-Type: text/plain; charset=UTF-8

On 9 Apr 2015 1:51 pm, <sthaug@nethelp.no> wrote:
> > But let me reply with another example: it should be possible to manually
> > assign an address on an interface, manually assign the default route,
> > have no RA at all, and still be able to ping the Internet.
>
> Of course. And a sensible OS (e.g. FreeBSD) will indeed let you do that.

So will Linux.

--001a113ed02adc1bb5051343b1ef
Content-Type: text/html; charset=UTF-8

<p dir="ltr"><br>
On 9 Apr 2015 1:51 pm, &lt;<a href="mailto:sthaug@nethelp.no">sthaug@nethelp.no</a>&gt; wrote:<br>
&gt; &gt; But let me reply with another example: it should be possible to manually<br>
&gt; &gt; assign an address on an interface, manually assign the default route,<br>
&gt; &gt; have no RA at all, and still be able to ping the Internet.<br>
&gt;<br>
&gt; Of course. And a sensible OS (e.g. FreeBSD) will indeed let you do that.</p>
<p dir="ltr">So will Linux.</p>

--001a113ed02adc1bb5051343b1ef--


From nobody Wed Apr  8 22:45:27 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8FF1B2C91 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 rWX4zRuncKkD for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:45:25 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA1D01B2C90 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 22:45:24 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t395jMbx023990; Thu, 9 Apr 2015 07:45:22 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C369220325C; Thu,  9 Apr 2015 07:46:27 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id AE7B3203256; Thu,  9 Apr 2015 07:46:27 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t395jKbF011158; Thu, 9 Apr 2015 07:45:22 +0200
Message-ID: <552611EE.1020803@gmail.com>
Date: Thu, 09 Apr 2015 07:45:18 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: sthaug@nethelp.no
References: <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk>	<89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk>	<552554D4.5000304@gmail.com> <20150409.064656.74691916.sthaug@nethelp.no>
In-Reply-To: <20150409.064656.74691916.sthaug@nethelp.no>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/6kDqQluDvWpXYQSPzNqgMjh7rjs>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 05:45:26 -0000

Le 09/04/2015 06:46, sthaug@nethelp.no a écrit :
>> But let me reply with another example: it should be possible to
>> manually assign an address on an interface, manually assign the
>> default route, have no RA at all, and still be able to ping the
>> Internet.
>
> Of course. And a sensible OS (e.g. FreeBSD) will indeed let you do
> that.

Will the OS also add a plen /128 whenever sysadmin types "ifconfig add
address" w/o specifying a plen?  And will it add an entry in the rt
table for that /128 address?  (linux does both).

Alex

>
> Steinar Haug, AS 2116
>
>



From nobody Wed Apr  8 22:46:03 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 197C51B2C9A for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 IDtWyGWlnlik for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:46:00 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 488771B2C99 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 22:46:00 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t395jvTf001286; Thu, 9 Apr 2015 07:45:57 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 65B6F203256; Thu,  9 Apr 2015 07:47:02 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4E9A12007EE; Thu,  9 Apr 2015 07:47:02 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t395juk8011475; Thu, 9 Apr 2015 07:45:57 +0200
Message-ID: <55261214.6060201@gmail.com>
Date: Thu, 09 Apr 2015 07:45:56 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, sthaug@nethelp.no
References: <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk>	<89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk>	<552554D4.5000304@gmail.com>	<20150409.064656.74691916.sthaug@nethelp.no> <CAKD1Yr2e3c0Q8_NTyv=RUyS7Ex-2tHPgN4hg3-neVwbK-Fxiag@mail.gmail.com>
In-Reply-To: <CAKD1Yr2e3c0Q8_NTyv=RUyS7Ex-2tHPgN4hg3-neVwbK-Fxiag@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Vo6cBfehQm7JKC11JCZj8uwjoSQ>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 05:46:02 -0000

Le 09/04/2015 07:12, Lorenzo Colitti a Ã©crit :
>
> On 9 Apr 2015 1:51 pm, <sthaug@nethelp.no <mailto:sthaug@nethelp.no>> wrote:
>  > > But let me reply with another example: it should be possible to
> manually
>  > > assign an address on an interface, manually assign the default route,
>  > > have no RA at all, and still be able to ping the Internet.
>  >
>  > Of course. And a sensible OS (e.g. FreeBSD) will indeed let you do that.
>
> So will Linux.

And linux will add a /128 plen whenever sysadmin types "ifconfig add 
address" w/o telling a plen.

Alex

>



From nobody Wed Apr  8 22:50:35 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF2601B2CAA for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 KWynO2ztSaLD for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:50:32 -0700 (PDT)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C02A21B2CA9 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 22:50:32 -0700 (PDT)
Received: by iedfl3 with SMTP id fl3so104552565ied.1 for <dhcwg@ietf.org>; Wed, 08 Apr 2015 22:50:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ojtQYoG044M/Kj1cVLQReYTuq3L+Ll2cT5vZmj2gUxU=; b=I01JT4ZD79vA8LjZK8c1O+bJ/y5gGJ1UwPMmgVrvFAWAXP7kUjCAUldawfqBqtRjr7 gidX6SENkr4GQbRVGi49iBqbzZ4jva+Mla/Pg2II6ckdBqQZGLXOxNgqxmwAx4ekdtr7 0yxuR9wFoS61xk0HFjHYu+zaI4qbZbCG/L8yX10yXGalGIgsWJlMjvoWMKvBT5127WLr JlIVO6eXXpq0tg0s78MONG2PKrDIYgrooY4I+bePryVEe2/4n2k5pUf1yGri/a1s5Hbf pY8NhM5dr9VbhEKnABCvTeT57JHoPrxF5/mPgMLt6eZACBttoy8nDTwwS6+yIyfIjjVP E0mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=ojtQYoG044M/Kj1cVLQReYTuq3L+Ll2cT5vZmj2gUxU=; b=RXWEPy0NXg+fEUh2OnaHHwSY7b46Cfy4+8H3bnZ3CrtL9I0A5u1fOrxj8uskKeMD2T 1QZrMh/NlRBNKzhslTIoRrC1xbrhCGEVkOnhEllOxSw4665qSLth9Nllzq2/IHJk6gWi OALVnOXbD6u8mydtF8OL5TPBWFvYXE+wxPqxlkpSl1LN+kFMVIfkSVKDeU40uB+AEtXi qav7tfAfahQ0F91Ll/AOQ/DWPW+S2sRvzChZhlRcuecOuwwpU/l69jNgEpGyTI9TP1/x mfSXz84uRFfJmi8YPD8RggqeShxzfaM7ycZqf1vobrsYpIprIt+d1f5p8LzBuvAll2i9 aNiA==
X-Gm-Message-State: ALoCoQltmITOAZkglNG08ynkzWI7bRhxyv4ey7htRwmxqDN8s0GPUM6Eo1jpgeKJcrbw3JHZmbmh
X-Received: by 10.43.72.138 with SMTP id yo10mr38191989icb.69.1428558632190; Wed, 08 Apr 2015 22:50:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Wed, 8 Apr 2015 22:50:11 -0700 (PDT)
In-Reply-To: <552611EE.1020803@gmail.com>
References: <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk> <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk> <552554D4.5000304@gmail.com> <20150409.064656.74691916.sthaug@nethelp.no> <552611EE.1020803@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Apr 2015 14:50:11 +0900
Message-ID: <CAKD1Yr2zrSQSEm=uatcSaiV9JnG6uYvK8bRvgf-F0LX1a4+XAA@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c204fed0292305134439db
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jXiz1qvg2v7M4jHSemrTx3X2GI0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 05:50:34 -0000

--001a11c204fed0292305134439db
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 9, 2015 at 2:45 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> Of course. And a sensible OS (e.g. FreeBSD) will indeed let you do
>> that.
>>
>
> Will the OS also add a plen /128 whenever sysadmin types "ifconfig add
> address" w/o specifying a plen?


Yes. Internally, the OS always represents addresses with prefix lengths.
This is a more general representation than just an address. An address of
prefix length /128 is an address with no implicit route, an address of
prefix length != /128 is an address without an implicit route.


> And will it add an entry in the rt table for that /128 address?  (linux
> does both).
>

Of course it does. That's necessary for things to work. It has to to add a
route pointing at the loopback interface, otherwise it wouldn't know that
if someone wants to send a packet to that address, it should send it on
loopback, and if it receives a packet for that address, it knows to deliver
that packet to UDP/TCP/... sockets.

--001a11c204fed0292305134439db
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 9, 2015 at 2:45 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petre=
scu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span=
 class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">Of course. And a sensible OS (e.=
g. FreeBSD) will indeed let you do<br>
that.<br>
</blockquote>
<br></span>
Will the OS also add a plen /128 whenever sysadmin types &quot;ifconfig add=
<br>
address&quot; w/o specifying a plen?</blockquote><div><br></div><div>Yes. I=
nternally, the OS always represents addresses with prefix lengths. This is =
a more general representation than just an address. An address of prefix le=
ngth /128 is an address with no implicit route, an address of prefix length=
 !=3D /128 is an address without an implicit route.</div><div>=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">And will it add an entry in the rt=C2=A0table=
 for that /128 address?=C2=A0 (linux does both).<br></blockquote><div><br><=
/div><div>Of course it does. That&#39;s necessary for things to work. It ha=
s to to add a route pointing at the loopback interface, otherwise it wouldn=
&#39;t know that if someone wants to send a packet to that address, it shou=
ld send it on loopback, and if it receives a packet for that address, it kn=
ows to deliver that packet to UDP/TCP/... sockets.</div></div></div></div>

--001a11c204fed0292305134439db--


From nobody Wed Apr  8 22:58:59 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0CE1B2CD5 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.783
X-Spam-Level: 
X-Spam-Status: No, score=-3.783 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, J_CHICKENPOX_24=0.6, J_CHICKENPOX_42=0.6, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 0ulsf_fXm3Yc for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 22:58:56 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D2211B2CD0 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 22:58:55 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t395wsGN004213 for <dhcwg@ietf.org>; Thu, 9 Apr 2015 07:58:54 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B8B0C203242 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 07:59:59 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B02762007EE for <dhcwg@ietf.org>; Thu,  9 Apr 2015 07:59:59 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t395waeQ006161 for <dhcwg@ietf.org>; Thu, 9 Apr 2015 07:58:54 +0200
Message-ID: <5526150C.7000702@gmail.com>
Date: Thu, 09 Apr 2015 07:58:36 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <00365B71-E9A4-4698-B4C9-89AA9DF90EF6@nominum.com> <551BAC15.3020700@gmail.com> <337765D7-7CF8-4DB5-A1FB-EE3E061EF7EC@thehobsons.co.uk> <551BD674.1040301@gmail.com> <1701949C-41CE-4FED-B5E8-6BF56533F11D@thehobsons.co.uk> <551CE97E.4020504@gmail.com> <6FD01CDD-A0E6-4013-89E2-74ECB14C0DF4@thehobsons.co.uk> <551D0865.9070308@gmail.com> <71DE0C98-997E-4475-9EF2-C9E11CCD6E49@thehobsons.co.uk> <551D7B09.5000601@gmail.com> <BD9154F6-70CB-4049-ADEA-6C086376BCF1@thehobsons.co.uk> <55250B05.8040600@gmail.com> <F9DD3EB9-E0D1-4690-AFF6-A3626049F1D4@thehobsons.co.uk> <55252F2C.1030402@innovationslab.net> <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gm ail.com> <DA5EB635-8D89-48A6-9320-50F5C8C67479@thehobsons.c! o.uk> < 5525561C.2030002@gmail.com> <B2DCE91D-3F51-4F21-8895-A4F5BC4AEB86@thehobsons.co.uk>
In-Reply-To: <B2DCE91D-3F51-4F21-8895-A4F5BC4AEB86@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/hnKjhiAJAZb9GwWlk-HAbVDmnws>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 05:58:58 -0000

Le 08/04/2015 21:13, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>> But let me reply with another example: it should be possible to
>> manually assign an address on an interface, manually assign the
>> default route, have no RA at all, and still be able to ping the
>> Internet.
>
> I don't recall reading anywhere that you cannot do that - but as I
> say, I'm no expert.

Well, with ifconfig (for example): one can add an address like this:
"ifconfig add address" or like this:
"ifconfig add address/plen".

In the former case, even though the sysadmin does not add a plen the
programmer behind will add a plen /128 to that address, and will add an
entry in the rt table for that.

> But that still does not mean you need to provide the prefix as part
> of the address.

In the above example the sysadmin does not need to provide a prefix but
the stack (linux) will add a /128 because so the programmer wants.

> So to do those three things, you'd do three things :
>
> add an address
>
> add a prefix (if needed)
>
> add a router (again, I don't know if manually configuring routes is
> considered unsupported or not, but I know it works in Debian and I
> can't see any reason not to allow it even if it is the hardest way to
> configure a network (in the general case))

I agree.  But the system will add a plen if the sysadmin doesnt.

> But the discussion was specifically about DHCP - so manual
> configuration is out of the scope of the thread.

I agree - this discussion is about auto-configuration.  But
auto-configuration comes _after_ configuration.  If the manual
configuration says that a plen is needed then the auto-configuration
must provide one.

> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>>> A particular network I connect to tries to satisfy everyone
>>>> (RA and DHCP) and the result is... not beautiful: there are two
>>>>  routers on the link: one sends the RA the other serves DHCP.
>>>>
>>>> This result (have two routers on same link - one for RA, one
>>>> for DHCP) was not the goal of a RA-w-DHCP discussion, I guess.
>>>
>>> Err, what ?
>>>
>>> You have described *ONE* router and *ONE* server.
>>
>> Ok, it's two MAchines: one sends the RA the other sends the DHCP
>> Advertise.  It's a point-to-point link (cellular).
>
> But you miss the point. There is nothing to stop both services being
>  part of one appliance - if they aren't then it's because for
> whatever reason the architect of that network decided to make them
> separate.

I missed it a bit, yes.  I mentioned reliability in this discussion
because in other discussions I am told reliability is the reason to have
both RA and DHCP in place.

There are other reasons to have both RA and DHCP in place in a cellular
network:
- accept as many as possible clients; some clients do only RA, whereas
   others do DHCP+RA.
- deliver a DNS server to clients who dont implement DNS-in-RA option.
- some cellular interface kinds and their drivers support DHCP others
   dont.

>>> The two could be on the same device - there is no fundamental
>>> reason why the router (offering RAs) cannot be on the same device
>>> as the DHCP server.
>>
>> There are two different src addresses in the RA and in the DHCP
>> Advertise.  Why would the DHCP server use a different src address
>> than the Router sending the RA if not because there were two
>> different machines on the same link?
>
> There are some good reasons to do that. One is to make services more
>  portable. Eg, if you run a machine with multiple services, then you
>  might run each service on a different IP. That way, should you
> decide to move one service, you take the IP away to the new home for
> the service and leave the rest of the services as is - saves all the
>  *fun* of getting all the users to be using the same updated DNS
> entries from the moment you move the service. Switchover takes only
> as long as the router needs to update it's ARP/neighbour cache.

Ok, switchover, load balancing...

But switchover and load balancing is easier when same protocol is
involved rather than two entirely different protocols (SLAAC and DHCP).
  The implementations of a same protocol rely on a same database
structure which are easier to synchronize during load balancing, switch
over, traffic offloading.

>>> If you have **CHOSEN** to run two devices to provide the
>>> services then that is up to you - it is not imposed by the
>>> standards.
>>
>> But no, this is wrong.  If you want to provide reliability with
>> RAs there are ways  for two Routers on same link send same RA in a
>>  reliable manner.  If you want reliability with DHCP there are ways
>>  to have multiple reliable DHCP servers on same link.
>>
>> But there is no way to achieve reliability between RA and DHCP. If
>>  the RA machine falls down the DHCP server can not provide same
>> information (not as of today, some parameters are still RA-only
>> whereas others are still DHCP-only).
>
> I don't quite follow there - but it's by design that the information
>  provided by RAs and DHCP are different, specifically that DHCP
> doesn't provide the prefix information.

YEs, and this design is wrong.  The design should allow for any
information to be in RA and any information to be in DHCP.

Reluctance to include some kind of information in RA, or in DHCP, has
little solid grounds.

> Wether you have one router & one DHCP server, or multiple routers and
> multiple DHCP servers - there is (of course) the issue of
> co-ordinating them so that if one of your internet connections goes
> down, you stop giving clients addresses in a prefix that's only
> usable via that connection. That's not really any different to the
> IPv4 world when using public addresses. But if the routers are
> redundant in that they both provide routing for the same prefix(es),
>  then I see no issue.

Yes, but coordination is easier when same kinds of databases (config
files) are used.

It's easier to coordinate between two dhcpd.conf files than between an
radvd.conf and and a dhcpd.conf contents.

> Perhaps you could clarify what the perceived issue is ?

The issue is that the principle of mandatory RA+DHCP (as opposed to
solely RA, or solely DHCP) leads to two different Routers in practice,
when a single one would have been sufficient.  A cost issue.

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr  8 23:11:06 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 390EB1B2D0E for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 9O71m3v0aBpq for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:11:03 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6E7D1B2D0D for <dhcwg@ietf.org>; Wed,  8 Apr 2015 23:11:02 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t396Axpn022844; Thu, 9 Apr 2015 08:10:59 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B2934203291; Thu,  9 Apr 2015 08:12:04 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A53CC203249; Thu,  9 Apr 2015 08:12:04 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t396AeSw008085; Thu, 9 Apr 2015 08:10:59 +0200
Message-ID: <552617E1.4040602@gmail.com>
Date: Thu, 09 Apr 2015 08:10:41 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk> <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk> <552554D4.5000304@gmail.com> <20150409.064656.74691916.sthaug@nethelp.no> <552611EE.1020803@gmail.com> <CAKD1Yr2zrSQSEm=uatcSaiV9JnG6uYvK8bRvgf-F0LX1a4+XAA@mail.gmail.com>
In-Reply-To: <CAKD1Yr2zrSQSEm=uatcSaiV9JnG6uYvK8bRvgf-F0LX1a4+XAA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/xshJc1X4puDB272j-UQkwi6bEVY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 06:11:05 -0000

Le 09/04/2015 07:50, Lorenzo Colitti a Ã©crit :
> On Thu, Apr 9, 2015 at 2:45 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>         Of course. And a sensible OS (e.g. FreeBSD) will indeed let you do
>         that.
>
>
>     Will the OS also add a plen /128 whenever sysadmin types "ifconfig add
>     address" w/o specifying a plen?
>
>
> Yes.

Ok, so the plen is needed anyways.

That's why a DHCP client invents there a 64, because it is needed. Were
it provided by DHCP protocol then the client would not need to invent it.

> Internally, the OS always represents addresses with prefix lengths.

Ok, so that's the way it should be. A prefix length is needed. Either it
is provided by sysadmin in CLI or by protocol. Otherwise the programmer
will always invent one (be it 64 or 128).

> This is a more general representation than just an address. An address
> of prefix length /128 is an address with no implicit route, an address
> of prefix length != /128 is an address without an implicit route.

('implicit' route? It's the same as 'host-based route' in your parlance?)

Whether the plen is 128 or 64, and whether it is told in cli or not, it
will always end as a routing table entry whenever an address is added.


>     And will it add an entry in the rt table for that /128 address?
>     (linux does both).
>
>
> Of course it does. That's necessary for things to work. It has to to
> add a route pointing at the loopback interface, otherwise it wouldn't
> know that if someone wants to send a packet to that address, it
> should send it on loopback, and if it receives a packet for that
> address, it knows to deliver that packet to UDP/TCP/... sockets.

Ok, so a plen is needed at least because the loopback iface is needed
for this 128 description. But loopback iface is not absolutely necessary
to talk locally to an address of self.

(remark if the sysadmin says add addr/64 then there is still a rt table
entry and there is no route to the loopback iface. And still one can
ping locally even though there is no /128 to the loopback interface
(send a packet to that address, receives for that address, deliver that
to UDP sockets).)

In all cases, a plen is needed.

Alex


From nobody Wed Apr  8 23:14:41 2015
Return-Path: <sthaug@nethelp.no>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 697C31B2A90 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 FJhZ8inID18t for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:14:38 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 3A5261B2A88 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 23:14:28 -0700 (PDT)
Received: (qmail 65894 invoked from network); 9 Apr 2015 06:14:28 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 9 Apr 2015 06:14:28 -0000
Date: Thu, 09 Apr 2015 08:14:27 +0200 (CEST)
Message-Id: <20150409.081427.74687401.sthaug@nethelp.no>
To: alexandru.petrescu@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <55254F6A.4020005@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.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/dhcwg/xJFD2ZR9sjrng4pU8hXwwTSRduk>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 06:14:40 -0000

> >> IPv6 address to a node's interface.  The RAs on that link will
> >> tell the node the prefixes in use on the link and routers to use
> >> to reach addresses off the link.
> >>
> >> What he said.
> >
> > Agreed ... precisely and concisely correct.
> 
> I disagree.  Almost entirely.
> 
> There must be a way for DHCP to work by itself, without assistance from RA.

As of today, there is no way to get DHCPv6 to work by itself, witout a
router (and RAs). I find this situation somewhat depressing - but it's
been like this for many years. Every attempt to change this has been
shot down.

So, as far as I can see, you cannot connect a bunch of computers to a
simple (unmanaged) Ethernet switch, configure one of them as a DHCPv6
server, and have the computers communicating using the DHCPv6 assigned
addresses:

- Addresses assigned by DHCPv6 are single addresses which say nothing
about reachability or on/off-link. There is no way to specify this using
DHCPv6.

- Furthermore, also frustrating DHCPv6 for address management, there is
no way to transmit the MAC addresses of the DHCPv6 clients to the DHCPv6
server, thus making any attempts to correlate DHCPv4 and DHCPv6 address
assignments difficult.

Yes, I am fully aware of RFC 6939 (Client Link-Layer Address Option in
DHCPv6) and of the DUID-LLT and DUID-LL formats. However,

- The RFC 6939 link layer address option is only used by DHCPv6 relay
agents.

- DHCPv6 servers are explicitly prohibited from "peeking inside" DUIDs
(even if some servers actually offer this functionality):

"Clients and servers MUST treat DUIDs as opaque values and MUST only
compare DUIDs for equality.  Clients and servers MUST NOT in any
other way interpret DUIDs." (RFC 3315 ch. 9)

Steinar Haug, AS 2116


From nobody Wed Apr  8 23:16:52 2015
Return-Path: <sthaug@nethelp.no>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E8D1B2A8F for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 bmZ_7bZNpLZh for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:16:49 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 2E5301B2A84 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 23:16:49 -0700 (PDT)
Received: (qmail 66001 invoked from network); 9 Apr 2015 06:16:48 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 9 Apr 2015 06:16:48 -0000
Date: Thu, 09 Apr 2015 08:16:48 +0200 (CEST)
Message-Id: <20150409.081648.41697299.sthaug@nethelp.no>
To: alexandru.petrescu@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <5525561C.2030002@gmail.com>
References: <DA5EB635-8D89-48A6-9320-50F5C8C67479@thehobsons.c! o.uk> <DA5EB635-8D89-48A6-9320-50F5C8C67479@thehobsons.co.uk> <5525561C.2030002@gmail.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/dhcwg/lnQdSwyhFoLMjZIss52L_I9oG0w>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 06:16:50 -0000

> But there is no way to achieve reliability between RA and DHCP.  If the
> RA machine falls down the DHCP server can not provide same information
> (not as of today, some parameters are still RA-only whereas others are
> still DHCP-only).

If you want reliability: Use redundant routers (both sending RAs) which
are also both DHCP relay agents.

Steinar Haug, AS 2116


From nobody Wed Apr  8 23:36:46 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280061A0025 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 IjpFKaTsVUs2 for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:36:43 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B8001A0022 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 23:36:42 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t396afFw030553 for <dhcwg@ietf.org>; Thu, 9 Apr 2015 08:36:41 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 40CD62032C7 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 08:37:46 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 392AE2030C2 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 08:37:46 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t396aeTg007971 for <dhcwg@ietf.org>; Thu, 9 Apr 2015 08:36:40 +0200
Message-ID: <55261DF8.3000302@gmail.com>
Date: Thu, 09 Apr 2015 08:36:40 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <alpine.DEB.2.02.1503270016290.20507@uplift.swm.pp.se> <201503271613.t2RGDdLn061234@givry.fdupont.fr> <CAJE_bqdxHcB0CNeV6wcz3oNk_Ooz3gNcv76aNqeqr=WXTGxL6w@mail.gmail.com> <CAKD1Yr2_UdT1mr_ETGnH=JTeVEprfQe6UicBK7D+AHqzYSd7gQ@mail.gmail.com> <A9E24C41-34D8-4BC5-9756-61EB528C0E83@thehobsons.co.uk> <1427968340.2822.53.camel@karl> <7B725F73-6270-47F7-9A9E-AD99F8B0DB05@thehobsons.co.uk> <269273A6-2FBD-4B16-BA1B-E9FAD8BA96E2@cisco.com> <D24147A1-956A-4F3A-B7FF-38D0112D5615@nominum.com> <5D192E07-F665-4388-AF84-4792B2C11FC1@cisco.com> <75B6FA9F576969419E42BECB86CB1B891683805F@xmb-rcd-x06.cisco.com> <5525045B.5050204@gmail.com> <CAKD1Yr3=ZGmxPsuOVf4++tp0Rh=ZTYK6ecc5Hy_HoGnc3OqXOA@mail.gmail.com> <5525432D.1020907@gmail.com> <C099CE1E-117D-429C-B859-04E35BC5DBA6@thehobsons.co.uk> <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk>
In-Reply-To: <89F420B8-8580-4AED-A4A4-36BBBB51ACE7@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/h8qz5DjyLlcUmR4T1o4KI7buMV8>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length - matching
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 06:36:45 -0000

Le 08/04/2015 18:00, Simon Hobson a écrit :
[...]
> As an example, if you wish to send a packet to 2001:DB8:1::1 and you
> are told (via an RA) that 2001:DB8:1::/48 is on-link, then do you
> have enough information to determine if the destination address is
> on-link ? Answer - yes you do. All you need to do is the simple
> logical operations we're familiar with from the IPv4 world - mask
> the address with the prefix length derived subnet mask, if the
> result matches then the address is "in" the prefix. Logical AND
> 2001:DB8::1 with ffff:ffff:ffff:: and you get 2001:DB8::, compare
> 2001:DB8:1:: with 2001:DB8:1:: and you'll find that it matches.

This is exact matching on a specified plen.  W/o a plen specified the
operation is not that straightforward.  So a plen is absolutely necessary.

"longest-match": when plen1 and plen2 are present (plen2 is longer), and
an address matches on plen2 on each of the prefixes - which prefix
should be selected as the one containing the address?  This is difficult
to say, since there is no spec.

In a sense, the prefix whose length is plen2 should be used, because
that is the "longest".  But in another sense, the prefix whose length is
plen1 also matches on the same number of bits.

The problem can be sensed when setting a prefix 2001:db8::/63 and a
2001:db8::/64 (two different prefixes, yet it is hard to tell which one
'contains' the address 2001:db8::1).

(for recall see the definition of rf4861:
>    longest prefix match
>                - the process of determining which prefix (if any) in a
>                  set of prefixes covers a target address.  A target
>                  address is covered by a prefix if all of the bits in
>                  the prefix match the left-most bits of the target
>                  address.  When multiple prefixes cover an address, the
>                  longest prefix is the one that matches.)



> Note that I didn't tell you what source address I was assuming -
> because it doesn't matter. It may or may not be in this prefix, or
> indeed any prefix advertised as being on-link for this interface. It
> could, for example, be 2001:DB8:1234::5678 which is *not* in the same
> prefix as the destination address.

I agree.

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr  8 23:43:05 2015
Return-Path: <sthaug@nethelp.no>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5F8F1A006F for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 Ii1Sfmdd8T4t for <dhcwg@ietfa.amsl.com>; Wed,  8 Apr 2015 23:43:02 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 367231A0069 for <dhcwg@ietf.org>; Wed,  8 Apr 2015 23:43:02 -0700 (PDT)
Received: (qmail 66585 invoked from network); 9 Apr 2015 06:43:01 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 9 Apr 2015 06:43:01 -0000
Date: Thu, 09 Apr 2015 08:43:01 +0200 (CEST)
Message-Id: <20150409.084301.71147261.sthaug@nethelp.no>
To: alexandru.petrescu@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <552611EE.1020803@gmail.com>
References: <552554D4.5000304@gmail.com> <20150409.064656.74691916.sthaug@nethelp.no> <552611EE.1020803@gmail.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/dhcwg/u83HUZrlYiUpe7gEQRBr4pnhwps>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 06:43:04 -0000

> Will the OS also add a plen /128 whenever sysadmin types "ifconfig add
> address" w/o specifying a plen?  And will it add an entry in the rt
> table for that /128 address?  (linux does both).

Checking on a couple of FreeBSD 10.1 servers in the lab here:

1. Adding an IPv6 address with no prefix specified (eg: ifconfig em0
inet6 2001:db8:1::1) results in an address with /64 prefix being
installed (and added to the routing table), and other hosts within the
same /64 are reachable.

2. Adding an IPv6 address with /128 prefix specified (eg: ifconfig em0
inet6 2001:db8:1::1/128) results in an address with /128 prefix being
installed (and added to the routing table). Obviously no other hosts
are reachable.

I'll let others argue whether the behavior in 1) is against the RFCs or
not. Speaking only for myself, I find it very sensible and practical.
Yes, I am aware of RFC 5942.

Steinar Haug, AS 2116


From nobody Thu Apr  9 00:21:14 2015
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C711C1A1AAD for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 00:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 t4jDcmf1xIF8 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 00:21:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 513C11A1AA5 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 00:21:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRE89897; Thu, 09 Apr 2015 07:21:10 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Apr 2015 08:21:09 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Thu, 9 Apr 2015 15:21:04 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHC minutes for IETF 92
Thread-Index: AdBylbrODNfwZygdTkOYiyQK50IGgQ==
Date: Thu, 9 Apr 2015 07:21:03 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B925F4FB723@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/PNuMFP42jGoF5a8M7C2MHFYUETo>
Cc: "dhc-chairs@tools.ietf.org" <dhc-chairs@tools.ietf.org>
Subject: [dhcwg] DHC minutes for IETF 92
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 07:21:12 -0000

SGksIGFsbCwNCg0KVGhlIG1pbnV0ZXMgZm9yIHRoZSBESEMgc2Vzc2lvbiBhdCBJRVRGOTIgaW4g
RGFsbGFzIGNhbiBiZSBmb3VuZCBhdDoNCg0KaHR0cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVkaW5n
cy85Mi9taW51dGVzL21pbnV0ZXMtOTItZGhjDQoNClBsZWFzZSBzZW5kIGFueSBjb3JyZWN0aW9u
cyB0byB0aGUgREhDIGNoYWlycyBvciBzZWNyZXRhcnkuDQoNCkJlc3QgcmVnYXJkcywNCg0KU2hl
bmcNCg==


From nobody Thu Apr  9 00:55:01 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5274F1A874C for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 00:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 SUFW7b9puqlg for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 00:54:57 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id F00101A8710 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 00:54:56 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 8BA721BC3E for <dhcwg@ietf.org>; Thu,  9 Apr 2015 07:54:28 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <20150409.081427.74687401.sthaug@nethelp.no>
Date: Thu, 9 Apr 2015 08:54:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/cjnSO1V9Ss_NfUeG3juo2fX-wQg>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 07:55:00 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> In the above example the sysadmin does not need to provide a prefix =
but
> the stack (linux) will add a /128 because so the programmer wants.

As I read things, a big part of your argument is "on ${OS of choice} =
prefixes are required and routes automatic, therefore the standard is =
wrong to say otherwise". It reminds me of certain other areas in the IT =
world where vendors with vested interests effectively tell the standards =
body "we've implemented this, make your standard fit"

FWIW, I can see the other side, but I'm convinced by the argument that =
says an address is separate from prefixes declared as on-link and =
routes.
We can work around the requirement for a prefix by specifying /128 - =
IIRC the argument was how to word this to say it can be done, but it's =
wrong to have to do it, ie say it without appearing to condone it's use =
and so encourage people to do implementations that require a prefix.
Using /128 also works around the other implementation issue - by =
avoiding the automatic addition of a route for the prefix.



sthaug@nethelp.no wrote:

> As of today, there is no way to get DHCPv6 to work by itself, witout a
> router (and RAs). I find this situation somewhat depressing - but it's
> been like this for many years. Every attempt to change this has been
> shot down.
>=20
> So, as far as I can see, you cannot connect a bunch of computers to a
> simple (unmanaged) Ethernet switch, configure one of them as a DHCPv6
> server, and have the computers communicating using the DHCPv6 assigned
> addresses:
>=20
> - Addresses assigned by DHCPv6 are single addresses which say nothing
> about reachability or on/off-link. There is no way to specify this =
using
> DHCPv6.

FWIW I would support there being an option to send the list of prefixes =
- note that this is different from specifying a prefix length for an =
address. AIUI a large part of the reason for separating the functions is =
to do with large organisation where different groups handle address =
management (ie DHCP) and another group handles routing - with an =
inference being that the two groups exist in isolation. IME (only in =
small/medium businesses) is of doing both roles myself - and even where =
they are separate groups, neither can operate in isolation from the =
others (no good assigning addresses from a prefix that isn't routed to =
that network !).

> - Furthermore, also frustrating DHCPv6 for address management, there =
is
> no way to transmit the MAC addresses of the DHCPv6 clients to the =
DHCPv6
> server, thus making any attempts to correlate DHCPv4 and DHCPv6 =
address
> assignments difficult.

It's not just IPv4-IPv6 correlation. As I've expressed before, until =
vendors generate a DUID at the factory, store it in non-volatile memory =
in the device, print it on a barcode on the side of the box, and all =
OSs/DHCP clients use it - then it's both less useful, and less stable =
than a MAC address as an identifier.
I see the need for a system wide UID, but I don't see the support =
appearing for it.

As an aside, I once worked in a place with Apollo Domain systems. In =
those, the system identity was so closely tied to the network hardware =
address that replacing a NIC or moving a disk between machines involved =
a routine to update the file id for every file on the system. At least =
this is how I vaguely recall it being told to me.



On 9 Apr 2015, at 07:36, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:

> Le 08/04/2015 18:00, Simon Hobson a =E9crit :
> [...]
>> As an example, if you wish to send a packet to 2001:DB8:1::1 and you
>> are told (via an RA) that 2001:DB8:1::/48 is on-link, then do you
>> have enough information to determine if the destination address is
>> on-link ? Answer - yes you do. All you need to do is the simple
>> logical operations we're familiar with from the IPv4 world - mask
>> the address with the prefix length derived subnet mask, if the
>> result matches then the address is "in" the prefix. Logical AND
>> 2001:DB8::1 with ffff:ffff:ffff:: and you get 2001:DB8::, compare
>> 2001:DB8:1:: with 2001:DB8:1:: and you'll find that it matches.
>=20
> This is exact matching on a specified plen.  W/o a plen specified the
> operation is not that straightforward.  So a plen is absolutely =
necessary.

I'm struggling to see if you genuinely are missing the point or =
trolling.
Yes, a prefix length is necessary **FOR THE DESTINATION**, it is not =
necessary for our own address. No-one is talking about not having a =
prefix length for prefixes we are told are attached to the link (ie =
on-link).


> "longest-match": when plen1 and plen2 are present (plen2 is longer), =
and
> an address matches on plen2 on each of the prefixes - which prefix
> should be selected as the one containing the address?  This is =
difficult
> to say, since there is no spec.

Assuming for one moment that there are no duplicate/overlapping prefixes =
across different interfaces, then it doesn't actually matter one jot =
whether you do longest wins, shortest wins, first match found wins, or =
even random. If the destination address matches *ANY* on-link prefix =
then the node is directly reachable via that link. The question we are =
answering is "can we directly reach that node", and that is "yes" if the =
node address is in any prefix on the link - the answer isn't a specific =
prefix, just a yes or no.

The only case I can think of where this breaks down is if there is a =
broken network config - with multiple networks with overlapping IP =
ranges. In that case, you may find that the destination address matches =
one or more on-link prefixes on more than one link. IMO that is broken =
(addresses not globally unique) and I see no reason not to leave it to =
the implementer to do what they want - whether that's longest match =
first, shortest match first, or something else.
In theory, if a node is reachable via either link, then it shouldn't =
matter which interface is used - one option might be to prefer higher =
performance (eg gigabit wired ethernet) over lower performance (eg =
wifi). An obvious situation this can arise is when connected to the same =
LAN via wired ethernet and wifi.
If there are overlapping prefixes on multiple networks, but a node is =
only reachable via one of them, then that's a recipe for bigger problems =
and with the abundance of IPv6 addresses should be easily avoided.



I'll finish by tossing in something to think about. You complain a lot =
about the complication of doing multiple prefix matches, which wins, =
etc.
If we go down the route of saying every address has an associated =
prefix, then if we add (say) 20 addresses to an interface* then we've =
added 20 prefixes. Now, instead of matching against the one (or small =
number) of on-link prefixes explicitly configured, you have 20 prefixes =
to test - 19 tests are redundant as they should all give the same =
answer.
The alternative is that when adding addresses, you have to figure out if =
there is already a prefix in the table and not add duplicates; and when =
deleting an address, the harder task of working out if this is the last =
address with that prefix and only deleting the prefix if it is. If you =
do that logic, then you are implicitly doing what you appear to be =
arguing against - treating the addresses and prefixes (routing table =
entries) as separate entities.

* I see multiple addresses becoming a lot more common. I've been in IT =
long enough to remember when each web site needed it's own address, and =
using browsers without the new fangled host header support. These days, =
there are still browsers that don't fully support multiple SSL enabled =
sites on one IP. The extensions for both of these are in effect =
workarounds to avoid using multiple addresses - there are arguments** =
for going back to multiple addresses with the abundance of IPv6.

** Most of these relate to identity and accountability. Eg, when a site =
sends out an email, if each site uses a different address then there's =
no issue as to who sent it, no problems with being blacklisted because =
"a neighbour" on the same server sent spam, no problems being =
blacklisted because you don't have the right reverse DNS, etc, etc.


From nobody Thu Apr  9 02:10:54 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 245DF1B29CD for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 02:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 A0AOL-WAyN7T for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 02:10:50 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81D641B29C5 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 02:10:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t399Altv021674 for <dhcwg@ietf.org>; Thu, 9 Apr 2015 11:10:47 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9E10B20357B for <dhcwg@ietf.org>; Thu,  9 Apr 2015 11:11:52 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9612C203571 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 11:11:52 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t399AMJh016068 for <dhcwg@ietf.org>; Thu, 9 Apr 2015 11:10:47 +0200
Message-ID: <552641FF.2070202@gmail.com>
Date: Thu, 09 Apr 2015 11:10:23 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk>
In-Reply-To: <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/79O1gN7bACJr5dg0P0I0F5hDk6k>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 09:10:53 -0000

Le 09/04/2015 09:54, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>> In the above example the sysadmin does not need to provide a
>> prefix but the stack (linux) will add a /128 because so the
>> programmer wants.
>
> As I read things, a big part of your argument is "on ${OS of choice}
> prefixes are required and routes automatic, therefore the standard is
> wrong to say otherwise".

${OS} bsd and linux contain the stacks which are fundamental of pretty
much everything out there.

> It reminds me of certain other areas in the IT world where vendors
> with vested interests effectively tell the standards body "we've
> implemented this, make your standard fit"

I am not a vendor with vested interests.  I am writing after years of
experience with these things.

> FWIW, I can see the other side, but I'm convinced by the argument
> that says an address is separate from prefixes declared as on-link
> and routes.

That is in specifications, yes.

> We can work around the requirement for a prefix by specifying /128 -
> IIRC the argument was how to word this to say it can be done, but
> it's wrong to have to do it, ie say it without appearing to condone
> it's use and so encourage people to do implementations that require
> a prefix. Using /128 also works around the other implementation issue
> - by avoiding the automatic addition of a route for the prefix.

My argument is the following:
- architecturally an address has no prefixl ength
- implementations need prefix length
- some implementations default to 64 others to 128
- prefixlen should be delivered by DHCP too
- recommending 128 as default preflen is not necessary

> sthaug@nethelp.no wrote:
>
>> As of today, there is no way to get DHCPv6 to work by itself,
>> witout a router (and RAs). I find this situation somewhat
>> depressing - but it's been like this for many years. Every attempt
>> to change this has been shot down.
>>
>> So, as far as I can see, you cannot connect a bunch of computers
>> to a simple (unmanaged) Ethernet switch, configure one of them as
>> a DHCPv6 server, and have the computers communicating using the
>> DHCPv6 assigned addresses:
>>
>> - Addresses assigned by DHCPv6 are single addresses which say
>> nothing about reachability or on/off-link. There is no way to
>> specify this using DHCPv6.
>
> FWIW I would support there being an option to send the list of
> prefixes - note that this is different from specifying a prefix
> length for an address.

Ok.

We may specify it as a triplet [prefix/len; id; address] so that a
Client is told by the server which address is contained by which prefix,
so it does not have to think longest-match.  A quick manner to encode
this triplet itno a message is to use an address and a prefixlen only
(many protocols do that).

> AIUI a large part of the reason for separating the functions is to do
> with large organisation where different groups handle address
> management (ie DHCP) and another group handles routing - with an
> inference being that the two groups exist in isolation. IME (only in
>  small/medium businesses) is of doing both roles myself - and even
> where they are separate groups, neither can operate in isolation from
> the others (no good assigning addresses from a prefix that isn't
> routed to that network !).

I agree.

>> - Furthermore, also frustrating DHCPv6 for address management,
>> there is no way to transmit the MAC addresses of the DHCPv6
>> clients to the DHCPv6 server, thus making any attempts to correlate
>> DHCPv4 and DHCPv6 address assignments difficult.
>
> It's not just IPv4-IPv6 correlation. As I've expressed before, until
> vendors generate a DUID at the factory, store it in non-volatile
> memory in the device, print it on a barcode on the side of the box,
> and all OSs/DHCP clients use it - then it's both less useful, and
> less stable than a MAC address as an identifier. I see the need for
> a system wide UID, but I don't see the support appearing for it.
>
> As an aside, I once worked in a place with Apollo Domain systems. In
> those, the system identity was so closely tied to the network
> hardware address that replacing a NIC or moving a disk between
> machines involved a routine to update the file id for every file on
> the system. At least this is how I vaguely recall it being told to
> me.
>
>
>
> On 9 Apr 2015, at 07:36, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>
>> Le 08/04/2015 18:00, Simon Hobson a écrit : [...]
>>> As an example, if you wish to send a packet to 2001:DB8:1::1 and
>>> you are told (via an RA) that 2001:DB8:1::/48 is on-link, then do
>>> you have enough information to determine if the destination
>>> address is on-link ? Answer - yes you do. All you need to do is
>>> the simple logical operations we're familiar with from the IPv4
>>> world - mask the address with the prefix length derived subnet
>>> mask, if the result matches then the address is "in" the prefix.
>>> Logical AND 2001:DB8::1 with ffff:ffff:ffff:: and you get
>>> 2001:DB8::, compare 2001:DB8:1:: with 2001:DB8:1:: and you'll
>>> find that it matches.
>>
>> This is exact matching on a specified plen.  W/o a plen specified
>> the operation is not that straightforward.  So a plen is
>> absolutely necessary.
>
> I'm struggling to see if you genuinely are missing the point or
> trolling.

Not trolling.

> Yes, a prefix length is necessary **FOR THE DESTINATION**, it is not
> necessary for our own address. No-one is talking about not having a
> prefix length for prefixes we are told are attached to the link (ie
> on-link).

Look - whenever adding an address on an interface you have to use a
prefixlen.

If you add an address on an interface manually then the system invents
an arbitrary one for you (64 or 128); if by using SLAAC you get the plen
from the RA.  If using DHCP you still get it from RA.  It all depends on
this RA.  This is not normal.

>> "longest-match": when plen1 and plen2 are present (plen2 is
>> longer), and an address matches on plen2 on each of the prefixes -
>> which prefix should be selected as the one containing the address?
>> This is difficult to say, since there is no spec.
>
> Assuming for one moment that there are no duplicate/overlapping
> prefixes across different interfaces, then it doesn't actually
> matter one jot whether you do longest wins, shortest wins, first
> match found wins, or even random. If the destination address matches
> *ANY* on-link prefix then the node is directly reachable via that
> link. The question we are answering is "can we directly reach that
> node", and that is "yes" if the node address is in any prefix on the
> link - the answer isn't a specific prefix, just a yes or no.
>
> The only case I can think of where this breaks down is if there is a
> broken network config - with multiple networks with overlapping IP
> ranges. In that case, you may find that the destination address
> matches one or more on-link prefixes on more than one link. IMO that
> is broken (addresses not globally unique) and I see no reason not to
> leave it to the implementer to do what they want - whether that's
> longest match first, shortest match first, or something else. In
> theory, if a node is reachable via either link, then it shouldn't
> matter which interface is used - one option might be to prefer
> higher performance (eg gigabit wired ethernet) over lower performance
> (eg wifi). An obvious situation this can arise is when connected to
> the same LAN via wired ethernet and wifi. If there are overlapping
> prefixes on multiple networks, but a node is only reachable via one
> of them, then that's a recipe for bigger problems and with the
> abundance of IPv6 addresses should be easily avoided.

I read your text.  I understand it somehow.  We can see  later.

Alex

>
>
>
> I'll finish by tossing in something to think about. You complain a
> lot about the complication of doing multiple prefix matches, which
> wins, etc. If we go down the route of saying every address has an
> associated prefix, then if we add (say) 20 addresses to an
> interface* then we've added 20 prefixes. Now, instead of matching
> against the one (or small number) of on-link prefixes explicitly
> configured, you have 20 prefixes to test - 19 tests are redundant as
> they should all give the same answer. The alternative is that when
> adding addresses, you have to figure out if there is already a prefix
> in the table and not add duplicates; and when deleting an address,
> the harder task of working out if this is the last address with that
> prefix and only deleting the prefix if it is. If you do that logic,
> then you are implicitly doing what you appear to be arguing against -
> treating the addresses and prefixes (routing table entries) as
> separate entities.
>
> * I see multiple addresses becoming a lot more common. I've been in
> IT long enough to remember when each web site needed it's own
> address, and using browsers without the new fangled host header
> support. These days, there are still browsers that don't fully
> support multiple SSL enabled sites on one IP. The extensions for
> both of these are in effect workarounds to avoid using multiple
> addresses - there are arguments** for going back to multiple
> addresses with the abundance of IPv6.
>
> ** Most of these relate to identity and accountability. Eg, when a
> site sends out an email, if each site uses a different address then
> there's no issue as to who sent it, no problems with being
> blacklisted because "a neighbour" on the same server sent spam, no
> problems being blacklisted because you don't have the right reverse
> DNS, etc, etc.
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Thu Apr  9 03:18:25 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 322951B2DD7 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 03:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 GzV34O3UsBK9 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 03:18:23 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20D9D1B2DD4 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 03:18:23 -0700 (PDT)
Received: by igbqf9 with SMTP id qf9so60698224igb.1 for <dhcwg@ietf.org>; Thu, 09 Apr 2015 03:18:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VlS8yP5r3GEorD34eu9QPwfJ/VNUMktAdgWMXkQnafs=; b=SZ92F50cfp5jAD0yYcMwkn6Y4oFz43ZH/OCpSugk+bG0wpUa59B3Y3C6YAZGhus6Z1 fhZTBUA1rW9mUsNVqR7ugKbS25HEQj4+ArKd/jOifKIP0cH7ZZF3lgx5QnwTf0wYkAtk M5k+aDlTjGGFIBNr1JuWQqcnIrVtS5AKQznujXAdCqnZ4mcx6WYivFPxUItjGDVJ9wwO XzfZN0NbaZh1LS7rlKMF5ioOF7L3WkbT9g5q9noDLuEzfNEwBAcJ/80jpKGlzgRw195T B9S7uLH1miiibci7816+3z4CGqU2nwXF3aJLOjzxKGIyHkIBkPreOalezp+4glLnB1+k Mzvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=VlS8yP5r3GEorD34eu9QPwfJ/VNUMktAdgWMXkQnafs=; b=L7dTmiY1LqKXQGa3N3lIMS6q9VVdviADvsvyZfCCUK87ghRe7e4egpZtPKYy6d4hmz sDFxbKZDfpqLudzdK6wiek64JGjHwtcVa1ZKPTDzsMmoCxuHc1GQWmINxF+HWLPlnsVW WLwKGs59h1JVwqZHawrwpyNvf2vi77t5SpYmPE6gj+k6JUmCqywFWLPNP2drCq9XJ3QU xeNfi1QvUUfbcL2thpzQd9UPHIn91cw1XYO4O29utkOCNbntXPGISYxRi4ZqAL8sAc6z TA3WCJGDUyHYghLQnVsygyte0gkUVtGboQm6vgwDQ6MS6OFwVQyl6XWwXOwqtE7zMmNT NWlw==
X-Gm-Message-State: ALoCoQmKWUvruIYXtv9SlPC07dkaTKxU1b3IxVgjIM9AyqsA8K0bB2hcldpqD05voT+17UID3lSi
X-Received: by 10.107.46.155 with SMTP id u27mr44350590iou.87.1428574702618; Thu, 09 Apr 2015 03:18:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Thu, 9 Apr 2015 03:18:01 -0700 (PDT)
In-Reply-To: <20150409.084301.71147261.sthaug@nethelp.no>
References: <552554D4.5000304@gmail.com> <20150409.064656.74691916.sthaug@nethelp.no> <552611EE.1020803@gmail.com> <20150409.084301.71147261.sthaug@nethelp.no>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Apr 2015 19:18:01 +0900
Message-ID: <CAKD1Yr1dCD-yC7Ddt7pypOcgHGHsKA6+KO2H4zFWsh6JBFBc-A@mail.gmail.com>
To: sthaug@nethelp.no
Content-Type: multipart/alternative; boundary=001a113ac5b6af76bc051347f722
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jyLYxyf7YbyeCFw3G5nMC8U2VhI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Alexandre Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 10:18:24 -0000

--001a113ac5b6af76bc051347f722
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 9, 2015 at 3:43 PM, <sthaug@nethelp.no> wrote:

> 1. Adding an IPv6 address with no prefix specified (eg: ifconfig em0
> inet6 2001:db8:1::1) results in an address with /64 prefix being
> installed (and added to the routing table), and other hosts within the
> same /64 are reachable.
> [...]
> I'll let others argue whether the behavior in 1) is against the RFCs or
> not.


Actually, it's so clearly a violation of RFC 5942 section 4 that there's no
argument to be had. :-)

   1.  The assignment of an IPv6 address -- whether through IPv6
       stateless address autoconfiguration [RFC4862], DHCPv6 [RFC3315],
       or manual configuration -- MUST NOT implicitly cause a prefix
       derived from that address to be treated as on-link and added to
       the Prefix List.


> Speaking only for myself, I find it very sensible and practical.
>

Whether you find it sensible and practical does not change the fact that it
is incorrect.

--001a113ac5b6af76bc051347f722
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 9, 2015 at 3:43 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:sthaug=
@nethelp.no" target=3D"_blank">sthaug@nethelp.no</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;pa=
dding-left:1ex">1. Adding an IPv6 address with no prefix specified (eg: ifc=
onfig em0<br>
inet6 2001:db8:1::1) results in an address with /64 prefix being<br>
installed (and added to the routing table), and other hosts within the<br>
same /64 are reachable.<br>
[...]<br>I&#39;ll let others argue whether the behavior in 1) is against th=
e RFCs or<br>
not.</blockquote><div><br></div><div><div>Actually, it&#39;s so clearly a v=
iolation=C2=A0of RFC 5942 section 4 that there&#39;s no argument to be had.=
 :-)</div><div><br></div><div>=C2=A0 =C2=A01.=C2=A0 The assignment of an IP=
v6 address -- whether through IPv6<br></div></div><div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0stateless address autoconfiguration [RFC4862], DHCPv6 [RFC3315=
],</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0or manual configuration -- MUST NOT=
 implicitly cause a prefix</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0derived fro=
m that address to be treated as on-link and added to</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0the Prefix List.</div></div><div>=C2=A0<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-widt=
h:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-le=
ft:1ex"> Speaking only for myself, I find it very sensible and practical.<b=
r></blockquote><div><br></div><div>Whether you find it sensible and practic=
al does not change the fact that it is incorrect.</div></div></div></div>

--001a113ac5b6af76bc051347f722--


From nobody Thu Apr  9 03:21:45 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7C131B2DF8 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 03:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 k_5hLNt0GaZL for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 03:21:42 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 473CB1B2DF7 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 03:21:42 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 09ED21BC3E for <dhcwg@ietf.org>; Thu,  9 Apr 2015 10:21:38 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <552641FF.2070202@gmail.com>
Date: Thu, 9 Apr 2015 11:21:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/E_Z_bzqqy1tbl44VVE-9ZI-7ugU>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 10:21:44 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

<snip>
> Look - whenever adding an address on an interface you have to use a
> prefixlen.

Then you are forever doomed to not understand IPv6 and be complaining =
that "it's wrong".
Because when adding an address you do **NOT** need to specify a prefix =
length - when adding an address **on an incorrect implementation** you =
need to provide one **only for the convenience of that implementation**, =
because it is **NOT** required in any way whatsoever for correct =
operation of IPv6.

Until you can separate what is actually needed, vs what certain =
implementations need, then you will never "get it". It did take me a =
while, and some explaining from others on this list before I "got it" - =
until then I thought like you and worked on the basis that what I was =
using (ie implementations in Linux) was "right".

I can fully see why the implementations are as they are - as Brian =
Haberman pointed out yesterday, people would have been rushing to get =
something working, and refactoring existing code is by far the easiest =
way to do that. Getting from where we are, to standards compliant will =
be an interesting challenge - deprecating certain things and persuading =
everyone to update everything that uses the old interface to update =
their software. The pragmatist in me thinks that perhaps it's not really =
necessary to rebuild all the code to not use prefix lengths with =
addresses - just default to /128 prefix lengths and throw out a warning =
message if anything different is set might be enough.


> If you add an address on an interface manually then the system invents
> an arbitrary one for you (64 or 128); if by using SLAAC you get the =
plen
> from the RA.  If using DHCP you still get it from RA.  It all depends =
on
> this RA.  This is not normal.

In the IPv6 world it **IS** normal. IPv6 =3D/=3D IPv4. You may have many =
years working with such systems, but that seems to be part of your =
problem - a reluctance or inability to accept that IPv6 is different to =
IPv4 by design. We can argue about whether those design decisions are =
right or not, but that is the design.

Your position indicates that you are still stuck in IPv4 thinking where =
"IP address plus subnet mask =3D=3D reachability information for =
neighbours". That's only true for certain network technologies (such as =
ethernet), and it's only true for single subnets.

There are, as pointed out in some of the RFCs/drafts you've read, =
networks where having an IP address in the same subnet/prefix as the =
destination does not make that destination directly reachable. In those =
cases, using "IP+subnet/prefix =3D=3D reachability information" breaks.

In the IPv6 world, it is considered "normal" for there to be multiple =
prefixes and for hosts to have multiple addresses. Having a single =
prefix is merely a case of that multiple being one". Except in the =
special case of that multiple being one, using "IP+subnet/prefix =3D=3D =
reachability information" breaks.


I'll give a further example of how I understand things are supposed to =
work - and why "old style" thinking doesn't work.

Lets say we have two (or more) internet providers, and unless we're big =
enough to go and get our own AS number etc, then we'll get different =
prefixes from each. In the normal case, each host is likely to be =
multihomed - having an address from each prefix, and we'll publish AAAA =
records for each address.
Each provider has a router, and each router provides an RA for the =
prefix(es) it serves. This is important - as I think you are assuming =
that all routers send the same list of prefixes. Each node aggregates =
the RA supplied prefixes to build it's prefix table.
Using ${some process}, each node will work out which traffic to send via =
each router (and which source address to use) - this is something I'm =
not 100% comfortable with, having been used to having routers make that =
decision.

Now lets say one provider goes offline. The router detects this (or is =
offline itself) and so RAs for the prefix(es) from that provider stop. =
When caches time out, each node will remove those prefixes from it's =
prefix table. Thus when a provider goes offline, the nodes using any =
prefix(es) from that provider will stop doing so - and in addition, =
nodes will also stop treating those prefixes as local.

So even though a DHCP server may still be handing out addresses in that =
prefix, or the hosts may be manually configured with them, they won't =
actually be used. Everything should fall back to using other addresses =
published for services/servers.

On the other hand, if you hand out **A** list of prefixes with DHCP - =
when a provider goes down, your network becomes "randomly broken" as =
nodes try to use addresses that are no longer valid. You have to detect =
the failed service, and update the DHCP configuration, and wait (perhaps =
days) for nodes to renew and get the update.
Alternatively, if DHCP doesn't do it, you have to manually configure =
each node to know about all the prefixes - and manually update them if a =
prefix is no longer valid.
Or you potentially have locally reachable neighbours communicating via =
two external connections if they are in different prefixes.

I hope it's obvious that for a situation like this, the separation of =
address assignment and routing information is "a good thing". It lets =
the routing dynamically update, without having to build "interesting" =
couplings between different services, and also operating quickly without =
the instability and risk from short DHCP lease times.

It doesn't address the issue of updating the outward facing DNS to =
remove the offline prefix - but that would be a problem no matter how =
the network addressing/routing was done. Between the service going down, =
and the DNS updates going out, clients will experience delays if they =
happen to try a "dead" address first before falling back and trying =
another address (they'll get a list of AAAA records, not just one) - but =
they will connect.


From nobody Thu Apr  9 03:35:50 2015
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04E571B2E1B for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 03:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 mGKDvBGbfr0o for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 03:35:47 -0700 (PDT)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B521B1B2E1A for <dhcwg@ietf.org>; Thu,  9 Apr 2015 03:35:46 -0700 (PDT)
Received: by lbbuc2 with SMTP id uc2so84222128lbb.2 for <dhcwg@ietf.org>; Thu, 09 Apr 2015 03:35:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=r1yGozPMjtDaYrkzfeA5n3+2JftBdU8lhRr6fAU1unQ=; b=X1LS0AS5DqswIoiX5rNPbfCKrD0ZpGTZhSygICIVbPyiuEeVI8lOlsBpnVpoodFUXl I62/ezRiwqk78AwpwLrUQeZGuTxNpGqhi9KF0ro7ymGgoVSfr6UbPdWfjGfwARX4CmyF wcW8sgdRIzuJgL6XTdH+CR5J9JBaWmaiCZI9mDNp9NgOijQ+PR2c4rQ/KhwQKNSV2pIe 1dSvgqTlmC+yWgtEYrQKYFeYmOsSA77voSqLbK61RTaGNLsV2MDD4ixfiNJzD5cvfwue tD1ggyxNZ2Qr8OG258eJXiRdMv3nWG7CFOIDE9YfzFOZfaQ8IrZVx6KuvRav6UpJVexe +7dQ==
X-Received: by 10.112.133.225 with SMTP id pf1mr27697833lbb.33.1428575745062;  Thu, 09 Apr 2015 03:35:45 -0700 (PDT)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id o7sm794965lbp.37.2015.04.09.03.35.43 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Apr 2015 03:35:43 -0700 (PDT)
Message-ID: <552655F9.2060403@gmail.com>
Date: Thu, 09 Apr 2015 12:35:37 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
References: <20150407211107.28341.70219.idtracker@ietfa.amsl.com>
In-Reply-To: <20150407211107.28341.70219.idtracker@ietfa.amsl.com>
X-TagToolbar-Keys: D20150409123537093
X-Forwarded-Message-Id: <20150407211107.28341.70219.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/q3KHzqgdRCDNFNmawtl_5HIZAB4>
Subject: [dhcwg] Adoption call request for draft-huitema-dhc-anonymity-profile-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 10:35:49 -0000

Hi!

This updated version is a merge of draft-huitema-anonymity-profile-01 and
draft-mrugalski-dhc-dhcpv6-privacy-mitigation-00. As discussed in Dallas,
an adoption call is the next logical step for this work.

<co-chair hat off>
As one of the co-authors, I'd like to request the chairs to start an adoption call.

<co-chair hat put back on>
As I'm a co-author, Bernie will have to handle this adoption call and
determine consensus on his own.

Tomek

-------- Forwarded Message --------
Subject: New Version Notification for draft-huitema-dhc-anonymity-profile-02.txt
Date: Tue, 07 Apr 2015 14:11:07 -0700
From: internet-drafts@ietf.org
To: Christian Huitema <huitema@microsoft.com>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>, Christian Huitema <huitema@microsoft.com>


A new version of I-D, draft-huitema-dhc-anonymity-profile-02.txt
has been successfully submitted by Christian Huitema and posted to the
IETF repository.

Name:		draft-huitema-dhc-anonymity-profile
Revision:	02
Title:		Anonymity profile for DHCP clients
Document date:	2015-04-07
Group:		Individual Submission
Pages:		19
URL:            http://www.ietf.org/internet-drafts/draft-huitema-dhc-anonymity-profile-02.txt
Status:         https://datatracker.ietf.org/doc/draft-huitema-dhc-anonymity-profile/
Htmlized:       http://tools.ietf.org/html/draft-huitema-dhc-anonymity-profile-02
Diff:           http://www.ietf.org/rfcdiff?url2=draft-huitema-dhc-anonymity-profile-02

Abstract:
   Some DHCP options carry unique identifiers.  These identifiers can
   enable device tracking even if the device administrator takes care of
   randomizing other potential identifications like link-layer addresses
   or IPv6 addresses.  The anonymity profile is designed for clients
   that wish to remain anonymous to the visited network.  The profile
   provides guidelines on the composition of DHCP or DHCPv6 requests,
   designed to minimize disclosure of identifying information.  This
   draft updates RFC4361.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat




From nobody Thu Apr  9 04:23:53 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 198021B377A for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 04:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 kBn9hGjMut5J for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 04:23:49 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A0701B3773 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 04:23:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t39BNlsp013452 for <dhcwg@ietf.org>; Thu, 9 Apr 2015 13:23:47 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AA228206B30 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 13:24:52 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A1D8A204E34 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 13:24:52 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t39BNLtQ030658 for <dhcwg@ietf.org>; Thu, 9 Apr 2015 13:23:47 +0200
Message-ID: <5526612A.7000502@gmail.com>
Date: Thu, 09 Apr 2015 13:23:22 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk>
In-Reply-To: <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/o0pa9SHRSXD-LoL7FGz4JBaea7s>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 11:23:52 -0000

Le 09/04/2015 12:21, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
> <snip>
>> Look - whenever adding an address on an interface you have to use a
>> prefixlen.
>
> Then you are forever doomed to not understand IPv6 and be
> complaining that "it's wrong". Because when adding an address you do
> **NOT** need to specify a prefix length - when adding an address **on
> an incorrect implementation** you need to provide one **only for the
> convenience of that implementation**, because it is **NOT** required
> in any way whatsoever for correct operation of IPv6.

Ok.

Is '128' the correct prefixlen to add to an address when putting it on
an interface?  Or is 64 the correct prefixlen?

Alex

>
> Until you can separate what is actually needed, vs what certain
> implementations need, then you will never "get it". It did take me a
> while, and some explaining from others on this list before I "got
> it" - until then I thought like you and worked on the basis that what
> I was using (ie implementations in Linux) was "right".
>
> I can fully see why the implementations are as they are - as Brian
> Haberman pointed out yesterday, people would have been rushing to
> get something working, and refactoring existing code is by far the
> easiest way to do that. Getting from where we are, to standards
> compliant will be an interesting challenge - deprecating certain
> things and persuading everyone to update everything that uses the
> old interface to update their software. The pragmatist in me thinks
> that perhaps it's not really necessary to rebuild all the code to not
> use prefix lengths with addresses - just default to /128 prefix
> lengths and throw out a warning message if anything different is set
> might be enough.
>
>
>> If you add an address on an interface manually then the system
>> invents an arbitrary one for you (64 or 128); if by using SLAAC
>> you get the plen from the RA.  If using DHCP you still get it from
>> RA. It all depends on this RA.  This is not normal.
>
> In the IPv6 world it **IS** normal. IPv6 =/= IPv4. You may have many
> years working with such systems, but that seems to be part of your
> problem - a reluctance or inability to accept that IPv6 is different
> to IPv4 by design. We can argue about whether those design decisions
> are right or not, but that is the design.
>
> Your position indicates that you are still stuck in IPv4 thinking
> where "IP address plus subnet mask == reachability information for
> neighbours". That's only true for certain network technologies (such
> as ethernet), and it's only true for single subnets.
>
> There are, as pointed out in some of the RFCs/drafts you've read,
> networks where having an IP address in the same subnet/prefix as the
> destination does not make that destination directly reachable. In
> those cases, using "IP+subnet/prefix == reachability information"
> breaks.
>
> In the IPv6 world, it is considered "normal" for there to be
> multiple prefixes and for hosts to have multiple addresses. Having a
> single prefix is merely a case of that multiple being one". Except in
> the special case of that multiple being one, using "IP+subnet/prefix
> == reachability information" breaks.
>
>
> I'll give a further example of how I understand things are supposed
> to work - and why "old style" thinking doesn't work.
>
> Lets say we have two (or more) internet providers, and unless we're
> big enough to go and get our own AS number etc, then we'll get
> different prefixes from each. In the normal case, each host is
> likely to be multihomed - having an address from each prefix, and
> we'll publish AAAA records for each address. Each provider has a
> router, and each router provides an RA for the prefix(es) it serves.
> This is important - as I think you are assuming that all routers send
> the same list of prefixes. Each node aggregates the RA supplied
> prefixes to build it's prefix table. Using ${some process}, each node
> will work out which traffic to send via each router (and which
> source address to use) - this is something I'm not 100% comfortable
> with, having been used to having routers make that decision.
>
> Now lets say one provider goes offline. The router detects this (or
> is offline itself) and so RAs for the prefix(es) from that provider
> stop. When caches time out, each node will remove those prefixes
> from it's prefix table. Thus when a provider goes offline, the nodes
> using any prefix(es) from that provider will stop doing so - and in
> addition, nodes will also stop treating those prefixes as local.
>
> So even though a DHCP server may still be handing out addresses in
> that prefix, or the hosts may be manually configured with them, they
> won't actually be used. Everything should fall back to using other
> addresses published for services/servers.
>
> On the other hand, if you hand out **A** list of prefixes with DHCP
> - when a provider goes down, your network becomes "randomly broken"
> as nodes try to use addresses that are no longer valid. You have to
> detect the failed service, and update the DHCP configuration, and
> wait (perhaps days) for nodes to renew and get the update.
> Alternatively, if DHCP doesn't do it, you have to manually configure
> each node to know about all the prefixes - and manually update them
> if a prefix is no longer valid. Or you potentially have locally
> reachable neighbours communicating via two external connections if
> they are in different prefixes.
>
> I hope it's obvious that for a situation like this, the separation
> of address assignment and routing information is "a good thing". It
> lets the routing dynamically update, without having to build
> "interesting" couplings between different services, and also
> operating quickly without the instability and risk from short DHCP
> lease times.
>
> It doesn't address the issue of updating the outward facing DNS to
> remove the offline prefix - but that would be a problem no matter
> how the network addressing/routing was done. Between the service
> going down, and the DNS updates going out, clients will experience
> delays if they happen to try a "dead" address first before falling
> back and trying another address (they'll get a list of AAAA records,
> not just one) - but they will connect.
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Thu Apr  9 04:30:07 2015
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8491A015F for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 04:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 Z_L3zsfx9rDQ for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 04:30:02 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D8191A014C for <dhcwg@ietf.org>; Thu,  9 Apr 2015 04:30:02 -0700 (PDT)
Received: by qkgx75 with SMTP id x75so120681148qkg.1 for <dhcwg@ietf.org>; Thu, 09 Apr 2015 04:30:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CSjoD4MKtb3tmuildduGEs03cVVMrZtvc9vS/2wCjI8=; b=i8w8NZx0vTCWmTgIOc9dNrbadPnbNsG+79IwMl+YYEWsmLh9lJe4VsX4BRlJX9agPB E88AwsjDQIfvjRxwpmhmpiJZZlBMVK0L92pdXEwDs+jdVnV1LMsHN25NhO2OJnH32KZ/ GMLHBbB+nRiO+mD+OIsR/B3dt8KE55146xr2epjd1zzoa7xlCc0UqYsSTWfFvwYS2kWy IV7YIiUs5Bt8j3VQNhLkJl3heEm/gqEnzyg2u+xGsRvyW5Xf7Cp7inYrwv7/DtNAXI3e VUz2TPXpTIu2yVGeDzVcIW3+f/C4oA93SykIrBPkbii7MU+2R2WYCcxhJwWrmAzzsfrE 1wmQ==
X-Received: by 10.55.49.211 with SMTP id x202mr56816123qkx.60.1428579001870; Thu, 09 Apr 2015 04:30:01 -0700 (PDT)
Received: from ?IPv6:2001:420:c0c4:1006::10d? ([2001:420:c0c4:1006::10d]) by mx.google.com with ESMTPSA id 5sm4567178qgg.28.2015.04.09.04.30.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Apr 2015 04:30:01 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <5526612A.7000502@gmail.com>
Date: Thu, 9 Apr 2015 07:30:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/dxuof5FxQiQTi2XhoJMk_YaDeTE>
Cc: dhcwg@ietf.org, Droms Ralph <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 11:30:05 -0000

> On Apr 9, 2015, at 7:23 AM 4/9/15, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
>=20
> Le 09/04/2015 12:21, Simon Hobson a =E9crit :
>> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>>=20
>> <snip>
>>> Look - whenever adding an address on an interface you have to use a
>>> prefixlen.
>>=20
>> Then you are forever doomed to not understand IPv6 and be
>> complaining that "it's wrong". Because when adding an address you do
>> **NOT** need to specify a prefix length - when adding an address **on
>> an incorrect implementation** you need to provide one **only for the
>> convenience of that implementation**, because it is **NOT** required
>> in any way whatsoever for correct operation of IPv6.
>=20
> Ok.
>=20
> Is '128' the correct prefixlen to add to an address when putting it on
> an interface?  Or is 64 the correct prefixlen?

Neither.  There is *no* prefix length associated with an address.  The =
prefix lengths are associated with the *prefixes* assigned to the link.

>=20
> Alex
>=20
>>=20
>> Until you can separate what is actually needed, vs what certain
>> implementations need, then you will never "get it". It did take me a
>> while, and some explaining from others on this list before I "got
>> it" - until then I thought like you and worked on the basis that what
>> I was using (ie implementations in Linux) was "right".
>>=20
>> I can fully see why the implementations are as they are - as Brian
>> Haberman pointed out yesterday, people would have been rushing to
>> get something working, and refactoring existing code is by far the
>> easiest way to do that. Getting from where we are, to standards
>> compliant will be an interesting challenge - deprecating certain
>> things and persuading everyone to update everything that uses the
>> old interface to update their software. The pragmatist in me thinks
>> that perhaps it's not really necessary to rebuild all the code to not
>> use prefix lengths with addresses - just default to /128 prefix
>> lengths and throw out a warning message if anything different is set
>> might be enough.
>>=20
>>=20
>>> If you add an address on an interface manually then the system
>>> invents an arbitrary one for you (64 or 128); if by using SLAAC
>>> you get the plen from the RA.  If using DHCP you still get it from
>>> RA. It all depends on this RA.  This is not normal.
>>=20
>> In the IPv6 world it **IS** normal. IPv6 =3D/=3D IPv4. You may have =
many
>> years working with such systems, but that seems to be part of your
>> problem - a reluctance or inability to accept that IPv6 is different
>> to IPv4 by design. We can argue about whether those design decisions
>> are right or not, but that is the design.
>>=20
>> Your position indicates that you are still stuck in IPv4 thinking
>> where "IP address plus subnet mask =3D=3D reachability information =
for
>> neighbours". That's only true for certain network technologies (such
>> as ethernet), and it's only true for single subnets.
>>=20
>> There are, as pointed out in some of the RFCs/drafts you've read,
>> networks where having an IP address in the same subnet/prefix as the
>> destination does not make that destination directly reachable. In
>> those cases, using "IP+subnet/prefix =3D=3D reachability information"
>> breaks.
>>=20
>> In the IPv6 world, it is considered "normal" for there to be
>> multiple prefixes and for hosts to have multiple addresses. Having a
>> single prefix is merely a case of that multiple being one". Except in
>> the special case of that multiple being one, using "IP+subnet/prefix
>> =3D=3D reachability information" breaks.
>>=20
>>=20
>> I'll give a further example of how I understand things are supposed
>> to work - and why "old style" thinking doesn't work.
>>=20
>> Lets say we have two (or more) internet providers, and unless we're
>> big enough to go and get our own AS number etc, then we'll get
>> different prefixes from each. In the normal case, each host is
>> likely to be multihomed - having an address from each prefix, and
>> we'll publish AAAA records for each address. Each provider has a
>> router, and each router provides an RA for the prefix(es) it serves.
>> This is important - as I think you are assuming that all routers send
>> the same list of prefixes. Each node aggregates the RA supplied
>> prefixes to build it's prefix table. Using ${some process}, each node
>> will work out which traffic to send via each router (and which
>> source address to use) - this is something I'm not 100% comfortable
>> with, having been used to having routers make that decision.
>>=20
>> Now lets say one provider goes offline. The router detects this (or
>> is offline itself) and so RAs for the prefix(es) from that provider
>> stop. When caches time out, each node will remove those prefixes
>> from it's prefix table. Thus when a provider goes offline, the nodes
>> using any prefix(es) from that provider will stop doing so - and in
>> addition, nodes will also stop treating those prefixes as local.
>>=20
>> So even though a DHCP server may still be handing out addresses in
>> that prefix, or the hosts may be manually configured with them, they
>> won't actually be used. Everything should fall back to using other
>> addresses published for services/servers.
>>=20
>> On the other hand, if you hand out **A** list of prefixes with DHCP
>> - when a provider goes down, your network becomes "randomly broken"
>> as nodes try to use addresses that are no longer valid. You have to
>> detect the failed service, and update the DHCP configuration, and
>> wait (perhaps days) for nodes to renew and get the update.
>> Alternatively, if DHCP doesn't do it, you have to manually configure
>> each node to know about all the prefixes - and manually update them
>> if a prefix is no longer valid. Or you potentially have locally
>> reachable neighbours communicating via two external connections if
>> they are in different prefixes.
>>=20
>> I hope it's obvious that for a situation like this, the separation
>> of address assignment and routing information is "a good thing". It
>> lets the routing dynamically update, without having to build
>> "interesting" couplings between different services, and also
>> operating quickly without the instability and risk from short DHCP
>> lease times.
>>=20
>> It doesn't address the issue of updating the outward facing DNS to
>> remove the offline prefix - but that would be a problem no matter
>> how the network addressing/routing was done. Between the service
>> going down, and the DNS updates going out, clients will experience
>> delays if they happen to try a "dead" address first before falling
>> back and trying another address (they'll get a list of AAAA records,
>> not just one) - but they will connect.
>>=20
>> _______________________________________________ dhcwg mailing list
>> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>>=20
>>=20
>=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Thu Apr  9 04:42:37 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D31AF1A0334 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 04:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 QwV54YtAITz5 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 04:42:32 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B1301A02BE for <dhcwg@ietf.org>; Thu,  9 Apr 2015 04:42:32 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t39BgTaS006063; Thu, 9 Apr 2015 13:42:29 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 1D5F3209B28; Thu,  9 Apr 2015 13:43:35 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 1098E20364A; Thu,  9 Apr 2015 13:43:35 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t39Bg499012083; Thu, 9 Apr 2015 13:42:29 +0200
Message-ID: <5526658C.8000708@gmail.com>
Date: Thu, 09 Apr 2015 13:42:04 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com>
In-Reply-To: <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/lX-yD_CDsLAjValmSJkeHJaCZSY>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 11:42:36 -0000

Le 09/04/2015 13:30, Ralph Droms a écrit :
>
>> On Apr 9, 2015, at 7:23 AM 4/9/15, Alexandru Petrescu
>> <alexandru.petrescu@gmail.com> wrote:
>>
>> Le 09/04/2015 12:21, Simon Hobson a écrit :
>>> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>>>
>>> <snip>
>>>> Look - whenever adding an address on an interface you have to
>>>> use a prefixlen.
>>>
>>> Then you are forever doomed to not understand IPv6 and be
>>> complaining that "it's wrong". Because when adding an address
>>> you do **NOT** need to specify a prefix length - when adding an
>>> address **on an incorrect implementation** you need to provide
>>> one **only for the convenience of that implementation**, because
>>> it is **NOT** required in any way whatsoever for correct
>>> operation of IPv6.
>>
>> Ok.
>>
>> Is '128' the correct prefixlen to add to an address when putting
>> it on an interface?  Or is 64 the correct prefixlen?
>
> Neither.  There is *no* prefix length associated with an address. The
> prefix lengths are associated with the *prefixes* assigned to the
> link.

This means that either there are no correct implementations of IPv6 out
there, or that a prefix must always assigned when an address is assigned.

If this latter then we absolutely want DHCP - which assigns addresses -
to also assign prefixes with their lengths.

Is there something blocking this?

Alex

>
>>
>> Alex
>>
>>>
>>> Until you can separate what is actually needed, vs what certain
>>> implementations need, then you will never "get it". It did take
>>> me a while, and some explaining from others on this list before
>>> I "got it" - until then I thought like you and worked on the
>>> basis that what I was using (ie implementations in Linux) was
>>> "right".
>>>
>>> I can fully see why the implementations are as they are - as
>>> Brian Haberman pointed out yesterday, people would have been
>>> rushing to get something working, and refactoring existing code
>>> is by far the easiest way to do that. Getting from where we are,
>>> to standards compliant will be an interesting challenge -
>>> deprecating certain things and persuading everyone to update
>>> everything that uses the old interface to update their software.
>>> The pragmatist in me thinks that perhaps it's not really
>>> necessary to rebuild all the code to not use prefix lengths with
>>> addresses - just default to /128 prefix lengths and throw out a
>>> warning message if anything different is set might be enough.
>>>
>>>
>>>> If you add an address on an interface manually then the system
>>>>  invents an arbitrary one for you (64 or 128); if by using
>>>> SLAAC you get the plen from the RA.  If using DHCP you still
>>>> get it from RA. It all depends on this RA.  This is not
>>>> normal.
>>>
>>> In the IPv6 world it **IS** normal. IPv6 =/= IPv4. You may have
>>> many years working with such systems, but that seems to be part
>>> of your problem - a reluctance or inability to accept that IPv6
>>> is different to IPv4 by design. We can argue about whether those
>>> design decisions are right or not, but that is the design.
>>>
>>> Your position indicates that you are still stuck in IPv4 thinking
>>> where "IP address plus subnet mask == reachability information
>>> for neighbours". That's only true for certain network
>>> technologies (such as ethernet), and it's only true for single
>>> subnets.
>>>
>>> There are, as pointed out in some of the RFCs/drafts you've read,
>>> networks where having an IP address in the same subnet/prefix as
>>> the destination does not make that destination directly
>>> reachable. In those cases, using "IP+subnet/prefix ==
>>> reachability information" breaks.
>>>
>>> In the IPv6 world, it is considered "normal" for there to be
>>> multiple prefixes and for hosts to have multiple addresses.
>>> Having a single prefix is merely a case of that multiple being
>>> one". Except in the special case of that multiple being one,
>>> using "IP+subnet/prefix == reachability information" breaks.
>>>
>>>
>>> I'll give a further example of how I understand things are
>>> supposed to work - and why "old style" thinking doesn't work.
>>>
>>> Lets say we have two (or more) internet providers, and unless
>>> we're big enough to go and get our own AS number etc, then we'll
>>> get different prefixes from each. In the normal case, each host
>>> is likely to be multihomed - having an address from each prefix,
>>> and we'll publish AAAA records for each address. Each provider
>>> has a router, and each router provides an RA for the prefix(es)
>>> it serves. This is important - as I think you are assuming that
>>> all routers send the same list of prefixes. Each node aggregates
>>> the RA supplied prefixes to build it's prefix table. Using
>>> ${some process}, each node will work out which traffic to send
>>> via each router (and which source address to use) - this is
>>> something I'm not 100% comfortable with, having been used to
>>> having routers make that decision.
>>>
>>> Now lets say one provider goes offline. The router detects this
>>> (or is offline itself) and so RAs for the prefix(es) from that
>>> provider stop. When caches time out, each node will remove those
>>> prefixes from it's prefix table. Thus when a provider goes
>>> offline, the nodes using any prefix(es) from that provider will
>>> stop doing so - and in addition, nodes will also stop treating
>>> those prefixes as local.
>>>
>>> So even though a DHCP server may still be handing out addresses
>>> in that prefix, or the hosts may be manually configured with
>>> them, they won't actually be used. Everything should fall back
>>> to using other addresses published for services/servers.
>>>
>>> On the other hand, if you hand out **A** list of prefixes with
>>> DHCP - when a provider goes down, your network becomes "randomly
>>> broken" as nodes try to use addresses that are no longer valid.
>>> You have to detect the failed service, and update the DHCP
>>> configuration, and wait (perhaps days) for nodes to renew and
>>> get the update. Alternatively, if DHCP doesn't do it, you have
>>> to manually configure each node to know about all the prefixes -
>>> and manually update them if a prefix is no longer valid. Or you
>>> potentially have locally reachable neighbours communicating via
>>> two external connections if they are in different prefixes.
>>>
>>> I hope it's obvious that for a situation like this, the
>>> separation of address assignment and routing information is "a
>>> good thing". It lets the routing dynamically update, without
>>> having to build "interesting" couplings between different
>>> services, and also operating quickly without the instability and
>>> risk from short DHCP lease times.
>>>
>>> It doesn't address the issue of updating the outward facing DNS
>>> to remove the offline prefix - but that would be a problem no
>>> matter how the network addressing/routing was done. Between the
>>> service going down, and the DNS updates going out, clients will
>>> experience delays if they happen to try a "dead" address first
>>> before falling back and trying another address (they'll get a
>>> list of AAAA records, not just one) - but they will connect.
>>>
>>> _______________________________________________ dhcwg mailing
>>> list dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>>>
>>>
>>
>>
>> _______________________________________________ dhcwg mailing list
>>  dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>



From nobody Thu Apr  9 04:56:42 2015
Return-Path: <sthaug@nethelp.no>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 455FD1A038F for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 04:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 cIuZTI3U54Wp for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 04:56:39 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id C11301A037E for <dhcwg@ietf.org>; Thu,  9 Apr 2015 04:56:38 -0700 (PDT)
Received: (qmail 77913 invoked from network); 9 Apr 2015 11:56:37 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 9 Apr 2015 11:56:37 -0000
Date: Thu, 09 Apr 2015 13:56:36 +0200 (CEST)
Message-Id: <20150409.135636.74676591.sthaug@nethelp.no>
To: alexandru.petrescu@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <5526658C.8000708@gmail.com>
References: <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.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/dhcwg/bfC3nREYFXw7lXWGDh8bw7p3pn4>
Cc: dhcwg@ietf.org, rdroms.ietf@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 11:56:41 -0000

> > Neither.  There is *no* prefix length associated with an address. The
> > prefix lengths are associated with the *prefixes* assigned to the
> > link.
> 
> This means that either there are no correct implementations of IPv6 out
> there, or that a prefix must always assigned when an address is assigned.
> 
> If this latter then we absolutely want DHCP - which assigns addresses -
> to also assign prefixes with their lengths.
> 
> Is there something blocking this?

DHCPv6 IA_NA can assign an address, no prefix length.
DHCPv6 IA_PD can assign a prefix.

Neither of them can assign a default gateway / specify on-link prefixes.

DHCPv6 *hosts* will normally not ask for IA_PD.

Steinar Haug, AS 2116


From nobody Thu Apr  9 05:02:47 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91B0E1A03A2 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 GZlI06idZXPL for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:02:40 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 4BD3A1A03B3 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 05:02:40 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id DD01FDA00CF; Thu,  9 Apr 2015 12:02:39 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 9 Apr 2015 05:02:39 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <20150409.081427.74687401.sthaug@nethelp.no>
Date: Thu, 9 Apr 2015 08:02:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <EEABBA8E-9943-41EB-8BA6-176F30FCC951@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no>
To: <sthaug@nethelp.no>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/32sI5ZLDJ90A5ZKRd3kkbRGSZGM>
Cc: dhcwg@ietf.org, alexandru.petrescu@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 12:02:41 -0000

On Apr 9, 2015, at 2:14 AM, <sthaug@nethelp.no> <sthaug@nethelp.no> =
wrote:
> - The RFC 6939 link layer address option is only used by DHCPv6 relay
> agents.
>=20
> - DHCPv6 servers are explicitly prohibited from "peeking inside" DUIDs
> (even if some servers actually offer this functionality):
>=20
> "Clients and servers MUST treat DUIDs as opaque values and MUST only
> compare DUIDs for equality.  Clients and servers MUST NOT in any
> other way interpret DUIDs." (RFC 3315 ch. 9)

The "explicit prohibition" that you are referring to is for the purposes =
of using the MAC address inside the DUID as a protocol element.   There =
is nothing wrong with you inferring something from the DUID if you want. =
  The problem would arise if you used the MAC address contained in the =
DUID, and not the DUID, as the key that uniquely identified the address =
assignment.

As for the client link address, if there is no relay agent, then the =
DHCP server can just scrape the layer two address off of the =
packet--there's no need to send it twice.


From nobody Thu Apr  9 05:12:51 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 097B71A1A63 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 QUynTdxfhBbh for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:12:49 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9B861A1B8F for <dhcwg@ietf.org>; Thu,  9 Apr 2015 05:12:39 -0700 (PDT)
Received: by igblo3 with SMTP id lo3so62668512igb.0 for <dhcwg@ietf.org>; Thu, 09 Apr 2015 05:12:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=tkE92SfON5wdvqaIIaZTqfKgkMXdPpaPQ253mhysRHU=; b=I1wOjMtomSGUjCdVCh9FTeg4HR05r+AoHw7QfIRMT6m4uFApc5XcAHoNU7JJ4bYi5g UEQ2HeIN/BBQrdiftscgEjJBEPrhk8fHaScIE70FVVtUVUaZv4REW1P796D0NT/vcTmn sy4C8OPGuhcNx37gtKzxfLw3odj10cJU6LubER10cGi0d1LB9RoOATZVPg35PuyadRPG DK7mTMica6D2NBKO39TIA5bk1Vg1KI8SZpEZLf1+cCYOcg6a0tuW4lRBTSnvss3JcBeo YZSAB8z7iUpLqrtw61Un2chXKIFIjjzhboMiiWK/wu+f9yWTtHlQ2I6AcjVN1VPzF5e7 wNjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=tkE92SfON5wdvqaIIaZTqfKgkMXdPpaPQ253mhysRHU=; b=beOTjCZ9VoeFYKnfgJQNeETAmui+Ha5svf9KZmXgp9SJOAORwUI2zPyPlD2lq2nSKi 0viKih2T6KCOlKgjJ8q7PeQAThmRmOSd+RixopxmAwjLpBP01B53ze4fB4poW2qvbRJm jHhtQrtlMpf0WsgPLkgtxncmSM1jN6XPu+th8TEgcFJOk7uunzC1MxCq9e6cZ77SCJaI E+thzYGU1kmoIwkJBhXd8JLIf+eHrGC17+p3t6WwoPIwsKkOZBeQl6almbRdTzEfasK0 Ew37I9OSvwXQ857J/Jjyj2MCmO0RGBeoHTrxgagwQPcDp9FqQYrRpdaAP23cqDV5GKS8 ASSQ==
X-Gm-Message-State: ALoCoQksru2DJElxzyMWyA8JtT08/cT7HL09gZJJ4vYTsmHX+UebmPuG3+lURXzBo8uLOCXUBPNq
X-Received: by 10.107.34.210 with SMTP id i201mr46510302ioi.1.1428581559382; Thu, 09 Apr 2015 05:12:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Thu, 9 Apr 2015 05:12:18 -0700 (PDT)
In-Reply-To: <5526658C.8000708@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Apr 2015 21:12:18 +0900
Message-ID: <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a114031a0615da305134990ed
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/-3t-nkITdhXbNcBA3fUBdJJSgxs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 12:12:50 -0000

--001a114031a0615da305134990ed
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 9, 2015 at 8:42 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> This means that either there are no correct implementations of IPv6 out
> there, or that a prefix must always assigned when an address is assigned.
>

No, there's a third choice: assigning an address can be implemented by
assigning a prefix of length /128.


> If this latter then we absolutely want DHCP - which assigns addresses -
> to also assign prefixes with their lengths.
>

That does not follow at all.

--001a114031a0615da305134990ed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 9, 2015 at 8:42 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petre=
scu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This =
means that either there are no correct implementations of IPv6 out<br>
there, or that a prefix must always assigned when an address is assigned.<b=
r></blockquote><div><br></div><div>No, there&#39;s a third choice: assignin=
g an address can be implemented by assigning a prefix of length /128.</div>=
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">If this latter then we abso=
lutely want DHCP - which assigns addresses -<br>
to also assign prefixes with their lengths.<br></blockquote><div><br></div>=
<div>That does not follow at all.</div></div></div></div>

--001a114031a0615da305134990ed--


From nobody Thu Apr  9 05:15:55 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7B271A6F2F for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9f81KRc_mUXl for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:15:52 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 703241A1BEF for <dhcwg@ietf.org>; Thu,  9 Apr 2015 05:15:52 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 54530DA00D1; Thu,  9 Apr 2015 12:15:52 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 9 Apr 2015 05:15:45 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <5526658C.8000708@gmail.com>
Date: Thu, 9 Apr 2015 08:15:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <3C0A02F8-C69C-43B6-84CD-4D36A73A0307@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/x4tNQ2PTRezdzwrm2DO-5xGlVY8>
Cc: dhcwg@ietf.org, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 12:15:53 -0000

On Apr 9, 2015, at 7:42 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
> This means that either there are no correct implementations of IPv6 =
out
> there, or that a prefix must always assigned when an address is =
assigned.

What makes an implementation correct or incorrect is not the details of =
how it is implemented, but rather whether or not it conforms to the =
specification.   An implementation that treats an IPv6 address it =
receives from DHCPv6 as having no associated prefix length will behave =
correctly.   One that treats it as having an associated prefix length =
will not.   So assuming that what you have said about FreeBSD is =
correct, FreeBSD will exhibit incorrect behavior in some situations, =
imputing reachability to addresses that are not reachable and failing to =
communicate with such hosts.

This is easy to test: set up two links each with a DHCP relay and a =
router that is advertising a default route but no prefixes, and that is =
routing between the two links.   Have the DHCP server issue IP addresses =
to both links from the same /64 prefix.   Configure a Linux box and a =
FreeBSD box on each link with a DHCP client.   Now try to communicate =
between the two Linux boxes, between the two FreeBSD boxes, and between =
a Linux box on one link and a FreeBSD box on the other link.

What you will see is that the Linux boxes will succeed in communicating, =
and the FreeBSD boxes will not be able to communicate either with each =
other or with Linux boxes on the other link, but _will_ be able to =
communicate with the Linux box on the same link.

So, again assuming that what you've reported about FreeBSD is correct, =
the FreeBSD box doesn't conform to the specification.

All of this discussion about how Linux imputes a /128 and FreeBSD =
imputes a /64 is irrelevant, because you're talking about details of how =
the stack is implemented, not about the _behavior_ of the stack.


From nobody Thu Apr  9 05:20:30 2015
Return-Path: <sthaug@nethelp.no>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D28EA1A1B1D for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 HuiwgVP0Brxo for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:20:27 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 3742D1A6F2F for <dhcwg@ietf.org>; Thu,  9 Apr 2015 05:20:22 -0700 (PDT)
Received: (qmail 79367 invoked from network); 9 Apr 2015 12:20:21 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 9 Apr 2015 12:20:21 -0000
Date: Thu, 09 Apr 2015 14:20:21 +0200 (CEST)
Message-Id: <20150409.142021.41704250.sthaug@nethelp.no>
To: Ted.Lemon@nominum.com
From: sthaug@nethelp.no
In-Reply-To: <EEABBA8E-9943-41EB-8BA6-176F30FCC951@nominum.com>
References: <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <EEABBA8E-9943-41EB-8BA6-176F30FCC951@nominum.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/dhcwg/5G6xRJWOCgFcT_RMwKTpUwfdHQg>
Cc: dhcwg@ietf.org, alexandru.petrescu@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 12:20:29 -0000

> > - DHCPv6 servers are explicitly prohibited from "peeking inside" DUIDs
> > (even if some servers actually offer this functionality):
> > 
> > "Clients and servers MUST treat DUIDs as opaque values and MUST only
> > compare DUIDs for equality.  Clients and servers MUST NOT in any
> > other way interpret DUIDs." (RFC 3315 ch. 9)
> 
> The "explicit prohibition" that you are referring to is for the purposes of using the MAC address inside the DUID as a protocol element.   There is nothing wrong with you inferring something from the DUID if you want.   The problem would arise if you used the MAC address contained in the DUID, and not the DUID, as the key that uniquely identified the address assignment.

It feels a bit like discussing "How many angels can dance on the head
of a pin?"  If I use the MAC address for the purpose of correlating
IPv4 and IPv6 address assignments, but use DUID to identify the
address assignment, the protocol police won't go after me? :-)

In any case, if RFC 3315 meant to say that there is nothing wrong in
inferring MAC address from DUID (as long as it's not used as a key to
identify the address assignment), I think the section quoted above
needs to be clarified.

Steinar Haug, AS 2116


From nobody Thu Apr  9 05:41:08 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 491251ACEE3 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 skcJk89K-ukO for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:41:02 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id A155C1ACE90 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 05:41:01 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 9E1931BC3E for <dhcwg@ietf.org>; Thu,  9 Apr 2015 12:40:57 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <20150409.142021.41704250.sthaug@nethelp.no>
Date: Thu, 9 Apr 2015 13:40:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9296338-9D16-4456-803C-2559D4B162CC@thehobsons.co.uk>
References: <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <EEABBA8E-9943-41EB-8BA6-176F30FCC951@nominum.com> <20150409.142021.41704250.sthaug@nethelp.no>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/qxaonji8y_WtIQzBr87oQrfbwOY>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 12:41:04 -0000

sthaug@nethelp.no wrote:

>>> "Clients and servers MUST treat DUIDs as opaque values and MUST only
>>> compare DUIDs for equality.  Clients and servers MUST NOT in any
>>> other way interpret DUIDs." (RFC 3315 ch. 9)
>>=20
>> The "explicit prohibition" that you are referring to is for the =
purposes of using the MAC address inside the DUID as a protocol element. =
  There is nothing wrong with you inferring something from the DUID if =
you want.   The problem would arise if you used the MAC address =
contained in the DUID, and not the DUID, as the key that uniquely =
identified the address assignment.
>=20
> It feels a bit like discussing "How many angels can dance on the head
> of a pin?"  If I use the MAC address for the purpose of correlating
> IPv4 and IPv6 address assignments, but use DUID to identify the
> address assignment, the protocol police won't go after me? :-)
>=20
> In any case, if RFC 3315 meant to say that there is nothing wrong in
> inferring MAC address from DUID (as long as it's not used as a key to
> identify the address assignment), I think the section quoted above
> needs to be clarified.

I agree, what the RFC says, and what Ted says (no offence intended), are =
mutually exclusive. We've had this discussion before as well :-/
But then it's not necessarily all that helpful as only DUID-LL and =
DUID-LLT have a readable MAC address - and these aren't generally used =
by "desktop" level devices (ie computers).


From nobody Thu Apr  9 06:02:37 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3DDA1A1B43 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 06:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 UGZQKnbVQ4do for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 06:02:32 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 6662A1A1A6F for <dhcwg@ietf.org>; Thu,  9 Apr 2015 06:02:32 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 317A8DA00D1; Thu,  9 Apr 2015 13:02:32 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 9 Apr 2015 06:02:31 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <20150409.142021.41704250.sthaug@nethelp.no>
Date: Thu, 9 Apr 2015 09:02:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <69CB370E-235E-4694-8BF3-52B3392F3E4A@nominum.com>
References: <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <EEABBA8E-9943-41EB-8BA6-176F30FCC951@nominum.com> <20150409.142021.41704250.sthaug@nethelp.no>
To: <sthaug@nethelp.no>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/XgElepvuTx6vALR0roDUWtzoipo>
Cc: dhcwg@ietf.org, alexandru.petrescu@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 13:02:36 -0000

On Apr 9, 2015, at 8:20 AM, sthaug@nethelp.no wrote:
> It feels a bit like discussing "How many angels can dance on the head
> of a pin?"  If I use the MAC address for the purpose of correlating
> IPv4 and IPv6 address assignments, but use DUID to identify the
> address assignment, the protocol police won't go after me? :-)

This represents a bit of a mischaracterization of what it means for a =
standard to say something.   When you see a MUST in a standard, it's =
intended to ensure that different implements interoperate correctly and =
behave correctly.   That's _all_ it means.   The only protocol police =
that exists is harsh reality: if you use the MAC address and not the =
DUID as a key, you will experience interop problems.  But if you are =
just trying to do correlation between DHCPv4 and DHCPv6, and there's no =
_protocol_ change, there is no reason not to do it.

> In any case, if RFC 3315 meant to say that there is nothing wrong in
> inferring MAC address from DUID (as long as it's not used as a key to
> identify the address assignment), I think the section quoted above
> needs to be clarified.

RFC 3315 is specifying the protocol, so it is correct in what it says.   =
Just remember that all of the MUSTs and SHOULDs are for interop purposes =
and don't go any farther than that, and you should be okay.


From nobody Thu Apr  9 07:58:09 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31C101A907F for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 07:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 0c1ifvXvrzZ5 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 07:58:06 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF3961A9038 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 07:58:05 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t39Ew1FQ023185; Thu, 9 Apr 2015 16:58:01 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 47816209DA6; Thu,  9 Apr 2015 16:59:07 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 2FAEF202FEE; Thu,  9 Apr 2015 16:59:07 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t39EvLNL021476; Thu, 9 Apr 2015 16:58:01 +0200
Message-ID: <55269351.10406@gmail.com>
Date: Thu, 09 Apr 2015 16:57:21 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/p9LISdk4EgGOJfvwIg8bISBCLhE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 14:58:08 -0000

Le 09/04/2015 14:12, Lorenzo Colitti a Ã©crit :
> On Thu, Apr 9, 2015 at 8:42 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>     This means that either there are no correct implementations of IPv6 out
>     there, or that a prefix must always assigned when an address is
>     assigned.
>
>
> No, there's a third choice: assigning an address can be implemented by
> assigning a prefix of length /128.

That is not specified.  Would you think consensus can be found to write 
down that statement of the 3rd choice?

>     If this latter then we absolutely want DHCP - which assigns addresses -
>     to also assign prefixes with their lengths.
>
>
> That does not follow at all.

If the 3rd choice above is not done (specify that assigning an address 
can be implemented by assigning a prefix of length /128) then what else 
would in your opinion follow?

Or should we leave it there: non-existent implementations of true IPv6.

Alex




From nobody Thu Apr  9 08:36:45 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A05831B2A19 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 08:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 wq3Sn_Sog0KT for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 08:36:42 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73DAF1B2CF7 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 08:36:42 -0700 (PDT)
Received: by iedfl3 with SMTP id fl3so117021658ied.1 for <dhcwg@ietf.org>; Thu, 09 Apr 2015 08:36:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=3ot04YD2ESx9PNuSbxpK2SbifGEkm3aAwAtPjcFRA4g=; b=ey1fHFF+2HRLSuJ5+chFXhP22wNsD9uvR1iJ5mA2DIY72ClebHfyvkakRQT5n2bbiC DfkYLNZGSUlvHikoUSLREzpNi/eQ18w6ILQuIzc620EHuWdrlVqIXVFWshRYJiPsfRhz 0KUo3P2LXpzJgj6BD8Z4DP/2BTGDYH6snzEmVFTeejsboZ1mFpFLioBdLAUiUd9p2vC7 x1xTLa49xDUVXNd9IY/sosfJ3zLkYtUhT5KI3J1YNH29uHHd7Yyl6hbmebhNK4nEmRXa U9nPVea7UY06ObQ5OEHFMMTkWBOl+MkJfUy6a/VlcHsHdzpsC3ZlvQddpM4xUkQjlNjN AVDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=3ot04YD2ESx9PNuSbxpK2SbifGEkm3aAwAtPjcFRA4g=; b=Yej7m4gi2CaL4s498vijPVOmWLZo3p2Oe2zaNG9uNPiJCeix2e6UiqN6zqbs7gjlUR nn3dGZcwnO/AmlfSg+zeXP8uSIkY8yEgGM9cmjVWB2Ahx+ov+Uab6kgLMkPTRNnD6wX4 U4K0rHMcuvp7uAp8VKvvP2WWDHNOSF2Ow8jaxLvpFWq4xGK1GU20e/bKhRmKZeO7SRSV oJC7Sitr3ds1iHvkZbPBqEE53C/ojX56fq0FUZtK+b1WvtePHN5MRf7h2DQcShkeN+TQ Ah4iCGr+4K/cT/5VPHDwZIOlHHy2oFUibATjrg+vPKeqGToqW5Z7SRm/sLzcpSywvaUM aFPg==
X-Gm-Message-State: ALoCoQmnL7cl4YuRsryLWlimntZPAYRhY+MvRQ1o/Va7a5iTDZ+ksuyAo6qCxYjhIM5if7Eq4Kqu
X-Received: by 10.43.119.196 with SMTP id fv4mr13670039icc.83.1428593801902; Thu, 09 Apr 2015 08:36:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Thu, 9 Apr 2015 08:36:21 -0700 (PDT)
In-Reply-To: <55269351.10406@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 10 Apr 2015 00:36:21 +0900
Message-ID: <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec517cdec176ecd05134c6a7b
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/EB0QPmbvD5Y-ZY00UHzpALZ2ZUs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 15:36:43 -0000

--bcaec517cdec176ecd05134c6a7b
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 9, 2015 at 11:57 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> If the 3rd choice above is not done (specify that assigning an address can
> be implemented by assigning a prefix of length /128) then what else would
> in your opinion follow?
>
> Or should we leave it there: non-existent implementations of true IPv6.
>

As Ted keeps saying, what's important is not how you configure the
implementation, but how it behaves.

If configuring an address on a host causes the host to think that the whole
of the address' /64 is on link, then the host is behaving incorrectly. If
configuring an address on a host does not cause the host to believe that
any other addresses are on link, then the host is behaving correctly,
regardless of whether the host displays the address as "2001:db8::1",
"2001:db8::1/128", "2001:0db8:0:00:0:0:0000:00/onetwentyeight", or
"20010db8000000000000000000000001 80".

--bcaec517cdec176ecd05134c6a7b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 9, 2015 at 11:57 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petr=
escu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rg=
b(204,204,204);border-left-style:solid;padding-left:1ex">If the 3rd choice =
above is not done (specify that assigning an address can be implemented by =
assigning a prefix of length /128) then what else would in your opinion fol=
low?<br>
<br>
Or should we leave it there: non-existent implementations of true IPv6.<br>=
</blockquote><div><br></div><div>As Ted keeps saying, what&#39;s important =
is not how you configure the implementation, but how it behaves.</div><div>=
<br></div><div>If configuring an address on a host causes the host to think=
 that the whole of the address&#39; /64 is on link, then the host is behavi=
ng incorrectly. If configuring an address on a host does not cause the host=
 to believe that any other addresses are on link, then the host is behaving=
 correctly, regardless of whether the host displays the address as &quot;20=
01:db8::1&quot;, &quot;2001:db8::1/128&quot;, &quot;2001:0db8:0:00:0:0:0000=
:00/onetwentyeight&quot;, or &quot;20010db8000000000000000000000001 80&quot=
;.</div></div></div></div>

--bcaec517cdec176ecd05134c6a7b--


From nobody Thu Apr  9 10:52:48 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCED01B3005 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 10:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 fPMwtqEHP6gT for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 10:52:45 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 129BF1B302C for <dhcwg@ietf.org>; Thu,  9 Apr 2015 10:52:28 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id E46FB880CE for <dhcwg@ietf.org>; Thu,  9 Apr 2015 10:52:27 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (unknown [76.21.129.88]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id F2EC513682CB for <dhcwg@ietf.org>; Thu,  9 Apr 2015 10:52:22 -0700 (PDT)
Message-ID: <5526BC55.8020006@innovationslab.net>
Date: Thu, 09 Apr 2015 13:52:21 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dhcwg@ietf.org
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dc6XdOrOT7SIIJvtp4EQad6lfEfWVtAah"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/JTP4gTxSZvFNBCjG9Q4951q8VzQ>
Subject: [dhcwg] Question on draft-ietf-dhc-dynamic-shared-v4allocation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 17:52:47 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--dc6XdOrOT7SIIJvtp4EQad6lfEfWVtAah
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

All,
    I have begun my AD evaluation of
draft-ietf-dhc-dynamic-shared-v4allocation and have a need for some
clarification.  Section 8 of the draft says:

   The DHCPv4 Port Parameters Option uses the same fields as the S46
   Port Parameters Option described in Section 4.5 of
   [I-D.ietf-softwire-map-dhcp], implemented as a DHCPv4 option.  This
   is to maintain compatibility with existing port set implementations.

   The format of OPTION_V4_PORTPARAMS is shown in Figure 1.

                 0                             1
                 0  1  2  3  4  5  6  7  8  9  0  1  2  3  4  5
                +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
                |      option-code      |     option-len        |
                +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
                |         offset        |       PSID-len        |
                +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
                |                     PSID                      |
                +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

                  Figure 1: DHCPv4 Port Parameters Option


However, when I go and review the option defined in section 4.5 of
draft-ietf-softwire-map-dhcp, I see an incompatible option format:

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |     OPTION_S46_PORTPARAMS     |         option-length         |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   offset      |    PSID-len   |              PSID             |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                   Figure 6: S46 Port Parameters Option

Which is correct?

Regards,
Brian


--dc6XdOrOT7SIIJvtp4EQad6lfEfWVtAah
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVJrxVAAoJEBOZRqCi7goqMK8IAMm0Tyi8LfT04GrMqVEHM9oj
3rDkH9a6fdmhelLm6GArRn9XWZsgRSkIn8OulP+c8sZlrx0tOKD8ERPauoABrUD8
De1uvViX04rJY+JU3VRsenC98A7s3WFEcABbFJ0skuDmnh5ACnNWZ+HXk3UYpMMr
17NRS2q0NMwbJKMxPkFfzjSBitQRQuu72IjdGY68bvQlUQSRl3t5lYZ+ZBCZP/pw
418GnjTlrzILZzKSfDdap8WptAYh0gqpL/JglPD3/O/Xz9CrGzvMNTiuLF0WxBWH
t0E031K3lvNgL26DLi3Fowui3shn4pnsJMPr8PLX/LRbkgncV097lcTP4s1YkrQ=
=GCay
-----END PGP SIGNATURE-----

--dc6XdOrOT7SIIJvtp4EQad6lfEfWVtAah--


From nobody Thu Apr  9 11:19:00 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4CA41B30AA for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 11:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 3Wk50FkrRfT5 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 11:18:56 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 8B0E11B30B3 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 11:18:18 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YgH1m-0005Nx-IE; Thu, 09 Apr 2015 20:18:11 +0200
Message-ID: <5526B5F9.9090707@si6networks.com>
Date: Thu, 09 Apr 2015 14:25:13 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com>
In-Reply-To: <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/bfYlm23q6CIPG83NE4PTNUPP99k>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 18:18:59 -0000

On 04/08/2015 09:18 PM, Lorenzo Colitti wrote:
>     For the time being, I think we should not consider the 100% stateless
>     version of this. After all, the man goal of this document is an address
>     selection scheme for DHCPv6, rather than an improvement in terms of "now
>     DHCPv6 can be fully stateless".
> 
> If this algorithm does not allow stateless operation, and still requires
> keeping (and synchronizing) a lease database, then I really don't see
> the point of specifying this algorithm at all, as it provides no
> advantages over stateful random assignment.

This algorithm doesn't require keeping a lease database. DHCPv6 does.

And no, as noted in my other email, it does not require synchronization
of the lease database. IN the case of failover, rather than "renewing"
or "rebinding" the same address, the node will be leased the same
address as if it was a brandnew address -- same end result.

So the clear benefit is that you can have multiple DHCPv6 servers
operating on the same network, and you get address stabiity without an
additional protocol.

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Apr  9 11:29:35 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11BF81A883B for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 11:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 a260Wedc_8xm for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 11:29:33 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83E0F1A8835 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 11:29:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2555; q=dns/txt; s=iport; t=1428604173; x=1429813773; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=kr+ZxLqi+iGY+re84ZDVfOfdnbzj8+7e+B5OFPpSjF8=; b=cvRmt2dZpb1WAoYhl0w8vg7NUKjDblAylPLTIhLPTFTC2P2sXZgvTGUZ F9QHhC0Iemt1iJtALL/wtPKB+9+IEjyg7YRh5Qfv6Z9PIDHgNSW68c2Lk zRCCh1wKNUTeQwjb1fWF1Kr4VZ1p/a9BjayTEQPabFIBmNqlUqYAFgYgT I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C9BAAQxCZV/4YNJK1cgwiBLgXERAmHVAKBRTgUAQEBAQEBAX2EHwEBAQMBJxM0CwUHBAIBCA4DBAEBAQoUBQQHMhQJCAIEDgUIiBoIzkcBAQEBAQEBAQEBAQEBAQEBAQEBAQEXiyuEGREBBhomCwcGgxGBFgEEkQGVYYkMIoIzgTxvgQs5fwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,551,1422921600"; d="scan'208";a="139745611"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-1.cisco.com with ESMTP; 09 Apr 2015 18:29:32 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t39ITWmF008929 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 9 Apr 2015 18:29:32 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Thu, 9 Apr 2015 13:29:32 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Fernando Gont <fgont@si6networks.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUWByZTAVuV8ESYM5tVpMLK4p04ge2AgABZ+YD//7DXMIAKWypfgABgb4CAAAcrgIAAANmAgAAE+ACAAAV/AIABrwHhgAABkwA=
Date: Thu, 9 Apr 2015 18:29:31 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <8C4E055C-ED1D-4951-8473-6166109ACE69@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com>
In-Reply-To: <5526B5F9.9090707@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.108]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SHwKcHhhDDxuPFKJhq-lmNZ0rvs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 18:29:35 -0000

> So the clear benefit is that you can have multiple DHCPv6 servers operati=
ng on the same network, and you get address stability without an additional=
 protocol.

This concept is flawed if the servers aren't cooperating. If there are mult=
iple servers that don't share lease data, how does server 1 know whether th=
e lease was leased to another client or renewed, if server 2 ends up commun=
icating with the client? Server 1 may also expire the lease (and remove FQD=
N or other data). Or when a leasequery is done, the servers will return con=
flicting data (one says not leased, other says leased).

I just don't buy that is has any real benefit.

But I am going to refrain from discussing this topic any further as my posi=
tion (not as co-chair, but as an individual) is clear. Once we get differen=
t people to weight in (either on the mailing list or at IETF-93) to determi=
ne consensus we can figure out the appropriate next step.

- Bernie

-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com]=20
Sent: Thursday, April 09, 2015 1:25 PM
To: Lorenzo Colitti
Cc: dhcwg@ietf.org; Bernie Volz (volz); Ted Lemon
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-address=
es -> abandon work? / IA_NA applicability

On 04/08/2015 09:18 PM, Lorenzo Colitti wrote:
>     For the time being, I think we should not consider the 100% stateless
>     version of this. After all, the man goal of this document is an addre=
ss
>     selection scheme for DHCPv6, rather than an improvement in terms of "=
now
>     DHCPv6 can be fully stateless".
>=20
> If this algorithm does not allow stateless operation, and still=20
> requires keeping (and synchronizing) a lease database, then I really=20
> don't see the point of specifying this algorithm at all, as it=20
> provides no advantages over stateful random assignment.

This algorithm doesn't require keeping a lease database. DHCPv6 does.

And no, as noted in my other email, it does not require synchronization of =
the lease database. IN the case of failover, rather than "renewing"
or "rebinding" the same address, the node will be leased the same address a=
s if it was a brandnew address -- same end result.

So the clear benefit is that you can have multiple DHCPv6 servers operating=
 on the same network, and you get address stabiity without an additional pr=
otocol.

--
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Apr  9 14:26:52 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57CE91B3364 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 14:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 4iAnqX0XKb4Y for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 14:26:43 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 C10D21B335E for <dhcwg@ietf.org>; Thu,  9 Apr 2015 14:26:43 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YgJyD-0006B9-LT; Thu, 09 Apr 2015 23:26:42 +0200
Message-ID: <5526D45A.9020701@si6networks.com>
Date: Thu, 09 Apr 2015 16:34:50 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/s291gnFWHGQsbP-98ISd33Gw9y0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 21:26:50 -0000

On 04/09/2015 03:29 PM, Bernie Volz (volz) wrote:
>> So the clear benefit is that you can have multiple DHCPv6 servers
>> operating on the same network, and you get address stability
>> without an additional protocol.
> 
> This concept is flawed if the servers aren't cooperating. If there
> are multiple servers that don't share lease data, how does server 1
> know whether the lease was leased to another client or renewed, if
> server 2 ends up communicating with the client? 

Usually, you need servers to communicate because there's no way to tell
which address each server may have assigned to which client. But that's
not the case with this method.

Let me provide another example:

Let's assume that servers were to implement e method by which they
select the IID by embedding the client's MAC address in the IID (that
is, the server essentially generates a SLACC address for the client).

If you have multiple servers, and you have access to the client's MAC,
then there's no need for black magic to tell which addres will be leased
to which client.


The method specified in this document is similar in that respect, with
the only difference in that the IIDs are unpredictable.



> Server 1 may also
> expire the lease (and remove FQDN or other data). Or when a
> leasequery is done, the servers will return conflicting data (one
> says not leased, other says leased).

In all cases, the servers will compute the same address. -- that's the
whole point of the expression we use, and of the servers sharing the
same secret key.


> I just don't buy that is has any real benefit.
> 
> But I am going to refrain from discussing this topic any further as
> my position (not as co-chair, but as an individual) is clear. Once we
> get different people to weight in (either on the mailing list or at
> IETF-93) to determine consensus we can figure out the appropriate
> next step.

That's fine. I'd just like folks to decide based on the properties of
the method. Some of the assertions you've made about it are incorrect,
though.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Apr  9 16:20:52 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4431B36A7 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 16:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 so_36nL0MziK for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 16:20:48 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB3C71B36A4 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 16:20:47 -0700 (PDT)
Received: by iggg4 with SMTP id g4so80122707igg.0 for <dhcwg@ietf.org>; Thu, 09 Apr 2015 16:20:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Ee6Jkh0uCjHfvr2kg7CbCdPOKjqNodhjrbJeaf4V7QA=; b=iVEMU3yc4wWNCsBcrUJpEt7G/q9FUmjow7iQBGXB/2nLOwxvxr+/6dTO61cib8FLfP 3kAUi21Bqqb9pcjMSvhjUn6RkUfXP5yegCp3KLN1dijpeZ+wtlGhBpfBve5RKuyv/IjS uuzN5rX/oaAWtoKngYVKCV/UGvl83Dmzzp1BEk3krR9gNQ6YMUDIyWcHhrRyrQjKITsg 0VwMmIesDRAeEbtpvMTygBOOaVM24v2ornUJrHPmMAVzU+9PvRQ6GMvKev1YCmmVYkkt swEmQdPrToaTw6Qw5KLAD9ZeSjiDMD07ht56h29uiMV7iST42kBRFN+NadYa6Qn3FvCs /j0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Ee6Jkh0uCjHfvr2kg7CbCdPOKjqNodhjrbJeaf4V7QA=; b=NX9U73uSrbEAJqsXR7jHHvVvy+Cije44RifWeE9AzpUTomtHx3vxkQ3BNKp0YY/8E8 oJL8Zb103xTEq6AOpPBkTTMr5Vm340I9I9je94yK+KrIHIbZWVCbsXIZXQMTXIgPDUcp Z4xp8xmHt6JCBfm+CYMXV++ObTaSf86Gkrvf0zoCJFeCpyma2jayAHDOC6kPgG1RHt9Z XrQnXGqEfeAgMkSa+zd3OZ+AGAOFZeeCc4a46Zaj1XgJX3GEt4MTngnQbcjQ5rV7i8tU EKJeTLFRBqDr8R/FdiiCR3pYuxZrQv8nJyCC+SEz1D6qzjJ3X6iYxY4qSmCS2FXtSk9f LWgQ==
X-Gm-Message-State: ALoCoQka5FIS4Hxbq6/VXVaHybSgastuxtPeYrbQwUHwvwlBWpHyRix/bR4fiMnwnlsJKYFESKBJ
X-Received: by 10.107.46.155 with SMTP id u27mr49576071iou.87.1428621647286; Thu, 09 Apr 2015 16:20:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Thu, 9 Apr 2015 16:20:26 -0700 (PDT)
In-Reply-To: <5526D45A.9020701@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 10 Apr 2015 08:20:26 +0900
Message-ID: <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a113ac5b6ce3147051352e52c
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/dwSPyh0v6IeyljYPQAYzecfCu0U>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 23:20:49 -0000

--001a113ac5b6ce3147051352e52c
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 10, 2015 at 4:34 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> > This concept is flawed if the servers aren't cooperating. If there
> > are multiple servers that don't share lease data, how does server 1
> > know whether the lease was leased to another client or renewed, if
> > server 2 ends up communicating with the client?
>
> Usually, you need servers to communicate because there's no way to tell
> which address each server may have assigned to which client. But that's
> not the case with this method.
>

It is still the case even with this method, because the servers need to
agree on the value of the counter variable.

--001a113ac5b6ce3147051352e52c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Apr 10, 2015 at 4:34 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; T=
his concept is flawed if the servers aren&#39;t cooperating. If there<br>
&gt; are multiple servers that don&#39;t share lease data, how does server =
1<br>
&gt; know whether the lease was leased to another client or renewed, if<br>
&gt; server 2 ends up communicating with the client?<br>
<br>
</span>Usually, you need servers to communicate because there&#39;s no way =
to tell<br>
which address each server may have assigned to which client. But that&#39;s=
<br>
not the case with this method.<br></blockquote><div><br></div><div>It is st=
ill the case even with this method, because the servers need to agree on th=
e value of the counter variable.=C2=A0</div></div></div></div>

--001a113ac5b6ce3147051352e52c--


From nobody Thu Apr  9 21:55:20 2015
Return-Path: <lh.sunlinh@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ECB61A0E10 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 21:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 Uu03MlRu3Evr for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 21:55:17 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A1121A1BDF for <dhcwg@ietf.org>; Thu,  9 Apr 2015 21:55:17 -0700 (PDT)
Received: by wiun10 with SMTP id n10so12560054wiu.1 for <dhcwg@ietf.org>; Thu, 09 Apr 2015 21:55:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6tRuNuwKCdXTsb+hGsrlQxnxaK0Qeh7zISDEy7vU0og=; b=ims87a0+PEi7mIPr80nfsrXCbdzy5VkOas990IWM8hoOWwg4B8ynxw9RW61awgrtlj lgFomZldA9DG6IMpBI4HPIpKjpiWW4kd8S9p96jLThC9HQOfUOkUB5gNx0CcZ0npLvBh inuXYF3X4q8AYv+CQpVkn6Gi2Ex+QXV2nn6DnIg5DuVQdUywuS3MG9q0edTWeluhXulg CEhdQEG1QGtZIVkzGdi/sVb0qOQbPw8ziEBefdpcaU2sTo4PCcFE90eSLrZvG6OwsGwT RVD4p6xRX7hLJbCfUB2s9q5jFw2rLGI4gyKAKERw/0VL3n8u1sXYhKqx4T+rjBQVcvoV SR0A==
X-Received: by 10.194.61.244 with SMTP id t20mr63082050wjr.83.1428641715841; Thu, 09 Apr 2015 21:55:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.147.85 with HTTP; Thu, 9 Apr 2015 21:54:55 -0700 (PDT)
In-Reply-To: <5526BC55.8020006@innovationslab.net>
References: <5526BC55.8020006@innovationslab.net>
From: Linhui Sun <lh.sunlinh@gmail.com>
Date: Fri, 10 Apr 2015 12:54:55 +0800
Message-ID: <CAO_YprbspqU3t3ucDMjJ6T1noLehmArUYDR--YKG_WhHs2FPAA@mail.gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/alternative; boundary=047d7b86e406fbef8a051357910b
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/qg4EC8bXyS_ZjgkzdhZu2arz_88>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Question on draft-ietf-dhc-dynamic-shared-v4allocation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 04:55:19 -0000

--047d7b86e406fbef8a051357910b
Content-Type: text/plain; charset=UTF-8

Hi, Brian

I think both are correct since they are defining two different kinds of
options. The option defined in draft-ietf-dhc-dynamic-shared-v4allocation
is a DHCPv4 option, while the draft-ietf-softwire-map-dhcp specifies DHCPv6
options. Thus the "option-code" and "option-len" fields are different in
the two options.

Best Regards,
Linhui

2015-04-10 1:52 GMT+08:00 Brian Haberman <brian@innovationslab.net>:

> All,
>     I have begun my AD evaluation of
> draft-ietf-dhc-dynamic-shared-v4allocation and have a need for some
> clarification.  Section 8 of the draft says:
>
>    The DHCPv4 Port Parameters Option uses the same fields as the S46
>    Port Parameters Option described in Section 4.5 of
>    [I-D.ietf-softwire-map-dhcp], implemented as a DHCPv4 option.  This
>    is to maintain compatibility with existing port set implementations.
>
>    The format of OPTION_V4_PORTPARAMS is shown in Figure 1.
>
>                  0                             1
>                  0  1  2  3  4  5  6  7  8  9  0  1  2  3  4  5
>                 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>                 |      option-code      |     option-len        |
>                 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>                 |         offset        |       PSID-len        |
>                 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>                 |                     PSID                      |
>                 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>
>                   Figure 1: DHCPv4 Port Parameters Option
>
>
> However, when I go and review the option defined in section 4.5 of
> draft-ietf-softwire-map-dhcp, I see an incompatible option format:
>
>       0                   1                   2                   3
>       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |     OPTION_S46_PORTPARAMS     |         option-length         |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |   offset      |    PSID-len   |              PSID             |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>                    Figure 6: S46 Port Parameters Option
>
> Which is correct?
>
> Regards,
> Brian
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>

--047d7b86e406fbef8a051357910b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Brian<div><br></div><div>I think both are correct sinc=
e they are defining two different kinds of options. The option defined in=
=C2=A0<span style=3D"font-size:14px">draft-ietf-dhc-dynamic-shared-</span><=
span style=3D"font-size:14px">v4allocation is a DHCPv4 option, while the=C2=
=A0</span><span style=3D"font-size:14px">draft-ietf-softwire-map-dhcp speci=
fies DHCPv6 options. Thus the &quot;option-code&quot; and &quot;option-len&=
quot; fields are different in the two options.</span></div><div><span style=
=3D"font-size:14px"><br></span></div><div><span style=3D"font-size:14px">Be=
st Regards,</span></div><div><span style=3D"font-size:14px">Linhui</span></=
div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2015-04-10 1:=
52 GMT+08:00 Brian Haberman <span dir=3D"ltr">&lt;<a href=3D"mailto:brian@i=
nnovationslab.net" target=3D"_blank">brian@innovationslab.net</a>&gt;</span=
>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">All,<br>
=C2=A0 =C2=A0 I have begun my AD evaluation of<br>
draft-ietf-dhc-dynamic-shared-v4allocation and have a need for some<br>
clarification.=C2=A0 Section 8 of the draft says:<br>
<br>
=C2=A0 =C2=A0The DHCPv4 Port Parameters Option uses the same fields as the =
S46<br>
=C2=A0 =C2=A0Port Parameters Option described in Section 4.5 of<br>
=C2=A0 =C2=A0[I-D.ietf-softwire-map-dhcp], implemented as a DHCPv4 option.=
=C2=A0 This<br>
=C2=A0 =C2=A0is to maintain compatibility with existing port set implementa=
tions.<br>
<br>
=C2=A0 =C2=A0The format of OPTION_V4_PORTPARAMS is shown in Figure 1.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A01<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00=C2=A0 1=C2=
=A0 2=C2=A0 3=C2=A0 4=C2=A0 5=C2=A0 6=C2=A0 7=C2=A0 8=C2=A0 9=C2=A0 0=C2=A0=
 1=C2=A0 2=C2=A0 3=C2=A0 4=C2=A0 5<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +--+--+--+--+--+--+=
--+--+--+--+--+--+--+--+--+--+<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=
=A0 option-code=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0option-len=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +--+--+--+--+--+--+=
--+--+--+--+--+--+--+--+--+--+<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0offset=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =
=C2=A0PSID-len=C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +--+--+--+--+--+--+=
--+--+--+--+--+--+--+--+--+--+<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0PSID=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +--+--+--+--+--+--+=
--+--+--+--+--+--+--+--+--+--+<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Figure 1: DH=
CPv4 Port Parameters Option<br>
<br>
<br>
However, when I go and review the option defined in section 4.5 of<br>
draft-ietf-softwire-map-dhcp, I see an incompatible option format:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A01=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A02=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A03<br>
=C2=A0 =C2=A0 =C2=A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 =
7 8 9 0 1<br>
=C2=A0 =C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<br>
=C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0OPTION_S46_PORTPARAMS=C2=A0 =C2=A0=
 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0option-length=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<br>
=C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0offset=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0=
 PSID-len=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 PSI=
D=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Figure=
 6: S46 Port Parameters Option<br>
<br>
Which is correct?<br>
<br>
Regards,<br>
Brian<br>
<br>
<br>_______________________________________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dhcwg</a><br>
<br></blockquote></div><br></div></div>

--047d7b86e406fbef8a051357910b--


From nobody Thu Apr  9 23:22:48 2015
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7079A1ACE8F for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 23:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.45
X-Spam-Level: 
X-Spam-Status: No, score=0.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_CHARSET_FARAWAY=2.45, 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 4tOlEGNfNMj2 for <dhcwg@ietfa.amsl.com>; Thu,  9 Apr 2015 23:22:46 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00B141ACE94 for <dhcwg@ietf.org>; Thu,  9 Apr 2015 23:22:45 -0700 (PDT)
Received: by paboj16 with SMTP id oj16so12217032pab.0 for <dhcwg@ietf.org>; Thu, 09 Apr 2015 23:22:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=FH1JP4WxBQBo1GtuFCEEfwPEdwJglnEbF1pvVHRiwyE=; b=YahBaHqe6Yi9LaGbcOQIjhOYwbtuG4MptyEyquZB0TX8coeei+/cI6gt0+Yt1wDrP3 T4Cr6lsv1ua/1D4YhZeM3xLl0bFwwQjUy36fEJae1vUp9CVYaK5MwNBv7cCwcTxx3mVU dqWJd9rgeh0uyl5Ybq9+hOtMGw6OA9RTimtsUj6aCQK7Sq7tAYkl495mp9bjvYg7t/oD lxdddWdt0Bwn8GJZ+Z39h7OdR+ekXHbHDUgZV+McqrrEI92eohB+y7oPMxY9ywUO3d8i n5Ev/hjdwYBw30sF7hMMKUCHdzqt3usRKfksqifPj1O7eg6Idu5i/oWqAe7liNKJfEo1 I+MQ==
X-Received: by 10.66.249.101 with SMTP id yt5mr17039pac.116.1428646965693; Thu, 09 Apr 2015 23:22:45 -0700 (PDT)
Received: from [192.168.1.7] ([112.249.225.102]) by mx.google.com with ESMTPSA id jd5sm989577pbd.35.2015.04.09.23.22.44 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Apr 2015 23:22:45 -0700 (PDT)
References: <5526BC55.8020006@innovationslab.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <5526BC55.8020006@innovationslab.net>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable
Message-Id: <A81DBA34-FEB2-4568-BAED-59EFC8BE1CDA@gmail.com>
X-Mailer: iPhone Mail (10A551)
From: Qi Sun <sunqi.csnet.thu@gmail.com>
Date: Fri, 10 Apr 2015 14:18:58 +0800
To: Brian Haberman <brian@innovationslab.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/qAeT4Y1V_6dIsM72pnZrMOCfnfE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Question on draft-ietf-dhc-dynamic-shared-v4allocation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 06:22:47 -0000

Dear Brian,

Thanks a lot for the evaluation!=20

If I understand you correctly, the incompatibility is caused because this dr=
aft is defining a DHCPv4 option while draft-ietf-softwire-map-dhcp defines a=
 DHCPv6 option. But the meanings of the fields should be the same, which "is=
 to maintain compatibility with existing port set implementations". Consider=
ing the readability, we drew the Figure like this.

Do we need to reword the sentence to this:
"The DHCPv4 Port Parameters Option uses the similar fields ..."

?

Thank you very much,
Qi

Sent from my iPhone

=D4=DA 2015-4-10=A3=AC1:52=A3=ACBrian Haberman <brian@innovationslab.net> =D0=
=B4=B5=C0=A3=BA

> All,
>    I have begun my AD evaluation of
> draft-ietf-dhc-dynamic-shared-v4allocation and have a need for some
> clarification.  Section 8 of the draft says:
>=20
>   The DHCPv4 Port Parameters Option uses the same fields as the S46
>   Port Parameters Option described in Section 4.5 of
>   [I-D.ietf-softwire-map-dhcp], implemented as a DHCPv4 option.  This
>   is to maintain compatibility with existing port set implementations.
>=20
>   The format of OPTION_V4_PORTPARAMS is shown in Figure 1.
>=20
>                 0                             1
>                 0  1  2  3  4  5  6  7  8  9  0  1  2  3  4  5
>                +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>                |      option-code      |     option-len        |
>                +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>                |         offset        |       PSID-len        |
>                +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>                |                     PSID                      |
>                +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>=20
>                  Figure 1: DHCPv4 Port Parameters Option
>=20
>=20
> However, when I go and review the option defined in section 4.5 of
> draft-ietf-softwire-map-dhcp, I see an incompatible option format:
>=20
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |     OPTION_S46_PORTPARAMS     |         option-length         |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |   offset      |    PSID-len   |              PSID             |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>=20
>                   Figure 6: S46 Port Parameters Option
>=20
> Which is correct?
>=20
> Regards,
> Brian
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Fri Apr 10 01:19:57 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8D511B2ACF for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 01:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 0MyMa46LKnhk for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 01:19:55 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C18E01B2ACE for <dhcwg@ietf.org>; Fri, 10 Apr 2015 01:19:54 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3A8JpgP005439; Fri, 10 Apr 2015 10:19:51 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id EDA69204FC6; Fri, 10 Apr 2015 10:20:57 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DEE75204F25; Fri, 10 Apr 2015 10:20:57 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3A8JFam001280; Fri, 10 Apr 2015 10:19:51 +0200
Message-ID: <55278783.2070104@gmail.com>
Date: Fri, 10 Apr 2015 10:19:15 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/hg-nWxB6yoVbtVdz-2bUKeoEkBo>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 08:19:56 -0000

Le 09/04/2015 17:36, Lorenzo Colitti a Ã©crit :
> On Thu, Apr 9, 2015 at 11:57 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>     If the 3rd choice above is not done (specify that assigning an
>     address can be implemented by assigning a prefix of length /128)
>     then what else would in your opinion follow?
>
>     Or should we leave it there: non-existent implementations of true IPv6.
>
>
> As Ted keeps saying, what's important is not how you configure the
> implementation, but how it behaves.

I disagree: RFCs should specify behaviour. Programmer should use it as a
precise first-hand guide on how to implement. Some place for imagination
of the programmer should be left of course, and the spec language should
be independent of the programming language also.

Plen is not a thing to be left to imagination.

> If configuring an address on a host causes the host to think that the
> whole of the address' /64 is on link, then the host is behaving
> incorrectly. If configuring an address on a host does not cause the host
> to believe that any other addresses are on link, then the host is
> behaving correctly, regardless of whether the host displays the address
> as "2001:db8::1", "2001:db8::1/128",
> "2001:0db8:0:00:0:0:0000:00/onetwentyeight", or
> "20010db8000000000000000000000001 80".

I agree, address/plen this is just a notation, for when there is a
hidden prefix; and the address in itself does not have a plen associated.

But here I ask whether or not /128 is the correct prefix length to be
assumed when the prefix length is not specified?

You seem to say that /128 is the correct prefix length to be assumed
when a prefix length is not specified.

But I disagree with that: /128 is not the right prefix length to be
assumed when a prefix length is not specified.

Because, in one particular cellular deployment the RA does not provide
the plen, and the address is provided by DHCP. In this, one wants the
assumed plen to be /127 or shorter (and certainly not 128) because there
are two ends in that subnet (the Client and the Router). At times there
are 3 ends in that subnet (the Client and two Routers): then the 
assumed' plen should be /126 or shorter.

For these reasons, the plen should be told and not assumed.

Alex





From nobody Fri Apr 10 01:28:06 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76A401B2B0A for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 01:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.983
X-Spam-Level: 
X-Spam-Status: No, score=-6.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 OaPCBQpbCAGp for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 01:27:56 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C28DC1B2AFC for <dhcwg@ietf.org>; Fri, 10 Apr 2015 01:27:55 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3A8Rq7T009784; Fri, 10 Apr 2015 10:27:52 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id EBCED205000; Fri, 10 Apr 2015 10:28:58 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DDA50205025; Fri, 10 Apr 2015 10:28:58 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3A8RDcj023985; Fri, 10 Apr 2015 10:27:48 +0200
Message-ID: <55278961.4020709@gmail.com>
Date: Fri, 10 Apr 2015 10:27:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <3C0A02F8-C69C-43B6-84CD-4D36A73A0307@nominum.com>
In-Reply-To: <3C0A02F8-C69C-43B6-84CD-4D36A73A0307@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/xpb5vlXRNcWAcmeqg0k-yrGYsgc>
Cc: dhcwg@ietf.org, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 08:28:00 -0000

Le 09/04/2015 14:15, Ted Lemon a écrit :
> On Apr 9, 2015, at 7:42 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> This means that either there are no correct implementations of IPv6
>> out there, or that a prefix must always assigned when an address is
>> assigned.
>
> What makes an implementation correct or incorrect is not the details
>  of how it is implemented, but rather whether or not it conforms to
> the specification.   An implementation that treats an IPv6 address it
> receives from DHCPv6 as having no associated prefix length will
> behave correctly.   One that treats it as having an associated prefix
> length will not.

Both linux and bsd assume an associated prefix length.  Some dhclient too.

> So assuming that what you have said about FreeBSD is correct,
> FreeBSD will exhibit incorrect behavior in some situations, imputing
> reachability to addresses that are not reachable and failing to
> communicate with such hosts.

I agree.

> This is easy to test: set up two links each with a DHCP relay and a
> router that is advertising a default route but no prefixes, and that
>  is routing between the two links.   Have the DHCP server issue IP
> addresses to both links from the same /64 prefix.   Configure a Linux
> box and a FreeBSD box on each link with a DHCP client.   Now try to
> communicate between the two Linux boxes, between the two FreeBSD
> boxes, and between a Linux box on one link and a FreeBSD box on the
> other link.
>
> What you will see is that the Linux boxes will succeed in
> communicating, and the FreeBSD boxes will not be able to communicate
>  either with each other or with Linux boxes on the other link, but
> _will_ be able to communicate with the Linux box on the same link.
>
> So, again assuming that what you've reported about FreeBSD is
> correct, the FreeBSD box doesn't conform to the specification.

(fyi Steinar reported the bsd ifconfig, to be confirmed).

I would not blame BSD for that.  In some cases what BSD seems to be
doing (assume /64 instead of linux's /128 when no plen is given) makes
work ok other things which wouldnt work if it were assumed 128.

Also, if we are to take RFCs by letter, both BSD and linux violate
RFC5942 section 4 bullet 1 "MUST NOT implicitly cause a prefix
derived from that address to be treated as on-link and added to      the
Prefix List."

Linux violates that because linux too causes a prefix to be derived from
that address as it adds an entry to the rt table (in linux there are 2
entries in the rt table added: one for the real interface and one for
the loopback).

To me this is a point where it is not stacks (bsd or linux) that are in
error - they need something to put there and simply dont know what.

Alex

>
> All of this discussion about how Linux imputes a /128 and FreeBSD
> imputes a /64 is irrelevant, because you're talking about details of
>  how the stack is implemented, not about the _behavior_ of the
> stack.
>
>
>



From nobody Fri Apr 10 01:32:18 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD3FB1A9029 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 01:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 xLB4G7seLyOz for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 01:32:15 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 964841A8033 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 01:32:15 -0700 (PDT)
Received: by igblo3 with SMTP id lo3so87399850igb.1 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 01:32:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Za9GNAJrQI7uOqVL8NNm1SfXkzSqdNGQhPL7mvq9fMw=; b=b03FtaKjjmcVUsjYTyAE0A0HPczXlXulZUgPrUS3rntd9FZLCNccPMClmFZWTfkoLN Wt08DG2eeRbVAQQfR7BhxdjbetbGcqAshUhohwwcbaQ6mUXq4RPI1x7ka3+MOXfUauC6 I/N2DfShSD6ESHQTvPhGyvs1tI9rVWsrZ4IoyF59C7LSE89JQTHU+kTyU6CfmevsNaMn n/vZXAJjfnpj1cnCrNuq6NgGJwJ7oTAkbgsQPF+Ad65D1FhDj9QNuJv5eXtTEAGwOGKu Wjrx3bfSMEXumJVQnoOPvh5oFB4uJa26x/qZN6tpu9Z8PKetQ+xWoc+GqClHGv4GDgxT ugZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Za9GNAJrQI7uOqVL8NNm1SfXkzSqdNGQhPL7mvq9fMw=; b=iN0XxkNKF2uDB90tIuN3bOUPOMrtiXJO4HRg6IKFOzM9yY92ksmODzx39J7+81feoG 1UOHgiHOhJ1dcV/lAbpoGJBz4ZeL+SAxa+287411eXoj4ILPt8zixHwZVl1I+kvqAjRS hMjiVXXP+nYNIHuTzYrWDZ+9CHSeBLJZzsRnpOEejkEOhQOefcC23EctNW3Dc23QUrMf tmn2CK/FzymDMPE0en1fVY5VE52jyMJ9z4qmZJenH67C3yH5ImxirgFEFrIbc8vbPwn9 0j+qlHdg6/PvNdGlDG2yDh1yEMW3Nug8X/irzgggfcQl6ZmFl8ARq7A0ogfFxixgC3Bj b7AA==
X-Gm-Message-State: ALoCoQkWHCggAXe+15NTPpL7IcIeXUaz1Ep4S8qC2m1oqLIDDNZ63FTvi625PE7Mj34FfBFokd2r
X-Received: by 10.43.72.138 with SMTP id yo10mr2036791icb.69.1428654734855; Fri, 10 Apr 2015 01:32:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Fri, 10 Apr 2015 01:31:54 -0700 (PDT)
In-Reply-To: <55278783.2070104@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 10 Apr 2015 17:31:54 +0900
Message-ID: <CAKD1Yr0WkNxoTDfudyYDNAnD7SxmsHXpLZq9PHtJrO5p_SgqTw@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c204fefa746c05135a99d5
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/OuhFPuYTYv0IlIiBxkwnWN-hZw8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 08:32:17 -0000

--001a11c204fefa746c05135a99d5
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 10, 2015 at 5:19 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> I agree, address/plen this is just a notation, for when there is a
>
hidden prefix; and the address in itself does not have a plen associated.
>
> But here I ask whether or not /128 is the correct prefix length to be
> assumed when the prefix length is not specified?
>

Yes, it is the correct prefix length. It is correct because it is the only
prefix length that includes nothing except the address itself. Thus, it is
the only prefix length that conforms with RFC 5942 section 4.1:

       assignment of an IPv6 address [...] MUST NOT implicitly cause a
prefix
       derived from that address to be treated as on-link and added to
       the Prefix List.

Because, in one particular cellular deployment the RA does not provide
> the plen, and the address is provided by DHCP. In this, one wants the
> assumed plen to be /127 or shorter (and certainly not 128) because there
> are two ends in that subnet (the Client and the Router). At times there
> are 3 ends in that subnet (the Client and two Routers): then the assumed'
> plen should be /126 or shorter.
>

In that deployment you will need to find a way to add an on-link prefix.
Unlike DHCPv4, DHCPv6 does not do this and has never done this. You can do
this with an RA containing a Prefix Information option with L=1, A=0; the
relevant text in RFC 4861 is:

   [ADDRCONF] may impose certain restrictions on the prefix length for
   address configuration purposes.  Therefore, the prefix might be
   rejected by [ADDRCONF] implementation in the host.  However, the
   prefix length is still valid for on-link determination when combined
   with other flags in the prefix option.

--001a11c204fefa746c05135a99d5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Apr 10, 2015 at 5:19 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petr=
escu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rg=
b(204,204,204);border-left-style:solid;padding-left:1ex">I agree, address/p=
len this is just a notation, for when there is a<br></blockquote><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width=
:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-lef=
t:1ex">
hidden prefix; and the address in itself does not have a plen associated.<b=
r>
<br>
But here I ask whether or not /128 is the correct prefix length to be<br>
assumed when the prefix length is not specified?<br></blockquote><div><br><=
/div><div>Yes, it is the correct prefix length. It is correct because it is=
 the only prefix length that includes nothing except the address itself. Th=
us, it is the only prefix length that conforms with RFC 5942 section 4.1:</=
div><div><br></div><div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0assignment of an IP=
v6 address [...] MUST NOT implicitly cause a prefix</div><div>=C2=A0 =C2=A0=
 =C2=A0 =C2=A0derived from that address to be treated as on-link and added =
to</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the Prefix List.</div></div><div><b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style=
:solid;padding-left:1ex">Because, in one particular cellular deployment the=
 RA does not provide<br>
the plen, and the address is provided by DHCP. In this, one wants the<br>
assumed plen to be /127 or shorter (and certainly not 128) because there<br=
>
are two ends in that subnet (the Client and the Router). At times there<br>
are 3 ends in that subnet (the Client and two Routers): then the assumed&#3=
9; plen should be /126 or shorter.<br></blockquote><div><br></div><div>In t=
hat deployment you will need to find a way to add an on-link prefix. Unlike=
 DHCPv4, DHCPv6 does not do this and has never done this. You can do this w=
ith an RA containing a Prefix Information option with L=3D1, A=3D0; the rel=
evant text in RFC 4861 is:</div><div><br></div><div><div>=C2=A0 =C2=A0[ADDR=
CONF] may impose certain restrictions on the prefix length for</div><div>=
=C2=A0 =C2=A0address configuration purposes.=C2=A0 Therefore, the prefix mi=
ght be</div><div>=C2=A0 =C2=A0rejected by [ADDRCONF] implementation in the =
host.=C2=A0 However, the</div><div>=C2=A0 =C2=A0prefix length is still vali=
d for on-link determination when combined<br></div><div>=C2=A0 =C2=A0with o=
ther flags in the prefix option.</div></div></div></div></div>

--001a11c204fefa746c05135a99d5--


From nobody Fri Apr 10 01:41:30 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63D6A1A1A34 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 01:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, 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 5aZC_1RAWITm for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 01:41:26 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id EB72B1A19FE for <dhcwg@ietf.org>; Fri, 10 Apr 2015 01:41:25 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 549861BC3E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 08:41:21 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <55278783.2070104@gmail.com>
Date: Fri, 10 Apr 2015 09:41:21 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/r61SPezNh1cRC1g9SrO4VoSq9x8>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 08:41:28 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> But here I ask whether or not /128 is the correct prefix length to be
> assumed when the prefix length is not specified?
>=20
> You seem to say that /128 is the correct prefix length to be assumed
> when a prefix length is not specified.
>=20
> But I disagree with that: /128 is not the right prefix length to be
> assumed when a prefix length is not specified.
>=20
> Because, in one particular cellular deployment the RA does not provide
> the plen, and the address is provided by DHCP. In this, one wants the
> assumed plen to be /127 or shorter (and certainly not 128) because =
there
> are two ends in that subnet (the Client and the Router). At times =
there
> are 3 ends in that subnet (the Client and two Routers): then the =
assumed' plen should be /126 or shorter.
>=20
> For these reasons, the plen should be told and not assumed.

You still don't make a case for the spec being wrong.
Why doesn't the RA contain a prefix length ?
Why can't the implementation work without it ?

Without going and having a detailed read (I'm supposed to be at work !), =
if a device gets an RA is it allowed to assume that the router it gets =
it from is on-link for the interface it received the RA on ? If the spec =
doesn't allow for that then it needs changing, but otherwise getting an =
RA is sufficient for the client to communicate - regardless of the IPs =
on the client and router (they do **NOT** have to be in the same prefix, =
unlike IPv4).

It looks like you still have not grasped the fundamental difference that =
in the IPv6 world "address + prefix length does not equal reachability =
information" and "in same prefix" is absolutely not required for two =
devices to directly communicate.



Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> I would not blame BSD for that.  In some cases what BSD seems to be
> doing (assume /64 instead of linux's /128 when no plen is given) makes
> work ok other things which wouldnt work if it were assumed 128.
>=20
> Also, if we are to take RFCs by letter, both BSD and linux violate
> RFC5942 section 4 bullet 1 "MUST NOT implicitly cause a prefix
> derived from that address to be treated as on-link and added to      =
the
> Prefix List."
>=20
> Linux violates that because linux too causes a prefix to be derived =
from
> that address as it adds an entry to the rt table (in linux there are 2
> entries in the rt table added: one for the real interface and one for
> the loopback).
>=20
> To me this is a point where it is not stacks (bsd or linux) that are =
in
> error - they need something to put there and simply dont know what.

Yes they are in error. As previously pointed out, the logical approach =
would have been to refactor the IPv4 code - thus dragging along legacy =
assumptions for the ride.
The "easy fix" would be to force all addresses to be /128 - then the =
incorrect operations (adding a route entry for the prefix) becomes a =
null operation. That's an easy fix for the DHCP client - just add a /128 =
prefix length to keep the tools happy.

Going back to your example, if the client assumed a /64 prefix - could =
one mobile device then talk *directly* to any other mobile device in =
that prefix ? If not sending the packet to the router, but just doing ND =
to find the other device on the *broadcast* network.
I assume the answer is no. And that's the issue this "don't assume =
(direct) reachability" bit is there to fix - not all networks support =
end-device to end-device communications even if they are in the same =
prefix. It's directly mentioned in the pre-amble to both the RFCs that =
have been previously mentioned.




From nobody Fri Apr 10 02:02:32 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93FE31A8A9A for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 02:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 O_f9_WhN5vUD for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 02:02:29 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBB341A8F48 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 02:02:28 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id BF642A1; Fri, 10 Apr 2015 11:02:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1428656545; bh=T1bvY26auHN9XogbMyUaI/g7nlANBy9IMRYG9390DF4=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=I83Nni3dGUAOFvCoD9VGOrZgnLdHw4pWi5OEX+M0oZp18dWIlqj+ZUh30GRNFmhkq I6va4Tq9hYsriqi1K1pwy6UeprpW+ghLw7kPHZQu1dZ/o2P3yaVb8+/YbuwEWlklsH vijdD/K5S6/+mU89QPU9IlIrSCD7pBnHgLFk0ZD4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id BACF09F; Fri, 10 Apr 2015 11:02:25 +0200 (CEST)
Date: Fri, 10 Apr 2015 11:02:25 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk>
Message-ID: <alpine.DEB.2.02.1504101056260.9531@uplift.swm.pp.se>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Tsb3dnUmTJ6bHDmIAarRJtUSrqc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 09:02:30 -0000

On Fri, 10 Apr 2015, Simon Hobson wrote:

> Why doesn't the RA contain a prefix length ?
> Why can't the implementation work without it ?

Any valid IPv6 with DHCPv6 support implementation should work correctly in 
the face of the following:

RA received with no on-link prefix, with M=1.
IA_NA asked for and received.

Now, the client should have an address on the interace, answer ND 
reachability questions for this address, and then if it needs to send 
traffic, send all of it to the default gw implied by the RA received.

On the gateway, there is a /something configured (that matches the DHCPv6 
IA_NA scope) so the router has no problem to send traffic to multiple 
devices on its interface. I just doesn't announce this /something as being 
on-link. None of these devices will try to send traffic to each other 
unless the router is configured to send ICMPv6 redirects (which in this 
scenario is unlikely because the reason for the setup would be that one 
actually wants all traffic to go via the router for some reason).

"ip -6 r l" on the IA_NA device would most likely (it was 3-4 years since 
I did this last so I don't remember exactly) show a /128 on the interface 
and a default route towards the default gateway learnt from RA.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Apr 10 02:32:17 2015
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A64D21AD0CF for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 02:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.451
X-Spam-Level: 
X-Spam-Status: No, score=0.451 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_CHARSET_FARAWAY=2.45, MIME_QP_LONG_LINE=0.001, 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 6rToSm88syhY for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 02:32:13 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9DF71AD0B2 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 02:32:13 -0700 (PDT)
Received: by pabsx10 with SMTP id sx10so16413120pab.3 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 02:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=QUsj22mJHfNYJsjtJury73MFr7SzGTljeP6veUYWMJQ=; b=oFiKMswP3UcfNXWYWmf+8YMhFTUn2CFPMksIGu1guPRCXJGSXKkdH93qTjEtymQ+/5 GSWgPW/UuhfCECSaR6vL4AdZNrrqvUKXZ0HpeL3QCE2jrHx0jO4PRdR7TLK91a3zyLUw JmQfxovovm0DDWLEgudpbS0Aq4rAJnDhXSPR5uxNyO94xtb+BW/H/lwhuL/xtOFWjHyW y6ISJAuId13KuhXWWAfAYLaKQ6JqMgPV6+H9J8ysugi5NmMtnmnemrJgzesAO+IKcEGc 0+OLopNyvADwn0Hi5JDB/ZHnReAQNQqqVw1gWUfQLdui/yDrF6ydIkMLlFL/TgqfATFt +Y7Q==
X-Received: by 10.68.65.66 with SMTP id v2mr1198069pbs.10.1428658333519; Fri, 10 Apr 2015 02:32:13 -0700 (PDT)
Received: from [192.168.1.7] ([112.249.225.102]) by mx.google.com with ESMTPSA id iz2sm1611474pbc.37.2015.04.10.02.32.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 10 Apr 2015 02:32:12 -0700 (PDT)
References: <5526BC55.8020006@innovationslab.net> <A81DBA34-FEB2-4568-BAED-59EFC8BE1CDA@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <A81DBA34-FEB2-4568-BAED-59EFC8BE1CDA@gmail.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable
Message-Id: <47A5238E-0081-4E78-881F-14722FEE801A@gmail.com>
X-Mailer: iPhone Mail (10A551)
From: Qi Sun <sunqi.csnet.thu@gmail.com>
Date: Fri, 10 Apr 2015 17:29:52 +0800
To: Brian Haberman <brian@innovationslab.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/FB5wcw4QkpvMuAHllNTdGrES6gw>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Question on draft-ietf-dhc-dynamic-shared-v4allocation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 09:32:15 -0000

Dear Brian,

After a second thought, the comment seems valid. The intention of that text w=
as that the meaning of those fields is the same, not the exact format. Howev=
er, the wording there is a little confusing.=20

So how about the following change:

OLD:
  The DHCPv4 Port Parameters Option uses the same fields as the S46
  Port Parameters Option described in Section 4.5 of
  [I-D.ietf-softwire-map-dhcp], implemented as a DHCPv4 option.  This
  is to maintain compatibility with existing port set implementations.

NEW:=20
The meaning of 'offset', 'PSID-len', and 'PSID' fields of the DHCPv4 Port Pa=
rameters Option is identical to that of 'offset', 'PSID-len', and 'PSID' fie=
lds of the S46 Port Parameters Option (Section 4.5 of [I-D.ietf-softwire-map=
-dhcp]). The use of the same encoding in both options is meant to ensure com=
patibility with existing port set implementations.

Would that be clearer?

Thanks,
Qi

Sent from my iPhone

=D4=DA 2015-4-10=A3=AC14:18=A3=ACQi Sun <sunqi.csnet.thu@gmail.com> =D0=B4=B5=
=C0=A3=BA

> Dear Brian,
>=20
> Thanks a lot for the evaluation!=20
>=20
> If I understand you correctly, the incompatibility is caused because this d=
raft is defining a DHCPv4 option while draft-ietf-softwire-map-dhcp defines a=
 DHCPv6 option. But the meanings of the fields should be the same, which "is=
 to maintain compatibility with existing port set implementations". Consider=
ing the readability, we drew the Figure like this.
>=20
> Do we need to reword the sentence to this:
> "The DHCPv4 Port Parameters Option uses the similar fields ..."
>=20
> ?
>=20
> Thank you very much,
> Qi
>=20
> Sent from my iPhone
>=20
> =D4=DA 2015-4-10=A3=AC1:52=A3=ACBrian Haberman <brian@innovationslab.net> =D0=
=B4=B5=C0=A3=BA
>=20
>> All,
>>   I have begun my AD evaluation of
>> draft-ietf-dhc-dynamic-shared-v4allocation and have a need for some
>> clarification.  Section 8 of the draft says:
>>=20
>>  The DHCPv4 Port Parameters Option uses the same fields as the S46
>>  Port Parameters Option described in Section 4.5 of
>>  [I-D.ietf-softwire-map-dhcp], implemented as a DHCPv4 option.  This
>>  is to maintain compatibility with existing port set implementations.
>>=20
>>  The format of OPTION_V4_PORTPARAMS is shown in Figure 1.
>>=20
>>                0                             1
>>                0  1  2  3  4  5  6  7  8  9  0  1  2  3  4  5
>>               +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>>               |      option-code      |     option-len        |
>>               +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>>               |         offset        |       PSID-len        |
>>               +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>>               |                     PSID                      |
>>               +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>>=20
>>                 Figure 1: DHCPv4 Port Parameters Option
>>=20
>>=20
>> However, when I go and review the option defined in section 4.5 of
>> draft-ietf-softwire-map-dhcp, I see an incompatible option format:
>>=20
>>     0                   1                   2                   3
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |     OPTION_S46_PORTPARAMS     |         option-length         |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |   offset      |    PSID-len   |              PSID             |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>=20
>>                  Figure 6: S46 Port Parameters Option
>>=20
>> Which is correct?
>>=20
>> Regards,
>> Brian
>>=20
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Fri Apr 10 02:50:04 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1B71B2B2D for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 02:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 Y4AU6Tng6NhX for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 02:50:00 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74F551B2B28 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 02:50:00 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3A9nuL2013569; Fri, 10 Apr 2015 11:49:56 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BA1152051B9; Fri, 10 Apr 2015 11:51:03 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id AC57C2050E2; Fri, 10 Apr 2015 11:51:03 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3A9nRIf022446; Fri, 10 Apr 2015 11:49:56 +0200
Message-ID: <55279CA7.3010400@gmail.com>
Date: Fri, 10 Apr 2015 11:49:27 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <CAKD1Yr0WkNxoTDfudyYDNAnD7SxmsHXpLZq9PHtJrO5p_SgqTw@mail.gmail.com>
In-Reply-To: <CAKD1Yr0WkNxoTDfudyYDNAnD7SxmsHXpLZq9PHtJrO5p_SgqTw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/d35IEq77mJc7tiblqL4NRFKEhKU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 09:50:02 -0000

Le 10/04/2015 10:31, Lorenzo Colitti a Ã©crit :
> On Fri, Apr 10, 2015 at 5:19 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>     I agree, address/plen this is just a notation, for when there is a
>
>     hidden prefix; and the address in itself does not have a plen
>     associated.
>
>     But here I ask whether or not /128 is the correct prefix length to be
>     assumed when the prefix length is not specified?
>
>
> Yes, it is the correct prefix length. It is correct because it is the
> only prefix length that includes nothing except the address itself.
> Thus, it is the only prefix length that conforms with RFC 5942 section 4.1:
>
>         assignment of an IPv6 address [...] MUST NOT implicitly cause a
> prefix
>         derived from that address to be treated as on-link and added to
>         the Prefix List.
>
>     Because, in one particular cellular deployment the RA does not provide
>     the plen, and the address is provided by DHCP. In this, one wants the
>     assumed plen to be /127 or shorter (and certainly not 128) because there
>     are two ends in that subnet (the Client and the Router). At times there
>     are 3 ends in that subnet (the Client and two Routers): then the
>     assumed' plen should be /126 or shorter.
>
>
> In that deployment you will need to find a way to add an on-link prefix.
> Unlike DHCPv4, DHCPv6 does not do this and has never done this.

Why?

Does DHCPv6 know that sometimes RA is not usable at all?

> You can
> do this with an RA containing a Prefix Information option with L=1, A=0;
> the relevant text in RFC 4861 is:
>
>     [ADDRCONF] may impose certain restrictions on the prefix length for
>     address configuration purposes.  Therefore, the prefix might be
>     rejected by [ADDRCONF] implementation in the host.  However, the
>     prefix length is still valid for on-link determination when combined
>     with other flags in the prefix option.

Things are not that simple.

In that deployment there are two RAs each issued by a different router, 
on a same link.  One RA contains the prefix of the link (plen 64).  But 
it is sent only once when the link is put up and never again.

Soliciting an RA leads to the 2nd router responding, and that second RA 
contains no prefix.

These RAs are not sent periodically, just once at the beginning, and 
when solicited.  There are reasons for it to act so, e.g. avoid channel 
occupancy and others.

But DHCPv4 and DHCPv6 respond ok to all kinds of DHCP messages.  Were 
DHCPv6 to provide the plen all could be fine.

Alex


From nobody Fri Apr 10 03:18:43 2015
Return-Path: <sthaug@nethelp.no>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 566E31B2B93 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 03:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 P4Tl3_b0h_g1 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 03:18:39 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id 810021B2B92 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 03:18:38 -0700 (PDT)
Received: (qmail 3335 invoked from network); 10 Apr 2015 10:18:36 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 10 Apr 2015 10:18:36 -0000
Date: Fri, 10 Apr 2015 12:18:36 +0200 (CEST)
Message-Id: <20150410.121836.74655364.sthaug@nethelp.no>
To: alexandru.petrescu@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <55279CA7.3010400@gmail.com>
References: <55278783.2070104@gmail.com> <CAKD1Yr0WkNxoTDfudyYDNAnD7SxmsHXpLZq9PHtJrO5p_SgqTw@mail.gmail.com> <55279CA7.3010400@gmail.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/dhcwg/Wpy8aq4JBzOUANU3hn-vbdrImRw>
Cc: dhcwg@ietf.org, rdroms.ietf@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 10:18:42 -0000

> > In that deployment you will need to find a way to add an on-link prefix.
> > Unlike DHCPv4, DHCPv6 does not do this and has never done this.
> 
> Why?
> 
> Does DHCPv6 know that sometimes RA is not usable at all?

DHCPv6 was designed to be dependent on RA. You may disagree about
that decision (I certainly do) - but that's the situation today.

Steinar Haug, AS 2116


From nobody Fri Apr 10 03:31:22 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 039261B2BBC for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 03:31:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 coVfxc_EalSq for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 03:31:18 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24D881B2BAB for <dhcwg@ietf.org>; Fri, 10 Apr 2015 03:31:17 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3AAVEaP000375; Fri, 10 Apr 2015 12:31:14 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 969032050DC; Fri, 10 Apr 2015 12:32:21 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 7CDB0200D9F; Fri, 10 Apr 2015 12:32:21 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3AAUq4C010158; Fri, 10 Apr 2015 12:31:14 +0200
Message-ID: <5527A65C.3020008@gmail.com>
Date: Fri, 10 Apr 2015 12:30:52 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: sthaug@nethelp.no
References: <55278783.2070104@gmail.com>	<CAKD1Yr0WkNxoTDfudyYDNAnD7SxmsHXpLZq9PHtJrO5p_SgqTw@mail.gmail.com>	<55279CA7.3010400@gmail.com> <20150410.121836.74655364.sthaug@nethelp.no>
In-Reply-To: <20150410.121836.74655364.sthaug@nethelp.no>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/18AQZUbwztDZ7PI6sk7SEFaKtlQ>
Cc: dhcwg@ietf.org, rdroms.ietf@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 10:31:20 -0000

Le 10/04/2015 12:18, sthaug@nethelp.no a écrit :
>>> In that deployment you will need to find a way to add an on-link
>>> prefix. Unlike DHCPv4, DHCPv6 does not do this and has never
>>> done this.
>>
>> Why?
>>
>> Does DHCPv6 know that sometimes RA is not usable at all?
>
> DHCPv6 was designed to be dependent on RA.

But it was not designed to work when RA itself fails.

For example, Prefix Information Option (PIO) is just an option to be in
RA.  Some RAs carry it but others dont.

Other parameters in RA like lifetime values, curr hop limit, are always
there (not optional).

Whatever is optionally absent in RA should be optionally present in
DHCP, otherwise the whole design fails.

> You may disagree about that decision (I certainly do) - but that's
> the situation today.

It is not a happy situation to be in.

Alex

>
> Steinar Haug, AS 2116
>
>



From nobody Fri Apr 10 04:14:44 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 853161B2C02 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 04:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.983
X-Spam-Level: 
X-Spam-Status: No, score=-6.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 17MOeVZeMUEG for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 04:14:39 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 131B71B2C53 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 04:14:37 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3ABEZ4e011289 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:14:35 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8DC1F20A343 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:15:42 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 85D5F20A328 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:15:42 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3ABE8Gv019386 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:14:35 +0200
Message-ID: <5527B080.6010201@gmail.com>
Date: Fri, 10 Apr 2015 13:14:08 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk>
In-Reply-To: <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/YicRF9SaO4_5YFW7LYR07pgb694>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 11:14:41 -0000

Le 10/04/2015 10:41, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>> But here I ask whether or not /128 is the correct prefix length to
>> be assumed when the prefix length is not specified?
>>
>> You seem to say that /128 is the correct prefix length to be
>> assumed when a prefix length is not specified.
>>
>> But I disagree with that: /128 is not the right prefix length to be
>> assumed when a prefix length is not specified.
>>
>> Because, in one particular cellular deployment the RA does not
>> provide the plen, and the address is provided by DHCP. In this,
>> one wants the assumed plen to be /127 or shorter (and certainly
>> not 128) because there are two ends in that subnet (the Client and
>> the Router). At times there are 3 ends in that subnet (the Client
>> and two Routers): then the assumed' plen should be /126 or
>> shorter.
>>
>> For these reasons, the plen should be told and not assumed.
>
> You still don't make a case for the spec being wrong. Why doesn't
> the RA contain a prefix length ?

Because the sysadmin did not put one there.

There are two RAs on this link, coming from two different routers.

The first RA is sent only once, when the interface comes up.  It does
not contain plen.  Never again later.

The second RA is sent unicast whenever solicited, but contains no prefix.

There are reasons to be so.  One that I can imagine is that it takes
less bandwidth (the RA containing a prefix is two times larger than w/o
a prefix).  There are other reasons there, but that's the way it is.

> Why can't the implementation work without it ?

The current implementation uses dhclient to acquire an address.  DHCPv6
does not provide a plen.  That dhclient thus uses a plen to be 64.  That
64 breaks RFC5942 section 4 bullet 1.  The plen is a must when adding an
address on an interface.

Other implementations prefer plen 128 instead of 64.  That 128 breaks a
neighboring relationship: the host does find a neighbor in its rt table
while the neighbor routers are there.

> Without going and having a detailed read (I'm supposed to be at work
> !), if a device gets an RA is it allowed to assume that the router
> it gets it from is on-link for the interface it received the RA on ?

Yes.  For that to work it will need to add an entry in its routing table
to tell it so.  That is happily the default route.  This is ok.

> If the spec doesn't allow for that then it needs changing, but
> otherwise getting an RA is sufficient for the client to communicate
> - regardless of the IPs on the client and router (they do **NOT**
> have to be in the same prefix, unlike IPv4).

Yes, it is sufficient to communicate with that router and with the 
Internet, if that's a default route.

The problem is not there.

The problem is that the RA does not contain a prefix, and the address is 
given by DHCP w/o a plen.

> It looks like you still have not grasped the fundamental difference
> that in the IPv6 world "address + prefix length does not equal
> reachability information" and "in same prefix" is absolutely not
> required for two devices to directly communicate.

YEs, and I refuse maybe to grasp it.

The reason is that IPv6 must work as IPv4 as much as possible.

If this plen were such a bad thing then why dont we remove it from 
DHCPv4?  IPv4 RA could deliver it instead.

Alex


>
>
>
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>> I would not blame BSD for that.  In some cases what BSD seems to be
>> doing (assume /64 instead of linux's /128 when no plen is given)
>> makes work ok other things which wouldnt work if it were assumed
>> 128.
>>
>> Also, if we are to take RFCs by letter, both BSD and linux violate
>>  RFC5942 section 4 bullet 1 "MUST NOT implicitly cause a prefix
>> derived from that address to be treated as on-link and added to the
>> Prefix List."
>>
>> Linux violates that because linux too causes a prefix to be
>> derived from that address as it adds an entry to the rt table (in
>> linux there are 2 entries in the rt table added: one for the real
>> interface and one for the loopback).
>>
>> To me this is a point where it is not stacks (bsd or linux) that
>> are in error - they need something to put there and simply dont
>> know what.
>
> Yes they are in error. As previously pointed out, the logical
> approach would have been to refactor the IPv4 code - thus dragging
> along legacy assumptions for the ride. The "easy fix" would be to
> force all addresses to be /128 - then the incorrect operations
> (adding a route entry for the prefix) becomes a null operation.
> That's an easy fix for the DHCP client - just add a /128 prefix
> length to keep the tools happy.
>
> Going back to your example, if the client assumed a /64 prefix -
> could one mobile device then talk *directly* to any other mobile
> device in that prefix ? If not sending the packet to the router, but
> just doing ND to find the other device on the *broadcast* network. I
> assume the answer is no. And that's the issue this "don't assume
> (direct) reachability" bit is there to fix - not all networks
> support end-device to end-device communications even if they are in
> the same prefix. It's directly mentioned in the pre-amble to both the
> RFCs that have been previously mentioned.
>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Fri Apr 10 04:16:54 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF7FE1B2C5E for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 04:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 n25k_sDd7UIC for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 04:16:51 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38E501B2C5A for <dhcwg@ietf.org>; Fri, 10 Apr 2015 04:16:51 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3ABGnsO015144 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:16:49 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0A05520A3B9 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:17:56 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 04A2C20A31C for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:17:56 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3ABGmaB020831 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:16:49 +0200
Message-ID: <5527B120.4070706@gmail.com>
Date: Fri, 10 Apr 2015 13:16:48 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk>
In-Reply-To: <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/UeJSBgs0ieYtA2Iiv7fgvKKGQU0>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 11:16:53 -0000

Le 10/04/2015 10:41, Simon Hobson a écrit :
[...]
> That's an easy fix for the DHCP client - just add a /128 prefix
> length to keep the tools happy.

I would not agree with that either.

/128 plen on an address makes no sense.  There are neighbors to that 
address on that interface; their common prefix should be used instead of 
/128.

/128 is a hack which works in some cases.

Alex

>
> Going back to your example, if the client assumed a /64 prefix -
> could one mobile device then talk *directly* to any other mobile
> device in that prefix ? If not sending the packet to the router, but
> just doing ND to find the other device on the *broadcast* network. I
> assume the answer is no. And that's the issue this "don't assume
> (direct) reachability" bit is there to fix - not all networks support
> end-device to end-device communications even if they are in the same
> prefix. It's directly mentioned in the pre-amble to both the RFCs
> that have been previously mentioned.
>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Fri Apr 10 04:55:50 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07D4C1B2CCC for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 04:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 JkcWMpA1SrQM for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 04:55:49 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 ED9F81B2CCE for <dhcwg@ietf.org>; Fri, 10 Apr 2015 04:55:48 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 9AEE9DA00BA; Fri, 10 Apr 2015 11:55:48 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 10 Apr 2015 04:55:42 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <55278783.2070104@gmail.com>
Date: Fri, 10 Apr 2015 07:55:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jwWRqHEP4dpGgS0d0d4gnGJPGqo>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 11:55:50 -0000

On Apr 10, 2015, at 4:19 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
>> As Ted keeps saying, what's important is not how you configure the
>> implementation, but how it behaves.
>=20
> I disagree: RFCs should specify behaviour. Programmer should use it as =
a
> precise first-hand guide on how to implement. Some place for =
imagination
> of the programmer should be left of course, and the spec language =
should
> be independent of the programming language also.

The RFCs specify the behavior of the host on the network, not the user =
interface of the host.   You are trying to argue about a user interface =
issue here.


From nobody Fri Apr 10 04:59:56 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67F2F1B2CD2 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 04:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 yt9qlhRWX4KY for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 04:59:54 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 7ABF51B2CCC for <dhcwg@ietf.org>; Fri, 10 Apr 2015 04:59:54 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 5C1FFDA00BA; Fri, 10 Apr 2015 11:59:54 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 10 Apr 2015 04:59:53 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <5527A65C.3020008@gmail.com>
Date: Fri, 10 Apr 2015 07:59:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <0FD16EA9-BBDF-48FE-97F5-82BA07527806@nominum.com>
References: <55278783.2070104@gmail.com>	<CAKD1Yr0WkNxoTDfudyYDNAnD7SxmsHXpLZq9PHtJrO5p_SgqTw@mail.gmail.com>	<55279CA7.3010400@gmail.com> <20150410.121836.74655364.sthaug@nethelp.no> <5527A65C.3020008@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/YWc6lG1ybvkDPj2vHDbgMgdcQDM>
Cc: dhcwg@ietf.org, rdroms.ietf@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 11:59:55 -0000

On Apr 10, 2015, at 6:30 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
> For example, Prefix Information Option (PIO) is just an option to be =
in
> RA.  Some RAs carry it but others dont.

It is a valid configuration for the router not to advertise any prefixes =
on the link, but just a default route.   It's not only valid, but =
potentially useful.   Referring to this as a configuration error or as =
"when the RA itself fails" is precisely the disconnect we seem to be =
having.


From nobody Fri Apr 10 05:22:29 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 931C91B2E27 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 LYihsu5nCMrJ for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:22:27 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEA651B2E1A for <dhcwg@ietf.org>; Fri, 10 Apr 2015 05:22:26 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3ACMOPO010505; Fri, 10 Apr 2015 14:22:24 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 02CEB20A4BC; Fri, 10 Apr 2015 14:23:31 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DD2E020A3D1; Fri, 10 Apr 2015 14:23:30 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3ACLxOJ029227; Fri, 10 Apr 2015 14:22:23 +0200
Message-ID: <5527C067.60900@gmail.com>
Date: Fri, 10 Apr 2015 14:21:59 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <55278783.2070104@gmail.com>	<CAKD1Yr0WkNxoTDfudyYDNAnD7SxmsHXpLZq9PHtJrO5p_SgqTw@mail.gmail.com>	<55279CA7.3010400@gmail.com> <20150410.121836.74655364.sthaug@nethelp.no> <5527A65C.3020008@gmail.com> <0FD16EA9-BBDF-48FE-97F5-82BA07527806@nominum.com>
In-Reply-To: <0FD16EA9-BBDF-48FE-97F5-82BA07527806@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/qujL64Yo1HNcGrjD5fTkecmms8A>
Cc: dhcwg@ietf.org, rdroms.ietf@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 12:22:28 -0000

Le 10/04/2015 13:59, Ted Lemon a écrit :
> On Apr 10, 2015, at 6:30 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> For example, Prefix Information Option (PIO) is just an option to
>> be in RA.  Some RAs carry it but others dont.
>
> It is a valid configuration for the router not to advertise any
> prefixes on the link, but just a default route.

That (the default route) is not mandatory in RA either.

> It's not only valid, but potentially useful.   Referring to this as a
> configuration error or as "when the RA itself fails" is precisely the
> disconnect we seem to be having.

I meant to say that cases where RA does to offer what the Host expects.

Alex

>
>
>



From nobody Fri Apr 10 05:27:46 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F7251B2D52 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 uV_Jp8JI82Ct for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:27:43 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8FF51A0370 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 05:27:42 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3ACRcXq007123; Fri, 10 Apr 2015 14:27:38 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A1C7420A509; Fri, 10 Apr 2015 14:28:45 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 84D7F20A47E; Fri, 10 Apr 2015 14:28:45 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3ACRbMR005246; Fri, 10 Apr 2015 14:27:38 +0200
Message-ID: <5527C1B9.4010304@gmail.com>
Date: Fri, 10 Apr 2015 14:27:37 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com>
In-Reply-To: <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/0tboN3augUc5R5cJcVc5POkTFZg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 12:27:44 -0000

Le 10/04/2015 13:55, Ted Lemon a écrit :
> On Apr 10, 2015, at 4:19 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>>> As Ted keeps saying, what's important is not how you configure
>>> the implementation, but how it behaves.
>>
>> I disagree: RFCs should specify behaviour. Programmer should use
>> it as a precise first-hand guide on how to implement. Some place
>> for imagination of the programmer should be left of course, and
>> the spec language should be independent of the programming
>> language also.
>
> The RFCs specify the behavior of the host on the network, not the
> user interface of the host.   You are trying to argue about a user
> interface issue here.

This is not just UI here.

An /128 entry in a routing table for an address assigned by DHCP makes
no sense.  A rt entry is made to be compared with a dst address, not
with a src address.

Alex

>
>
>



From nobody Fri Apr 10 05:27:56 2015
Return-Path: <shemant@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCDB1B307A for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 qr7MGEewLnIn for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:27:53 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 471F51B2F9C for <dhcwg@ietf.org>; Fri, 10 Apr 2015 05:27:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=591; q=dns/txt; s=iport; t=1428668873; x=1429878473; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Xso85KHXXqWUy6rxQqhJWZflCKmiO8d2PUoRHwMfRTQ=; b=HP2K3w7AHqjdJw1K8CM+fdov8Yg4xhrWrwP8otZBlXc1XrBGNZiqWL8N NUc7h8QFQaK8r5TDRpm+SR5A/4xm6UNO9UtplBxkotJJcwNnGttVpyHvk IzI7iULk6hfD7cTt4OPM6y1mSIBWJsrCJMYRGjar2qO7M9Ec958Ue3Cnm A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BaBABrwSdV/5tdJa1cgwyBLgXEXgmHTwKBPDgUAQEBAQEBAX2EHwEBAQMBOj8FBwQCAQgRBAEBCxQJByERFAkIAgQBDQUIiA4DCQjJIw2FTQEBAQEBAQEBAQEBAQEBAQEBAQEBAReLK4JIggMxBwaDEYEWAQSRA4g/j3yGNiKDb2+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,556,1422921600"; d="scan'208";a="139980954"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP; 10 Apr 2015 12:27:35 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t3ACRZkj006893 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 10 Apr 2015 12:27:35 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.233]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0195.001; Fri, 10 Apr 2015 07:27:35 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQaKj8INk+f2Ge0U+xrfWR5Xce+p0w77kAgATBEYCAABEcgIABNV6AgABWGYCAAF6yAIAAF7yAgABqQYCAACnwgIAACJMAgAAfjoCAAShRAIAABR8AgAAft4CAACwwAIAAXHqAgABH0ICACLwQgIAAC+KAgAAfNgCAAARRgIAAFzkAgAAK5gCAAPAGgIAAG++AgAAVOYCAABPkAIAAEUQAgAAB24CAAANeAIAACHMAgAAuHYCAAArmgIABGDWAgAADiACAABWrgIAACCUAgAADbgCAABjbAIAABjCA//+sshA=
Date: Fri, 10 Apr 2015 12:27:35 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B891683CEBA@xmb-rcd-x06.cisco.com>
References: <55278783.2070104@gmail.com> <CAKD1Yr0WkNxoTDfudyYDNAnD7SxmsHXpLZq9PHtJrO5p_SgqTw@mail.gmail.com> <55279CA7.3010400@gmail.com> <20150410.121836.74655364.sthaug@nethelp.no> <5527A65C.3020008@gmail.com> <0FD16EA9-BBDF-48FE-97F5-82BA07527806@nominum.com> <5527C067.60900@gmail.com>
In-Reply-To: <5527C067.60900@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.126]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/5WJqEsdUo3PXVvA6gC9KrKiNAG8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "rdroms.ietf@gmail.com" <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 12:27:54 -0000

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Alexandru Petrescu
Sent: Friday, April 10, 2015 8:22 AM
To: Ted Lemon
Cc: dhcwg@ietf.org; rdroms.ietf@gmail.com
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length


> I meant to say that cases where RA does to offer what the Host expects.

Sorry, I haven't been reading all emails on this thread.   However, for the=
 question above, if the RA includes no PIO, then the router is signally eac=
h destination is off-link - send traffic to the default router.

Hemant


From nobody Fri Apr 10 05:29:51 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA031B307A for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 8tBTwVtf-mkx for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:29:47 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BD161B3039 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 05:29:47 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 5B1D7880F3; Fri, 10 Apr 2015 05:29:47 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id E92BD71B0001; Fri, 10 Apr 2015 05:29:46 -0700 (PDT)
Message-ID: <5527C232.2030304@innovationslab.net>
Date: Fri, 10 Apr 2015 08:29:38 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Qi Sun <sunqi.csnet.thu@gmail.com>
References: <5526BC55.8020006@innovationslab.net> <A81DBA34-FEB2-4568-BAED-59EFC8BE1CDA@gmail.com> <47A5238E-0081-4E78-881F-14722FEE801A@gmail.com>
In-Reply-To: <47A5238E-0081-4E78-881F-14722FEE801A@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7qq6olxNb7Uvm0PdW9fu4fUXlu125S4tb"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/zdiJm8iyDnNe_pStaTOQlOf8Lo8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Question on draft-ietf-dhc-dynamic-shared-v4allocation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 12:29:49 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7qq6olxNb7Uvm0PdW9fu4fUXlu125S4tb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Qi,

On 4/10/15 5:29 AM, Qi Sun wrote:
> Dear Brian,
>=20
> After a second thought, the comment seems valid. The intention of
> that text was that the meaning of those fields is the same, not the
> exact format. However, the wording there is a little confusing.
>=20
> So how about the following change:
>=20
> OLD: The DHCPv4 Port Parameters Option uses the same fields as the
> S46 Port Parameters Option described in Section 4.5 of=20
> [I-D.ietf-softwire-map-dhcp], implemented as a DHCPv4 option.  This=20
> is to maintain compatibility with existing port set implementations.
>=20
> NEW: The meaning of 'offset', 'PSID-len', and 'PSID' fields of the
> DHCPv4 Port Parameters Option is identical to that of 'offset',
> 'PSID-len', and 'PSID' fields of the S46 Port Parameters Option
> (Section 4.5 of [I-D.ietf-softwire-map-dhcp]). The use of the same
> encoding in both options is meant to ensure compatibility with
> existing port set implementations.
>=20
> Would that be clearer?

Yes, that would be clearer and explains why I was shaking my head.

Let me finish my review and then you can submit a document with any
other changes needed.

Regards,
Brian

>=20
> Thanks, Qi
>=20
> Sent from my iPhone
>=20
> =E5=9C=A8 2015-4-10=EF=BC=8C14:18=EF=BC=8CQi Sun <sunqi.csnet.thu@gmail=
=2Ecom> =E5=86=99=E9=81=93=EF=BC=9A
>=20
>> Dear Brian,
>>=20
>> Thanks a lot for the evaluation!
>>=20
>> If I understand you correctly, the incompatibility is caused
>> because this draft is defining a DHCPv4 option while
>> draft-ietf-softwire-map-dhcp defines a DHCPv6 option. But the
>> meanings of the fields should be the same, which "is to maintain
>> compatibility with existing port set implementations". Considering
>> the readability, we drew the Figure like this.
>>=20
>> Do we need to reword the sentence to this: "The DHCPv4 Port
>> Parameters Option uses the similar fields ..."
>>=20
>> ?
>>=20
>> Thank you very much, Qi
>>=20
>> Sent from my iPhone
>>=20
>> =E5=9C=A8 2015-4-10=EF=BC=8C1:52=EF=BC=8CBrian Haberman <brian@innovat=
ionslab.net> =E5=86=99=E9=81=93=EF=BC=9A
>>=20
>>> All, I have begun my AD evaluation of=20
>>> draft-ietf-dhc-dynamic-shared-v4allocation and have a need for
>>> some clarification.  Section 8 of the draft says:
>>>=20
>>> The DHCPv4 Port Parameters Option uses the same fields as the
>>> S46 Port Parameters Option described in Section 4.5 of=20
>>> [I-D.ietf-softwire-map-dhcp], implemented as a DHCPv4 option.
>>> This is to maintain compatibility with existing port set
>>> implementations.
>>>=20
>>> The format of OPTION_V4_PORTPARAMS is shown in Figure 1.
>>>=20
>>> 0                             1 0  1  2  3  4  5  6  7  8  9  0
>>> 1  2  3  4  5 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ |
>>> option-code      |     option-len        |=20
>>> +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ |
>>> offset        |       PSID-len        |=20
>>> +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ |
>>> PSID                      |=20
>>> +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
>>>=20
>>> Figure 1: DHCPv4 Port Parameters Option
>>>=20
>>>=20
>>> However, when I go and review the option defined in section 4.5
>>> of draft-ietf-softwire-map-dhcp, I see an incompatible option
>>> format:
>>>=20
>>> 0                   1                   2                   3 0 1
>>> 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1=20
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>>=20
|     OPTION_S46_PORTPARAMS     |         option-length         |
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>>=20
|   offset      |    PSID-len   |              PSID             |
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>>
>>>=20
Figure 6: S46 Port Parameters Option
>>>=20
>>> Which is correct?
>>>=20
>>> Regards, Brian
>>>=20
>>> _______________________________________________ dhcwg mailing
>>> list dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg


--7qq6olxNb7Uvm0PdW9fu4fUXlu125S4tb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVJ8I3AAoJEBOZRqCi7goqK50H/1gV2/KFs84sLmS2HMTwATwj
vJMjDVwxcMqQ3EFSrsUOfF7BDD4bLEd4x2Jq9srxsbP2iIvK7vS+Ioa60xSWMMQI
cprgn8Uy9XQC1Oh+YRmH5jUI4EWCgb2nNVs3W7yVWYPSdGjBzYKsVqrs4E1kY2/+
LgNbIPbewIHkksjYS8+2LIr9ifaL8ofevnoPwBRMjCCdii7ttUBL70B9wpo0Bdb2
kHgzxyNE7Eck/d2OvCBshZAj3RPQeP5HyV5TjyM+mic1oOc7cHSr5+N6UTzLkOLi
43aYoYZXYK5ALNg5iIXYGMmN+trlA4zxTzaCtjJhyto2NW2LTKzr2Sq70FWlmMk=
=6Tta
-----END PGP SIGNATURE-----

--7qq6olxNb7Uvm0PdW9fu4fUXlu125S4tb--


From nobody Fri Apr 10 05:42:22 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC0E1B3198 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 FTedEMK9f08k for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 05:42:18 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 53F4E1A03E1 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 05:42:18 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id C0AB11BC3E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 12:42:13 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5527B080.6010201@gmail.com>
Date: Fri, 10 Apr 2015 13:42:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/YaCcoeY1YrgKaECeGzt1rid3ijY>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 12:42:21 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> There are two RAs on this link, coming from two different routers.
>=20
> The first RA is sent only once, when the interface comes up.  It does
> not contain plen.  Never again later.
>=20
> The second RA is sent unicast whenever solicited, but contains no =
prefix.
>=20
> There are reasons to be so.  One that I can imagine is that it takes
> less bandwidth (the RA containing a prefix is two times larger than =
w/o
> a prefix).  There are other reasons there, but that's the way it is.

Actually, I see nothing wrong with that.

>> Why can't the implementation work without it ?
>=20
> The current implementation uses dhclient to acquire an address.
> DHCPv6 does not provide a plen.

Correct, that is by design.

> That dhclient thus uses a plen to be 64.  That
> 64 breaks RFC5942 section 4 bullet 1.  The plen is a must when adding =
an
> address on an interface.

Please try in your mind to separate the two things.
A prefix length is **NOT** in any way required in order to have an IPv6 =
address.
The **CLIENT UI IMPLEMENTATION** requires that one be specified.

That a client uses a /64 is **WRONG**. The client is broken and you =
should be targeting your efforts at the vendor to get that fixed. If the =
client implementation either used /128 (a hack), or better still did not =
try to associate prefixes with addresses (significant code redesign), =
then it would most likey "just work" out of the box.

> Other implementations prefer plen 128 instead of 64.  That 128 breaks =
a
> neighboring relationship: the host does find a neighbor in its rt =
table
> while the neighbor routers are there.

Actually, /128 is correct.
The device will communicate with the default gateway it's learned from =
the RA, and **IFF** the network supports it and the router is correctly =
configured, it will learn of directly reachable neighbours via ICMP =
redirects from the router. If it cannot directly communicate with other =
devices (which is quite possible on such a radio system) then it is =
correct that no on-link prefixes are specified in the RAs.


> The problem is that the RA does not contain a prefix, and the address =
is given by DHCP w/o a plen.

But there is no problem there, the problem is in your mind.

>> It looks like you still have not grasped the fundamental difference
>> that in the IPv6 world "address + prefix length does not equal
>> reachability information" and "in same prefix" is absolutely not
>> required for two devices to directly communicate.
>=20
> YEs, and I refuse maybe to grasp it.
>=20
> The reason is that IPv6 must work as IPv4 as much as possible.

I can see your point, but IPv6 is **NOT** "IPV4 with extra address =
bits".
There were lots of things wrong, or at least suboptimal, in IPv4 - IPv6 =
is an opportunity to start afresh and fix some of those. We may not like =
some of the changes (I'm not a fan of some), but they are changed and =
that's that.

So far, your argument is boiling down to "I don't like change" - with a =
pinch of "our system doesn't work because the standard don't match our =
incorrect setup". (where "incorrect setup" includes the client that =
applies a prefix length that it should not be doing).





Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> That's an easy fix for the DHCP client - just add a /128 prefix
>> length to keep the tools happy.
>=20
> I would not agree with that either.
>=20
> /128 plen on an address makes no sense.  There are neighbors to that =
address on that interface; their common prefix should be used instead of =
/128.

But it makes perfect sense if you understand that devices do not have to =
be in the same prefix to communicate with each other, AND that addresses =
are separate from the routing table. As explained before, the "is =
address in a prefix" decision needs only the **destination** address and =
the **on-link** prefix list - it needs no information about what =
prefix(es) our own address(es) are or are not members of.

> /128 is a hack which works in some cases.

Yes it is. It's a hack that works around incorrect implementations.




Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> An /128 entry in a routing table for an address assigned by DHCP makes
> no sense.  A rt entry is made to be compared with a dst address, not
> with a src address.

Correct, but this is an artefact of having to use a /128 prefix length =
in order to work around the incorrect implementation. The /128 route to =
our own address is, as you say, completely superfluous - but it doesn't =
actually break anything. It is not required by the specs.

The destination routes *should* be populated according to RAs received. =
If there are no on-link prefixes supplied by RA, then there should be no =
prefix table entries implying direct reachability of neighbours. There =
may well be neighbour routes as a result of ICMP redirects from a router =
- if the network supports that and the router is configured for it.


From nobody Fri Apr 10 06:13:53 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57C771B3511 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 o15G2gBHaE4g for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:13:49 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 638801B350E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:13:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3ADDleB022092 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 15:13:47 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3067320A510 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 15:14:54 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 280DA204E50 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 15:14:54 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3ADDDO4010933 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 15:13:46 +0200
Message-ID: <5527CC69.40204@gmail.com>
Date: Fri, 10 Apr 2015 15:13:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk>
In-Reply-To: <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Lu40aiderqKvkDCbNyq5CuWCQF0>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 13:13:52 -0000

Le 10/04/2015 14:42, Simon Hobson a écrit :
[...]

>> That dhclient thus uses a plen to be 64.  That 64 breaks RFC5942
>> section 4 bullet 1.  The plen is a must when adding an address on
>> an interface.
>
> Please try in your mind to separate the two things. A prefix length
> is **NOT** in any way required in order to have an IPv6 address. The
> **CLIENT UI IMPLEMENTATION** requires that one be specified.
>
> That a client uses a /64 is **WRONG**. The client is broken and you
> should be targeting your efforts at the vendor to get that fixed.

The software writer asks this "if not 64 then what else"?

>> Other implementations prefer plen 128 instead of 64.  That 128
>> breaks a neighboring relationship: the host does find a neighbor
>> in its rt table while the neighbor routers are there.
>
> Actually, /128 is correct.

But it is less correct to set an entry in the rt table for an address
allocated for self.  The rt table is for destination not for sources.

> The device will communicate with the default gateway it's learned
> from the RA, and **IFF** the network supports it and the router is
> correctly configured, it will learn of directly reachable neighbours
> via ICMP redirects from the router.

ICMP redirects from the router are ok, but some times routers dont issue
ICMP redirects (it's the case here).

> If it cannot directly communicate with other devices (which is quite
>  possible on such a radio system) then it is correct that no on-link
>  prefixes are specified in the RAs.

Maybe yes.

But it's hard to demand implementation of ICMP redirect.  Maybe that
stack does not implement it, maybe it's filtered out for firewalling.
With firewalling, it's illogic to forbid IPv4 ICMP Redirects, but allow
IPv6 ICMP Redirects.

It's simpler to have it in dhcp.

>> The problem is that the RA does not contain a prefix, and the
>> address is given by DHCP w/o a plen.
>
> But there is no problem there, the problem is in your mind.

No no, I have a deployment problem.  I hack around with 64 and 128 on
interfaces to just make it work for IPv6, whereas all works fine with IPv4.

>>> It looks like you still have not grasped the fundamental
>>> difference that in the IPv6 world "address + prefix length does
>>> not equal reachability information" and "in same prefix" is
>>> absolutely not required for two devices to directly communicate.
>>
>> YEs, and I refuse maybe to grasp it.
>>
>> The reason is that IPv6 must work as IPv4 as much as possible.
>
> I can see your point, but IPv6 is **NOT** "IPV4 with extra address
> bits".

Well it should.  And DHCPv6 plen is only part of the differences.  All
these translate in heavy workload in making IPv6 work.  Or maybe people
like that workload?

> There were lots of things wrong, or at least suboptimal, in IPv4

I beg to disagree.  IPv4 works out of the box everywhere and that is the
first requirement.  IPv6 is an add-on that pretends to be different and
hence harder to deploy.

> IPv6 is an opportunity to start afresh and fix some of those.

Maybe it was so in the past.  IPv4 also evolved a lot and many things
work better now than 20 years ago.

> We may not like some of the changes (I'm not a fan of some), but
> they are changed and that's that.
>
> So far, your argument is boiling down to "I don't like change" -
> with

I am not in a situation to not liking change.  I do propose IPv6 to
everyone.

The situation I am in is that many customers ask IPv4 and I suggest them
IPv6 together with it.

But, to get through, firewalling is the first thing that must be
precisely the same in IPv6 as in IPv4.  Because IPv4 firewalling is
tried and true and works and we dont want new IPv6 attacks for the sake
of migrating to IPv6.

Or, firewalling is the same in IPv6 as in IPv4 only when the protocols
are the same.

Alex

>
>
>
>
>
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>> That's an easy fix for the DHCP client - just add a /128 prefix
>>> length to keep the tools happy.
>>
>> I would not agree with that either.
>>
>> /128 plen on an address makes no sense.  There are neighbors to
>> that address on that interface; their common prefix should be used
>> instead of /128.
>
> But it makes perfect sense if you understand that devices do not
> have to be in the same prefix to communicate with each other, AND
> that addresses are separate from the routing table. As explained
> before, the "is address in a prefix" decision needs only the
> **destination** address and the **on-link** prefix list - it needs no
> information about what prefix(es) our own address(es) are or are not
> members of.
>
>> /128 is a hack which works in some cases.
>
> Yes it is. It's a hack that works around incorrect implementations.
>
>
>
>
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>> An /128 entry in a routing table for an address assigned by DHCP
>> makes no sense.  A rt entry is made to be compared with a dst
>> address, not with a src address.
>
> Correct, but this is an artefact of having to use a /128 prefix
> length in order to work around the incorrect implementation. The
> /128 route to our own address is, as you say, completely superfluous
> - but it doesn't actually break anything. It is not required by the
> specs.
>
> The destination routes *should* be populated according to RAs
> received. If there are no on-link prefixes supplied by RA, then
> there should be no prefix table entries implying direct reachability
> of neighbours. There may well be neighbour routes as a result of
> ICMP redirects from a router - if the network supports that and the
> router is configured for it.
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Fri Apr 10 06:23:38 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0B951B3559 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level: 
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 UGBXe7QoyUIi for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:23:27 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3E771B32BB for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:23:26 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C0224A2; Fri, 10 Apr 2015 15:23:24 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1428672204; bh=IsHE2M7H9E45nKGqT8Kd69O41Y3J90X6AVnQNAV/7es=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=e+IrENHviRcsiU7djOVDfp/2XJxExeUi7oM8jRwOMu4dNOcAPzWKeGEW+Bw8Lu60l g+xSvhtXpHfUXbx4PtJ+rJ0bE1BdRLbYB5AApcKrzKP6ge7uzrstnIi5B2/9OoVgEY bz/yPwU9rrXcvVjxwx5n+I0Rv1O8SvDCpiEPxjZo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id BBC789F; Fri, 10 Apr 2015 15:23:24 +0200 (CEST)
Date: Fri, 10 Apr 2015 15:23:24 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
In-Reply-To: <5527CC69.40204@gmail.com>
Message-ID: <alpine.DEB.2.02.1504101519020.9531@uplift.swm.pp.se>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/BFOMEV5WMSSUNDiRwavhaLUeZk4>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 13:23:35 -0000

On Fri, 10 Apr 2015, Alexandru Petrescu wrote:

> No no, I have a deployment problem.  I hack around with 64 and 128 on
> interfaces to just make it work for IPv6, whereas all works fine with IPv4.

Your problem is that you're trying to do something that violates the IPv6 
fundamental design, and your solution to this is to say that DHCPv6 should 
be changed.

You're asking for a fundamental change in the way IPv6 was designed, and 
you haven't given a good reason for this, other than to wave hands and say 
you need it to be this way.

If you want IPv6 to work as you expect in IPv4, you need to send RAs with 
prefix and default gateway. DHCPv6 IA_NA was never intended to work on its 
own. If you want to hack around, I encourage you to implement proprietary 
options in DHCPv6 to signal to your special client what it needs to do for 
your special use-case, and then you implement enough support for this in 
your client.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Apr 10 06:24:07 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 273061B3551 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 PdVgXOfuGDqe for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:24:04 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AC1C1B354E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:24:04 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 318AE880CE for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:24:04 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id F37DE71B0001 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:24:03 -0700 (PDT)
Message-ID: <5527CEEB.1070201@innovationslab.net>
Date: Fri, 10 Apr 2015 09:23:55 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com> <5527C1B9.4010304@gmail.com>
In-Reply-To: <5527C1B9.4010304@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KmexmrI40beeQ7M0t7VJUCQGvpa69rtHe"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ZqtnQp0OXu__R6AOGo5t4zNv2PA>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 13:24:06 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--KmexmrI40beeQ7M0t7VJUCQGvpa69rtHe
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable



On 4/10/15 8:27 AM, Alexandru Petrescu wrote:
> Le 10/04/2015 13:55, Ted Lemon a =E9crit :
>> On Apr 10, 2015, at 4:19 AM, Alexandru Petrescu
>> <alexandru.petrescu@gmail.com> wrote:
>>>> As Ted keeps saying, what's important is not how you configure
>>>> the implementation, but how it behaves.
>>>
>>> I disagree: RFCs should specify behaviour. Programmer should use
>>> it as a precise first-hand guide on how to implement. Some place
>>> for imagination of the programmer should be left of course, and
>>> the spec language should be independent of the programming
>>> language also.
>>
>> The RFCs specify the behavior of the host on the network, not the
>> user interface of the host.   You are trying to argue about a user
>> interface issue here.
>=20
> This is not just UI here.
>=20
> An /128 entry in a routing table for an address assigned by DHCP makes
> no sense.  A rt entry is made to be compared with a dst address, not
> with a src address.

Hmm... I have an application running on my machine that communicates
with another application on my machine.  I can't use the DHCPv6-assigned
address as a destination address for communication between these
applications???


--KmexmrI40beeQ7M0t7VJUCQGvpa69rtHe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVJ87rAAoJEBOZRqCi7goqjcAIALPUtACSWrpsGcIZ71UwCuYg
V5ve4anLL5zku7hLSDl7Dt13ZoBnyAWPuvI7GhTDa/TdmzII8xvQFlwx7ASfKCvw
hAhmu6SnRTpmcyZ5cfncUNmXYLrncTGJrjCX7coj3GFyBIRbEUap7ASg7+GllxPg
ymwIp+kNi3d5og+PIO8daWxeiAGkft9c4Y3hk01c74WE7GlIO9fwGcpkS6D1scnw
yWMqnLgXLqWxYC+tVdC2CMqqF9CMZ5rVSVB0ARel857WGWXJJGLm8YDFHCFUSMvq
enFkZnH1bZ0pKrsxsfhxLCICRUHDYjzj+6Fg+9U0c4R2S5G+IDifbhNjCv2pHBQ=
=6xdP
-----END PGP SIGNATURE-----

--KmexmrI40beeQ7M0t7VJUCQGvpa69rtHe--


From nobody Fri Apr 10 06:55:15 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2E741B361B for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 F78rgjPtWZL1 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:55:12 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C60E31B3615 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:55:12 -0700 (PDT)
Received: by iejt8 with SMTP id t8so17729552iej.2 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:55:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5xA4hyan81w3PZulCuTeDjg6GDp11e9jjoGN4TkhRgo=; b=FGi2Wgq+uPbRbR7X4w9Jb5/ki5b2bNnkp/BX6x5KZTrm/hG0moJlNfNLYCJwk661w/ Pz9efqqC+pZZlu1G5BkZoSFPd6OcPxV0PQWNOWAXYOeJyknWvQVoAh2e5LbUVypalo9U q3x4+AHqLEIcJB7qmpKfhUKF432Oqf4Pu57lr42/U7YOj544DE3p8wm4xClw3CmdS7ca 0CPwhJQjmm2WHJ4HfreXVdSAbegyF7bS+XQTGbCJ5nGj1WwtgNx3ceC/NMXtOpjb04H/ 10Jy8pjWQCosXI1nCnE8HLVnkdh3p5+jngwBaUmAN/uKLMnFFE/f3soJuKY/dx8IGMJ7 B6/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=5xA4hyan81w3PZulCuTeDjg6GDp11e9jjoGN4TkhRgo=; b=W+5AgWppu+2+7DOmcsv/3mC2S6WngiLjBinWP1UATqj7+Ds8nWD/7YRCNoij5vhGZX lCJfM5a6as9FVr+D+w8zZc+HjMWCsrZOu18AAIYTOfbvqOL2KOTv5dMYrax+boEn+074 4K1LC0tGCwG1Bkg/bdcITp324csim+fP+bGNwa75c9wF9Hath6kEDj4yrYUJ7KdpE6e9 EJSrYGX0LtP1d3BUbIUB2bFXzlN0hsC9/1DjmgfknER214hUGjewwZGHZO0Qgfz6qWeI HrZdVqvo/uiqZhmWWMHqzT0QPrbEWY+YAJxRLN2RfI9KsSxnkIGN2fX1CTYazTyY0LKu UozA==
X-Gm-Message-State: ALoCoQmqt81PubEToGCvPGHVYcdFG4J+/dGfbNTZho9PVOqZ0LEvVJrHVqhx1SQKLDP+P/lC9dAw
X-Received: by 10.50.77.13 with SMTP id o13mr17748036igw.39.1428674112027; Fri, 10 Apr 2015 06:55:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Fri, 10 Apr 2015 06:54:51 -0700 (PDT)
In-Reply-To: <5527CEEB.1070201@innovationslab.net>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com> <5527C1B9.4010304@gmail.com> <5527CEEB.1070201@innovationslab.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 10 Apr 2015 22:54:51 +0900
Message-ID: <CAKD1Yr2BMHHwvey-LG2L+zZf8EtbMPyGvvwmiwKEhp5Js3SdvQ@mail.gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/alternative; boundary=047d7bdc110af2d2ef05135f1c1c
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/tPpgRfNqRwV5GDIgjjSV-tbscgg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 13:55:14 -0000

--047d7bdc110af2d2ef05135f1c1c
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 10, 2015 at 10:23 PM, Brian Haberman <brian@innovationslab.net>
wrote:

> Hmm... I have an application running on my machine that communicates
> with another application on my machine.  I can't use the DHCPv6-assigned
> address as a destination address for communication between these
> applications???
>

You can. Every implementation I've seen will configure things so that if
you assign an IP address to an interface, packets sent to that IP address
are looped back to the IP stack instead of sent on that interface.

RFC 6724 Rule 1, if you are trying to talk to an address that is assigned
to your host, you will always use that address.

So yes, if all you have is a DHCPv6 address, you can use that to talk
between applications on the same machine. That's not very useful though -
you can use ::1 for that too. You can also talk to link-local addresses,
which is only marginally more useful.

--047d7bdc110af2d2ef05135f1c1c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Apr 10, 2015 at 10:23 PM, Brian Haberman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:brian@innovationslab.net" target=3D"_blank">brian@innovationslab=
.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,=
204);border-left-style:solid;padding-left:1ex"><div><div><span style=3D"col=
or:rgb(34,34,34)">Hmm... I have an application running on my machine that c=
ommunicates</span><br></div></div>
with another application on my machine.=C2=A0 I can&#39;t use the DHCPv6-as=
signed<br>
address as a destination address for communication between these<br>
applications???<br></blockquote><div><br></div><div>You can. <span style=3D=
"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-styl=
e:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-=
height:normal;text-align:start;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;float:none;display:inline!important;background-=
color:rgb(255,255,255)">Every implementation I&#39;ve seen will configure t=
hings so that if you assign an IP address to an interface, packets sent to =
that IP address are looped back to the IP stack instead of sent on that int=
erface.</span></div><div><br></div><div>RFC 6724 Rule 1, if you are trying =
to talk to an address that is assigned to your host, you will always use th=
at address.</div><div><br></div><div>So yes, if all you have is a DHCPv6 ad=
dress, you can use that to talk between applications on the same machine. T=
hat&#39;s not very useful though - you can use ::1 for that too. You can al=
so talk to link-local addresses, which is only marginally more useful.</div=
></div></div></div>

--047d7bdc110af2d2ef05135f1c1c--


From nobody Fri Apr 10 06:58:25 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D51B1B362F for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:58:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 NKd9XNdstk-R for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 06:58:22 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F76C1B3539 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:58:22 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 1595488132 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:58:22 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id D2C9371B0001 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 06:58:21 -0700 (PDT)
Message-ID: <5527D6F5.3040600@innovationslab.net>
Date: Fri, 10 Apr 2015 09:58:13 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com> <5527C1B9.4010304@gmail.com> <5527CEEB.1070201@innovationslab.net> <CAKD1Yr2BMHHwvey-LG2L+zZf8EtbMPyGvvwmiwKEhp5Js3SdvQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr2BMHHwvey-LG2L+zZf8EtbMPyGvvwmiwKEhp5Js3SdvQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0AmeWO3UhUv9QpcoRtr7aIkKdp9rEkB6p"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/JzP1AOztrsrjgA6E19KDc1aMfiw>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 13:58:23 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--0AmeWO3UhUv9QpcoRtr7aIkKdp9rEkB6p
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Lorenzo,

On 4/10/15 9:54 AM, Lorenzo Colitti wrote:
> On Fri, Apr 10, 2015 at 10:23 PM, Brian Haberman <brian@innovationslab.=
net>
> wrote:
>=20
>> Hmm... I have an application running on my machine that communicates
>> with another application on my machine.  I can't use the DHCPv6-assign=
ed
>> address as a destination address for communication between these
>> applications???
>>
>=20
> You can. Every implementation I've seen will configure things so that i=
f
> you assign an IP address to an interface, packets sent to that IP addre=
ss
> are looped back to the IP stack instead of sent on that interface.
>=20
> RFC 6724 Rule 1, if you are trying to talk to an address that is assign=
ed
> to your host, you will always use that address.
>=20
> So yes, if all you have is a DHCPv6 address, you can use that to talk
> between applications on the same machine. That's not very useful though=
 -
> you can use ::1 for that too. You can also talk to link-local addresses=
,
> which is only marginally more useful.
>=20

I pretty much agree with everything you wrote.  I was just trying to
point out a valid reason to Alex why a device should add a route table
entry for a DHCPv6-assigned address with a prefix length of 128.

Regards,
Brian


--0AmeWO3UhUv9QpcoRtr7aIkKdp9rEkB6p
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVJ9b1AAoJEBOZRqCi7goqBh0H+wcvaSmophmqTrXYbqyPwPUP
QEAw+YykhOp2DvviLlEbDQpz7oz0O+s4mK/fq/yRwHGYRdSpjyWx8N0vYSLBJsmQ
XOdcF8RYth/iVtvkGz+xwm4PpmFwCnxgM9aJ7qVI/x7JAzYZgbzbK26dQKhwRFPM
78qF/MANq3fumkxp3zCrXqCsMxRvZTf8vnoEITiJXDNqPhF0/U7uK/cXleBJJ54k
LjPE2VqSp6XTKWLuLdCFskLN/Dc1XDXIycHuw33r7c6vrkaB7op6sA5cwasoydWt
qoeGVtlv+AoLAQ1FE7JkaK4wmZdRAG2dwjSuFEmlh+AZwbp/UC4G2ZnmYhB//ag=
=Lw4Q
-----END PGP SIGNATURE-----

--0AmeWO3UhUv9QpcoRtr7aIkKdp9rEkB6p--


From nobody Fri Apr 10 07:34:52 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E7E1A0204 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 07:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 f8af5p8v7NgF for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 07:34:49 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5291A015F for <dhcwg@ietf.org>; Fri, 10 Apr 2015 07:34:49 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id C29121BC3E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 14:34:44 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5527CC69.40204@gmail.com>
Date: Fri, 10 Apr 2015 15:34:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/P7x3wKKfERZD604UfK4jBbx_BPA>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 14:34:51 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> That a client uses a /64 is **WRONG**. The client is broken and you
>> should be targeting your efforts at the vendor to get that fixed.
>=20
> The software writer asks this "if not 64 then what else"?

Which is fair enough.
The "correct" answer is that there is no prefix length<period>.
Given that the tools incorrectly require one, then the useful answer is =
"if the tools demand one, then use /128 which should fudge things enough =
to work correctly.

>>> Other implementations prefer plen 128 instead of 64.  That 128
>>> breaks a neighboring relationship: the host does find a neighbor
>>> in its rt table while the neighbor routers are there.
>>=20
>> Actually, /128 is correct.
>=20
> But it is less correct to set an entry in the rt table for an address
> allocated for self.  The rt table is for destination not for sources.

We're talking about how to "make things work properly in the face of =
incorrect implementations. You are right that adding a route to =
ourselves with a /128 prefix isn't correct - it's a side effect of =
having to provide a prefix length when one does not exist. However, =
having such a route doesn't actually break anything.

> ICMP redirects from the router are ok, but some times routers dont =
issue
> ICMP redirects (it's the case here).

Then the router must forward the packets. It **MUST** do one or the =
other, *OR* you must have a network that supports direct communication =
AND supply the right RAs.
This is sounding like "we set it up wrong but it's the standard's fault =
it doesn't work".

>> If it cannot directly communicate with other devices (which is quite
>> possible on such a radio system) then it is correct that no on-link
>> prefixes are specified in the RAs.
>=20
> Maybe yes.
>=20
> But it's hard to demand implementation of ICMP redirect.  Maybe that
> stack does not implement it, maybe it's filtered out for firewalling.
> With firewalling, it's illogic to forbid IPv4 ICMP Redirects, but =
allow
> IPv6 ICMP Redirects.

If a router is even half way to being a decent router then it'll handle =
redirects - as they do for IPv4. If it can't handle fundamental things, =
then it's not correct to call it a "router".
Again, this is an implementation vs standard issue - and it's not the =
standard that's the problem here. And yet again, if you configure it to =
not do something then that's your issue.

>> There were lots of things wrong, or at least suboptimal, in IPv4
>=20
> I beg to disagree.  IPv4 works out of the box everywhere and that is =
the
> first requirement.

Complete and utter bulls**t.
IPv4 certainly does not work properly out of the box everywhere. There =
are a **LOT** of hacks on various networks needed to make stuff work - =
it appears you have little experience outside of "broadcast capable, =
ethernet like" networks or you wouldn't make such a statement.



> IPv6 is an add-on that pretends to be different and hence harder to =
deploy.

It is a new protocol, it is not pretending to be different, it *IS* =
different.

>> IPv6 is an opportunity to start afresh and fix some of those.
>=20
> Maybe it was so in the past.  IPv4 also evolved a lot and many things
> work better now than 20 years ago.

But regardless of how some tweaks may be done, the fundamental design =
cannot be changed without breaking every existing implementation. This =
is a good argument for getting IPv6 right - before it gets to the "can't =
change anything without breaking the internet" stage (actually, I think =
we're more or less past that for the basics now).

> But, to get through, firewalling is the first thing that must be
> precisely the same in IPv6 as in IPv4.  Because IPv4 firewalling is
> tried and true and works and we dont want new IPv6 attacks for the =
sake
> of migrating to IPv6.
>=20
> Or, firewalling is the same in IPv6 as in IPv4 only when the protocols
> are the same.

There's no significant difference between firewalling IPv6 and IPv4. =
Some details yes, but fundamentally it's the same process.




Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> Your problem is that you're trying to do something that violates the =
IPv6 fundamental design, and your solution to this is to say that DHCPv6 =
should be changed.
>=20
> You're asking for a fundamental change in the way IPv6 was designed, =
and you haven't given a good reason for this, other than to wave hands =
and say you need it to be this way.
>=20
> If you want IPv6 to work as you expect in IPv4, you need to send RAs =
with prefix and default gateway. DHCPv6 IA_NA was never intended to work =
on its own. If you want to hack around, I encourage you to implement =
proprietary options in DHCPv6 to signal to your special client what it =
needs to do for your special use-case, and then you implement enough =
support for this in your client.

+1





From nobody Fri Apr 10 07:46:25 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E66271A038C for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 07:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 5qFWBLZuh4qQ for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 07:46:23 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 EA4701A037A for <dhcwg@ietf.org>; Fri, 10 Apr 2015 07:46:22 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id A0863DA00D5; Fri, 10 Apr 2015 14:46:22 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 10 Apr 2015 07:46:22 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <5527C1B9.4010304@gmail.com>
Date: Fri, 10 Apr 2015 10:46:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <8ED2E2CA-5755-4E5B-B779-319D41BF7897@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com> <5527C1B9.4010304@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Nv6awweXELmdnzluoiFRmNhxYZM>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 14:46:24 -0000

On Apr 10, 2015, at 8:27 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
> An /128 entry in a routing table for an address assigned by DHCP makes
> no sense.  A rt entry is made to be compared with a dst address, not
> with a src address.

We do not specify data structures on operating systems any more than we =
specify user interfaces.   Should we require the use of red/black trees =
for routing tables?   Binary trees?   Heap sort/binary search?

The answer is that we do not do things like that not only because it =
would be inappropriate, but because the debate about which algorithm to =
select would never end.   Just like this discussion.   Please stop.


From nobody Fri Apr 10 08:04:07 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 174F41A1A1C for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:04:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 Iqa8gcQ_pA_h for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:04:05 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35C941A1A17 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 08:04:05 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3AF42hN004036 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:04:02 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 1661120A76A for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:05:10 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0DAE6200B4D for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:05:10 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3AF3bff015499 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:04:02 +0200
Message-ID: <5527E648.3070900@gmail.com>
Date: Fri, 10 Apr 2015 17:03:36 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com> <5527C1B9.4010304@gmail.com> <5527CEEB.1070201@innovationslab.net>
In-Reply-To: <5527CEEB.1070201@innovationslab.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/8WJGCUhM3kSoiqEPrG0U3kx2JXw>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 15:04:07 -0000

Le 10/04/2015 15:23, Brian Haberman a écrit :
>
>
> On 4/10/15 8:27 AM, Alexandru Petrescu wrote:
>> Le 10/04/2015 13:55, Ted Lemon a écrit :
>>> On Apr 10, 2015, at 4:19 AM, Alexandru Petrescu
>>> <alexandru.petrescu@gmail.com> wrote:
>>>>> As Ted keeps saying, what's important is not how you configure
>>>>> the implementation, but how it behaves.
>>>>
>>>> I disagree: RFCs should specify behaviour. Programmer should use
>>>> it as a precise first-hand guide on how to implement. Some place
>>>> for imagination of the programmer should be left of course, and
>>>> the spec language should be independent of the programming
>>>> language also.
>>>
>>> The RFCs specify the behavior of the host on the network, not the
>>> user interface of the host.   You are trying to argue about a user
>>> interface issue here.
>>
>> This is not just UI here.
>>
>> An /128 entry in a routing table for an address assigned by DHCP makes
>> no sense.  A rt entry is made to be compared with a dst address, not
>> with a src address.
>
> Hmm... I have an application running on my machine that communicates
> with another application on my machine.  I can't use the DHCPv6-assigned
> address as a destination address for communication between these
> applications???

YEs you could, but wouldnt the ::1 be better for that app on that machine?

Alex

>
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>



From nobody Fri Apr 10 08:08:25 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 079551A19E9 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 OgjT4wl5qB3t for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:08:23 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id D43001A0AF8 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 08:08:22 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 7A2821BC3E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 15:08:19 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5527E648.3070900@gmail.com>
Date: Fri, 10 Apr 2015 16:08:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <909718CB-4812-4522-8D89-E6E2D7BD80C8@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <961904C4-3D80-4697-9E7A-B0E8BD9A3CE1@nominum.com> <5527C1B9.4010304@gmail.com> <5527CEEB.1070201@innovationslab.net> <5527E648.3070900@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/6MF0J2o3bqyS76CN-ewGYHr-xek>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 15:08:24 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> Hmm... I have an application running on my machine that communicates
>> with another application on my machine.  I can't use the =
DHCPv6-assigned
>> address as a destination address for communication between these
>> applications???
>=20
> YEs you could, but wouldnt the ::1 be better for that app on that =
machine?

Not always.
There are many reasons why connecting to a non-loopback address makes =
sense. Not least is where you've configured certain services to only =
listen on certain addresses.
But his question wasn't one needing an answer - it was pointing out the =
error in your logic.


From nobody Fri Apr 10 08:15:17 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E028F1A1A97 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 TQRGzK_epnPs for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:15:13 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F28551A1A8B for <dhcwg@ietf.org>; Fri, 10 Apr 2015 08:15:12 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3AFFB82008306 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:15:11 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6068420A795 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:16:18 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 586D020A780 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:16:18 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3AFEXfg027907 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:15:11 +0200
Message-ID: <5527E8D9.9040509@gmail.com>
Date: Fri, 10 Apr 2015 17:14:33 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk>
In-Reply-To: <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/HIXK-Suk32yHjndOHHPEjdPJRq8>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 15:15:16 -0000

Le 10/04/2015 16:34, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>> That a client uses a /64 is **WRONG**. The client is broken and
>>> you should be targeting your efforts at the vendor to get that
>>> fixed.
>>
>> The software writer asks this "if not 64 then what else"?
>
> Which is fair enough. The "correct" answer is that there is no prefix
> length<period>. Given that the tools incorrectly require one, then
> the useful answer is "if the tools demand one, then use /128 which
> should fudge things enough to work correctly.

Again - if you put there 128 you loose all your neighbors.

Alex

>
>>>> Other implementations prefer plen 128 instead of 64.  That 128
>>>> breaks a neighboring relationship: the host does find a
>>>> neighbor in its rt table while the neighbor routers are there.
>>>
>>> Actually, /128 is correct.
>>
>> But it is less correct to set an entry in the rt table for an
>> address allocated for self.  The rt table is for destination not
>> for sources.
>
> We're talking about how to "make things work properly in the face of
> incorrect implementations. You are right that adding a route to
> ourselves with a /128 prefix isn't correct - it's a side effect of
> having to provide a prefix length when one does not exist. However,
> having such a route doesn't actually break anything.
>
>> ICMP redirects from the router are ok, but some times routers dont
>> issue ICMP redirects (it's the case here).
>
> Then the router must forward the packets. It **MUST** do one or the
> other, *OR* you must have a network that supports direct
> communication AND supply the right RAs. This is sounding like "we set
> it up wrong but it's the standard's fault it doesn't work".
>
>>> If it cannot directly communicate with other devices (which is
>>> quite possible on such a radio system) then it is correct that no
>>> on-link prefixes are specified in the RAs.
>>
>> Maybe yes.
>>
>> But it's hard to demand implementation of ICMP redirect.  Maybe
>> that stack does not implement it, maybe it's filtered out for
>> firewalling. With firewalling, it's illogic to forbid IPv4 ICMP
>> Redirects, but allow IPv6 ICMP Redirects.
>
> If a router is even half way to being a decent router then it'll
> handle redirects - as they do for IPv4. If it can't handle
> fundamental things, then it's not correct to call it a "router".
> Again, this is an implementation vs standard issue - and it's not the
> standard that's the problem here. And yet again, if you configure it
> to not do something then that's your issue.
>
>>> There were lots of things wrong, or at least suboptimal, in IPv4
>>
>> I beg to disagree.  IPv4 works out of the box everywhere and that
>> is the first requirement.
>
> Complete and utter bulls**t. IPv4 certainly does not work properly
> out of the box everywhere. There are a **LOT** of hacks on various
> networks needed to make stuff work - it appears you have little
> experience outside of "broadcast capable, ethernet like" networks or
> you wouldn't make such a statement.
>
>
>
>> IPv6 is an add-on that pretends to be different and hence harder to
>> deploy.
>
> It is a new protocol, it is not pretending to be different, it *IS*
> different.
>
>>> IPv6 is an opportunity to start afresh and fix some of those.
>>
>> Maybe it was so in the past.  IPv4 also evolved a lot and many
>> things work better now than 20 years ago.
>
> But regardless of how some tweaks may be done, the fundamental design
> cannot be changed without breaking every existing implementation.
> This is a good argument for getting IPv6 right - before it gets to
> the "can't change anything without breaking the internet" stage
> (actually, I think we're more or less past that for the basics now).
>
>> But, to get through, firewalling is the first thing that must be
>> precisely the same in IPv6 as in IPv4.  Because IPv4 firewalling
>> is tried and true and works and we dont want new IPv6 attacks for
>> the sake of migrating to IPv6.
>>
>> Or, firewalling is the same in IPv6 as in IPv4 only when the
>> protocols are the same.
>
> There's no significant difference between firewalling IPv6 and IPv4.
> Some details yes, but fundamentally it's the same process.
>
>
>
>
> Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
>> Your problem is that you're trying to do something that violates
>> the IPv6 fundamental design, and your solution to this is to say
>> that DHCPv6 should be changed.
>>
>> You're asking for a fundamental change in the way IPv6 was
>> designed, and you haven't given a good reason for this, other than
>> to wave hands and say you need it to be this way.
>>
>> If you want IPv6 to work as you expect in IPv4, you need to send
>> RAs with prefix and default gateway. DHCPv6 IA_NA was never
>> intended to work on its own. If you want to hack around, I
>> encourage you to implement proprietary options in DHCPv6 to signal
>> to your special client what it needs to do for your special
>> use-case, and then you implement enough support for this in your
>> client.
>
> +1
>
>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Fri Apr 10 08:16:20 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED5A41A1AA6; Fri, 10 Apr 2015 08:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 EkMw8NvDiGSD; Fri, 10 Apr 2015 08:16:14 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D750C1A1A9A; Fri, 10 Apr 2015 08:16:11 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id BA5A3880F3; Fri, 10 Apr 2015 08:16:11 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 37BBA71B0001; Fri, 10 Apr 2015 08:16:11 -0700 (PDT)
Message-ID: <5527E933.6070107@innovationslab.net>
Date: Fri, 10 Apr 2015 11:16:03 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org,  "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dsE9ciwhxLXtbTanKKxejdvi7LaHAW5oE"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/KwG8d3L4KnS4z-6XP37nOzCwdLg>
Subject: [dhcwg] AD Evaluation: draft-ietf-dhc-dynamic-shared-v4allocation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 15:16:19 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--dsE9ciwhxLXtbTanKKxejdvi7LaHAW5oE
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

All,
     I have completed my AD evaluation of this draft and only have a
handful of comments/questions.  Please let me know if you have any
questions/concerns with these.

* Introduction

The last paragraph briefly describes the limited deployments/topologies
where this solution can be used.  Section 9.1 goes into more detail that
I think is quite useful and should appear earlier.  I would suggest
inserting a Applicability Statement section after the Intro that
highlights where this solution can be used.  That will frame the later
discussions of the protocol details.

* Section 3

I would drop the "MUST" from the definition of Shared IPv4 address.

* Section 4

I don't see the need for using 2119 keywords here, so I would suggest
s/MAY allocate the same IPv4 address/can allocate the same IPv4 address/

* Section 6

s/allocated and IPv4/allocated an IPv4/

* Section 6.1

The following text is confusing:

"client MUST NOT configure the received restricted IPv4 address on-link"

Can you clean up that statement?

* Section 7

I don't think all the MUSTs are needed in the 2nd paragraph.  Much of it
is trying to dictate implementation details.  I would suggest rewording
it as requirements for expected behavior.

* Section 8

I believe we have agreement on the text changes to clarify the use of
this option.

* Meta question

In section 6, there is text that describes how a client handles the case
where it sent OPTION_V4_PORTPARAMS but receives an unshared address in
response.  The text in the section 7 doesn't discuss when/how a server
can omit that option when the client sent it.  Is there a need to cover
that situation in more detail for the server?

Regards,
Brian


--dsE9ciwhxLXtbTanKKxejdvi7LaHAW5oE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVJ+kzAAoJEBOZRqCi7goqDEEIALlVXCR8gEhOxDIjMULMm4Mm
vQ8CQjp6CLIP6hglxOr5R2vg3riXy0ByTy9pu+iaYrpvck1/p2tEYN/oor2ujAEL
BHTicP4heosnHRms9pnU9+rbLMyOooTP054He7JDYWbr17YbHLkmo72LzLvBIv/w
T9c9fCkgj0aYzrasFaD6WGSo+ZZ122qoH+KiD2okQgM/gQzAioWuiUju36vsijq5
hkmNP7RL9g7Rc16TTJFtfufP4IpSny1e5BxzwBVxec782HwQlJkAAjxs75y7wtSq
2kSEvidralwknCpxsugn++sq8xniFeOrQw4vtiWiUt1JVudOOHM9+QM3aOZtyKg=
=Rhnq
-----END PGP SIGNATURE-----

--dsE9ciwhxLXtbTanKKxejdvi7LaHAW5oE--


From nobody Fri Apr 10 08:17:16 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 657731A1AC9; Fri, 10 Apr 2015 08:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 RNC1OSkRmivK; Fri, 10 Apr 2015 08:17:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E82D91A1A58; Fri, 10 Apr 2015 08:17:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <draft-ietf-dhc-dynamic-shared-v4allocation.ad@ietf.org>, <volz@cisco.com>, <dhc-chairs@ietf.org>, <draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org>, <dhcwg@ietf.org>,  <draft-ietf-dhc-dynamic-shared-v4allocation.shepherd@ietf.org>, 
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150410151706.30042.27489.idtracker@ietfa.amsl.com>
Date: Fri, 10 Apr 2015 08:17:06 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/S8ndnHRkqF7TyeodscVcDLrkKRw>
Subject: [dhcwg] ID Tracker State Update Notice: <draft-ietf-dhc-dynamic-shared-v4allocation-05.txt>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 15:17:14 -0000

IESG state changed to AD Evaluation::Revised I-D Needed from AD Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/


From nobody Fri Apr 10 08:36:36 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0CE31A1F16 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Cm6C6c6evabv for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:36:22 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 666AC1A1F00 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 08:36:22 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 1AA8A1BC3E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 15:35:55 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5527E8D9.9040509@gmail.com>
Date: Fri, 10 Apr 2015 16:35:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/wr4sJXju3QNGMZKlp8sjR84k9XM>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 15:36:29 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> Which is fair enough. The "correct" answer is that there is no prefix
>> length<period>. Given that the tools incorrectly require one, then
>> the useful answer is "if the tools demand one, then use /128 which
>> should fudge things enough to work correctly.
>=20
> Again - if you put there 128 you loose all your neighbors.

Now listen carefully. NO YOU DO NOT<period>
If you use a /128, the system will **CORRECTLY** use the information it =
is given to determine which addresses are directly reachable neighbours. =
It really is as simple as that.
Your problem is that you have what sound like an improperly configured =
network and you won't accept that the answer is to properly configure it =
rather than "fix" the standards.

Sticking with your cellular network. When a node A is configured with an =
address, and node B is configured with an address, should nodes A and B =
be able to send packets directly to each other ? Ie, is it a broadcast =
network like ethernet, or is it a unicast network where each device can =
only talk to the base router ?




From nobody Fri Apr 10 08:41:47 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC93F1A6EE0 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 6iHxRVp5oAkA for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:41:36 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F0171A6F03 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 08:41:35 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3AFfYrB016255 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:41:34 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3BB8E20A734 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:42:41 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 33FC620267A for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:42:41 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3AFfXJk001258 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 17:41:33 +0200
Message-ID: <5527EF2D.1020506@gmail.com>
Date: Fri, 10 Apr 2015 17:41:33 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk>
In-Reply-To: <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/wxs7c76yojzc8a4TztObBgdKHmQ>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 15:41:40 -0000

Le 10/04/2015 17:35, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>> Which is fair enough. The "correct" answer is that there is no
>>> prefix length<period>. Given that the tools incorrectly require
>>> one, then the useful answer is "if the tools demand one, then use
>>> /128 which should fudge things enough to work correctly.
>>
>> Again - if you put there 128 you loose all your neighbors.
>
> Now listen carefully. NO YOU DO NOT<period> If you use a /128, the
> system will **CORRECTLY** use the information it is given to
> determine which addresses are directly reachable neighbours. It
> really is as simple as that. Your problem is that you have what sound
> like an improperly configured network and you won't accept that the
> answer is to properly configure it rather than "fix" the standards.
>
> Sticking with your cellular network. When a node A is configured with
> an address, and node B is configured with an address, should nodes A
> and B be able to send packets directly to each other ? Ie, is it a
> broadcast network like ethernet, or is it a unicast network where
> each device can only talk to the base router ?

It's a unicast that tends to become broadcast more and more (get rid of 
pppd).

A is the Client (smartphone), B and C are two routers on that link with 
two different ll addresses, in the infrastructure.

That would be a /126.

Alex

>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Fri Apr 10 08:48:15 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDB271A1AC9 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 6DuqXvvqI4lc for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 08:48:13 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 318791A6F28 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 08:48:10 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 74C701BC3E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 15:48:06 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5527EF2D.1020506@gmail.com>
Date: Fri, 10 Apr 2015 16:48:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk> <5527EF2D.1020506@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ZS1L4pWGldSZcqBCX_S4BdOWw3M>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 15:48:15 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> Sticking with your cellular network. When a node A is configured with
>> an address, and node B is configured with an address, should nodes A
>> and B be able to send packets directly to each other ? Ie, is it a
>> broadcast network like ethernet, or is it a unicast network where
>> each device can only talk to the base router ?
>=20
> It's a unicast that tends to become broadcast more and more (get rid =
of pppd).
>=20
> A is the Client (smartphone), B and C are two routers on that link =
with two different ll addresses, in the infrastructure.
>=20
> That would be a /126.

Not necessarily. They could all be /128, they could be in a /64, or they =
could be in a /56, or they could be in a /48, or ...

Now please answer the question I asked - and in case it wasn't clear =
enough I'll change it slightly.
If two end devices (say smartphone A and smartphone B) are connected to =
your network, does the network technology allow them to directly =
communicate (ie direct A-B) or does communication have to go via a =
router (ie A-R-B) ? Ignore addressing, whether it's IPv4 or IPv6, at the =
lowest network level - can they directly exchange packets ?

And if they can, are the restrictions (such as them having to be "signed =
in" with the same cell/controller) for it to work, or will it work =
regardless of the device location/the cell it's signed in with/ etc ?


From nobody Fri Apr 10 09:08:35 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 159271A6EE9 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 nSWEnx2v73pN for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:08:32 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33FAC1A6F1E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 09:08:31 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3AG8TuD029560 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 18:08:29 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7C49D20A81E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 18:09:36 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 74A9320A709 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 18:09:36 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3AG86Qv021657 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 18:08:29 +0200
Message-ID: <5527F566.6080402@gmail.com>
Date: Fri, 10 Apr 2015 18:08:06 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk> <5527EF2D.1020506@gmail.com> <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk>
In-Reply-To: <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ITL2_5YnsrexW44elcMGHmRDRPk>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 16:08:34 -0000

Le 10/04/2015 17:48, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>> Sticking with your cellular network. When a node A is configured
>>> with an address, and node B is configured with an address,
>>> should nodes A and B be able to send packets directly to each
>>> other ? Ie, is it a broadcast network like ethernet, or is it a
>>> unicast network where each device can only talk to the base
>>> router ?
>>
>> It's a unicast that tends to become broadcast more and more (get
>> rid of pppd).
>>
>> A is the Client (smartphone), B and C are two routers on that link
>> with two different ll addresses, in the infrastructure.
>>
>> That would be a /126.
>
> Not necessarily. They could all be /128, they could be in a /64, or
> they could be in a /56, or they could be in a /48, or ...

We know that only three IP addresses are there.  The longest prefix
stringing them would be a /126.  Other plens like /48 and /64 are also
possible but would represent an enormous address waste.  And yes,
everything could be /128 in this Internet.  But host-based routes have
inconvenients that I suppose well known.

(and yes I know consensus considers there are enough /64s out there)

> Now please answer the question I asked - and in case it wasn't clear
> enough I'll change it slightly. If two end devices (say smartphone A
> and smartphone B) are connected to your network, does the network
> technology allow them to directly communicate (ie direct A-B) or
> does communication have to go via a router (ie A-R-B) ? Ignore
> addressing, whether it's IPv4 or IPv6, at the lowest network level -
> can they directly exchange packets ?

I can answer you by digging something, but I dont know why you ask.

Intuitevely, that is where cellular systems go: A talk directly to B at
IP layer.  Link-layer packets may continue go to R for
some time and maybe (just maybe) one day they won't, although it is unsure.

> And if they can, are the restrictions (such as them having to be
> "signed in" with the same cell/controller) for it to work, or will
> it work regardless of the device location/the cell it's signed in
> with/ etc ?

That I couldnt know, because I would need a special traffic analyzer to
show these link-layer headers - I dont have that and I dont want to get one.

Why is this related to our discussion on prefix lengths?

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Fri Apr 10 09:08:55 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4986E1A6F33 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 6VNNSDnlxuHf for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:08:52 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 256361A700C for <dhcwg@ietf.org>; Fri, 10 Apr 2015 09:08:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 0394BDA0077; Fri, 10 Apr 2015 16:08:45 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 10 Apr 2015 09:08:44 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <5527E8D9.9040509@gmail.com>
Date: Fri, 10 Apr 2015 12:08:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <FDD4F61E-A047-47B8-B68A-C0F2C96D33CD@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/hKw8I_BDMc7iixYvpVvBvmIdbWc>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 16:08:53 -0000

On Apr 10, 2015, at 11:14 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
> Again - if you put there 128 you loose all your neighbors.

Okay, so if I understand you, what you are saying is that if you install =
a /128 route to the IA_NA address, then that will remove any route to =
that a narrower prefix containing that /128.   But that's not true.   =
The /128 route will only match the one IP address that it was added for; =
if there is already a route for the /64 that contains the /128, then =
installing the /128 will not prevent the /64 from working, and you will =
be able to communicate with your neighbors just fine.

However, if all you have is the IA_NA, then addresses that are in that =
/64 are not guaranteed to be on-link.


From nobody Fri Apr 10 09:18:44 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF6741A8A3D for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 og-1hv-uQO1P for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:18:39 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBBA51A8981 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 09:18:35 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3AGIYjc032271; Fri, 10 Apr 2015 18:18:34 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4D0CA20A70B; Fri, 10 Apr 2015 18:19:41 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 41D5B204E50; Fri, 10 Apr 2015 18:19:41 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3AGIAPk025750; Fri, 10 Apr 2015 18:18:33 +0200
Message-ID: <5527F7C2.2010409@gmail.com>
Date: Fri, 10 Apr 2015 18:18:10 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <FDD4F61E-A047-47B8-B68A-C0F2C96D33CD@nominum.com>
In-Reply-To: <FDD4F61E-A047-47B8-B68A-C0F2C96D33CD@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/xe44SjUtZAZ6eM_OUDX6sGcaQDA>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 16:18:40 -0000

Le 10/04/2015 18:08, Ted Lemon a écrit :
> On Apr 10, 2015, at 11:14 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> Again - if you put there 128 you loose all your neighbors.
>
> Okay, so if I understand you, what you are saying is that if you
> install a /128 route to the IA_NA address, then that will remove any
> route to that a narrower prefix containing that /128.   But that's
> not true.

Right (although I am not saying that a route is removed).

> The /128 route will only match the one IP address that it was added
> for;

YEs.

> if there is already a route for the /64 that contains the /128,

who put that /64 route there?  The faulty dhclient?  DHCP doesnt, RA doesnt.

> then installing the /128 will not prevent the /64 from working, and
> you will be able to communicate with your neighbors just fine.

Yes.  But if you install a /128 you will not install a /64 too;
because nobody tells you to install a /64.

It is in that sense that you lose your neighbors: you dont install a 64
because that RFC tells you you must not deduce and install a 64 if all
you get is an address from DHCP.

> However, if all you have is the IA_NA, then addresses that are in
> that /64 are not guaranteed to be on-link.

Yes.

Alex

>
>
>



From nobody Fri Apr 10 09:26:08 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E76371ABC0F for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 g4MGK19Aoc5v for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:26:05 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 588C81A92B3 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 09:26:05 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 0D3DC1BC3E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 16:26:02 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5527F7C2.2010409@gmail.com>
Date: Fri, 10 Apr 2015 17:26:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <210FD351-3442-4F58-902A-E1EEBA1216D6@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <FDD4F61E-A047-47B8-B68A-C0F2C96D33CD@nominum.com> <5527F7C2.2010409@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/GbyGauMnaQMsg19imwIEeblt3N8>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 16:26:07 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> if there is already a route for the /64 that contains the /128,
>=20
> who put that /64 route there?  The faulty dhclient?  DHCP doesnt, RA =
doesnt.

RA **WILL** if it's configured to. Eg, on an ethernet network, if you =
are using a /64 on it, then your RA would specify that that prefix is =
on-link and the OS stack will then add a route to the /64  - or more =
correctly, add the /64 prefix to it's list of known prefixes, which will =
most likely manifest itself in the UI as a "route".
Or it could have been manually configured by an administrator.

>> then installing the /128 will not prevent the /64 from working, and
>> you will be able to communicate with your neighbors just fine.
>=20
> Yes.  But if you install a /128 you will not install a /64 too;
> because nobody tells you to install a /64.

If the RA tells you to, you install it. If the administrator manually =
configures it, then you install it.

>> However, if all you have is the IA_NA, then addresses that are in
>> that /64 are not guaranteed to be on-link.
>=20
> Yes.

Which is why you **MUST NOT** deduce that when getting an address, other =
addresses in the prefix you infer applies to it are directly reachable.


From nobody Fri Apr 10 09:33:16 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 516B31A8BB2 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 8R3aTyyqTfOB for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:33:13 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id AFF4B1A82E2 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 09:33:12 -0700 (PDT)
X-Quarantine-ID: <Ug1Q1wyjWqhO>
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
X-Amavis-Alert: BAD HEADER SECTION, Header line longer than 998 characters: References: <CA[...]
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 078771BC3E for <dhcwg@ietf.org>; Fri, 10 Apr 2015 16:33:09 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <5527F566.6080402@gmail.com>
Date: Fri, 10 Apr 2015 17:33:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <322C629A-9121-467D-B92F-8539B9F4B95F@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk> <5527EF2D.1020506@gmail.com> <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk> <5527F5 66.6080402@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/o8qshkuV6ABsKnuX5EMfBUqbFjY>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 16:33:14 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> Not necessarily. They could all be /128, they could be in a /64, or
>> they could be in a /56, or they could be in a /48, or ...
>=20
> We know that only three IP addresses are there.  The longest prefix
> stringing them would be a /126.  Other plens like /48 and /64 are also
> possible but would represent an enormous address waste.

No, you still will not let go of that IPv4 thinking.
You could have thousands of end devices on the network, all using =
addresses from one /64 prefix.

>> Now please answer the question I asked - and in case it wasn't clear
>> enough I'll change it slightly. If two end devices (say smartphone A
>> and smartphone B) are connected to your network, does the network
>> technology allow them to directly communicate (ie direct A-B) or
>> does communication have to go via a router (ie A-R-B) ? Ignore
>> addressing, whether it's IPv4 or IPv6, at the lowest network level -
>> can they directly exchange packets ?
>=20
> I can answer you by digging something, but I dont know why you ask.
>=20
> Intuitevely, that is where cellular systems go: A talk directly to B =
at
> IP layer.  Link-layer packets may continue go to R for
> some time and maybe (just maybe) one day they won't, although it is =
unsure.
>=20
>> And if they can, are the restrictions (such as them having to be
>> "signed in" with the same cell/controller) for it to work, or will
>> it work regardless of the device location/the cell it's signed in
>> with/ etc ?
>=20
> That I couldnt know, because I would need a special traffic analyzer =
to
> show these link-layer headers - I dont have that and I dont want to =
get one.
>=20
> Why is this related to our discussion on prefix lengths?

It's related to why you think things are broken. Now we find that you do =
not even know how the network works. If you don't know fundamentals like =
that, then you cannot say things are broken.

You do not need a protocol analyser - you should be able to answer the =
question. Can subscriber device A send a packet directly to subscriber =
device B, under all circumstances ? Can device A find device B by =
broadcast, or does it need to be told the hardware address to use by a =
third party (ie router) ?

You **NEED** to know things like this, if you can describe your network, =
someone can probably tell you what's wrong - though that's out of scope =
for this list, it's effectively where this thread has been going for 2 =
days.
If someone explains what is wrong and how to fix it, perhaps then you'll =
accept that the concepts you are being told actually do work !
If you can't describe *your* network, then there's no point carrying on =
the discussion - because we don't know for you.




From nobody Fri Apr 10 09:43:36 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 671DC1A86F6 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 L9wL_XCPqM6K for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 09:43:33 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E17E1ACE19 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 09:43:33 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3AGhVnP029000 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 18:43:31 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6817820A882 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 18:44:38 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 607E820A86F for <dhcwg@ietf.org>; Fri, 10 Apr 2015 18:44:38 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3AGh4AY011004 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 18:43:31 +0200
Message-ID: <5527FD98.2000100@gmail.com>
Date: Fri, 10 Apr 2015 18:43:04 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <FDD4F61E-A047-47B8-B68A-C0F2C96D33CD@nominum.com> <5527F7C2.2010409@gmail.com> <210FD351-3442-4F58-902A-E1EEBA1216D6@thehobsons.co.uk>
In-Reply-To: <210FD351-3442-4F58-902A-E1EEBA1216D6@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/1zhacMHGk9WJtzOlxaAvolsbajg>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 16:43:35 -0000

Le 10/04/2015 18:26, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>> if there is already a route for the /64 that contains the /128,
>>
>> who put that /64 route there?  The faulty dhclient?  DHCP doesnt,
>> RA doesnt.
>
> RA **WILL** if it's configured to.

It's configured to be sent only once, and only at the beginning of the
connection process.  After that, the subsequent RAs dont have a plen.

It's as if you put up and down your interface to see an RA/plen.

This is ok for smartphones who browse the web now and then, but it is
less ok for computer permanently connected on cellular links.

Of course - one could ask the network operator to put /64 in all
subsequent RAs.  But there are reasons for that request to get rejected,
and I already told you some of these reasons.

Btw, there may be other reasons for the operator to reject putting a /64
in each DHCP message as well, I dont know.

> Eg, on an ethernet network, if you are using a /64 on it, then your
> RA would specify that that prefix is on-link and the OS stack will
> then add a route to the /64  - or more correctly, add the /64 prefix
> to it's list of known prefixes, which will most likely manifest
> itself in the UI as a "route". Or it could have been manually
> configured by an administrator.

Yes and yes.

>>> then installing the /128 will not prevent the /64 from working,
>>> and you will be able to communicate with your neighbors just
>>> fine.
>>
>> Yes.  But if you install a /128 you will not install a /64 too;
>> because nobody tells you to install a /64.
>
> If the RA tells you to, you install it. If the administrator
> manually configures it, then you install it.

The RA tells it so just once.  If you lose that once then it's lost
forever.  You can solicit other RAs, you get them, but they dont have
prefixes in them.

>>> However, if all you have is the IA_NA, then addresses that are in
>>> that /64 are not guaranteed to be on-link.
>>
>> Yes.
>
> Which is why you **MUST NOT** deduce that when getting an address,
> other addresses in the prefix you infer applies to it are directly
> reachable.

I do not infer any prefix or prefixlen from an address.  I want to be
told the prefixlen.  I dont want to imagine one.

Alex

>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Fri Apr 10 10:05:03 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B09131B29B0 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 10:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 7zG2RRjQYry9 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 10:05:00 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F07EC1B29A2 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 10:04:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3AH4wHm001648 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 19:04:58 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4C7D5204E50 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 19:06:05 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 449FE200E0D for <dhcwg@ietf.org>; Fri, 10 Apr 2015 19:06:05 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3AH4YuN010681 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 19:04:57 +0200
Message-ID: <552802A2.5000209@gmail.com>
Date: Fri, 10 Apr 2015 19:04:34 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk> <5527EF2D.1020506@gmail.com> <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk> <5527F5 66.6080402@gmail.com> <322C629A-9121-467D-B92F-8539B9F4B95F@thehobsons.co.uk>
In-Reply-To: <322C629A-9121-467D-B92F-8539B9F4B95F@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/JzXGFKVUeGRYF4ymGGoCfS03N5o>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 17:05:01 -0000

Le 10/04/2015 18:33, Simon Hobson a écrit :
[...]
> You do not need a protocol analyser - you should be able to answer
> the question. Can subscriber device A send a packet directly to
> subscriber device B, under all circumstances ?

YEs it can but what do you mean by 'directly'.

> Can device A find device B by broadcast, or does it need to be told
> the hardware address to use by a third party (ie router) ?

In principle, A should be able to try to find B by multicasting an NS.
I would need to check whether a Redirect is present but I havent seen
any up to now.  There are MLD REPORTs about joining these local groups.

But of course this being a cellular system, and evolving as we speak,
quirks are present here and there, like IEEE-allocated MAC addresses for
3GPP interfaces, using all 24 bits 0 on the interface specific.

> You **NEED** to know things like this, if you can describe your
> network, someone can probably tell you what's wrong - though that's
> out of scope for this list, it's effectively where this thread has
> been going for 2 days. If someone explains what is wrong and how to
> fix it, perhaps then you'll accept that the concepts you are being
> told actually do work ! If you can't describe *your* network, then
> there's no point carrying on the discussion - because we don't know
> for you.

Let me clarify - I do not ask anybody to debug this deployment.  It
works for the purposes it is designed.  It is a huge step forward from
before.  It has other advantages over other cellular systems, like
offering simultaneous IPv4 and IPv6.

I tell you how things happen there to explain why RA is not something
that is always there.

In Ethernet in general one is right to assume RA/plen always there.  But
that is not the case for e.g. some particular cellular system.

Alex

>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Fri Apr 10 12:00:38 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379AA1B2E6F for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 12:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 mT5Fkfxvh38Q for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 12:00:35 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70ACF1B2DF1 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 12:00:25 -0700 (PDT)
Received: by iedfl3 with SMTP id fl3so27995610ied.1 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 12:00:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PHlAqBQilxJxDlPbF57LFWcfobPQDj5mneoM1lisUnw=; b=EUSiUiIk1iDfTUnS/XQkf45BHGuf489Xygrg29bYOjLkNMN287Gv3gVPEomTb0twrT NF2gVQSFFaA0hy8P833jv10tk3L1XUOLN0PMkQcxS1HloheauzckBFP1Q8D5POs2io/B OrH3ztmru1sA1h7+3OBX5zBJIsQJxJhIos3TulAfcaoZsT4Gr1oZgUAnk8CMB55Ai4Mu JZv/7WC/a0mtMDKnPplmDAfK1HO2GGzNsCr6Jm12u2jFkl39OJFerk29zgVpWrYIi4TR fjDwJWC0DTx7vXZsJdu1nFIkddEPetFyQOcBlip1PC3UYvl0QgpXEF6dCHK+M5crUANi 8Y6Q==
MIME-Version: 1.0
X-Received: by 10.43.163.71 with SMTP id mn7mr5551709icc.72.1428692424850; Fri, 10 Apr 2015 12:00:24 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.21.3 with HTTP; Fri, 10 Apr 2015 12:00:24 -0700 (PDT)
In-Reply-To: <5526658C.8000708@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com>
Date: Fri, 10 Apr 2015 12:00:24 -0700
X-Google-Sender-Auth: 5bK5-3JWlWAO5DRjLRZbLAP25-s
Message-ID: <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SuPAM1pe-CK2vjT9cYw52XjkQ8E>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 19:00:37 -0000

At Thu, 09 Apr 2015 13:42:04 +0200,
Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> >> Is '128' the correct prefixlen to add to an address when putting
> >> it on an interface?  Or is 64 the correct prefixlen?
> >
> > Neither.  There is *no* prefix length associated with an address. The
> > prefix lengths are associated with the *prefixes* assigned to the
> > link.
>
> This means that either there are no correct implementations of IPv6 out
> there, or that a prefix must always assigned when an address is assigned.

It seems to me that several things are conflated:

A. Externally visible behavior of an implementation (e.g., whether one
   implementation can reach another after some kind of events like
   getting an RA or DHCP-based address assignment)
B. Internal implementation details to realize the behavior
C. Operational interface exposed to the user of an implementation

In general, my understanding is that if we talk about "correctness" in
terms of protocol conformance, only point A matters.  Some
implementations may have something ugly in their implementation
details due to, e.g., historical constraints, but as long as
externally visible behavior conforms to what the protocol
specification states, it's generally considered "correct".

In that sense I believe most of existing implementations are actually
correct in terms of address and prefix relationship.

I don't know much about Linux internal, but BSD variants clearly
separate the concepts of address and prefix in the kernel internal
(you can see the latter by 'ndp -p'), and determine whether a
particular destination is directly reachable just on the prefix
information.

You can indeed specify the "prefix length" when you manually configure
an address, but this is actually a shortcut of manually configuring an
address (which doesn't have a concept of prefix length) and manually
configuring an on-link prefix derived from the address and the prefix
length.

I admit there may still be some confusing part, especially in user
interfaces (e.g., in retrospect, it was a bad idea to use the default
value of 64 for prefix length in BSD's ifconfig implementation), but
it's not because implementors didn't understand the spec or the spec
was unclear, but mainly due to technical compromise between protocol
purity and compatibility/meeting expectations of legacy users.

I also tend to agree that there's some gap to be filled in the sense
of protocol discussion: today it's not very clear how to manage an
isolated network using DHCPv6-based address assignment.  (Although
IMO this should be outside of rfc3315bis) just saying "run an
RA-advertising server/router" is probably not enough at least in
practice.  Also, if there's really a common case where running an
RA-advertising node isn't feasible (I don't think the operational cost
is a critical reason - if it's really needed it shouldn't be that
difficult to unify that feature in a DHCPv6 server implementation),
there may actually be a technical gap that has to be filled with some
protocol extensions.  Only then it makes sense to discuss a specific
solution like providing on-link prefix information via DHCPv6.

>From the discussion so far, I wasn't even convinced whether you
deployment example proves the need for *some* protocol enhancements.
Simply repeating the need for a specific solution of 'prefix-info by
DHCPv6' without even persuading others on the problem won't get us
anywhere.

So, if I may, my suggestion for you is to write an I-D explaining why
you cannot deploy your network with a router (or any node) that keeps
advertising RAs.  If it's convincing enough we can then move on to the
next step.

--
JINMEI, Tatuya


From nobody Fri Apr 10 12:02:35 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDFF91B2D7C for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 12:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 0PleCn996MTN for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 12:02:31 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 7FEB01B2D8B for <dhcwg@ietf.org>; Fri, 10 Apr 2015 12:02:11 -0700 (PDT)
Received: from [181.29.103.112] (helo=[192.168.1.120]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YgeBs-0004nL-FQ; Fri, 10 Apr 2015 21:02:09 +0200
Message-ID: <5527FA77.5070301@si6networks.com>
Date: Fri, 10 Apr 2015 13:29:43 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com>
In-Reply-To: <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/a9c4_w9QzS7fIT2Ek2kjpyIH6DU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 19:02:34 -0000

On 04/09/2015 08:20 PM, Lorenzo Colitti wrote:
> On Fri, Apr 10, 2015 at 4:34 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > This concept is flawed if the servers aren't cooperating. If there
>     > are multiple servers that don't share lease data, how does server 1
>     > know whether the lease was leased to another client or renewed, if
>     > server 2 ends up communicating with the client?
> 
>     Usually, you need servers to communicate because there's no way to tell
>     which address each server may have assigned to which client. But that's
>     not the case with this method.
> 
> 
> It is still the case even with this method, because the servers need to
> agree on the value of the counter variable. 

The Counter value is there for completeness sake. Me, I don't expecThe
assumption is that thanks to the huge address space, you want hit
collisions.

In order for this scheme to not result in address stability, two things
must happen:

1) There address collisions -- considered extremely unlikely, and,

2) Clines employ different DHCPv6 servers (failover scenario), and,

2) The two nodes that bootstrap do so in a different order (otherwise,
they will still be leased the same addresses).

I'd say that a DHCPv6 servers is free to store the Counter value for
each lease, if they please. But it's not worth it to synchronize it. --
the assumption in this scheme is that the address space for the local
subnet is so large that you will not find collisions.

If you, we could rename the I-D as "probabilistically stable" -- but I
hope that's not needed.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Apr 10 12:54:06 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 126E31A87B2 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 12:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ZpXfE1TqQ0Mk for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 12:54:03 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 1A7C51A1B76 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 12:54:03 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id EC9A7DA00D8; Fri, 10 Apr 2015 19:54:02 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 10 Apr 2015 12:54:02 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <5527F7C2.2010409@gmail.com>
Date: Fri, 10 Apr 2015 15:53:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <EA232E89-370A-4750-BCAA-F6FCD7F45175@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <FDD4F61E-A047-47B8-B68A-C0F2C96D33CD@nominum.com> <5527F7C2.2010409@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/tU2cPfD41DF64UuZVmyXPhJssaU>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 19:54:04 -0000

On Apr 10, 2015, at 12:18 PM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
>> then installing the /128 will not prevent the /64 from working, and
>> you will be able to communicate with your neighbors just fine.
>=20
> Yes.  But if you install a /128 you will not install a /64 too;
> because nobody tells you to install a /64.
>=20
> It is in that sense that you lose your neighbors: you dont install a =
64
> because that RFC tells you you must not deduce and install a 64 if all
> you get is an address from DHCP.

No, in that case you never had any neighbors.   There is no event that =
can be described as "losing your neighbors."


From nobody Fri Apr 10 13:04:54 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE9C51A87E8 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 13:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7AQ0qKktUqj9 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 13:04:51 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 34EF31A882C for <dhcwg@ietf.org>; Fri, 10 Apr 2015 13:04:42 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 236F1DA00D8; Fri, 10 Apr 2015 20:04:42 +0000 (UTC)
Received: from [10.0.20.187] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 10 Apr 2015 13:04:41 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <552802A2.5000209@gmail.com>
Date: Fri, 10 Apr 2015 16:04:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <BF3BD337-C2BC-4FD6-B331-8A0A4397004F@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk> <5527EF2D.1020506@gmail.com> <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk> <5527F5 66.6080402@gmail.com> <322C629A-9121-467D-B92F-8539B9F4B95F@thehobsons.co.uk> <552802A2.5000209@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/UGn7xAj391-3jKYheTNi-etX4nc>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 20:04:53 -0000

On Apr 10, 2015, at 1:04 PM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
> In principle, A should be able to try to find B by multicasting an NS.
> I would need to check whether a Redirect is present but I havent seen
> any up to now.  There are MLD REPORTs about joining these local =
groups.
>=20
> But of course this being a cellular system, and evolving as we speak,
> quirks are present here and there, like IEEE-allocated MAC addresses =
for
> 3GPP interfaces, using all 24 bits 0 on the interface specific.

Alex, Simon is talking about what happens at layer 1 and 2, not at layer =
2.5.   And what happens at layers 1 and 2 is that handsets do not =
communicate, because they do not have dependable propagation.  Handset =
A, in order to talk to handset B, sends its packet to router R, which =
forwards it to handset B.   Handsets never communicate directly with =
each other.   This is true not only of cellular networks, but also of =
wifi infrastructure networks.=


From nobody Fri Apr 10 16:11:54 2015
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2073E1B2E3F for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 16:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 afsToWpZHNS6 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 16:11:51 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E41191B2E3D for <dhcwg@ietf.org>; Fri, 10 Apr 2015 16:11:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t3ANBoxD027311; Fri, 10 Apr 2015 16:11:50 -0700
Received: from XCH-BLV-301.nw.nos.boeing.com (xch-blv-301.nw.nos.boeing.com [130.247.25.213]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t3ANBlln027307 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for <dhcwg@ietf.org>; Fri, 10 Apr 2015 16:11:48 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.120]) by XCH-BLV-301.nw.nos.boeing.com ([169.254.1.111]) with mapi id 14.03.0235.001; Fri, 10 Apr 2015 16:11:47 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Delegating IPv4 addresses with DHCPv6 Prefix Delegation
Thread-Index: AdBz4juL4rin49V4SsuyHkcxI+BbCQ==
Date: Fri, 10 Apr 2015 23:11:46 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E44E77@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/AxbQEnK1EnEw3pqRGDqsoEi_hr8>
Subject: [dhcwg] Delegating IPv4 addresses with DHCPv6 Prefix Delegation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 23:11:53 -0000

Hi,

AERO is doing something with ordinary DHCPv6 Prefix Delegation that this gr=
oup
might find interesting. Client nodes that need to configure an IPv4 address=
 use
DHCPv6 Prefix Delegation to receive an IPv4-Mapped IPv6 prefix. The client
contacts the DHCPv6 server via tunneling over an IPv6 network. The delegate=
d
prefix is of the form:

    ::FFFF:192.0.2.1/128

When the client receives the delegated prefix from the server, it assigns t=
he IPv4
address (i.e., 192.0.2.1) to a virtual interface. The client can then use t=
he address
for IPv4-in-IPv6 tunneling.

Note that this requires no new DHCPv6 messages, nor any carriage of DHCPv4
messages. The spec is here:

https://datatracker.ietf.org/doc/draft-templin-aerolink/

Comments?

Thanks - Fred
fred.l.templin@boeing.com


From nobody Fri Apr 10 21:39:08 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 266681B2FB0 for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 21:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 C-wKFaXmQier for <dhcwg@ietfa.amsl.com>; Fri, 10 Apr 2015 21:39:05 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60CFA1B2FB1 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 21:39:05 -0700 (PDT)
Received: by igbqf9 with SMTP id qf9so12464960igb.1 for <dhcwg@ietf.org>; Fri, 10 Apr 2015 21:39:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=hz/4xWOSHZEY5aP9LEY+irZsQjk/13nYWVN6kLQB7oI=; b=BH8ZbY+5KrbetPl54Juba581PwJ9d9JSn/df9OVgCUivVY0nCxlgbJ5VK7NLzJReKz oJZfBM2V+I5u6BI20CsY4PdHwdQ+7wys+3TcFOJo2OvDRsVvmm/30pqq6Hy9fA7oQx89 l4pbYmVnROfUKYkVqGFz551hqLX+6jN9VEFPWDhIF8gI4dMBXxN3p7ZxsGke3Rz3rq6W RhVZa4kNDIofcNmEzoxV57OG2mDP2S/Ir+c9Kmn/aljf5OqDGyld1DMBTZz4mahD7aAR 1yTPKfHEyfbFF6I7I4Iyc9V5I6XjCS0iAu2gc68Qpks3jO95uRQU3nY7DF0v2Qie3iA8 H3Zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=hz/4xWOSHZEY5aP9LEY+irZsQjk/13nYWVN6kLQB7oI=; b=JHhhIwN1eJNh5XvtiHFNuTS6cpQpQGWAEPHlrgyIg5eMjyRO0GguOX4LGBt4cZNnbQ Zzr4ZdC/XteUyPFqt+Lz66EDZPe0p3tObcDDZOzWv4YGguVj+TXd9mWFTyyTpuK/jrix EWzXqtlEuvb1HGMr3RDPR+ANWCIz2Vvug2eVXXeaLdti3/Q1aSIVTr9slLHROHOIOz7w Yt2W/bOn6MYHjdx8SVGdKGnZ+sqtXV1DN9AiDH+B3vw+EoNS/fDjDtqa90C6cCjUY7yu qyl5BgJ1VGQ2dmz2BN1b4dRLTU4DRcSh8YXKJW7+KwL8TjAX2+gyYMKvfrRsZk7jSKaz cDHw==
X-Gm-Message-State: ALoCoQmZG/ZTPutCE0FMWWqED/2K+hBC6YcUOEHk/XPYv7atxTewJZhB9WtfCz6llMQOfknlpGIK
X-Received: by 10.50.4.97 with SMTP id j1mr2841001igj.46.1428727144809; Fri, 10 Apr 2015 21:39:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.195.75 with HTTP; Fri, 10 Apr 2015 21:38:44 -0700 (PDT)
In-Reply-To: <5527FA77.5070301@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com> <5527FA77.5070301@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 11 Apr 2015 13:38:44 +0900
Message-ID: <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a11c2cd4ef2ae1405136b7530
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/m1LYjrgwM-JCVsBr5b0ZZA0MjSI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2015 04:39:07 -0000

--001a11c2cd4ef2ae1405136b7530
Content-Type: text/plain; charset=UTF-8

On Sat, Apr 11, 2015 at 1:29 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> On 04/09/2015 08:20 PM, Lorenzo Colitti wrote:
> >     > This concept is flawed if the servers aren't cooperating. If there
> >     > are multiple servers that don't share lease data, how does server 1
> >     > know whether the lease was leased to another client or renewed, if
> >     > server 2 ends up communicating with the client?
> >
> >     Usually, you need servers to communicate because there's no way to
> tell
> >     which address each server may have assigned to which client. But
> that's
> >     not the case with this method.
> >
> >
> > It is still the case even with this method, because the servers need to
> > agree on the value of the counter variable.
>
> The Counter value is there for completeness sake. Me, I don't expecThe
> assumption is that thanks to the huge address space, you want hit
> collisions.
>

But you have to say what happens in this case. If the client sends a
DECLINE for any reason, what happens? Is it dead in the water with the
wrong IP address? Does the server just respond with the same IP address as
before, hoping that the client will like it? If you don't want the draft to
specify the behaviour, you should at least provide a list of the possible
options, because from what I see, the possible options are all bad.


> I'd say that a DHCPv6 servers is free to store the Counter value for
> each lease, if they please. But it's not worth it to synchronize it. --
> the assumption in this scheme is that the address space for the local
> subnet is so large that you will not find collisions.
>
> If you, we could rename the I-D as "probabilistically stable" -- but I
> hope that's not needed.


One of the major objections I have here is that the draft says that the
addresses are stable and stateless. However, that statement is not true in
the presence of DECLINEs, collisions, or misconfigurations (probably more
likely than collisions). If the draft didn't say the addresses are stable,
or if it didn't say that the addresses can be calculated statelessly, then
that would be OK, but it does. I think that if you want to standardize this
approach, then IMO you need to quantify what happens in these cases.

Also, I think statelessness is pointless. DHCPv6 is a fundamentally
stateful protocol. It's not just the lease database - clients and servers
also keep track of IAs, server IDs, client IDs, DUIDs. Even if you make the
address calculation stateless, to show value you'll need to show whether
this scheme works when you swap out servers. If it this scheme doesn't work
when you swap servers, then there's really no point in making the address
calculation stateless, since you need to share state anyway.

More in general. Whether you continue work on this document is to you, but
I'll point out that Bernie has stated multiple times that he wants to see
people support this draft, not just "not object to it". I don't see much in
the way of support today. As far as I'm concerned, you may be able to
address the issues that I list above and remove some of the objections, but
I doubt you'll be able to convince me personally that this scheme has value
and turn me into supporter.

Cheers,
Lorenzo

--001a11c2cd4ef2ae1405136b7530
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, Apr 11, 2015 at 1:29 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bord=
er-left-style:solid;padding-left:1ex"><span>On 04/09/2015 08:20 PM, Lorenzo=
 Colitti wrote:<br></span><div><div>&gt;=C2=A0 =C2=A0 =C2=A0&gt; This conce=
pt is flawed if the servers aren&#39;t cooperating. If there<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; are multiple servers that don&#39;t share leas=
e data, how does server 1<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; know whether the lease was leased to another c=
lient or renewed, if<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; server 2 ends up communicating with the client=
?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Usually, you need servers to communicate because th=
ere&#39;s no way to tell<br>
&gt;=C2=A0 =C2=A0 =C2=A0which address each server may have assigned to whic=
h client. But that&#39;s<br>
&gt;=C2=A0 =C2=A0 =C2=A0not the case with this method.<br>
&gt;<br>
&gt;<br>
&gt; It is still the case even with this method, because the servers need t=
o<br>
&gt; agree on the value of the counter variable.<br>
<br>
</div></div>The Counter value is there for completeness sake. Me, I don&#39=
;t expecThe<br>
assumption is that thanks to the huge address space, you want hit<br>
collisions.<br></blockquote><div><br></div><div>But you have to say what ha=
ppens in this case. If the client sends a DECLINE for any reason, what happ=
ens? Is it dead in the water with the wrong IP address? Does the server jus=
t respond with the same IP address as before, hoping that the client will l=
ike it? If you don&#39;t want the draft to specify the behaviour, you shoul=
d at least provide a list of the possible options, because from what I see,=
 the possible options are all bad.</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">=
I&#39;d say that a DHCPv6 servers is free to store the Counter value for<br=
>
each lease, if they please. But it&#39;s not worth it to synchronize it. --=
<br>
the assumption in this scheme is that the address space for the local<br>
subnet is so large that you will not find collisions.<br>
<br>
If you, we could rename the I-D as &quot;probabilistically stable&quot; -- =
but I<br>
hope that&#39;s not needed.</blockquote><div><br></div><div>One of the majo=
r objections I have here is that the draft says that the addresses are stab=
le and stateless. However, that statement is not true in the presence of DE=
CLINEs, collisions, or misconfigurations (probably more likely than collisi=
ons). If the draft didn&#39;t say the addresses are stable, or if it didn&#=
39;t say that the addresses can be calculated statelessly, then that would =
be OK, but it does. I think that if you want to standardize this approach, =
then IMO you need to quantify what happens in these cases.<br></div><div><b=
r></div><div>Also, I think statelessness is pointless. DHCPv6 is a fundamen=
tally stateful protocol. It&#39;s not just the lease database - clients and=
 servers also keep track of IAs, server IDs, client IDs, DUIDs. Even if you=
 make the address calculation stateless, to show value you&#39;ll need to s=
how whether this scheme works when you swap out servers. If it this scheme =
doesn&#39;t work when you swap servers, then there&#39;s really no point in=
 making the address calculation stateless, since you need to share state an=
yway.</div><div><br></div><div>More in general.=C2=A0<span style=3D"color:r=
gb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal=
;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:n=
ormal;text-align:start;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;float:none;display:inline!important;background-color:rg=
b(255,255,255)">Whether you continue work on this document is to you, but I=
&#39;ll point out that=C2=A0</span>Bernie has stated multiple times that he=
 wants to see people support this draft, not just &quot;not object to it&qu=
ot;. I don&#39;t see much in the way of support today. As far as I&#39;m co=
ncerned, you may be able to address the issues that I list above and remove=
 some of the objections, but I doubt you&#39;ll be able to convince me pers=
onally that this scheme has value and turn me into supporter.</div><div><br=
></div><div>Cheers,</div><div>Lorenzo</div></div></div></div>

--001a11c2cd4ef2ae1405136b7530--


From nobody Sat Apr 11 02:39:46 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFA421A8743 for <dhcwg@ietfa.amsl.com>; Sat, 11 Apr 2015 02:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7IzcQ1EFdzst for <dhcwg@ietfa.amsl.com>; Sat, 11 Apr 2015 02:39:43 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 456F01A872B for <dhcwg@ietf.org>; Sat, 11 Apr 2015 02:39:42 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.61] (88-111-162-175.dynamic.dsl.as9105.com [88.111.162.175]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id B2FE51BC3E for <dhcwg@ietf.org>; Sat, 11 Apr 2015 09:39:37 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <552802A2.5000209@gmail.com>
Date: Sat, 11 Apr 2015 10:39:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C50D7937-1472-465E-AB40-7A468E0D2295@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk> <5527EF2D.1020506@gmail.com> <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk> <5527F5 66.6080402@gmail.com> <322C629A-9121-467D-B92F-8539B9F4B95F@thehobsons.co.uk> <552802A2.5000209@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/5I_r8xof2_guQGoKVZbLyCMAUF4>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2015 09:39:46 -0000

On 10 Apr 2015, at 18:04, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:

> Let me clarify - I do not ask anybody to debug this deployment.

Well actually, indirectly you are. Because you are adamant that the =
standards are wrong because **YOUR DEPLOYMENT** doesn't work properly - =
and you are not prepared to accept that perhaps the standards are right =
*IFF* the deployment is done properly. I am certain that your deployment =
is wrong, because several things you have said about it do not make =
sense.
* Note: deployment includes the clients.


Now, taking a few things said, adding what (not a lot) I know about =
cellular and radio systems (architecturally, treat them as a hub and =
spoke arrangement with a load of P-P links), and this is what I think =
should be happening.


You have a base infrastructure with router(s), DHCP server(s), and of =
course - all the radio gear and pipes to hook it all together.

A subscriber comes along and signs in with the network. The back end =
system (through whatever means) determines an IPv6 address for the =
client. This address (**NO** prefix) is delivered to the client (via PPP =
or DHCP or something else according to the technology in use) which =
configures it on it's interface.
The client addresses may be determined in many ways. Most likely, the =
simplest will be a single /56 or /48 block across the whole network. It =
may also be a /64 or /56 across a smaller part of the network (say a =
region managed by one management node). That is a design issue for =
whoever creates it.

Alongside this, the router(s) may or may not send an unsolicited RA. =
Because the clients can't realistically talk directly to all other =
clients in the prefix, any RAs sent do **NOT** contain any on-link =
prefixes. The RAs will of course contain router information.

At this point, the client is now a working IPv6 node. It has an IPv6 =
address, it does not think any other IPv6 addresses are "on-link", and =
it knows the address of at least one router it can use to send packets.
Note that the client has just two pieces of information : it's address, =
and the address of a router. It has **NO** prefixes configured.

When the client wants to communicate with the DHCP server, it sends it's =
renewal packet to the router. In such a setup, I'd expect that to be =
handled by a relay agent rather than being attached to the link =
directly. The router will either relay the packet (relay agent), or it =
will forward it. In the unlikely event that the client node can actually =
send packets directly to the DHCP server without going through the =
router, then the router will send an ICMP redirect and the node will =
then know that the server is on-link.

The client will need to periodically send Router Solicitation messages =
to get fresh RAs. As you point out, for a client that's only active =
intermittently, this is probably more efficient that the router =
broadcasting them all the time.

Normal internet traffic will of course just go out through the router.

Should one client node wish to talk to another client node, then things =
get more interesting. In the general case, I would not expect this to be =
possible - it would be inefficient to allow one client to send a =
broadcast (multicast) message out across your whole network and to all =
other subscribers ! So my expectation is that all traffic would go via =
the gateway router regardless of destination.
However, if client-client communication is possible and allowed - which =
might be possible in a subset of cases such as both clients attached to =
same cell tower - then if the router determines that this is possible, =
it may send an ICMP redirect to one of the clients informing it that the =
other client is directly reachable. I would doubt if this would be =
allowed at all though for various management and technical reasons.


> In Ethernet in general one is right to assume RA/plen always there.  =
But
> that is not the case for e.g. some particular cellular system.

So you are now allowing for the prefix length to not be there, after =
spending several days arguing that it **MUST** be there and refusing to =
listen to reason.


From nobody Mon Apr 13 01:38:26 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 645DF1B2EEF for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 01:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.283
X-Spam-Level: 
X-Spam-Status: No, score=-2.283 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 s44xHr-_LnGp for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 01:38:24 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEEE51B2EEB for <dhcwg@ietf.org>; Mon, 13 Apr 2015 01:38:23 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3D8cLs7016481; Mon, 13 Apr 2015 10:38:21 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C36AE20B87B; Mon, 13 Apr 2015 10:39:32 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B754920B6DA; Mon, 13 Apr 2015 10:39:32 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3D8cFK1008520; Mon, 13 Apr 2015 10:38:21 +0200
Message-ID: <552B8077.8060201@gmail.com>
Date: Mon, 13 Apr 2015 10:38:15 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <FDD4F61E-A047-47B8-B68A-C0F2C96D33CD@nominum.com> <5527F7C2.2010409@gmail.com> <EA232E89-370A-4750-BCAA-F6FCD7F45175@nominum.com>
In-Reply-To: <EA232E89-370A-4750-BCAA-F6FCD7F45175@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/LuqJAqv-pC296c-_SoWC-QTid9A>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 08:38:25 -0000

Le 10/04/2015 21:53, Ted Lemon a écrit :
> On Apr 10, 2015, at 12:18 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>>> then installing the /128 will not prevent the /64 from working,
>>> and you will be able to communicate with your neighbors just
>>> fine.
>>
>> Yes.  But if you install a /128 you will not install a /64 too;
>> because nobody tells you to install a /64.
>>
>> It is in that sense that you lose your neighbors: you dont install
>> a 64 because that RFC tells you you must not deduce and install a
>> 64 if all you get is an address from DHCP.
>
> No, in that case you never had any neighbors.   There is no event
> that can be described as "losing your neighbors."
>
>

Losing ability to have neighbors (run ND).

Alex



From nobody Mon Apr 13 01:39:54 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0586A1B2EEF for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 01:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 KM1559S0toVa for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 01:39:51 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48B3D1B2EEE for <dhcwg@ietf.org>; Mon, 13 Apr 2015 01:39:51 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3D8dlkV001765; Mon, 13 Apr 2015 10:39:49 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8997820B8A1; Mon, 13 Apr 2015 10:41:00 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 7E0B020B6DA; Mon, 13 Apr 2015 10:41:00 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3D8dl9A009823; Mon, 13 Apr 2015 10:39:49 +0200
Message-ID: <552B80D3.2090605@gmail.com>
Date: Mon, 13 Apr 2015 10:39:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk> <5527EF2D.1020506@gmail.com> <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk> <5527F5 66.6080402@gmail.com> <322C629A-9121-467D-B92F-8539B9F4B95F@thehobsons.co.uk> <552802A2.5000209@gmail.com> <BF3BD337-C2BC-4FD6-B331-8A0A4397004F@nomi! num.com>
In-Reply-To: <BF3BD337-C2BC-4FD6-B331-8A0A4397004F@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/_xnCdds7kX6J0uZtqmxZqsiX7Jw>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 08:39:53 -0000

Le 10/04/2015 22:04, Ted Lemon a écrit :
> On Apr 10, 2015, at 1:04 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> In principle, A should be able to try to find B by multicasting an
>> NS. I would need to check whether a Redirect is present but I
>> havent seen any up to now.  There are MLD REPORTs about joining
>> these local groups.
>>
>> But of course this being a cellular system, and evolving as we
>> speak, quirks are present here and there, like IEEE-allocated MAC
>> addresses for 3GPP interfaces, using all 24 bits 0 on the
>> interface specific.
>
> Alex, Simon is talking about what happens at layer 1 and 2, not at
> layer 2.5.   And what happens at layers 1 and 2 is that handsets do
> not communicate, because they do not have dependable propagation.
> Handset A, in order to talk to handset B, sends its packet to router
> R, which forwards it to handset B.   Handsets never communicate
> directly with each other.   This is true not only of cellular
> networks, but also of wifi infrastructure networks.

I agree.  At layer 1 and 2 that's how it acts in cellular and wifi,
(although ND is on top of them and considers them neighbors.)

(and there are exceptions like D2D, LTE Direct and IBSS).

Alex

>



From nobody Mon Apr 13 02:24:26 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A2C1B304F for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 02:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.283
X-Spam-Level: 
X-Spam-Status: No, score=-2.283 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 wMQ3LC2vCpTX for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 02:24:23 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0B1D1B304E for <dhcwg@ietf.org>; Mon, 13 Apr 2015 02:24:22 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3D9OL5B005665; Mon, 13 Apr 2015 11:24:21 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3EBEF20B95D; Mon, 13 Apr 2015 11:25:32 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 37C6D20B95A; Mon, 13 Apr 2015 11:25:32 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3D9Ntkd020005; Mon, 13 Apr 2015 11:24:20 +0200
Message-ID: <552B8B2B.3030803@gmail.com>
Date: Mon, 13 Apr 2015 11:23:55 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Simon Hobson <linux@thehobsons.co.uk>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAKD1Yr0sT0w17G=AgGaFqPpnxiUaq6bhH_MCbceBEUOnApRpdQ@mail.gmail.com> <55269351.10406@gmail.com> <CAKD1Yr3y_77Mokem8cV+sdkYLx42aYEeZAMvi8PEPvjme70duQ@mail.gmail.com> <55278783.2070104@gmail.com> <5DAC786D-1A65-4F25-BF18-400B8DC62348@thehobsons.co.uk> <5527B080.6010201@gmail.com> <1BAE9F3B-1A0F-46EE-8E3A-5205E28B8A28@thehobsons.co.uk> <5527CC69.40204@gmail.com> <5648C53F-0149-499E-B1AC-0F2D647EA48F@thehobsons.co.uk> <5527E8D9.9040509@gmail.com> <6859290A-8141-4FAF-81FB-82BDC3225318@thehobsons.co.uk> <5527EF2D.1020506@gmail.com> <760A8462-9E3B-4D90-991C-2416859DA940@thehobsons.co.uk> <5527F5 66.6080402@gmail.com> <322C629A-9121-467D-B92F-8539B9F4B95F@thehobsons.co.uk> <552802A2.5000209@gmail.com> <C50D7937-1472-465E-AB40-7A468E0D2295@thehobsons.co.uk>
In-Reply-To: <C50D7937-1472-465E-AB40-7A468E0D2295@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/gkXiUzoPAt9BBm-MLKuvJPLWlrs>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 09:24:25 -0000

Le 11/04/2015 11:39, Simon Hobson a écrit :
>
> On 10 Apr 2015, at 18:04, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>
>> Let me clarify - I do not ask anybody to debug this deployment.
>
> Well actually, indirectly you are. Because you are adamant that the
> standards are wrong because **YOUR DEPLOYMENT** doesn't work
> properly - and you are not prepared to accept that perhaps the
> standards are right *IFF* the deployment is done properly. I am
> certain that your deployment is wrong, because several things you
> have said about it do not make sense. * Note: deployment includes the
> clients.
>
>
> Now, taking a few things said, adding what (not a lot) I know about
> cellular and radio systems (architecturally, treat them as a hub and
> spoke arrangement with a load of P-P links), and this is what I think
> should be happening.
>
>
> You have a base infrastructure with router(s), DHCP server(s), and
> of course - all the radio gear and pipes to hook it all together.
>
> A subscriber comes along and signs in with the network. The back end
> system (through whatever means) determines an IPv6 address for the
> client. This address (**NO** prefix) is delivered to the client (via
> PPP or DHCP or something else according to the technology in use)
> which configures it on it's interface. The client addresses may be
> determined in many ways. Most likely, the simplest will be a single
> /56 or /48 block across the whole network. It may also be a /64 or
> /56 across a smaller part of the network (say a region managed by
> one management node). That is a design issue for whoever creates it.
>
> Alongside this, the router(s) may or may not send an unsolicited RA.
> Because the clients can't realistically talk directly to all other
> clients in the prefix, any RAs sent do **NOT** contain any on-link
> prefixes. The RAs will of course contain router information.
>
> At this point, the client is now a working IPv6 node. It has an IPv6
> address, it does not think any other IPv6 addresses are "on-link",
> and it knows the address of at least one router it can use to send
> packets. Note that the client has just two pieces of information :
> it's address, and the address of a router. It has **NO** prefixes
> configured.

Sure, it works.

The problems are the following: (1) all cell operators I am aware of
only deliver only a /64, not shorter.  As such that handset can't be
used for clean tethering.

(2) the setting you describe precludes the use of Neighbor Discovery.
We want ND to work on these links.  The new generation of drivers make
that ptp link loook as if it were an Ethernet link, use ND.  This
tendency is very pronounced.

> When the client wants to communicate with the DHCP server, it sends
> it's renewal packet to the router.

Yes.

> In such a setup, I'd expect that to be handled by a relay agent
> rather than being attached to the link directly.

I'd expect it too, but no, no Relay.  Because the src address of the
DHCP Advertise is a link-local address. (if it were a relay the src
would have been a global address of the Server).

Cellular deployments of IPv6 have an additional distinct legs of DHCP 
for DHCPv6 Prefix Delegation.

I find this cumbersome (two distinct legs of DHCP) - the straight
way would be to use a DHCP topology with Server and Relay. But of course
there may be other reasons for these two distinct legs, that I am not 
aware of.

> The router will either relay the packet (relay agent), or it will
> forward it. In the unlikely event that the client node can actually
> send packets directly to the DHCP server without going through the
> router, then the router will send an ICMP redirect and the node will
> then know that the server is on-link.

There's no redirect in my link.  But technologically it should be possible.

> The client will need to periodically send Router Solicitation
> messages to get fresh RAs. As you point out, for a client that's
> only active intermittently, this is probably more efficient that the
>  router broadcasting them all the time.

YEs, but there is more to that.

The refreshing RAs come from different source than the initial RA, and
the refreshing RA is half the size of the initial RA (contains no
prefix/plen).

And there are Clients needing hours-long continuous connections.

> Normal internet traffic will of course just go out through the
> router.

YEs.

> Should one client node wish to talk to another client node, then
> things get more interesting. In the general case, I would not expect
> this to be possible - it would be inefficient to allow one client to
> send a broadcast (multicast) message out across your whole network
> and to all other subscribers !

No, this is old view.

The reason applies only if we talk broadcast.

But with multicast that worry disappears.

Handsets interested to listen to ND will join that multicast group.

> So my expectation is that all traffic would go via the gateway router
> regardless of destination. However, if client-client communication is
> possible and allowed - which might be possible in a subset of cases
> such as both clients attached to same cell tower - then if the router
> determines that this is possible, it may send an ICMP redirect to one
> of the clients informing it that the other client is directly
> reachable.

I agree with you in a certain sense.

But, using ND and prefixes instead of ICMP Redirect host-based routes
has certain advantages, like small routing tables and aggregated routes.

The small world of interfaces of cellular networks slowly moves towards
this ND-capable behaviour hiding the point-to-point nature.

It has a great advantage in that LTE Direct and Device-to-Device
communications without tower become easily possible, supportable.

> I would doubt if this would be allowed at all though for various
> management and technical reasons.

Yes, there are reasons like that, e.g. the spectrum is licensed so it
must be very well controlled (large investment is at stake), and
security and identification on a per-identifier basis.

>> In Ethernet in general one is right to assume RA/plen always
>> there. But that is not the case for e.g. some particular cellular
>> system.
>
> So you are now allowing for the prefix length to not be there, after
> spending several days arguing that it **MUST** be there and refusing
> to listen to reason.

I meant to say in Ethernet RA containing plen is always there.

In cellular systems RA containing a plen is not always there.

Alex

> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>



From nobody Mon Apr 13 08:07:54 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 260611ACD1C; Mon, 13 Apr 2015 08:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 okpoZbG8PwM1; Mon, 13 Apr 2015 08:07:50 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DADA1ACD03; Mon, 13 Apr 2015 08:07:43 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 738A888112; Mon, 13 Apr 2015 08:07:43 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 060331368274; Mon, 13 Apr 2015 08:07:42 -0700 (PDT)
Message-ID: <552BDBB8.8020709@innovationslab.net>
Date: Mon, 13 Apr 2015 11:07:36 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>,  draft-ietf-dhc-access-network-identifier@ietf.org
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xDDgr52JGbhF2bHnGnCE4CSrMtmugROBf"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/KXhPivaQiOLZdVdhnypsHLwIJVY>
Subject: [dhcwg] AD Evaluation: draft-ietf-dhc-access-network-identifier
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 15:07:53 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--xDDgr52JGbhF2bHnGnCE4CSrMtmugROBf
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

All,
     I have completed my AD Evaluation of
draft-ietf-dhc-access-network-identifier as a part of the publication
process.  This is a well-written document and I only have a few
comments/questions on it.  Once these are resolved, the document can
continue through the publication process...

* This document references RFC 6021, but 6021 has been obsoleted by 6991.=


* Section 4.3.1 says that the SSID MUST be provided if the access
technology is 802.11.  However, it is not as strict when the access
technology is 3GPP or 3GPP2.  Should those access technologies also use
MUST-level requirements on the value?  Would it be useful to identify
the acceptable values in this option for all access technologies listed
here?

http://www.iana.org/assignments/mobility-parameters/mobility-parameters.x=
html#mobility-parameters-10

* Section 4.4.1 (and 5.3.1) provide an option for conveying the
Operator's Vendor ID.  Where does this Vendor ID come from?  Is there a
stable reference for Vendor IDs in this context?

* Section 4.4.2 (and 5.3.2) provide the Realm, but there is no
discussion of what Realm means.  Adding some context would be useful.

* Given the Motivation and Security Considerations sections, is there
really a deployment model where these options should be inserted by the
DHCP client?  It seems to me that the client really isn't in a position
to know if/when this option should be included in its DHCP message.

Regards,
Brian


--xDDgr52JGbhF2bHnGnCE4CSrMtmugROBf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVK9u4AAoJEBOZRqCi7goqCp4H/1y8BmD5HwdFLw+n7Z1OieoO
os9oF6o5KsL6V30SxHejXqOmRQd+wl/EcZWF9UK1XXqfVYju3x8mu32y5FY5l8fr
2DEgSWcC2FFi4o3I4QHLI8aTLM+QBPDWWpaMUObYgifbyiYyFbu4kYVxFsMme51I
9IoGIrHpWku4QKXkEU6EDuiN9C71KGCAdylWVbSfvmwLKwLM2WfiVoG1+noYdfpX
jnNYz6Hafuss/tGx4McUTFJ/Vn5+r4iVaSHimb6bz9Vo4zi8Yv4wegdOi6kSCMKW
UuvYqqHAN7NQUqdXJOngx6P2L3Ac/MwIjWZZd8GucLzhAq6wZDyxfaehexfH3RY=
=3fdr
-----END PGP SIGNATURE-----

--xDDgr52JGbhF2bHnGnCE4CSrMtmugROBf--


From nobody Mon Apr 13 08:10:33 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 708051ACD05; Mon, 13 Apr 2015 08:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 CBqwF-usL4iU; Mon, 13 Apr 2015 08:10:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CCC21ACD01; Mon, 13 Apr 2015 08:10:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <dhc-chairs@ietf.org>, <draft-ietf-dhc-access-network-identifier.shepherd@ietf.org>,  <draft-ietf-dhc-access-network-identifier.ad@ietf.org>,  <dhcwg@ietf.org>, <draft-ietf-dhc-access-network-identifier@ietf.org>, <jiangsheng@huawei.com>, 
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150413151030.17875.59765.idtracker@ietfa.amsl.com>
Date: Mon, 13 Apr 2015 08:10:30 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/A-yJ4_tAAxlhfYu3HjCbJhOYG9A>
Subject: [dhcwg] ID Tracker State Update Notice: <draft-ietf-dhc-access-network-identifier-06.txt>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 15:10:31 -0000

IESG state changed to AD Evaluation::Revised I-D Needed from AD Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-dhc-access-network-identifier/


From nobody Mon Apr 13 09:05:14 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 437091A0163; Mon, 13 Apr 2015 09:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 QJiiuc5pYDeZ; Mon, 13 Apr 2015 09:05:06 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 027621A0141; Mon, 13 Apr 2015 09:05:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7079; q=dns/txt; s=iport; t=1428941106; x=1430150706; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DRdi11MzMMKz6kP6ENO9iDora0tfP4MUnho3jjyK7pY=; b=NHjpIT0CmDO4SAjJhryhwCCGZOYkI4904Zx1LfXZZu5VImR+6xCmbe9t clL24RkKf/z8TXKXsptKRL4M52MwTVsLpsV8cGT8uM4j+gS+qihaF4isC bBe46LZsb1VoZWbdt5MF4ReuMUzwbgrqqDQoIVTHaKvXpt3PnWB6Ziyjv I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BwBQBW6CtV/5hdJa1SCoMMUlzGXwELhX8CgTpMAQEBAQEBfoQgAQEEAQEBawsQAgEIPwcnCxQRAgQOBQmIIQ3NGQEBAQEBAQEBAQEBAQEBAQEBAQEBAReLK4QfOx4EB4MXgRYFjmERghqDeYYWAYgUjFciggMcgVBvAYJCAQEB
X-IronPort-AV: E=Sophos;i="5.11,570,1422921600";  d="scan'208,217";a="411447427"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-3.cisco.com with ESMTP; 13 Apr 2015 16:05:05 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t3DG55OD018570 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Apr 2015 16:05:05 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.142]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Mon, 13 Apr 2015 11:05:04 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Brian Haberman <brian@innovationslab.net>
Thread-Topic: [dhcwg] AD Evaluation: draft-ietf-dhc-access-network-identifier
Thread-Index: AQHQdfujtsSIjz1CCEijqY1Zlrzmxp1LGz2n
Date: Mon, 13 Apr 2015 16:05:04 +0000
Message-ID: <E343F59D-2ABA-4E95-813C-6F42BC65DB61@cisco.com>
References: <552BDBB8.8020709@innovationslab.net>
In-Reply-To: <552BDBB8.8020709@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_E343F59D2ABA4E95813C6F42BC65DB61ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/i_iIBj2IP35SW2HI_rRoH8h0mqc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-access-network-identifier@ietf.org" <draft-ietf-dhc-access-network-identifier@ietf.org>
Subject: Re: [dhcwg] AD Evaluation: draft-ietf-dhc-access-network-identifier
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 16:05:12 -0000

--_000_E343F59D2ABA4E95813C6F42BC65DB61ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Brian:

Thanks for review.

Regarding section 4.4.1 & 5.3.2, the Vendor ID is defined in terminology se=
ction 3:


Vendor ID - The Vendor ID is the SMI Network Management Private Enterprise
      Code of the IANA-maintained Private Enterprise Numbers registry
      [SMI<https://tools.ietf.org/html/draft-ietf-dhc-access-network-identi=
fier-06#ref-SMI>].

Not sure if that is suffient or whether work at least adding reference back=
 to Section 3 or just remove from there and place info in the two sections.

I will let the others comment on the other issues, though I agree that havi=
ng client provide this information is pretty useless.

- Bernie (from iPad)

On Apr 13, 2015, at 11:08 AM, Brian Haberman <brian@innovationslab.net<mail=
to:brian@innovationslab.net>> wrote:

All,
    I have completed my AD Evaluation of
draft-ietf-dhc-access-network-identifier as a part of the publication
process.  This is a well-written document and I only have a few
comments/questions on it.  Once these are resolved, the document can
continue through the publication process...

* This document references RFC 6021, but 6021 has been obsoleted by 6991.

* Section 4.3.1 says that the SSID MUST be provided if the access
technology is 802.11.  However, it is not as strict when the access
technology is 3GPP or 3GPP2.  Should those access technologies also use
MUST-level requirements on the value?  Would it be useful to identify
the acceptable values in this option for all access technologies listed
here?

http://www.iana.org/assignments/mobility-parameters/mobility-parameters.xht=
ml#mobility-parameters-10

* Section 4.4.1 (and 5.3.1) provide an option for conveying the
Operator's Vendor ID.  Where does this Vendor ID come from?  Is there a
stable reference for Vendor IDs in this context?

* Section 4.4.2 (and 5.3.2) provide the Realm, but there is no
discussion of what Realm means.  Adding some context would be useful.

* Given the Motivation and Security Considerations sections, is there
really a deployment model where these options should be inserted by the
DHCP client?  It seems to me that the client really isn't in a position
to know if/when this option should be included in its DHCP message.

Regards,
Brian

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg

--_000_E343F59D2ABA4E95813C6F42BC65DB61ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Hi Brian:</div>
<div><br>
</div>
<div>Thanks for review.</div>
<div><br>
</div>
<div>Regarding section 4.4.1 &amp; 5.3.2, the Vendor ID is defined in termi=
nology section 3:</div>
<div><br>
</div>
<div>
<pre class=3D"newpage" style=3D"margin-top: 0px; margin-bottom: 0px; page-b=
reak-before: always;"><blockquote type=3D"cite"><font color=3D"#000000" fac=
e=3D"UICTFontTextStyleBody"><span style=3D"white-space: normal; background-=
color: rgba(255, 255, 255, 0);">Vendor ID - The Vendor ID is the SMI Networ=
k Management Private Enterprise
      Code of the IANA-maintained Private Enterprise Numbers registry
      [<a href=3D"https://tools.ietf.org/html/draft-ietf-dhc-access-network=
-identifier-06#ref-SMI" title=3D"&quot;PRIVATE ENTERPRISE NUMBERS, SMI Netw=
ork Management Private Enterprise Codes&quot;">SMI</a>].</span></font></blo=
ckquote></pre>
<div><br>
</div>
<div>Not sure if that is suffient or whether work at least adding reference=
 back to Section 3 or just remove from there and place info in the two sect=
ions.</div>
<div><br>
</div>
<div>I will let the others comment on the other issues, though I agree that=
 having client provide this information is pretty useless.&nbsp;</div>
<div><br>
</div>
- Bernie (from iPad)</div>
<div><br>
On Apr 13, 2015, at 11:08 AM, Brian Haberman &lt;<a href=3D"mailto:brian@in=
novationslab.net">brian@innovationslab.net</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div><span>All,</span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;I have completed my AD Evaluation of</span><b=
r>
<span>draft-ietf-dhc-access-network-identifier as a part of the publication=
</span><br>
<span>process. &nbsp;This is a well-written document and I only have a few<=
/span><br>
<span>comments/questions on it. &nbsp;Once these are resolved, the document=
 can</span><br>
<span>continue through the publication process...</span><br>
<span></span><br>
<span>* This document references RFC 6021, but 6021 has been obsoleted by 6=
991.</span><br>
<span></span><br>
<span>* Section 4.3.1 says that the SSID MUST be provided if the access</sp=
an><br>
<span>technology is 802.11. &nbsp;However, it is not as strict when the acc=
ess</span><br>
<span>technology is 3GPP or 3GPP2. &nbsp;Should those access technologies a=
lso use</span><br>
<span>MUST-level requirements on the value? &nbsp;Would it be useful to ide=
ntify</span><br>
<span>the acceptable values in this option for all access technologies list=
ed</span><br>
<span>here?</span><br>
<span></span><br>
<span><a href=3D"http://www.iana.org/assignments/mobility-parameters/mobili=
ty-parameters.xhtml#mobility-parameters-10">http://www.iana.org/assignments=
/mobility-parameters/mobility-parameters.xhtml#mobility-parameters-10</a></=
span><br>
<span></span><br>
<span>* Section 4.4.1 (and 5.3.1) provide an option for conveying the</span=
><br>
<span>Operator's Vendor ID. &nbsp;Where does this Vendor ID come from? &nbs=
p;Is there a</span><br>
<span>stable reference for Vendor IDs in this context?</span><br>
<span></span><br>
<span>* Section 4.4.2 (and 5.3.2) provide the Realm, but there is no</span>=
<br>
<span>discussion of what Realm means. &nbsp;Adding some context would be us=
eful.</span><br>
<span></span><br>
<span>* Given the Motivation and Security Considerations sections, is there=
</span><br>
<span>really a deployment model where these options should be inserted by t=
he</span><br>
<span>DHCP client? &nbsp;It seems to me that the client really isn't in a p=
osition</span><br>
<span>to know if/when this option should be included in its DHCP message.</=
span><br>
<span></span><br>
<span>Regards,</span><br>
<span>Brian</span><br>
<span></span><br>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>dhcwg mailing list</span><br>
<span><a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg">https://www.i=
etf.org/mailman/listinfo/dhcwg</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_E343F59D2ABA4E95813C6F42BC65DB61ciscocom_--


From nobody Mon Apr 13 11:17:01 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BFDB1B2A2A for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 11:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.921
X-Spam-Level: 
X-Spam-Status: No, score=0.921 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 GjMzmmfx35-y for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 11:16:57 -0700 (PDT)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E1E31B2A29 for <dhcwg@ietf.org>; Mon, 13 Apr 2015 11:16:57 -0700 (PDT)
Received: by iebrs15 with SMTP id rs15so72038984ieb.3 for <dhcwg@ietf.org>; Mon, 13 Apr 2015 11:16:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=pTtWqi14WMICYcJVtwBc7DnJYQ+dOWsvvhYi9mY7iZs=; b=ckMH+ROVAhnRc+bJ4rRX4TqiehJWgcLOeCCZrXgpMm0fY6II6yWP/rPBEED45MvU9u Q5aM2JdKe4uzfHYaE22/n9tLWl5uqcauIr6ZkaZVhbl/u0Wlhho2bYwUflKC8lTAuw21 EWHGNiZPH/RPdFvw4Zrm2e8Wo6aw4pphcSsaqm5DzID5JJHw5nUxJ7D8Pq2ZlAOz3mxe QCiXYKRyzXDiS8Ra6Axaa4sx/xpQgq0rJJ7stnOO5go1e2EmedXXkv8Wp6pTvizFXS7N 9pD0n1HKYGWHLmHnrDbMdQ16X8bTN961gZ70otwkC2ez580efg9KkIPhsOHVOpLLoj3W 0xwg==
MIME-Version: 1.0
X-Received: by 10.50.143.106 with SMTP id sd10mr18336625igb.17.1428949016972;  Mon, 13 Apr 2015 11:16:56 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.21.3 with HTTP; Mon, 13 Apr 2015 11:16:56 -0700 (PDT)
In-Reply-To: <5526D45A.9020701@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1CA321EE@xmb-rcd-x04.cisco.com> <6D7A465E-6EBE-4B69-9B65-BAC7BF2A9873@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1CA3229F@xmb-rcd-x04.cisco.com> <55214802.1070305@si6networks.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com>
Date: Mon, 13 Apr 2015 11:16:56 -0700
X-Google-Sender-Auth: GoVcdHO30zvTvWnHXmP2zFu9JjE
Message-ID: <CAJE_bqcd60Qw+ZJPC35q_MndFpOxabc7ewXhKLDWiUt5Lzo7Rw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/l0AiDwNVDqnNZOKtxnHupAfaeGc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 18:17:00 -0000

At Thu, 09 Apr 2015 16:34:50 -0300,
Fernando Gont <fgont@si6networks.com> wrote:

> >> So the clear benefit is that you can have multiple DHCPv6 servers
> >> operating on the same network, and you get address stability
> >> without an additional protocol.
> >
> > This concept is flawed if the servers aren't cooperating. If there
> > are multiple servers that don't share lease data, how does server 1
> > know whether the lease was leased to another client or renewed, if
> > server 2 ends up communicating with the client?
>
> Usually, you need servers to communicate because there's no way to tell
> which address each server may have assigned to which client. But that's
> not the case with this method.

I tend to agree with Bernie here.  Those servers would most likely
have to maintain/share other kinds of states than address itself
anyway: T1/T2, address lifetimes, previously advertised FQDN, etc.
This algorithm might make address information optional from that has
to be explicitly shared, but even so it won't make the failover
implementation any simpler in practice.

As I stated in my own response to this inquiry, I see some niche
benefit in the proposed approach, so I wouldn't necessarily be opposed
to publishing it.  But, to me, the benefit seems to be quite minor.

--
JINMEI, Tatuya


From nobody Mon Apr 13 15:07:10 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B751F1AC3AB for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 15:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 qf4S6Q5f0hIj for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 15:07:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 024C81AC3BC for <dhcwg@ietf.org>; Mon, 13 Apr 2015 15:07:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <dhcwg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150413220705.23466.93749.idtracker@ietfa.amsl.com>
Date: Mon, 13 Apr 2015 15:07:05 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ZnTHc3g9EadCWEOhxc0jKuuheD4>
Subject: [dhcwg] Milestones changed for dhc WG
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 22:07:08 -0000

Deleted milestone "Submit draft-ietf-dhc-addr-registration to IESG".

Changed milestone "Submit access-network-identifier to IESG", set due
date to April 2015 from February 2015, resolved as "Done".

URL: http://datatracker.ietf.org/wg/dhc/charter/


From nobody Mon Apr 13 15:08:54 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 259871A90F2 for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 15:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 xXK9P9NyYIoB for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 15:08:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C021ACAD5 for <dhcwg@ietf.org>; Mon, 13 Apr 2015 15:08:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <dhcwg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150413220849.20306.16757.idtracker@ietfa.amsl.com>
Date: Mon, 13 Apr 2015 15:08:49 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/NFO0EbpXwY7pNRxWmTtblfBS-Tc>
Subject: [dhcwg] Milestones changed for dhc WG
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 22:08:53 -0000

Changed milestone "WG last calll on draft-ietf-dhc-addr-registration",
resolved as "Failed Last Call".

URL: http://datatracker.ietf.org/wg/dhc/charter/


From nobody Mon Apr 13 22:50:28 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 242A61B33DD for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 22:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.39
X-Spam-Level: **
X-Spam-Status: No, score=2.39 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_03_06=1.592, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 am56jJD5VUxd for <dhcwg@ietfa.amsl.com>; Mon, 13 Apr 2015 22:50:25 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 DCAF11B33DB for <dhcwg@ietf.org>; Mon, 13 Apr 2015 22:50:24 -0700 (PDT)
Received: from [186.134.14.206] (helo=[192.168.123.128]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Yhtjp-0002c8-2e; Tue, 14 Apr 2015 07:50:21 +0200
Message-ID: <552C679E.4020305@si6networks.com>
Date: Mon, 13 Apr 2015 22:04:30 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com> <5527FA77.5070301@si6networks.com> <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com>
In-Reply-To: <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/iVIdsy9wrOAXWhWPuw2smBDEqIY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 05:50:27 -0000

Hi, Lorenzo,

On 04/11/2015 01:38 AM, Lorenzo Colitti wrote:
> On Sat, Apr 11, 2015 at 1:29 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     On 04/09/2015 08:20 PM, Lorenzo Colitti wrote:
>     >     > This concept is flawed if the servers aren't cooperating. If
>     there
>     >     > are multiple servers that don't share lease data, how does
>     server 1
>     >     > know whether the lease was leased to another client or
>     renewed, if
>     >     > server 2 ends up communicating with the client?
>     >
>     >     Usually, you need servers to communicate because there's no
>     way to tell
>     >     which address each server may have assigned to which client.
>     But that's
>     >     not the case with this method.
>     >
>     >
>     > It is still the case even with this method, because the servers
>     need to
>     > agree on the value of the counter variable.
> 
>     The Counter value is there for completeness sake. Me, I don't expecThe
>     assumption is that thanks to the huge address space, you want hit
>     collisions.
> 
> But you have to say what happens in this case. If the client sends a
> DECLINE for any reason, what happens? Is it dead in the water with the
> wrong IP address? Does the server just respond with the same IP address
> as before, hoping that the client will like it? If you don't want the
> draft to specify the behaviour, you should at least provide a list of
> the possible options, because from what I see, the possible options are
> all bad.

In my mental model, if the client sends a DECLINE, that's interpreted as
a collision, hence Counter is incremented, and you get a different IPv6
address.

I guess this should be configurable:
1) "Hard assignment": IPv6 addresses collisions are flagged as
"impossible", and server always offer the same address (i.e., Counter is
not used at all)

2) Soft assignment: server assigns an address but offers an alternative
one in the case of collisions.


Not sure why you say all options are bad. If you were doing
randomized/statefull DCHPv6 address assignments, you'd have to handle
DECLINEs, too.



>     I'd say that a DHCPv6 servers is free to store the Counter value for
>     each lease, if they please. But it's not worth it to synchronize it. --
>     the assumption in this scheme is that the address space for the local
>     subnet is so large that you will not find collisions.
> 
>     If you, we could rename the I-D as "probabilistically stable" -- but I
>     hope that's not needed.
> 
> 
> One of the major objections I have here is that the draft says that the
> addresses are stable and stateless. However, that statement is not true
> in the presence of DECLINEs, collisions, or misconfigurations (probably
> more likely than collisions). If the draft didn't say the addresses are
> stable, or if it didn't say that the addresses can be calculated
> statelessly, then that would be OK, but it does. I think that if you
> want to standardize this approach, then IMO you need to quantify what
> happens in these cases.

Ok. I will craft text along these lines. Among other things, discuss
DECLINES, note that collissions are expected to be virtually impossible
thanks to the address space, etc.


> Also, I think statelessness is pointless. DHCPv6 is a fundamentally
> stateful protocol. It's not just the lease database - clients and
> servers also keep track of IAs, server IDs, client IDs, DUIDs. Even if
> you make the address calculation stateless, to show value you'll need to
> show whether this scheme works when you swap out servers. If it this
> scheme doesn't work when you swap servers, then there's really no point
> in making the address calculation stateless, since you need to share
> state anyway.

Swap == replace the server with a "cloned" one (same IPv6 address, and
Server DUID)?

or...?



> More in general. Whether you continue work on this document is to you,
> but I'll point out that Bernie has stated multiple times that he wants
> to see people support this draft, not just "not object to it". I don't
> see much in the way of support today. As far as I'm concerned, you may
> be able to address the issues that I list above and remove some of the
> objections, but I doubt you'll be able to convince me personally that
> this scheme has value and turn me into supporter.

Part of that seems to have to do with how things work if you swap the
server. I can give that a try (if you stay open to change yur mind if
that makes sense).

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Apr 14 05:00:29 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92ECE1A8AE4; Tue, 14 Apr 2015 05:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 iR7YL5DY-LXn; Tue, 14 Apr 2015 05:00:26 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A73A51A8AEB; Tue, 14 Apr 2015 05:00:24 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 671F4880CE; Tue, 14 Apr 2015 05:00:24 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id EE1701368274; Tue, 14 Apr 2015 05:00:23 -0700 (PDT)
Message-ID: <552D0153.8070709@innovationslab.net>
Date: Tue, 14 Apr 2015 08:00:19 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
References: <552BDBB8.8020709@innovationslab.net> <E343F59D-2ABA-4E95-813C-6F42BC65DB61@cisco.com>
In-Reply-To: <E343F59D-2ABA-4E95-813C-6F42BC65DB61@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PGDehtk8DujoADBSxc6GDuqNE3Bx8Ul8q"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/tpMbICjHcQBedAXe4esKq6maXX4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-access-network-identifier@ietf.org" <draft-ietf-dhc-access-network-identifier@ietf.org>
Subject: Re: [dhcwg] AD Evaluation: draft-ietf-dhc-access-network-identifier
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 12:00:27 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PGDehtk8DujoADBSxc6GDuqNE3Bx8Ul8q
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Bernie,

On 4/13/15 12:05 PM, Bernie Volz (volz) wrote:
> Hi Brian:
>=20
> Thanks for review.
>=20
> Regarding section 4.4.1 & 5.3.2, the Vendor ID is defined in
> terminology section 3:
>=20
>=20
> Vendor ID - The Vendor ID is the SMI Network Management Private
> Enterprise Code of the IANA-maintained Private Enterprise Numbers
> registry=20
> [SMI<https://tools.ietf.org/html/draft-ietf-dhc-access-network-identifi=
er-06#ref-SMI>].
>
>  Not sure if that is suffient or whether work at least adding
> reference back to Section 3 or just remove from there and place info
> in the two sections.

Not sure how I missed that in Section 3.  Maybe a simple reference like
"(as described in Section 3)" will help readers.

Regards,
Brian

>=20
> I will let the others comment on the other issues, though I agree
> that having client provide this information is pretty useless.
>=20
> - Bernie (from iPad)
>=20
> On Apr 13, 2015, at 11:08 AM, Brian Haberman
> <brian@innovationslab.net<mailto:brian@innovationslab.net>> wrote:
>=20
> All, I have completed my AD Evaluation of=20
> draft-ietf-dhc-access-network-identifier as a part of the
> publication process.  This is a well-written document and I only have
> a few comments/questions on it.  Once these are resolved, the
> document can continue through the publication process...
>=20
> * This document references RFC 6021, but 6021 has been obsoleted by
> 6991.
>=20
> * Section 4.3.1 says that the SSID MUST be provided if the access=20
> technology is 802.11.  However, it is not as strict when the access=20
> technology is 3GPP or 3GPP2.  Should those access technologies also
> use MUST-level requirements on the value?  Would it be useful to
> identify the acceptable values in this option for all access
> technologies listed here?
>=20
> http://www.iana.org/assignments/mobility-parameters/mobility-parameters=
=2Exhtml#mobility-parameters-10
>
>  * Section 4.4.1 (and 5.3.1) provide an option for conveying the=20
> Operator's Vendor ID.  Where does this Vendor ID come from?  Is there
> a stable reference for Vendor IDs in this context?
>=20
> * Section 4.4.2 (and 5.3.2) provide the Realm, but there is no=20
> discussion of what Realm means.  Adding some context would be
> useful.
>=20
> * Given the Motivation and Security Considerations sections, is
> there really a deployment model where these options should be
> inserted by the DHCP client?  It seems to me that the client really
> isn't in a position to know if/when this option should be included in
> its DHCP message.
>=20
> Regards, Brian
>=20
> _______________________________________________ dhcwg mailing list=20
> dhcwg@ietf.org<mailto:dhcwg@ietf.org>=20
> https://www.ietf.org/mailman/listinfo/dhcwg
>=20


--PGDehtk8DujoADBSxc6GDuqNE3Bx8Ul8q
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVLQFYAAoJEBOZRqCi7goqt24IAIV5hIc9+Ss8sugy3I6ztJfP
IppSnSGnkA6xzy+UZwnzcdMoTOgMynnbYPt8lyQeC+cinLgSbr+C0C2IV9OIvvl1
yXyT8+WcgPI6G+zdX9/XcNYgm/3lOItgMbwgue3/bRjfiHZ2ChXxO4lXEbXqSrMO
rt10xVoE4lAQ4pU+iducbvIFCa6OY1B0YWlFaTRj9mLn2BQjouYAV02XiNQIbrdQ
ctQjpK5PpfhzZy32adRSH4Ly66Q1MVKcqp7F0iRW3wSt4vKs7zQEtp0qjkEtbCpa
Kc1LdRxBcUIpSpOFfmmspUJSMZD53on4wuMHw4Qn00U95+PhrQwXDIenyQ4J3IE=
=mT48
-----END PGP SIGNATURE-----

--PGDehtk8DujoADBSxc6GDuqNE3Bx8Ul8q--


From nobody Tue Apr 14 09:59:26 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4AAF1B2F36 for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 09:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 vb0JeWpt43oB for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 09:59:16 -0700 (PDT)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 738381B2EF4 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 09:59:16 -0700 (PDT)
Received: by iebrs15 with SMTP id rs15so20134833ieb.3 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 09:59:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=xJH8s4eggA7nBXsBRIFhNwgJv6wDYdJUvRulpRMQ0vk=; b=W6mSF402hJOtYTFvVHJyVQtnCGQeloj3Je8IwSjxn+WfhbOsMSbAJ0qU/7lIx7GGxL X4qSNuBHzGshHogPy7dW324EL8wgVnML6AcJ3/r5gen8lVkmyz9wvqdf/Mlm0bcQFlxB qJvjHPsI91BZWD+VtR/xxSGHSeU8IYvIbwYeqa3M1Qd3zHGHZRZ8HpatvCCjVi6zpSUK IOjK6jJ9tGF1XVyxd2c15luAvfvKmD0x+F1aHT4sWEr3cyQ4jkAStZN+2amI0qMCmvZl RFQouLQAMgpFd/d/aSQCd9kIx1oBX0rxk3c8/x6XUbqwxxM7NTrbEYgPEcxJaUNpc4TI 2zNg==
MIME-Version: 1.0
X-Received: by 10.107.128.3 with SMTP id b3mr30294412iod.24.1429030755930; Tue, 14 Apr 2015 09:59:15 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.21.3 with HTTP; Tue, 14 Apr 2015 09:59:15 -0700 (PDT)
In-Reply-To: <552433E9.2010106@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA38753@xmb-rcd-x04.cisco.com> <552433E9.2010106@gmail.com>
Date: Tue, 14 Apr 2015 09:59:15 -0700
X-Google-Sender-Auth: ersxRKDhwY1pHh27qO6Ma4LUowQ
Message-ID: <CAJE_bqeEobXmyfC=Xo0HJwM0+foquhR9apMGo4931VggeEc6mQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/uxcE0yO6plKoHQP_G5fg4Kiskbc>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Summary of the 3315bis discussions in Dallas
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 16:59:17 -0000

At Tue, 07 Apr 2015 21:45:45 +0200,
Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:

> #86 =E2=80=93 Information-request in Delayed Authentication Protocol (DAP=
)
> (Slide 13)
> =E2=80=93 Ted suggested we remove DAP from DHCPv6bis as it is not
> known to have been deployed by anyone. As far as we can tell, there's
> only one implementation. (Tomek comment added during writing those
> minutes: I did implement it in Dibbler. The mechanism, including option
> formats, was underspecified and I had to make judgement decisions that
> would likely prevent interop. I'm not aware of any other implementations
> or deployments that use DAP in Dibbler).

WIDE DHCPv6 supports DAP (even before the birth of Dibbler, I
suspect:-):
http://sourceforge.net/projects/wide-dhcpv6/

If my memory is correct, there was even interoperability testing (for
DHCPv6 in general, but also covering DAP) many years ago, so there
should have been at least one other implementation of DAP than the
WIDE implementation.

I'm noting this just to make the implementation status more accurate.
I have no objection to the proposal of removing DAP from 3315bis (in
fact, I guess I once even suggested that myself before).

--
JINMEI, Tatuya


From nobody Tue Apr 14 10:49:30 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26FBA1A1A78 for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 10:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 lvP9eyjIfook for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 10:49:26 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 337BF1A1A98 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 10:49:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7736; q=dns/txt; s=iport; t=1429033765; x=1430243365; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=e5r3UFkacn5OhTjiOej/Gbcas/B9wl+za81/LXKskW0=; b=B4ELKTskJQXZ/iDklcJEYRcYufTlEW3BCzNH/ycLKvBjOxEvD6ix/Qth tc223KlD4t/ot8bg/3coOT2tXqM86kXqEf2t48UhfvJC1nwU1iLTsc3Mw 1IDgVC69nyhvMPj6Lta49xV3rOyehHAsWy60CsOLojf3RHOTLIxU5Oj9/ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BcBADpUS1V/4sNJK1cgwyBLgWDEMJWCYdPAhyBKzgUAQEBAQEBAX2EHwEBAQMBIwQNRQUHBAIBCA4DBAEBAQICBhkEAwICAjAUAQgIAgQBDQUIiBoItlSVdgEBAQEBAQEBAQEBAQEBAQEBAQEBAReBIYoKhDEaFhALBwaCYi+BFgEEkQ6LLoM3hweJESKCAxwUgTxvgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.11,577,1422921600"; d="scan'208";a="141192303"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-6.cisco.com with ESMTP; 14 Apr 2015 17:49:24 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t3EHnNLS003814 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Apr 2015 17:49:23 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.142]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Tue, 14 Apr 2015 12:49:23 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Fernando Gont <fgont@si6networks.com>, Lorenzo Colitti <lorenzo@google.com>
Thread-Topic: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
Thread-Index: AQHQbKUWByZTAVuV8ESYM5tVpMLK4p04ge2AgABZ+YD//7DXMIAKWypfgABgb4CAAAcrgIAAANmAgAAE+ACAAAV/AIABrwHhgAABkwCAAZ0fPYAFbAoBgADGg3A=
Date: Tue, 14 Apr 2015 17:49:22 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA66028@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <CAKD1Yr3UYT0yPEqftEXpN8zmk=-dka_NMcu3rbb_GG+YSnk2ZQ@mail.gmail.com> <5524D09B.3090706@si6networks.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com> <5527FA77.5070301@si6networks.com> <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com> <552C679E.4020305@si6networks.com>
In-Reply-To: <552C679E.4020305@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.76]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/nN3MYSnhVxsSYmdk8nFDJeSx8UA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 17:49:28 -0000

Pk9rLiBJIHdpbGwgY3JhZnQgdGV4dCBhbG9uZyB0aGVzZSBsaW5lcy4gQW1vbmcgb3RoZXIgdGhp
bmdzLCBkaXNjdXNzIERFQ0xJTkVTLCBub3RlIHRoYXQgY29sbGlzaW9ucyBhcmUgZXhwZWN0ZWQg
dG8gYmUgdmlydHVhbGx5IGltcG9zc2libGUgdGhhbmtzIHRvIHRoZSBhZGRyZXNzIHNwYWNlLCBl
dGMuDQoNClRoaXMgaXMgTk9UIHRydWUgYXQgYWxsIChjb2xsaXNpb25zIHZpcnR1YWxseSBpbXBv
c3NpYmxlKS4gSW4gZmFjdCwgdGhlIGV4YWN0IG9wcG9zaXRlIHdpbGwgYWxtb3N0IGNlcnRhaW5s
eSBiZSB0cnVlLg0KDQpBbHNvIHRoaW5rIG9mIGNhc2VzIHdoZXJlIG11Y2ggc21hbGxlciBzcGFj
ZXMgdGhhbiBhIC82NCBhcmUgYmVpbmcgdXNlZCAoc3VjaCBhcyB3aGVuIGEgc2VydmVyIGlzIGNv
bmZpZ3VyZWQgZm9yIGEgc3RhcnQgdG8gZW5kIHJhbmdlICgxIHRvIDEwMDAwMCkpIG9yIHdoZW4g
YSBsb25nZXIgcHJlZml4IGxlbmd0aCBpcyBiZWluZyB1c2VkICgvOTYpIGZvciBhc3NpZ25pbmcg
YWRkcmVzc2VzLg0KDQotIEJlcm5pZQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogRmVybmFuZG8gR29udCBbbWFpbHRvOmZnb250QHNpNm5ldHdvcmtzLmNvbV0gDQpTZW50OiBN
b25kYXksIEFwcmlsIDEzLCAyMDE1IDk6MDUgUE0NClRvOiBMb3JlbnpvIENvbGl0dGkNCkNjOiBC
ZXJuaWUgVm9seiAodm9seik7IGRoY3dnQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW2RoY3dnXSBO
ZXh0IHN0ZXAocykgZm9yIGRyYWZ0LWlldGYtZGhjLXN0YWJsZS1wcml2YWN5LWFkZHJlc3NlcyAt
PiBhYmFuZG9uIHdvcms/IC8gSUFfTkEgYXBwbGljYWJpbGl0eQ0KDQpIaSwgTG9yZW56bywNCg0K
T24gMDQvMTEvMjAxNSAwMTozOCBBTSwgTG9yZW56byBDb2xpdHRpIHdyb3RlOg0KPiBPbiBTYXQs
IEFwciAxMSwgMjAxNSBhdCAxOjI5IEFNLCBGZXJuYW5kbyBHb250IDxmZ29udEBzaTZuZXR3b3Jr
cy5jb20gDQo+IDxtYWlsdG86ZmdvbnRAc2k2bmV0d29ya3MuY29tPj4gd3JvdGU6DQo+IA0KPiAg
ICAgT24gMDQvMDkvMjAxNSAwODoyMCBQTSwgTG9yZW56byBDb2xpdHRpIHdyb3RlOg0KPiAgICAg
PiAgICAgPiBUaGlzIGNvbmNlcHQgaXMgZmxhd2VkIGlmIHRoZSBzZXJ2ZXJzIGFyZW4ndCBjb29w
ZXJhdGluZy4gSWYNCj4gICAgIHRoZXJlDQo+ICAgICA+ICAgICA+IGFyZSBtdWx0aXBsZSBzZXJ2
ZXJzIHRoYXQgZG9uJ3Qgc2hhcmUgbGVhc2UgZGF0YSwgaG93IGRvZXMNCj4gICAgIHNlcnZlciAx
DQo+ICAgICA+ICAgICA+IGtub3cgd2hldGhlciB0aGUgbGVhc2Ugd2FzIGxlYXNlZCB0byBhbm90
aGVyIGNsaWVudCBvcg0KPiAgICAgcmVuZXdlZCwgaWYNCj4gICAgID4gICAgID4gc2VydmVyIDIg
ZW5kcyB1cCBjb21tdW5pY2F0aW5nIHdpdGggdGhlIGNsaWVudD8NCj4gICAgID4NCj4gICAgID4g
ICAgIFVzdWFsbHksIHlvdSBuZWVkIHNlcnZlcnMgdG8gY29tbXVuaWNhdGUgYmVjYXVzZSB0aGVy
ZSdzIG5vDQo+ICAgICB3YXkgdG8gdGVsbA0KPiAgICAgPiAgICAgd2hpY2ggYWRkcmVzcyBlYWNo
IHNlcnZlciBtYXkgaGF2ZSBhc3NpZ25lZCB0byB3aGljaCBjbGllbnQuDQo+ICAgICBCdXQgdGhh
dCdzDQo+ICAgICA+ICAgICBub3QgdGhlIGNhc2Ugd2l0aCB0aGlzIG1ldGhvZC4NCj4gICAgID4N
Cj4gICAgID4NCj4gICAgID4gSXQgaXMgc3RpbGwgdGhlIGNhc2UgZXZlbiB3aXRoIHRoaXMgbWV0
aG9kLCBiZWNhdXNlIHRoZSBzZXJ2ZXJzDQo+ICAgICBuZWVkIHRvDQo+ICAgICA+IGFncmVlIG9u
IHRoZSB2YWx1ZSBvZiB0aGUgY291bnRlciB2YXJpYWJsZS4NCj4gDQo+ICAgICBUaGUgQ291bnRl
ciB2YWx1ZSBpcyB0aGVyZSBmb3IgY29tcGxldGVuZXNzIHNha2UuIE1lLCBJIGRvbid0IGV4cGVj
VGhlDQo+ICAgICBhc3N1bXB0aW9uIGlzIHRoYXQgdGhhbmtzIHRvIHRoZSBodWdlIGFkZHJlc3Mg
c3BhY2UsIHlvdSB3YW50IGhpdA0KPiAgICAgY29sbGlzaW9ucy4NCj4gDQo+IEJ1dCB5b3UgaGF2
ZSB0byBzYXkgd2hhdCBoYXBwZW5zIGluIHRoaXMgY2FzZS4gSWYgdGhlIGNsaWVudCBzZW5kcyBh
IA0KPiBERUNMSU5FIGZvciBhbnkgcmVhc29uLCB3aGF0IGhhcHBlbnM/IElzIGl0IGRlYWQgaW4g
dGhlIHdhdGVyIHdpdGggdGhlIA0KPiB3cm9uZyBJUCBhZGRyZXNzPyBEb2VzIHRoZSBzZXJ2ZXIg
anVzdCByZXNwb25kIHdpdGggdGhlIHNhbWUgSVAgDQo+IGFkZHJlc3MgYXMgYmVmb3JlLCBob3Bp
bmcgdGhhdCB0aGUgY2xpZW50IHdpbGwgbGlrZSBpdD8gSWYgeW91IGRvbid0IA0KPiB3YW50IHRo
ZSBkcmFmdCB0byBzcGVjaWZ5IHRoZSBiZWhhdmlvdXIsIHlvdSBzaG91bGQgYXQgbGVhc3QgcHJv
dmlkZSBhIA0KPiBsaXN0IG9mIHRoZSBwb3NzaWJsZSBvcHRpb25zLCBiZWNhdXNlIGZyb20gd2hh
dCBJIHNlZSwgdGhlIHBvc3NpYmxlIA0KPiBvcHRpb25zIGFyZSBhbGwgYmFkLg0KDQpJbiBteSBt
ZW50YWwgbW9kZWwsIGlmIHRoZSBjbGllbnQgc2VuZHMgYSBERUNMSU5FLCB0aGF0J3MgaW50ZXJw
cmV0ZWQgYXMgYSBjb2xsaXNpb24sIGhlbmNlIENvdW50ZXIgaXMgaW5jcmVtZW50ZWQsIGFuZCB5
b3UgZ2V0IGEgZGlmZmVyZW50IElQdjYgYWRkcmVzcy4NCg0KSSBndWVzcyB0aGlzIHNob3VsZCBi
ZSBjb25maWd1cmFibGU6DQoxKSAiSGFyZCBhc3NpZ25tZW50IjogSVB2NiBhZGRyZXNzZXMgY29s
bGlzaW9ucyBhcmUgZmxhZ2dlZCBhcyAiaW1wb3NzaWJsZSIsIGFuZCBzZXJ2ZXIgYWx3YXlzIG9m
ZmVyIHRoZSBzYW1lIGFkZHJlc3MgKGkuZS4sIENvdW50ZXIgaXMgbm90IHVzZWQgYXQgYWxsKQ0K
DQoyKSBTb2Z0IGFzc2lnbm1lbnQ6IHNlcnZlciBhc3NpZ25zIGFuIGFkZHJlc3MgYnV0IG9mZmVy
cyBhbiBhbHRlcm5hdGl2ZSBvbmUgaW4gdGhlIGNhc2Ugb2YgY29sbGlzaW9ucy4NCg0KDQpOb3Qg
c3VyZSB3aHkgeW91IHNheSBhbGwgb3B0aW9ucyBhcmUgYmFkLiBJZiB5b3Ugd2VyZSBkb2luZyBy
YW5kb21pemVkL3N0YXRlZnVsbCBEQ0hQdjYgYWRkcmVzcyBhc3NpZ25tZW50cywgeW91J2QgaGF2
ZSB0byBoYW5kbGUgREVDTElORXMsIHRvby4NCg0KDQoNCj4gICAgIEknZCBzYXkgdGhhdCBhIERI
Q1B2NiBzZXJ2ZXJzIGlzIGZyZWUgdG8gc3RvcmUgdGhlIENvdW50ZXIgdmFsdWUgZm9yDQo+ICAg
ICBlYWNoIGxlYXNlLCBpZiB0aGV5IHBsZWFzZS4gQnV0IGl0J3Mgbm90IHdvcnRoIGl0IHRvIHN5
bmNocm9uaXplIGl0LiAtLQ0KPiAgICAgdGhlIGFzc3VtcHRpb24gaW4gdGhpcyBzY2hlbWUgaXMg
dGhhdCB0aGUgYWRkcmVzcyBzcGFjZSBmb3IgdGhlIGxvY2FsDQo+ICAgICBzdWJuZXQgaXMgc28g
bGFyZ2UgdGhhdCB5b3Ugd2lsbCBub3QgZmluZCBjb2xsaXNpb25zLg0KPiANCj4gICAgIElmIHlv
dSwgd2UgY291bGQgcmVuYW1lIHRoZSBJLUQgYXMgInByb2JhYmlsaXN0aWNhbGx5IHN0YWJsZSIg
LS0gYnV0IEkNCj4gICAgIGhvcGUgdGhhdCdzIG5vdCBuZWVkZWQuDQo+IA0KPiANCj4gT25lIG9m
IHRoZSBtYWpvciBvYmplY3Rpb25zIEkgaGF2ZSBoZXJlIGlzIHRoYXQgdGhlIGRyYWZ0IHNheXMg
dGhhdCANCj4gdGhlIGFkZHJlc3NlcyBhcmUgc3RhYmxlIGFuZCBzdGF0ZWxlc3MuIEhvd2V2ZXIs
IHRoYXQgc3RhdGVtZW50IGlzIG5vdCANCj4gdHJ1ZSBpbiB0aGUgcHJlc2VuY2Ugb2YgREVDTElO
RXMsIGNvbGxpc2lvbnMsIG9yIG1pc2NvbmZpZ3VyYXRpb25zIA0KPiAocHJvYmFibHkgbW9yZSBs
aWtlbHkgdGhhbiBjb2xsaXNpb25zKS4gSWYgdGhlIGRyYWZ0IGRpZG4ndCBzYXkgdGhlIA0KPiBh
ZGRyZXNzZXMgYXJlIHN0YWJsZSwgb3IgaWYgaXQgZGlkbid0IHNheSB0aGF0IHRoZSBhZGRyZXNz
ZXMgY2FuIGJlIA0KPiBjYWxjdWxhdGVkIHN0YXRlbGVzc2x5LCB0aGVuIHRoYXQgd291bGQgYmUg
T0ssIGJ1dCBpdCBkb2VzLiBJIHRoaW5rIA0KPiB0aGF0IGlmIHlvdSB3YW50IHRvIHN0YW5kYXJk
aXplIHRoaXMgYXBwcm9hY2gsIHRoZW4gSU1PIHlvdSBuZWVkIHRvIA0KPiBxdWFudGlmeSB3aGF0
IGhhcHBlbnMgaW4gdGhlc2UgY2FzZXMuDQoNCk9rLiBJIHdpbGwgY3JhZnQgdGV4dCBhbG9uZyB0
aGVzZSBsaW5lcy4gQW1vbmcgb3RoZXIgdGhpbmdzLCBkaXNjdXNzIERFQ0xJTkVTLCBub3RlIHRo
YXQgY29sbGlzc2lvbnMgYXJlIGV4cGVjdGVkIHRvIGJlIHZpcnR1YWxseSBpbXBvc3NpYmxlIHRo
YW5rcyB0byB0aGUgYWRkcmVzcyBzcGFjZSwgZXRjLg0KDQoNCj4gQWxzbywgSSB0aGluayBzdGF0
ZWxlc3NuZXNzIGlzIHBvaW50bGVzcy4gREhDUHY2IGlzIGEgZnVuZGFtZW50YWxseSANCj4gc3Rh
dGVmdWwgcHJvdG9jb2wuIEl0J3Mgbm90IGp1c3QgdGhlIGxlYXNlIGRhdGFiYXNlIC0gY2xpZW50
cyBhbmQgDQo+IHNlcnZlcnMgYWxzbyBrZWVwIHRyYWNrIG9mIElBcywgc2VydmVyIElEcywgY2xp
ZW50IElEcywgRFVJRHMuIEV2ZW4gaWYgDQo+IHlvdSBtYWtlIHRoZSBhZGRyZXNzIGNhbGN1bGF0
aW9uIHN0YXRlbGVzcywgdG8gc2hvdyB2YWx1ZSB5b3UnbGwgbmVlZCANCj4gdG8gc2hvdyB3aGV0
aGVyIHRoaXMgc2NoZW1lIHdvcmtzIHdoZW4geW91IHN3YXAgb3V0IHNlcnZlcnMuIElmIGl0IA0K
PiB0aGlzIHNjaGVtZSBkb2Vzbid0IHdvcmsgd2hlbiB5b3Ugc3dhcCBzZXJ2ZXJzLCB0aGVuIHRo
ZXJlJ3MgcmVhbGx5IG5vIA0KPiBwb2ludCBpbiBtYWtpbmcgdGhlIGFkZHJlc3MgY2FsY3VsYXRp
b24gc3RhdGVsZXNzLCBzaW5jZSB5b3UgbmVlZCB0byANCj4gc2hhcmUgc3RhdGUgYW55d2F5Lg0K
DQpTd2FwID09IHJlcGxhY2UgdGhlIHNlcnZlciB3aXRoIGEgImNsb25lZCIgb25lIChzYW1lIElQ
djYgYWRkcmVzcywgYW5kIFNlcnZlciBEVUlEKT8NCg0Kb3IuLi4/DQoNCg0KDQo+IE1vcmUgaW4g
Z2VuZXJhbC4gV2hldGhlciB5b3UgY29udGludWUgd29yayBvbiB0aGlzIGRvY3VtZW50IGlzIHRv
IHlvdSwgDQo+IGJ1dCBJJ2xsIHBvaW50IG91dCB0aGF0IEJlcm5pZSBoYXMgc3RhdGVkIG11bHRp
cGxlIHRpbWVzIHRoYXQgaGUgd2FudHMgDQo+IHRvIHNlZSBwZW9wbGUgc3VwcG9ydCB0aGlzIGRy
YWZ0LCBub3QganVzdCAibm90IG9iamVjdCB0byBpdCIuIEkgZG9uJ3QgDQo+IHNlZSBtdWNoIGlu
IHRoZSB3YXkgb2Ygc3VwcG9ydCB0b2RheS4gQXMgZmFyIGFzIEknbSBjb25jZXJuZWQsIHlvdSBt
YXkgDQo+IGJlIGFibGUgdG8gYWRkcmVzcyB0aGUgaXNzdWVzIHRoYXQgSSBsaXN0IGFib3ZlIGFu
ZCByZW1vdmUgc29tZSBvZiB0aGUgDQo+IG9iamVjdGlvbnMsIGJ1dCBJIGRvdWJ0IHlvdSdsbCBi
ZSBhYmxlIHRvIGNvbnZpbmNlIG1lIHBlcnNvbmFsbHkgdGhhdCANCj4gdGhpcyBzY2hlbWUgaGFz
IHZhbHVlIGFuZCB0dXJuIG1lIGludG8gc3VwcG9ydGVyLg0KDQpQYXJ0IG9mIHRoYXQgc2VlbXMg
dG8gaGF2ZSB0byBkbyB3aXRoIGhvdyB0aGluZ3Mgd29yayBpZiB5b3Ugc3dhcCB0aGUgc2VydmVy
LiBJIGNhbiBnaXZlIHRoYXQgYSB0cnkgKGlmIHlvdSBzdGF5IG9wZW4gdG8gY2hhbmdlIHl1ciBt
aW5kIGlmIHRoYXQgbWFrZXMgc2Vuc2UpLg0KDQpUaGFua3MsDQotLQ0KRmVybmFuZG8gR29udA0K
U0k2IE5ldHdvcmtzDQplLW1haWw6IGZnb250QHNpNm5ldHdvcmtzLmNvbQ0KUEdQIEZpbmdlcnBy
aW50OiA2NjY2IDMxQzYgRDQ4NCA2M0IyIDhGQjEgRTNDNCBBRTI1IDBENTUgMUQ0RSA3NDkyDQoN
Cg0KDQoNCg==


From nobody Tue Apr 14 11:59:07 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C31031ACD1D for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 11:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 GOZlX_9duM5g for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 11:59:03 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 C46EA1ACD92 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 11:58:44 -0700 (PDT)
Received: from [186.134.14.206] (helo=[192.168.123.128]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1Yi62j-0006C8-L1; Tue, 14 Apr 2015 20:58:41 +0200
Message-ID: <552D6343.9050404@si6networks.com>
Date: Tue, 14 Apr 2015 15:58:11 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>,  Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com> <5527FA77.5070301@si6networks.com> <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com> <552C679E.4020305@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA66028@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA66028@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/uDDlacApyqaaf6wMNo33Okv52Eo>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 18:59:05 -0000

On 04/14/2015 02:49 PM, Bernie Volz (volz) wrote:
>> Ok. I will craft text along these lines. Among other things,
>> discuss DECLINES, note that collisions are expected to be virtually
>> impossible thanks to the address space, etc.
> 
> This is NOT true at all (collisions virtually impossible). In fact,
> the exact opposite will almost certainly be true.

May I ask that you provide a rationale for that assertion?

Mine is this: the subnet address space is so large that the problem is
essentially a birthday paradox.



> Also think of cases where much smaller spaces than a /64 are being
> used (such as when a server is configured for a start to end range (1
> to 100000)) or when a longer prefix length is being used (/96) for
> assigning addresses.

That is true. In the first version of the I-D we didn't support ranges.
Now we do, and we should certainly put a huge warning that the address
space should be huge, or things don't work as expected.

If you ask me, I'd say that the standard subnet size is /64. And if you
have a /64 but are assigning addresses from, say, a /110, that's where
the flaw relies. And if you just want to keep some part of the address
space for assigning static addresses to servers, then grab a small
address pool for that, and use the rest for the random/stable addresses
-- but not the other way around!

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Apr 14 12:44:01 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C88551ACDBE for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 12:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.683
X-Spam-Level: 
X-Spam-Status: No, score=-4.683 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 JKTht3dcZPli for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 12:43:57 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 931AB1B2F82 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 12:43:57 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3EJhs3R019932; Tue, 14 Apr 2015 21:43:54 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8199E20CF87; Tue, 14 Apr 2015 21:45:07 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 7345220CF79; Tue, 14 Apr 2015 21:45:07 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.86.2]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3EJhomY015057; Tue, 14 Apr 2015 21:43:53 +0200
Message-ID: <552D6DF6.5050905@gmail.com>
Date: Tue, 14 Apr 2015 22:43:50 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com>	<4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com>	<55254F6A.4020005@gmail.com>	<20150409.081427.74687401.sthaug@nethelp.no>	<4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk>	<552641FF.2070202@gmail.com>	<686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk>	<5526612A.7000502@gmail.com>	<4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com>	<5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com>
In-Reply-To: <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/1Ekrohzl3o6QzPXROhSbQr-hcSg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 19:44:00 -0000

Le 10/04/2015 22:00, ç¥žæ˜Žé�”å“‰ a Ã©crit :
[...]

> I don't know much about Linux internal, but BSD variants clearly
> separate the concepts of address and prefix in the kernel internal
> (you can see the latter by 'ndp -p'), and determine whether a
> particular destination is directly reachable just on the prefix
> information.

Yes.  Linux has a similar command to display structures of ND.

> You can indeed specify the "prefix length" when you manually
> configure an address, but this is actually a shortcut of manually
> configuring an address (which doesn't have a concept of prefix
> length) and manually configuring an on-link prefix derived from the
> address and the prefix length.
>
> I admit there may still be some confusing part, especially in user
> interfaces (e.g., in retrospect, it was a bad idea to use the
> default value of 64 for prefix length in BSD's ifconfig
> implementation), but it's not because implementors didn't understand
> the spec or the spec was unclear, but mainly due to technical
> compromise between protocol purity and compatibility/meeting
> expectations of legacy users.

On my side, I also think there is much confusion.

Even in Windows: one can not manually set an address without stating a 
prefixlength (named "subnet mask").

> I also tend to agree that there's some gap to be filled in the sense
> of protocol discussion: today it's not very clear how to manage an
> isolated network using DHCPv6-based address assignment.  (Although
> IMO this should be outside of rfc3315bis) just saying "run an
> RA-advertising server/router" is probably not enough at least in
> practice.  Also, if there's really a common case where running an
> RA-advertising node isn't feasible (I don't think the operational
> cost is a critical reason - if it's really needed it shouldn't be
> that difficult to unify that feature in a DHCPv6 server
> implementation), there may actually be a technical gap that has to be
> filled with some protocol extensions.  Only then it makes sense to
> discuss a specific solution like providing on-link prefix information
> via DHCPv6.
>
>> From the discussion so far, I wasn't even convinced whether you
> deployment example proves the need for *some* protocol enhancements.
> Simply repeating the need for a specific solution of 'prefix-info by
> DHCPv6' without even persuading others on the problem won't get us
> anywhere.

Right.

> So, if I may, my suggestion for you is to write an I-D explaining
> why you cannot deploy your network with a router (or any node) that
> keeps advertising RAs.  If it's convincing enough we can then move on
> to the next step.

Ok; I will need co-authors.

Alex

>
> -- JINMEI, Tatuya
>



From nobody Tue Apr 14 17:53:02 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B25991B2ABA for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 17:53:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 H8H6FWoIZCOO for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 17:53:00 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D70331B2A62 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 17:52:47 -0700 (PDT)
Received: by igbqf9 with SMTP id qf9so29399092igb.1 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 17:52:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=nVUUOKim0a4UC16zdE65eOZmLHuPlQbntCgFOy0USfg=; b=kTERSk7/g0qA8bVRNNFEbaMilt/+uBoA2lMKYRtHxuUgb9ZAyjj++ts1sctpwUMBSk WtW5HRELkgJuz78xDJmZuqaznIu4U1mSA73RoZ1Aovs/bM33jdQ4muExwmSbRCLsCSkT vAVrRXN2EFPnhzXxWGhDUB5amSPjnBvOBPGRAVU6SDZNZ53eS4TcebRB9C2aRmptF5jr s0ydUooHc6lZPP9wJtoGKrGzd1fm10bSxT+cHrakeyjCzu571yQWxPHyc8tDtCPVU3vz Oko5FaVgJzsI8y04lQWiOmvc2WPo3E/lHvL3Z4VVmuT21IPPQ07Sa8L6QmnhrOridsyn tfDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=nVUUOKim0a4UC16zdE65eOZmLHuPlQbntCgFOy0USfg=; b=FVBclxy3WcbMseLy2ZXmZa7y2Bg1aKD2rlyFGZ3WED9eEnUQ4hmbTDD0aVSjJdTRcN BjfcQ9RJbjb4B+WBMRUddXBFcNcfNgKEXmiV2IquzLAy4bxTUJdyFQgQlWrI4q3A/VqY B995jj+dSWDVNv+TSsmx5wYHrzuH41/SCcNzptKLkAiWw2i8Km6EOphCFkBssUk99JBF yDlf1oMU8+vWnnc7wDXQepFl+1WLthNHw7wriCQyHqDY1W1/OAYm56eh6IwVTq6hVHky r8FC76Bre1YDFJ/T2fED1oizpDyS5HbrH/fJLYESpmLo+X+6oBPfmFE27rNUgcPXTvmx Ubqw==
X-Gm-Message-State: ALoCoQnPNynBDwtJOB4ekULrDmDUXedcM67E2HBe9aaEJa2p7Xhuhj8Xeg2ADe5CBJD1epmOG7FS
X-Received: by 10.50.137.97 with SMTP id qh1mr28352277igb.39.1429059167314; Tue, 14 Apr 2015 17:52:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Tue, 14 Apr 2015 17:52:26 -0700 (PDT)
In-Reply-To: <552D6DF6.5050905@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 09:52:26 +0900
Message-ID: <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3f1f40816ea0513b8c40c
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/fvnyyn2QYdwXeqHyAXMqVph10ls>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 00:53:01 -0000

--001a11c3f1f40816ea0513b8c40c
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 4:43 AM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> So, if I may, my suggestion for you is to write an I-D explaining
>> why you cannot deploy your network with a router (or any node) that
>> keeps advertising RAs.  If it's convincing enough we can then move on
>> to the next step.
>>
>
> Ok; I will need co-authors.
>

Before you start writing a document... what is the reason that you can't do
this?

--001a11c3f1f40816ea0513b8c40c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 4:43 AM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petr=
escu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><spa=
n class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">So, if I may, my suggestion for=
 you is to write an I-D explaining<br>
why you cannot deploy your network with a router (or any node) that<br>
keeps advertising RAs.=C2=A0 If it&#39;s convincing enough we can then move=
 on<br>
to the next step.<br>
</blockquote>
<br></span>
Ok; I will need co-authors.<br></blockquote><div><br></div><div>Before you =
start writing a document... what is the reason that you can&#39;t do this?=
=C2=A0</div></div></div></div>

--001a11c3f1f40816ea0513b8c40c--


From nobody Tue Apr 14 18:09:57 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 665841B2AED for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 18:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 98nE2k74Wttq for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 18:09:55 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F02961B2AEC for <dhcwg@ietf.org>; Tue, 14 Apr 2015 18:09:54 -0700 (PDT)
Received: by iejt8 with SMTP id t8so29588582iej.2 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 18:09:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0BSNwsxSmw9aCiiK9MxUmg0RJJo2u/B7+U8w6ZCLgHI=; b=oJNwBZ8+L8crTStOsB6/u+AYb55As+KEGBMcZK8w6Zxinj2GU2ls0pH7AZWDym2QRJ 4UX8whaPtnnPcVvIhOXbq5KjDMbZeI87m2VUKvrcN2n9f1OtswDTM1jdxBYw9+ZeRCJC SzwsNyFUGawgjGcmvGQ88m4b9e9zDJlDb4HP2W10hql0n1aKp2+sy9zBJg2YK7pZLrwX 9d0JhYURzzfIXv/h1bxeeniJ4mZSjJhftC0QUm2yR59HkWnLoIHIJ+ehv9XxBLaBHD7Q xZMh4LHSNIkQwlLxN9eerThYrN1EYdx362gLlxrV+7iiG9tRDAVzrYmrXSuC0a6hrZRt LAJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=0BSNwsxSmw9aCiiK9MxUmg0RJJo2u/B7+U8w6ZCLgHI=; b=A0uXYiG9etfraUEzuO9xXv9KU1tGKLcGmRXQxmLESD+wLNB/KRFtuWoucYdoI6w3gc /umQXET6g0c7iF+uMYbggX0yyMtZieqn3S7OwygGWZnIM0ZIL2JyRxSTpPwtKFFm8cCB 0RHkgAAYu9K15hq2OvCDPc3cCa85rdqYH63KgdEA4JR7FG4s2J788gwoP66ERdMo7BvR qOdvfidtoNdZVeTzASrs/H9sHR0971YjoC5JgMWep3rsiftuIXej2dogwLnTlTK24R58 2NmAV40X/h+87RPOoPVdptR5EwfRMpp0+vi9pEv481Zyum7IWyxXo3e4fN3XXmWf+xTN WHbA==
X-Gm-Message-State: ALoCoQk9vXJLu7dLjg6iAe4HpWvIWsEVvEzOM9PMIHZp0T8aawMXJhAHylEajsPZ+dkt6pZ4EBQo
X-Received: by 10.42.207.206 with SMTP id fz14mr29137994icb.34.1429060194286;  Tue, 14 Apr 2015 18:09:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Tue, 14 Apr 2015 18:09:33 -0700 (PDT)
In-Reply-To: <552D6343.9050404@si6networks.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com> <5527FA77.5070301@si6networks.com> <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com> <552C679E.4020305@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA66028@xmb-rcd-x04.cisco.com> <552D6343.9050404@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 10:09:33 +0900
Message-ID: <CAKD1Yr1v7Rf+uKCcYwsCKkSTuRUegQVMuPDfefR71Xb836LqaA@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=20cf30426df63e7abf0513b901c1
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/2Cg9280eGdl86ytjwAQj1LGhewI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 01:09:56 -0000

--20cf30426df63e7abf0513b901c1
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 3:58 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> That is true. In the first version of the I-D we didn't support ranges.
> Now we do, and we should certainly put a huge warning that the address
> space should be huge, or things don't work as expected.
>

Supporting stateless allocation in anything smaller than a /64 is harmful.

You are creating the risk that people coming from outdated IPv4 assumptions
will take a /112, think, "That's big enough for everyone, right? I only
have a few hundred hosts. And I want to limit my subnet size to avoid these
ND cache DoS attacks I've heard about," and get burned by the fact that
there's a 50% chance of collision when there are 250 hosts in the network.
Because your algorithm doesn't support collisions well, they'll be
completely stuck.

Before you argue that it makes sense to support stateless allocation when
the subnet is "large enough" - how large is large enough? People used to
fully-stateful IPv4 deployments with forced forwarding (e.g., large
conference networks that force 1 IPv4 address = 1 MAC address and don't use
broadcast ARP because the wifi chipset filters it out for them) may well do
something like /96 (That's large enough, right? It's the size of the whole
of the IPv4 Internet!) and put 20,000 hosts on it and fall over in the same
way. Yes - large conferences like MWC do have 20k hosts on the same subnet.

Also - if you change the range size, do all the addresses change? That
would make it an even worse idea.

--20cf30426df63e7abf0513b901c1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 3:58 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That is true. In the fi=
rst version of the I-D we didn&#39;t support ranges.<br>
Now we do, and we should certainly put a huge warning that the address<br>
space should be huge, or things don&#39;t work as expected.<br></blockquote=
><div><br></div><div>Supporting stateless allocation in anything smaller th=
an a /64 is harmful.</div><div><br></div><div>You are creating the risk tha=
t people coming from outdated IPv4 assumptions will take a /112, think, &qu=
ot;That&#39;s big enough for everyone, right? I only have a few hundred hos=
ts. And I want to limit my subnet size to avoid these ND cache DoS attacks =
I&#39;ve heard about,&quot; and get burned by the fact that there&#39;s a 5=
0% chance of collision when there are 250 hosts in the network. Because you=
r algorithm doesn&#39;t support collisions well, they&#39;ll be completely =
stuck.</div><div><br></div><div>Before you argue that it makes sense to sup=
port stateless allocation when the subnet is &quot;large enough&quot; - how=
 large is large enough? People used to fully-stateful IPv4 deployments with=
 forced forwarding (e.g., large conference networks that force 1 IPv4 addre=
ss =3D 1 MAC address and don&#39;t use broadcast ARP because the wifi chips=
et filters it out for them) may well do something like /96 (That&#39;s larg=
e enough, right? It&#39;s the size of the whole of the IPv4 Internet!) and =
put 20,000 hosts on it and fall over in the same way. Yes - large conferenc=
es like MWC do have 20k hosts on the same subnet.</div><div><br></div><div>=
Also - if you change the range size, do all the addresses change? That woul=
d make it an even worse idea.</div></div></div></div>

--20cf30426df63e7abf0513b901c1--


From nobody Tue Apr 14 18:51:18 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 858A91B2BE2 for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 18:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 sXc1iHyfc3fS for <dhcwg@ietfa.amsl.com>; Tue, 14 Apr 2015 18:51:15 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 987341B2BD3 for <dhcwg@ietf.org>; Tue, 14 Apr 2015 18:51:15 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 35E08DA01AB; Wed, 15 Apr 2015 01:51:15 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 14 Apr 2015 18:51:14 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <552D6343.9050404@si6networks.com>
Date: Tue, 14 Apr 2015 21:51:03 -0400
Content-Transfer-Encoding: 7bit
Message-ID: <CF0CC1A9-8455-41DD-84DD-E0E05895C912@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <CAKD1Yr2Ztzoys+xKBzsEHU5hqJmfGpn-GeWPEqNCHRuWOTgsJQ@mail.gmail.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com> <5527FA77.5070301@si6networks.com> <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com> <552C679E.4020305@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA66028@xmb-rcd-x04.cisco.com> <552D6343.9050404@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/_JyfF49BvPhTCXphrzzoc7LVO7k>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 01:51:17 -0000

On Apr 14, 2015, at 2:58 PM, Fernando Gont <fgont@si6networks.com> wrote:
> Mine is this: the subnet address space is so large that the problem is
> essentially a birthday paradox.

That assumes a random distribution.


From nobody Wed Apr 15 00:57:25 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 118891B3296; Wed, 15 Apr 2015 00:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 9j7IRTgcZjMW; Wed, 15 Apr 2015 00:57:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A832E1B3290; Wed, 15 Apr 2015 00:57:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150415075722.12607.96285.idtracker@ietfa.amsl.com>
Date: Wed, 15 Apr 2015 00:57:22 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jXXY7SBSYLPGkBIFE-IQl57JX7w>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dynamic-shared-v4allocation-06.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 07:57:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Dynamic Allocation of Shared IPv4 Addresses
        Authors         : Yong Cui
                          Qiong Sun
                          Ian Farrer
                          Yiu L. Lee
                          Qi Sun
                          Mohamed Boucadair
	Filename        : draft-ietf-dhc-dynamic-shared-v4allocation-06.txt
	Pages           : 14
	Date            : 2015-04-15

Abstract:
   This memo describes the dynamic allocation of shared IPv4 addresses
   to clients using DHCPv4.  Address sharing allows a single IPv4
   address to be allocated to multiple active clients simultaneously,
   each client being differentiated by a unique set of transport layer
   source port numbers.  The necessary changes to existing DHCPv4 client
   and server behavior are described and a new DHCPv4 option for
   provisioning clients with shared IPv4 addresses is included.

   Due to the nature of IP address sharing, some limitations to its
   applicability are necessary.  This memo describes these limitations
   and recommends suitable architectures and technologies where address
   sharing may be utilized.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dynamic-shared-v4allocation-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Apr 15 00:57:34 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 943BC1B329D; Wed, 15 Apr 2015 00:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 CxKNbt7ICdZG; Wed, 15 Apr 2015 00:57:25 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D87A51B3292; Wed, 15 Apr 2015 00:57:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <draft-ietf-dhc-dynamic-shared-v4allocation.ad@ietf.org>, <volz@cisco.com>, <dhc-chairs@ietf.org>, <draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org>, <dhcwg@ietf.org>,  <draft-ietf-dhc-dynamic-shared-v4allocation.shepherd@ietf.org>,  <brian@innovationslab.net>, 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150415075722.12607.23392.idtracker@ietfa.amsl.com>
Date: Wed, 15 Apr 2015 00:57:22 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/QCRoOVvoj-RQN0II2N3CaATSpik>
Subject: [dhcwg] New Version Notification - draft-ietf-dhc-dynamic-shared-v4allocation-06.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 07:57:26 -0000

A new version (-06) has been submitted for draft-ietf-dhc-dynamic-shared-v4allocation:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dynamic-shared-v4allocation-06.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dynamic-shared-v4allocation-06

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Wed Apr 15 03:34:08 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8807B1A1B53 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 03:34:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 ttn6MbFsPjso for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 03:34:03 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D68C81A1B5F for <dhcwg@ietf.org>; Wed, 15 Apr 2015 03:34:02 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FAXwDb004501; Wed, 15 Apr 2015 12:33:58 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0B1BB203F21; Wed, 15 Apr 2015 12:35:13 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E5D32203EB1; Wed, 15 Apr 2015 12:35:12 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FAXabU009726; Wed, 15 Apr 2015 12:33:58 +0200
Message-ID: <552E3E7F.7060702@gmail.com>
Date: Wed, 15 Apr 2015 13:33:35 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/3PflcZOMzIDQ0QOs8TDGHCkIUlM>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 10:34:07 -0000

Le 15/04/2015 03:52, Lorenzo Colitti a Ã©crit :
> On Wed, Apr 15, 2015 at 4:43 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>         So, if I may, my suggestion for you is to write an I-D explaining
>         why you cannot deploy your network with a router (or any node) that
>         keeps advertising RAs.  If it's convincing enough we can then
>         move on
>         to the next step.
>
>
>     Ok; I will need co-authors.
>
>
> Before you start writing a document... what is the reason that you can't
> do this?

BEfore answering that - do we agree that the plen is mandatory?

Alex



From nobody Wed Apr 15 03:38:47 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C051A1B80 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 03:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 wAtjURc0Jwvx for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 03:38:45 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 063D91A1B7F for <dhcwg@ietf.org>; Wed, 15 Apr 2015 03:38:45 -0700 (PDT)
Received: by oiko83 with SMTP id o83so16611998oik.1 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 03:38:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LL9RDwMf9HgzTPHjsSit5AglThWmzbPrILudcXcNVAI=; b=bmAjAT7KEq8DZsPkq3SjetMQ9a4yla7v0tHvdjjiZA5ct1sn3CIoIvzo1gzw1FsJ7k dG9K01lH15F15D7CMaTtZq/uzAoX0cm+k5jQkOphnrDvznSNBJxRfgUU3D46NFmhM4la 7lM+//kB4w7IaK0T6ZJ94FlWv/3dAD2KhOYiGjrE2aoGn/wqIyjAV4SMccGW5C6yeJy+ HNMV1zZte1d9AmBwHnD+Ui1RGYrS/Sg2vE63PR8bRP6LEX6OJelrK3oVjbc/aOj7IeeX YHj+S6/vfoZOJchIpyWaKeCUqM1HYOLIESNNtAcdJD8xs8sMvmaENEp5iIaHVfyQxshy A8kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=LL9RDwMf9HgzTPHjsSit5AglThWmzbPrILudcXcNVAI=; b=hSTlynp1QVdm0FTV/Enw57jhDpU1qb/NaDOZ7fypX8xh3IaIp+MB1CTucuWHyDFs9E UBGFfKk0CfBoQeNL2n5S1nnBP+WGlVDCYGjoVu/Hgzq7+QsEoZ+PdRDSuSxXsBer2qbT qWnBYCtPLKTsRZ1PQcfmvzaQq1XgoZU4mJ0Ij+f8xFa4TRHn/pBdGW1/TT5dw/xIJLwU +wXC6MwLg6KJf9Cix3NGz5yXfCNL6CK65NVegZhW9Rl2rCKIUMRBg4gbWjnwDK9Lf9hl mvU0WfN3wE2Q42j2c+QEMJSB229sLJbqGGyJ+I14S3bNs/VsCKnWGl7Cl+d6gu7+upf7 TnyQ==
X-Gm-Message-State: ALoCoQlg7Ng97eor4wnsRekiOOLpE1f1dxOcokKqhIsU3kaCKNYAVlvumRljcC5E+SZrmeo3sa5g
X-Received: by 10.50.43.162 with SMTP id x2mr30218431igl.46.1429094324477; Wed, 15 Apr 2015 03:38:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 15 Apr 2015 03:38:23 -0700 (PDT)
In-Reply-To: <552E3E7F.7060702@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 19:38:23 +0900
Message-ID: <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=089e0103e4ce8fed430513c0f397
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/GiUHUI_x93oL8i8mKHQnG_QfrV4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 10:38:46 -0000

--089e0103e4ce8fed430513c0f397
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 7:33 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

>         So, if I may, my suggestion for you is to write an I-D explaining
>>         why you cannot deploy your network with a router (or any node)
>> that
>>         keeps advertising RAs.  If it's convincing enough we can then
>>         move on
>>         to the next step.
>>
>>
>>     Ok; I will need co-authors.
>>
>>
>> Before you start writing a document... what is the reason that you can't
>> do this?
>>
>
> BEfore answering that - do we agree that the plen is mandatory?
>

plen of what? Of an address? Of an on-link prefix?

Mandatory for what?

--089e0103e4ce8fed430513c0f397
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 7:33 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petr=
escu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><span class=3D"">=C2=A0 =C2=A0 =C2=A0 =C2=A0 So,=
 if I may, my suggestion for you is to write an I-D explaining<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 why you cannot deploy your network with a route=
r (or any node) that<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 keeps advertising RAs.=C2=A0 If it&#39;s convin=
cing enough we can then<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 move on<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to the next step.<br>
<br>
<br>
=C2=A0 =C2=A0 Ok; I will need co-authors.<br>
<br>
<br>
Before you start writing a document... what is the reason that you can&#39;=
t<br>
do this?<br>
</span></blockquote>
<br>
BEfore answering that - do we agree that the plen is mandatory?<br></blockq=
uote><div><br></div><div>plen of what? Of an address? Of an on-link prefix?=
</div><div><br></div><div>Mandatory for what?=C2=A0</div></div></div></div>

--089e0103e4ce8fed430513c0f397--


From nobody Wed Apr 15 03:44:05 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A8E41A1BD1 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 03:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 sr4-cyyBhObF for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 03:44:02 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 964FC1A1BDC for <dhcwg@ietf.org>; Wed, 15 Apr 2015 03:44:00 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FAhuGf006957; Wed, 15 Apr 2015 12:43:56 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 27050203FBC; Wed, 15 Apr 2015 12:45:11 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 17482203FB8; Wed, 15 Apr 2015 12:45:11 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FAhrOl022657; Wed, 15 Apr 2015 12:43:56 +0200
Message-ID: <552E40E9.7040203@gmail.com>
Date: Wed, 15 Apr 2015 13:43:53 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com>
In-Reply-To: <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/CdqJxUbKXYalrWcfLGCAoBsNg0U>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 10:44:03 -0000

Le 15/04/2015 13:38, Lorenzo Colitti a Ã©crit :
> On Wed, Apr 15, 2015 at 7:33 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>                  So, if I may, my suggestion for you is to write an I-D
>         explaining
>                  why you cannot deploy your network with a router (or
>         any node) that
>                  keeps advertising RAs.  If it's convincing enough we
>         can then
>                  move on
>                  to the next step.
>
>
>              Ok; I will need co-authors.
>
>
>         Before you start writing a document... what is the reason that
>         you can't
>         do this?
>
>
>     BEfore answering that - do we agree that the plen is mandatory?
>
>
> plen of what? Of an address? Of an on-link prefix?
>
> Mandatory for what?

Whenever assigning an address to some computer a plen must be given as 
well (a decimal value between 1 and 128).  Do we agree with this?

Alex




From nobody Wed Apr 15 04:06:12 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B16F1A6FFC for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 M7Gpd7Z7A4_w for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:06:09 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7711A6FFB for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:06:08 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.61] (88-111-162-175.dynamic.dsl.as9105.com [88.111.162.175]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id CD97E1BC3E for <dhcwg@ietf.org>; Wed, 15 Apr 2015 11:06:04 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <552E40E9.7040203@gmail.com>
Date: Wed, 15 Apr 2015 12:06:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <62377F15-094C-4D99-BB43-6F03B7563AA1@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com> <552E40E9.7040203@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jCiaZ0XeaWM3X4PaE95vCe5RFoM>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 11:06:11 -0000

Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

>> plen of what? Of an address? Of an on-link prefix?
>>=20
>> Mandatory for what?
>=20
> Whenever assigning an address to some computer a plen must be given as =
well (a decimal value between 1 and 128).  Do we agree with this?

No. Because it is not.
The fact that some (most ?) implementations require it for =
historical/compatibility reasons does not make it so.




From nobody Wed Apr 15 04:21:15 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8551A702C for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 jpU4-NX8LQgT for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:21:12 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 661801B34D9 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:16:29 -0700 (PDT)
Received: by oign205 with SMTP id n205so17411296oig.2 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:16:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bFaI7DwfgKCUcuaMmDb/U+3zt1ai6h0oQF5fgNhD82k=; b=JBUAEeIgMc6b82fCbF2NTtvvL2/mXHlmp9/9ONsLHFULrZyBQcbQONiasXjgSU2avi BmJMTiK1SecJ9D1O0VLAVm9hzfJFkijdG8mSMuBZpq3u83jmiW4QKrqGdoaGqtGitLwr NS1RmGD8Lco1FdR8viPUD1C7OTpuXRN4+CdWA8qLzT+ziEjweVLGe01CabzQGkQFPNUf CAwOHOwNF6Aom9yCRqRPrEir7GDJ5pjmz+DxM0RpkRKLyXoOoBZvRozRc6HJJKdDJZdo /YvrBOURF1/Nch882cjhrkS1K0pzYfwm1r0TqDI2gmoeBKXqW8bMYw/pxz3PqgyGN7E2 LJVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=bFaI7DwfgKCUcuaMmDb/U+3zt1ai6h0oQF5fgNhD82k=; b=M0aNmHVUkr1AatVAsFCqzW21qGEjO0C+rPANe1r26pbClH8xlWbJQRmV7yGsb8dnRu 4dohCNZ1XXzG0znK3cTVaTiKFdQDDwYBu44uuRy4C6Mq5tbcsC0Nfx70bfxZ5sdH2FJX kX1nuVtdATYGH64hfiiQY/bVLDob4IE83dQyXzRNiK50oSywMWo0StjHg6tjEneQjQhM uOujfDrKE3gNrIZ10dItw+UK/+uDCzocqxfG5B2p1lTPAz/Ox4MJ+QvG940SCrZZ8L6/ TAdjm1hx+r4uILfTaSxtUMnYoEvnhXhTiCxGJyV/wtSVrrIm378QYFJ410Iu0cc8ef+a 9yeA==
X-Gm-Message-State: ALoCoQnAkULT4G3YIQrp5FzDzKTLSMx74dWwH4/0YqkAZMw07Foi56YfjwTRDzLEaiWhV8rAbm5L
X-Received: by 10.43.119.196 with SMTP id fv4mr30860901icc.83.1429096588866; Wed, 15 Apr 2015 04:16:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 15 Apr 2015 04:16:08 -0700 (PDT)
In-Reply-To: <552E40E9.7040203@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com> <552E40E9.7040203@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 20:16:08 +0900
Message-ID: <CAKD1Yr2j2k_a8bd7G08HyqbehBMZyjWpOjCXna5eUWh7ZvQhUA@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec517cdec87a9470513c17a46
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/7SzmK74kfSktjrVTAw5L7yj9Wf0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 11:21:13 -0000

--bcaec517cdec87a9470513c17a46
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 7:43 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> Whenever assigning an address to some computer a plen must be given as
> well (a decimal value between 1 and 128).  Do we agree with this?
>

Even if we did agree, it wouldn't really matter, because the IETF does not
standardize node user interfaces. It primarily standardizes node behaviour.

--bcaec517cdec87a9470513c17a46
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 7:43 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petr=
escu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When=
ever assigning an address to some computer a plen must be given as well (a =
decimal value between 1 and 128).=C2=A0 Do we agree with this?<br></blockqu=
ote><div><br></div><div>Even if we did agree, it wouldn&#39;t really matter=
, because the IETF does not standardize node user interfaces. It primarily =
standardizes node behaviour.</div></div></div></div>

--bcaec517cdec87a9470513c17a46--


From nobody Wed Apr 15 04:24:59 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5671A86FE for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 nGnjVlTX2pbm for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:24:57 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id 433681A8702 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:24:57 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.61] (88-111-162-175.dynamic.dsl.as9105.com [88.111.162.175]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id A6C4F1BC3E for <dhcwg@ietf.org>; Wed, 15 Apr 2015 11:24:53 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <CAKD1Yr2j2k_a8bd7G08HyqbehBMZyjWpOjCXna5eUWh7ZvQhUA@mail.gmail.com>
Date: Wed, 15 Apr 2015 12:24:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB14E8A4-7DDA-46DF-958D-C667A3D2A1E9@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com> <552E40E9.7040203@gmail.com> <CAKD1Yr2j2k_a8bd7G08HyqbehBMZyjWpOjCXna5eUWh7ZvQhUA@mail.gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SB8TFQtDv4FTKhJ-sOf-ZSNLvfw>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 11:24:58 -0000

Lorenzo Colitti <lorenzo@google.com> wrote:

> Even if we did agree, it wouldn't really matter, because the IETF does =
not standardize node user interfaces. It primarily standardizes node =
behaviour.

But I think Alexandru's argument is that a node cannot operate if it has =
an address without a prefix length - that's behaviour rather than user =
interface.



From nobody Wed Apr 15 04:33:31 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F195B1A8794 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 NTPkXRof7d9v for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:33:28 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 158401A8793 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:33:27 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FBXPwr013895 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 13:33:25 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A34FC203FBC for <dhcwg@ietf.org>; Wed, 15 Apr 2015 13:34:39 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9B7F5203FB8 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 13:34:39 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FBX3KQ021516 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 13:33:25 +0200
Message-ID: <552E4C6E.1040204@gmail.com>
Date: Wed, 15 Apr 2015 14:33:02 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com> <552E40E9.7040203@gmail.com> <62377F15-094C-4D99-BB43-6F03B7563AA1@thehobsons.co.uk>
In-Reply-To: <62377F15-094C-4D99-BB43-6F03B7563AA1@thehobsons.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/tJMoKTCqTnq49LmO8G8W7xqvuv0>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 11:33:30 -0000

Le 15/04/2015 14:06, Simon Hobson a écrit :
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>>> plen of what? Of an address? Of an on-link prefix?
>>>
>>> Mandatory for what?
>>
>> Whenever assigning an address to some computer a plen must be
>> given as well (a decimal value between 1 and 128).  Do we agree
>> with this?
>
> No. Because it is not. The fact that some (most ?) implementations
> require it for historical/compatibility reasons does not make it so.

An address does not have a prefixlen.  A prefixlen for that address is
required in order to behave and determine neighbordhood relationships 
("on-link determination RFC4861") and optimizations such as reducing 
search times and routing table sizes.  An implicit prefixlen is valued 
at 128 on some node user interface, and 64 on another node user 
interface.  An explicit prefixlen may be specified by RA.

Hm?

Alex



>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>
>



From nobody Wed Apr 15 04:33:52 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8F21A87AA for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 JUx2E4aCdVy9 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:33:49 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64B1F1A8793 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:33:49 -0700 (PDT)
Received: by obfe9 with SMTP id e9so15755467obf.1 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:33:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RyYIN9op9Fw8jZ7E9A/uDWQGHY1skFsDlij+4jOWC5I=; b=QtAWO0ex5HQ5FJhM1zH5UbV4TxQDdZ3JOV+Yojw11P6El7+p4gJmxU2cJeo3qt+mPf Hy7Ohm69uAguBbjG9HkYvKxyXG01btcsFy4rx6KU/kl8ymim1m6n3DY8KY018AgmGr+N iZUk6AWXiZz0yGtqFyle5D2OWG6UQQoFOIRf7cdAKVgq8OJi+Fq1vXNTHJ5JNt5o4kcx N/7hbEdR7hupjPQSARyda3jhR7qBQ8HFloBKzHfFtJ/vPuD9kXeOquOb1kWUyIiWuVxF uAi8irHkzRGa46utzQHrv44C73VTFOSCIC6HGBqBiLPklR+uAGOsdR/gsYMlJbw6esYf FcGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=RyYIN9op9Fw8jZ7E9A/uDWQGHY1skFsDlij+4jOWC5I=; b=QZ1GPw1XaukaZjXUhN4wlanTY6M1wPUeivpXW2HDUjNd1dCNy9C5wiczXoLK48xSST l+AwUcotUE5VkNKSTQKhek/NmU04bqH8tEi/kxD41kc38D0nlnHjp4bg4uhljmw6C8W4 +5KoJpKT1cTMMpLfOIvW7H2X3/sajOejrRN79NMQan1r4ErTK17tsz/BSrmerfydJzP1 U2/Ly2M/6hVNYIv/Cujp6ecZZUdFq/cTiCxjnTSHj6z7AyVROnaFstU8AJohEl8iqe+F bm/2aOqUuRNrYSRp+XWkuxf3bdm5t/dHX000AMFY81s7XhZxLgU4rbpzJN1jyDLkHcvX FyDg==
X-Gm-Message-State: ALoCoQn1ws3FzeSACCtaZ1npYuxnpzcHBzrWVaA4G1B9s6WAXesx4BxRFedVjZnz7FFER1BUaEnr
X-Received: by 10.107.34.210 with SMTP id i201mr35570587ioi.1.1429097628779; Wed, 15 Apr 2015 04:33:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 15 Apr 2015 04:33:27 -0700 (PDT)
In-Reply-To: <BB14E8A4-7DDA-46DF-958D-C667A3D2A1E9@thehobsons.co.uk>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com> <552E40E9.7040203@gmail.com> <CAKD1Yr2j2k_a8bd7G08HyqbehBMZyjWpOjCXna5eUWh7ZvQhUA@mail.gmail.com> <BB14E8A4-7DDA-46DF-958D-C667A3D2A1E9@thehobsons.co.uk>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 20:33:27 +0900
Message-ID: <CAKD1Yr2bzsE5szO48XvV1MbY-UEMHPaBeJT6pWOEowCOdxQLyw@mail.gmail.com>
To: Simon Hobson <linux@thehobsons.co.uk>
Content-Type: multipart/alternative; boundary=001a114031a08371960513c1b865
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Z-kJsb_F0r7xLHmu9kecxOdgY5Q>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 11:33:50 -0000

--001a114031a08371960513c1b865
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 8:24 PM, Simon Hobson <linux@thehobsons.co.uk>
wrote:

> > Even if we did agree, it wouldn't really matter, because the IETF does
> not standardize node user interfaces. It primarily standardizes node
> behaviour.
>
> But I think Alexandru's argument is that a node cannot operate if it has
> an address without a prefix length - that's behaviour rather than user
> interface.


If it can't, then it's in violation of RFC 5942, no?

--001a114031a08371960513c1b865
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 8:24 PM, Simon Hobson <span dir=3D"ltr">&lt;<a href=3D"=
mailto:linux@thehobsons.co.uk" target=3D"_blank">linux@thehobsons.co.uk</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; =
Even if we did agree, it wouldn&#39;t really matter, because the IETF does =
not standardize node user interfaces. It primarily standardizes node behavi=
our.<br>
<br>
</span>But I think Alexandru&#39;s argument is that a node cannot operate i=
f it has an address without a prefix length - that&#39;s behaviour rather t=
han user interface.</blockquote><div><br></div><div>If it can&#39;t, then i=
t&#39;s in violation of RFC 5942, no?=C2=A0<br></div></div></div></div>

--001a114031a08371960513c1b865--


From nobody Wed Apr 15 04:39:34 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4AB1A87AA for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 2A9ivoFY2Li9 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:39:32 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 78F7F1A879E for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:39:32 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id F25CFDA01E8; Wed, 15 Apr 2015 11:39:31 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 15 Apr 2015 04:39:31 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <552E3E7F.7060702@gmail.com>
Date: Wed, 15 Apr 2015 07:39:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/d97yTV-RuxFXkCy21MxcO3_7eQI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 11:39:33 -0000

On Apr 15, 2015, at 6:33 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
> BEfore answering that - do we agree that the plen is mandatory?

No.   All you need is a default route.   Prefix length is optional.


From nobody Wed Apr 15 04:42:00 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC2EE1A87C1 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 9QsZmAVNZgJR for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 04:41:58 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D73581A87C2 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:41:57 -0700 (PDT)
Received: by oica37 with SMTP id a37so18028950oic.0 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 04:41:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=nyLFro4kx/OSYKh3LPhKD5+JoPYV6bMbG/8trU6+agg=; b=lWrobSG7PJnOnDHZJdwN4d3ee0UC8A0ydfs0+9WRi7a7bIfG7FHq+4EKFl5bhQOpBU zmTYuSVuUvg2tVWXwIoP9X558MKjQiFRdU/mBQz7wdA7uAm3jLIk9kRNDbAl7CEbEoUI I7k7ueyBDYROX1482P2tWZGxVxKFdPxwNfb1L6x2Kb9VTJqkBWFu5OBLRw+3nFkkVQZn 8sdBTSLQW9yG9MoK4PmmGbL9cutpf54hDt8ae/TKyabWqIq7p/Qne8h4YfMGj8RSRAha gLDrNVb3zEPHPTyr/0Lj9wUzBcQ/+zXIt5+gdL3a66kKVrsXuu7Ul2cKiSDcn3/qhGsg P8Gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=nyLFro4kx/OSYKh3LPhKD5+JoPYV6bMbG/8trU6+agg=; b=IDnLddiqCGzJ+jblsOnRud018BpMSKwwPTonp8U+rNOxZ+0uIm5SercxVkqj8aUERw 7vqiPdJlqK4nJp41P7B9whxwl+VXuFpa5FdOFU/b/EFUf4XndhdY/RoEJfc5FOIzi7jQ SCSqKTtjgKWhDmgN3ChR1r6+9wIsFTJD1L8CeHeC+FxQpguOtRooPgy/Eo171jbStH73 POCR71FyO1z8YesvJmTR7sZ41M+Osf7nYgaEmHZc6h5WmSi1iR7NoRJ/ovTM8oAnPZib m6PTQD347HGvF5903s1HV21mM7oWwAopXyUmPEPabdzbEMod+gfCu4pRBXne98HcghOV gWAQ==
X-Gm-Message-State: ALoCoQmErakdXBgIodA9wWM4XKUn+5kUEWM4p7pcgDdLUvnDCV6N4IyTgNLdm2NvmfMcT4p3gatF
X-Received: by 10.107.46.155 with SMTP id u27mr7166172iou.87.1429098117259; Wed, 15 Apr 2015 04:41:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 15 Apr 2015 04:41:36 -0700 (PDT)
In-Reply-To: <552E4C6E.1040204@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com> <552E40E9.7040203@gmail.com> <62377F15-094C-4D99-BB43-6F03B7563AA1@thehobsons.co.uk> <552E4C6E.1040204@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 20:41:36 +0900
Message-ID: <CAKD1Yr06RVriDi=PZkveziSOXM95HrW+2PE_5wHdVcr2XGb64g@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ac5b6a124530513c1d511
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Ti2758KfbrZ8uyq9DHZPFTRn99g>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 11:41:59 -0000

--001a113ac5b6a124530513c1d511
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 8:33 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> A prefixlen for that address is required in order to behave and determine
> neighbordhood relationships ("on-link determination RFC4861")


No. What is required to determine which nodes are directly reachable on
link-via neighbour discovery is not the prefix length of the address. What
is required is *an on-link prefix*.

The prefix is not required to be associated with the address, though some
implementations may couple the two together.

If the destination address matches one of the on-link prefixes,
communication happens directly, via ND. If it does not, communication must
happen through a router.

and optimizations such as reducing search times and routing table sizes.
> An implicit prefixlen is valued at 128 on some node user interface, and 64
> on another node user interface.  An explicit prefixlen may be specified by
> RA.
>

No. An RA may specify an on-link prefix. It does not specify the prefix
length of any addresses.

--001a113ac5b6a124530513c1d511
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 8:33 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petr=
escu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rg=
b(204,204,204);border-left-style:solid;padding-left:1ex">A prefixlen for th=
at address is=C2=A0required in order to behave and determine neighbordhood =
relationships (&quot;on-link determination RFC4861&quot;)</blockquote><div>=
<br></div><div>No. What is required to determine which nodes are directly r=
eachable on link-via neighbour discovery is not the prefix length of the ad=
dress. What is required is *an on-link prefix*.</div><div><br></div><div>Th=
e prefix is not required to be associated with the address, though some imp=
lementations may couple the two together.<br></div><div><br></div><div><div=
 style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;=
font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:nor=
mal;line-height:normal;text-align:start;text-indent:0px;text-transform:none=
;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">If =
the destination address matches one of the on-link prefixes, communication =
happens directly, via ND. If it does not, communication must happen through=
 a router.</div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204)=
;border-left-style:solid;padding-left:1ex">and optimizations such as reduci=
ng search times and routing table sizes.=C2=A0 An implicit prefixlen is val=
ued at 128 on some node user interface, and 64 on another node user interfa=
ce.=C2=A0 An explicit prefixlen may be specified by RA.<br></blockquote><di=
v><br></div><div>No. An RA may specify an on-link prefix. It does not speci=
fy the prefix length of any addresses.</div></div></div></div>

--001a113ac5b6a124530513c1d511--


From nobody Wed Apr 15 05:04:51 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9032D1A88B6 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 PemtrGyg-8G4 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:04:48 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED89F1A88B3 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 05:04:47 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FC4jPD002560; Wed, 15 Apr 2015 14:04:45 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 604A1203FB8; Wed, 15 Apr 2015 14:05:59 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 5407C203E36; Wed, 15 Apr 2015 14:05:59 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FC4gxf002086; Wed, 15 Apr 2015 14:04:44 +0200
Message-ID: <552E53DA.3@gmail.com>
Date: Wed, 15 Apr 2015 15:04:42 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com> <552E40E9.7040203@gmail.com> <62377F15-094C-4D99-BB43-6F03B7563AA1@thehobsons.co.uk> <552E4C6E.1040204@gmail.com> <CAKD1Yr06RVriDi=PZkveziSOXM95HrW+2PE_5wHdVcr2XGb64g@mail.gmail.com>
In-Reply-To: <CAKD1Yr06RVriDi=PZkveziSOXM95HrW+2PE_5wHdVcr2XGb64g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/aKv_MSuTy0JhoRZTq4yi_FIcP1o>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 12:04:49 -0000

Lorenzo - I am trying to understant you to improve text.

Le 15/04/2015 14:41, Lorenzo Colitti a Ã©crit :
> On Wed, Apr 15, 2015 at 8:33 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>     A prefixlen for that address is required in order to behave and
>     determine neighbordhood relationships ("on-link determination RFC4861")
>
>
> No. What is required to determine which nodes are directly reachable
> on link-via neighbour discovery is not the prefix length of the
> address. What is required is *an on-link prefix*.
>
> The prefix is not required to be associated with the address, though
>  some implementations may couple the two together.

Do you think a prefix that is not associated with the address will help
on-link determination?

> If the destination address matches one of the on-link prefixes,
> communication happens directly, via ND.

Dont you think it is not necessary that a plen (be it 128) be associated 
with that address
(not the plen of the onlink prefix) in order to realize that (mis)match 
operation?  Or you think that plen (128) is not necessary?

> If it does not, communication
> must happen through a router.
>
>     and optimizations such as reducing search times and routing table
>     sizes.  An implicit prefixlen is valued at 128 on some node user
>     interface, and 64 on another node user interface.  An explicit
>     prefixlen may be specified by RA.
>
>
> No. An RA may specify an on-link prefix. It does not specify the prefix
> length of any addresses.

Ok.

Alex


From nobody Wed Apr 15 05:40:56 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 563BC1A8ADE for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 c_C_siBDWfOf for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:40:54 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD7331A8AD7 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 05:40:53 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FCeooT016166; Wed, 15 Apr 2015 14:40:50 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D2F5D201A16; Wed, 15 Apr 2015 14:42:04 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B6EAD205923; Wed, 15 Apr 2015 14:42:04 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FCelFW007977; Wed, 15 Apr 2015 14:40:49 +0200
Message-ID: <552E5C4F.1030504@gmail.com>
Date: Wed, 15 Apr 2015 15:40:47 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com>
In-Reply-To: <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SeItyVuXjq4KSwZCMGJsrRLxDhU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 12:40:55 -0000

Le 15/04/2015 14:39, Ted Lemon a Ã©crit :
> On Apr 15, 2015, at 6:33 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> BEfore answering that - do we agree that the plen is mandatory?
>
> No.   All you need is a default route.   Prefix length is optional.
>
>
>

Ok, that's an exception that should be mentioned.

(but even with the default route there is an address and an associated
  plen - ::/0 - the '::' and the '/0' _are_ specified in RFC and are not
  assumed differently by different implementations, like they were in
  the past when the default route was 2000::/3 by some implementations.)

Alex



From nobody Wed Apr 15 05:45:15 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35A2D1B33FB for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Jf7f-dN-zfPe for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:45:12 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 45F0B1B33F9 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 05:45:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id B6959DA019D; Wed, 15 Apr 2015 12:45:11 +0000 (UTC)
Received: from [10.0.20.157] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 15 Apr 2015 05:45:05 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <552E5C4F.1030504@gmail.com>
Date: Wed, 15 Apr 2015 08:45:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/0T95fVyrTgw_-tjd-7VXtSsZfao>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 12:45:14 -0000

On Apr 15, 2015, at 8:40 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
>> No.   All you need is a default route.   Prefix length is optional.
>=20
> Ok, that's an exception that should be mentioned.

No, it's not an exception.   It's the point: prefix and IP address are =
orthogonal.   Unrelated.   There is no connection between the two.   =
Maybe you have prefixes, maybe you don't.   Maybe you have an IP address =
in those prefixes, maybe you don't.   This whole conversation is based =
on the idea that there is some definite connection between an IP address =
and an on-link prefix, and that is simply not the case.


From nobody Wed Apr 15 05:48:08 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2FA31AD0D3 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 M6avpyK53pmA for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:48:05 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16DB71B3402 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 05:48:03 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FCm1Nd019408; Wed, 15 Apr 2015 14:48:01 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E0539205958; Wed, 15 Apr 2015 14:49:15 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C5C2520599D; Wed, 15 Apr 2015 14:49:15 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FClusL001265; Wed, 15 Apr 2015 14:48:00 +0200
Message-ID: <552E5DFC.6000306@gmail.com>
Date: Wed, 15 Apr 2015 15:47:56 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com>
In-Reply-To: <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/PvSctNJTX3ic05oSJNx5AOoj3M8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 12:48:06 -0000

Le 15/04/2015 15:45, Ted Lemon a Ã©crit :
> On Apr 15, 2015, at 8:40 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>>> No.   All you need is a default route.   Prefix length is
>>> optional.
>>
>> Ok, that's an exception that should be mentioned.
>
> No, it's not an exception.   It's the point: prefix and IP address
> are orthogonal.   Unrelated.   There is no connection between the
> two.   Maybe you have prefixes, maybe you don't.   Maybe you have an
> IP address in those prefixes, maybe you don't.   This whole
> conversation is based on the idea that there is some definite
> connection between an IP address and an on-link prefix, and that is
> simply not the case.

Ted - is the plen of the default route specified?

Alex

>
>
>



From nobody Wed Apr 15 05:55:52 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 586581B33FD for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 9VYiTypEOCqe for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 05:55:49 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 844A61A8A94 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 05:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1708; q=dns/txt; s=iport; t=1429102549; x=1430312149; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=CTcxjMSGSbqM5hT1ApwIGy0rLF+hiilsDMDtDwS5ZR8=; b=KyZuSonSFSd9sMIA+0hTD6YaXIIDRskZiQdFtDASkxPkwV3YhC7uaxbc cKPC8ydTRlcyQA52PwvL1xuP+TAF24r1zIQDmcQBEVFYF+LOEpIqkopVC znBY2QQhsGOqSpMP9mRu3lNmUZQREyQyuC/0rVD8LEYLI4EK3iIEbQk3j o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BPBQDLXi5V/4cNJK1cgwxSXIMVxBgKhgMCHIEbTAEBAQEBAX6EIAEBAQMBAQEBMToLBQsCAQgYBCgCAh8GCyUCBA4FiBYDCQgNkUqcfAiQVQ2FRwEBAQEBAQEBAQEBAQEBAQEBAQEBARMEgR2KDoJIghkbB4JkM4EWAQSRDohEgU2ONIY7IoNvb4JDAQEB
X-IronPort-AV: E=Sophos;i="5.11,581,1422921600"; d="scan'208";a="408916756"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-9.cisco.com with ESMTP; 15 Apr 2015 12:55:49 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t3FCtmBl005770 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Apr 2015 12:55:48 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.142]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0195.001; Wed, 15 Apr 2015 07:55:48 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQdxZwgr0/OmkYZEOYe9wn8RRXhJ1ONOWAgAASaACAABEigIAAATAAgAAA0AD//65g6w==
Date: Wed, 15 Apr 2015 12:55:47 +0000
Message-ID: <DC1BDEC7-F279-4C95-83B8-404C512CC0E3@cisco.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com>, <552E5DFC.6000306@gmail.com>
In-Reply-To: <552E5DFC.6000306@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/95u6uT7q8Y_Rnx2Iq3UKQHgUvlI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?gb2312?B?yfHD999f1NU=?= <jinmei@wide.ad.jp>, Ted Lemon <Ted.Lemon@nominum.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 12:55:51 -0000

SXQgaXMgdGhlIGRlZmF1bHQgKGxhc3QgcmVzb3J0KSAuLi4gU28gaXQgd291bGQgYmUgLzAgdG8g
bWF0Y2ggYW55dGhpbmcuIExvbmdlc3QgbWF0Y2ggaXMgdXN1YWxseSB1c2VkIC0gaGVuY2UgaXQg
aXMgdGhlIGxvd2VzdCBwcmlvcml0eSByb3V0ZS4gVGhpcyBpcyBuZXR3b3JraW5nIDEwMS4NCg0K
LSBCZXJuaWUgKGZyb20gaVBhZCkNCg0KPiBPbiBBcHIgMTUsIDIwMTUsIGF0IDg6NDggQU0sIEFs
ZXhhbmRydSBQZXRyZXNjdSA8YWxleGFuZHJ1LnBldHJlc2N1QGdtYWlsLmNvbT4gd3JvdGU6DQo+
IA0KPiBMZSAxNS8wNC8yMDE1IDE1OjQ1LCBUZWQgTGVtb24gYSCopmNyaXQgOg0KPj4gT24gQXBy
IDE1LCAyMDE1LCBhdCA4OjQwIEFNLCBBbGV4YW5kcnUgUGV0cmVzY3UNCj4+IDxhbGV4YW5kcnUu
cGV0cmVzY3VAZ21haWwuY29tPiB3cm90ZToNCj4+Pj4gTm8uICAgQWxsIHlvdSBuZWVkIGlzIGEg
ZGVmYXVsdCByb3V0ZS4gICBQcmVmaXggbGVuZ3RoIGlzDQo+Pj4+IG9wdGlvbmFsLg0KPj4+IA0K
Pj4+IE9rLCB0aGF0J3MgYW4gZXhjZXB0aW9uIHRoYXQgc2hvdWxkIGJlIG1lbnRpb25lZC4NCj4+
IA0KPj4gTm8sIGl0J3Mgbm90IGFuIGV4Y2VwdGlvbi4gICBJdCdzIHRoZSBwb2ludDogcHJlZml4
IGFuZCBJUCBhZGRyZXNzDQo+PiBhcmUgb3J0aG9nb25hbC4gICBVbnJlbGF0ZWQuICAgVGhlcmUg
aXMgbm8gY29ubmVjdGlvbiBiZXR3ZWVuIHRoZQ0KPj4gdHdvLiAgIE1heWJlIHlvdSBoYXZlIHBy
ZWZpeGVzLCBtYXliZSB5b3UgZG9uJ3QuICAgTWF5YmUgeW91IGhhdmUgYW4NCj4+IElQIGFkZHJl
c3MgaW4gdGhvc2UgcHJlZml4ZXMsIG1heWJlIHlvdSBkb24ndC4gICBUaGlzIHdob2xlDQo+PiBj
b252ZXJzYXRpb24gaXMgYmFzZWQgb24gdGhlIGlkZWEgdGhhdCB0aGVyZSBpcyBzb21lIGRlZmlu
aXRlDQo+PiBjb25uZWN0aW9uIGJldHdlZW4gYW4gSVAgYWRkcmVzcyBhbmQgYW4gb24tbGluayBw
cmVmaXgsIGFuZCB0aGF0IGlzDQo+PiBzaW1wbHkgbm90IHRoZSBjYXNlLg0KPiANCj4gVGVkIC0g
aXMgdGhlIHBsZW4gb2YgdGhlIGRlZmF1bHQgcm91dGUgc3BlY2lmaWVkPw0KPiANCj4gQWxleA0K
PiANCj4+IA0KPj4gDQo+PiANCj4gDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPiBkaGN3ZyBtYWlsaW5nIGxpc3QNCj4gZGhjd2dAaWV0Zi5v
cmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaGN3Zw0K


From nobody Wed Apr 15 06:29:47 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B69D1A90B4 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 pb7hAhAR1ifU for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:29:45 -0700 (PDT)
Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2EC41A00A7 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 06:29:44 -0700 (PDT)
Received: by ykft189 with SMTP id t189so589764ykf.1 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 06:29:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=h47H7iNhaUB1NDHLpW1h3Du03/V59ban8K1FphffsHw=; b=Feh4R5lXzcRwbUc/zyBoolwVvRfr7AfiCRDAJoHbEspKzKRzTl8GqLJroYUnUqr0kQ VOtD0qixldasF0rydxIZi6wLRPsr7ogEeAxlQ4wXxYD3Z5pUOrZMNP0JmFYxbqrcnn8e 7hoL8t8WQbKHRfIduyHeY/0QLUqS5PMcrmyYKapb8Ql9bQFvzROe16wA04eKrzDpkMUB +haJG2ZIx3SN/X7hdYH2RYJX/j7RkSkr9PLxF1LXCtFG5eLUtBJ5aElFER/oyKLNKoSz r5Qe3bmamOm3/wIis6uzCc2wrPhac5AQQT7jb3YLOK2ecu8/FonFIDXTAZOiOOowXMtl xlOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=h47H7iNhaUB1NDHLpW1h3Du03/V59ban8K1FphffsHw=; b=VTflNFtzq8zFc9CYjZd+DU6cdSdy0Z9F8UDGjypK8EYOyq5G5VE6HDCGVKgQ5V7whe /QzvtYU2CX4n3xBffZDY2VEKlXqz/s3tGto18kc+SMQe6Mq0SUvfWddqLtK7AgnAzxzT 8y+5812sgpiMtz1zNBP5kEwUkvuRSrf8vdDBBi8EEmsn2EZvs4n4mESk41pEcZooajcI uuqF3dOgQJP5WrDG0e+90K5vhhL561Sv4AUYIoYHr4PStGOPLJ3afNwV8RGTM8DrL21n uyY9/QhRk4pImEdEcw3hy0Wz75EOM4YDxxAuKbILaspmiFX1zr8YW47SKHJdG5BhZXXL eSgw==
X-Gm-Message-State: ALoCoQlApJJuoP+cRcw2ci+hVDn2E4Y05awplfIXFPkPrLJC4ehGnl0x3i7P3ePAlFmggleEXMAN
X-Received: by 10.50.137.97 with SMTP id qh1mr31398874igb.39.1429104584227; Wed, 15 Apr 2015 06:29:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 15 Apr 2015 06:29:23 -0700 (PDT)
In-Reply-To: <552E53DA.3@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <CAKD1Yr3ze5f3WJfJgnrJ5HLYStbyi3UAodYsVa1-3=rqMc0G0Q@mail.gmail.com> <552E40E9.7040203@gmail.com> <62377F15-094C-4D99-BB43-6F03B7563AA1@thehobsons.co.uk> <552E4C6E.1040204@gmail.com> <CAKD1Yr06RVriDi=PZkveziSOXM95HrW+2PE_5wHdVcr2XGb64g@mail.gmail.com> <552E53DA.3@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 22:29:23 +0900
Message-ID: <CAKD1Yr3_33BNY=Pdxd2VT5OxmqRdH8-RCOnKJJfdcZpyu0CJzQ@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3f1f41738560513c357eb
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/9Clo_D8qIzyfykx17Gg_ci60Y-8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 13:29:46 -0000

--001a11c3f1f41738560513c357eb
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 9:04 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

>  you think a prefix that is not associated with the address will help
>>
> on-link determination?


On-link determination is independent from the IP addresses on the system.
Whether an address is on-link or not is a function of the destination
prefix the address is in, regardless of what IP addresses you have.
Example: you can have prefix 2001:db8::/64 be on-link on a particular
interface, but you might only have a link-local address on that interface.

 If the destination address matches one of the on-link prefixes,
>> communication happens directly, via ND.
>>
>
> Dont you think it is not necessary that a plen (be it 128) be associated
> with that address
> (not the plen of the onlink prefix) in order to realize that (mis)match
> operation?  Or you think that plen (128) is not necessary?


No, whether a specific address is on-link or not does not depend on what IP
addresses you have.

--001a11c3f1f41738560513c357eb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 9:04 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.petr=
escu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">=C2=A0you think a prefix that is not associated =
with the address will help<br></blockquote>
on-link determination?</blockquote><div><br></div><div>On-link determinatio=
n is independent from the IP addresses on the system. Whether an address is=
 on-link or not is a function of the destination prefix the address is in, =
regardless of what IP addresses you have. Example: you can have prefix 2001=
:db8::/64 be on-link on a particular interface, but you might only have a l=
ink-local address on that interface.</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If the destination address matches one of the on-link prefixes,<br>
communication happens directly, via ND.<br>
</blockquote>
<br></span>
Dont you think it is not necessary that a plen (be it 128) be associated wi=
th that address<br>
(not the plen of the onlink prefix) in order to realize that (mis)match ope=
ration?=C2=A0 Or you think that plen (128) is not necessary?</blockquote><d=
iv><br></div><div>No, whether a specific address is on-link or not does not=
 depend on what IP addresses you have.</div></div></div></div>

--001a11c3f1f41738560513c357eb--


From nobody Wed Apr 15 06:30:37 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AF0B1B3489 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eOhDdljsWJDo for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:30:35 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 2D10A1A00A7 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 06:30:35 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id E53E4DA01E1; Wed, 15 Apr 2015 13:30:34 +0000 (UTC)
Received: from [10.0.20.157] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 15 Apr 2015 06:30:28 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <552E5DFC.6000306@gmail.com>
Date: Wed, 15 Apr 2015 09:30:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Y_CdCeeoKJK4rpnHIlxVbkR10s8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 13:30:36 -0000

On Apr 15, 2015, at 8:47 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
> Ted - is the plen of the default route specified?

Are you kidding?


From nobody Wed Apr 15 06:34:33 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CCC31B34B4 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 S-LbXmUghxfT for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:34:30 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E59B1B34A1 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 06:34:29 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FDYQP4011070; Wed, 15 Apr 2015 15:34:26 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 88A952059F7; Wed, 15 Apr 2015 15:35:40 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 6EFBC2058CB; Wed, 15 Apr 2015 15:35:40 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FDYNEQ005397; Wed, 15 Apr 2015 15:34:25 +0200
Message-ID: <552E68DF.5050102@gmail.com>
Date: Wed, 15 Apr 2015 16:34:23 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com> <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com>
In-Reply-To: <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/U5Icp6kaqycSgaZhRHMq8w9M6YU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 13:34:31 -0000

Le 15/04/2015 16:30, Ted Lemon a Ã©crit :
> On Apr 15, 2015, at 8:47 AM, Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>> Ted - is the plen of the default route specified?
>
> Are you kidding?

No, sorry, and not trolling.

The plen associated with the address of the next-hop gw in the rt table 
_is_ specified: it is /0.  Before being specified various
implementations of linux and bsd were doing various things with 
2000::/3.  There are reasons for /3 instead of /0, at least because all 
addresses currently specified by the IPv6 Addressing Architecture RFC 
says that all addresses start with binary 001.

Alex

>
>
>



From nobody Wed Apr 15 06:38:19 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7554E1B34D5 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 h2RVPlNq_gv2 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:38:17 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4179D1B34D3 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 06:38:04 -0700 (PDT)
Received: by obbfy7 with SMTP id fy7so20142539obb.2 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 06:38:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bvHwbbM1NN9ji4Okl5k0wSzmbVR3Id25e4RHHKxITeM=; b=ROg60UXe2+9Z28zPOsYvWDeBjhzKz6xMK6475iGSHTQzPwvuXqbqylQYVksAzlwn+R gqyQg6BPl0FsJb0gbRloL+mdlUpemAxSB0vq5Zs8E0M8aMA/DCPBMARtznzibZlPkk6d jiHtHSyR0PMTX7ORwWDtT6baq7sxINvquCVqyrWIMOjDi3wx/alzavyViHTlZK8XgJA6 DWol3JZZijnK7wYjgmvtvpnShol6bSx9ozMaMiLnUJttOikM9e9CsgjLT0gZOGYDNQR6 L2f3b/kJf6YuZsZcar8hfT02N9/EIGGr6SDySHZeYN2dO2dkripj7gg0mYwmASh8NQOB CEGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=bvHwbbM1NN9ji4Okl5k0wSzmbVR3Id25e4RHHKxITeM=; b=afIVojLCoDUpZMV57fS6bmkjCEBihnb1G11JpHDneJrw3PCJnj39sUNwz/hue8bu/G a7Bq+2IF9ZssbguwOPBD0hpmJxgspmvFmpi6vbttOCTu+KZ0syLionVSHWNWngHH6aY8 mhlDgl1HbOdbmUGGtZkt+WG8OA/KXfEfP3vDI9EeU4rT8cw1TVdh7VUCslQB7hzGpLvT ntqvUWp+Lva3YrL1yRQ32eHlZQCxFKcwXT53OKT91AYCMg4/TIvUywO+NZDy+3rHAe/O +rE/yqSKDGvnlWUaFcSLhs9QNAaBl1UP0ByX0AOZqm8z1Qet6XxWTLrCWbv87osIKHDN ChWA==
X-Gm-Message-State: ALoCoQlZpt3LpeLWDmRRh2+SNlxMRS68RnTQpF/VkJD6QpuieaBBSDZ+TnMsT/3RNgQ6VyZXmKD1
X-Received: by 10.107.130.145 with SMTP id m17mr34655443ioi.89.1429105044633;  Wed, 15 Apr 2015 06:37:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 15 Apr 2015 06:37:03 -0700 (PDT)
In-Reply-To: <552E68DF.5050102@gmail.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com> <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com> <552E68DF.5050102@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 22:37:03 +0900
Message-ID: <CAKD1Yr0d7hgVRruRNrwC2W7_2sP-h-3t8w1Y89vcPf15jXaMrQ@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ed02a8872f40513c3727d
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/tfdYU7tsWpOP2hssjXWt1o8nj44>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ted Lemon <Ted.Lemon@nominum.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 13:38:18 -0000

--001a113ed02a8872f40513c3727d
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 10:34 PM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> The plen associated with the address of the next-hop gw in the rt table
> _is_ specified: it is /0.  Before being specified various


That's irrelevant. The default route is not on link.

--001a113ed02a8872f40513c3727d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 10:34 PM, Alexandru Petrescu <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:alexandru.petrescu@gmail.com" target=3D"_blank">alexandru.pet=
rescu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The=
 plen associated with the address of the next-hop gw in the rt table _is_ s=
pecified: it is /0.=C2=A0 Before being specified various</blockquote><div><=
br></div><div>That&#39;s irrelevant. The default route is not on link.=C2=
=A0</div></div></div></div>

--001a113ed02a8872f40513c3727d--


From nobody Wed Apr 15 06:42:18 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E11751B34E5 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 rdEnyfNy_CMe for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:42:14 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64C411A905E for <dhcwg@ietf.org>; Wed, 15 Apr 2015 06:42:14 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FDgA4X014395; Wed, 15 Apr 2015 15:42:10 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D1B552059DE; Wed, 15 Apr 2015 15:43:24 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B5312203E36; Wed, 15 Apr 2015 15:43:24 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FDg6T8016867; Wed, 15 Apr 2015 15:42:09 +0200
Message-ID: <552E6AAE.7060907@gmail.com>
Date: Wed, 15 Apr 2015 16:42:06 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com> <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com> <552E68DF.5050102@gmail.com> <CAKD1Yr0d7hgVRruRNrwC2W7_2sP-h-3t8w1Y89vcPf15jXaMrQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr0d7hgVRruRNrwC2W7_2sP-h-3t8w1Y89vcPf15jXaMrQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/NFCR9NuUhvknuxYyYO99xsc0-YI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ted Lemon <Ted.Lemon@nominum.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 13:42:18 -0000

Le 15/04/2015 16:37, Lorenzo Colitti a Ã©crit :
> On Wed, Apr 15, 2015 at 10:34 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>     The plen associated with the address of the next-hop gw in the rt
>     table _is_ specified: it is /0.  Before being specified various
>
>
> That's irrelevant. The default route is not on link.

Right, the prefix of the default route is not on link.

Alex



From nobody Wed Apr 15 06:53:33 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB6081B3495 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 XPXWJ3Er70AT for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 06:53:30 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 009841A923E for <dhcwg@ietf.org>; Wed, 15 Apr 2015 06:53:29 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FDrRK5019786 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 15:53:27 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 46A88205A66 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 15:54:42 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3E962205A05 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 15:54:42 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FDrPKg002195 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 15:53:27 +0200
Message-ID: <552E6D55.4030800@gmail.com>
Date: Wed, 15 Apr 2015 16:53:25 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com> <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com> <552E68DF.5050102@gmail.com>
In-Reply-To: <552E68DF.5050102@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jMXUb5-xkp6Qb3-Nvmvc8OMdimM>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 13:53:32 -0000

Le 15/04/2015 16:34, Alexandru Petrescu a Ã©crit :
> Le 15/04/2015 16:30, Ted Lemon a Ã©crit :
>> On Apr 15, 2015, at 8:47 AM, Alexandru Petrescu
>> <alexandru.petrescu@gmail.com> wrote:
>>> Ted - is the plen of the default route specified?
>>
>> Are you kidding?
>
> No, sorry, and not trolling.
>
> The plen associated with the address of the next-hop gw in the rt
> table _is_ specified: it is /0.

(I meant the plen of the prefix, not of the address of the next-hop).

Alex

   Before being specified various
> implementations of linux and bsd were doing various things with
> 2000::/3.  There are reasons for /3 instead of /0, at least because
> all addresses currently specified by the IPv6 Addressing Architecture
> RFC says that all addresses start with binary 001.
>
> Alex
>
>>
>>
>>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg



From nobody Wed Apr 15 07:08:35 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8761B1B3559 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 07:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 zzSRUBor-Y7O for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 07:08:32 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 535291B3570 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 07:08:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=385; q=dns/txt; s=iport; t=1429106885; x=1430316485; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=3Jl3maykYfiy9LoNY9efmwz7pvKjyh3sduMIjQ0Lmd4=; b=kDSWECoJz1x4DoTngztILyBW7Wb9CxlseWYYycqcf4oumplyezMB2DjI 6Wgh/H2yOYQI3WFBVpFZ+56wyrCdAstm3WlBLcx89ZQy2g7ep9Svc5DDE KucOiAvvZzg/XGV5aTljBmZjZIofdy4YpOhBk2ChtzmGgIXigHLCDYKgU 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CEBAAScC5V/4QNJK1cgwyBLgXFXQmHUgKBOTgUAQEBAQEBAX2EIQEBBCkRNBsCAQIGNhAyJQIEARKIKsUdAQEBAQEBAQMBAQEBAQEBG4srhQOELQEEhFyMMogQggGBHYM3jE6DTSKDb2+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,582,1422921600"; d="scan'208";a="141426712"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-1.cisco.com with ESMTP; 15 Apr 2015 14:08:04 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t3FE83sT016564 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Apr 2015 14:08:03 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.142]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Wed, 15 Apr 2015 09:08:03 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQdxZwgr0/OmkYZEOYe9wn8RRXhJ1ONOWAgAASaACAABEigIAAATAAgAAA0ACAAAvegIAAARyAgAAFUYD//8EDAA==
Importance: high
X-Priority: 1
Date: Wed, 15 Apr 2015 14:08:03 +0000
Message-ID: <D153E82C.CAD5%volz@cisco.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com> <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com> <552E68DF.5050102@gmail.com> <552E6D55.4030800@gmail.com>
In-Reply-To: <552E6D55.4030800@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.9.150325
x-originating-ip: [10.98.1.204]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <38665EB0EE68D84CA5A89F5FAC04FA26@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/2ebDxWEJQ2UL-f-IuwFiDrZT5Aw>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 14:08:34 -0000

Hi:

Please remove dhcwg@ietf.org if you want to continue this discussion
privately. But it is time to stop this useless debate on the dhcwg mailing
list.

If there is further discussion on this topic that includes the dhcwg, I
will moderate future posts from the senders for a period (and block any on
this topic).

Thank you for your attention to this matter.

- Bernie


From nobody Wed Apr 15 07:11:06 2015
Return-Path: <lorenzo@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B10241B3524 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 07:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 Inbr95wM8xVz for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 07:11:03 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDF081A9140 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 07:11:03 -0700 (PDT)
Received: by oign205 with SMTP id n205so23637541oig.2 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 07:11:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=euTyS5BwIn1FU80UKdR3Pkd/KzNAUm6KC9DKgdh/Mhc=; b=euE44dJWDC9vmzhHcLf7ZQKj+Pjfg+7s5m8TR8EZUYIT2oMzVrs9V7vuIzfwS1oz3Q g+gqBrYwNp/+uWQngiGujgfzWkmwbkMfwOlzxC2A4+mPl9/RiDl9gnL+B9iyQgqDGQDT yf9lcd7OzqeXC7rbypfQlg2fzDt8ydQEpMG5d7g1jKxOJzqkHV2VSM5o+kqYBGUjpNvk noYflCDzJX0baJbO9GdjXpJbwFbelT0IZggD7vGM+7ToSN8lE9IsS7zZ6H/gE63Mitn+ 4WSsYrpwHQZJTMkRP85LbVTaESmRcWyQFkbGqLVSdLgZYG+HQXgdM5Y5iHm1LpgGPD37 fsLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=euTyS5BwIn1FU80UKdR3Pkd/KzNAUm6KC9DKgdh/Mhc=; b=VX39p6OdCDXUADPdGe42nGfIy61LZ07EYvSJq4Yg1DjU54sfaIQjAQmxrWpNZVN++W +41k3R90Vkn7oD2P9L2MYyNbkHmLyMpE85dxTt9jIf/QxST9Hmj/0Ps29gQr2oqaVkiE ZxQTnJIDoTOWtOHEOybLYr6HxFRYz9dTdDds1PCxBjzSupHlh6wT6X5SR2E95huw8mF7 t4LO7JSc54KnbRKzO1EZ/vHbUpliT8Ia6KCp9y+ImxZNi/YHcpuBP58vVt9PaqT5eRNV zESi88vXMYLjr+8Tl6kyN5qJFO8fFuku/x6qp2vcH1D7yRZFfmSgmz+Ii8JI20wccHQm RrIg==
X-Gm-Message-State: ALoCoQmyOdcnGD4+6WYOqrh/+jkSqwnBEoCgoznbyw8G7eWTmT1LYJpw2C/jcm6+dp9ODlOuPrPD
X-Received: by 10.50.137.97 with SMTP id qh1mr31647509igb.39.1429107035577; Wed, 15 Apr 2015 07:10:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.73.2 with HTTP; Wed, 15 Apr 2015 07:10:14 -0700 (PDT)
In-Reply-To: <D153E82C.CAD5%volz@cisco.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com> <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com> <552E68DF.5050102@gmail.com> <552E6D55.4030800@gmail.com> <D153E82C.CAD5%volz@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Apr 2015 23:10:14 +0900
Message-ID: <CAKD1Yr0=vgpTdm6hLnd=bO_MKfiXYugHDQ5TFW8T7VCiN_Q1xw@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c3f1f433c6800513c3e92c
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/tY0KVnzGQR-etVrApSEwjgaS-Ng>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 14:11:04 -0000

--001a11c3f1f433c6800513c3e92c
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 15, 2015 at 11:08 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> Please remove dhcwg@ietf.org if you want to continue this discussion
> privately. But it is time to stop this useless debate on the dhcwg mailing
> list.


Acknowledged.

Bernie, do you know what happened to the suggested text that was posted
reams of messages back? Do we need to salvage it and move it to another
thread?

--001a11c3f1f433c6800513c3e92c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 15, 2015 at 11:08 PM, Bernie Volz (volz) <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">Please remove <a href=3D"mailto=
:dhcwg@ietf.org">dhcwg@ietf.org</a> if you want to continue this discussion=
<br>
privately. But it is time to stop this useless debate on the dhcwg mailing<=
br>
list.</blockquote><div><br></div><div>Acknowledged.</div><div><br></div><di=
v>Bernie, do you know what happened to the suggested text that was posted r=
eams of messages back? Do we need to salvage it and move it to another thre=
ad?</div></div></div></div>

--001a11c3f1f433c6800513c3e92c--


From nobody Wed Apr 15 07:15:34 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24C7A1B3565 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 07:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 ncz6WK-ooCrH for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 07:15:28 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAD3F1B3560 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 07:15:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3829; q=dns/txt; s=iport; t=1429107327; x=1430316927; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=7/lGQqEIFLHFQslzPonjUb7H+T71hM/IeduHPx4RUl4=; b=RhKAVdD/Wjw1Wg758s6ou7PVWKjN1wRXJ54GxivSGePwM9biJPggJKhW MIQut1u9+/m6y+UdWsznZD5px46clqjFdK7k6Z+rgwgprY9QqunCJJ7rE +7phbiAhoEhEaakDnlLCFXs9fwaTA7sY0MyE3vDLTh/NS0SmWzLkPVRvr Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DpBQAEci5V/4sNJK1cgkVHUlwFxTMqCYFPhgMCgTo4FAEBAQEBAQF9hCABAQEEbgsQAgEIBA0DAQIoByERFAkIAgQOBYgWAxENvz0NhUcBAQEBAQEBAwEBAQEBAQEBARmLK4JIgW80EQeELQWBTI0oghqDeYRLgU2BHTqCfYlghjsig29vAYFDfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,582,1422921600";  d="scan'208,217";a="141446400"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-3.cisco.com with ESMTP; 15 Apr 2015 14:15:06 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t3FEF6QA024204 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Apr 2015 14:15:06 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.142]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Wed, 15 Apr 2015 09:15:06 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Lorenzo Colitti <lorenzo@google.com>
Thread-Topic: [dhcwg] Microphone comment about DHCPv6 address prefix length
Thread-Index: AQHQdxZwgr0/OmkYZEOYe9wn8RRXhJ1ONOWAgAASaACAABEigIAAATAAgAAA0ACAAAvegIAAARyAgAAFUYD//8EDAIAAQ7AA//++RwA=
Date: Wed, 15 Apr 2015 14:15:05 +0000
Message-ID: <D153EA2B.CAE5%volz@cisco.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <4A782B67-EFD2-4067-AF29-4BCCFDD51009@gmail.com> <55254F6A.4020005@gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com> <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com> <552E68DF.5050102@gmail.com> <552E6D55.4030800@gmail.com> <D153E82C.CAD5%volz@cisco.com> <CAKD1Yr0=vgpTdm6hLnd=bO_MKfiXYugHDQ5TFW8T7VCiN_Q1xw@mail.gmail.com>
In-Reply-To: <CAKD1Yr0=vgpTdm6hLnd=bO_MKfiXYugHDQ5TFW8T7VCiN_Q1xw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.9.150325
x-originating-ip: [10.98.1.204]
Content-Type: multipart/alternative; boundary="_000_D153EA2BCAE5volzciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/o2Gv-VFP6ZHkKKYYg5s9fh4arBQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 14:15:34 -0000

--_000_D153EA2BCAE5volzciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

See http://trac.tools.ietf.org/group/dhcpv6bis/ticket/68.

- Bernie

From: Lorenzo Colitti <lorenzo@google.com<mailto:lorenzo@google.com>>
Date: Wednesday, April 15, 2015 at 10:10 AM
To: Bernie Volz <volz@cisco.com<mailto:volz@cisco.com>>
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com<mailto:alexandru.petre=
scu@gmail.com>>, "dhcwg@ietf.org<mailto:dhcwg@ietf.org>" <dhcwg@ietf.org<ma=
ilto:dhcwg@ietf.org>>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length

On Wed, Apr 15, 2015 at 11:08 PM, Bernie Volz (volz) <volz@cisco.com<mailto=
:volz@cisco.com>> wrote:
Please remove dhcwg@ietf.org<mailto:dhcwg@ietf.org> if you want to continue=
 this discussion
privately. But it is time to stop this useless debate on the dhcwg mailing
list.

Acknowledged.

Bernie, do you know what happened to the suggested text that was posted rea=
ms of messages back? Do we need to salvage it and move it to another thread=
?

--_000_D153EA2BCAE5volzciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <38358A2ABFD586498402FE63C4461B16@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>See&nbsp;<a href=3D"http://trac.tools.ietf.org/group/dhcpv6bis/ticket/=
68">http://trac.tools.ietf.org/group/dhcpv6bis/ticket/68</a>.</div>
<div><br>
</div>
<div>- Bernie</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Lorenzo Colitti &lt;<a href=
=3D"mailto:lorenzo@google.com">lorenzo@google.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, April 15, 2015 at =
10:10 AM<br>
<span style=3D"font-weight:bold">To: </span>Bernie Volz &lt;<a href=3D"mail=
to:volz@cisco.com">volz@cisco.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Alexandru Petrescu &lt;<a href=
=3D"mailto:alexandru.petrescu@gmail.com">alexandru.petrescu@gmail.com</a>&g=
t;, &quot;<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>&quot; &lt;<a=
 href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [dhcwg] Microphone com=
ment about DHCPv6 address prefix length<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">On Wed, Apr 15, 2015 at 11:08 PM, Bernie Volz (v=
olz) <span dir=3D"ltr">
&lt;<a href=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&=
gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Please remove <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a> if you w=
ant to continue this discussion<br>
privately. But it is time to stop this useless debate on the dhcwg mailing<=
br>
list.</blockquote>
<div><br>
</div>
<div>Acknowledged.</div>
<div><br>
</div>
<div>Bernie, do you know what happened to the suggested text that was poste=
d reams of messages back? Do we need to salvage it and move it to another t=
hread?</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D153EA2BCAE5volzciscocom_--


From nobody Wed Apr 15 07:16:44 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF6B01A910B for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 07:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 NU-AEEWmdo6r for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 07:16:42 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C50201A8824 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 07:16:41 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3FEGa9p025714; Wed, 15 Apr 2015 16:16:36 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BFC8E205AAB; Wed, 15 Apr 2015 16:17:50 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id AD26B205A05; Wed, 15 Apr 2015 16:17:50 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.190]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3FEGXLk006459; Wed, 15 Apr 2015 16:16:35 +0200
Message-ID: <552E72C1.3080608@gmail.com>
Date: Wed, 15 Apr 2015 17:16:33 +0300
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr2y=BzJGpfgWOMvHvRzsUsGrE1G-xz4ZSZREXd1nHK4-Q@mail.gmail.com> <20150409.081427.74687401.sthaug@nethelp.no> <4EAA933E-365A-4542-AECA-552081DA0FE3@thehobsons.co.uk> <552641FF.2070202@gmail.com> <686DB635-0612-4D76-9E5B-C64950F3EBD0@thehobsons.co.uk> <5526612A.7000502@gmail.com> <4661AA65-1A71-4AA0-AED2-1E951D17C6D4@gmail.com> <5526658C.8000708@gmail.com> <CAJE_bqeh+=5yxvj-m7ZjFxN__bLr9F8y+qvZU_h-fO0Uh0PHxQ@mail.gmail.com> <552D6DF6.5050905@gmail.com> <CAKD1Yr3ZHnv62a5HyMoUo59FXLGGKFW5JnnyjTkBLEH2R2f-tQ@mail.gmail.com> <552E3E7F.7060702@gmail.com> <D6BE26C0-2183-4CEB-9CF7-4B59F247D7C5@nominum.com> <552E5C4F.1030504@gmail.com> <30491AD8-7701-4FCD-84AC-372A9871496A@nominum.com> <552E5DFC.6000306@gmail.com> <A4513938-C6FE-4559-A9D4-45CC7AA1C976@nominum.com> <552E68DF.5050102@gmail.com> <552E6D55.4030800@gmail.com> <D153E82C.CAD5%volz@cisco.com> <CAKD1Yr0=vgpTdm6hLnd=bO_MKfiXYugHDQ5TFW8T7VCiN_Q1xw@mail.gmail.com> <D153EA2B.CAE5%volz@cisco.com>
In-Reply-To: <D153EA2B.CAE5%volz@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/wI_8B53BltXVGnRTTrR9ihy0dPU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 14:16:43 -0000

I agree this is not a 3315bis issue.

Alex

Le 15/04/2015 17:15, Bernie Volz (volz) a écrit :
> See http://trac.tools.ietf.org/group/dhcpv6bis/ticket/68.
>
> - Bernie
>
> From: Lorenzo Colitti <lorenzo@google.com <mailto:lorenzo@google.com>>
> Date: Wednesday, April 15, 2015 at 10:10 AM
> To: Bernie Volz <volz@cisco.com <mailto:volz@cisco.com>>
> Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com
> <mailto:alexandru.petrescu@gmail.com>>, "dhcwg@ietf.org
> <mailto:dhcwg@ietf.org>" <dhcwg@ietf.org <mailto:dhcwg@ietf.org>>
> Subject: Re: [dhcwg] Microphone comment about DHCPv6 address prefix length
>
> On Wed, Apr 15, 2015 at 11:08 PM, Bernie Volz (volz) <volz@cisco.com
> <mailto:volz@cisco.com>> wrote:
>
>     Please remove dhcwg@ietf.org <mailto:dhcwg@ietf.org> if you want to
>     continue this discussion
>     privately. But it is time to stop this useless debate on the dhcwg
>     mailing
>     list.
>
>
> Acknowledged.
>
> Bernie, do you know what happened to the suggested text that was posted
> reams of messages back? Do we need to salvage it and move it to another
> thread?




From nobody Wed Apr 15 09:35:12 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8250F1B3625 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 09:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 8lZ-XR_7R6H0 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 09:35:08 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 BCC671B3629 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 09:35:05 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YiQHG-0006tL-IU; Wed, 15 Apr 2015 18:35:02 +0200
Message-ID: <552E913E.5080102@si6networks.com>
Date: Wed, 15 Apr 2015 13:26:38 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <55250911.30100@si6networks.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com> <5527FA77.5070301@si6networks.com> <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com> <552C679E.4020305@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA66028@xmb-rcd-x04.cisco.com> <552D6343.9050404@si6networks.com> <CF0CC1A9-8455-41DD-84DD-E0E05895C912@nominum.com>
In-Reply-To: <CF0CC1A9-8455-41DD-84DD-E0E05895C912@nominum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/q_E8hQg5O4WIjhTThSZF066zxiw>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 16:35:10 -0000

On 04/14/2015 10:51 PM, Ted Lemon wrote:
> On Apr 14, 2015, at 2:58 PM, Fernando Gont <fgont@si6networks.com> wrote:
>> Mine is this: the subnet address space is so large that the problem is
>> essentially a birthday paradox.
> 
> That assumes a random distribution.

Random addreses, uniform distribution. And F() provides that.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Apr 15 09:35:17 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 791131B3626 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 09:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 ga2cVae2wL0m for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 09:35:12 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 1F6611B362B for <dhcwg@ietf.org>; Wed, 15 Apr 2015 09:35:12 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YiQHO-0006tc-B4; Wed, 15 Apr 2015 18:35:10 +0200
Message-ID: <552E9307.6010205@si6networks.com>
Date: Wed, 15 Apr 2015 13:34:15 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA32071@xmb-rcd-x04.cisco.com> <CAKD1Yr0ojVmk-ctUO313zvAx01P=B-A2zVuwDm73+dLgVwDLOw@mail.gmail.com> <55250DF2.8050001@si6networks.com> <CAKD1Yr33wFmjjqjYu8YEpqYvnn=kh9oJhe1YAC7UEzacQFBaWg@mail.gmail.com> <55251EFA.4000204@si6networks.com> <CAKD1Yr0XK-DQkcJKwTYmiWzCzZs4pubCme9rAgoZ_ig-P5MgsQ@mail.gmail.com> <55253F14.6000706@si6networks.com> <CAKD1Yr0Q2634Rfw0_9NiU+-S_yfD2RwPs7uPWAbTuOADyx8bHg@mail.gmail.com> <5526B5F9.9090707@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA499A7@xmb-rcd-x04.cisco.com> <5526D45A.9020701@si6networks.com> <CAKD1Yr2g9sc8Y3URBMt=yNkD61-iG37rpNc5ZXJHjLfghD3KJA@mail.gmail.com> <5527FA77.5070301@si6networks.com> <CAKD1Yr3M0gbbbE6a=DfT1SW7jeXoHX1EQMbDagtF-+n13sAQ0w@mail.gmail.com> <552C679E.4020305@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1CA66028@xmb-rcd-x04.cisco.com> <552D6343.9050404@si6networks.com> <CAKD1Yr1v7Rf+uKCcYwsCKkSTuRUegQVMuPDfefR71Xb836LqaA@mail.gmail.com>
In-Reply-To: <CAKD1Yr1v7Rf+uKCcYwsCKkSTuRUegQVMuPDfefR71Xb836LqaA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ZfmOUmXaWCW31aJOObj6I3LyV-Y>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Next step(s) for draft-ietf-dhc-stable-privacy-addresses -> abandon work? / IA_NA applicability
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 16:35:13 -0000

On 04/14/2015 10:09 PM, Lorenzo Colitti wrote:
> On Wed, Apr 15, 2015 at 3:58 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     That is true. In the first version of the I-D we didn't support ranges.
>     Now we do, and we should certainly put a huge warning that the address
>     space should be huge, or things don't work as expected.
> 
> Supporting stateless allocation in anything smaller than a /64 is harmful.
> 
> You are creating the risk that people coming from outdated IPv4
> assumptions will take a /112, think, "That's big enough for everyone,
> right? I only have a few hundred hosts. And I want to limit my subnet
> size to avoid these ND cache DoS attacks I've heard about," and get
> burned by the fact that there's a 50% chance of collision when there are
> 250 hosts in the network. Because your algorithm doesn't support
> collisions well, they'll be completely stuck.

The only reason for which ranges are supported is such that you can
reserve a small part of the address space for static allocations.

Reserving ~100-1000 out of the 2**64 addresses is more than enough for
that purpose, and does not affect the collision rate.



> Before you argue that it makes sense to support stateless allocation
> when the subnet is "large enough" - how large is large enough? People
> used to fully-stateful IPv4 deployments with forced forwarding (e.g.,
> large conference networks that force 1 IPv4 address = 1 MAC address and
> don't use broadcast ARP because the wifi chipset filters it out for
> them) may well do something like /96 (That's large enough, right? It's
> the size of the whole of the IPv4 Internet!) and put 20,000 hosts on it
> and fall over in the same way. Yes - large conferences like MWC do have
> 20k hosts on the same subnet.

Sorry, I don't follow. I never argued in favor of non-/64 subnets. And,
as noted above, the only reason for which our I-D supports ranges is so
that you can reserver a tiny bit of the address space for static
allocations. That's it.



> Also - if you change the range size, do all the addresses change? That
> would make it an even worse idea.

They don't. It's the Prefix that we include in F().

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Apr 15 10:00:24 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501271B2E00 for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 10:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 L9mAwTt6l_Yc for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 10:00:21 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66B5A1B2DFE for <dhcwg@ietf.org>; Wed, 15 Apr 2015 10:00:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7385; q=dns/txt; s=iport; t=1429117221; x=1430326821; h=from:to:subject:date:message-id:mime-version; bh=gkqg+rNin4G99NNdrlUoBcorJ5pLPmUXRHxTxe2xyfQ=; b=IIuf/CfrjUsxCRrWjcuxv9GF8ZH+e3Z+6HCNFMXTh9wPxFPoEYdzZatX C8iX+NLhOG7ULD12v5NUOPWG3hY7rD71zzU8nRh30ysZQX2LkbeDDijQM dLiBetHoYZ9H81haACsljcT0kjiYcJiLftzlBkYwt3h+uz7Ge6R0U+aCS 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AQBQA5mC5V/5hdJa1cgkVHUmHNQAKBO0wBAQEBAQF+hCIBBB0QQR0BKlYmAQQbDIgWn1ilIwEBAQEBAQQBAQEBAQEBG4xogw6DT4EWBY56ghyLNYM4jFeDTSKDb4IzfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,582,1422921600";  d="scan'208,217";a="408980874"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 15 Apr 2015 17:00:13 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t3FH0DH1023921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Wed, 15 Apr 2015 17:00:13 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.142]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Wed, 15 Apr 2015 12:00:13 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Call for Adoption: draft-huitema-dhc-anonymity-profile, ends April 29, 2015
Thread-Index: AdB3nVyi2CTwlN+jTCySs+HRwBxbNQ==
Date: Wed, 15 Apr 2015 17:00:12 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA6909B@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.204]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1CA6909Bxmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/06SQMmMXIgt8GSGDysvRPH-4YWw>
Subject: [dhcwg] Call for Adoption: draft-huitema-dhc-anonymity-profile, ends April 29, 2015
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 17:00:23 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1CA6909Bxmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:



The authors have requested that the working group adopt draft-huitema-dhc-a=
nonymity-profile as a working group work item. The document is the next log=
ical step to address the privacy issues identified in the recently adopted =
draft-ietf-dhc-dhcp-privacy and draft-ietf-dhc-dhcpv6-privacy documents. Wh=
ile not explicitly on the charter, privacy is a major concern within the IE=
TF community. This document "provides guidelines on the composition of DHCP=
 or DHCPv6 requests, designed to minimize disclosure of identifying informa=
tion."



Given the already adopted documents and interest in this work shown at IETF=
-92 (Dallas), the WG co-chairs believe there is consensus to adopt this doc=
ument. We are confirming that consensus on the mailing list.



If you think the WG should NOT adopt this work, please state so (with your =
reasons). Feel free to also express support for adopting this work.



Please respond on or before April 29, 2015.



Thanks!



-          Bernie (& Tomek)

--_000_489D13FBFA9B3E41812EA89F188F018E1CA6909Bxmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:863057409;
	mso-list-type:hybrid;
	mso-list-template-ids:919227648 -2009668410 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hi:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The authors have requested that the working group=
 adopt draft-huitema-dhc-anonymity-profile as a working group work item. Th=
e document is the next logical step to address the privacy issues identifie=
d in the recently adopted draft-ietf-dhc-dhcp-privacy
 and draft-ietf-dhc-dhcpv6-privacy documents. While not explicitly on the c=
harter, privacy is a major concern within the IETF community. This document=
 &#8220;provides guidelines on the composition of DHCP or DHCPv6 requests, =
designed to minimize disclosure of identifying
 information.&#8221;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Given the already adopted documents and interest =
in this work shown at IETF-92 (Dallas), the WG co-chairs believe there is c=
onsensus to adopt this document. We are confirming that consensus on the ma=
iling list.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">If you think the WG should NOT adopt this work, p=
lease state so (with your reasons). Feel free to also express support for a=
dopting this work.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please respond on or before April 29, 2015.<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks!<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>Bernie (&amp; Tomek)<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1CA6909Bxmbrcdx04ciscoc_--


From nobody Wed Apr 15 10:17:22 2015
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D796D1B2E1E; Wed, 15 Apr 2015 10:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 W1R6EMLoqM1i; Wed, 15 Apr 2015 10:17:19 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEEFE1B2E06; Wed, 15 Apr 2015 10:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15010; q=dns/txt; s=iport; t=1429118239; x=1430327839; h=from:to:subject:date:message-id:mime-version; bh=ngI2P9g4vECTCT3CJf4Od6uYdnvVsGcSXgHRzGEJBBM=; b=WoXO7U3UOOOu3udDYHMCoNIqKs5QNyeFwj2saC8dBy5OdpaOU9qVJfGd BdvbWw2Kc5yXhS6MY7Lzz2HgcqLmgjsjNO0eXg0DaP1iMg8zyfbPQR/0N xHlMZMvyUK4hqKP3q7NJaVdSDmLfWifFFjex0VsnXoHa19vmaZVIUjB/z Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AyBQCHnC5V/5ldJa1cgkVHUlwFgxCCCMAnKgmBT4YDAhyBHzgUAQEBAQEBAX2EIgEEIwpBHQEMHiACBDAmAQQBGgEFiBwNrx6VSgEBAQEBAQEBAQEBAQEBAQEBAQEBAReMaIJtAQELFBYXgnMvgRYFhl6EJIYUgXCCC4c6OowUhw4igVuCFG8BgQo5fwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,582,1422921600";  d="scan'208,217";a="141546003"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-4.cisco.com with ESMTP; 15 Apr 2015 17:17:18 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t3FHHICe008699 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Apr 2015 17:17:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.142]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.03.0195.001; Wed, 15 Apr 2015 12:17:17 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>
Thread-Topic: RFC3315bis co-author meeting - 4/22/2015 0800 EDT
Thread-Index: AdB3n5IjvLmztwXoQV6K4D9Qx5lKMQ==
Date: Wed, 15 Apr 2015 17:17:17 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1CA691EE@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.204]
Content-Type: multipart/mixed; boundary="_004_489D13FBFA9B3E41812EA89F188F018E1CA691EExmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/is-aEK2d_b6AHL2r6wMNHMTzoyc>
Subject: [dhcwg] RFC3315bis co-author meeting - 4/22/2015 0800 EDT
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 17:17:21 -0000

--_004_489D13FBFA9B3E41812EA89F188F018E1CA691EExmbrcdx04ciscoc_
Content-Type: multipart/alternative;
	boundary="_000_489D13FBFA9B3E41812EA89F188F018E1CA691EExmbrcdx04ciscoc_"

--_000_489D13FBFA9B3E41812EA89F188F018E1CA691EExmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:

This is to notify the DHC WG that there will be a draft-ietf-dhc-rfc3315bis=
 co-author meeting at 0800 to 0900 EDT on Wed 4/22/2015. Those interested i=
n participating may join the discussion. We will use https://jitsi.tools.ie=
tf.org/dhcpv6.

The agenda is:



- Review currently assigned tickets (why not done & is reassignment  needed=
). See http://trac.tools.ietf.org/group/dhcpv6bis/report/4.

- Update tickets based on IETF-92 Dallas discussion (see http://www.ietf.or=
g/mail-archive/web/dhcwg/current/msg16480.html) and assign tickets as neede=
d.  Tickets 142, 144, 81, 17, 58, 82, 114, 70, 86 were included in this dis=
cussion.

- Assign stateful issues tickets (59, 60, 61, 62, 63, 64, 64, 66).

- Review other unassigned tickets and assign if ready, or initiate discussi=
on on DHC WG mailing list to finalize consensus if needed.

- Any other business?



-          Tomek & Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1CA691EExmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1264075866;
	mso-list-type:hybrid;
	mso-list-template-ids:1549719776 435191384 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is to notify the DHC WG that there will be a dr=
aft-ietf-dhc-rfc3315bis co-author meeting at 0800 to 0900 EDT on Wed 4/22/2=
015. Those interested in participating may join the discussion. We will use
<a href=3D"https://jitsi.tools.ietf.org/dhcpv6">https://jitsi.tools.ietf.or=
g/dhcpv6</a>.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The agenda is:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Review currently assigned tickets (why not done=
 &amp; is reassignment&nbsp; needed). See
<a href=3D"http://trac.tools.ietf.org/group/dhcpv6bis/report/4">http://trac=
.tools.ietf.org/group/dhcpv6bis/report/4</a>.<o:p></o:p></p>
<p class=3D"MsoPlainText">- Update tickets based on IETF-92 Dallas discussi=
on (see <a href=3D"http://www.ietf.org/mail-archive/web/dhcwg/current/msg16=
480.html">
http://www.ietf.org/mail-archive/web/dhcwg/current/msg16480.html</a>) and a=
ssign tickets as needed.&nbsp; Tickets 142, 144, 81, 17, 58, 82, 114, 70, 8=
6 were included in this discussion.<o:p></o:p></p>
<p class=3D"MsoPlainText">- Assign stateful issues tickets (59, 60, 61, 62,=
 63, 64, 64, 66).<o:p></o:p></p>
<p class=3D"MsoPlainText">- Review other unassigned tickets and assign if r=
eady, or initiate discussion on DHC WG mailing list to finalize consensus i=
f needed.<o:p></o:p></p>
<p class=3D"MsoPlainText">- Any other business?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>Tomek &amp; Bernie<o:p></o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1CA691EExmbrcdx04ciscoc_--

--_004_489D13FBFA9B3E41812EA89F188F018E1CA691EExmbrcdx04ciscoc_
Content-Type: message/rfc822
Content-Disposition: attachment;
	creation-date="Wed, 15 Apr 2015 17:17:16 GMT";
	modification-date="Wed, 15 Apr 2015 17:17:16 GMT"

From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcpv6bis@ietf.org"
	<dhcpv6bis@ietf.org>
Subject: draft-ietf-dhc-rfc3315bis co-author meeting 
Thread-Index: AdB3n/QaKfZCzgxOTMW0rr1aoxLxQQ==
Date: Wed, 15 Apr 2015 17:16:47 +0000
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative;
	boundary="_000_7773756772797480806777807377697775687165717766727974807_"
MIME-Version: 1.0

--_000_7773756772797480806777807377697775687165717766727974807_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi:

This is to notify the DHC WG that there will be a draft-ietf-dhc-rfc3315bis=
 co-author meeting at 0800 to 0900 EDT on Wed 4/22/2015. Those interested i=
n participating may join the discussion. We will use https://jitsi.tools.ie=
tf.org/dhcpv6.

The agenda is:

- Review currently assigned tickets (why not done & is reassignment  needed=
). See http://trac.tools.ietf.org/group/dhcpv6bis/report/4.
- Update tickets based on IETF-92 Dallas discussion (see http://www.ietf.or=
g/mail-archive/web/dhcwg/current/msg16480.html) and assign tickets as neede=
d.  Tickets 142, 144, 81, 17, 58, 82, 114, 70, 86 were included in this dis=
cussion.
- Assign stateful issues tickets (59, 60, 61, 62, 63, 64, 64, 66).
- Review other unassigned tickets and assign if ready, or initiate discussi=
on on DHC WG mailing list to finalize consensus if needed.
- Any other business?

-       Tomek & Bernie





--_000_7773756772797480806777807377697775687165717766727974807_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>Hi:</div>
<div>&nbsp;</div>
<div>This is to notify the DHC WG that there will be a draft-ietf-dhc-rfc33=
15bis co-author meeting at 0800 to 0900 EDT on Wed 4/22/2015. Those interes=
ted in participating may join the discussion. We will use <a href=3D"https:=
//jitsi.tools.ietf.org/dhcpv6"><font color=3D"blue"><u>https://jitsi.tools.=
ietf.org/dhcpv6</u></font></a>.</div>
<div>&nbsp;</div>
<div>The agenda is:</div>
<div>&nbsp;</div>
<div>- Review currently assigned tickets (why not done &amp; is reassignmen=
t&nbsp; needed). See <a href=3D"http://trac.tools.ietf.org/group/dhcpv6bis/=
report/4"><font color=3D"blue"><u>http://trac.tools.ietf.org/group/dhcpv6bi=
s/report/4</u></font></a>.</div>
<div>- Update tickets based on IETF-92 Dallas discussion (see <a href=3D"ht=
tp://www.ietf.org/mail-archive/web/dhcwg/current/msg16480.html"><font color=
=3D"blue"><u>http://www.ietf.org/mail-archive/web/dhcwg/current/msg16480.ht=
ml</u></font></a>) and assign tickets
as needed.&nbsp; Tickets 142, 144, 81, 17, 58, 82, 114, 70, 86 were include=
d in this discussion.</div>
<div>- Assign stateful issues tickets (59, 60, 61, 62, 63, 64, 64, 66).</di=
v>
<div>- Review other unassigned tickets and assign if ready, or initiate dis=
cussion on DHC WG mailing list to finalize consensus if needed.</div>
<div>- Any other business?</div>
<div>&nbsp;</div>
<ul style=3D"margin:0;padding-left:36pt;">
<li>Tomek &amp; Bernie</li><a name=3D"WBXOImailBodyEnd"></a>
</ul>
<div>&nbsp;</div>
<div>&nbsp;</div>
<a name=3D"WBXOImailBodyStart"></a>
<div>&nbsp;</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_7773756772797480806777807377697775687165717766727974807_
Content-Type: text/calendar; charset="utf-8"; method=PUBLISH
Content-Transfer-Encoding: base64

QkVHSU46VkNBTEVOREFSDQpNRVRIT0Q6UFVCTElTSA0KUFJPRElEOk1pY3Jvc29mdCBFeGNoYW5n
ZSBTZXJ2ZXIgMjAxMA0KVkVSU0lPTjoyLjANCkJFR0lOOlZUSU1FWk9ORQ0KVFpJRDpFYXN0ZXJu
IFN0YW5kYXJkIFRpbWUNCkJFR0lOOlNUQU5EQVJEDQpEVFNUQVJUOjE2MDEwMTAxVDAyMDAwMA0K
VFpPRkZTRVRGUk9NOi0wNDAwDQpUWk9GRlNFVFRPOi0wNTAwDQpSUlVMRTpGUkVRPVlFQVJMWTtJ
TlRFUlZBTD0xO0JZREFZPTFTVTtCWU1PTlRIPTExDQpFTkQ6U1RBTkRBUkQNCkJFR0lOOkRBWUxJ
R0hUDQpEVFNUQVJUOjE2MDEwMTAxVDAyMDAwMA0KVFpPRkZTRVRGUk9NOi0wNTAwDQpUWk9GRlNF
VFRPOi0wNDAwDQpSUlVMRTpGUkVRPVlFQVJMWTtJTlRFUlZBTD0xO0JZREFZPTJTVTtCWU1PTlRI
PTMNCkVORDpEQVlMSUdIVA0KRU5EOlZUSU1FWk9ORQ0KQkVHSU46VkVWRU5UDQpPUkdBTklaRVI7
Q049QmVybmllIFZvbHogKHZvbHopOk1BSUxUTzp2b2x6QGNpc2NvLmNvbQ0KREVTQ1JJUFRJT047
TEFOR1VBR0U9ZW4tVVM6SGk6XG5cblRoaXMgaXMgdG8gbm90aWZ5IHRoZSBESEMgV0cgdGhhdCB0
aGVyZSB3DQogaWxsIGJlIGEgZHJhZnQtaWV0Zi1kaGMtcmZjMzMxNWJpcyBjby1hdXRob3IgbWVl
dGluZyBhdCAwODAwIHRvIDA5MDAgRURUIG8NCiBuIFdlZCA0LzIyLzIwMTUuIFRob3NlIGludGVy
ZXN0ZWQgaW4gcGFydGljaXBhdGluZyBtYXkgam9pbiB0aGUgZGlzY3Vzc2lvbg0KIC4gV2Ugd2ls
bCB1c2UgaHR0cHM6Ly9qaXRzaS50b29scy5pZXRmLm9yZy9kaGNwdjYuXG5cblRoZSBhZ2VuZGEg
aXM6XG5cbi0gDQogUmV2aWV3IGN1cnJlbnRseSBhc3NpZ25lZCB0aWNrZXRzICh3aHkgbm90IGRv
bmUgJiBpcyByZWFzc2lnbm1lbnQgIG5lZWRlZCkNCiAuIFNlZSBodHRwOi8vdHJhYy50b29scy5p
ZXRmLm9yZy9ncm91cC9kaGNwdjZiaXMvcmVwb3J0LzQuXG4tIFVwZGF0ZSB0aWNrZQ0KIHRzIGJh
c2VkIG9uIElFVEYtOTIgRGFsbGFzIGRpc2N1c3Npb24gKHNlZSBodHRwOi8vd3d3LmlldGYub3Jn
L21haWwtYXJjaGl2DQogZS93ZWIvZGhjd2cvY3VycmVudC9tc2cxNjQ4MC5odG1sKSBhbmQgYXNz
aWduIHRpY2tldHMgYXMgbmVlZGVkLiAgVGlja2V0cyANCiAxNDJcLCAxNDRcLCA4MVwsIDE3XCwg
NThcLCA4MlwsIDExNFwsIDcwXCwgODYgd2VyZSBpbmNsdWRlZCBpbiB0aGlzIGRpc2N1cw0KIHNp
b24uXG4tIEFzc2lnbiBzdGF0ZWZ1bCBpc3N1ZXMgdGlja2V0cyAoNTlcLCA2MFwsIDYxXCwgNjJc
LCA2M1wsIDY0XCwgNjRcDQogLCA2NikuXG4tIFJldmlldyBvdGhlciB1bmFzc2lnbmVkIHRpY2tl
dHMgYW5kIGFzc2lnbiBpZiByZWFkeVwsIG9yIGluaXRpYXQNCiBlIGRpc2N1c3Npb24gb24gREhD
IFdHIG1haWxpbmcgbGlzdCB0byBmaW5hbGl6ZSBjb25zZW5zdXMgaWYgbmVlZGVkLlxuLSBBbg0K
IHkgb3RoZXIgYnVzaW5lc3M/XG5cbi0gICAgICAgVG9tZWsgJiBCZXJuaWVcblxuXG5cblxuDQpT
VU1NQVJZO0xBTkdVQUdFPWVuLVVTOmRyYWZ0LWlldGYtZGhjLXJmYzMzMTViaXMgY28tYXV0aG9y
IG1lZXRpbmcgDQpEVFNUQVJUO1RaSUQ9RWFzdGVybiBTdGFuZGFyZCBUaW1lOjIwMTUwNDIyVDA4
MDAwMA0KRFRFTkQ7VFpJRD1FYXN0ZXJuIFN0YW5kYXJkIFRpbWU6MjAxNTA0MjJUMDkwMDAwDQpV
SUQ6MDQwMDAwMDA4MjAwRTAwMDc0QzVCNzEwMUE4MkUwMDgwMDAwMDAwMEYwNkIzMjZEN0U3N0Qw
MDEwMDAwMDAwMDAwMDAwMDANCiAwMTAwMDAwMDBDOEEyN0U5RkYyQ0Y4QzRDQTM2MDZDMTdFOUZB
MEFDQQ0KQ0xBU1M6UFVCTElDDQpQUklPUklUWTo1DQpEVFNUQU1QOjIwMTUwNDE1VDE3MTY0N1oN
ClRSQU5TUDpPUEFRVUUNClNUQVRVUzpDT05GSVJNRUQNClNFUVVFTkNFOjANCkxPQ0FUSU9OO0xB
TkdVQUdFPWVuLVVTOmh0dHBzOi8vaml0c2kudG9vbHMuaWV0Zi5vcmcvZGhjcHY2DQpYLU1JQ1JP
U09GVC1DRE8tQVBQVC1TRVFVRU5DRTowDQpYLU1JQ1JPU09GVC1DRE8tT1dORVJBUFBUSUQ6MTkz
OTM5NDIzDQpYLU1JQ1JPU09GVC1DRE8tQlVTWVNUQVRVUzpCVVNZDQpYLU1JQ1JPU09GVC1DRE8t
SU5URU5ERURTVEFUVVM6QlVTWQ0KWC1NSUNST1NPRlQtQ0RPLUFMTERBWUVWRU5UOkZBTFNFDQpY
LU1JQ1JPU09GVC1DRE8tSU1QT1JUQU5DRToxDQpYLU1JQ1JPU09GVC1DRE8tSU5TVFRZUEU6MA0K
WC1NSUNST1NPRlQtRElTQUxMT1ctQ09VTlRFUjpGQUxTRQ0KQkVHSU46VkFMQVJNDQpBQ1RJT046
RElTUExBWQ0KREVTQ1JJUFRJT046UkVNSU5ERVINClRSSUdHRVI7UkVMQVRFRD1TVEFSVDotUFQx
NU0NCkVORDpWQUxBUk0NCkVORDpWRVZFTlQNCkVORDpWQ0FMRU5EQVINCg==

--_000_7773756772797480806777807377697775687165717766727974807_--

--_004_489D13FBFA9B3E41812EA89F188F018E1CA691EExmbrcdx04ciscoc_--


From nobody Wed Apr 15 12:28:18 2015
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C806D1A88FE for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 12:28:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 IX5SyDsQC9Db for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 12:28:16 -0700 (PDT)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB7211A88F4 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 12:28:15 -0700 (PDT)
Received: by lbcga7 with SMTP id ga7so42105060lbc.1 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 12:28:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jgpczBGQvq8FCck1xGQRuf3zlFdYQr+BrZVeq2ZbbTA=; b=coZHJkqN2Xh/9l/XOamxAr45WX8juBaaXggTxKGuviNW2SLdeM+LDLrfUHQ9CSQBNF r+IFcuoTSPbLMF1yVhv1vns2O84PNdpBeR6J20cnu39KM04qymJwNtxs0WJU9BI11qsV wqVoP/xRchaNgc0tpOdA43Su4F+IfMKkfMRF6ym2T7pfokVjQPQUIhH7srHf5CwmMDPp wrLbwyhw0dGPTeCmRn6yb+1pm5u5Z5puL2ZMinnc9mBHo33qYjy2BS93xS9onrjLuNr2 +zdjlHAaCcLGo6L4HbYX8+0m8I24NOnbkRCHAgGC85N89ME4WGPv6kyrke8RQm1i4K1V Gg5w==
X-Received: by 10.112.93.72 with SMTP id cs8mr25349747lbb.15.1429126094346; Wed, 15 Apr 2015 12:28:14 -0700 (PDT)
Received: from [192.168.10.14] (89-79-26-47.dynamic.chello.pl. [89.79.26.47]) by mx.google.com with ESMTPSA id y8sm1140206lag.10.2015.04.15.12.28.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Apr 2015 12:28:13 -0700 (PDT)
Message-ID: <552EBBB0.4010005@gmail.com>
Date: Wed, 15 Apr 2015 21:27:44 +0200
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1CA6909B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA6909B@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/iEkNiH-4sZ-ybL_Tx-_CXKMXJIE>
Subject: Re: [dhcwg] Call for Adoption: draft-huitema-dhc-anonymity-profile, ends April 29, 2015
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 19:28:17 -0000

I strongly support adoption of this document. In fits into focus of  the
DHC WG, and IETF in general. As a side note, the text has good quality.
Although it may be less important from the adoption perspective.

Marcin

On 04/15/15 19:00, Bernie Volz (volz) wrote:
> Hi:
> 
>  
> 
> The authors have requested that the working group adopt
> draft-huitema-dhc-anonymity-profile as a working group work item. The
> document is the next logical step to address the privacy issues
> identified in the recently adopted draft-ietf-dhc-dhcp-privacy and
> draft-ietf-dhc-dhcpv6-privacy documents. While not explicitly on the
> charter, privacy is a major concern within the IETF community. This
> document “provides guidelines on the composition of DHCP or DHCPv6
> requests, designed to minimize disclosure of identifying information.”
> 
>  
> 
> Given the already adopted documents and interest in this work shown at
> IETF-92 (Dallas), the WG co-chairs believe there is consensus to adopt
> this document. We are confirming that consensus on the mailing list.
> 
>  
> 
> If you think the WG should NOT adopt this work, please state so (with
> your reasons). Feel free to also express support for adopting this work.
> 
>  
> 
> Please respond on or before April 29, 2015.
> 
>  
> 
> Thanks!
> 
>  
> 
> -          Bernie (& Tomek)
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 


From nobody Wed Apr 15 22:42:58 2015
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DDE71A89FE for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 22:42:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 5KL1kAZIsU5z for <dhcwg@ietfa.amsl.com>; Wed, 15 Apr 2015 22:42:56 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 816E81A8911 for <dhcwg@ietf.org>; Wed, 15 Apr 2015 22:42:55 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRL79090; Thu, 16 Apr 2015 05:42:54 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 16 Apr 2015 06:42:53 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.135]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Thu, 16 Apr 2015 13:42:47 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Call for Adoption: draft-huitema-dhc-anonymity-profile, ends April 29, 2015
Thread-Index: AdB3nVyi2CTwlN+jTCySs+HRwBxbNQAaoZCg
Date: Thu, 16 Apr 2015 05:42:46 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B925F501BE3@nkgeml512-mbx.china.huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CA6909B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA6909B@xmb-rcd-x04.cisco.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.197]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B925F501BE3nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pRVChusJqYRSEkNJFX5CJIENEPk>
Subject: Re: [dhcwg] Call for Adoption: draft-huitema-dhc-anonymity-profile, ends April 29, 2015
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2015 05:42:57 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B925F501BE3nkgeml512mbxchi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBkbyBsaWtlIHRvIGV4cHJlc3MgbXkgc3VwcG9ydCBmb3IgdGhpcyB3b3JrIGFnYWluLiBJbXBv
cnRhbnQgd29yayBhbmQgbmljZSBlZmZvcnRzIGZyb20gdGhlIGF1dGhvcnMuDQoNCkJlc3QgcmVn
YXJkcywNCg0KU2hlbmcNCg0KRnJvbTogZGhjd2cgW21haWx0bzpkaGN3Zy1ib3VuY2VzQGlldGYu
b3JnXSBPbiBCZWhhbGYgT2YgQmVybmllIFZvbHogKHZvbHopDQpTZW50OiBUaHVyc2RheSwgQXBy
aWwgMTYsIDIwMTUgMTowMCBBTQ0KVG86IGRoY3dnQGlldGYub3JnDQpTdWJqZWN0OiBbZGhjd2dd
IENhbGwgZm9yIEFkb3B0aW9uOiBkcmFmdC1odWl0ZW1hLWRoYy1hbm9ueW1pdHktcHJvZmlsZSwg
ZW5kcyBBcHJpbCAyOSwgMjAxNQ0KDQoNCkhpOg0KDQoNCg0KVGhlIGF1dGhvcnMgaGF2ZSByZXF1
ZXN0ZWQgdGhhdCB0aGUgd29ya2luZyBncm91cCBhZG9wdCBkcmFmdC1odWl0ZW1hLWRoYy1hbm9u
eW1pdHktcHJvZmlsZSBhcyBhIHdvcmtpbmcgZ3JvdXAgd29yayBpdGVtLiBUaGUgZG9jdW1lbnQg
aXMgdGhlIG5leHQgbG9naWNhbCBzdGVwIHRvIGFkZHJlc3MgdGhlIHByaXZhY3kgaXNzdWVzIGlk
ZW50aWZpZWQgaW4gdGhlIHJlY2VudGx5IGFkb3B0ZWQgZHJhZnQtaWV0Zi1kaGMtZGhjcC1wcml2
YWN5IGFuZCBkcmFmdC1pZXRmLWRoYy1kaGNwdjYtcHJpdmFjeSBkb2N1bWVudHMuIFdoaWxlIG5v
dCBleHBsaWNpdGx5IG9uIHRoZSBjaGFydGVyLCBwcml2YWN5IGlzIGEgbWFqb3IgY29uY2VybiB3
aXRoaW4gdGhlIElFVEYgY29tbXVuaXR5LiBUaGlzIGRvY3VtZW50IOKAnHByb3ZpZGVzIGd1aWRl
bGluZXMgb24gdGhlIGNvbXBvc2l0aW9uIG9mIERIQ1Agb3IgREhDUHY2IHJlcXVlc3RzLCBkZXNp
Z25lZCB0byBtaW5pbWl6ZSBkaXNjbG9zdXJlIG9mIGlkZW50aWZ5aW5nIGluZm9ybWF0aW9uLuKA
nQ0KDQoNCg0KR2l2ZW4gdGhlIGFscmVhZHkgYWRvcHRlZCBkb2N1bWVudHMgYW5kIGludGVyZXN0
IGluIHRoaXMgd29yayBzaG93biBhdCBJRVRGLTkyIChEYWxsYXMpLCB0aGUgV0cgY28tY2hhaXJz
IGJlbGlldmUgdGhlcmUgaXMgY29uc2Vuc3VzIHRvIGFkb3B0IHRoaXMgZG9jdW1lbnQuIFdlIGFy
ZSBjb25maXJtaW5nIHRoYXQgY29uc2Vuc3VzIG9uIHRoZSBtYWlsaW5nIGxpc3QuDQoNCg0KDQpJ
ZiB5b3UgdGhpbmsgdGhlIFdHIHNob3VsZCBOT1QgYWRvcHQgdGhpcyB3b3JrLCBwbGVhc2Ugc3Rh
dGUgc28gKHdpdGggeW91ciByZWFzb25zKS4gRmVlbCBmcmVlIHRvIGFsc28gZXhwcmVzcyBzdXBw
b3J0IGZvciBhZG9wdGluZyB0aGlzIHdvcmsuDQoNCg0KDQpQbGVhc2UgcmVzcG9uZCBvbiBvciBi
ZWZvcmUgQXByaWwgMjksIDIwMTUuDQoNCg0KDQpUaGFua3MhDQoNCg0KDQotICAgICAgICBCZXJu
aWUgKCYgVG9tZWspDQo=

--_000_5D36713D8A4E7348A7E10DF7437A4B925F501BE3nkgeml512mbxchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVu
dD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8q
IEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6V2luZ2Rpbmdz
Ow0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh
bWlseTpTaW1TdW47DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIg
MTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6U2ltU3VuOw0K
CXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KLyogU3R5bGUgRGVm
aW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7
bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCmE6bGluaywgc3Bhbi5Nc29I
eXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93
ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29QbGFpblRleHQsIGRpdi5N
c29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJc
N0VBRlw2NTg3XDY3MkMgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAx
cHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiO30NCnNwYW4uQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiXDdFQUZcNjU4N1w2NzJDIENoYXIi
Ow0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazpcN0VBRlw2NTg3XDY3
MkM7DQoJZm9udC1mYW1pbHk6U2ltU3VuO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHls
ZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
Y29sb3I6d2luZG93dGV4dDt9DQpwLlBsYWluVGV4dCwgbGkuUGxhaW5UZXh0LCBkaXYuUGxhaW5U
ZXh0DQoJe21zby1zdHlsZS1uYW1lOiJQbGFpbiBUZXh0IjsNCgltc28tc3R5bGUtbGluazoiUGxh
aW4gVGV4dCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm
b250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
c3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQbGFpbiBUZXh0IENoYXIiOw0K
CW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCI7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUyMg0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2Vj
dGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIu
MHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8q
IExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjg2MzA1NzQwOTsN
Cgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6OTE5MjI3NjQ4
IC0yMDA5NjY4NDEwIDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4Njkz
IDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2
ZWwtc3RhcnQtYXQ6MDsNCgltc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxl
dmVsLXRleHQ6LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVy
LXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsInNhbnMtc2VyaWYiOw0KCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
bXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwy
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0K
QGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDpcRjBBNzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWls
eTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpcRjBCNzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBw
dDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw2
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpcRjBB
NzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0K
QGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDpcRjBCNzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWls
eTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw5DQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpcRjBBNzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0Kb2wNCgl7bWFyZ2luLWJv
dHRvbTowY207fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KLS0+PC9zdHlsZT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9
IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIx
IiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkg
bGFuZz0iWkgtQ04iIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29y
ZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj5JIGRvIGxpa2UgdG8gZXhwcmVzcyBt
eSBzdXBwb3J0IGZvciB0aGlzIHdvcmsgYWdhaW4uIEltcG9ydGFudCB3b3JrIGFuZCBuaWNlIGVm
Zm9ydHMgZnJvbSB0aGUgYXV0aG9ycy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMx
RjQ5N0QiPkJlc3QgcmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6
IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5
N0QiPlNoZW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2
Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0
O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gZGhjd2cgW21haWx0bzpkaGN3
Zy1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5CZXJuaWUgVm9seiAodm9s
eik8YnI+DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIEFwcmlsIDE2LCAyMDE1IDE6MDAgQU08YnI+
DQo8Yj5Ubzo8L2I+IGRoY3dnQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFtkaGN3Z10g
Q2FsbCBmb3IgQWRvcHRpb246IGRyYWZ0LWh1aXRlbWEtZGhjLWFub255bWl0eS1wcm9maWxlLCBl
bmRzIEFwcmlsIDI5LCAyMDE1PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+
SGk6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4g
bGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5UaGUgYXV0aG9ycyBoYXZlIHJlcXVlc3RlZCB0
aGF0IHRoZSB3b3JraW5nIGdyb3VwIGFkb3B0IGRyYWZ0LWh1aXRlbWEtZGhjLWFub255bWl0eS1w
cm9maWxlIGFzIGEgd29ya2luZyBncm91cCB3b3JrIGl0ZW0uIFRoZSBkb2N1bWVudCBpcyB0aGUg
bmV4dCBsb2dpY2FsIHN0ZXAgdG8gYWRkcmVzcyB0aGUgcHJpdmFjeSBpc3N1ZXMgaWRlbnRpZmll
ZCBpbiB0aGUgcmVjZW50bHkNCiBhZG9wdGVkIGRyYWZ0LWlldGYtZGhjLWRoY3AtcHJpdmFjeSBh
bmQgZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXByaXZhY3kgZG9jdW1lbnRzLiBXaGlsZSBub3QgZXhw
bGljaXRseSBvbiB0aGUgY2hhcnRlciwgcHJpdmFjeSBpcyBhIG1ham9yIGNvbmNlcm4gd2l0aGlu
IHRoZSBJRVRGIGNvbW11bml0eS4gVGhpcyBkb2N1bWVudCDigJxwcm92aWRlcyBndWlkZWxpbmVz
IG9uIHRoZSBjb21wb3NpdGlvbiBvZiBESENQIG9yIERIQ1B2NiByZXF1ZXN0cywgZGVzaWduZWQN
CiB0byBtaW5pbWl6ZSBkaXNjbG9zdXJlIG9mIGlkZW50aWZ5aW5nIGluZm9ybWF0aW9uLuKAnTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9
IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+R2l2ZW4gdGhlIGFscmVhZHkgYWRvcHRlZCBkb2N1bWVu
dHMgYW5kIGludGVyZXN0IGluIHRoaXMgd29yayBzaG93biBhdCBJRVRGLTkyIChEYWxsYXMpLCB0
aGUgV0cgY28tY2hhaXJzIGJlbGlldmUgdGhlcmUgaXMgY29uc2Vuc3VzIHRvIGFkb3B0IHRoaXMg
ZG9jdW1lbnQuIFdlIGFyZSBjb25maXJtaW5nIHRoYXQgY29uc2Vuc3VzIG9uIHRoZSBtYWlsaW5n
IGxpc3QuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNw
YW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5JZiB5b3UgdGhpbmsgdGhlIFdHIHNob3Vs
ZCBOT1QgYWRvcHQgdGhpcyB3b3JrLCBwbGVhc2Ugc3RhdGUgc28gKHdpdGggeW91ciByZWFzb25z
KS4gRmVlbCBmcmVlIHRvIGFsc28gZXhwcmVzcyBzdXBwb3J0IGZvciBhZG9wdGluZyB0aGlzIHdv
cmsuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4g
bGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5QbGVhc2UgcmVzcG9uZCBvbiBvciBiZWZvcmUg
QXByaWwgMjksIDIwMTUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5UaGFua3MhPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiIHN0
eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQ7dGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBs
ZXZlbDEgbGZvMiI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBsYW5nPSJFTi1VUyI+PHNw
YW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+LTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90
O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gbGFuZz0iRU4t
VVMiPkJlcm5pZSAoJmFtcDsgVG9tZWspPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_5D36713D8A4E7348A7E10DF7437A4B925F501BE3nkgeml512mbxchi_--


From nobody Thu Apr 16 04:32:28 2015
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84CA41A1B69 for <dhcwg@ietfa.amsl.com>; Thu, 16 Apr 2015 04:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 6VjDefcLsoUI for <dhcwg@ietfa.amsl.com>; Thu, 16 Apr 2015 04:32:26 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D1B51A1B65 for <dhcwg@ietf.org>; Thu, 16 Apr 2015 04:32:26 -0700 (PDT)
Received: by lbbzk7 with SMTP id zk7so56222554lbb.0 for <dhcwg@ietf.org>; Thu, 16 Apr 2015 04:32:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=6tWrDb+NwhgqJeluYICo2t+Lx/ffxpeikEvW4KDP7IU=; b=Ev9qSm7KKZLD4hU6cZ2/Xt8X1l51Y5WgwJQxBgNz1CtwAEVdFJzI9AD8jUz6heJOM8 Ul+RgKiuNZ96tVC0xaVW4fCInRGvJFRy4y6MHmFozoU2MJG1/F8yB+T0FDQYd1uPX08y gfizdrzRFOCyQACGxpscAA43U+hV3osbY9/UUAvgh9Yb4T4Tq9G31TLun/CXxs8Yg3U2 tBDqVtOVZJ0xIam/y1O81lNi0E3KgoguxGKCXKJuLT/PCjOpGQXsr/QwS8mMzoYN/F8N HeU7cQg+ssq6puaxA/UBpIndRN7aMGBfFa1BgT2BwoMnl8OnWZgz6ENzQ9V02h0LL9G9 ErLQ==
X-Received: by 10.152.36.2 with SMTP id m2mr27787945laj.72.1429183944406; Thu, 16 Apr 2015 04:32:24 -0700 (PDT)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id x8sm1617523lal.43.2015.04.16.04.32.23 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Apr 2015 04:32:23 -0700 (PDT)
Message-ID: <552F9DC4.8040908@gmail.com>
Date: Thu, 16 Apr 2015 13:32:20 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1CA6909B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CA6909B@xmb-rcd-x04.cisco.com>
X-TagToolbar-Keys: D20150416133220444
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/r_cugVcWWc1fnh0oqcBKIO_3GhQ>
Subject: Re: [dhcwg] Call for Adoption: draft-huitema-dhc-anonymity-profile, ends April 29, 2015
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2015 11:32:27 -0000

With my co-chair hat off, I strongly support adoption of this work.

Disclaimer: I'm a co-author.


From nobody Wed Apr 22 08:32:35 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 043601AC417; Wed, 22 Apr 2015 08:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.912
X-Spam-Level: 
X-Spam-Status: No, score=-103.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 C5_pXaBCGM2f; Wed, 22 Apr 2015 08:32:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 64EE51AC40C; Wed, 22 Apr 2015 08:32:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2501D180208; Wed, 22 Apr 2015 08:31:19 -0700 (PDT)
To: volz@cisco.com,  burcak@juniper.net, paduffy@cisco.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150422153119.2501D180208@rfc-editor.org>
Date: Wed, 22 Apr 2015 08:31:19 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/h5k18jtT43IKiNC9l2qW72HrkM0>
Cc: dhcwg@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [dhcwg] [Errata Held for Document Update] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 15:32:31 -0000

The following errata report has been held for document update 
for RFC3495, "Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3495&eid=4128

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Bernie Volz <volz@cisco.com>
Date Reported: 2014-10-10
Held by: Brian Haberman (IESG)

Section: 5.5.

Original Text
-------------
   The PacketCable architecture requires an MTA to authenticate itself
   to the TSP's network via the Kerberos protocol.  A Kerberos Realm
   name is required at the MTA to permit a DNS lookup for the address of
   the TSP's Kerberos Key Distribution Center (KDC) entity.

   The Kerberos Realm name MUST be encoded per the domain style realm
   name described in RFC 1510 [5].  This realm name MUST be all capital
   letters and conform to the syntax described in RFC 1035 [3] section
   3.1.  The sub-option is encoded as follows:

       Code   Len   Kerberos Realm Name
      +-----+-----+-----+-----+   +-----+
      |  6  |  n  |  k1 |  k2 |...|  kn |
      +-----+-----+-----+-----+   +-----+

Corrected Text
--------------
   The PacketCable architecture requires an MTA to authenticate itself
   to the TSP's network via the Kerberos protocol.  A Kerberos Realm
   name is required at the MTA to permit a DNS lookup for the address of
   the TSP's Kerberos Key Distribution Center (KDC) entity.

   The Kerberos Realm name MUST be use a domain style realm name
   described in RFC 1510 [5].  This realm name MUST be all capital
   letters and be encoded as described in RFC 1035 [3] section 3.1.
   The sub-option is encoded as follows:

       Code   Len   Kerberos Realm Name
      +-----+-----+-----+-----+   +-----+
      |  6  |  n  |  k1 |  k2 |...|  kn |
      +-----+-----+-----+-----+   +-----+

   Where k1...kn is the "DNS wire" encoded realm name (see RFC 3315,
   section 8). Thus, the realm "BASIC.1" is encoded as
   "RFCCORRECTED_TEXT5BASICRFCCORRECTED_TEXT11RFCCORRECTED_TEXT0".

Notes
-----
This text is not completely clear about how the realm name is to be encoded - as a 'string' or 'fqdn'.

RFC 1510 states:

   Kerberos realms are encoded as GeneralStrings. Realms shall not
   contain a character with the code 0 (the ASCII NUL).  Most realms
   will usually consist of several components separated by periods (.),
   in the style of Internet Domain Names, or separated by slashes (/) in
   the style of X.500 names.

And the reference to RFC 1035 section 3.1 is "conform to the syntax" which isn't the same as use this encoding - though I do agree that section 3.1 is mostly about "DNS wire encoding". It is just the use of "encoded" and "confirm to the syntax" combination that makes this unclear.

It is believed that the intended encoding is in DNS wire format. And, this should be clarified.

--------------------------------------
RFC3495 (draft-ietf-dhc-packetcable-06)
--------------------------------------
Title               : Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration
Publication Date    : March 2003
Author(s)           : B. Beser, P. Duffy, Ed.
Category            : PROPOSED STANDARD
Source              : Dynamic Host Configuration
Area                : Internet
Stream              : IETF
Verifying Party     : IESG


From nobody Wed Apr 22 09:10:23 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0F251B370E; Wed, 22 Apr 2015 09:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 K7afgJ2dIDvO; Wed, 22 Apr 2015 09:10:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8896C1B36E5; Wed, 22 Apr 2015 09:10:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20150422161011.17093.59021.idtracker@ietfa.amsl.com>
Date: Wed, 22 Apr 2015 09:10:11 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/4p_miiHJFyw3pkYZpxMriT74dzM>
Cc: dhcwg@ietf.org
Subject: [dhcwg] Last Call: <draft-ietf-dhc-dynamic-shared-v4allocation-06.txt> (Dynamic Allocation of Shared IPv4 Addresses) to Proposed Standard
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2015 16:10:22 -0000

The IESG has received a request from the Dynamic Host Configuration WG
(dhc) to consider the following document:
- 'Dynamic Allocation of Shared IPv4 Addresses'
  <draft-ietf-dhc-dynamic-shared-v4allocation-06.txt> as Proposed
Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-05-06. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This memo describes the dynamic allocation of shared IPv4 addresses
   to clients using DHCPv4.  Address sharing allows a single IPv4
   address to be allocated to multiple active clients simultaneously,
   each client being differentiated by a unique set of transport layer
   source port numbers.  The necessary changes to existing DHCPv4 client
   and server behavior are described and a new DHCPv4 option for
   provisioning clients with shared IPv4 addresses is included.

   Due to the nature of IP address sharing, some limitations to its
   applicability are necessary.  This memo describes these limitations
   and recommends suitable architectures and technologies where address
   sharing may be utilized.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/ballot/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/2502/
   http://datatracker.ietf.org/ipr/1102/
   http://datatracker.ietf.org/ipr/1119/



