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

["Ivancic, William D. (GRC-RHN0)" <[e-mail]>]

Alex,

I think you might want to consider writing the requirements to be a little more generic.  As is, at least to me, some of the requirements almost specify a solution.  This is a always a bit difficult as you may have a solution in mind, but others may have a different solution that may be better.  If the requirements are more generic to the problem rather than specifying a solution, you allow a broader solution space.  I tired some modifications below.

Also, I moved R3 before R0-2.

   o  R0.  Support of multiple interfaces: The vehicle (not restricted
      to the MR physically) should support several interfaces towards
      the infrastructure. And at least one internal to the vehicle.

o  R1.  IP addressing within each vehicle for Sub-networks support: Mobile router support several sub-networks hosting stakeholder networks,

   o  R2.  IP addressing on the interface between vehicles. (May or may not be globally reachable)

   o  R3.  Globally Reachable from Internet: (This may be a globally reachable address, or perhaps something else.)



   o  R4.  Quality of Service: One stakeholder may request for a minimum
      bandwidth for its applications.  QoS should ensure those minimums
      are taken into accounts.

   o  R5.  Broadcasted Alerts support: For example, Along the highway, the MR may
      receive alerts about accident through 802.11p or some other mechanism.

   o  R6.  Store, Carry and Forward: Improve communication efficiency by
      delaying transfer of information.

   o  R7.  Efficient inter-vehicular routing: For Example, may take advantage of geographic information (not
      restricted to geonetworking).

   o  R8.  Security: MR must prevent routing of packets between sub
      networks and ensure protection of those data within the vehicle.

   o  R9.  Continuity of ongoing sessions: it is desirable that ongoing
      sessions between one device within the vehicle and one device in
      the Internet is maintained ongoing during vehicle movements, and
      upon handovers between heterogeneous access points.

   o  R10.  Reachability at permanent home addresses: it is desirable
      that each device connected inside a vehicle to be reachable at a
      permanent fixed address, for all other IP devices deployed in the
      Internet.    (I think R3 takes care of this.)





On Jul 13, 2012, at 1:04 PM, Alexandru Petrescu wrote:

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.

From: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Date: July 13, 2012 1:01:02 PM EDT
To: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Subject: New Version Notification for draft-petrescu-its-scenarios-reqs-01.txt



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


_______________________________________________
its mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/its

******************************
William D. Ivancic
Phone [phone]
Fax [phone]
Networking Lab 216-433-2620
Mobile [phone]
http://roland.grc.nasa.gov/~ivancic