IETF Logo Mail Archive

Re: [ipwave] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 09 April 2019 20:04 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 28CCE120325 for <its@ietfa.amsl.com>; Tue, 9 Apr 2019 13:04:25 -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 exwU40d6wCpP for <its@ietfa.amsl.com>; Tue, 9 Apr 2019 13:04:22 -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 8A9461200A2 for <its@ietf.org>; Tue, 9 Apr 2019 13:04:22 -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 x39K4F27080821; Tue, 9 Apr 2019 22:04:15 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5BFA62041B1; Tue, 9 Apr 2019 22:04:15 +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 44FB4201035; Tue, 9 Apr 2019 22:04:15 +0200 (CEST)
Received: from [10.8.68.16] ([10.8.68.16]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x39K4EFX010926; Tue, 9 Apr 2019 22:04:14 +0200
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Suresh Krishnan <Suresh@kaloom.com>
Cc: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>, "its@ietf.org" <its@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "Stanley, Dorothy" <dorothy.stanley@hpe.com>
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com> <9d5c8168-a915-358e-d7eb-0362cad96d81@gmail.com> <27AE185B-1D95-4DCD-8C76-AECE90E46802@cisco.com> <MN2PR11MB35651C4D8957516CF034BFADD8510@MN2PR11MB3565.namprd11.prod.outlook.com> <CALypLp9SuURGJ4f8FBzZg1WQOo9B4xsB8Y4uGW+Jtfm2b=8Sww@mail.gmail.com> <F4BC9027-35E0-4ADB-845A-15B5DD27C069@cisco.com> <64e1744b-6fc6-17b8-0186-399dd0fe91fc@gmail.com> <613CAFD7-ED72-4523-A58F-B5BE6C38448B@kaloom.com> <AD741CB0-4DB1-4B3F-AAD2-4BE27BFBD57C@cisco.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5792fbd4-0a39-0b88-1a8d-f40ab417be89@gmail.com>
Date: Tue, 09 Apr 2019 22:04:14 +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: <AD741CB0-4DB1-4B3F-AAD2-4BE27BFBD57C@cisco.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/TT6Uv4MwYMcO2aeBAy0AdgVyXPQ>
Subject: Re: [ipwave] Intdir early review of draft-ietf-ipwave-ipv6-over-80211ocb-34
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: Tue, 09 Apr 2019 20:04:25 -0000

Pascal,

Le 09/04/2019 à 18:50, Pascal Thubert (pthubert) a écrit :
[...]

> At the end of the day I’m not clear why we want to publish it. Maybe
> as an informational description of OCB to prepare for the work in the
> WG?

There were about 3 bofs on this and long discussions on chartering or no 
chartering, and what to charter.

Your comment above sounds to me as if we wanted to charter again now.

> I’d be fine with that but then the title should change.

I think this is not serious.  We changed the title many times.  The last 
title was contributed extensively by a very knowledgeable person.

This makes me say the following:

I would like to ask you something else: why do you insist so much on 
this?  What fundamental issue you think is at stake (beyond text or RFC 
referrals)?  Sounds as if you have some other strong reason pushing you 
to ask these things...  maybe some personal issue against me, or some 
other interest?

Alex

> 
> All the best,
> 
> Pascal
> 
>> Le 10 avr. 2019 à 00:05, Suresh Krishnan <Suresh@kaloom.com> a
>> écrit :
>> 
>> Hi Pascal/Alex, Upleveling this a bit.
>> 
>>> On Apr 9, 2019, at 9:54 AM, Alexandre Petrescu
>>> <alexandre.petrescu@gmail.com> wrote:
>>> 
>>> 
>>> 
>>>> Le 09/04/2019 à 02:04, Pascal Thubert (pthubert) a écrit : 
>>>> Hello Carlos I think we’re a bit stuck. I spent really a long
>>>> time explaining why RFC 4861 does not cut it
>>> 
>>> Pascal, with all due respect.
>>> 
>>> You seem to be claiming RFC4861 does not work on WiFi
>>> altogether.
>>> 
>>> Is it so?
>> 
>> Pascal, we do know that RFC4861 ND *does* work on 802.11 OCB
>> networks as witnessed by the several existing implementations. Of
>> course, there are cases where it may may be sub optimal and this is
>> why I was fine with explaining some of the shortfalls with an
>> informational pointer to RFC8505 (Thanks for helping with the
>> text!! I think it provides a great overview). I personally do not
>> think mandating RFC8505 is warranted at this point.
>> 
>> Thanks Suresh

v2.23.0 | Report a Bug | By Email