[netext] updated draft on requirements imposed by traffic safety applications on network/transport layers

"Georgios Karagiannis" <karagian@cs.utwente.nl> Wed, 28 October 2009 07:58 UTC

Return-Path: <karagian@cs.utwente.nl>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E83EB3A68DB for <netext@core3.amsl.com>; Wed, 28 Oct 2009 00:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.097
X-Spam-Level:
X-Spam-Status: No, score=0.097 tagged_above=-999 required=5 tests=[AWL=0.601, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 zJ2QqR2YmNu3 for <netext@core3.amsl.com>; Wed, 28 Oct 2009 00:58:18 -0700 (PDT)
Received: from rotterdam.ewi.utwente.nl (rotterdam.ewi.utwente.nl [130.89.10.5]) by core3.amsl.com (Postfix) with ESMTP id 7D2F13A6881 for <netext@ietf.org>; Wed, 28 Oct 2009 00:58:18 -0700 (PDT)
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26]) by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id n9S7wUW5011588; Wed, 28 Oct 2009 08:58:31 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap1.ewi.utwente.nl) by webmail.cs.utwente.nl with HTTP; Wed, 28 Oct 2009 07:58:30 +0000
To: netext@ietf.org
Date: Wed, 28 Oct 2009 07:58:30 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <k5IAaTN6.1256716710.2427960.karagian@ewi.utwente.nl>
In-Reply-To: <s5FNohOR.1256715576.5370620.karagian@ewi.utwente.nl>
From: Georgios Karagiannis <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Errors-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (rotterdam.ewi.utwente.nl [130.89.10.5]); Wed, 28 Oct 2009 08:58:33 +0100 (MET)
Cc: "ryuji@jp.toyota-itc.com" <ryuji@jp.toyota-itc.com>, "john@jbkenney.com" <john@jbkenney.com>
Subject: [netext] updated draft on requirements imposed by traffic safety applications on network/transport layers
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2009 07:58:19 -0000

Hi all

An updated version of an Internet draft has been submitted to the IETF
that describes a number of communication performance requirements that
are imposed by traffic safety applications on a network layer,
see:
http://www.ietf.org/id/draft-karagiannis-traffic-safety-requirements-01.txt

These traffic safety applications and requirements have been derived by
the USA VSC (Vehicular Safety Communications)and VSC-A
(VSC-Applications) projects and by the European Car to Car Communication
Consortium (C2C-CC) and the ETSI TC ITS standardization body. The goal
of this document is to stimulate the discussion on judging whether these
performance requirements could or could not be supported (currently and
in the future) by IP based network solutions.

The goal of this document is to stimulate the discussion on judging
whether these performance requirements could or could not be supported
(currently and in the future) by IP based network and transport
solutions.

Best regards,
Georgios