Re: [Rats] Profile identifier (was Re: EAT Profiles)

The OID can be a PEN, which is a prefix assigned by IANA, and then the party that owns the prefix can manage the rest by themselves.  I like the distributed nature of that approach.

Russ

> On Sep 20, 2022, at 4:09 PM, Laurence Lundblade <lgl@island-resort.com> wrote:
> 
> Here’s 3 ways to identify a profile. The first two are in EAT now. The last is not.
> 
> 1) OID
> 2) URI
> 3) IANA first-come-first-served integer. No text strings, just a simple monotonic integer, 0, 1, 2, 3, 4… A URI can be associated with the integer if the profile is published, but it isn’t required.
> 
> We can do any combo of the above (e.g., what’s in the doc now, just 2 and 3,…). I don’t have a strong opinion, but just 3 seems in the spirit of being small and simple to me.
> 
> The two issues with 3) I can see are:
> - Is it OK to consume more IANA resources here? I assume yes. It’s kind of their job and it isn’t hard to do this
> - The profile was pre-allocated by IANA as OID and URI and there probably some implementations
> 
> LL
> 
> 
> 
>> On Sep 19, 2022, at 9:51 AM, Henk Birkholz <henk.birkholz@sit.fraunhofer.de <mailto:henk.birkholz@sit.fraunhofer.de>> wrote:
>> 
>> If it has to be specified in a stable document anyways, I cannot fathom the need for a URI. Just do a number and go to IANA?
>> 
>> On 19.09.22 17:42, Thomas Fossati wrote:
>>> hi Henk,
>>> On Mon, Sep 19, 2022 at 1:04 PM Henk Birkholz <henk.birkholz@sit.fraunhofer.de <mailto:henk.birkholz@sit.fraunhofer.de> <mailto:henk.birkholz@sit.fraunhofer.de <mailto:henk.birkholz@sit.fraunhofer.de>>> wrote:
>>>     >      > * Would it be useful to reference profiles by number
>>>    (rather than
>>>     >      > URLs)? Probably so.
>>>     >
>>>     > It seems like we ought to have an optional registry, and if
>>>    someone wants to use a URI, then fine.
>>>    Not sure on the URI part really, but if there is enough support for
>>>    it... How would EAT ensure interoperability, if we allow for 'any
>>>    URI as
>>>    profile identifier' use outside the 'custom/local/experimental' scope?
>>>    Or would that automatically imply that scope?
>>> I wouldn't be worried about that.  EAT profiles need to be specified in a stable document.  The visibility of that document is what determines the reach and interoperability of that profile.  A profile ID (URL or else) is an identifier for the document.
>>> cheers,
>>> -- 
>>> Thomas
>> 
>> _______________________________________________
>> RATS mailing list
>> RATS@ietf.org <mailto:RATS@ietf.org>
>> https://www.ietf.org/mailman/listinfo/rats
> 
> _______________________________________________
> RATS mailing list
> RATS@ietf.org
> https://www.ietf.org/mailman/listinfo/rats