Re: [Int-dir] IPv6-over-foo and Addressing Architecture (was Re: Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34 - options for fe80::/10 vs fe80::/64)

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 11 April 2019 13:37 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2227A1204DC; Thu, 11 Apr 2019 06:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 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, URIBL_BLOCKED=0.001] 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 JUfHSgd07zR7; Thu, 11 Apr 2019 06:37:56 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 649521202CD; Thu, 11 Apr 2019 06:37:56 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3BDbnOQ010934; Thu, 11 Apr 2019 15:37:49 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7DE00203E67; Thu, 11 Apr 2019 15:37:49 +0200 (CEST)
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 5FC1C201B36; Thu, 11 Apr 2019 15:37:49 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3BDbnS3006756; Thu, 11 Apr 2019 15:37:49 +0200
To: Suresh Krishnan <Suresh@kaloom.com>
Cc: Ole Troan <otroan@employees.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "its@ietf.org" <its@ietf.org>, "int-dir@ietf.org" <int-dir@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>, "draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org" <draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com> <386b9f4c-f9b5-900c-817a-95df68226ed9@gmail.com> <cc9564f5-b049-fa99-31a4-98a9c9c1261a@gmail.com> <856F277E-8F26-48BC-9C57-70DC61AA4E06@employees.org> <c91328aa-72e4-c0be-ec86-5bfd57f79009@gmail.com> <1BF2A47E-3672-462B-A4EC-77C59D9F0CEA@employees.org> <2ba71d54-8f2f-1681-3b2a-1eda04a0abf9@gmail.com> <B618E1B8-1E01-4966-97B2-AAF5FC6FE38A@employees.org> <bf83d3c2-a161-310f-98f4-158a097314a6@gmail.com> <D1A09E57-11E2-4FBC-8263-D8349FBFB454@employees.org> <MN2PR11MB3565A36F02B010B12E709ABED82E0@MN2PR11MB3565.namprd11.prod.outlook.com> <39c49adc-65b2-bfa8-4f97-b1216d7a71a4@gmail.com> <CAJE_bqf0+JjX81TeoqmirgKw4KnHoJdkCmgBx0nfu+-OeWPP3A@mail.gmail.com> <c878f52b-2ce9-7a83-5867-38d7565cd0f2@gmail.com> <c59e6e7a-0adb-7d24-50e7-3ffda6013ad5@cea.fr> <6601B81C-80E4-4CD4-8F4D-627B4208F151@employees.org> <5fbbad0e-cd27-2017-36ec-de8da1a5a9f0@gmail.com> <7AC9CCFC-278E-4B8A-A992-056D9C3F57EB@kaloom.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <be11c2c3-097f-c827-2fe3-e82759f6df0b@gmail.com>
Date: Thu, 11 Apr 2019 15:37:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <7AC9CCFC-278E-4B8A-A992-056D9C3F57EB@kaloom.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/int-dir/mHaYb-dKThseQZPM_bLDNC8H79U>
Subject: Re: [Int-dir] IPv6-over-foo and Addressing Architecture (was Re: Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34 - options for fe80::/10 vs fe80::/64)
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2019 13:38:01 -0000


Le 11/04/2019 à 15:26, Suresh Krishnan a écrit :
> Hi Alex,
> 
>> On Apr 11, 2019, at 7:53 AM, Alexandre Petrescu
>> <alexandre.petrescu@gmail.com> wrote:
>> 
>> Le 11/04/2019 à 13:38, Ole Troan a écrit :
>>>>>> I actually don't know if "this ipv6-over-80211ocb spec
>>>>>> needs to rely on the use of a non-0 value in the
>>>>>> intermediate 54 bits", btw. If that's not the case, it's
>>>>>> much safer and less controversial to just not mention it
>>>>>> (either in the form of "LL prefix length" or more
>>>>>> explicitly).  I guess that's also what others are
>>>>>> suggesting (and I agree with them in that sense).
>>>> There is the option of being silent about the prefix length of
>>>> IPv6 LLs in the IPv6-over-OCB document. There is the option of
>>>> mentioning "fe80::/10", but with "Updates 4291 section X" in
>>>> the header of the 1st page. There is the option of proving by
>>>> implementation that fe80:1::1/32 on OCB is not harmful to
>>>> others.
>>> Two of these options will likely prohibit consensus being reqched
>>> on this document. I encourage you to carefully consider how to
>>> best spend your time and the time of the particpants in the
>>> involved set of working groups.
>> 
>> YEs, thank you for the advice Ole.  I need to take care how to
>> spend my time.  Maybe try to avoid taking on directions that are
>> known to be dead ended.
>> 
>> I read your message as a warning that I take seriously.  For that,
>> I would like to ask you whether you make this suggestion as a WG
>> Chair of 6man WG?  Or as a contributor to other WGs?
> 
> <AD Hat On> I would like to look at this from a different angle. It
> is clear from the current standards that you need to be using
> fe80::/64 to form the LL address as the IPv6 address architecture
> requires the IID to be 64 bits long (for non b000 prefixes) and SLAAC
> requires the prefix and the IID lengths to add up to 128. If you want
> this changed, I don’t think this is the document where you should do
> it. The *burden of proof is on you* to show why the status quo does
> not work in this case and IMHO it has not been meet.
> 
> I would request that you keep the link-local prefix length discussion
> out of this draft, and in 6man where it belongs. Here is the thread
> that you started in January this year in 6man
> 
> https://mailarchive.ietf.org/arch/msg/ipv6/SD0OSOxFe9UGExX84u_CQSdfOsM
>
>  and the associated draft
> 
> https://datatracker.ietf.org/doc/draft-petrescu-6man-ll-prefix-len/
> 
> If you wish to pursue this topic further, please do so with *that*
> draft. An IP-over-foo document is not a place to do such a major
> architectural change.

Well ok, but I would like to pursue that draft without opposition.

The draft did have discussion yet it got refused for presentation.

I would like to avoid ping pong.

Alex

> 
> Thanks Suresh
>