[its] New draft on scenarios and requirements for IP in ITS

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 13 July 2012 17:03 UTC

Return-Path: <alexandru.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 266D311E8114 for <its@ietfa.amsl.com>; Fri, 13 Jul 2012 10:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.999
X-Spam-Level:
X-Spam-Status: No, score=-4.999 tagged_above=-999 required=5 tests=[AWL=-2.750, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCcCyZLuUSFk for <its@ietfa.amsl.com>; Fri, 13 Jul 2012 10:03:58 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 27F3711E808F for <its@ietf.org>; Fri, 13 Jul 2012 10:03:57 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id q6DH4Xa9015145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <its@ietf.org>; Fri, 13 Jul 2012 19:04:33 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id q6DH4XZT018157 for <its@ietf.org>; Fri, 13 Jul 2012 19:04:33 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id q6DH4Tng016407 for <its@ietf.org>; Fri, 13 Jul 2012 19:04:33 +0200
Message-ID: <5000551E.9000800@gmail.com>
Date: Fri, 13 Jul 2012 19:04:30 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "its@ietf.org" <its@ietf.org>
Content-Type: multipart/mixed; boundary="------------010007020506010809070902"
Subject: [its] New draft on scenarios and requirements for IP in ITS
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Intelligent Transportation Systems discussion list." <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 13 Jul 2012 17:03:59 -0000

Participants to ITS informal effort at IETF,

Per our recent discussions, we submitted a new draft about scenarios and
requirements for IP in ITS:

          draft-petrescu-its-scenarios-reqs-01.txt

I would like to request feedback about the scenarios and requirements
described in this draft.

Thanks in advance,

Alex and on behalf of co-authors.
--- Begin Message ---
A new version of I-D, draft-petrescu-its-scenarios-reqs-01.txt
has been successfully submitted by Alexandru Petrescu and posted to the
IETF repository.

Filename:	 draft-petrescu-its-scenarios-reqs
Revision:	 01
Title:		 Scenarios and Requirements for IP in Intelligent Transportation Systems
Creation date:	 2012-07-13
WG ID:		 Individual Submission
Number of pages: 12
URL:             http://www.ietf.org/internet-drafts/draft-petrescu-its-scenarios-reqs-01.txt
Status:          http://datatracker.ietf.org/doc/draft-petrescu-its-scenarios-reqs
Htmlized:        http://tools.ietf.org/html/draft-petrescu-its-scenarios-reqs-01
Diff:            http://tools.ietf.org/rfcdiff?url2=draft-petrescu-its-scenarios-reqs-01

Abstract:
   This draft describes scenarios of vehicular communications that are
   considered pertinent to Intelligent Transportation Systems.  In these
   scenarios, the necessity of using IP networking technologies and
   protocols is exposed.

                                                                                  


The IETF Secretariat
--- End Message ---