Re: [Rats] [Cbor] 🔔 WGLC on draft-ietf-cbor-tags-oid-02

I see.

So if you are doing DN’s in CBOR this way, it’s kind “in for a penny, in for a pound” and you want to handle the mentioned example using what is described in section 5.

CWT seems a little ambiguous as to whether thusly encoded OIDs are allowed as a label/key. Section 3 says:

   To keep CWTs as small as possible, the Claim Keys are represented
   using integers or text strings.

This seems more of a statement of design intent rather than a prohibition against other types of Claim Keys, but one could interpret it as a prohibition.

Thanks

LL

> On Oct 29, 2020, at 1:25 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> Hi Laurence,
> 
> On 2020-10-29, at 20:44, Laurence Lundblade <lgl@island-resort.com> wrote:
>> 
>> The question I have is whether there is any intent for these OIDs to be keys or labels in CBOR maps.
> 
> The way tag factoring (Section 5 [1]) works for maps was specifically meant to support this.
> 
>> In X.509/PKIX extensions are labeled by OIDs. Would there be similar use in CBOR?
> 
> Please see the example on page 8 [2] for such usage.
> 
>> Typically, CBOR map labels are integers and sometimes text strings. Having to pay attention to tags in map keys might be very inconvenient for some CBOR decoders, though that could be avoided in a given protocol by saying the map keys are byte strings that borrow tag 111 content eliminating the need for the tag.
> 
> That is of course also possible.
> 
> Which reminds me that we specify CDDL control operators, but not prelude-like conventional names for the types created by these tags (e.g., cf. [3]).  Now Issue 6 [4].
> 
> Grüße, Carsten
> 
> [1]: https://www.ietf.org/archive/id/draft-ietf-cbor-tags-oid-02.html#name-tag-factoring-with-oid-arra
> [2]: https://tools.ietf.org/html/draft-ietf-cbor-tags-oid-02#page-8
> [Yessss… :-)]
> [3]: https://www.rfc-editor.org/rfc/rfc8746.html#section-5
> [4]: https://github.com/cbor-wg/cbor-oid/issues/6
> _______________________________________________
> RATS mailing list
> RATS@ietf.org
> https://www.ietf.org/mailman/listinfo/rats