Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1 LL on loopback

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 18 April 2019 11:48 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 56DA31202F8; Thu, 18 Apr 2019 04:48:02 -0700 (PDT)
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 LV3L-rxzv3QX; Thu, 18 Apr 2019 04:48:00 -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 10A20120148; Thu, 18 Apr 2019 04:47:59 -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 x3IBlsQL025975; Thu, 18 Apr 2019 13:47:54 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DE2EF2063BB; Thu, 18 Apr 2019 13:47:54 +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 C736D206275; Thu, 18 Apr 2019 13:47:54 +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 x3IBlsIY021185; Thu, 18 Apr 2019 13:47:54 +0200
To: 神明達哉 <jinmei@wide.ad.jp>
Cc: Pascal Thubert <pthubert@cisco.com>, "<int-dir@ietf.org>" <int-dir@ietf.org>, draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org, its@ietf.org, IETF Discussion <ietf@ietf.org>
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com> <bcb6d12d-5b21-1f10-1afe-221321f8e7a6@gmail.com> <CAJE_bqd5t77B5ij3ot-F-ucx5+3A7LATC-VTBx3w2_kCDD8fNA@mail.gmail.com> <35193c42-44ec-7337-56e6-84df6053843e@gmail.com> <CAJE_bqdkhNFLg9ZT3uSFmjd-+5J78nQTQ8wKDHE8fe2v9Zn8Rg@mail.gmail.com> <35eeeddc-e861-d357-1468-dd853c53ea4d@gmail.com> <CAJE_bqfDPom7+LunUD7XtmcE4kxFFBOcFVe+BgFNejdQNqDn=Q@mail.gmail.com> <973eaac2-9fe7-f438-c0e4-2eeafeec6087@gmail.com> <CAJE_bqeA4xgfWmDQoMNDy86G+5g5HN2-XxHtHdong6Zn1DQ2rA@mail.gmail.com> <bad0ddda-444f-460c-64f9-97d32376fef9@gmail.com> <CAJE_bqd_O_3dD7TzChmhBpScCXXquMZB=wJjVNXMhi=79KbnXg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6b9ed6ed-2f8f-5e4c-b772-5c8d4c883708@gmail.com>
Date: Thu, 18 Apr 2019 13:47:53 +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: <CAJE_bqd_O_3dD7TzChmhBpScCXXquMZB=wJjVNXMhi=79KbnXg@mail.gmail.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/4FQg6FKRg_5_y7mFb2oKAqSV0h8>
Subject: Re: [Int-dir] side note RFC 4291 2nd par sec. 2.1 LL on loopback
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, 18 Apr 2019 11:48:03 -0000


Le 17/04/2019 à 17:20, 神明達哉 a écrit :
> At Wed, 17 Apr 2019 16:33:53 +0200,
> Alexandre Petrescu <alexandre.petrescu@gmail.com 
> <mailto:alexandre.petrescu@gmail.com>> wrote:
> 
>  > >  > [...]> Note also that MacOS is derived from BSD in case you don't
>  > >  > > remember/know it.  And, in fact it also generates both 
> "fe80::1" and
>  > >  > > "::1" on the "lo0" interface.
>  > >  >
>  > >  > Right, I forgot that.
>  > >  >
>  > >  > But there is something I never knew for sure.
>  > >  >
>  > >  > Are BSD flavors supporting OCB options?
>  > >
>  > > I don't know, but I don't think it matters here anyway:
>  >
>  > Maybe it matters, maybe it does not matter.
>  >
>  > If BSD does not support OCB, why should we write an IP-over-OCB spec
>  > along the lines of BSD which does not accept fe80:1::1 in the first 
> place?
> 
> I don't get it.  This sub-thread is not about fe80:1::1 but about
> whether to assign an fe80 address on a loopback interface.
> 
> But to answer the question: because we don't know if that assumption
> holds in future or we don't know if there are other platforms that
> strictly assume the RFC4291 format but yet implement the IP-over-OCB
> spec.

Right, we may expect a future platform to stricly abide to RFC4291, and 
implement OCB too.

For now, we know that linux supports OCB and fe80:1::1.  My trial with 
multiple single-link subnets uses fe80:1::/32, fe80:2::/32 and 
fe80:3::/32.  They are all on linux-based openwrt.

I would like this to interoperate with others and in the future too.

> We should either make IP-over-OCB compliant/consistent with
> existing standards, or make it clear that IP-over-OCB makes an
> exception to the existing standards by formally updating the latter.
> That's, in my understanding, what a responsible spec author of an IETF
> document is supposed to do, especially if they really respect the
> concept of interoperability.  And that's the point of my very first
> message in this entire int-dir thread.

I am interested in interoperability.

I would like to test linux talk to BSD in OCB mode.

The first thing that blocks is lack of OCB support in BSD.  After that 
is fixed we can talk fe80:1::1 in BSD.

Another first thing that blocks is that I do not know how to make an 
"Update: 4291" statement on the first page of this document.

Also, the AD suggestion is to stay silent about plen like 64 or 118 or 
so, and deal with this elsewhere.

Alex
> 
> Frankly, I'm surprised to hear that an author of a would-be standards
> track document says something like this:
> 
>  > If BSD does not support OCB, why should we write an IP-over-OCB spec
>  > along the lines of BSD which does not accept fe80:1::1 in the first 
> place?
> 
> To me, this sounds like the author saying they don't care about
> interoperabitlity beyond the platforms they are interested in.
> 
> --
> JINMEI, Tatuya