1 / 13

IEEE 802.18 RR-TAG Ad Hoc Agenda

IEEE 802.18 RR-TAG Ad Hoc Agenda. Date: 11 February 19. Authors / Chair Presiding:. Call to Order / Administrative Items. Officers for the RR-TAG / IEEE 802.18: Chair is Jay Holcomb (Itron) Vice-chair, looking for someone Secretary, looking for someone

austin
Download Presentation

IEEE 802.18 RR-TAG Ad Hoc Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IEEE 802.18 RR-TAGAd Hoc Agenda • Date: 11 February 19 Authors / Chair Presiding: Jay Holcomb (Itron)

  2. Call to Order / Administrative Items • Officers for the RR-TAG / IEEE 802.18: • Chair is Jay Holcomb (Itron) • Vice-chair, looking for someone • Secretary, looking for someone • Voters: 41 (9 on EC); Nearly Voters: 3; Aspirant members: 14 • A quorum is met since this meeting was announced more then 45 days ago. • With teleconferences approval on 12 July 2018, quorum is met. After aug31, after 12 July 2018. • IEEE 802 Required notices: • Affiliation FAQ - http://standards.ieee.org/faqs/affiliationFAQ.html • > Be sure to announce you name, affiliation, employer and clients the first time you speak. • Anti-Trust FAQ - http://standards.ieee.org/resources/antitrust-guidelines.pdf • Ethics - https://www.ieee.org/about/corporate/governance/p7-8.html • IEEE 802 WG Policies and Procedures - http://www.ieee802.org/devdocs.shtml • The 4 administration slides, reminder from your WG opening plenary  new 02jan18 • (note: call for essential patents is n/a, as the RR-TAG does not do standards) Jay Holcomb (Itron)

  3. Jay Holcomb (Itron) Other Guidelines for IEEE WG Meetings • All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. • Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. • Don’t discuss specific license rates, terms, or conditions. • Relative costs of different technical approaches that include relative costs of patent licensing terms may be discussed in standards development meetings. • Technical considerations remain the primary focus • Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. • Don’t discuss the status or substance of ongoing or threatened litigation. • Don’t be silent if inappropriate topics are discussed … do formally object. --------------------------------------------------------------- For more details, see IEEE-SA Standards Board Operations Manual, clause 5.3.10 and Antitrust and Competition Policy: What You Need to Know at http://standards.ieee.org/develop/policies/antitrust.pdf

  4. Participation in IEEE 802 Meetings • Participation in any IEEE 802 meeting (Sponsor, Sponsor subgroup, Working Group, Working Group subgroup, etc.) is on an individual basis • Participants in the IEEE standards development individual process shall act based on their qualifications and experience. (https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf section 5.2.1) • IEEE 802 Working Group membership is by individual; “Working Group members shall participate in the consensus process in a manner consistent with their professional expert opinion as individuals, and not as organizational representatives”. (subclause 4.2.1 “Establishment”, of the IEEE 802 LMSC Working Group Policies and Procedures) • Participants have an obligation to act and vote as an individual and not under the direction of any other individual or group. A Participant’s obligation to act and vote as an individual applies in all cases, regardless of any external commitments, agreements, contracts, or orders. • Participants shall not direct the actions or votes of any other member of an IEEE 802 Working Group or retaliate against any other member for their actions or votes within IEEE 802 Working Group meetings, see https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf section 5.2.1.3 and the IEEE 802 LMSC Working Group Policies and Procedures, subclause 3.4.1 “Chair”, list item x. • By participating in IEEE 802 meetings, you accept these requirements. If you do not agree to these policies then you shall not participate. (and please leave the call or meeting.) Jay Holcomb (Itron)

  5. Agenda for Ad Hoc • Call to Order • Administrative items • Need a recording secretary, • looking for an 802.18 Vice-Chair. • Discussion items • U.S. DoT RFC on V2X Communications • Actions required • Comments on US DOT RFC • AOB • Adjourn • Motion: Any objection to approving the agenda as presented? None heard. • To approve the agenda as presented • Moved by: • Seconded by: • Discussion? • Vote: Unanimous consent Jay Holcomb (Itron) Agenda

  6. U.S. DoT Releases RFC on V2X Communications -1 of 3 • https://www.nhtsa.gov/press-releases/us-department-transportation-releases-request-comment-rfc-vehicle-everything-v2x • The RFC can be found at www.transportation.gov/v2x • Or in Mentor: https://mentor.ieee.org/802.18/dcn/18/18-18-0166-00-0000-usdot-v2x-communciations-request-for-comments.docx • Comments: • https://www.regulations.gov/document?D=DOT-OST-2018-0210-0001 • There are 18 comments filed already and nothing obviously new on the site for an extension. • SUMMARY: Over the past several years, the Department of Transportation and its operating administrations have engaged in numerous activities related to connected vehicles, including vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-pedestrian (V2P) communications, collectively referred to as “V2X” communications. Recently, there have been developments in core aspects of the communication technologies that could be associated with V2X. This notice requests comment on how these developments impact both V2X in general and the Department’s role in encouraging the integration of V2X. Jay Holcomb (Itron)

  7. U.S. DoT Releases RFC on V2X Communications -2 of 3 • Comments due 25 Jan 19. Unofficial extension to 24 Feb 19. • https://www.federalregister.gov/documents/2018/12/26/2018-27785/notice-of-request-for-comments-v2x-communications?utm_campaign=subscription%20mailing%20list&utm_source=federalregister.gov&utm_medium=email • https://www.transportation.gov/v2x • To meet 24 Feb 19, need to approve by teleconference on 14 Feb 19. • We have 1 teleconferences to finish, 14 Feb. • Next Ad Hoc: a place holder announced for Wednesday, 13Feb., 17:00et/14:00pt. • Work on the draft comments: • https://mentor.ieee.org/802.18/dcn/19/18-19-0008 Jay Holcomb (Itron)

  8. U.S. DoT Releases RFC on V2X Communications -3 of 3 • The 9 questions. • #0 – The beyond the 9 questions, and have an owner for this • #1 – assigned • #2 – assigned • #3 – We should answer, some overlap with #2, owner of #2 will look at this one. • #4 – This is prime for 11bd, and overlap with #1, owner of #1 will look at this one. • #5 – How is .11p and .11bd viewed? • Some qualification will be needed on how the question is interpreted. • #6 - Maybe easier to answer • #7 - This is very related to #0 • #8 - Maybe easier to answer, but keep high level. • #9 - Not a clear question. Need to restate interoperability is needed, assigned for a couple of sentences • Some of the questions may end up not answered we will see. • Remember this is just an RFC now, the NPRM is later that we can comment on also. • So it is okay to focus on the questions/answers we have and let some go. • However, if anyone can help with some questions, additional text or even edits to the text already, would make our comments that much better. Jay Holcomb (Itron)

  9. References that could be sited in DoT comments • EC Draft Law on Vehicle Communications • Communication standards for connected and autonomous vehicles; • Feedback due 08 Feb., RR TAG did not plan to feedback. • https://ec.europa.eu/info/law/better-regulation/initiatives/ares-2017-2592333_en#isc-2018-08207 • Is there anything in this we could use in DoT comments? Yes • Additional reference that may have some inputs is our comments on the 5GAA waiver request. • https://mentor.ieee.org/802.18/dcn/18/18-18-0159-07-0000-fcc-gn-18-357-5gaa-waiver-ieee-802-comments.docx Jay Holcomb (Itron)

  10. Actions Required • Send in comment text on DOT’s Request For Comments on V2X to the chair. (Best by night before discussions) • (Be thinking about ACMA consultation that had 60GHz. ) • Info: • Latest Cisco VNI 2018-2022 networking trends: https://www.cisco.com/c/en/us/solutions/collateral/service-provider/visual-networking-index-vni/white-paper-c11-741490.pdf Jay Holcomb (Itron)

  11. Any Other Business • none Jay Holcomb (Itron)

  12. Adjourn • Next Ad Hoc: Wednesday, 13 Feb 19; 16:00 ET • Next teleconference: 14 Feb 2019 – 15:00 – <15:55 ET • Call in info: https://mentor.ieee.org/802.18/dcn/16/18-16-0038-11-0000-teleconference-call-in-info.pptx(or latest) (note: new call in for 2019) • Note: If the call-in link doesn’t work send the Chair an email right away. • All changes/cancellations will be sent out to the 802.18 list server. • Adjourn: • Agenda complete, any objection to Adjourn. • None heard, we are Adjourned at 16:______ ET • Thank You Jay Holcomb (Itron)

  13. Jay Holcomb (Itron) Thank You Back up and/or previous slides follow

More Related