Many thanks. I wasn’t aware of this. G/
Sent from Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Amanda Baber <amanda.ba...@iana.org> Sent: Monday, April 14, 2025 7:23 PM To: Gunter van de Velde (Nokia) <gunter.van_de_ve...@nokia.com>; The IESG <i...@ietf.org> Cc: draft-ietf-anima-brski-...@ietf.org <draft-ietf-anima-brski-...@ietf.org>; anima-cha...@ietf.org <anima-cha...@ietf.org>; anima@ietf.org <anima@ietf.org>; i...@kovatsch.net <i...@kovatsch.net>; t...@cs.fau.de <t...@cs.fau.de> Subject: Re: [Ext] Gunter Van de Velde's No Objection on draft-ietf-anima-brski-prm-18: (with COMMENT) Hi Gunter, RFC 6335 (Section 8.1.1) requires that IETF Stream documents list the IESG as the assignee and the IETF Chair as the contact for port and service name registrations: https://datatracker.ietf.org/doc/html/rfc6335#section-8.1.1 Thanks, Amanda 3789 10.2. Service Name and Transport Protocol Port Number Registry 3790 3791 IANA has registered the following service names: 3792 3793 *Service Name:* brski-pledge 3794 *Transport Protocol(s):* tcp 3795 *Assignee:* IESG i...@ietf.org (mailto:i...@ietf.org) 3796 *Contact:* IETF Chair ch...@ietf.org (mailto:ch...@ietf.org) 3797 *Description:* The Bootstrapping Remote Secure Key Infrastructure 3798 Pledge 3799 *Reference:* [THISRFC] GV> Does this need to be the iesg and the chair to be as assignee and contact? At first glance this looks unusual. This seems to have happened in v18 of the draft. Gunter Van de Velde RTG Area Director
_______________________________________________ Anima mailing list -- anima@ietf.org To unsubscribe send an email to anima-le...@ietf.org
