RT-Owner: amanda.baber
From: "Amanda Baber via RT" <iana-issues@iana.org>
In-Reply-To: <rt-5.0.3-1040798-1761848103-87.1435506-37-0@icann.org>
References: <RT-Ticket-1435506@icann.org>
 <rt-5.0.3-1040798-1761848103-87.1435506-37-0@icann.org>
Message-ID: <rt-5.0.3-1064555-1761867473-956.1435506-37-0@icann.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Date: Thu, 30 Oct 2025 23:37:53 +0000
MIME-Version: 1.0
Message-ID-Hash: NSFWHKWTUWTU323MF66YLZRAN2LMA3PQ
CC: draft-ietf-idr-bgp4-rfc4271bis.all@ietf.org, idr@ietf.org
Reply-To: iana-issues@iana.org
Subject: =?utf-8?q?=5BIdr=5D_=5BIANA_=231435506=5D_Early_review=3A_draft-ietf-idr-bgp?=
	=?utf-8?q?4-rfc4271bis-00_=28IETF_124=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/idr/N0tKzuPXU_GSM5dhREIWN06ESgo>

Dear Authors (cc: idr WG),

Before the IETF meeting, we check working group agendas for documents with =
IANA-related issues. We have notes about this document:

https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp4-rfc4271bis-00

1) References to RFC 4020 should be replaced with references to RFC 7120. (=
For what it=E2=80=99s worth, draft-baber-ianabis-rfc7120bis should proceed =
to IANABIS WGLC soon.)

2) RFC 7313 changed the name of the =E2=80=9CBGP Error Codes=E2=80=9D regis=
try to =E2=80=9CBGP Error (Notification) Codes.=E2=80=9D

3) =E2=80=9CError Subcodes=E2=80=9D is listed at https://www.iana.org/assig=
nments/bgp-parameters as =E2=80=9CBGP Error Subcodes.=E2=80=9D I can=E2=80=
=99t locate the source of this change, but we generally recommend keeping t=
he =E2=80=9C<protocol name> <registry name>=E2=80=9D naming pattern.

4) The IPFIX registries include multiple references to RFC 4271:

https://www.iana.org/assignments/ipfix

Most of these appear in description fields, but there's also one in a IPFIX=
 MPLS label type (Value 46) registration made by RFC 5102. (This was origin=
ally housed in a table in the description field for IPFIX Information Eleme=
nt 46, but the table was turned into a subregistry.) If it's correct to rep=
lace those references, please add a sentence like "IANA will replace all re=
ferences to RFC 4271 in the IP Flow Information Export (IPFIX) Entities reg=
istry group at https://www.iana.org/assignments/ipfix with references to th=
is document."

If you have any questions, just let us know. If you'd like to talk in perso=
n, you can find us next to the RFC Editor's table from Monday through Thurs=
day. You can also request another review at any time by contacting us at ia=
na@iana.org.

For more information about IANA Considerations section requirements, please=
 see

https://www.iana.org/help/protocol-registration

Best regards,

Amanda Baber
IANA