IANA generally won't contact secondary experts unless the primary can't respond. (We should probably document this in 8126bis.) However, some registries only have co-primary experts. When that's the case, we'll contact them after designation to work out consensus protocol, with the understanding that they can decide to change how many approvals should be required at any time, even on a per-request basis. We'd recommend not recording how many approvals are required in the RFC.
Thanks,
Amanda Baber
IANA Operations Manager
On 3/11/25, 9:22 AM, "Esko Dijk" <esko.dijk@xxxxxxxxxxxxxxxxx> wrote:
> I am not a DE of this particular registry, but Esko is, so he may
> provide some insight into their setup.
There's no formal definition anywhere that I'm aware of. The registry does use one "primary" expert and multiple "secondary" experts currently.
This suggests that the primary expert is contacted first by IANA. In practice any one expert can make the decision without requiring consensus or discussion with other experts.
For me ok to leave this all to 'DE / IANA self-organization'.
Esko
-----Original Message-----
From: Thomas Fossati <thomas.fossati@xxxxxxxxxx>
Sent: maandag 10 maart 2025 16:33
To: Salz, Rich <rsalz@xxxxxxxxxx>
Cc: secdir@xxxxxxxx; core@xxxxxxxx; draft-ietf-core-cf-reg-update.all@xxxxxxxx; last-call@xxxxxxxx
Subject: Re: Secdir last call review of draft-ietf-core-cf-reg-update-05
On Mon, 10 Mar 2025 at 16:05, Salz, Rich <rsalz@xxxxxxxxxx> wrote:
> > Sec 4.4 should clarify state explicitly if there is one DE, or
> > multiple and what the quorum is.
>
> Is the DE team’s composition and consensus protocol usually explicitly
> defined? My instinct is to let the DEs self-organise on such matters.
>
> In my experience (TLS registries and and NTP registry RFC), those are explicitly put in the doc so that the IESG can review and decide how many to pick. Shrug, if it works with your AD, then fine.
Francesca's AD review didn't raise this as an issue, so I presume
she's OK with the current state of affairs.
I am not a DE of this particular registry, but Esko is, so he may
provide some insight into their setup.
> So overall, my concerns are addressed.
Thanks again for your time & consideration.
--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx
<<attachment: smime.p7s>>
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
