Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem

Mark ZZZ Smith <markzzzsmith@yahoo.com.au> Wed, 23 October 2013 09:12 UTC

Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9835821E80AE for <v6ops@ietfa.amsl.com>; Wed, 23 Oct 2013 02:12:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.466
X-Spam-Level:
X-Spam-Status: No, score=-1.466 tagged_above=-999 required=5 tests=[AWL=0.633, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TCkVkgRELyLa for <v6ops@ietfa.amsl.com>; Wed, 23 Oct 2013 02:12:01 -0700 (PDT)
Received: from nm30-vm0.bullet.mail.bf1.yahoo.com (nm30-vm0.bullet.mail.bf1.yahoo.com [98.139.213.126]) by ietfa.amsl.com (Postfix) with ESMTP id 160A511E8341 for <v6ops@ietf.org>; Wed, 23 Oct 2013 02:11:50 -0700 (PDT)
Received: from [98.139.212.150] by nm30.bullet.mail.bf1.yahoo.com with NNFMP; 23 Oct 2013 09:11:50 -0000
Received: from [98.139.212.193] by tm7.bullet.mail.bf1.yahoo.com with NNFMP; 23 Oct 2013 09:11:50 -0000
Received: from [127.0.0.1] by omp1002.mail.bf1.yahoo.com with NNFMP; 23 Oct 2013 09:11:50 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 586058.22437.bm@omp1002.mail.bf1.yahoo.com
Received: (qmail 39671 invoked by uid 60001); 23 Oct 2013 09:11:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1382519510; bh=7+vP2QyR7UvVVm82+WKyk0YvmjT3OT/FtVIzIAruRIA=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=53QL4bho/7HHzx67HMRdDuLutFyW7lMzd1+ZN1DVUWHLvi6ksjoGnifTIfFGGNu/gHeyK3DaNRNZ5X1P6ZMzuzv7q0vmJIEJhdxd1EHQm05yCfwxzV85K8vA7SSKXmXr5XGtYeThDzFugtZyCaISCBXnvznE3/25XgtaZ3ffL88=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bFr/Qa/Lz280KCYVNxOhoXauAWwq6Qn/gbL1gSZjXt6T8hXs67H8MNLOqI9I4M/7+bWj+N91BbUchaI+mXag/KASyxTI0Mbs4GmlKZZMFUZOQVCN5G6T1jIREB+TlHu/SirYUR/g21yIyagtjH4/z4UNdRuCMHCoj4ZRCa7VG7I=;
X-YMail-OSG: YnSPwTEVM1my8uKzVxFmztNbK991FajHsZ_wgHOVMOifoKc IQDqrUzFnA65aJ5cOaF8EbyccJcD1toZwnAJLSIeJvAp5AR8bUhwbG00Aie4 hj.uiwH4rY6AV_IH728ktVyQ.Aey.9.y8tdsYpi80XvYT.OU_RItnZ20rzfa PwJ9YXRIXn1uiHwivxtp4SaqxgW54XhZ7XBKUtnyLH.uqT0CGzIJ6Fqv.bn0 CBWSfJdACZ26ABXVZHqgj8YGdLrQQ3r6Iy_vdQI9ETJ9oVPy3ygM6muvHkrx rLF9GVwrIvdnzxPhEA4Qbs1Yih8nDL.cJAkjNSvbpJDkhDcelboW7PXK3n1N pzXXiHBQ_SRsiu8BkbX_.J9WVXR5BEFmDRzEu0HS5NBPqQMoYweqIXizpb2M B48wVje4JohWEgborAggSXRK2YBzK8hINDDu4tNWcEzQgK5ejXilkELDuv_E GGuo2hH1BW6lZh49sE0OrXi8fkafajBtUkfiHtLbj9G.J.UYNDgR5rkP6r5P 5PYjXTUqt_ge0Y4o6HymgaGvgU2w7Uzhi5IlUdB_f7lG5RKNLHS4vmuMspbI ZTSqRATYWT4nBLq8H6xaFMw--
Received: from [150.101.221.237] by web142502.mail.bf1.yahoo.com via HTTP; Wed, 23 Oct 2013 02:11:49 PDT
X-Rocket-MIMEInfo: 002.001, SGksCgoKLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQo.IEZyb206IE1pa2FlbCBBYnJhaGFtc3NvbiA8c3dtaWtlQHN3bS5wcC5zZT4KPiBUbzogTWFyayBaWlogU21pdGggPG1hcmt6enpzbWl0aEB5YWhvby5jb20uYXU.Cj4gQ2M6IExpdWJpbmcgKExlbykgPGxlby5saXViaW5nQGh1YXdlaS5jb20.OyAidjZvcHNAaWV0Zi5vcmciIDx2Nm9wc0BpZXRmLm9yZz47ICJkcmFmdC1saXUtYm9uaWNhLXY2b3BzLWRoY3B2Ni1zbGFhYy1wcm9ibGVtQHRvb2xzLmlldGYub3JnIiA8ZHJhZnQtbGl1LWJvbmljYS0BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <201310211245.r9LCj0B29668@ftpeng-update.cisco.com> <alpine.DEB.2.02.1310211454090.26825@uplift.swm.pp.se> <8AE0F17B87264D4CAC7DE0AA6C406F453D7CC14B@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1310221511520.8663@uplift.swm.pp.se> <1382469405.56346.YahooMailNeo@web142504.mail.bf1.yahoo.com> <alpine.DEB.2.02.1310230533340.1838@uplift.swm.pp.se>
Message-ID: <1382519509.39565.YahooMailNeo@web142502.mail.bf1.yahoo.com>
Date: Wed, 23 Oct 2013 02:11:49 -0700 (PDT)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1310230533340.1838@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org" <draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org>
Subject: Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2013 09:12:06 -0000

Hi,


----- Original Message -----
> From: Mikael Abrahamsson <swmike@swm.pp.se>
> To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
> Cc: Liubing (Leo) <leo.liubing@huawei.com>om>; "v6ops@ietf.org" <v6ops@ietf.org>rg>; "draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org" <draft-liu-bonica-v6ops-dhcpv6-slaac-problem@tools.ietf.org>
> Sent: Wednesday, 23 October 2013 2:40 PM
> Subject: Re: [v6ops] DHCPv6/SLAAC Make Hosts Confusing-//RE: new draft: draft-liu-bonica-v6ops-dhcpv6-slaac-problem
> 
> On Tue, 22 Oct 2013, Mark ZZZ Smith wrote:
> 
>>  Is this saying that the prefix length of the address on host is /128?
> 
> A single address is always a /128. This /128 can be part of an on-link 
> other network, or it isn't.
> 

My question was more specificaly about you using "/128", rather than "an address" or "a single address", because I wondered if the DHCPv6 server supplies a /128 prefix length and the host configures a /128 prefix length on the address.

As you say below, address prefix length doesn't indicate on-link or off-link presence. So I'd expect a DHCPv6 server to hand out single IPv6 addresses with a /64 prefix length, as I think that would be more consistent and more expected when the subnet's prefix length is /64.

For somebody with a IPv4 experience, who wasn't aware an IPv6 prefix length doesn't indicate on-link presence, I think the use of a /128 prefix length in this scenario would imply that prefix length does indicate on-link presence. Somewhat pedantic perhaps, however I think anything that may give false indications of IPv6's behaviour, when it is different to IPv4's, is better to avoid.


Regards,
Mark.

>>  If that is the case, as the prefix length in doesn't indicate on-link 
> or 
>>  off-link status (as RA PIOs do), is there any specific reason for the 
>>  prefix length the DHCPv6 server hands out to be /128 instead of the 
>>  subnet's prefix length of /64? 
> 
> The DHCPv6 server always hands out /128. This /128 can be within a subnet 
> advertised in RA, or it can be outside of it. The host doesn't care. When 
> a subnet is being advertised in RA you get a network route pointing to the 
> interface without an IPv6 address as next-hop.
> 
> So it's perfectly achievable today (and it works) to have the following:
> 
> Host gets 2001:db8:fff::1/128 from dhcp
> host gets on-link 2001:db8:1::/64 from RA and creates a route towards the 
> interface for this, but doesn't do SLAAC because A=0.
> Host gets default route from router and installs it.
> 
> Now, the *router* needs to understand that 2001:db8:fff::1/128 is on-link, 
> but no other hosts on the network does not.
> 
> So what networks are being announced in RA is completely decoupled from 
> addresses handed out by DHCPv6 IA_NA. It's perfectly valid to hand out a 
> /128 and then have no on-link prefixes at all, or have some with A=0.
> 
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se
>