Re: [MEXT] non-IETF standards for draft-ietf-mext-nemo-ro-automotive-req-01.txt
Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 05 December 2008 15:58 UTC
Return-Path: <mext-bounces@ietf.org>
X-Original-To: monami6-archive@megatron.ietf.org
Delivered-To: ietfarch-monami6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id B713F3A67AE;
Fri, 5 Dec 2008 07:58:59 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 5545B3A67AE
for <mext@core3.amsl.com>; Fri, 5 Dec 2008 07:58:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.872
X-Spam-Level:
X-Spam-Status: No, score=-5.872 tagged_above=-999 required=5 tests=[AWL=0.727,
BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id ifmxj6yNnS-0 for <mext@core3.amsl.com>;
Fri, 5 Dec 2008 07:58:57 -0800 (PST)
Received: from mail128.messagelabs.com (mail128.messagelabs.com
[216.82.250.131])
by core3.amsl.com (Postfix) with SMTP id 9DAB93A63D3
for <mext@ietf.org>; Fri, 5 Dec 2008 07:58:57 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-10.tower-128.messagelabs.com!1228492732!18309276!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [136.182.1.14]
Received: (qmail 23615 invoked from network); 5 Dec 2008 15:58:52 -0000
Received: from unknown (HELO motgate4.mot.com) (136.182.1.14)
by server-10.tower-128.messagelabs.com with SMTP;
5 Dec 2008 15:58:52 -0000
Received: from il27exr03.cig.mot.com (il27exr03.mot.com [10.17.196.72])
by motgate4.mot.com (8.12.11/Motorola) with ESMTP id mB5FwqeX017694;
Fri, 5 Dec 2008 08:58:52 -0700 (MST)
Received: from il27vts02.mot.com (il27vts02.cig.mot.com [10.17.196.86])
by il27exr03.cig.mot.com (8.13.1/Vontu) with SMTP id mB5FwqnJ026446;
Fri, 5 Dec 2008 09:58:52 -0600 (CST)
Received: from [127.0.0.1] ([10.161.201.117])
by il27exr03.cig.mot.com (8.13.1/8.13.0) with ESMTP id mB5FwpcS026435;
Fri, 5 Dec 2008 09:58:51 -0600 (CST)
Message-ID: <49394FBA.9080806@gmail.com>
Date: Fri, 05 Dec 2008 16:58:50 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Roberto Baldessari <Roberto.Baldessari@nw.neclab.eu>
References: <547F018265F92642B577B986577D671C4FBFEE@VENUS.office>
In-Reply-To: <547F018265F92642B577B986577D671C4FBFEE@VENUS.office>
X-Antivirus: avast! (VPS 081204-0, 04/12/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: mext <mext@ietf.org>
Subject: Re: [MEXT] non-IETF standards for
draft-ietf-mext-nemo-ro-automotive-req-01.txt
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>,
<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>,
<mailto:mext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org
Dear Roberto, Roberto Baldessari wrote: [...] > IEEE 802.11p and IEEE 1609.X are two separate standard drafts. The > 1609 family specifies additional protocols (WSMP) and mechanisms to > be used on top/in combination of/with 802.11p. In Europe 1609 does > not have much consensus for various reasons. ETSI is likely to make a > profile of 802.11p and redefine some functionalities that are offered > by 1609 but in a different way. Further, 11p and 1609 are going to > change. The latest 11p version is D4.02, Sept 2008. Please send me in private 11p D4.02 dated September 2008. > To cut the story short, 1609 is not assumed in the draft. Feel free > to contact me offline if you need more info (I feel we're getting out > of scope of this ML). I need to identify precisely what can be done in IETF MEXT about: 1609, 11p and ETSI European Profile. I will contact you in private about these documents. Alex ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ MEXT mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
- [MEXT] Comments on draft-ietf-mext-nemo-ro-automo… Alexandru Petrescu
- Re: [MEXT] Comments on draft-ietf-mext-nemo-ro-au… Roberto Baldessari
- Re: [MEXT] Comments on draft-ietf-mext-nemo-ro-au… Alexandru Petrescu
- Re: [MEXT] Comments on draft-ietf-mext-nemo-ro-au… Roberto Baldessari
- Re: [MEXT] non-IETF standards for draft-ietf-mext… Alexandru Petrescu
- [MEXT] Comments on draft-ietf-mext-nemo-ro-automo… Carlos Jesús Bernardos Cano