<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">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.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Andrew<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 7/21/2021 5:11 PM, Martin Hannigan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMDXq5N8d77DqCv2bsabvjCj9HPCQqu0ejydsBfKFUbQJ7x2qA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div><br>
</div>
<div dir="auto">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. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Andrew: How does a public 32 bit ASN reduce the
need to use a private ASN?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Warm regards,</div>
<div dir="auto"><br>
</div>
<div dir="auto">-M<</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jul 21, 2021 at 4:38
PM Andrew Dul <<a href="mailto:andrew.dul@quark.net"
moz-do-not-send="true">andrew.dul@quark.net</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Based
upon the input we have received from ARIN staff it seems
that <br>
additional clarity is desired in section 5 for ASN
assignments.<br>
<br>
I am not convinced however that the current draft text is
the best way <br>
to fix the issues raised so far. I don't have specific test
suggestions <br>
at this point but believe we should discuss how the text
should be <br>
improved in light of how ASNs are now being used by various
cloud <br>
providers and the fact that ASNs are now 32-bits in length
which in many <br>
cases reduces the need to use private AS numbers.<br>
<br>
Andrew<br>
<br>
On 7/20/2021 5:23 PM, Chris Woodfield wrote:<br>
> 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.<br>
><br>
> 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.<br>
><br>
> Hope this helps,<br>
><br>
> -C<br>
><br>
>> On Jul 20, 2021, at 12:52 PM, ARIN <<a
href="mailto:info@arin.net" target="_blank"
moz-do-not-send="true">info@arin.net</a>> wrote:<br>
>><br>
>> 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.<br>
>> <br>
>> Draft Policy ARIN-2021-3 is below and can be found
at:<br>
>> <br>
>> <a
href="https://www.arin.net/participate/policy/drafts/2021_3/"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.arin.net/participate/policy/drafts/2021_3/</a><br>
>> <br>
>> 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:<br>
>> <br>
>> * Enabling Fair and Impartial Number Resource
Administration<br>
>> * Technically Sound<br>
>> * Supported by the Community<br>
>> <br>
>> The PDP can be found at:<br>
>> <a
href="https://www.arin.net/participate/policy/pdp/"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.arin.net/participate/policy/pdp/</a><br>
>> <br>
>> Draft Policies and Proposals under discussion can
be found at:<br>
>> <a
href="https://www.arin.net/participate/policy/drafts/"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.arin.net/participate/policy/drafts/</a><br>
>> <br>
>> Regards,<br>
>> <br>
>> Sean Hopkins<br>
>> Senior Policy Analyst<br>
>> American Registry for Internet Numbers (ARIN)<br>
>> <br>
>> <br>
>> <br>
>> Draft Policy ARIN-2021-3: Private AS Number and
Unique Routing Policy Clarifications<br>
>> <br>
>> Problem Statement:<br>
>> <br>
>> At ARIN 47, staff identified three points of
potential confusion with current text in NRPM Section 5: AS
Numbers.<br>
>> <br>
>> 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.<br>
>> <br>
>> 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.<br>
>> <br>
>> 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.<br>
>> <br>
>> Policy statement:<br>
>> <br>
>> In Section 5 -<br>
>> <br>
>> Replace<br>
>> <br>
>> “Sites that do not require a unique AS Number
should use one or more of the AS Numbers reserved for
private use.”<br>
>> <br>
>> with<br>
>> <br>
>> “Private ASNs should be used only when there is no
plan to use them on the public Internet.”<br>
>> <br>
>> Replace<br>
>> <br>
>> “1. A unique routing policy (its policy differs
from its border gateway peers) 2. A multihomed site.”<br>
>> <br>
>> with<br>
>> <br>
>> “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”<br>
>> <br>
>> Replace<br>
>> <br>
>> “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.”<br>
>> <br>
>> with<br>
>> <br>
>> “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.”<br>
>> <br>
>> Timetable for implementation: Immediate<br>
>> <br>
>> <br>
>> <br>
>> _______________________________________________<br>
>> ARIN-PPML<br>
>> You are receiving this message because you are
subscribed to<br>
>> the ARIN Public Policy Mailing List (<a
href="mailto:ARIN-PPML@arin.net" target="_blank"
moz-do-not-send="true">ARIN-PPML@arin.net</a>).<br>
>> Unsubscribe or manage your mailing list
subscription at:<br>
>> <a
href="https://lists.arin.net/mailman/listinfo/arin-ppml"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
>> Please contact <a href="mailto:info@arin.net"
target="_blank" moz-do-not-send="true">info@arin.net</a>
if you experience any issues.<br>
> _______________________________________________<br>
> ARIN-PPML<br>
> You are receiving this message because you are
subscribed to<br>
> the ARIN Public Policy Mailing List (<a
href="mailto:ARIN-PPML@arin.net" target="_blank"
moz-do-not-send="true">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription
at:<br>
> <a
href="https://lists.arin.net/mailman/listinfo/arin-ppml"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net"
target="_blank" moz-do-not-send="true">info@arin.net</a>
if you experience any issues.<br>
<br>
<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a
href="mailto:ARIN-PPML@arin.net" target="_blank"
moz-do-not-send="true">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net"
target="_blank" moz-do-not-send="true">info@arin.net</a>
if you experience any issues.<br>
</blockquote>
</div>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>