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:46 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 90452131782 for <v6ops@ietfa.amsl.com>; Tue, 4 Jul 2017 13:46:33 -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 9kxTMAuDtyAb for <v6ops@ietfa.amsl.com>; Tue, 4 Jul 2017 13:46:32 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::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 EB0E013174E for <v6ops@ietf.org>; Tue, 4 Jul 2017 13:46:31 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id q85so5970362pfq.1 for <v6ops@ietf.org>; Tue, 04 Jul 2017 13:46:31 -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=DUtXr0ExVcSTi/3IbpE6WBsIg8m2+DfrwVrrUo3zXeY=; b=OOj5nSAcaNpOK1V/DsUG4q+bduCbThCnCcUNERDcRWZMmoGWjo/ejEex7OgqGzZNrU PU1hOszd9uhQrCqKXbJevFXzWWmcn1X/AhYqiq0sjDJaewjSg0ZQQ3C60mRMQp7tXyWL yhDWtMiINlKPVTITRW3KHZ8BqkfCfuaIEuPexn1JM2LH8Jy5Q4teiOZOw5ypzBLruZhE mnBNAiebYBiggaO7v6wAoeaQS77zIKXSC9QOcncUjS3tQGd2VeM/CMv487zqsbalpS1R iX42mx1IcAvSHrlquDOLfos81P0osITebB0IckggNHihyYaXfbTTLZ6RY3HU240NYkyu nTdA==
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=DUtXr0ExVcSTi/3IbpE6WBsIg8m2+DfrwVrrUo3zXeY=; b=QnVvwELSlVQfcZBAeIwErlTEAh7+IE+TS1mpo8KPE1pvYd0Zhel6sJKgdic+GBF27Y kLuttbj5oaRE/VKHs+8SR6bSTp4xJWtvPFsjCCivI6k+OIo0m6ZQ07iaB5ImdMaxrfi+ kxjKdOcqUmaxeHsMZXOWPwJYYCq8i/LUVLimiJwJSectZqxw+I+eF1So6P5KAqbvnlAp E0rV2jXh+fGFrYwHBkA6bIqs8f5x9swZ4R7o9yZoaxxdxmlxO24ZF3WK/Ko4555lYl08 qmM2nl5Nz21j11CWfEi7XRTn+RIGJDs+m2XbCfuAALs5G5ZpC4qvI70esXFhuMuBE5sh Gstg==
X-Gm-Message-State: AIVw1106AuJd8egtB5MfNq4owhjWG3M/m2UOEH0ChC540Hc3FEnr0XRU z+zu4mrHqcL1fJvT
X-Received: by 10.98.14.130 with SMTP id 2mr17265401pfo.218.1499201191332; Tue, 04 Jul 2017 13:46:31 -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 n74sm46627657pfh.118.2017.07.04.13.46.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jul 2017 13:46:30 -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> <c00acac9-da2e-0952-1c56-134813620dd7@gmail.com> <2A1B0327-CAA2-40B6-8BC2-30586A64E8AD@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5a5db7d9-61ab-c8a9-ec9b-6bf45fd56aa8@gmail.com>
Date: Wed, 05 Jul 2017 08:46:30 +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: <2A1B0327-CAA2-40B6-8BC2-30586A64E8AD@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/5eHSztLBD-woeY5MKdsH9kSm6xU>
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:46:34 -0000

On 05/07/2017 08:35, Ole Troan wrote:
> Brian,
> 
>>> 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?
> 
> Are you implying there are links where link-local multicast aren't available?

I'm not aware of any, but do we actually have a standard that makes it mandatory?

> If course on the link type I describe there is ever only two nodes connected. 

Sure, I understood that.
 
> If we can't do better than require every link to have a service discovery "helper" then sure link-local multicast is fine ( benefit is well known addresses).

Yes. I think it's unavoidable. Certainly our intention in ANIMA is that discovery must work on any topology without prior configuration, and that requires every node that has more than one interface to automatically deploy a discovery relay between its interfaces. (And yes, that in turn requires loop prevention.)

  Brian