[its] Scenarios, potential topics...

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 16 March 2012 12:38 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 3925221F8573 for <its@ietfa.amsl.com>; Fri, 16 Mar 2012 05:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.118
X-Spam-Level:
X-Spam-Status: No, score=-7.118 tagged_above=-999 required=5 tests=[AWL=-0.869, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 yqrzXyxiC9yI for <its@ietfa.amsl.com>; Fri, 16 Mar 2012 05:38:57 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.144]) by ietfa.amsl.com (Postfix) with ESMTP id 16E2321F8575 for <its@ietf.org>; Fri, 16 Mar 2012 05:38:53 -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 q2GCcr3N016294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <its@ietf.org>; Fri, 16 Mar 2012 13:38:53 +0100
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 q2GCcqx5032247 for <its@ietf.org>; Fri, 16 Mar 2012 13:38:52 +0100 (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 q2GCcnwt019020 for <its@ietf.org>; Fri, 16 Mar 2012 13:38:52 +0100
Message-ID: <4F633459.9080106@gmail.com>
Date: Fri, 16 Mar 2012 13:38:49 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: its@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [its] Scenarios, potential topics...
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, 16 Mar 2012 12:38:58 -0000

Welcome to the ITS list at IETF, an informal discussion.

Earlier at IETF discussions related to vehicular communications happened
in several groups (MEXT, AUTOCONF, 6MAN, to name but a few), drafts were
published [*].  At times people expressed interest to meet f2f.  Now
there is this email list.

Participants are solicited to work on the topic of using IP in
Intelligent Transportation Systems.  The term ITS is a placeholder that,
in my oppinion, is generic enough to cover many aspects of vehicular
communications; vehicles may be wheeled, watered, flown.  Ambulance,
fire engine, coastal ship are particular examples.

Scenario :  A router deployed in a moving vehicle, uses its egress
interface to connect to larger-area access network(s) or to other
vehicles.  Should it use IPv6-over-LTE?  Should it use Mobile IP?

Example potential work items:
- Reqs for IPv6 in vehicular networks
- V2V with RA
- V2R(oadside)
- VIN and IPv6 addressing
- ULA and IPv6 for vehicles
- IPv6 multicast
- ISO TC204
- IPv6 over 802.11p (IPv6-over-foo).
- open.

I am told about other vehicular drafts and discussions, that I have not
cited, existed and still exist (about e.g. ecall).  I am interested to
learn about all the vehicular activities at IETF.

Relevant std works: IEEE 802.11p, 802.22, ETSI ITS, ISO.

Open to discussion: what are the scenarios?  What are the potential work
items?  What might be needed, if anything at all?

Alex
[*]
draft-ietf-mext-nemo-ro-automotive-req-02
draft-jhlee-mext-mnpp-00.txt, October 2009.
draft-ietf-mext-nemo-ro-automotive-req-02, Jan. 2009.
draft-karagiannis-traffic-safety-requirements-02.txt, Feb. 2010.
draft-wakikawa-roll-invehicle-reqs-00.txt, May 2008.
draft-petrescu-autoconf-ra-based-routing-01.txt, Feb. 2011.
draft-petrescu-mip4-tuntype-change-00.txt, March 2011.
draft-uehara-dtnrg-decentralized-probe-message-00.txt, Nov. 2010.
draft-uehara-dtnrg-decentralized-probe-transport-00, Nov. 2010
draft-rosen-ecrit-ecall-04.txt, March 2010.
draft-singh-simple-vehicle-info, July 2007.
draft-sijeon-mext-nemo-pmip6-00, Oct. 2010.
draft-bauer-mext-aero-solspace, Sep. 2009.
draft-bauer-mext-aero-topology, Sep. 2009.
draft-bernardos-mext-aero-nemo-ro-sol-analysis, Nov. 2008.
draft-rosen-ecrit-ecall-05.txt, March 2012.