North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Policies: Routing a subset of another ISP's address block
On Wed, Apr 05, 2000 at 05:11:02PM -0400, Daniel L. Golding wrote: > Jesper, > > Do you then suggest the elimination of the ARIN multihomed issuance > policy - which is, BTW, the method most folks use to get PI space these > days? After all, you can't be truly multihomed without PI space in your > scheme of things. This would seriously raise the bar for folks to get PI > space in the first place. You would effectively ban anyone doing BGP > advertisements that doesn't have their own PI space already. This is a > troublesome suggestion. It denies the benefits of multihoming to small > enterprises and ISPs, effectively discriminating against them. Here in europe (RIPE instead of ARIN), you can request PI space, without any guaranties of it being routeable, but it usually is. > I find your line of reasoning, which is essentially "tough cookies" to be > unconvincing. I must also assume that you haven't worked for a small ISP > or CLEC recently, nor have you had such for a customer. Actually I've helped quite a few such customers, my recommendation usually is to get PI space from RIPE, and get both providers to announce it from their ASN, this works quite well, and also save a ASN - if the customer really want to run BGP, we have arrangements with other ISP's here, that we find a private ASN (that none of us use currently), and assign this ASN to the customer, and we then strip the private ASN on the edges of our network. > There must be room for providers of all sizes in the marketplace. If this > thesis enjoyed widespread acceptance by the major Tier I ISPs, I have no > doubt that it would be considered anti-competative. Naturally there is room for everybody, but things still need to work. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.