%% You should probably cite draft-ietf-ipwave-vehicular-networking instead of this I-D. @techreport{ietf-ipwave-problem-statement-00, number = {draft-ietf-ipwave-problem-statement-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-ipwave-problem-statement/00/}, author = {Jaehoon Paul Jeong and Alexandre Petrescu and Tae (Tom) Oh and Dapeng Liu and Charles E. Perkins}, title = {{Problem Statement for IP Wireless Access in Vehicular Environments}}, pagetotal = 19, year = 2017, month = jul, day = 3, abstract = {This document provides a problem statement for IP Wireless Access in Vehicular Environments (IPWAVE), that is, vehicular networks. This document addresses the extension of IPv6 as the network layer protocol in vehicular networks. It deals with networking issues in one-hop communication between a Road-Side Unit (RSU) and a vehicle, that is, "vehicle-to-infrastructure" (V2I) communication. It also deals with one-hop communication between two neighboring vehicles, that is, "vehicle-to-vehicle" (V2V) communication. Major issues about IPv6 in vehicular networks include neighbor discovery protocol, stateless address autoconfiguration, and DNS configuration for Internet connectivity. When a vehicle and an RSU have an internal network (respectively), the document discusses internetworking issues between two internal networks through either V2I or V2V communication. Those issues include prefix discovery, prefix exchange, service discovery, security, and privacy.}, }