Re: <draft-ietf-6man-rfc4291bis-09.txt>

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 22 July 2017 20:47 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B88B131822 for <ipv6@ietfa.amsl.com>; Sat, 22 Jul 2017 13:47:30 -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 P9NoN6KgMQdK for <ipv6@ietfa.amsl.com>; Sat, 22 Jul 2017 13:47:28 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 939E7131A4F for <ipv6@ietf.org>; Sat, 22 Jul 2017 13:47:28 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id s70so34691940pfs.0 for <ipv6@ietf.org>; Sat, 22 Jul 2017 13:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=2r4EfNZZLE6SgQlLUkNQFxa4FbOR12k91XV50Frrq98=; b=C8M2iyhJoFcvHsLEDzMQLM0CGT9xUQ/oCuFCFNnjWjCcpQUBOxnH/57isKEPfz+8kB 51yuFteWz/EdG53sIIRB6miMLWfRdW0Bxs7UIiTq+O74X+dbYQ+dlKsirCpikU6HyJKq BjwslR1yPoZz1SBt6L/xJTOUbSNMIMLSjyBJH+jVK3PnZwxan6bpbBkjnwgNsCsyrG6v 3zMzBpWGCjxbUtV2XEzRI04k3nb34JD1WL2x6b2nK82wYbaGzVYyiFMzg46i+S2KDdgF R3Qj/JnGTFNDRi94huVL/vkIcn7IQ0Spe+NKl9J2arypHnqwpz7twNTe4VaWYK36tv2+ Ob+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=2r4EfNZZLE6SgQlLUkNQFxa4FbOR12k91XV50Frrq98=; b=CJp1w7hDDcPm0ykgc7GxSSXroYmDgfL43jbbBWZHuLqs2PA0hAqU338Aq8zNwtxdXB qCyDc0/tdOm1h1eiix3dslfXzES4qn2yyi35rS8++d0OvoET/IySmi4wawECY5jN4Yp1 dHRW1mYIOqf0rrrQMHkOVKqcHwIArBJ8nuqEMrIbS2F0rgbvGbjPjXFzOiIp5Sq/pLgq bKjbaJNn+lUSn1HNlzHHHSiyPwKrdP1dWbTvAlvSjslNuSEQhiOTIH+s6tC5Bdx569sM 9C8+xsqaAPENmSy6tffkExao4sM0r/a7kw3OUY19reX3JQTVloaxt1VLUNUpg5LW+A4u 1ggw==
X-Gm-Message-State: AIVw112+CTyYC6mulHmHK4GFMfaWnLuLBaYVKGlWcs6XryQ6+i7GNePI QqnzloCfKg06Xft+
X-Received: by 10.101.83.197 with SMTP id z5mr11608716pgr.261.1500756448012; Sat, 22 Jul 2017 13:47:28 -0700 (PDT)
Received: from ?IPv6:2406:e007:4a2d:1:28cc:dc4c:9703:6781? ([2406:e007:4a2d:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id s17sm15962462pfg.166.2017.07.22.13.47.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Jul 2017 13:47:27 -0700 (PDT)
Subject: Re: <draft-ietf-6man-rfc4291bis-09.txt>
To: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>, ipv6@ietf.org
References: <20150804195752.5065.13523.idtracker@ietfa.amsl.com> <5AB14F48-2799-4A86-830D-E8A89CCADAAC@gmail.com> <CAKD1Yr0Bt4hhBvtSVWrLpns4odzek3U5WJkuQoS1NGsPozW0sg@mail.gmail.com> <CAN-Dau3vVREsYc4Y6AAdDpLKsMjwH_2saS7JTn8P6fRDXRKV7Q@mail.gmail.com> <596F63F4.9010501@foobar.org> <fe7a1def-e656-c6d8-5336-ed5595331b74@gmail.com> <ed0fde09ae2a4a598c9a84eb0df659e8@XCH15-06-11.nw.nos.boeing.com> <69a7f9f2-584e-a2bc-1200-64fad8f9baf7@gmail.com> <652efa7dcb414b7ba6128bb4f93a3d7e@XCH15-06-11.nw.nos.boeing.com> <CAJE_bqfbLzfSYBBuS58CB6EWYkLLoqgGnb==v0CSScfZBFp=HQ@mail.gmail.com> <m1dYUCB-0000F6C@stereo.hq.phicoh.net> <bf2ab8d8-9070-c53f-90bd-831630021749@gmail.com> <m1dYwTM-0000FzC@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <be9f995c-b717-e87b-3ab9-3a1faa35d770@gmail.com>
Date: Sun, 23 Jul 2017 08:47:23 +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: <m1dYwTM-0000FzC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8Xu2yiBuOxNFBJYYsQUMkJidQh4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 20:47:30 -0000

On 23/07/2017 03:37, Philip Homburg wrote:
>> Then you really have to answer my question: if they are not called "interface
>> identifier" what are those bits called?
> 
> So let me call them 'host part'

Hate to be picky but in RFC8200 'host' does not include 'router' and these
bits certainly exist in router addresses.

So it would have to be 'node part'. But in most cases (the only exception
being anycast) these bits may be (not must be) different in the node per
interface, so 'node' is still wrong. I just don't get why it isn't
'interface part' (with an exception for anycast). And if it's 'interface
part' I really don't see why it isn't 'interface identifier'.

Here's a thought. How would it be if the contentious sentence in 4291bis
read, in its entirety:

"Interface Identifiers are 64 bits long when used for Stateless
Address Autoconfiguration (SLAAC) [RFC4862]."

?.

Who here could not live with that?

    Brian


> 
>>> What we currently have is that requirements on IID depend on the use case.
>>
>> If they are called something else, the requirements will still depend on
>> the use case.
> 
> Basically a 'host part' doesn't have any properties. You can say it
> identifies an interface, but that is not the case if a 'host part' is 
> part of an anycast address.
> 
> So a host part has a specific length, which is of course related to the
> prefix length. And that's it.
> 
> For manual address configuration, a host part doesn't have any properties
> except that it should be unique.
> 
> For DHCP IA_NA the same applies. Though in the context of DHCP you may also
> want to talk about privacy. But that goes way beyond what rfc4291 deals
> with. 
> 
> Some host parts may be anycast addresses. But by and large whether an
> address is anycast is a local flag that needs to be set. There are no specific
> requirements for host parts that are anycast addresses.
> 
> Only when a host part happens to be used in SLAAC, we get a completely
> different story.
>