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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 06 March 2019 15:15 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 7110F1275E9 for <its@ietfa.amsl.com>; Wed, 6 Mar 2019 07:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.126
X-Spam-Level:
X-Spam-Status: No, score=-0.126 tagged_above=-999 required=5 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.972] 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 ATM1oQKRUqFP for <its@ietfa.amsl.com>; Wed, 6 Mar 2019 07:15:05 -0800 (PST)
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 7F41E12705F for <its@ietf.org>; Wed, 6 Mar 2019 07:15:05 -0800 (PST)
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 x26FF06i015082; Wed, 6 Mar 2019 16:15:00 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8301E201A0E; Wed, 6 Mar 2019 16:15:00 +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 753D6206F5D; Wed, 6 Mar 2019 16:15:00 +0100 (CET)
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 x26FF0Na022423; Wed, 6 Mar 2019 16:15:00 +0100
To: Pascal Thubert <pthubert@cisco.com>
Cc: its@ietf.org
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c5b1034b-e13c-6a16-e440-2e94918afbe7@gmail.com>
Date: Wed, 06 Mar 2019 16:15:00 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2
MIME-Version: 1.0
In-Reply-To: <155169869045.5118.3508360720339540639@ietfa.amsl.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/I348DwTKCNzxARt0ene_tAV0TWw>
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: Wed, 06 Mar 2019 15:15:07 -0000

Hi Pascal,

Le 04/03/2019 à 12:24, Pascal Thubert a écrit :
[...]
> "   An 'adaptation' layer is inserted between a MAC layer and the
>     Networking layer.  This is used to transform some parameters between
>     their form expected by the IP stack and the form provided by the MAC
>     layer.
> "
> Is this different from what an AP does when it bridges Wi-Fi to Ethernet? Is
> this IETF business?

No and yes:

No, this Ethernet Adaptation Layer is not different from what an AP does 
when it bridges WiFi to Ethernet.  All Access Points do this Ethernet 
Adaptation Layer.

Yes, it is debatable whether it is an IETF or IEEE business, but I tend 
to say it is an IETF business now.  There are three reasons for that:

1. IETF recently defined such adaptation layers several times (6lowpan 
comes to mind and more).

2. IEEE does not define such an adaptation layer - there is no IEEE 
document that describes in a manner that a simple programmer understands 
how this adaptation layer works (some have referred informally to IEEE 
'bridging' topic but I did not see that document myself).

3. not least, a particular field that this Ethernet Adaptation Layer 
(EAL) must fill is ethertype 0x86dd, whose value _is_ more under the 
authority of IETF than of IEEE.

Do you think otherwise?

Alex
[...]