Re: appropriate length of fe80:: prefix and new IP-over-foo drafts

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 31 January 2019 13:00 UTC

Return-Path: <alexandre.petrescu@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 9B761129BBF for <ipv6@ietfa.amsl.com>; Thu, 31 Jan 2019 05:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
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 G7AfIfGMqN8g for <ipv6@ietfa.amsl.com>; Thu, 31 Jan 2019 05:00:11 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 A7B18128CB7 for <ipv6@ietf.org>; Thu, 31 Jan 2019 05:00:10 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x0VD06Ak041653; Thu, 31 Jan 2019 14:00:08 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9CF03206A6B; Thu, 31 Jan 2019 14:00:08 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 85C29206AAF; Thu, 31 Jan 2019 14:00:08 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x0VD04DD018681; Thu, 31 Jan 2019 14:00:04 +0100
Subject: Re: appropriate length of fe80:: prefix and new IP-over-foo drafts
To: Fernando Gont <fgont@si6networks.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Mark Smith <markzzzsmith@gmail.com>
Cc: IPv6 IPv6 List <ipv6@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>, phessler@openbsd.org
References: <6d9657d0-803c-fcb2-ddb9-13f707bdfd47@gmail.com> <27f3c3266f2e4a7f9ed773e986d41275@ustx2ex-dag1mb5.msg.corp.akamai.com> <38ef7dced8e34455b1059ce3ca8afeb1@ustx2ex-dag1mb5.msg.corp.akamai.com> <0af59661-ed8b-cd25-1125-468604edee53@gmail.com> <1df7d774-fe97-2feb-444a-94992cb89581@gmail.com> <CAJE_bqfVkFkvxVto67VGhjDK61ob6wxZXCRObtmwpr3GSyenfw@mail.gmail.com> <2def076d-b6bf-d84f-152b-d1d9277e9e73@gmail.com> <CAKQ4NaUW5-VY=TMjh0Ap01KTg4=An8=EXH_ej40nW=GM1kUL4w@mail.gmail.com> <c54b9702-1c6f-e5ae-971d-7d3ef443d994@gmail.com> <CAO42Z2wPAF6YCwsb+f0BXMEOKdFSiiFRNop=ChvKFPW32UepBA@mail.gmail.com> <e2a1a5c4-832f-744e-db69-2100c32fb59e@gmail.com> <c0d25c47-4684-8e1b-518d-2b00b41b9ed5@gmail.com> <6b712b9f-9a72-86a1-eab0-262b54962de8@si6networks.com> <62f2709f-5167-b884-d0e3-9a42d1eb4027@gmail.com> <207325ab-f42a-c775-459f-0c07ccc19116@si6networks.com> <6a91176d-5348-31c6-392f-a8ce03f161ab@gmail.com> <4472303b-6b60-b90d-6a24-ac98a8111e5c@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <86bd1106-1189-c2a2-eaa2-788818035c3b@gmail.com>
Date: Thu, 31 Jan 2019 14:00:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <4472303b-6b60-b90d-6a24-ac98a8111e5c@si6networks.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vp-YPlHKEx4m73iFFsz9r_cEUBc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 31 Jan 2019 13:00:18 -0000


Le 31/01/2019 à 13:31, Fernando Gont a écrit :
> On 31/1/19 09:25, Alexandre Petrescu wrote:
>>
>>
>> Le 31/01/2019 à 12:41, Fernando Gont a écrit :
>>> On 31/1/19 08:33, Alexandre Petrescu wrote:
>>>>
>>>>
>>>> Le 31/01/2019 à 12:17, Fernando Gont a écrit :
>>>>> On 31/1/19 07:24, Alexandre Petrescu wrote:
>>>>>>
>>>>>>
>>>>>> Le 30/01/2019 à 23:14, Brian E Carpenter a écrit :
>>>>>>> Section 5.3 "Creation of Link-Local Addresses" of RFC4862 refers to
>>>>>>> an interface identifier of N bits and an fe80::0 prefix "of
>>>>>>> appropriate length", which according to the addressing architecture
>>>>>>> is 128-N. But N is undefined by RFC4862 and cannot be derived from an
>>>>>>> RA because all this happens as soon as the interface is enabled.
>>>>>>> Therefore N must be predefined.
>>>>>>>
>>>>>>> As pioneered by RFC2464**, all ipv6-over-foo documents must therefore
>>>>>>> specify N for their link type. So far, everybody has specified 64, as
>>>>>>> far as I know. Is there a reason to do otherwise for the two drafts
>>>>>>> mentioned below?
>>>>>>
>>>>>> One of the two drafts involves a Network ID of length 24.
>>>>>>
>>>>>> The question is why not use 24 for InterfaceID?  Just because Ethernet
>>>>>> had it that way?
>>>>>
>>>>> You can certainly do that with OpenBSD. ;-)
>>>>
>>>> In linux too I can add (and we actually do) link-local addresses with
>>>> prefix length 32.
>>>
>>> They will not work if you try to employ them with BSDs. BSDs use bits in
>>> the range /16 /64 to store information such as the interface index.
>>> So... don't use prefixes shorter than /64 for link-locals, or you'll be
>>> asking for trouble.
>>
>> Ah?  according to which spec do the BSD implementers put bits in the
>> range 16-64?
> 
> They don't send those bits on the wire. But they do use those bits as
> described. -- According to no spec. If the link-local prefix is assumed
> to be /64, then you're free to use those bits *internally* as you wish.
> That's what BSDs do. Jinmei is quite likely in a better position ot
> comment on this.

I would like to kindly ask Jinmei to make sure to keep that internal 
such that to not forbid the end user to ifconfig add fe80:1::1/63

If possible.

Alex

> 
> Thanks,
>