In a 32-bit ASN world..in cases where one might choose to use a
private-asn, such as being multi-homed to the same provider, if an
organization wants to use a public ASN we shouldn't discourage that
through policy, as it also allows an organization to easily become BGP
multihomed in the future.
Andrew
On 7/21/2021 5:11 PM, Martin Hannigan wrote:
I’m not endorsing anything, but the remarks that Chris regarding the
content he commented on were good observations that are typical of our
lack of writing standards for the NRPM. I could see budget being spent
on improving that.
Andrew: How does a public 32 bit ASN reduce the need to use a private ASN?
Warm regards,
-M<
On Wed, Jul 21, 2021 at 4:38 PM Andrew Dul <andrew....@quark.net
<mailto:andrew....@quark.net>> wrote:
Based upon the input we have received from ARIN staff it seems that
additional clarity is desired in section 5 for ASN assignments.
I am not convinced however that the current draft text is the best
way
to fix the issues raised so far. I don't have specific test
suggestions
at this point but believe we should discuss how the text should be
improved in light of how ASNs are now being used by various cloud
providers and the fact that ASNs are now 32-bits in length which
in many
cases reduces the need to use private AS numbers.
Andrew
On 7/20/2021 5:23 PM, Chris Woodfield wrote:
> Speaking in support, but I’d like to recommend an adjustment in
the proposal text. I think the phrase “unique routing policy, such
as BGP” is technically incorrect; BGP is a protocol, not a policy.
BGP is how a network *communicates* the relevant aspects of its
unique routing policy to its peers, but is not the policy in and
of itself.
>
> As such, where the proposal text says “unique routing policy,
such as BGP”, I think this should read “unique routing policy,
implemented via BGP” - that should fix the bug here.
>
> Hope this helps,
>
> -C
>
>> On Jul 20, 2021, at 12:52 PM, ARIN <i...@arin.net
<mailto:i...@arin.net>> wrote:
>>
>> On 15 July 2021, the ARIN Advisory Council (AC) accepted
"ARIN-prop-298: Private AS Number and Unique Routing Policy
Clarifications" as a Draft Policy.
>>
>> Draft Policy ARIN-2021-3 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/>
>>
>> You are encouraged to discuss all Draft Policies on PPML. The
AC will evaluate the discussion in order to assess the conformance
of this draft policy with ARIN's Principles of Internet number
resource policy as stated in the Policy Development Process (PDP).
Specifically, these principles are:
>>
>> * Enabling Fair and Impartial Number Resource Administration
>> * Technically Sound
>> * Supported by the Community
>>
>> The PDP can be found at:
>> https://www.arin.net/participate/policy/pdp/
<https://www.arin.net/participate/policy/pdp/>
>>
>> Draft Policies and Proposals under discussion can be found at:
>> https://www.arin.net/participate/policy/drafts/
<https://www.arin.net/participate/policy/drafts/>
>>
>> Regards,
>>
>> Sean Hopkins
>> Senior Policy Analyst
>> American Registry for Internet Numbers (ARIN)
>>
>>
>>
>> Draft Policy ARIN-2021-3: Private AS Number and Unique Routing
Policy Clarifications
>>
>> Problem Statement:
>>
>> At ARIN 47, staff identified three points of potential
confusion with current text in NRPM Section 5: AS Numbers.
>>
>> 1. “Sites that do not require a unique AS Number should use one
or more of the AS Numbers reserved for private use.” Some
customers are not aware that their need for a unique AS Number
depends upon their need (or lack thereof) to utilize the AS Number
on the public Internet.
>>
>> 2. “In order to be assigned an AS Number, each requesting
organization must provide ARIN with verification that it has one
of the following…A unique routing policy (its policy differs from
its border gateway peers)…A multihomed site.” Few customers
qualify for an AS Number under the “unique routing policy”
requirement, specifically because they aren’t aware of what
“unique routing policy” applies to.
>>
>> 3. “AS Numbers are issued based on current need. An
organization should request an AS Number only when it is already
multihomed or will immediately become multihomed.” All ARIN
delegations are based on current needs, and some customers aren’t
aware they need network plans when they request an AS Number.
Additionally, clarification that some organizations may have a
unique need for an AS Number outside of utilizing a unique routing
policy, such as BGP.
>>
>> Policy statement:
>>
>> In Section 5 -
>>
>> Replace
>>
>> “Sites that do not require a unique AS Number should use one or
more of the AS Numbers reserved for private use.”
>>
>> with
>>
>> “Private ASNs should be used only when there is no plan to use
them on the public Internet.”
>>
>> Replace
>>
>> “1. A unique routing policy (its policy differs from its border
gateway peers) 2. A multihomed site.”
>>
>> with
>>
>> “1. A plan to connect their network using a unique routing
policy, such as Border Gateway Protocol (BGP) 2. A network
requiring routing policies to be deployed which are unique only to
that network”
>>
>> Replace
>>
>> “AS Numbers are issued based on current need. An organization
should request an AS Number only when it is already multihomed or
will immediately become multihomed.”
>>
>> with
>>
>> “AS Numbers should be requested when an organization has
network plans ready and is either planning to use a unique routing
policy (such as BGP) or has a unique need for an AS Number.”
>>
>> Timetable for implementation: Immediate
>>
>>
>>
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML@arin.net
<mailto:ARIN-PPML@arin.net>).
>> Unsubscribe or manage your mailing list subscription at:
>> https://lists.arin.net/mailman/listinfo/arin-ppml
<https://lists.arin.net/mailman/listinfo/arin-ppml>
>> Please contact i...@arin.net <mailto:i...@arin.net> if you
experience any issues.
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML@arin.net
<mailto:ARIN-PPML@arin.net>).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
<https://lists.arin.net/mailman/listinfo/arin-ppml>
> Please contact i...@arin.net <mailto:i...@arin.net> if you
experience any issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net
<mailto:ARIN-PPML@arin.net>).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
<https://lists.arin.net/mailman/listinfo/arin-ppml>
Please contact i...@arin.net <mailto:i...@arin.net> if you
experience any issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.
