IETF Logo Mail Archive

Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 calling Ethernet Adaptation Layer a name

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 01 February 2017 12:50 UTC

Return-Path: <alexandre.petrescu@cea.fr>
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 84DCA129D9F for <its@ietfa.amsl.com>; Wed, 1 Feb 2017 04:50:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.195
X-Spam-Level:
X-Spam-Status: No, score=-9.195 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.199] autolearn=unavailable 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 AeP6eDcmV9Rj for <its@ietfa.amsl.com>; Wed, 1 Feb 2017 04:50:15 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85FF6129D8D for <its@ietf.org>; Wed, 1 Feb 2017 04:44:48 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id v11CikMO010108 for <its@ietf.org>; Wed, 1 Feb 2017 13:44:46 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5805F2043EA for <its@ietf.org>; Wed, 1 Feb 2017 13:44:46 +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 4D50F202D2C for <its@ietf.org>; Wed, 1 Feb 2017 13:44:46 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v11Cik6e009661 for <its@ietf.org>; Wed, 1 Feb 2017 13:44:46 +0100
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <c5e320a9-6c3d-17bc-bbee-1994ffd3f7a4@gmail.com> <51c7f6d4-a998-bc91-1b01-3b9f06fb61fc@fischer-tech.eu>
Organization: CEA
To: its@ietf.org
Message-ID: <ef8b5c3e-1fe3-1486-d087-fe89f1c7f281@cea.fr>
Date: Wed, 01 Feb 2017 13:44:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <51c7f6d4-a998-bc91-1b01-3b9f06fb61fc@fischer-tech.eu>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms020307050608020300050404"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/Sb7NjahfaMzC4IaRNphwSSoydzQ>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 calling Ethernet Adaptation Layer a name
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: Wed, 01 Feb 2017 12:50:16 -0000

Dear IPWAVErs,

The current draft says in abstract:
> [...] 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.

A commenter said:
> Since the IETF ipwave scope is to address IPv6 over 802.11 OCB,
> assuming that the OSI model is used, the boundary on the data plane
> is the LLC SAP (LLC / Higher Layer boundary).  This is the
> “line-in-the-sand”.

IMHO the Ethernet Adaptation Layer is a name I invented to describe what
happens when computers change between 802.11 headers and wired-Ethernet
headers.

The "line in the sand" term is very suggestive as well.

The ISO term "LLC to SAP" interface, or "LLC to Higher Layer" boundary
is also good.

At this time I am tempted to continue calling it an "Ethernet Adaptation
Layer", because at IETF there are other such adaptation layers (e.g.
LoWPAN adaptation layer for IPv6 over 802.15.4 in RFC4944).

Alex

v2.23.0 | Report a Bug | By Email