1. Status of ITS communications work items at IETF Alexandre Petrescu, CEA, Meeting of Collaboration on ITS Communication Standards, Geneva, Switzerland, March 4th, 2016

2. BoF « ITS » at next IETF ietf.org/mailman/listinfo/its Meet f2f 4-8 April 2016 in Buenos Aires Moving network to nearby moving network communications discussion about the use of IP networking protocols for moving network to nearby moving network applications like V2V. Among the considered applications C-ACC is mentioned. As a result some ideas are coming forward, but no work is chartered at this time.

3. Context Router Host Router Host 2001:db8:1::/64 Host 2001:db8:2::/64 2001:db8:3::/64 Communication possible at PHY layer Communication impossible at PHY layer Problems: Prefix discovery: how routers securely discover the prefixes in the mobile network? Prefix exchange: how routers inform each other about their prefix? How Hosts in different mobile networks can unicast packets? How Hosts in different mobile networks can address by name? Mobile Network1 Mobile Network2 Cage Antenna, light emitter/sensor, cable Mobility situations TCP/IPv6 Moving networks Heterogeneous links: WiFi, 802.11p, IrDA, VLC, LTE-D, PLC

4. Applicability Vehicular networks (automobiles) Host Router Host 2001:db8:3::/64 Network at Toll Station Vehicle to vehicle Communications (V2V, CACC) Vehicle to toll Station (V2I) Connected rail: Public safety:

5. Internet Engineering Task Force (synthesis by IRTSystemX) Definition – “The IETF is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet.” Mission – “The IETF's mission is "to make the Internet work better," but (…) from an engineering point of view.” – The IETF tries “to avoid policy and business questions, as much as possible.” Legal status – Informal group, without status, without membership and without subscription – Formally established in 1986 by the IAB (existed informally previously) – Why was it created? It was created to bring together researchers and practitioners to foster interoperability between computers using TCP/IP protocols and to ensure scalability of the Internet. – Where are the Head Quarters? The IETF meets thrice a year at various places on most continents. There is no fixed location, and no Head Quarters. However, the Internet Society (main sponsor of the meeting events) has fixed Regional Bureaus on six “bureaus” Africa, Asia-Pacific, Europe, Latin America and Carribean, Mid-East, North America.

6. Working Group Creation – Meet persons with shared interests in a specific technical area related to Internet protocols (bar- BOF) – Write together a charter for the WG (timeline, problem statement, state-of-the-art, use cases, …) – Ask for a BOF (Birds Of a Feather) @next IETF meeting BOF meeting: – Around 1 hour: 20 mins to present the charter, 40 mins for questions/answers – (Who?) nominates the BOF chairs – the chairs are nominated by the Area Directors in charge of the area where the WG is to be formed. The BoF Chairs could be the persons who mount the BoF. The BoF Chairs could become the WG Chairs should the WG be formed, but it is not mandatory – each time the ADs can select different persons. – The number of persons present in the room has an importance  At the end of a BoF (last 5 minutes), a number of yes-no questions are formulated by the Chairs, with the help from the room; the room must respond to the questions (poll) by “humming” or by raising hands. The answers are evaluated by the ADs who make a decision of forming or not.

7. Working Group Management – A written charter defines what is the work to do and timeline – One or more chairs (how are hey nominated?) They are nominated by the ADs. Prior to the meeting, on an ongoing basis, individuals express interest to chair groups, and there are private waiting lists of people willing to chair. On another hand, there are a number of BoFs happening. ADs make the matches. The chair selection is at the entire discretion of the Ads, and not based on voting. – WG mailing-list creation – Average duration of WG - 3 years – More than 100 WG at the moment Objectives – Develop technical specifications to address issues mentioned in the charter – Working documents: Internet-Drafts (I-D) Shared and open documents, readable by anybody for review and comments Results – Request For Comment (RFC) specifications

8. IETF Meeting IETF meets 3 times/year 6 days duration: from Sunday to Friday – Saturday : not really part of IETF, but Hackathon: bring your device and try interoperability with others. – Sunday: newcomers sessions, IETF tutorials, programing events (hackaton, …) – Monday -> Friday: WG sessions – Social event one evening Tuesday – Thursday: “bits and bytes” demos ensures large publicity Audio & video streaming and recording, archiving Remote participation possible A registration must be paid

9. ITS perspective No WG focused on Intelligent Transportation Systems. As there are no groups focused on IoT, or 5G, etc. But focus on particular technical topics which can be applied in ITS context

10. Past IETF WG items related to ITS Mobile IP and Network Mobility extensions (RFC3963, RFC5177) Next-Generation Pan-European eCall

11. More recent documents Transport Layer Security (TLS) Client authentication Using IEEE 1609-2 Certificate Problem Statement for Internet-wide Geo- networking Problem Statement for IP in ITS use cases C-ACC and Platooning Cooperative Adaptive Cruise Control and Platooning at SDOs and Gap Analysis Transmission of IPv6 Packets over IEEE 802.11 Networks Outside the Context of a Basic Service Set

12. Other ITS-related activities at IETF Category A Liaison with ISO TC204

13. BoF « ITS » at next IETF ietf.org/mailman/listinfo/its Meet f2f 4-8 April 2016 in Buenos Aires Moving network to nearby moving network communications discussion about the use of IP networking protocols for moving network to nearby moving network applications like V2V. Among the considered applications C-ACC is mentioned. As a result some ideas are coming forward, but no work is chartered at this time.

14. Context Router Host Router Host 2001:db8:1::/64 Host 2001:db8:2::/64 2001:db8:3::/64 Communication possible at PHY layer Communication impossible at PHY layer Problems: Prefix discovery: how routers securely discover the prefixes in the mobile network? Prefix exchange: how routers inform each other about their prefix? How Hosts in different mobile networks can unicast packets? How Hosts in different mobile networks can address by name? Mobile Network1 Mobile Network2 Cage Antenna, light emitter/sensor, cable Mobility situations TCP/IPv6 Moving networks Heterogeneous links: WiFi, 802.11p, IrDA, VLC, LTE-D, PLC

15. Applicability Vehicular networks (automobiles) Host Router Host 2001:db8:3::/64 Network at Toll Station Vehicle to vehicle Communications (V2V, CACC) Vehicle to toll Station (V2I) Connected rail: Public safety: