Re: IPv4 and ASN Policy draft on-line
If I go the Oregon router server and look up their /19 and find only 1 path to that /19 or I find that the ASN origin has disappeared and been replaced by their upstream then there is no justification for getting an ASN.
randy
Hank
Wrong. there are valid cases where a (globally unique) AS# is required which does not show up in the DFZ. (and, of course, there are places where a private AS# would do just as well). The bottom line is: how much are we (collectively) prepared to pay (in real money for RIR staff salaries, complexity, hassle and delay for *all* requests) in order to save a couple of AS numbers... -WW _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber@CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hi, On Tue, Sep 25, 2001 at 12:58:44PM +0200, Wilfried Woeber, UniVie/ACOnet wrote:
Wrong. there are valid cases where a (globally unique) AS# is required which does not show up in the DFZ. (and, of course, there are places where a private AS# would do just as well).
Hmmm. I'm curious: could you name a few? The things that I could imagine are "private peerings somewhere", which "should" work using private AS#s just fine.
The bottom line is: how much are we (collectively) prepared to pay (in real money for RIR staff salaries, complexity, hassle and delay for *all* requests) in order to save a couple of AS numbers...
Or to phrase it differently: will it be more expensive than to upgrade all routers world-wide to be able to handle 32bit AS#s? While there *is* the option to never reclaim AS#s and just go to 32bits, I, for one, do not really want to handle 32-bit-long AS#s in daily operation, and do not really want to see all the new and exciting bugs that they would bring with them... Gert Doering -- NetMaster -- SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
there are valid cases where a (globally unique) AS# is required which does not show up in the DFZ. (and, of course, there are places where a private AS# would do just as well). Hmmm. I'm curious: could you name a few? The things that I could imagine are "private peerings somewhere", which "should" work using private AS#s just fine.
private peering, in the sense i to which i am used, folk who use a p2p circuit as opposed to an l2 mesh, have the exact same routing needs as folk who peer publicly. randy
At 12:58 25/09/01 +0200, Wilfried Woeber, UniVie/ACOnet wrote:
If I go the Oregon router server and look up their /19 and find only 1 path to that /19 or I find that the ASN origin has disappeared and been replaced by their upstream then there is no justification for getting an ASN.
randy
Hank
Wrong. there are valid cases where a (globally unique) AS# is required which does not show up in the DFZ. (and, of course, there are places where a private AS# would do just as well).
The bottom line is: how much are we (collectively) prepared to pay (in real money for RIR staff salaries, complexity, hassle and delay for *all* requests) in order to save a couple of AS numbers...
Based on my estimates, 15-20% fall into the now defunct or now single homed category. Totally not insignificant. -Hank
-WW _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber@CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
there are valid cases where a (globally unique) AS# is required which does not show up in the DFZ.
please illustrate randy
participants (4)
-
Gert Doering -
Hank Nussbacher -
Randy Bush -
Wilfried Woeber, UniVie/ACOnet