RE: Address Space ASN Allocation Process
I think this is operational... I beg to differ: http://www.arin.net/policy/nrpm.html#four3 I have done this for a customer, and they got a /22. There is also a policy proposal right now that would allow an end user to get a BGP ASN, get RIR IP space and do it all at once... http://www.arin.net/policy/proposals/2005_7.htmlh Robert Seastrom is the author of this... Robert, you out there ?? 4.3.2. Minimum assignment 4.3.2.1 Single Connection The minimum block of IP address space assigned by ARIN to end-users is a /20. If assignments smaller than /20 are needed, end-users should contact their upstream provider. 4.3.2.2 Multihomed Connection For multihomed end-users, the minimum block of IP address space assigned is a /22. If assignments smaller than a /22 are needed, multihomed end-users should contact their upstream providers. When prefixes are assigned which are longer than /20, they will be from a block reserved for that purpose. I hope this helps... Jim -Original Message- From: sjk [mailto:[EMAIL PROTECTED] Sent: Monday, September 26, 2005 6:47 PM To: Vicky Rode Cc: nanog@merit.edu Subject: Re: Address Space ASN Allocation Process On Mon, 26 Sep 2005, Vicky Rode wrote: Hi, Just trying to get some clarity and direction regarding obtaining address space/ASN for my client. Is there a minimum address space (?) an entity would need to justify to go directly to RIR (ARIN in this case) as opposed to the upstream provider? Is /20 the minimum allocation? Can my client approach RIR and request for a /23? If my client do procure a /23 how do they make make sure that this address space will be globally routable? Multihome will also be part of their network implementation, can they apply for an ASN number? Yes, minimum assignment is /20 (and this is considered temporary, as the official minimum is /19) -- there used to be some experimental /24s, but I believe these are now gone. ARIN will only assign /20 or more -- larger prefixes must come from your upstream provider. Being multihomed means you will be required to get an AS number. Once you have your address block, you can fill out the request from ARIN. --sjk
Address Space ASN Allocation Process
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Just trying to get some clarity and direction regarding obtaining address space/ASN for my client. Is there a minimum address space (?) an entity would need to justify to go directly to RIR (ARIN in this case) as opposed to the upstream provider? Is /20 the minimum allocation? Can my client approach RIR and request for a /23? If my client do procure a /23 how do they make make sure that this address space will be globally routable? Multihome will also be part of their network implementation, can they apply for an ASN number? Any insight will be appreciated. regards, /vicky -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDOHZ1pbZvCIJx1bcRAihfAJwLF026eea0TxIt5nww7/jCr4YBxQCg57M/ zTUBKD1pkuE7S3NHnjqyqPU= =lWUk -END PGP SIGNATURE-
Re: Address Space ASN Allocation Process
On Mon, 26 Sep 2005, Vicky Rode wrote: Hi, Just trying to get some clarity and direction regarding obtaining address space/ASN for my client. Is there a minimum address space (?) an entity would need to justify to go directly to RIR (ARIN in this case) as opposed to the upstream provider? Is /20 the minimum allocation? Can my client approach RIR and request for a /23? If my client do procure a /23 how do they make make sure that this address space will be globally routable? Multihome will also be part of their network implementation, can they apply for an ASN number? Yes, minimum assignment is /20 (and this is considered temporary, as the official minimum is /19) -- there used to be some experimental /24s, but I believe these are now gone. ARIN will only assign /20 or more -- larger prefixes must come from your upstream provider. Being multihomed means you will be required to get an AS number. Once you have your address block, you can fill out the request from ARIN. --sjk
RE: Address Space ASN Allocation Process
Hi, Just trying to get some clarity and direction regarding obtaining address space/ASN for my client. Is there a minimum address space (?) an entity would need to justify to go directly to RIR (ARIN in this case) as opposed to the upstream provider? Is /20 the minimum allocation? Can my client approach RIR and request for a /23? The minimum assignment from ARIN is actually a /22, which will only be given to multi-homed end-users who qualify (http://www.arin.net/policy/nrpm.html#four3). Other than that, the smallest assignment is /20. If my client do procure a /23 how do they make make sure that this address space will be globally routable? Regardless of where their IP's come from, all they have to do is announce them to their upstream providers using BGP. Multihome will also be part of their network implementation, can they apply for an ASN number? Yes, they can apply for an ASN number as long as they can show ARIN that they are in the process of bringing up connectivity with more than one ISP. ARIN's web page is actually pretty easy to navigate for finding this and all the other information you will need. I would suggest checking it out. http://www.arin.net ~ Rob Reeves IP Network Engineer Arbinet 703-456-4172 [EMAIL PROTECTED] ~
Re: Address Space ASN Allocation Process
On Mon, 26 Sep 2005, Vicky Rode wrote: Just trying to get some clarity and direction regarding obtaining address space/ASN for my client. Is there a minimum address space (?) an entity would need to justify to go directly to RIR (ARIN in this case) as opposed to the upstream provider? Is /20 the minimum allocation? Can my client approach RIR and request for a /23? If you ask for a /23, at this point, ARIN will most likely tell them to get additional space from their upstream. If the organization is utilizing at least a /23's worth of space now and ready to multihome, they can request a /22 from ARIN. Their IPv4 allocation policies are documented here: http://www.arin.net/policy/nrpm.html#four If my client do procure a /23 how do they make make sure that this address space will be globally routable? I would recommend they register a maintainer, AS and appropriate route objects in the RADB or one of the many IRR mirrors. Some carriers build their filters based off of IRR data. That's still not a guarantee of global routability, but keeping their records in good order is a good start. Multihome will also be part of their network implementation, can they apply for an ASN number? They can apply if they're close to being ready (within 30 days) to multihome. You (your client) needs to be able to announce at least one /24 to two or more upstream providers in order to meet ARIN's criteria for assignment of an ASN. ARIN's ASN criteria are documented here: http://www.arin.net/registration/guidelines/asn.html jms
Re: Address Space ASN Allocation Process
On Sep 26, 2005, at 8:27 PM, Justin M. Streiner wrote: I would recommend they register a maintainer, AS and appropriate route objects in the RADB or one of the many IRR mirrors. Some carriers build their filters based off of IRR data. That's still not a guarantee of global routability, but keeping their records in good order is a good start. I'll second the route registry suggestion. We turned up BGP about a year ago, and found that most of our traffic got bit-bucketed by big edge networks without registering routes. If you don't want to pay RADB, you can use AltDB. --Chris
