69. In order to process any RFCP it is important to provide as much information as possible.

70. Changes should outline the key elements of the proposed change(s), references to associated documentation and description of perceived technology trend (if appropriate). Changes should only be proposed in areas where a technology is gaining a broad market acceptance and mature product base.

71. Requests for new standards will address details such as a full specification title, description of applicability, and reference to a Web address or other source. Changes to, or deletion, of existing standards will require appropriate support justification.

72. Under normal circumstances, changes to mandatory standards will have already, for example a standard possibly proposed as maturing from 'emerging' to 'mandatory'.

73. Rationale for changes must be adequately supported with implementation evidence in order to allow the review process to proceed.

74. The rationale used by the IP CaT for determining the selection of standards and profiles for inclusion in the NISP will be part of the IP CaT Standard Operating Procedures.