Re: [v6ops] draft-ietf-v6ops-host-addr-availability discussion
"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 03 November 2015 01:24 UTC
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C9461ACE0C for <v6ops@ietfa.amsl.com>; Mon, 2 Nov 2015 17:24:17 -0800 (PST)
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 KghRRzeJNJps for <v6ops@ietfa.amsl.com>; Mon, 2 Nov 2015 17:24:15 -0800 (PST)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) (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 B8E0A1ACDAB for <v6ops@ietf.org>; Mon, 2 Nov 2015 17:24:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id tA31ODUV006288; Mon, 2 Nov 2015 19:24:13 -0600
Received: from XCH-PHX-213.sw.nos.boeing.com (xch-phx-213.sw.nos.boeing.com [130.247.25.142]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id tA31OAkn006274 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 2 Nov 2015 19:24:11 -0600
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.14]) by XCH-PHX-213.sw.nos.boeing.com ([169.254.13.206]) with mapi id 14.03.0235.001; Mon, 2 Nov 2015 17:24:11 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>
Thread-Topic: [v6ops] draft-ietf-v6ops-host-addr-availability discussion
Thread-Index: AQHRFS2IJ4h76jRqCkuPztS49pNk7Z6JZjuggACchgD//3qXcA==
Date: Tue, 03 Nov 2015 01:24:10 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832F393F1@XCH-BLV-504.nw.nos.boeing.com>
References: <8D175A1F-B1AE-44B4-838E-1C853B6C937D@cisco.com> <2134F8430051B64F815C691A62D9831832F391A7@XCH-BLV-504.nw.nos.boeing.com> <CAKD1Yr15C-uoxUw0kgWO-d=LmUK8qWGLS7vt+22W+k8xXtDY+g@mail.gmail.com>
In-Reply-To: <CAKD1Yr15C-uoxUw0kgWO-d=LmUK8qWGLS7vt+22W+k8xXtDY+g@mail.gmail.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: multipart/alternative; boundary="_000_2134F8430051B64F815C691A62D9831832F393F1XCHBLV504nwnosb_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/hwa2hOT7Nu_bDizvV1YlQP8JHf4>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-host-addr-availability discussion
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2015 01:24:17 -0000
Hi Lorenzo, Responses below in “green”: From: Lorenzo Colitti [mailto:lorenzo@google.com] Sent: Monday, November 02, 2015 5:04 PM To: Templin, Fred L Cc: Fred Baker (fred); v6ops@ietf.org Subject: Re: [v6ops] draft-ietf-v6ops-host-addr-availability discussion On Tue, Nov 3, 2015 at 8:59 AM, Templin, Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote: I have one text addition suggestion and one question. On P. 7, in Table 1, suggest adding a new final row as follows: requires DAD Yes Yes No N/A Meaning that multi-addresses configured by SLAAC or DHCPv6 IA_NA/IA_TA must use DAD to check for duplicates on the link they were obtained. In a multi-addressing environment where millions of addresses are required, this could amount to a substantial amount of DAD multicast traffic. On the other hand, DAD is not needed for DHCPv6 PD because the network has unambiguously delegated the prefix for the node's exclusive use. I don't think "Requires DAD: No" is correct. Even if the device gets a /64 prefix entirely for its own use, it still needs to do DAD with any other devices on that /64 (e.g., tethered devices, VMs, etc.). I'm not opposed to adding a line to the table, though I don't think it provides much value - if we put our mind to it, I'm sure we could come up with lots of things we could add to the table that aren't there at the moment. My main concern is that if we add something to the table it needs to be correct. What I mean is “Requires DAD on the interface over which the prefix was received”, but that was too long to fit in the table. Let’s call the interface “A”. If the node gets SLAAC addresses or DHCP IA_NA/IA_TA addresses over interface “A”, then it needs to do DAD on interface “A” for each such address. If the node gets a DHCPv6 PD over interface “A”, however, it does not need to do DAD over interface “A” at all. If the node assigns the delegated prefix to interface “B”, then you are right that that DAD will be required among all tethered devices, VMs, etc. on interface “B”. But, there will still be no need for DAD on interface “A”. Does that clarify? I have a question also on table 1. Under ""Unlimited" endpoints", why does it say "no" for DHCPv6 PD? I think it should say "yes" instead, since a prefix obtained by DHCPv6 PD can be used to configure an unlimited number of addresses on the link over which the prefix was received. The table is written from the perspective of the network assigning addresses to devices that connect to it. Therefore, it says "no" because if you use DHCPv6 PD you can't assign address space to an unlimited number of endpoints - you are limited to however many /64s you have available. If you use IA_NA or SLAAC, any network with a /64 subnet has, at least in theory, an "unlimited" number of addresses to assign to clients. Of course, that's only true in theory. In practice, there's going to be a limit due to scaling reasons. I don’t understand this. True that SLAAC and DHCPv6 IA_NA/IA_TA can be used to assign an unlimited number of addresses to interface “A”. But, so can DHCPv6 PD. When the node receives the delegated prefix (e.g., a /64), it can assign as many unique IPv6 addresses as it likes to interface “A”. And again, it need not do DAD for any of them.
- [v6ops] draft-ietf-v6ops-host-addr-availability d… Fred Baker (fred)
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Alexandre Petrescu
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Lorenzo Colitti
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Lorenzo Colitti
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Brian E Carpenter
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… David Farmer
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… David Farmer
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Lorenzo Colitti
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Lorenzo Colitti
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Brian E Carpenter
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Alexandre Petrescu
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Lorenzo Colitti
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Alexandre Petrescu
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Lorenzo Colitti
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Alexandre Petrescu
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… David Farmer
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Lorenzo Colitti
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… David Farmer
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Lorenzo Colitti
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… David Farmer
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Alexandre Petrescu
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Alexandre Petrescu
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- [v6ops] DAD again [was: draft-ietf-v6ops-host-add… Brian E Carpenter
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Templin, Fred L
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Philip Homburg
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… Templin, Fred L
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Mukom Akong T.
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Templin, Fred L
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… 神明達哉
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Lorenzo Colitti
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Alexandre Petrescu
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Alexandre Petrescu
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Gert Doering
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Gert Doering
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Gert Doering
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Gert Doering
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Gert Doering
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Templin, Fred L
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Templin, Fred L
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Hemant Singh (shemant)
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Owen DeLong
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Brian E Carpenter
- Re: [v6ops] DAD again [was: draft-ietf-v6ops-host… Templin, Fred L
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… David Schinazi
- Re: [v6ops] draft-ietf-v6ops-host-addr-availabili… David Farmer