Opened 10 years ago

Closed 9 years ago

#9 closed enhancement (wontfix)

Add "spi" field

Reported by: rbarnes@… Owned by: draft-ietf-jose-json-web-signature@…
Priority: major Milestone:
Component: json-web-signature Version:
Severity: Active WG Document Keywords:
Cc:

Description

Add an optional "spi" field, containing an opaque identifier for the security parameters (algorithms, content keys, etc.) associated with this JOSE object. When an entity receives an object containing an "spi" field as well as security parameters, it adds the parameters to a cache, indexed by the "spi" value. When an entity receives an object with an "spi" field and no parameters, and it has that "spi" value in cache, then it uses the cached parameters to process the object. If an entity receives an object of the latter type, and it does not have the "spi" value in cache, then it is unable to process the object.

Change History (3)

comment:1 Changed 10 years ago by sakimura@…

Per Brian Campbell's message and the subsequent discussion, I would like to propose it to be written as a separate draft so that the complete meaning of the proposal is clear.

comment:2 Changed 10 years ago by michael.jones@…

FYI, this proposal has now been written up as draft-barnes-jose-spi-00.

comment:3 Changed 9 years ago by ietf@…

  • Resolution set to wontfix
  • Status changed from new to closed

It was decided at the interim meeting that we would not be doing this in the current version. If desired it can be revived at a later time in an independent draft.

Note: See TracTickets for help on using tickets.