Best regards, GeoffG On Jun 5, 2019, at 9:00 AM, Angela Thomas < a.n.thomas@xxxxxxxx > wrote: Hello all, This e-mail is to advise you of the opening of IEEE Standards Sponsor Revision Ballot Recirculation - 2 for: Title: Standard for Wireless Access in Vehicular Environments (WAVE)-Identifiers Scope: This standard defines identifiers for use with the IEEE 1609(TM) series of standards.   

Best regards, GeoffG On Jun 5, 2019, at 9:00 AM, Angela Thomas < a.n.thomas@xxxxxxxx > wrote: Hello all, This e-mail is to advise you of the opening of IEEE Standards Sponsor Revision Ballot Recirculation - 2 for: Title: Standard for Wireless Access in Vehicular Environments (WAVE)-Identifiers Scope: This standard defines identifiers for use with the IEEE 1609(TM) series of standards.   

It has been noted by the WG that "there may be editorial changes as a result of late-arriving 1609 WG review, but these docs are stable technically."

Best regards, GeoffG On Jun 5, 2019, at 9:00 AM, Angela Thomas < a.n.thomas@xxxxxxxx > wrote: Hello all, This e-mail is to advise you of the opening of IEEE Standards Sponsor Revision Ballot Recirculation - 2 for: Title: Standard for Wireless Access in Vehicular Environments (WAVE)-Identifiers Scope: This standard defines identifiers for use with the IEEE 1609(TM) series of standards.   

I don't know > where that usage is documented, but I assume it's somewhere in the 1609 > standards. > > --- > Henry Ptasinski > henry@xxxxxxxxxx > > On 01/21/2014 12:10 AM, Rene Struik wrote: > > --- This message came from the IEEE 802.11 Working Group Reflector --- > > > > Hi Donald: > > > > Perhaps, present-day considerations (a decade later) would warrant > > rethinking this topic; hence, my note. > > > > Of course, any documentation of TGi days that sheds light on > > considerations at the time would help.

Presentations and discussion -  discussion on potential development of comment to comments of FCC 5.9 GHz NPRM, Joseph Levy (InterDigital) -  update of IEEE 1609 discussion on interface between 802.11bd and upper layer, John Kenney (Toyota ITC) 6.    

I don't know > where that usage is documented, but I assume it's somewhere in the 1609 > standards. > > --- > Henry Ptasinski > henry@xxxxxxxxxx > > On 01/21/2014 12:10 AM, Rene Struik wrote: > > --- This message came from the IEEE 802.11 Working Group Reflector --- > > > > Hi Donald: > > > > Perhaps, present-day considerations (a decade later) would warrant > > rethinking this topic; hence, my note. > > > > Of course, any documentation of TGi days that sheds light on > > considerations at the time would help.

The values 00 00 00 00 00 00 00 00 to 00 00 00 00 00 00 00 ff are reserved for allocation by the IEEE 1609 Working Group  Applicants need to provide an organization name and contact information.

Note (b) - TC on Jun 25 is specifically for joint discussion with IEEE 1609 experts.

The values 00 00 00 00 00 00 00 00 to 00 00 00 00 00 00 00 ff are reserved for allocation by the IEEE 1609 Working Group  Applicants need to provide an organization name and contact information.

Re: [STDS-802-11-CAC] 答复: [STDS-802-11-CAC] Reminder - Next CAC teleconf Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-11-CAC] 答复: [STDS-802-11-CAC] Reminder - Next CAC teleconference is Monday 2022-10-10 at 9am Eastern To : STDS-802-11-CAC@xxxxxxxxxxxxxxxxx Subject : Re: [STDS-802-11-CAC] 答复: [STDS-802-11-CAC] Reminder - Next CAC teleconference is Monday 2022-10-10 at 9am Eastern From : laurent cariou < 00001be540c02bbe-dmarc-request@xxxxxxxxxxxxxxxxx > Date : Mon, 10 Oct 2022 11:59:33 +0000 --- This message came from the IEEE 802.11 Chairs' Advisory Committee Reflector --- Hi Dorothy, agenda for UHR SG for november is in doc 1-22/1720r0 Thanks Laurent   Le dimanche 9 octobre 2022 à 05:08:00 UTC+2, Xiaofei Wang <00001995ce968e76-dmarc-request@xxxxxxxxxxxxxxxxx> a écrit : --- This message came from the IEEE 802.11 Chairs' Advisory Committee Reflector --- Hi Dorothy, The agenda for AIML Nov 2022 plenary is 11-22/1609. 

Best regards, GeoffG On Jun 5, 2019, at 9:00 AM, Angela Thomas < a.n.thomas@xxxxxxxx > wrote: Hello all, This e-mail is to advise you of the opening of IEEE Standards Sponsor Revision Ballot Recirculation - 2 for: Title: Standard for Wireless Access in Vehicular Environments (WAVE)-Identifiers Scope: This standard defines identifiers for use with the IEEE 1609(TM) series of standards.   

