[media-types] Re: [IANA #1421575] application/vp+sd-jw t registration request

Brian Campbell <[email protected]>
Newsgroups gmane.ietf.types
Message-ID <CA+k3eCQB1A+zcYvMOgtj9hKJo5E1xx=9KDSXfGQYRQNxqvNKZA@mail.gmail.com>
As previously mentioned on this mailing list[1] as well as in response
to the June 24th message[2], the "application/vp+sd-jwt" media
type is a net harm to the internet and should not be endorsed, or given the
impression of endorsement, by the IETF or IANA through registration.

[1]
https://mailarchive.ietf.org/arch/msg/media-types/VnhrnlQmh8rtlo6iU8gS1QYYK_I/
https://mailarchive.ietf.org/arch/msg/media-types/AL6QDGXYl-zsfkN4x_S9Jq_RX9I/
https://mailarchive.ietf.org/arch/msg/media-types/G9Lku0QcRYjjG09QXUYurqfOtQA/

[2]
https://mailarchive.ietf.org/arch/msg/media-types/QgmYXmEHGZr6FeeUzsLt7E4Wd3E/



On Wed, Jul 2, 2025 at 7:17 PM Amanda Baber via RT <
[email protected]> wrote:

> Hi Murray,
>
> #2 of 2 from June 24th.
>
> thanks,
> Amanda
>
> On Tue Jun 24 19:10:58 2025, amanda.baber wrote:
> > Hi Murray,
> >
> > This is #2 of 2 from W3C.
> >
> > thanks,
> > Amanda
> >
> > =====
> >
> > Name: Ivan Herman
> >
> > Email: [email protected]
> >
> > Media type name: application
> >
> > Media subtype name: vp+sd-jwt
> >
> > Required parameters: N/A
> >
> > Optional parameters: N/A
> >
> > Encoding considerations: binary
> >
> > application/sd-jwt values are a series of base64url-encoded values
> > (some of which may be the empty string) separated by period ('.') and
> > tilde ('~') characters.
> >
> > Security considerations: As defined in https://www.w3.org/TR/vc-jose-
> > cose/#security-considerations. See also the security considerations in
> > Selective Disclosure for JWTs (SD-JWT)
> > (https://datatracker.ietf.org/doc/html/draft-ietf-oauth-selective-
> > disclosure-jwt).
> >
> > Interoperability considerations: As defined in
> > https://www.w3.org/TR/vc-jose-cose/#conformance.
> >
> > Published specification: https://www.w3.org/TR/vc-jose-cose
> >
> > Applications which use this media: W3C Verifiable Credential issuer,
> > holder, and verifier software, conforming to the [VC-DATA-MODEL-2.0]
> > (https://www.w3.org/TR/vc-data-model-2.0/), are among the applications
> > that will use the media types. Conforming application types are
> > described in https://www.w3.org/TR/vc-jose-cose/#conformance and
> > https://www.w3.org/TR/vc-data-model-2.0/#conformance.
> >
> > Fragment identifier considerations: N/A
> >
> > Restrictions on usage: N/A
> >
> > Provisional registration? (standards tree only): No
> >
> > Additional information:
> >
> > 1. Deprecated alias names for this type: N/A
> > 2. Magic number(s): N/A
> > 3. File extension(s): N/A
> > 4. Macintosh file type code: N/A
> > 5. Object Identifiers: N/A
> >
> > General Comments:
> >
> > Person to contact for further information:
> >
> > 1. Name: Ivan Herman
> > 2. Email: [email protected]
> >
> > Intended usage: COMMON
> >
> > Author/Change controller: W3C Verifiable Credentials Working Group
> > [email protected]
>
> _______________________________________________
> media-types mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.