name: CR
full_form: Change Request
context: When a 3GPP member company identifies the need for a new sub-domain name of ".3gppnetwork.org", that 3GPP member company shall propose a CR to this specification at the earliest available meeting of the responsible working group for this TS. The CR shall propose a new sub-domain name. The new sub-domain proposed shall be formatted in one of the formats as described in the following table. Table E.1: Sub-domain formats for the "3gppnetwork.org" domain and their respective intended usage NOTE 1: "<service_ID>" is a chosen label, conformant to DNS naming conventions (usually IETF RFC 1035 [19] and IETF RFC 1123 [20]) that clearly and succinctly describe the service and/or operation that is intended to use this sub-domain. NOTE 2: "<MNC>" and "<MCC>" are the MNC (padded to the left with a zero, if only a 2-digit MNC) and MCC of a PLMN. NOTE 3: "NID", "<MNC>" and "<MCC>" are the NID (hexadecimal digits as specified in clause 12.7), MNC (padded to the left with a zero, if only a 2-digit MNC) and MCC identifying a Stand-alone Non-Public Network (SNPN). Care should be taken when choosing which format a domain name should use. Once a format has been chosen, the responsible working group shall then check the CR and either endorse it or reject it. If the CR is endorsed, then the responsible working group shall send an LS to the GSMA NG with TSG-CT in copy. The LS shall describe the following key points: - the context - the service - intended use - involved actors - proposed new sub-domain name GSMA NG will then verify the consistence of the proposal and its usage within the domain's structure and interworking rules (e.g. access to the GRX/IPX Root DNS servers). GSMA NG will then endorse or reject the proposal and inform the responsible working group (in 3GPP) and also TSG CT. It is possible that GSMA NG will also specify, changes to the newly proposed sub-domain name (e.g. due to requested sub-domain name already allocated). NOTE 4: There is no need to request GSMA NG for new labels to the left of an already GSMA NG approved "<service_ID>". It is the responsibility of the responsible working group to ensure uniqueness of such new labels. It should be noted that services already defined to use the ".gprs" domain name will continue to do so and shall not use the new domain name of ".3gppnetwork.org"; this is to avoid destabilising services that are already live.
description: A Change Request (CR) in the context of 3GPP refers to a formal proposal submitted by a member company for modifications or additions to existing specifications, including the introduction of new sub-domain names under the '.3gppnetwork.org' domain. This process involves careful consideration and validation by the responsible working group and GSMA NG to ensure consistency and avoid conflicts within the domain structure.
explanation: CR is categorized as Miscellaneous because it represents a procedural aspect within the 3GPP's standardization process, focusing on the management of change requests rather than fitting neatly into categories like Network Function or Protocol. It involves a specific set of steps and considerations for proposing and validating changes to specifications and domain names.
section_title: Annex E (normative): Procedure for sub-domain allocation
biotag_Context: O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,B-Organization,B-Specification,O,O,O,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,B-Organization,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,B-Organization,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Interface,O,O,O,O,O,O,O,O,O,B-Organization,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Message,I-Message,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Interface,O,O,O,O,O,O,O,O,O,O