Committee

 Tools & info

 Document area

 Spectrum issues

 Rules

 

 
   
Change Requests are valid for published MESA specifications and not for "working drafts". In line with the MESA Technical Working Procedures, when a published MESA deliverable (MESA Specification or MESA Report) is revised in order to produce a subsequent version, this shall be performed under change control within the relevant SSG or TSG. 

All development of the deliverable shall be achieved by change requests to be approved by the SSG or TSG.

For delegates who want to propose an editorial modification, the addition of a feature, a functional modification of a feature or a correction to one of the approved MESA documents, please follow the instructions below.

HOW TO CREATE A CHANGE REQUEST (CR)

  1. Download the MESA CR form (.doc - 93 KB).
     
  2. Fill in all relevant areas on the CR cover sheet. See Annex A of these instructions for further detail.
     

  3. Open the specification to which you wish to make a change. It is very IMPORTANT to ensure that you are using the latest version of the specification to make the change. If in doubt, contact the MESA Secretariat at MESAsupport@etsi.org
     

  4. Copy the subclause(s) from the document that you want to change and paste it into the CR form, starting on p. 2. Enter your changes with revision marks in the copied text.
     

  5. Send your CR to MESAsupport@etsi.org, who will submit it to the next Project MESA meeting on your behalf.

  6. Approved CRs (in meeting or on a 2 weeks AbC) are stored in http://www.projectmesa.org/ftp/Change_requests/
     

Examples of expressions of provision in MESA specifications:

To ensure that everybody else understands your proposed changes the same way that you do, it is very important to keep to the following rules:

SHALL: To be used to indicate a requirement. e.g. "The ACH shall be used for sending RFCH in the downlink" is correct. Do not use "The ACH is used for sending RFCH in the downlink" or "The ACH must be used for sending RFCH in the downlink".

SHOULD: To be used to indicate recommendation. i.e. if among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or a certain course of action is preferred but not necessarily required, or (in the negative form) a certain possibility or course of action is deprecated but not prohibited.

MAY: To be used to indicate permission. To be used instead of phrases such as "is permitted", "is allowed" or is permissible". The opposite of "may" is "need not".

CAN: To be used to indicate possibility and capability. To be used instead of phrases such as "be able to", "there is a possibility of" or "it is possible to".


 
ANNEX A: The CR cover sheet

This annex provides further information on how to fill out the cover sheet of a CR.

The header:

  •  The header is the header of usual MESA documents, including the Meeting number, the Document number, and meeting location and date. The document number is allocated by the MESA Secretariat (MESAsupport@etsi.org).

The title box:

  • The change request number. This is a 6 digit number and is allocated by the MESA Secretariat. You must obtain this number from MESAsupport@etsi.org before submitting your change request.
     

  • The MESA Specification number (e.g. TS 70 123).
     

  • The version number that the CR refers to (make sure that this is the latest version). E.g. V.1.1.1.

Source:

  • The name of the MESA member organization to which the author proposing the CR belongs. If the CR has already been agreed at a rapporteur meeting, the name of the group (and document number) should be used instead.

Subject:

  • One line (only) of concise text that describes the subject of the CR. Details should be put under "reason for change".

                 good examples:      "Clarification to the PHY preamble structure"

                                                 "Alignment of operation and parameter names"

                 bad examples:        "correction"

                                                 "editorial correction"

                                                 "correction to TS xxx xxx"

                                                 "various improvements"

Category:

  • Choose one category only.

Reason:

  • This should be 1 to 10 lines of text that describes in further detail the reasons why the change is necessary and how the change is done.

Clauses affected:

  • Each subclause that is affected by the change should be listed here. New subclause number can be followed by "(new)".
     

* If you have any questions about the Change Requests, please contact MESAsupport@etsi.org *

 

 
 
 What is Project MESA?  What can Project MESA do for you?  Site map  Home  Contact