Skip to main content

6. Structured Syntax Suffix Registration Procedures

Some media types specify a particular named structured syntax as part of their definition by using the "+suffix" convention. Structured syntax suffix registrations provide a central registry for identifying and avoiding conflicts between suffixes used in media types.

Structured syntax suffix registrations MUST NOT:

  • Restrict the creation of media types that employ the identified structured syntax
  • Require a reference to a structured syntax suffix registration in other specifications
  • Require the use of any particular form of structured syntax
  • Provide any form of syntax definition, only identification of the structured syntax

To create a structured syntax suffix registration:

  1. Choose a unique "+suffix". This suffix identifier MUST begin with a plus sign ("+") and obey the same syntax requirements for restricted-name as given in Section 4.2.

  2. Prepare a registration request containing all of the required parts of your registration request as described in Section 6.2.

  3. Post the registration request to the [email protected] mailing list for review and comment to bring the structured syntax suffix type registration to the attention of the community. Allow a reasonable time for discussion and comment.

  4. Respond to review comments and make revisions to the proposed registration as needed to bring it into line with the guidelines given in this document.

  5. Submit the (possibly updated) registration template (or pointer to the document containing it) to IANA at [email protected].

Upon receipt of a structured syntax suffix registration request:

  1. IANA checks the submission for completeness; if sections are missing or citations are not correct, IANA rejects the registration request.

  2. IANA checks the current registry for an entry with the same name; if such a registry exists, IANA rejects the registration request.

  3. IANA requests Expert Review of the registration request against the corresponding guidelines.

  4. The Designated Expert may request additional review or discussion, as necessary.

  5. If Expert Review recommends registration, IANA adds the registration to the appropriate registry.

The initial registry content specification [RFC6839] provides examples of structured syntax suffix registrations.

6.1 Change Procedures​

Registrations may be updated in each registry by the same mechanism as required for an initial registration. In cases where the original definition of the scheme is contained in an IESG-approved document, update of the specification also requires IESG approval.

6.2 Structured Syntax Suffix Registration Template​

This template describes the fields that must be supplied in a structured syntax suffix registration request:

Name

  • Full name of the well-defined structured syntax.

+suffix

  • Suffix used to indicate conformance to the syntax.

References

  • Include full citations for all specifications necessary to understand the structured syntax.

Encoding considerations

  • General guidance regarding encoding considerations for any type employing this syntax should be given here. The same requirements for media type encoding considerations given in Section 4.8 apply here.

Interoperability considerations

  • Any issues regarding the interoperable use of types employing this structured syntax should be given here. Examples would include the existence of incompatible versions of the syntax, issues combining certain charsets with the syntax, or incompatibilities with other types or protocols.

Fragment identifier considerations

  • Generic processing of fragment identifiers for any type employing this syntax should be described here.

Security considerations

  • Security considerations shared by media types employing this structured syntax must be specified here. The same requirements for media type security considerations given in Section 4.6 apply here, with the exception that the option of not assessing the security considerations is not available for suffix registrations.

Contact

  • Person (including contact information) to contact for further information.

Author/Change controller

  • Person (including contact information) authorized to change this suffix registration.
Last updated on