Problem Statement for the use of IP in some ITS scenarios
draft-petrescu-its-problem-00
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
---|---|---|---|
Authors | Alexandre Petrescu , Dapeng Liu | ||
Last updated | 2015-09-18 | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | I-D Exists | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
draft-petrescu-its-problem-00
default router. This mode of operation is not considered in this document. The peer-to-peer operation of a V2V topology is an important part in ITS applications such as C-ACC and Platooning. This operation mode allows each vehicle to send and receive application data (coordinates, speed) as IP packets, without the need of assistance from fixed infrastructure. Each vehicle is pre-equipped with a unique IPv6 prefix and each computer in a vehicle is identified by a unique IPv6 address. In order for one computer in one vehicle to reach another computer in another vehicle it is necessary that the embedded routers in each vehicle learn the IPv6 prefix (and/or the IPv6 address) of the other vehicles. A prefix-exchange mechanism is needed, otherwise the IP communication can not be established. After each vehicle has informed the other vehicles nearby about its prefix, the forwarding tables of each vehicle must be updated to contain the tuple [prefix; IP address] of each other vehicles. The updating must deal with situations when vehicles leave the network, otherwise numerous ICMP Destination Unreachable messages may occur on the inter-vehicle media. The problem is thus how to realize this prefix exchange. 6. Problem of Prefix Exchange with the First-hop Infrastructure The Problem of Prefix Exchange with the First-hop Infrastructure 7. Conclusions conclusions 8. Security Considerations security 9. IANA Considerations iana 10. Contributors contributors Petrescu & Liu Expires March 21, 2016 [Page 5] Internet-DraftProblem Statement for IP in C-ACC and PlatooSeptember 2015 11. Acknowledgements acks 12. References 12.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>. 12.2. Informative References [I-D.liu-its-scenario] Liu, D., "Scenario of Intelligent Transportation System", draft-liu-its-scenario-00 (work in progress), March 2015. [I-D.petrescu-ipv6-over-80211p] Petrescu, A., Pfister, P., Benamar, N., and T. Leinmueller, "Transmission of IPv6 Packets over IEEE 802.11p Networks", draft-petrescu-ipv6-over-80211p-02 (work in progress), June 2014. Appendix A. ChangeLog The changes are listed in reverse chronological order, most recent changes appearing at the top of the list. From nil to draft-petrescu-its-problem-00.xml: o initial version Authors' Addresses Alexandre Petrescu CEA, LIST CEA Saclay Gif-sur-Yvette , Ile-de-France 91190 France Phone: +33169089223 Email: Alexandre.Petrescu@cea.fr Petrescu & Liu Expires March 21, 2016 [Page 6] Internet-DraftProblem Statement for IP in C-ACC and PlatooSeptember 2015 Dapeng Liu Beijing , Beijing 100022 China Phone: +86-13911788933 Email: maxpassion@gmail.com Petrescu & Liu Expires March 21, 2016 [Page 7]