Cough, cough, you've got "AN_Proxy" twice in your update. It's above my pay grade, but IMHO somebody needs to tell IANA specifically about this, earlier than AUTH48.
Regards Brian On 07-Nov-20 09:49, Toerless Eckert wrote: > Ok, if you are certain that we can do this in AUTH48, then the following will > suffice: > > https://github.com/anima-wg/anima-bootstrap/issues/147 > > If not, then let me know what i should do process wise (author or wg-chair). > > Cheers > Toerless > > On Sat, Nov 07, 2020 at 08:51:28AM +1300, Brian E Carpenter wrote: >> Yes, this is a glitch. Good catch. I think it's editorial so it can be fixed >> easily, but IANA does need to be informed. The phrasing in the ACP draft is >> fine: >> >> The IANA is requested to register the value "xxx" (without quotes) to the >> GRASP Objectives Names Table in the GRASP Parameter Registry. The >> specification for this value is this document, Section yyy. >> >> Regards >> Brian >> >> On 07-Nov-20 05:24, Toerless Eckert wrote: >>> *sigh* >>> >>> Am i completeley confused, or did we miss until now the IANA request in >>> BRSKI for >>> the new entries AN_Proxy and AN_join_registrar ? >>> >>> I was just checking IANA actions for ACP and did not see these two in the >>> GRASP >>> registry: >>> >>> https://www.ietf.org/archive/id/draft-ietf-anima-bootstrapping-keyinfra-44.txt >>> >>> Not sure about the process, e.g.: if "specification required" (GRASP >>> registry) >>> mandates the IANA text in the BRSKI RFC... I fear it does ? If three is an >>> easier >>> way as having Warren approve another rev... ? >>> >>> Cheers >>> Toerless >>> >>> _______________________________________________ >>> Anima mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/anima >>> > _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
