[Rats] OIDs for profile (was Re: IANA pre-RFC code points)

FYI, one of the implications of using an OID here is that to translate a token to/from CBOR to JSON will require code to turn CBOR OIDs into text string dotted-decimal OIDs and vice versa. That’s going to require a full encoder/decoder of the ASN.1 OID format. 

This is probably OK because:
- this is nothing near a full ASN.1 encoder/decoder
- this will happen mostly on servers where code size is not an issue

Note that the plan to format an OID in JSON is to use a text string like “1.2.20.1”. 

(I’m working on code that will translate CBOR tokens to JSON; it’s a good validation of the EAT draft).

LL

> On Feb 27, 2021, at 8:29 PM, Laurence Lundblade <lgl@island-resort.com> wrote:
> 
> OK. There’s a PR for OIDs and URIs now. It also does pre-assignment for the profile claim so it can be included. 
> 
> Ned, please advice on next step here.
> - Is Profile stable enough for reassignment?
> - If so, do we have to issue an -09 draft?
> 
> Please, no more request for claims for pre-assignment so we can get this done.
> 
> LL
> 
> 
> 
>> On Feb 17, 2021, at 3:06 AM, Henk Birkholz <henk.birkholz@sit.fraunhofer.de> wrote:
>> 
>> + 1 to:
>> 
>> * oids as a preferred choice (uri are fine but alas not very concise)
>> * avoiding unstructured text (and inheriting that weirdness here)
>> * avoiding more registries (not only because of more delay)
>> 
>> On 17.02.21 10:55, Thomas Fossati wrote:
>>> Hi Laurence,
>>> On 17/02/2021, 00:59, "Laurence Lundblade" <lgl@island-resort.com> wrote:
>>>>> On Feb 16, 2021, at 5:44 PM, Thomas Fossati <Thomas.Fossati@arm.com> wrote:
>>>>> 
>>>>> On 16/02/2021, 20:25, "Laurence Lundblade" <lgl@island-resort.com> wrote:
>>>>>> Below...
>>>>>> 
>>>>>>> On Feb 16, 2021, at 11:10 AM, <Thomas.Fossati@arm.com> wrote:
>>>>>>> 
>>>>>>> On 16/02/2021, 17:43, <lgl@island-resort.com> wrote:
>>>>>>>> 
>>>>>>>> If we can agree that profiles are necessary and that a simple
>>>>>>>> text string is good enough to name a profile, then we can put in
>>>>>>>> in the pre-allocation.  We don't have to agree on the mechanism
>>>>>>>> for defining profiles, just for naming them.
>>>>>>> 
>>>>>>> I think what is in -08 in terms of defining a profile is great.
>>>>>>> 
>>>>>>> I think we should just nail down the type and constraints around
>>>>>>> the claim value.  The way it is now (i.e., plain, unstructured
>>>>>>> tstr) creates an incentive to using short strings and therefore
>>>>>>> increasing the chance of collisions, which is bad.
>>>>>>> 
>>>>>>> If we say:
>>>>>>> ~~~
>>>>>>> profile-claim = ( profile => $profile-type,)
>>>>>>> 
>>>>>>> $profile-type /= uri ; i.e., #6.32(tstr)
>>>>>>> $profile-type /= oid ; draft-ietf-cbor-tags-oid
>>>>>>> ~~~
>>>>>>> 
>>>>>>> We'd allow both human readable https://fidoalliance.org/profile/a,
>>>>>>> as well as compact, machine readable 1.3.6.1.4.1.etc in a way that
>>>>>>> prevents clashes.
>>>>>>> 
>>>>>>> I don't think it's crazy to expect the profile owner to also
>>>>>>> control a DNS name and/or a PEN.
>>>>>> 
>>>>>> Yes, I was thinking we might want this to be a URI or such myself.
>>>>>> Here’s several options:
>>>>>> 
>>>>>> 1) Make it string-or-uri like the JWT issuer, subject and audience
>>>>>>   claims. Already well-established approach.
>>>>>> 
>>>>>> 2) Allow string, URI or OID. Most flexibility, but do we really
>>>>>>   need OIDs?
>>>>> 
>>>>> I like OIDs because they are relatively compact and unambiguous.
>>>>> They look like the CBOR-friendly equivalent of URIs.  They also
>>>>> render well in JSON as strings in dotted notation.
>>>> 
>>>> I think a good very compact CBOR-friendly way would be to use a simple
>>>> integer in some way.
>>>> 
>>>> One way to do that is to make an IANA registry for profiles with each
>>>> entry:
>>>>  - integer
>>>>  - name
>>>>  - URI
>>> Yes, but we'd need another registry.  Going with URIs and OIDs (PENs)
>>> would avoid the extra IANA round-trip.
>>>> The profile claim in a token could be solely the integer value. Or it
>>>> could be the URI or the text string.
>>>> 
>>>> I'd prefer that to more use of OIDs.
>>> I am not married to any particular format, I am looking for one that can
>>> effectively balance:
>>> * compactness of representation
>>> * minimal IANA impact
>>> * collision avoidance of the identifiers
>>>> The policy for the registry would be pretty loose. Just indicate the
>>>> existence of some document somewhere. Maybe reserve the values less
>>>> than 24 for profiles documents that are standards.
>>>> 
>>>> This seems pretty good to me, but I'm a bit worried about delaying the
>>>> pre-allocation for it since it involves creating another IANA
>>>> registry.
>>> yep
>>> cheers, t
>>> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>>> _______________________________________________
>>> RATS mailing list
>>> RATS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rats
> 
> _______________________________________________
> RATS mailing list
> RATS@ietf.org
> https://www.ietf.org/mailman/listinfo/rats