[core] Re: Core: FYI/discuss/complain: draft-ietf-anima-brski-discovery-09 updating rfc6690

[Esko Dijk <[e-mail]>]

Hi Toerless,

the prior discussion on this in September 2025 was only between you and 
me - so best to double-check this in the next CoRE interim, which is 
early December.

I would prefer a shorter note to add to the Resource Type (rt=) Link 
Target Attribute Values registry; like:

   Resource Type values with the "brski" prefix MUST be reviewed by the 
Designated Experts of the BRSKI Discovery Parameters Registry (Section 
5.4 of [ThisRFC]).

This will automatically point the reader to the requirements for such 
entry, which should be defined in the document itself. These are the 
same requirements that the experts would review for.
And we don't have to burden non-BRSKI users of the registry with the 
long & detailed text note.

Esko

On 7-11-2025 16:29, Toerless Eckert wrote:
> Hi folks,
>
> forgot to ask for slot, so we can discuss again on next interim if contntuous.
>
> We had some discuss in one of the prior core interims about how to "reserve"
> whatver.* prefixes in the IANA Resource Type Link Target Attribute Values,
> and in my memory, there ws no immediate agreement to go all the way out in
> making this a new registry (through a separate new rfc), so for now i am trying to go with what
> looks like the second option, adding individual entries as updates to rfc6690.
>
> So, draft-ietf-anima-brski-discovery-09 does exactly that for brski.*. Please check.
> section 4.3 and 5.1.1
>
> Goal of course is that the additional requirements checks from 4.3 are being applied
> to new brski.* allocations into the table.
>
> This was checked with Amanda Barber (IANA) and uses appropriate terminology
> ("registration procedure table" instead of "registration table").
>
> Cheers
>      Toerless
>
> _______________________________________________
> core mailing list [e-mail]
> To unsubscribe send an email [e-mail]

-- 
*IoTconsultancy.nl* | Email/Teams: [e-mail] | +31 6 
2385 8339