Re: [v6ops] question about draft-jjmb-v6ops-unique-ipv6-prefix-per-host

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 04 July 2017 20:17 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 45295131775 for <v6ops@ietfa.amsl.com>; Tue, 4 Jul 2017 13:17:36 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xdKPTYpoTFqJ for <v6ops@ietfa.amsl.com>; Tue, 4 Jul 2017 13:17:34 -0700 (PDT)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::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 B2C0B12F26D for <v6ops@ietf.org>; Tue, 4 Jul 2017 13:17:34 -0700 (PDT)
Received: by mail-pg0-x22e.google.com with SMTP id t186so114499494pgb.1 for <v6ops@ietf.org>; Tue, 04 Jul 2017 13:17:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=DyzN/P1S23PhJYErxknfi3rBX1I496AXlPS7/rvV+kc=; b=akAS4hiqFDbePfYEoRm0z2IGYAF8m7HiSKjC6Fuywbq9UqdGVYqFMg0iEuwpzGoeya yPftb+NZjN/T+Qx4Te3Zq3P9z7kgiJntnJJXHOIqVk9xOYVFIvdcME+ORR2i3BLvKs35 70/sYYcwGHt8FkrYz5ektQfxN2HQXIHbXbdgPnUxd8CDKMQWauFB/3QKYqZ0x2xLzB83 Srnw1dlIBKn73XhPRN9xAOEyiWeagN2amfyNOCupF5lX0gfJeFZAMzLEUq+FLzzyNtKd /3UIVXiIoKOmRkfbhtGT5Q0rxz2BmILcd46uOuXhLriMu7ruzAyVbUf+TxvTDgdQY7gW WBIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=DyzN/P1S23PhJYErxknfi3rBX1I496AXlPS7/rvV+kc=; b=KhOtDZqEavNpiSsaw8cBp0TKoEzqre+tVdXBBm1uwAOBpNra6cZqp6Ajv0X/fSCec/ hTSJ5baLqle8bZGUYt9Y91/M20nsJnOTbtl7bxck15fH9tOETw9tCSqkn85nvJmnXA47 +35PX0g6W/A/syStZDBwLGTXlbhJfGHQobNYgHBHOi+W+y4KslV+8GylTy3vWw7PJPav PAVjrwTDrIP0k7Af9FHFKntLrlBRLq7S9yEeq8VIqUGS9kRJTTz4JkLyAo5fZPLnomAn co9ftPCGlgz0C6qcjYf5GPdA/78vxrnJmccd1oHq/PAyI2tLj5898A1krC5IF9q+OJnb oTnA==
X-Gm-Message-State: AIVw113SCi+M8oRJKfUImh7itFz4y1EnVDsSckNUtabfVWSi/pWUizn/ 4li6yOJICYYLzDN7
X-Received: by 10.84.198.67 with SMTP id o61mr18218113pld.98.1499199454001; Tue, 04 Jul 2017 13:17:34 -0700 (PDT)
Received: from ?IPv6:2406:e007:4f03:1:28cc:dc4c:9703:6781? ([2406:e007:4f03:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id l85sm18455766pfi.53.2017.07.04.13.17.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 13:17:33 -0700 (PDT)
To: Ole Troan <otroan@employees.org>
Cc: Ted Lemon <mellon@fugue.com>, v6ops@ietf.org
References: <5348A2C7-D762-470B-9BC9-86B8A09E6369@consulintel.es> <CAKD1Yr1UNvfrozET0Ay4LCtZe-NSBAGwbCcpye7JhGtpzyT2Sg@mail.gmail.com> <645EA227-F9E8-4B15-878B-83BC8FD9809A@employees.org> <DCB3CF45-C552-4A37-B7A2-E90C080170BD@fugue.com> <07EE34C2-A479-41EB-B983-D8F2D585E306@employees.org> <071E625C-7B68-4E9F-98C6-262A1052CBF1@fugue.com> <310527F9-C27E-4EA0-B655-9B20878DC459@employees.org> <3cc51f51-139d-940d-bf05-6e449528f8b1@gmail.com> <F8DA8CE5-7D8A-4513-8F1B-601AB96141D6@employees.org> <C62AC675-F128-45A5-8F72-A54144AD7C09@fugue.com> <1E8426B8-1622-42EF-97E2-D81F70A78493@employees.org> <958452FD-2F9F-4057-BCB9-D62F2DC2127A@fugue.com> <2254408d-0382-fda6-aabf-2fefe033c4cc@gmail.com> <ACE9A0A9-33D4-4C64-BE28-80E2FB9D8646@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <c00acac9-da2e-0952-1c56-134813620dd7@gmail.com>
Date: Wed, 05 Jul 2017 08:17:32 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <ACE9A0A9-33D4-4C64-BE28-80E2FB9D8646@employees.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/a_S02XRq6CInpAV-WjPC3_dsFOo>
Subject: Re: [v6ops] question about draft-jjmb-v6ops-unique-ipv6-prefix-per-host
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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, 04 Jul 2017 20:17:36 -0000

On 04/07/2017 18:59, Ole Troan wrote:
> Brian,
> 
>>> On Jul 3, 2017, at 5:41 PM, Ole Troan <otroan@employees.org> wrote:
>>>> It breaks the assumption that everything you want discovered is within the same broadcast domain. Many think that assumption was broken anyway.
>>>
>>> Given the document I'm presently working on, I wouldn't really argue with that, except to say that it's still the default assumption in most environments.
>>
>> Yes, and that has deeply impacted both a document I'm working on
>> (draft-ietf-anima-grasp) and a demo implementation thereof
>> (https://github.com/becarpenter/graspy/blob/master/grasp.py).
>>
>> The cost of *not* having link-local multicast is considerable,
>> because it means that every node, however dumb, must replicate
>> and relay discovery in one way or another.
> 
> The solution I briefly described previously of course supports link-local multicast.
> 
> If your answer to the discovery problem is that we must put all nodes on the network in the same broadcast domain, we know that doesn't scale well. 

Of course not. I think both DNSSD and ANIMA have got beyond that point.

...
> Since we have to solve the problem for multiple links anyway, does it then make a difference that logical topology follows physical topology and each host is on its own link?

If the discovery traffic is a very small proportion of total traffic, it probably doesn't matter exactly which solution you adopt. But (as Tim implies for DNSSD), I think you should use link-local multicast when it's available. Are we disagreeing?

    Brian