I strongly take position that at least one AS any company may have in advance. It's nothing, but it's make further pain is void. On Tue, 7 May 2019 at 16:55, Hansen, Christoffer <christoffer@netravnen.de> wrote:
On 07/05/2019 14:18, Aled Morris via address-policy-wg wrote:
I'm in the process of helping a startup ISP get RIPE membership and resources and have hit against a little bit of poor wording in the AS guidelines RIPE-679, specifically:
*A network must be multihomed in order to qualify for an AS Number.*
The application for an AS number has been delayed because the NCC analyst working on the ticket is claiming the ISP has to be *already multihomed* before an AS can be issued.
This interpretation doesn't make any sense to me. Surely the intention *to become multihomed* should be the requirement for obtaining an AS number?
I don't even see how you can be properly multihomed if you don't have an AS number. Are we supposed to implement some kind of NAT multihoming first?
Can we look to change the wording in RIPE-679 to make this clear?
Pointing to RFC 1930 and pointing out you will want to move - from "Single-homed site, multiple prefixes" - to "Multi-homed site, multiple prefixes" requires you be assigned an ASN.
You can ask the the NCC analyst, if it is alright to provide them with agreements with existing upstream provider A and future upstream provider B is sufficient to be assigned the ASN(?)
-Christoffer
----
https://tools.ietf.org/html/rfc1930#section-5.1
* Single-homed site, multiple prefixes
Again, a separate AS is not needed; the prefixes should be placed in an AS of the site's provider.
* Multi-homed site
Here multi-homed is taken to mean a prefix or group of prefixes which connects to more than one service provider (i.e. more than one AS with its own routing policy). It does not mean a network multi-homed running an IGP for the purposes of resilience.
An AS is required; the site's prefixes should be part of a single AS, distinct from the ASes of its service providers. This allows the customer the ability to have a different repre- sentation of policy and preference among the different service providers. This is ALMOST THE ONLY case where a network operator should create its own AS number. In this case, the site should ensure that it has the necessary facilities to run appropriate routing protocols, such as BGP4.