> On Mar 22, 2022, at 13:39 , Jay Hennigan <[email protected]> wrote: > > On 3/8/22 06:51, ARIN wrote: >> The following Draft Policy has been revised: >> * ARIN-2021-3: Private AS Number and Unique Routing Policy Clarifications >> Revised text is below and can be found at: >> https://www.arin.net/participate/policy/drafts/2021_3/ >> <https://www.arin.net/participate/policy/drafts/2021_3/> > > I concur that "peer" be substituted for "upstream provider" in the first > statement below. > > > To originate announcement of IP Number Resources via an accepted > > protocol (such as Border Gateway Protocol) from an AS Number different > > > than that of its peer; > > I think that the word "network" should be substituted for "site" below, as > the multihoming may originate from multiple locations. > > > To multihome a network with one or more Autonomous Systems; or > > I'm not sure what value the third statement below offers that isn't covered > by either of the first two, and it seems to weaken the case that public ASNs > must be justified. I suggest removing it unless I'm missing > a use case not covered by either of the previous two. > > > To use an AS Number to interconnect with other Autonomous Systems.”
I’d be OK with that, but alternatively, I think the most efficient would be to simply remove the first two which are as near as I can tell entirely subsets of the third. Owen _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