Cover Page Using a Light Image IEEE Registration Authority OUI Registry Tiers proposal Glenn Parsons, RAC Chair November 2012 RAC Members  Glenn Parsons, Chair  Geoff Thompson, (LMSC prime) IEEE 802  Clint Chaplin, (LMSC alternate) IEEE 802  Bob Davis, (MSC prime)  Leonard Tsai, (MSC alternate)  Tom Kurihara, (VTS / ITS prime) IEEE 1609  Geoffrey Garner , (I&M prime) IEEE 1588  George Riley, ex-officio (CS SAB) Staff – Angela Thomas, RAC Secretary – Karen Lambert, Registrar 2 Current OUI based identifiers • Company_id is a 24-bit OUI value assigned by the IEEE-RA • CDI-32™ is a concatenation of a 24-bit OUI value assigned by the IEEE-RA and an 8-bit extension identifier assigned by the organization with that OUI assignment. • TCDI-40™ is a concatenation of a 24-bit OUI value assigned by the IEEE-RA and a16-bit extension identifier assigned by the organization with that OUI assignment. • MAC-48 (obsolete label) / EUI-48™ is a concatenation of a 24-bit OUI value assigned by the IEEE-RA and a 24-bit extension identifier assigned by the organization with that OUI assignment. • EUI-60 (deprecated) is a concatenation of a 24-bit OUI assigned by the IEEE-RA and a 36-bit extension identifier assigned by the organization with that OUI assignment. • EUI-64™ is a concatenation of the 24-bit or 36-bit OUI value assigned by the IEEE-RA and a 40-bit or 28-bit extension identifier assigned by the organization with that OUI assignment. • IPv6 is a concatenation of a 64-bit EUI-64™ (derived from a MAC-48/EUI-48™) and a 64-bit extension identifier assigned by the device with the MAC-48/EUI-48 ™ assignment.

Note (b) - TC on Jun 25 is specifically for joint discussion with IEEE 1609 experts.

The files that are located at   https://ieee.app.box.com/folder/166341576611   were approved by the 1609 WG today.  

Best regards, GeoffG On Jun 5, 2019, at 9:00 AM, Angela Thomas < a.n.thomas@xxxxxxxx > wrote: Hello all, This e-mail is to advise you of the opening of IEEE Standards Sponsor Revision Ballot Recirculation - 2 for: Title: Standard for Wireless Access in Vehicular Environments (WAVE)-Identifiers Scope: This standard defines identifiers for use with the IEEE 1609(TM) series of standards.   

.: IEEE 802.11- 20 /xxxxr0 ppt/theme/theme1.xml ppt/slides/slide1.xml Snapshot of IEEE 802.11 TGbd Jan 2020 Since the Nov 2019 meeting Nov meeting minutes is available here The Tech Editor is still working on D0.1 and continues to call for draft spec text proposal 2 teleconferences was held and the TC minutes are available here FCC announced NRMP on 5.9 GHz which may cause impact to the progress and PAR of TGbd Goal of 20 20 Jan meeting 5 sessions scheduled for TGbd during Jan-2020 meeting including two adhoc sessions, with one MAC adhoc session dedicated to joint session with 1609 experts.

Cover Page Using a Light Image IEEE Registration Authority OUI Registry Tiers proposal Glenn Parsons, RAC Chair November 2012 RAC Members  Glenn Parsons, Chair  Geoff Thompson, (LMSC prime) IEEE 802  Clint Chaplin, (LMSC alternate) IEEE 802  Bob Davis, (MSC prime)  Leonard Tsai, (MSC alternate)  Tom Kurihara, (VTS / ITS prime) IEEE 1609  Geoffrey Garner , (I&M prime) IEEE 1588  George Riley, ex-officio (CS SAB) Staff – Angela Thomas, RAC Secretary – Karen Lambert, Registrar 2 Current OUI based identifiers • Company_id is a 24-bit OUI value assigned by the IEEE-RA • CDI-32™ is a concatenation of a 24-bit OUI value assigned by the IEEE-RA and an 8-bit extension identifier assigned by the organization with that OUI assignment. • TCDI-40™ is a concatenation of a 24-bit OUI value assigned by the IEEE-RA and a16-bit extension identifier assigned by the organization with that OUI assignment. • MAC-48 (obsolete label) / EUI-48™ is a concatenation of a 24-bit OUI value assigned by the IEEE-RA and a 24-bit extension identifier assigned by the organization with that OUI assignment. • EUI-60 (deprecated) is a concatenation of a 24-bit OUI assigned by the IEEE-RA and a 36-bit extension identifier assigned by the organization with that OUI assignment. • EUI-64™ is a concatenation of the 24-bit or 36-bit OUI value assigned by the IEEE-RA and a 40-bit or 28-bit extension identifier assigned by the organization with that OUI assignment. • IPv6 is a concatenation of a 64-bit EUI-64™ (derived from a MAC-48/EUI-48™) and a 64-bit extension identifier assigned by the device with the MAC-48/EUI-48 ™ assignment.

It has been noted by the WG that "there may be editorial changes as a result of late-arriving 1609 WG review, but these docs are stable technically."

Best regards, GeoffG On Jun 5, 2019, at 9:00 AM, Angela Thomas < a.n.thomas@xxxxxxxx > wrote: Hello all, This e-mail is to advise you of the opening of IEEE Standards Sponsor Revision Ballot Recirculation - 2 for: Title: Standard for Wireless Access in Vehicular Environments (WAVE)-Identifiers Scope: This standard defines identifiers for use with the IEEE 1609(TM) series of standards.   

Stanley, HP Enterprise Slide 1 ppt/slides/slide2.xml IEEE 802.11 AIML TIG – November 2022 Artificial Intelligence and Machine Learning November meeting: 2 Meeting slots: Monday PM2; Wednesday AM1 Agenda: 11-22/1609 802 Tutorial: Wireless Meets ML: Rethinking Next Generation Wi-Fi Networks Monday 7:30 pm – 8:50 pm (Bangkok time) November 2022 D.

The 1609 WG will take these facts into consideration in the revision cycle.

It has been noted by the WG that "there may be editorial changes as a result of late-arriving 1609 WG review, but these docs are stable technically."

Note (b) - TC on Jun 25 is specifically for joint discussion with IEEE 1609 experts.

IEEE 1609 would like an OID of the form: iso(1) member-body(2) us(840) ieee1609(TBD) I understand from the discussion that we need to go to ANSI to get an allocation under 840.