IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Document Naming Convention Date Submitted: January 2008 Presented at IEEE session #24 in Taipei Authors or Source(s): Vivek Gupta Abstract: This contribution describes the Document Naming Convention in

IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3 IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards Development Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6

DCN Convention for The file name shall be as shown. An example of a good filename that conforms to the naming convention is Naming_Convention.ppt Generic filename: gg-yy-ssss-rr-GGGG-brief_topic_name.ext, where “gg” is the 802 group 21 “yy” is the last 2 digits of the year the document is presented “ssss” is the sequence number of the document (contributor obtains this number from a WG official or from the website, incorporates it in the document before making the submission). Sequence number resets to 1 at end of every year. “rr” is the revision number “GGGG” is the file code. This is the WG, TG (task group letter), SG (as designated by chair), or SC (as designated by chair) to which the document is assigned or presented. Current choices are as follows: 0000: WG documents mrpm: Multi Radio Power Management Study Group documents 0sec: Security Study Group documents “brief_topic_name” Human readable name should be as short as possible (please use underscore as the coupling letter between words). Do not add any other detail in this sub-string of the filename. “ext” Is the commonly used 3 letter file extensions:.doc for Word,.ppt for PowerPoint,.pdf for Adobe Acrobat compatible files,.xls for Excel spread sheets.

DCN Convention for Example of WG Document Instructions_For_Getting_Free_IEEE_Web Account Example of MRPM Study Group document mrpm-Use_Case_out-of-coverage Example of Security Study Group document sec-Security-Study-Group-Document