Re: [Rats] IANA pre-RFC code points

[Thomas Fossati <[e-mail]>]

Ned, Laurence, Giri, all,

On 05/02/2021, 19:50, "Smith, Ned" <[e-mail]> wrote:
> Folks,
> The EAT draft https://datatracker.ietf.org/doc/draft-ietf-rats-eat/
> contains proposed IANA pre-RFC early assignment code point definitions
> in section 7.3.1.
>
> The conditions for making an official IANA request are below in [c]
> and [d].
>
> Does the list believe the code points are stable?
>
> Does the list have sufficient interest in pre-RFC implementation and
> deployment to move forward with the request?

It'd be extremely useful to us if the "profile" claim could be added to
the list early assignments.

That way the PSA token would just use the standard code point assigned
to "profile" to create the context to interpret the rest of the private
PSA claims - which means we would not need to make any further request
to IANA.

Hopefully it is not too late to ask :-)

Cheers!



> Thanks,
> Ned / RATs Chairs
>
> [c] The specifications of these code points must be stable; i.e., if
>  there is a change, implementations based on the earlier and later
>  specifications must be seamlessly interoperable.
>
> [d] The Working Group chairs and Area Directors (ADs) judge that
>  there is sufficient interest in the community for early (pre-RFC)
>  implementation and deployment, or that failure to make an early
>  allocation might lead to contention for the code point in the
>  field.

_______________________________________________
RATS mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/rats

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.