<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.karagiannis-traffic-safety-requirements" target="https://datatracker.ietf.org/doc/html/draft-karagiannis-traffic-safety-requirements-02">
   <front>
      <title>Traffic safety applications requirements</title>
      <author initials="G." surname="Karagiannis" fullname="Georgios Karagiannis">
         <organization>University of Twente</organization>
      </author>
      <author initials="R." surname="Wakikawa" fullname="Ryuji Wakikawa">
         <organization>Toyota ITC</organization>
      </author>
      <author initials="J." surname="Kenney" fullname="John Kenney">
         <organization>Toyota ITC</organization>
      </author>
      <author initials="C. J." surname="Bernardos" fullname="Carlos J. Bernardos">
         <organization>Universidad Carlos III de Madrid</organization>
      </author>
      <author initials="F." surname="Kargl" fullname="Frank Kargl">
         <organization>University of Twente</organization>
      </author>
      <date month="February" day="25" year="2010" />
      <abstract>
	 <t>This document describes a number of communication performance
requirements that are imposed by traffic safety applications on a
network layer.  These traffic safety applications and requirements
have been derived by the USA VSC (Vehicle 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-karagiannis-traffic-safety-requirements-02" />
   
</reference>
