One document matched: draft-petrescu-its-scenarios-reqs-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" []>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>

<rfc category="info"
     docName="draft-petrescu-its-scenarios-reqs-00.txt"
     ipr="trust200902">

  <!-- category values: std, bcp, info, exp, and historic ipr values:
       trust200902, noModificationTrust200902,
       noDerivativesTrust200902, or pre5378Trust200902 you can add the
       attributes updates="NNNN" and obsoletes="NNNN" they will
       automatically be output with "(if approved)" -->

  <front>

    <title abbrev="Scenarios and Reqs for IP in ITS">
      Scenarios and Requirements
      for IP in Intelligent Transportation
      Systems
    </title>

    <author initials='A.' surname="Petrescu" fullname='Alexandru Petrescu'>
      <organization>CEA</organization>
      <address>
	<postal>
	  <street>
	    Communicating Systems Laboratory, Point Courrier 173
	  </street>
	  <city>
	    Palaiseau
	  </city>
	  <region>
	  </region>
	  <code>
	    F-91120
	  </code>
	  <country>
	    France
	  </country>
	</postal>
	<phone>
	  +33(0)169089223
	</phone>
	<email>
	  alexandru.petrescu@cea.fr
	</email>
      </address>
    </author>

    <author initials='C.' surname="Janneteau"
	    fullname='Christophe Janneteau'>
      <organization>CEA</organization>
      <address>
	<postal>
	  <street>
	    Communicating Systems Laboratory, Point Courrier 173
	  </street>
	  <city>
	    Palaiseau
	  </city>
	  <region>
	  </region>
	  <code>
	    F-91120
	  </code>
	  <country>
	    France
	  </country>
	</postal>
	<phone>
	  +33(0)169089182
	</phone>
	<email>
	  christophe.janneteau@cea.fr
	</email>
      </address>
    </author>	

    <author initials='W.' surname="Klaudel"
	    fullname='Witold Klaudel'>
      <organization>Renault</organization>
      <address>
	<postal>
	  <street>
	    1 Av. du Golf
	  </street>
	  <city>
	    Guyancourt
	  </city>
	  <region>
	  </region>
	  <code>
	    F-78288
	  </code>
	  <country>
	    France
	  </country>
	</postal>
	<phone>
	  +33(0)176845680
	</phone>
	<email>
	  witold.klaudel@renault.com
	</email>
      </address>
    </author>	

    <date/>

    <!-- Meta-data Declarations -->

    <area>Internet</area>

    <workgroup>Network Working Group</workgroup>

    <!-- WG name at the upperleft corner of the doc, IETF is fine for
         individual submissions.  If this element is not present, the
         default is "Network Working Group", which is used by the RFC
         Editor as a nod to the history of the IETF. -->

    <keyword>
      IP, Internet Protocol, ITS, Intelligent Transportation Systems,
      Mobile IPv6, Neighbor Discovery, Vehicle-to-Vehicle
      communications, Vehicle-to-Vehicle-to-Infrastructure
      communications.
    </keyword>

    <!-- Keywords will be incorporated into HTML output files in a
         meta tag but they have no effect on text or nroff output. If
         you submit your draft to the RFC Editor, the keywords will be
         used for the search engine. -->

    <abstract>
      <t>
	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.
      </t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
	<t>
	  The field of vehicular communications is encompassing a
	  large number of wired and wireless technologies.  In
	  particular, the breakthrough advancements in wide-area
	  cellular telecommunications, the advent of inexpensive
	  hardware, impressively high bandwidth and low-cost data
	  subscription plans make possible new paradigms which put the
	  vehicle at the center of a communications ecosystem.  It can
	  be observed that whereas only in the recent past linking
	  vehicles in a robust manner to a fixed infrastructure
	  represented endeavors available only to top categories, more
	  and more middle category vehicles are announced to take
	  advantage of data connectivity.
	</t>

	<t>
	  Communication protocols used in the fixed and mobile
	  (terminal) Internet can be applied in the scenarios
	  employing vehicles which communicate.  A number of
	  particular aspects make vehicular communications different,
	  not least being the that mobility is the norm, rather than
	  the exception.  At the same time, several protocols
	  developped at IETF are good candidates to form basis of
	  further development of IP protocols for vehicular
	  communications.
	</t>

	<t>
	  The use of Internet protocols in the vehicular scenarios may
	  prove advantageous from several standpoints:
	  <list style='symbols'>
	    <t>
	      immediate availability of a large number of applications
	      with an established customer base.
	    </t>
	    <t>
	      scalability: large numbers of inter-communicating
	      vehicles can be accommodated across large distances.
	    </t>
	    <t>
	      accessing heterogeneous, mixed and multiple-standard
	      link layer technologies.
	    </t>
	  </list>	  
	</t>

	<t>
	  The context of vehicular communications considers the use of
	  several classes of Internet protocols for vehicular
	  applications.  One particular family of protocols is Mobile
	  IP.  Its salient features characterize well several mobility
	  aspects such as reachability at permanent addresses,
	  seamless handovers and group mobility management.  Earlier
	  documents at IETF idenfitied a number of scenarios and
	  potential requirements for further work towards improving
	  the Mobile IP protocols for a better adaptation in vehicular
	  environments (see for example the draft titled "Automotive
	  Industry Requirements for NEMO Route Optimization" edited
	  in 2009 <xref
	  target="I-D.ietf-mext-nemo-ro-automotive-req"/>.)
	</t>

	<t>
	  A Vehicle-to-Infrastructure scenario (V2I) is a typical
	  setting in which a vehicle uses a long-range wireless
	  interface (cellular, sattelite) to connect to a fixed
	  infrastructure.  As a separate matter, scenarios of
	  Vehicle-to-Vehicle (V2V) communications consider direct
	  communications between vehicles, without, or with minimal,
	  assistance from the infrastructure.  In areas where wireless
	  coverage is absent, Vehicle-to-Vehicle-to-Infrastructure
	  communications are scenarios where covered vehicles offer
	  access to non covered vehicles, in a multi-hop manner.
	</t>
	
    </section>
	
    <section title="Terminology">
      <t>
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
        document are to be interpreted as described in
	<xref target="RFC2119">RFC 2119</xref>.
      </t>
    </section>

    <section title="Scenarios">
      <section title="Vehicle-to-Infrastructure (V2I)">
	<t>
	  This section describes the communication scenario in which
	  one mobile vehicle connects to a fixed infrastructure.
	</t>
	<t>
	  Topology:
	</t>
	<figure align="center"
		anchor="xml_topo1"
		title="Topology for Vehicle-to-Infrastructure V2I Communications">
	  <artwork align="center">
	    <![CDATA[
         --------             /--------------+
        | Vehicle|---     ---/Fixed          |------>Internet
         --------  wireless  \Infrastructure |
                     link     \--------------+                
                 (long range)
           ]]></artwork>
	</figure>

      </section>
      <section title="Vehicle-to-Vehicle (V2V)">
	<t>
	  Topology:
	</t>
	<figure align="center"
		anchor="xml_topo2"
		title="Topology for Vehicle-to-Vehicle V2V Communications">
	  <artwork align="center">
	    <![CDATA[
         --------             --------
        | Vehicle|--       --| Vehicle|
         --------  wireless   --------
                     link     
                   (short range)
	    ]]></artwork>
	</figure>
	
      </section>
      <section title="Vehicle-to-Vehicle-to-Infrastructure (V2V2I)">
	<t>
	  Topology:
	</t>
	<figure align="center"
		anchor="xml_topo3"
		title="Topology for Vehicle-to-Vehicle-to-Infrastructure V2V2I Communications">
	  <artwork align="center">
	    <![CDATA[
  --------             --------       /-------------+
 | Vehicle|--       --| Vehicle|-- --/Fixed         |----->Internet 
  --------  wireless   --------  w   \Infrastructure|
              link              link  \-------------+                
           (short range)     (long range)
             ]]></artwork>
	</figure>

	
      </section>
      <section title="Infrastructure Support">
      </section>
    </section>

    <section title="Requirements">
      <t>
	<list style='symbols'>
	  <t>
	    R0. IP addressing within each vehicle.
	  </t>
	  <t>
	    R1. IP addressing on the interface between vehicles.
	  </t>
	  <t>
	    Rn.
	  </t>
	</list>
      </t>
    </section>

    <section anchor="Acknowledgements"
	     title="Acknowledgements">
      <t>
	The authors would like to acknowledge colleagues who commented
	and thus helped improving this document.
      </t>
    <!-- Possibly a 'Contributors' section ... -->
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>
	No particular requirements to IANA.
      </t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>
	Currently no Security considerations.
      </t>
    </section>
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>

    <references title="Normative References">
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119" ?>
    </references>

    <references title="Informative References">
      <?rfc
      	include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-mext-nemo-ro-automotive-req"
      ?>
    </references>


    <section anchor='changelog'
	     title='ChangeLog'>
      <t>
	The changes are listed in reverse chronological order, most
	recent changes appearing at the top of the list.
      </t>

      <t>
	From -- to draft-petrescu-its-scenarios-reqs-00.txt:
	<list style='symbols'>
	  <t>
	    First version of draft issued.
	  </t>
	</list>	
      </t>
    </section>

  </back>
</rfc>