doc.: IEEE /0702r0 Submission May 2007 R. Roy / SRASlide 1 ISO TC 204 WG 16 Liaison Report Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. ieee802.org/guides/bylaws/sb-bylaws.pdf Date: Authors:

doc.: IEEE /0702r0 Submission May 2007 R. Roy / SRASlide 2 Abstract Since the last meeting in Orlando, TC 204 has held a plenary meeting in Lexington, KY. WG 16 generally does not meet during plenary sessions. A CALM M5/C2C-CC/IEEE 802/P1609 workshop was held last week in Sophia Antipolis. This presentation presents the results and conclusions of this workshop.

doc.: IEEE /0702r0 Submission May 2007 R. Roy / SRASlide 3 Summary of Presentations C2C-CC presentation –Overview of the C2C system was presented –Open questions were put on the table IEEE/WAVE presentation –Status of IEEE standards development was presented (standards versus system design specifications) –Input from the C2C-CC was strongly encouraged (once again). CALM presentation –Overview of CALM was given Sets of standards were exchanged

doc.: IEEE /0702r0 Submission May 2007 R. Roy / SRASlide 4 Results of Meetings C2C-CALM-IEEE harmonization issues –Low-level architecture –Periodic broadcast frame structure and data content –Congestion reduction strategies Applications may need to inform management plane about special situations to adapt congestion mitigation strategies –C2C-CC/CALM M5 PHY has yet to be determined – maximum flexibility to achieve most efficient PHY is desired C2C-CC/CALM M5 requested a flexible set of “band plans” so as to allow them to test what works best C2C-CC indicated a strong interest in testing a “synchronized wideband time-slotted” PHY (enhanced )

doc.: IEEE /0702r0 Submission May 2007 R. Roy / SRASlide 5 What’s Ahead Way forward for CALM M5 –21215 & development Urgent need for – first draft for “public” commenting June 2007 Reference to – Mandatory part “Layman's guide” – Informative Next step: Interoperability Conformance requirements (ETSI?) –We need co-operation with experts from IEEE and C2C in particular, but also from COOPERS; SAFESPOT and CVIS in particular. –Main group led by HJF: Dick Roy, Justin McNew, Volunteers from C2C/SAFESPOT by 18 May –First commenting expected after Nagasaki meeting. –Mainly work by , but some physical meetings are also expected Open issues –Boundary between communication system and applications. –More work needed on congestion