ddi-spec: document which suffix, mime type and sector sizes to use for DDIs

Author: poettering

specs/discoverable_disk_image.md

@@ -17,7 +17,21 @@ into one.  They are designed to be composable and stackable, and provide securit
 The images use the GPT partition table verbatim, so it will not be redefined here. Each partition contains
 a standard Linux filesystem (e.g.: `erofs`), so again this will not be redefined here.
 The [DPS](discoverable_partitions_specification.md) defines the GUIDs to use and the format of the
-dm-verity signature partition's JSON content.
+`dm-verity` signature partition's JSON content.
+
+It is recommended to use a sector size of 512 bytes or 4096 for DDIs. Software operating with DDIs should
+automatically derive the sector size used for a DDI by looking for the `EFI PART` magic string at offsets 512
+or 4096, as per GPT specification.
+
+## Naming
+
+DDIs should use `.raw` as file suffix. A secondary suffix may be used to clarify the specific usage class of
+a DDI. For now the two secondary suffixes `.sysext.raw` and `.confext.raw` are defined (for system extension
+DDIs and configuration extension DDIs, see [Extension
+Images](https://uapi-group.org/specifications/specs/extension_image) for details).
+
+The MIME type for DDIs is `application/vnd.efi.img`, [as per
+IANA](https://www.iana.org/assignments/media-types/application/vnd.efi.img).
 
 ## Image Version
 If the DDI is versioned, the version format described in the

specs/extension_image.md

@@ -38,6 +38,11 @@ to identify them.
 Extension Images should be additive, and not override content present in the base image or other DDIs,
 but this will not be enforced.
 
+## File Suffix
+Since extensions images are DDIs, they should carry the `.raw` suffix. In order to make discerning system
+extensions and configuration extensions easy it is recommended to use the `.sysext.raw` suffix for system
+extensions, and `.confext.raw` for configuration extensions.
+
 ## Identification
 An Extension Image must contain a `extension-release.<IMAGE>` file, where `<IMAGE>` must either match the
 name of the sysext minus the suffix, or alternatively `extension-release.<IMAGE>` must be tagged with a