[rpd] new version of "Multihoming not required for ASN"(AFPUB-2019-ASN-DRAFT04)

[JORDI PALET MARTINEZ]

Hi Fernando,

 

I think they read the same, as explained by Owen. I asked him about that when he proposed that text and I thought about that many times.

 

I think it is clear that if you have a single upstream provider and ask you for a public ASN, it is a technical requirement for *that connection*.

 

The “or” with the rest of the sentence mean that “both” are choices.

 

Note that was the main motivation to have this policy change (single upstream, no other peerings).

 

Regards,

Jordi

@jordipalet

 

 

 

El 25/11/19 16:44, "Fernando Frediani" <fhfrediani at gmail.com> escribió:

 

Hello Jordi

The change you made on 7.2.2 from "Single interconnection, with a provider that requires a public" to "Show a unique routing policy or demonstrate a technical need for a coordinated globally unique" means different things in my view and may make things slightly more difficult for organizations to receive an ASN.

When it says "show a unique routing policy" doesn't necessarily mean two Transit providers  (it could be an IX, a private peering to another ASN, etc), but excludes the possibility to have an ASN with a single Transit Upstream. On the second part that says "demonstrate a technical need for a coordinated globally unique ASN" what kind of technical need could for example be acceptable to justify to have an ASN with a single Transit Upstream provider (have their own assigned IP space ?) ?
My concern is not to exclude de possibility for organizations to have an ASN even if they have a single interconnection with their Transit Upstream.

Could you clarify this please ?

Thanks
Fernando Frediani

On 25/11/2019 08:45, JORDI PALET MARTINEZ via RPD wrote:
Hi all,
 
Find attached a new version of the proposal "Multihoming not required for ASN", following the latest inputs in the list.
 
I've also prepared an online diff of the changes to the proposed policy text, so it is easy to track:
 
https://www.diffchecker.com/omm6xj7m
 
 
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.
 


_______________________________________________
RPD mailing list
RPD at afrinic.net
https://lists.afrinic.net/mailman/listinfo/rpd
_______________________________________________ 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
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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20191125/508c4e2b/attachment-0001.html>