[ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 ETSI CAM and IP

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 12 February 2017 18: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 CB0C01299DC for <its@ietfa.amsl.com>; Sun, 12 Feb 2017 10:50:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.997
X-Spam-Level:
X-Spam-Status: No, score=-5.997 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=-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 z-6ppsq45lbN for <its@ietfa.amsl.com>; Sun, 12 Feb 2017 10:50:41 -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 6116A1299DA for <its@ietf.org>; Sun, 12 Feb 2017 10:50:41 -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 v1CIodVs008609 for <its@ietf.org>; Sun, 12 Feb 2017 19:50:39 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 70F55205B17 for <its@ietf.org>; Sun, 12 Feb 2017 19:50:39 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 661BF203A19 for <its@ietf.org>; Sun, 12 Feb 2017 19:50:39 +0100 (CET)
Received: from [132.166.84.15] ([132.166.84.15]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v1CIoc3R031781 for <its@ietf.org>; Sun, 12 Feb 2017 19:50:39 +0100
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: "its@ietf.org" <its@ietf.org>
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com>
Organization: CEA
Message-ID: <c8c079ab-1417-be34-a2bc-cd2c3b781b85@cea.fr>
Date: Sun, 12 Feb 2017 19:50:07 +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: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040002020208050304050206"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/xWMMyqHDEE2G_c_uvS3UklZZ-M4>
Subject: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 ETSI CAM and IP
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 Feb 2017 18:50:43 -0000

draft-ietf-ipwave-ipv6-over-80211ocb-00
ETSI CAM and IP

It has been commented, that to the best of one's reading, the
ETSI ITS documents do not specify what is the protocol that should be
used to encapsulate CAMs.  This leads to wonder whether or not IP can be
used to transport CAMs, and, if not - why not?

The ETSI documents having been reviewed are the following:
ETSI TS 102 637-2
ETSI EN 302 665

In this draft, the old text is the following:
> D.2. Non IP Communications
>
> In IEEE 1609 and ETSI ITS, safety-related communications CANNOT be
> used with IP datagrams. For example, Basic Safety Message (BSM, an
> IEEE 1609 datagram) and Cooperative Awareness Message (CAM, an ETSI
> ITS-G5 datagram), are each transmitted as a payload that is preceded
> by link-layer headers, without an IP header.

I propose the following new text:
> D.2. Non IP Communications
>
> In IEEE 1609 and ETSI ITS, safety-related communications MAY NOT be
> used with IP datagrams. For example, Basic Safety Message (BSM, an
> IEEE 1609 datagram), are each transmitted as a payload that is preceded
> by link-layer headers, without an IP header.

(remark "MAY NOT" instead of CANNOT, and CAM absence).

Alex