Automobiles and vehicles of all types are increasingly connected to the Internet. Comfort-enhancing entertainment applications, road safety applications using bidirectional data flows, and connected automated driving are but a few new features expected in automobiles to hit the roads from now to year 2020. Today, there are several deployed Vehicle-to-Internet technologies (V2Internet) that make use of embedded Internet modules, or through driver's cellular smartphone: mirrorlink, carplay, android auto. However, Vehicle-to-Vehicle (V2V) and Vehicle-to-Infrastructure (V2I, not to be mistaken with V2Internet) communications are still being developed. Some vehicle and infrastructure communications will use IP and others will not. Multiple applications need to share one data link, including non-IP-based protocols sharing the data link with IP-based protocols. This group will work on V2V and V2I use-cases where IP is well-suited as a networking technology, supporting also applications that involve exchanges of safety-related messages between vehicles and infrastructure if necessary. This group will develop IP-based protocols to establish direct and secure connectivity between a vehicle, which is often comprised of moving networks, and other vehicles and stationary systems. Some communications will be extremely short lived, but others will last for many hours or days. Moving network to nearby moving or fixed network communications may involve various kinds of link layers: 802.11-OCB (Outside the Context of a Basic Service Set, also called 802.11p), 802.15.4 with 6lowpan, 802.11ad, VLC (Visible Light Communications), IrDA, LTE-D, LP-WAN. One of the most used link layers for vehicular networks is IEEE 802.11-OCB, as a basis for DSRC. However, IPv6 on 802.11-OCB is not yet defined. The group will work only on IPv6 solutions. The group will leverage on technologies for Internet of Things (IoT) which are developed in other IETF and IRTF efforts: 6lo WG, LP-WAN WG, and T2T RG. Co-existence with techniques of infrastructure mobility management will be coordinated with the DMM WG, LISP WG, and other mobility solutions. The group will coordinate with IEEE 802.11. Other SDOs interested in this work include ISO/TC204, ETSI TC ITS, 3GPP, and NHTSA. This group will not work on V2V or V2I use-cases where IP is not well-suited. Without re-chartering, this group will not work on Delay-Tolerant Networking nor on Information-Centric Networking. If the group is successful in accomplishing its first goals, then it can be rechartered to work on other things (examples include but are not limited to: a 1-hop mechanism of IP prefix exchange between moving networks, an n-hop extension, naming for moving networks; generalization for trains, air, unmanned and space use-cases).