Re: [ipwave] 118

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 19 April 2019 08:51 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA8B512008F; Fri, 19 Apr 2019 01:51:09 -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 NRorPzjkOnnA; Fri, 19 Apr 2019 01:51:07 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 0B8D6120044; Fri, 19 Apr 2019 01:51:06 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3J8p4pv015867; Fri, 19 Apr 2019 10:51:04 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 21C9A2030A8; Fri, 19 Apr 2019 10:51:04 +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 0ACFD203027; Fri, 19 Apr 2019 10:51:04 +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 x3J8p3Dh003353; Fri, 19 Apr 2019 10:51:03 +0200
To: 神明達哉 <jinmei@wide.ad.jp>
Cc: draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org, "Joel M. Halpern" <jmh@joelhalpern.com>, IETF Discussion <ietf@ietf.org>, its@ietf.org, "<int-dir@ietf.org>" <int-dir@ietf.org>
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com> <b2459889-f8d6-43c0-acc2-2ffe00fb1985@gmail.com> <26900f46-88da-cf3e-9ae0-b23e056ee840@gmail.com> <ad32743d-981a-0ae7-a6ca-f7a4e9841831@gmail.com> <ece445c6-d599-152c-80aa-670495cbb64d@gmail.com> <CAJE_bqdVqPT761+59TOPHXnr5RqtjNk6WAA81_jZAogGqpJX2A@mail.gmail.com> <350c5cf2-b338-047d-e99b-db6d6a4f6574@gmail.com> <4b717f2c-e8b3-8a47-96d4-67901a98c15f@gmail.com> <f3f722c3-ace5-2e9a-7aaa-30cdc6b5980c@joelhalpern.com> <374342fd-0cf6-30ab-94ae-ef401b005c08@gmail.com> <CAJE_bqcft94gRMUA4Xdq3zzEwZGBxcarZfSQn_HzDoeJ9m=MZg@mail.gmail.com> <2c4dd3e9-90ff-e2d3-5461-f55dcf45717f@gmail.com> <CAJE_bqfd_YQeYrdh9HCu-3mkWmrbAomcL10p1VPG4eaW1gwfRA@mail.gmail.com> <da98f944-bb9e-04b7-ed45-f8fbb11c45ea@gmail.com> <CAJE_bqdb+Uj4+imD5pycBgXkJxiuJsMBKf+jByaYmCtwqLayTg@mail.gmail.com> <a512529d-0d36-efc8-c231-73421c63d9ec@gmail.com> <CAJE_bqd_0kqqNnHww9-bzN7P_d7LvZnSFCHD1DzEwSMpd7sWBA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <1a5503c2-7bed-06bd-ba29-3f9e84f07d13@gmail.com>
Date: Fri, 19 Apr 2019 10:51:03 +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_0kqqNnHww9-bzN7P_d7LvZnSFCHD1DzEwSMpd7sWBA@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/its/qFf0XjEikhiax7eINhhm73Qztvg>
Subject: Re: [ipwave] 118
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2019 08:51:10 -0000


Le 18/04/2019 à 23:56, 神明達哉 a écrit :
> At Thu, 18 Apr 2019 23:44:54 +0200,
> Alexandre Petrescu <alexandre.petrescu@gmail.com 
> <mailto:alexandre.petrescu@gmail.com>> wrote:
> 
>  > > of course not.  But I expect your proposal will be quite controversial
>  > > and take a long time.  I also admit I *expect* its odds are low and 
> it's
>  > > quite possible that you end up falling back to the status quo;
>  > > changing a long standing standard is always hard.  But that doesn't
>  > > mean I *hope* it will fail (also, my expectation can prove incorrect).
>  >
>  > This is a structural problem.
>  >
>  > If you direct us to 6MAN and know and assume the variable len IID gets
>  > stuck there then you should not direct as there.
> 
> Actually, that's exactly why my primary suggestion is to stick to the
> status quo for now.  Changing the status quo needs a discussion at
> 6man, and it will take long time and can possibly fail, so if you want
> to avoid the delay, the only feasible option for now is to stick to
> the status quo and defer any incremental changes to that separate
> discussion.  Hence the suggestion.  I believe I've always been clear
> about it, hiding nothing.
> 
> And it's now your call.  If you don't like to go with the status quo
> for now and do believe you can get a quick consensus at 6man, I just
> wish you a good luck.

The status quo is the following: the IP-over-OCB does not specify the 
len of  IID.  It refers to "other documents".

If we go to 6man is to get 6man consensus and quickly.  Otherwise we 
dont go there.

If you, or the AD think we could not get consensus there, then you, or 
the AD, should not direct us there.

We could stay here and write IID len is 118.  At that point it should be 
6man who should come here and see whether 6man gets consensus here.

Alex
> 
> --
> JINMEI, Tatuya