Re: [ipwave] I-D Action: draft-ietf-ipwave-ipv6-over-80211ocb-01.txt - Ethernet Adaptation Layer

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 12 March 2017 16:57 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 DEC8C129412 for <its@ietfa.amsl.com>; Sun, 12 Mar 2017 09:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level:
X-Spam-Status: No, score=-0.333 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, SPF_SOFTFAIL=0.665] autolearn=no 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 jrWANqPZ6cGD for <its@ietfa.amsl.com>; Sun, 12 Mar 2017 09:57:15 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 EA18F1293F4 for <its@ietf.org>; Sun, 12 Mar 2017 09:57:14 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v2CGv8d7048266; Sun, 12 Mar 2017 17:57:08 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BC064202F08; Sun, 12 Mar 2017 17:57:08 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id AEA02201555; Sun, 12 Mar 2017 17:57:08 +0100 (CET)
Received: from [132.166.84.164] ([132.166.84.164]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v2CGv7Sx011786; Sun, 12 Mar 2017 17:57:08 +0100
To: dickroy@alum.mit.edu
References: <148760815996.26105.11019844131535465220.idtracker@ietfa.amsl.com> <81bdbc7d-73b5-3d80-652b-a5bdcafe6b7e@cea.fr> <1581897D14634B82A973F515F80C082F@SRA6>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <4f043b87-ad8f-7b29-8b20-17599703aec6@gmail.com>
Date: Sun, 12 Mar 2017 17:57:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <1581897D14634B82A973F515F80C082F@SRA6>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/cu8En6V1Sko2bj4YpgHnOHVDgZ8>
Cc: "its@ietf.org" <its@ietf.org>
Subject: Re: [ipwave] I-D Action: draft-ietf-ipwave-ipv6-over-80211ocb-01.txt - Ethernet Adaptation Layer
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 12 Mar 2017 16:57:17 -0000

Dick,

I hope now your postings will show up on the email list.

Le 21/02/2017 à 03:47, Dick Roy a écrit :
> Alex,
>
> Attached is a doc with some of my initial comments. I thought I
> should get it to you ASAP as there are significant issues surrounding
> the LLC sublayer and EPD operation throughout the draft that should
> be fixed.  In particular, the Ethernet Adaptation Layer doesn't
> really exist above the 802.11 MAC sublayer ... anywhere.  It's all
> LLC sublayer operation.  The adaptation to which you refer happens in
> bridges that connect 802.11 links to Ethernet-based LANs.

The "Ethernet Adaptation Layer" I am describing is a new name.  But the 
behaviour is there for many years in implementations.

Implementations adapt between 802.11 Headers and Ethernet II Headers.

This adaptation is not only happening in a bridge.  It als happening in 
a computer with a single WiFi interface: the Ethernet Adaptation Layer 
adapts between 802.11 Headers and EthernetII Headers in that computer.

The IP stack sees only the EthernetII Headers.  This is illustrated in 
the following figure copied from the draft.

Do you agree with this concept of "Ethernet Adaptation Layer"?


            +--------------------+-------------+-------------+---------+
            | 802.11 Data Header | LLC Header  | IPv6 Header | Payload |
            +--------------------+-------------+-------------+---------+
                             ^
                             |
                             802.11-to-Ethernet Adaptation Layer
                             |
                             v

            +---------------------+-------------+---------+
            | Ethernet II Header  | IPv6 Header | Payload |
            +---------------------+-------------+---------+

Alex

>
> Cheers,
>
> RR
>
> -----Original Message----- From: its [mailto:its-bounces@ietf.org] On
> Behalf Of Alexandre Petrescu Sent: Monday, February 20, 2017 8:41 AM
> To: its@ietf.org Subject: Re: [ipwave] I-D Action:
> draft-ietf-ipwave-ipv6-over-80211ocb-01.txt
>
> Hello IPWAVErs,
>
> I submitted this -01 version addressing comments we received so far:
> https://tools.ietf.org/html/draft-ietf-ipwave-ipv6-over-80211ocb-01
>
> Please comment.  We could still discuss and make a better -02 before
> the deadline for Chicago.
>
> This is the changelog: o Introduced message exchange diagram
> illustrating differences between 802.11 and 802.11 in OCB mode. o
> Introduced an appendix listing for information the list of 802.11
> messages that may be transmitted in OCB mode. o Removed appendix
> sections "Privacy Requirements", "Authentication Requirements" and
> "Security Certificate Generation". o Removed appendix section "Non IP
> Communications". o Introductory phrase in the Security Considerations
> section. o Improved the definition of "OCB". o Introduced theoretical
> stacked layers about IPv6 and IEEE layers including EPD. o Removed
> the appendix describing the details of prohibiting IPv6 on certain
> channels relevant to 802.11-OCB. o Added a brief reference in the
> privacy text about a precise clause in IEEE 1609.3 and .4. o
> Clarified the definition of a Road Side Unit. o Removed the
> discussion about security of WSA (because is non-IP). o Removed
> mentioning of the GeoNetworking discussion. o Moved references to
> scientific articles to a separate 'overview' draft, and referred to
> it.
>
> Alex
>
> Le 20/02/2017 à 17:29, internet-drafts@ietf.org a écrit :
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>> This draft is a work item of the IP Wireless Access in Vehicular
> Environments of the IETF.
>>
>> Title           : Transmission of IPv6 Packets over IEEE 802.11
> Networks in mode Outside the Context of a Basic Service Set
> (IPv6-over-80211ocb)
>> Authors         : Alexandre Petrescu Nabil Benamar Jérôme Härri
>> Christian Huitema Jong-Hyouk Lee Thierry Ernst Tony Li Filename
>> : draft-ietf-ipwave-ipv6-over-80211ocb-01.txt Pages           : 32
>> Date            : 2017-02-20
>>
>> Abstract: In order to transmit IPv6 packets on IEEE 802.11 networks
>> run outside the context of a basic service set (OCB, earlier
>> "802.11p") there is a need to define a few parameters such as the
>> recommended Maximum Transmission Unit size, the header format
>> preceding the IPv6 header, the Type value within it, and others.
>> This document describes these parameters for IPv6 and IEEE 802.11
>> OCB networks; it portrays the layering of IPv6 on 802.11 OCB
>> similarly to other known 802.11 and Ethernet layers - by using an
>> Ethernet Adaptation Layer.
>>
>> In addition, the document attempts to list what is different in
>> 802.11 OCB (802.11p) compared to more 'traditional' 802.11a/b/g/n
>> layers, layers over which IPv6 protocols operates without issues.
>> Most notably, the operation outside the context of a BSS (OCB) has
>> impact on IPv6 handover behaviour and on IPv6 security.
>>
>> An example of an IPv6 packet captured while transmitted over an
>> IEEE 802.11 OCB link (802.11p) is given.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-ipwave-ipv6-over-80211ocb/
>>
>>
>>
There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-ipwave-ipv6-over-80211ocb-01
>>
>>
>>
A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-ipwave-ipv6-over-80211ocb-01
>>
>>
>>
>>
Please note that it may take a couple of minutes from the time of
> submission
>> until the htmlized version and diff are available at
>> tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________ I-D-Announce
>> mailing list I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft
>> directories: http://www.ietf.org/shadow.html or
>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>