Overview SDE Management:
This process is used to register a new SDE using a new unique Tagged Record Extension (TRE), or Data Extension Segment (DES) identifier, using the submission forms from Document Submission Process Page download for filling out. See the SDE Registry for currently used values.
At any time in the review and preparation process that you have questions or concerns please contact the NTB at firstname.lastname@example.org
The following sections provide information on the SDE registration process. Both TRE and DES submissions must have the "POC" tab completed as part of the submission package.
When the appropriate registration forms are filled out, submit to: email@example.com
An SDE can either be a TRE, or a DES. Those implementations using SDEs are allowed only to use approved SDE that are either Controlled or Registered by the Custodial Support Team (CST)/NTB. A Controlled or Registered TRE (6-bytes) or a DES ID (25-bytes) shall contain a valid alphanumeric identifier properly registered with the CST/NTB.
Any SDE not registered with the CST/NTB is invalid.
Controlled Extension (CE):
A Controlled SDE allows additional data constructs within a Joint BIIF Profile (JBP) file with NTB consensus. For a CE, both the Unique Extension Type Identifier (TRETAG for TRE(s), DESID for DES(s), and the specification contained in the User-Defined Data (Control Extension Data (TREDATA) for TRE(s), and DESDATA for DES(s) the fields are subject to full NTB registration and configuration control.
Registered Extension (RE):
A Registered SDE allows JBP users to establish user defined data constructs within a JBP file without NTB consensus. RE use is considered private in that a specific RE only needed by the agreed users. If other users require the RE to understand/exploit the JBP, then the RE cannot be private. The structure and content of the User-Defined Data (TREDATA) field does not need to be configuration managed.
Tagged Record Extension (TRE):
There are two similar, but different, TRE types: Controlled Extensions (CE) and Registered Extensions (RE). The principles are described as follows:
- Controlled TRE(s) both the Field Value and the TRE data are under the control of the STANAG 4545 CST/NTB Configuration Authority.
- Registered TRE(s) only the Field Value is under the control of the STANAG 4545 CST/NTB Configuration Authority.
Registering a new CE for either a TRE or DES:
The requester will fill out the SDE Registration (see SDE-Submission-Form tab) request with the appropriate information as well as the requester will fill out the POC (see POC tab) form and submit to the firstname.lastname@example.org. Additionally, within a six-month period the requested must submit an RFC for a new NTB Document Request (see RFC-Submission-Form tab) containing the SDE and associated supporting documentation and submit to the email@example.com. The NTB will then review the submitted proposal for change to ensure that it is relevant and is not duplicating another effort. If the change proposal is accepted, the NTB will assign an RFC control number to the action and notify the submitter of acceptance for further coordination in preparation for the next NTB Meeting and 45-day review process, (see RFC-Process tab in downloaded Submission Request Forms).
Registering a new RE for a TRE:
The requester will fill out the SDE Registration (see SDE-Submission-Form tab) request with the appropriate information as well as the requester will fill out the POC (see POC tab) form and submit to the firstname.lastname@example.org. The NTB will then review the submitted request for a unique TRE identifier to ensure that it is not duplicating another effort. The NTB will then notify the requester if the unique TRE identifier is accepted or if the requester needs to change because identifier is already used and will need modification.
Example of SDE Submission Form:
See the "Submission Request Forms" documentation for example of a submission.