Signature Validation Token
draft-santesson-svt-08

(Via drafts-eval@iana.org): IESG/Authors/ISE:

The IANA Functions Operator has completed its review of draft-santesson-svt-08. If any part of this review is inaccurate, please let us know.

We understand that when this document is sent to us for processing, we will perform two registry actions.

QUESTION:

Would it be appropriate to list the IETF as the change controller instead of the IESG? In recent years, we've been asked to use the former instead of the latter (as documented in expired I-D https://datatracker.ietf.org/doc/draft-leiba-ietf-iana-registrations).

ACTION 1:

The following entry will be added to the JSON Web Token Claims registry:

Claim Name: sig_val_claims
Claim Description: Signature Validation Token
Change Controller: IESG
Reference: this document, Section 3.2.3

Please see
https://www.iana.org/assignments/jwt

ACTION 2:

The following entry will be added to the JSON Web Signature and Encryption Header Parameters registry:

Header Parameter Name: svt
Header Parameter Description: Signature Validation Token
Header Parameter Usage Location(s): JWS
Change Controller: IESG
Specification Document(s): this document, Appendix C.1.1

Please see
https://www.iana.org/assignments/jose

Both actions have been approved by the designated experts.

Thank you,

Amanda Baber
IANA Operations Manager

draft-santesson-svt has been presented to the ISE for
publication as an Informational RFC on the Independent Stream.

==Purpose==

This draft provides a means known as a signature validation token to
extend the validity of a signature beyond its initial lifetime.  This
is an alternative to having to resigning an object, but requires that
a verifier trust the entity attesting that they had verified the
original signature when it was valid.  There are other interesting
applications of such technology, such as creating a signature token
using different algorithms other than the original.

This document provides means to use the SVT for several different
formats, including JWS, PDF, signatures, and XML signatures.

== History==

This draft was brought to the attention of the ISE on the 2nd of
August, 2021.  The work was initially referred to the OAUTH chairs
to see if it was in scope.  A further heads up was transmitted to
the OAUTH WG on the 30th of January, 2022.  The document sent to
DISPATCH but was seemingly not dispatched.

==Non-IETF Work==

n/a

==Security Considerations==

See Section 7 of the document.

==IANA==

See Section 6 of the document.  At least one request for a jwt code
point went to jwt-reg-review some time last year, but was not
responded to.  The IANA is requested to process reviews for requests
in this document at this time.

==Reviews==

Carsten Borman and Leif Johanssen reviewed this work and provided
useful fiedback.