1 / 6

802.20 Closing Slides

Guidelines for the correspondence groups in IEEE 802.20, including requirements, channel modeling, and evaluation criteria. Open participation with the option to contribute separately. Document formats and numbering/naming conventions are also specified.

swoodard
Download Presentation

802.20 Closing Slides

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. C802.20-03/10 802.20 Closing Slides Mark Klerer – Jerry Upton Vice-Chairs

  2. Requirements Correspondence Group Ground Rules • Drive towards a consensus correspondence group contribution for July Plenary Session • Build document from ground-up considering contributions from previous meetings and PAR and 5C • Participation open to everyone • Keeping multiple alternatives in text is OK • Correspondence group participants reserve the right to contribute separately • Contributors are expected to provide text that they would like included including a brief rationale of why they want the change • Correspondence Group Chair: Khurram Sheikh (Sprint) • E-mail list: stds-80220-requirements

  3. Channel Modeling and Traffic Correspondence Group Ground Rules • Drive towards a consensus correspondence group contribution for July Plenary Session with final model set by September Interim Session • July set to be based on channel types and traffic types as known at that time based on the work of the requirements correspondence group. • Participation open to everyone • Build document from ground-up considering contributions from previous meetings, PAR, 5C and requirements working group. • Keeping multiple alternatives in text is OK • Correspondence group participants reserve the right to contribute separately • Contributors are expected to provide text that they would like included including a brief rationale of why they want the change • Correspondence Group Chair: Glenn Golden (Flarion Technologies) • E-mail list: stds-80220-ch-models

  4. Evaluation Criteria Correspondence Group Ground Rules • Drive towards a consensus correspondence group contribution for September Interim Session • Work to be based on requirements as defined by the requirements correspondence group and utilize the channel models and traffic models specified by the channel modeling correspondence group. • Build document from ground-up considering contributions from previous two meetings and work of other correspondence groups. • Keeping multiple alternatives in text is OK • Correspondence group participants reserve the right to contribute separately • Contributors are expected to provide text that they would like included including a brief rationale of why they want the change • Correspondence Group Chair: Farooq Khan (Lucent) • E-mail list: stds-80220-eval-criteria

  5. Document Formats for used in 802.20 • PDF files are mandatory • Use light background and dark text • If possible, please convert files to PDF prior to submitting • Optionally PPT, DOC and ZIP files may also be provided. ZIP files shall contain only PPT, DOC or PDF files. • Contributions proposing draft text for inclusion in a standard shall provide that text in DOC format

  6. Document Numbering/Naming in 802.20(Interim Plan) • For the time being we retain the existing numbering system with the following enhancement: • A suffix will be added to: • distinguish between different file types of the same document • distinguish between a submitted document and an associated presentation • New document numbering/naming plan will be discussed in the context of the file naming conventions proposed for the electronic system being proposed by 802.11/.15 (See IEEE 802-03/11)

More Related