1609.0 Comment Resolution

1. 1609.0 Comment Resolution John Moring February 2013

2. Summary • Ballot comments • Received 257 total • 5 “Must be satisfied” • 161 Editorial, 55 General, 43 Technical • Plus a couple sets of comments received out of band • Status • Edits completed • Posted in 1609_0 d5.5_130205.pdf • grouper.ieee.org/infotree/groups/vt-its/1609/private/0/2013 • 160 “Accepted” and edited • 48 “Revised” and edited • 16 proposed for rejection (see comment sheet) • Pending • 20 related to “Service” verbiage (more following) • 7 assigned for action by others (see comment sheet) • 2 needing input (see comment sheet) • 4 related to PAR change (more following) • Plus some comments received out-of-band from Tom and Carl

3. 1609.0 PAR • There are several problems with the existing 1609.0 PAR, reflected in the document text. • Scope: This guide describes the Wireless Access in Vehicular Environments (WAVE/DSRC) architecture and services necessary for multi-channel DSRC/WAVE devices to communicate in a mobile vehicular environment. • Purpose: The purpose of this guide is to describe the architecture of the DSRC/WAVE operations currently represented by the family of IEEE 1609 standards and IEEE Std 802.11p.

4. IEEE Guidance • The scope of the standard shall explain in statements of fact what is covered in the standard and, if necessary, what is not covered in the standard—in other words, the technical boundaries of the document. … • For new and revision projects, the scope of the draft shall be within the scope of that given on the PAR, as determined by the balloting group voting on the draft. • A paragraph describing the purpose of the standard is not mandatory in the draft. However, if included, the purpose of the standard and its intended application shall be included in a separate subclause (1.2). The purpose shall explain why the standards project is needed. • For new and revision projects, the purpose (if included) of the draft shall be within the parameters of the purpose given on the PAR, as determined by the balloting group voting on the draft.

5. Proposal • Update Scope in PAR and 1609.0: • “This guide describes the architecture, components, and operation* of a Wireless Access in Vehicular Environments (WAVE) system based on IEEE 1609 standards and IEEE Std 802.11.” • Update Purpose in PAR and remove from 1609.0 as redundant: • “The purpose of this guide is to describe the architecture, components, and operation of a WAVE system based on IEEE 1609 standards and IEEE Std 802.11.” * This language reflects what is in the Overview, and also the 1609.0 headings

6. PAR Action • Submit PAR change request • Modify 1609.0 • Modify 1.1 per agreement • Delete 1.2 • Add new text relating to DSRC to 1. Overview • “The term Dedicated Short Range Communications (DSRC) is sometimes used in the US to refer to radio spectrum or technologies associated with WAVE. In Europe, DSRC refers to a distinct radio technology operating at 5.8GHz, used, e.g., for electronic fee collection.” • Proceed to reballot

7. “Service” • Recall discussion from last meeting • “Service” is used ambiguously and inconsistently throughout the standards, especially 1609.0 • Attracted at least 20 comments • Posted a proposed general resolution to the reflector, summarized here

8. Examples from 1609.0 • Service sometimes refers to the situation where one or more devices have tuned to an RF channel to exchange information particular to one or more applications • “Applications may choose to send their traffic in the context of a WAVE service or not. If they do not use a WAVE service their communication options are limited to WSMs sent on the CCH. Devices associated with a service tune to the designated SCH in order to exchange data.” • “A service is established to support traffic to/from specific applications, and its presence advertised for other devices with compatible applications.”

9. Use of “service”  • A capability, provided by one entity to another • A layer an adjacent layer • “Service request”, “service access point", … • 1609.3 specifies services: provider, user, WSM, CCH, management data, timing advertisement • One device to another • “Client/server”, “application service” • A modified proper noun, hopefully fairly consistent with the usage above • WAVE Service Advertisement, Service Info (in WSA), User Service Request, WSM Service Request, Provider Service Request, Provider Service Identifier, Provider Service Context, Service Channel, … • Also used unmodified to refer imprecisely to a higher layer entity (e.g., application process), or to a channel access for the purpose of communicating with an application over the air (e.g., as announced in the WSA), or to the communications between applications  X • #3 is problematic

10. We didn’t have a noun for • The situation where one or more devices have tuned to an RF channel to exchange information particular to one or more applications • “Upon receipt and successful processing of a provider service request, Networking Services establishes a(n) (term1).” • “advertised application service opportunity” • Benefit: using a modified “service” term rather than inventing a new term does not make the new text incompatible with published standards

11. We didn’t have a verb for • Tuning to an RF channel for the purpose of exchanging information particular to one or more applications • “On receipt of a WSA corresponding to the user service request, Networking Services causes the device to (term2) the (term1).” • “Participate in” or “become a participant in”

12. Proposed definitions – new terms • application service.* A service, involving an exchange of data, generally provided by a higher layer entity on one WAVE device to a similar entity on another WAVE device, using WAVE communications. • advertised application service opportunity.* An SCH that is accessed by one or more Participant WAVE devices (i.e., one or more Provider and zero or more Users) for the purpose of supporting an application service, where the association of the SCH and the application service is announced in a WSA. • unadvertised application service opportunity.* An SCH that is accessed by one or more Participant WAVE devices for the purpose of supporting an application service, where the association of SCH and the application service is not announced in a WSA. • Participant. A WAVE device, in either Provider or User role, that accesses an SCH for the purpose of supporting an application service. * Perhaps capitalize these terms?

13. Proposed definitions - modified • higher layer entity. An entity, such as an application, that resides above the WAVE protocols in the protocol stack and may make use of WAVE communication services. • Provider. A WAVE device that transmits a WSA containing Service Info, i.e., indicating an advertised application service opportunity. • User. A WAVE device that monitors received WSAs for indication of an advertised application service opportunity of interest. • WAVE. A series of standards, developed by the IEEE 1609 working group, for wireless communications including vehicle-to-vehicle and vehicle-to-roadside. Alternately, a system built using that series of standards.

14. Next steps • Agree on definitions and usage per previous paper (sent 7 Feb. 2013) • Update 1609.0 draft, and reballot • Revisit published standards (.2/.3/.4) and update wording for clarity and consistency