+1 with "Registrations not created through IETF consensus can also be removed or deactivated by the original registrant, in consultation with the Designated Experts."
-- JG James Gould Fellow Engineer [email protected] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 2/26/26, 2:34 PM, "Andy Newton" <[email protected] <mailto:[email protected]>> wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 2/26/26 12:33 PM, Hollenbeck, Scott wrote: > "Registrations created through IETF consensus can only be removed or > deactivated with IESG Approval (see [RFC8126]). Registrations not created > through IETF consensus can be removed or deactivated with the approval of the > IESG, in consultation with or at the request of the Designated Experts." > > If so, that still leaves out the evaluation criteria for a request to remove > or deactivate a registration not created through IETF consensus received from > someone other than the IESG. Can we add this? > > "Registrations not created through IETF consensus can also be removed or > deactivated by the original registrant, in consultation with the Designated > Experts." Good catch. +1 Thanks, -andy _______________________________________________ regext mailing list -- [email protected] <mailto:[email protected]> To unsubscribe send an email to [email protected] <mailto:[email protected]> _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
