Dear IESG-designated registry expert:
Thank you again for volunteering to serve as a protocol parameter reviewer.
I’m writing to notify you that we’ve subscribed you to a mailing list for expert-specific announcements from IANA. We’ll send a message to this list if we need to announce a survey or describe a new process, but don’t anticipate contacting you more than once or twice a year, if that.
If you have any questions or suggestions for us, or if you need to update the contact information in our internal directory, please send a message to iana(a)iana.org. That address points to a heavily-monitored ticketing system and should be picked up within a day.
We don’t need any action from you, but before signing off, I’ll use this message to provide some information about IANA processes. You’ve likely read most of the following in a welcome email or a “designated expert status check” message, but while you’re here:
IANA has two registration review request processes: one for requests made by individuals/organizations, and another for registrations that won’t be completed until the I-D that describes them is approved for publication as an RFC.
In the former case:
* Unless the relevant RFC tells the applicant to send their request directly to an expert mailing list (these are not monitored by us), we receive their request via email or one of the forms at https://www.iana.org/protocols/apply.
* We forward it to you in an email that has a ticket number in the subject line.
* If you have comments/questions, we forward them to the requester (without including your name), unless you prefer to write the requester directly (ideally copying us in the process, with the ticket number in the subject line).
When an I-D asks for registration in an Expert Review or Specification Required registry, the authors can use that process to request permanent registration before IETF Last Call (at the expert’s discretion). However, we usually don’t see those registration requests until IETF Last Call or Conflict Review. At that point:
* We send a review request to the experts, with the document’s WG (if applicable) in copy.
* If you approve, unless directed otherwise, we'll wait to update the registry until the IESG approves the document.
* We aren’t notified when documents are updated, but we re-check them before the IESG telechat and after IESG approval. If we find that changes have been made, we may ask you (or the AD, if we can't reach you quickly) whether it needs another review.
If you don’t/can’t reply:
* IANA has been asked to set a two-week deadline for experts. If we don't receive a response, and there is no secondary expert, we'll likely try contacting you from outside our ticketing system before we ask for help. (Note that we require only that you respond, not that a final decision be made. Also, we understand that a few RFCs set a three- or four-week deadline instead.)
* If you’re unable to make a decision or feel you have a conflict of interest, we can ask the ADs for help.
* If we don’t hear from you within 30 days, we’ll escalate to an AD.
* If there’s a chance that a request could come in while you’re on leave, and you’re the only reviewer, please drop us a line at iana(a)iana.org.
Additional information:
* IANA does not monitor expert mailing lists. If the RFC for your registry tells the applicant to send their request to a mailing list, the experts must send the request to us upon approval.
* If IANA receives an RFC 7120 early allocation request for a Specification Required registration, IANA will ask which (if any) of the following is appropriate: an RFC 7120 early allocation (which is renewable, but marked “TEMPORARY” in the registry); an immediate permanent allocation; or no allocation until the document is approved by the IESG.
If you’re part of an expert team, we should have asked you whether we should consider a review complete after one expert responds (our default practice) or whether you’d like us to wait for a majority, wait for everyone, wait for 48 hours after the first response, etc. Whichever practice you’ve established, we’ll wait for more experts if you believe it’s appropriate for that particular request.
If you’re part of a team but never received that email, or if you’ve never received an email from IANA’s ticketing system at all (the subject line would begin with “[IANA #” followed by a number), please contact me at amanda.baber(a)iana.org. We may be having trouble reaching you from our system.
If you provided any backup addresses, we’ve added them to the subscriber list as well. If you’d like me to remove any of them from this list (but not our internal directory), just let me know.
Thanks and best regards,
Amanda Baber
IANA Operations Manager
