doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 1 Mesh Networking Task Group Process Donald E. Eastlake 3 rd

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 2 Generic Process of Getting to Letter Ballot Adoption of PAR and 5 Criteria Technical Presentations and Discussions Specify Any Additional Requirements and Comparison Criteria Call For Proposals Select/Combine from Submitted Complete/Partial Proposals to Produce a Draft Refine Draft Letter Ballot

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide Example Project Histories (Figure above by Bruce Kramer.) 11s 24-Jun-04 May/July 05

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 4 Goals for July 2004 Meeting Adopted By ESS Mesh SG in May July (Portland, Oregon) –Adopt Initial Definitions document –Usage Cases and Functional Requirements discussion –Architecture Presentations –Other ad-hoc subgroup results and Presentations –Joint Meeting with r, etc.

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 5 Future Schedule as Discussed at May 2004 Meeting September 2004 (Berlin, German) –Adopt Functional Requirements / Evaluation Criteria document –Approve Skeleton “Draft” 0.0 –Other ad-hoc subgroup results –Call for Proposals issued immediately after meeting with deadline for submission of two weeks before the November meeting. November 2004 (San Antonio, Texas) –Presentation of Proposals January 2005 (Monterey, California) –Condensation of Proposals -> Draft 0.1 March 2005 (Atlanta, Georgia) –Refinement of Draft (May 2005 (Sydney, Australia) –Letter Ballot Authorized?)

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 6 Ad Hoc Subgroups and Internal TGs Actions Ad Hoc Subgroups –Have no special status unless TGs votes on them or their output. –Any group of members can get together and make submissions. Within the P&Ps (RRONR, notice for meetings and Teleconferences), we can do what we want internally: –“Adopted” internal TGs motions/documents can be amended by majority with notice (i.e., if change is on agenda) or 2/3 vote without notice. –We can issue a call for proposals With no requirements other than the PAR & 5 Criteria With some guidelines With detailed requirements –We can have “Functional Requirements Document” that is a general or specific as we like.

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 7 Ad Hoc Subgroups Informal ad-hoc subgroups: –Usage Cases – coordinator Steve Conner “Usage Models”, 11-04/764r1 and 11-04/662r7 –Definitions – coordinator Tricci So “Draft Terms and Definitions for s”, 11-04/730r1 –Informants re Other standards/drafts/study groups 802.1ae, 802.1af /Security – coordinator Bob Moskowitz –“802.11s Security Proposal”, 11-04/777r k, h /Radio Resources/Metrics – coordinator WNM, CAPWAP /Management – coordinator

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 8 Ad Hoc Subgroups Informal ad-hoc subgroups (cont.): –Routing – coordinator Tyan-Shu Jou “802.11s Routing Sub-Group Discussion on May 04”, /765r0 –Quality of Service – coordinator Lily Yang –Security – coordinator Jasmeet Chhabra The above groups may be using the following wiki page: – bin/wiki.pl?/AdHocGroups

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 9 Ad Hoc Subgroups Some Possible Dispositions of Subgroup Output Documents (as amended if desired) –No action –Include in a TGs adopted “Recommended Reading List” –Adopt as an internal working paper –Adopt as mandatory for proposal conformance

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 10 Calling for Proposals in September? If a call for proposals is to be issued shortly after the September meeting, we should issue a warning at this meeting that we plan to do that. Proposals obviously must conform to the PAR and 5 Criteria. Will we have a Functional Requirements or Evaluation Criteria Document? What other documents, if any, should be referenced by the Call for Proposals?

doc.: IEEE /800r1 Submission July 2004 Donald Eastlake 3rd, MotorolaSlide 11 Possibilities to Accelerate TGs Possibilities for TGs Between July and September Meetings to accelerate action on, for example, a Functional Requirements document: –Nothing –One Teleconference –Ad-hoc face to face meeting (requires 30 days notice) –Multiple Teleconferences (requires 10 days notice)