Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] new version of policy proposal AFPUB-2019-ASN-DRAFT03 "Multihoming not required for ASN"

Owen DeLong owen at delong.com
Wed Nov 13 01:06:54 UTC 2019





> On Nov 12, 2019, at 02:04 , JORDI PALET MARTINEZ via RPD <rpd at afrinic.net> wrote:

>

> Hi Owen,

>

> In the previous meeting, that sentence with the private ASNs was already there, nobody objected to it, including yourself. That's why I didn't modified that part.


I apologize for not previously noticing it.


> I think it provides clarity, however, if is a problem for anyone, I'm happy to remove that. A middle way alterative is a footnote:


A footnote still duplicates data unnecessarily and creates a need to update the CPM any time the IETF chooses to adjust the private ASN range(s). We should avoid duplicating IETF information in policy to avoid the risk of it falling out of sync.


> It is important to determine which sites require unique AS Numbers. Sites which do not require a unique AS Number should use one or more of the AS Numbers reserved for private use*.

>

> *Those numbers are: 64,512 - 65,535 and 4,200,000,000 - 4,294,967,294 (RFC1930, RFC6996 and possible future updates) - date of publication.

>

> Will you agree on that?

>

> Regarding your point on 7.2.2, your wording "technical need", an ISP that has a single upstream and that single upstream is mandating to provide BGP a public ASN, I think will not fall into "technical need”.


It certainly falls into “Unique Routing Policy”, but I would say that it also meets the definition of “technical need”, since the affected organization cannot technically route their addresses via said provider without a public ASN.

Owen


>

> Regards,

> Jordi

> @jordipalet

>

>

>

> El 12/11/19 2:57, "Owen DeLong" <owen at delong.com <mailto:owen at delong.com>> escribió:

>

> Oppose as written.

>

> Adding the specific AS numbers for private use to 7.2 is an unnecessary duplication of data that has no mechanism for preserving synchronization with reality.

>

> Take that out and I would support the policy as written, tough I would prefer to replace 7.2.2 with:

>

> 7.2.2 Show a unique routing policy or demonstrate a technical need for a coordinated globally unique ASN.

>

> Owen

>

>

>> On Nov 11, 2019, at 01:50 , JORDI PALET MARTINEZ via RPD <rpd at afrinic.net> wrote:

>>

>> Hi all,

>>

>> One of the policy proposals that I've updated a week ago, is attached in PDF.

>>

>> As usual, it tries to address the inputs from the list, meeting and staff analysis.

>>

>> Please, let me know any inputs.

>>

>> Regards,

>> Jordi

>> @jordipalet

>>

>>

>>

>>

>>

>> **********************************************

>> IPv4 is over

>> Are you ready for the new Internet ?

>> http://www.theipv6company.com

>> The IPv6 Company

>>

>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

>>

>> <AfriNIC-ASN-no-multihoming-v3.pdf>_______________________________________________

>> RPD mailing list

>> RPD at afrinic.net

>> https://lists.afrinic.net/mailman/listinfo/rpd

>

>

>

>

>

> **********************************************

> IPv4 is over

> Are you ready for the new Internet ?

> http://www.theipv6company.com <http://www.theipv6company.com/>

> The IPv6 Company

>

> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

>

>

>

>

> _______________________________________________

> RPD mailing list

> RPD at afrinic.net <mailto:RPD at afrinic.net>

> https://lists.afrinic.net/mailman/listinfo/rpd <https://lists.afrinic.net/mailman/listinfo/rpd>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20191112/056b0a24/attachment-0001.html>


More information about the RPD mailing list