Add special landmark group that expresses just timestamp - #270
Conversation
|
|
||
| For the case where a relying party wants to express the active landmarks it has available, without detailing which CAs in particular, we provide the *universal timestamped landmark group* as follows. | ||
|
|
||
| * The identifying OID arc of the group is `id-mtc-timestamp` (`44363.47.3`). |
There was a problem hiding this comment.
As in other places where we use a 44353.47.* OID, it's worth noting here that 44363.47.3 is temporary and will eventually be replaced by a relative OID allocated by IANA.
There was a problem hiding this comment.
Where should IANA allocate it? (See other allocations.) I think it might be fine to leave as is.
There was a problem hiding this comment.
I'm suggesting structuring thee text this way:
The attribute's value is a RELATIVE-OID containing the trust anchor ID's ASN.1 representation. For example, the distinguished name for a CA with ID
32473.1would be represented in syntax of {{?RFC4514}} as:1.3.6.1.5.5.7.25.TBD=#0d0481fd5901For initial experimentation, early implementations of this design will:
Use UTF8String to represent the attribute's value rather than RELATIVE-OID. The UTF8String contains trust anchor ID's ASCII representation, e.g.
32473.1.Use the OID 1.3.6.1.4.1.44363.47.1 instead of
id-rdna-trustAnchorID.For example, the distinguished name for a CA with ID
32473.1would be represented in syntax of {{?RFC4514}} as:1.3.6.1.4.1.44363.47.1=#0c0733323437332e31
2 participants
No description provided.