That also works for me.

Owen


> On Mar 15, 2022, at 12:42 , Andrew Dul <[email protected]> wrote:
> 
> I'd like to propose another option for the last part of section5, to make it 
> clear that a planning and implementation period is permissible.
> 
> 
> "AS Numbers shall be issued to organizations meeting section 5 criteria and 
> up to 12 months prior to planned implementation on their network."
> 
> 
> 
> On 3/8/2022 7:54 PM, Owen DeLong via ARIN-PPML wrote:
>> I’m fine with all but the last change… The new wording is potentially more 
>> problematic than the old wording in that “current need” might imply that one 
>> needs to already be multi homed before one can get an ASN, which creates a 
>> bit of a catch-22 which is the reason for the “or immediately become…” 
>> language.
>> 
>> I suggest instead that we consider the following:
>> 
>> AS Numbers are based on current need, as set out in this section 5. However, 
>> a site which plans to begin exchanging inter domain routing protocols with 
>> other autonomous systems upon receipt of the ASN requested is considered to 
>> have current need.
>> 
>> This would, IMHO, have the clarifying effect which is sought in the problem 
>> statement.
>> 
>> Owen
>> 
>> 
>>> On Mar 8, 2022, at 06:51, ARIN <[email protected] <mailto:[email protected]>> 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/>
>>>  
>>> You are encouraged to discuss all Draft Policies on PPML. The AC will 
>>> evaluate the discussion 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.
>>>  
>>> “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 unique AS Numbers depends upon their need (or lack thereof) 
>>> to                   interconnect with other organizations’ Autonomous 
>>> Systems.
>>>  
>>> “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 AS Numbers under the “unique 
>>> routing policy” requirement, because they don’t understand what “unique 
>>> routing policy” actually means in practice.
>>>  
>>> “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 AS 
>>> Numbers. Additionally, clarification that some organizations may have a 
>>> unique need for an AS Number outside of utilizing a unique routing policy, 
>>> such as one implemented using, for example, a protocol such as Border 
>>> Gateway Protocol (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
>>>  
>>> “If a unique AS Number is not required for a given network design, one or 
>>> more of the AS Numbers reserved for private use should be utilized.”
>>>  
>>> Replace
>>>  
>>> “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) 2. A multihomed site”
>>>  
>>> with
>>>  
>>> “In order to be assigned an AS Number, each requesting organization must 
>>> provide ARIN with verification that it requires a unique routing policy, 
>>> such as a plan:
>>>  
>>>     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 upstream provider;
>>>  
>>>     To multihome a site with one or more Autonomous Systems; or
>>>  
>>>     To use an AS Number to interconnect with other Autonomous Systems.”
>>>  
>>> 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 are issued based on current need, as set out in this section 5.”
>>> _______________________________________________
>>> ARIN-PPML
>>> You are receiving this message because you are subscribed to
>>> the ARIN Public Policy Mailing List ([email protected] 
>>> <mailto:[email protected]>).
>>> 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 [email protected] <mailto:[email protected]> if you experience any 
>>> issues.
>> 
>> 
>> 
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List ([email protected] 
>> <mailto:[email protected]>).
>> 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 [email protected] <mailto:[email protected]> if you experience any 
>> issues.
> 
> _______________________________________________
> 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.

_______________________________________________
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.

Reply via email to