Hi Ketan,
The email address works, but we’re not OK with using “not available” in the reference column instead of this document. For FCFS and Expert Review registries, in the absence of a specification, we’ll list public contacts (which could be the same entity as the change controller) in the reference field. If it’s important to not list this document there, a contact/controller should be listed instead. This would need to be added to the IANA Considerations section. Thanks, Amanda From: Ketan Talaulikar <[email protected]> Date: Tuesday, December 2, 2025 at 8:28 PM To: Michael Richardson <[email protected]> Cc: Amanda Baber <[email protected]>, Mahesh Jethanandani <[email protected]>, "Joe Clarke (jclarke)" <[email protected]>, Guy Harris <[email protected]>, The IESG <[email protected]>, "[email protected]" <[email protected]>, opsawg-chairs <[email protected]>, opsawg <[email protected]> Subject: Re: [Ext] Re: [OPSAWG]Ketan Talaulikar's Discuss on draft-ietf-opsawg-pcaplinktype-12: (with DISCUSS and COMMENT) Hi Michael, That works for me. For the initial allocations where reference is not available, perhaps place 'not available' in the reference column? Amanda, I hope that works? Thanks, Ketan On Wed, Dec 3, 2025 at 9:00 AM Michael Richardson <[email protected]> wrote: I've asked for a [email protected] mailbox to be created. Guy and I will have access to it. I'm pretty sure that nobody wants to embed Guy and my email addresses into an RFC's IANA Considerations. -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
