[media-types] application/dc+sd-jwt registration review reques t
Brian Campbell <[email protected]> Sun, 2 Aug 2026 15:16:59 -0700
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <CA+k3eCRHh34oy8phn5ZF8nCFJ1n=uVGadAxDH1aABETyPD8Nmg@mail.gmail.com> |
--===============0404931022394510543==
Content-Type: multipart/alternative; boundary="0000000000005cf329065817c9b5"
--0000000000005cf329065817c9b5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hello media-types list,
The https://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-vc/ document
is moving into AD review and the AD (Deb, who is cc'd) recently asked about
the status of the anticipated media type registration therein. I've used
email for such endeavors in the past, but based on an erroneous reading of
the note on https://www.iana.org/assignments/media-types, thought the form
at https://www.iana.org/form/media-types was the preferred way to
initiate that process. Sabrina kindly corrected my misunderstanding and
directed me back to sending the template to this list for informal review
and general awareness. The media type template from the draft is copied
below.
Thank you,
Brian
The Internet media type for an SD-JWT VC is application/dc+sd-jwt.
- Type name: application
- Subtype name: dc+sd-jwt
- Required parameters: n/a
- Optional parameters: n/a
- Encoding considerations: 8-bit code points; SD-JWT VC values are
encoded as a series of base64url-encoded values (some of which may be th=
e
empty string) separated by period ('.') and tilde ('~') characters.
- Security considerations: See Security Considerations in Section 6
<https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-17.html#secu=
rity-considerations>.
- Interoperability considerations: n/a
- Published specification: [[ this specification ]]
- Applications that use this media type: Applications that issue,
present, and verify SD-JWT-based Verifiable Digital Credentials.
-
Additional information:
- Magic number(s): n/a
- File extension(s): n/a
- Macintosh file type code(s): n/a
- Person & email address to contact for further information: Oliver
Terbu [email protected]
- Intended usage: COMMON
- Restrictions on usage: none
- Author: Oliver Terbu [email protected]
- Change controller: IETF
--=20
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged=
=20
material for the sole use of the intended recipient(s). Any review, use,=20
distribution or disclosure by others is strictly prohibited.=C2=A0 If you h=
ave=20
received this communication in error, please notify the sender immediately=
=20
by e-mail and delete the message and any file attachments from your=20
computer. Thank you._
--0000000000005cf329065817c9b5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hello media-types list,</div><div><br></div><div>The=
=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-v=
c/">https://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-vc/</a>=C2=A0d=
ocument
is moving into AD review and the AD (Deb, who is cc'd) recently=20
asked about the status of the anticipated media type registration=20
therein. I've used email for such endeavors in=C2=A0the past, but based=
on an erroneous reading of the note on <a href=3D"https://www.iana.org/ass=
ignments/media-types">https://www.iana.org/assignments/media-types</a>,=C2=
=A0thought the form at=C2=A0<a href=3D"https://www.iana.org/form/media-type=
s">https://www.iana.org/form/media-types</a> was the preferred way to initi=
ate=C2=A0that=C2=A0process.=C2=A0Sabrina kindly corrected my misunderstandi=
ng and directed me back to sending the template to this list for informal r=
eview and general awareness. The=C2=A0media type template from the draft is=
copied below.=C2=A0=C2=A0</div><div><br></div><div>Thank you,</div><div>Br=
ian</div><div><br></div><div><br></div><div><p id=3D"gmail-appendix-A.2.1-1=
">The Internet media type for an SD-JWT VC is <code>application/dc+sd-jwt</=
code>.</p>
<ul class=3D"gmail-compact"><li class=3D"gmail-compact" id=3D"gmail-appendi=
x-A.2.1-2.1">Type name: <code>application</code>
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.2">Subtype na=
me: <code>dc+sd-jwt</code>
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.3">Required p=
arameters: n/a
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.4">Optional p=
arameters: n/a
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.5">Encoding=
=20
considerations: 8-bit code points; SD-JWT VC values are encoded as a=20
series of base64url-encoded values (some of which may be the empty=20
string) separated by period ('.') and tilde ('~') character=
s.
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.6">Security c=
onsiderations: See Security Considerations in <a href=3D"https://www.ietf.o=
rg/archive/id/draft-ietf-oauth-sd-jwt-vc-17.html#security-considerations" c=
lass=3D"gmail-auto gmail-internal gmail-xref">Section 6</a>.
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.7">Interopera=
bility considerations: n/a
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.8">Published =
specification: [[ this specification ]]
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.9">Applicatio=
ns that use this media type: Applications that issue, present, and verify S=
D-JWT-based Verifiable Digital Credentials.
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.10">
<p id=3D"gmail-appendix-A.2.1-2.10.1">Additional information:=
</p>
<ul class=3D"gmail-compact"><li class=3D"gmail-compact" id=3D"gmail-appendi=
x-A.2.1-2.10.2.1">Magic number(s): n/a
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.10.2.2">File =
extension(s): n/a
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.10.2.3">Macin=
tosh file type code(s): n/a
</li></ul>
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.11">Person &a=
mp; email address to contact for further information: Oliver Terbu <a href=
=3D"mailto:[email protected]">[email protected]</a>
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.12">Intended =
usage: COMMON
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.13">Restricti=
ons on usage: none
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.14">Author: O=
liver Terbu <a href=3D"mailto:[email protected]">oliver.terbu@mattr=
.global</a>
</li><li class=3D"gmail-compact" id=3D"gmail-appendix-A.2.1-2.15">Change co=
ntroller: IETF</li></ul><br></div></div>
<br>
<i style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align:ba=
seline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-=
ui,-apple-system,system-ui,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,C=
antarell,"Helvetica Neue",Arial,sans-serif;color:rgb(85,85,85)"><=
span style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align:=
baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,=
-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ub=
untu,Cantarell,"Helvetica Neue",Arial,sans-serif;font-weight:600"=
><font size=3D"2">CONFIDENTIALITY NOTICE: This email may contain confidenti=
al and privileged material for the sole use of the intended recipient(s). A=
ny review, use, distribution or disclosure by others is strictly prohibited=
.=C2=A0 If you have received this communication in error, please notify the=
sender immediately by e-mail and delete the message and any file attachmen=
ts from your computer. Thank you.</font></span></i>
--0000000000005cf329065817c9b5--
--===============0404931022394510543==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbWVkaWEtdHlw
ZXMgbWFpbGluZyBsaXN0IC0tIG1lZGlhLXR5cGVzQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNl
bmQgYW4gZW1haWwgdG8gbWVkaWEtdHlwZXMtbGVhdmVAaWV0Zi5vcmcK
--===============0404931022394510543==--