Hi,
I know I have a thing for picking stuff like this... but...
What does the list think about taking a shot at some revisions to
RFC1930/BCP6? I would argue that this is somewhat in-scope for GROW.
Specifically, I'd argue that it might make sense to revisit the strict
multi-homed requirement; As of now, iirc, the only RIR requiring that
is RIPE.
Thank you for bringing this up here as well. :)
RFC 1930 was written in 1996. The five modern RIRs were variously formed
between 1992 and 2004, and the NRO was established in 2003. ICANN was founded
in 1998.
The concept of "internet governance" as it applies to number resources is quite
different today than it was when RFC 1930 was written. The RIRs all have established
roles and processes around policy, they collaborate together under the umbrella of the
NRO and the roles of ICANN and the ASO in all of this are more clearly understood.
RFC 1930 is documentation of historical consensus, and it contributes to policy
in 2025 rather than specifying it. The kind of policy I mean is more commonly
developed in other organisations and communities today than the IETF.
RFC 1930 is very much alive and active policy in RIPE, AFRINIC and APNIC.
https://www.ripe.net/publications/docs/ripe-679/
https://afrinic.net/policy/manual#ASN-Eligibility
https://www.apnic.net/community/policy/resources#a_h_10_0
On RIPE Address policy WG mailing list I've wrote:
Four octet (32 bit) ASNs were defined in May 2007 in RFC 4893. It has taken
several years for routing equipment in general use to catch up, but with 32 bit
AS numbers, ASN are not a scarce resource anymore.
IANA has assigned 402332 ASN to RIRs which is ~0.01 % of available 32 bit ASN
space. While RIRs have assigned only around, 88400 to network operators, which
represents ~0,002 % of available 32 bit ASN.
*Our policies should reflect that, and we should utilize number
resources in such a way to help network operators reduce operational
complexity and increase visibility for operating and troubleshooting
networks.*
...with having RFC 1930 and RFC 2270 in mind.
Essentially, I agree that this is a historic consensus, but it still
actively in use in RIR policies, while I don't believe that it serves
its purpose anymore.
I think we should open a conversation if these RFC still serve their
intended purpose and update their status accordingly.
Best,
Urban Suhadolnik
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]
