We currently have two /19 that we advertise on a single ASN. A client would like to obtain /23 or /22 from us. This is not a problem, except that their primary internet provider is someone else, other than us. I think that they would need to have their own ASN to advertise their portion of our ip space to their peers. My question is, should we provide the ASN or should they apply for an ASN? What is the minimum block considered routable, is it reasaonable to advertise a /23 on its own ASN? Are there any other solutions I haven't thought of? Thanks, Adi
On Dec 8, 2004, at 2:59 PM, Adi Linden wrote:
We currently have two /19 that we advertise on a single ASN. A client would like to obtain /23 or /22 from us. This is not a problem, except that their primary internet provider is someone else, other than us. I think that they would need to have their own ASN to advertise their portion of our ip space to their peers.
My question is, should we provide the ASN or should they apply for an ASN?
They should.
What is the minimum block considered routable, is it reasaonable to advertise a /23 on its own ASN?
Many people do /24s. There is no real difference between a /24 and /23 in most people's filters. A /20 may or may not get them more reachability, but as long as you accept their /23 and announce the aggregate CIDR, it should not matter.
Are there any other solutions I haven't thought of?
Yes, but they are all bad. :) -- TTFN, patrick P.S. Wow, two operational posts in one day. What is happening to this list?
Assuming that this is in North America (this is NAnog, afterall), they should probably apply to ARIN for both the /22 (if they can justify that much space) and the ASN, or, get the ASN from ARIN and the space from you. As of policy 2002-3, ARIN will assign /22s to end users that have need of a unique routing policy and meet other tests necessary for such an assignment. These are the same tests you would be required to hold them to for you to assign them a PA /22. Owen --On Wednesday, December 8, 2004 13:59 -0600 Adi Linden <adil@adis.on.ca> wrote:
We currently have two /19 that we advertise on a single ASN. A client would like to obtain /23 or /22 from us. This is not a problem, except that their primary internet provider is someone else, other than us. I think that they would need to have their own ASN to advertise their portion of our ip space to their peers.
My question is, should we provide the ASN or should they apply for an ASN? What is the minimum block considered routable, is it reasaonable to advertise a /23 on its own ASN?
Are there any other solutions I haven't thought of?
Thanks, Adi
-- If this message was not signed with gpg key 0FE2AA3D, it's probably a forgery.
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Adi Linden Sent: Wednesday, December 08, 2004 1:59 PM To: nanog@merit.edu Subject: ASN and Peering Problem
We currently have two /19 that we advertise on a single ASN. A client would like to obtain /23 or /22 from us. This is not a
If I understand, they would like you and the other provider to both announce the IP space, from your respective ASN's. Real-world, this will work, but causes an "inconsistent origin" bgp error. -ejay problem, except
that their primary internet provider is someone else, other than us. I think that they would need to have their own ASN to advertise their portion of our ip space to their peers.
My question is, should we provide the ASN or should they apply for an ASN? What is the minimum block considered routable, is it reasaonable to advertise a /23 on its own ASN?
Are there any other solutions I haven't thought of?
Thanks, Adi
participants (4)
-
Adi Linden -
Ejay Hire -
Owen DeLong -
Patrick W Gilmore