search

ietf-rats-wg / draft-ietf-rats-corim

Other
6 stars 7 forks source link

Extensible RIM freshness #161

Open nedmsmith opened 11 months ago

nedmsmith commented 11 months ago

CoRIM defines a freshness mechanism as:

? &(rim-validity: 4) => validity-map
validity-map = {
  ? &(not-before: 0) => time
  &(not-after: 1) => time
}

However, validity-map is not extensible. Hence, alternative freshness mechanisms such as those described by RFC9334 including epoch markers, can't be used with CoRIM.

If validity-map was extensible, then support for alternatives could be added by a profile or later by the base schema.

This issue proposes the following change to base schema:

validity-map = {
  ? &(not-before: 0) => time
  &(not-after: 1) => time
  * $$validity-map-extension
}
thomas-fossati commented 11 months ago

I don't think this is the right place where to add extensibility.

The reason why validity-map has very scoped semantics is because it is reused in different contexts (corim-map, corim-meta-map and concise-bom-tag). Allowing extensibility there makes it hard to track all the subtle semantics differences it may assume when embedded in one or the other context.

If the use case is Concise Evidence / Concise AR, a freshness indicator can already be added via the $$corim-map-extension.