January 1996 - Test - lists.nanog.org

Re: Policy Statement on Address Space Allocations
by Hank Nussbacher 27 Jan '96

27 Jan '96

On Fri, 26 Jan 1996 14:03:19 -0000 you said: >But still, sorry that it wasn't as smooth as it could >have been if there hadn't been a flaw in the filtering >that crept in in about April, long before anyone was >even really thinking of allocating from 206.0.0.0/8. > >However, as I think everyone remembers, after a short while, >in an effort to assist in getting aggregation of the >then-announced bits of 206.0.0.0/8 working OK and giving >people some time to get used to the filtering, I did relax >the filtering on 206.0.0.0/8 to permit /19s. > >As you note, this was to the benefit of other peoples' customers. > >| the real message is if you have a 206+ address, make sure that your >| provider can put it into an aggregation block for you (or go to sprint). > >Right, and we have been warning our customer base for >some time that if they announce a 206+ address that is >not aggregatable into something reasonably big (like a /18), >they run the risk of losing connectivity to other providers >if they ever were to impose similar filters for business >or technical reasons. Lets take a real world example between Sean's and Daniel's arguments. I am the registry of Last Resort for Israel and I assign CIDR blocks to ISPs here in Israel. I follow the slow start model of RIPE and give initially a /22 and then a /21 and then a /20, etc. One new ISP in Israel wanted more address space and found that Net99 (all ISPs have to connect to an ISP in the USA due to Israeli gov't regulations) would give it a /21 from 206.161.0.0 and later Agis gave it a /19 from 206.249.0.0. So we have now an ISP that circumvented the allocation policies and went to the USA to get cheap, large blocks at possibly an expense of them not being portable and/or not routable even if it is portable in the future. The smaller, new ISPs that don't know even what questions to ask will get stuck more and more by this type of situation. We can't do anything about that. But we do need a better GLOBAL policy for IP address allocation that everyone adheres to (perhaps I am asking for utopia). > Sean. Hank Nussbacher

1 0

Re: Policy Statement on Address Space Allocations
by Hank Nussbacher 27 Jan '96

27 Jan '96

On Fri, 26 Jan 1996 13:59:32 +0000 (GMT) you said: >Just to spend a few minutes thinking about it, what do the phone >companies do ? They are the nearest thing with a large installed base >that the Internet even begins to map onto. There are however some >fundemental differences - primarily the fragmentation of Europe (which >is not the case in the US). > >We have a 2Mb line from London to Amsterdam which costs us very much >the same as a T1 from London to Washington. As I understand it, this >"milk them for all they are worth" pricing of the telcos applies to >cross-border land lines in Europe also. > >All this impacts very severely on the commercial decisions taken as to >the routeing of traffic. I would much rather buy more lines to the US >and let the traffics flow back to Europe then to just buy lines to >Europe. Luckily, commercial concerns are not the only contraints >within which we have to work. What this has to do with RIPE allocation policies is beyond me. Everyone in the European realm suffers from extremely high tariffs. So what? >To wash some dirty laundry here, we as a provider have been trying to >get new address space for our dial up customers from RIPE NCC for almost 6 >months now. We allocate *each* dialup customer *1* IP address from a >block and dynamically route them based on where they log in to the >service (including RSN Amsterdam). The RIPE NCC has >effectively< refused >us space because they believe that we should change the product we >sell and use dynamic IP for dialups. > >We are the largest dialup ISP in Europe. We are not the largest provider >in Europe because we follow the rest of the ISPs like sheep, buying Ciscos >and installing off the shelf terminal servers. We provide a product which >our customers understand gives them *more* for their money. We do something >different, and the customers like it. Tough fact of business life that. You and hundreds of other companies approach RIPE with the same story of how big they are, how large their investors are, how their network is gonna take the world of the Internet by storm, and therefore they deserve a /16 or even a /15. If RIPE followed your logic, there would be no more address space left. Use dynamic IP like the rest of us. We all realize the drain of IP addresses and try our best to maximize the addresses. Why should you be different? >But this is all I have seen you do, therefore, how can I but believe >that this is the case. Every private mail that has been sent to us as >a company involves you acting as God and us as the grovelling peasants >praying for a benidication of address space. I have all these mails >in my various folders, as do you. It all depends on your ego. You could just look at them as an organization assigned the tough role of making sure there are IP addresses available in 1999. You see it as God. A viewpoint based on your world view. >Why not. We are not a communist society are we ? Each individual member >of RIPE have their own unique requirements in a commercial and >academically challenging world. We have a USP (Unique Selling Point) of >giving our paying customers there own IP address (OK - it is not >unique, but close enough). We have built propretary technology that >allows our users to use *any* of our dial in points and get the same >service, with the same IP number etc etc, and as one of our primary USPs >we cannot allow the RIPE NCC to try to change that. IBM has 460 POPs in over 40 countries and uses dynamic IP addresses. I can be in London or NYC or Tel Aviv and still use my SLIP connection to read my mail wherever I am. Why should you have static IP addresses for something others can do the dynamic way and thereby conserve IP address space? >Peter Galbavy peter(a)demon.net Hank Nussbacher Israel

1 0

Re: Policy Statement on Address Space Allocations
by Havard.Eidnes＠runit.sintef.no 27 Jan '96

27 Jan '96

Hi, I see Daniel hasn't answered this one (weekend for some, I guess ;-) > > The point is that we will guarantee that our allocation policy > > will create no more than 1024 allocations per /8 and therefore > > not necessitate by itself more routes than that. Currently our > > allocation sizes are /19 - /16. If you think about it a little > > you will see that it is easy to achieve. > > > > And just in case: Yes the minimum allocation is /19 irrespective > > of the number of hosts covered. Note: allocation != assignment. > > OK, so just to make it clear, if a customer would come to the RIPE > NCC and the customer has just 1 host you would still allocated him > /19 block. Correct? This may be obvious to some familiar to the european networking scene already, but anyway... The RIPE NCC itself does in general not deal directly with end customers, only with local registries. To be allocated address space directly from the RIPE NCC you have to first establish yourself as a local registry, pay the startup fee and contribute to the financing of the running costs of the RIPE NCC. Remember, there is noone else than the organizations running the local registries who are picking up the tab for running the RIPE NCC. The typical local registry is also an ISP. Also note the distinction between allocation and assignment made by Daniel which could be lost on some. In this specific case allocation means "address space allocated for a local registry for subsequent assignment to customers". I've seen people critizising the RIPE NCC for their inflexible policies and the practicing of these policies. One important aspect of the RIPE NCC policies when allocating address space to registries is simplicity and uniformity of policy, because one of the worst things that could happen for the RIPE NCC would be for them to rightfully be accused of giving unfair preferential treatment to some registries (=~ ISPs) over others. The chance of this happening (or the RIPE NCC being accused of it) increases with the fuzziness of policies and the amount of evaluation and judgement the RIPE NCC has to apply to individual cases. I think this is fairly accurate, but since this is not coming from the authoritative source I may have made minor mistakes in formulating the above. Regards, - Havard

2 1

on a lighter note...
by hwb＠upeksa.sdsc.edu 27 Jan '96

27 Jan '96

Regarding the NANOG meeting. I am not endorsing their product (or saying anything against it, for that matter, just neutral), but we do have two Xircom wireless Ethernet access points. There are for short distance (may be 30 meters or so in my experience) communication and do some 1 Mbps with a 2.4GHz spread spectrum radio as some "shared medium." The radio guts sits on a PCMCIA card. that fits nicely into a (laptop) PC, and costs a few hundred dollars (not sure about the exact amount). If there were sufficient interest, we could probably use them at the meeting place, so don't leave home without your PCMCIA card. Though I will only install the access points if people ask for it. Y'know, people who don't always want to depend on cables. By the way, I would also be interested hearing from people having experience with other wireless products.

1 0

RE: Policy Statement on Address Space Allocations
by lodge＠houston.omnes.net 27 Jan '96

27 Jan '96

I've been reading this address allocation ping-pong match for some time, and I'm a bit confused. I'd like to describe a real-world case, and gain some understanding by getting some advice. On one hand, we have registries that won't hand out /18 class C blocks for fear of depleting the remaining address space too quickly. On the other, we have "core" providers refusing to route longer prefixes because their routers are about to melt down. I'm currently trying to get a new ISP for a small country on its feet. It can't get addresses from its upstream provider, because they've not got enough and are trying to get some more themselves. They also want to be multi-homed from day one. They currently offer all sorts of fully redundant data services, and understandably they can't see why they should have a single point of failure in their global Internet access. We can spell BGP, and we'll teach them how to spell it too. How about some concrete advice on The Right Thing to do from you folks? Thanks, Mathew -- | Mathew Lodge: lodge(a)houston.omnes.net |5599 San Felipe, 4th Floor | | Internet Specialist, Omnes -- A |Houston, Texas 77056, USA | | Schlumberger/Cable & Wireless company |Phone: +1 713 513 3237 | | http://www.omnes.net/ |Fax: +1 713 513 3126 |

2 1

Re: Policy Statement on Address Space Allocations
by William Allen Simpson 27 Jan '96

27 Jan '96

I trimmed the CC list even further. And you are forwarned that this is a flame, with combined technical and political content: > From: Peter Galbavy <peter(a)demon.net> > Just to spend a few minutes thinking about it, what do the phone > companies do ? They are the nearest thing with a large installed base > that the Internet even begins to map onto. There are however some > fundemental differences - primarily the fragmentation of Europe (which > is not the case in the US). > It should not surprise you that we've heard this before, and rejected it before. > We have a 2Mb line from London to Amsterdam which costs us very much > the same as a T1 from London to Washington. As I understand it, this > "milk them for all they are worth" pricing of the telcos applies to > cross-border land lines in Europe also. > So, lay your own lines if it is cost effective. Heck, spread spectrum radio comes to mind.... if not microwave towers on the oil rigs in the north sea.... > All this impacts very severely on the commercial decisions taken as to > the routeing of traffic. I would much rather buy more lines to the US > and let the traffics flow back to Europe then to just buy lines to > Europe. > Is this why the US-UK links are soooooo overcrowded? Destroying connectivity for the rest of us? > We allocate *each* dialup customer *1* IP address from a > block and dynamically route them based on where they log in to the > service (including RSN Amsterdam). The RIPE NCC has >effectively< refused > us space because they believe that we should change the product we > sell and use dynamic IP for dialups. > Hell yes! Damn right! Three cheers for RIPE!!! Anyone who still allocates more than 1 address per actual dial-up link should be taken out and shot! We spent rather a lot of volunteer-years getting this to work (PPP). > We provide a product which > our customers understand gives them *more* for their money. We do something > different, and the customers like it. Tough fact of business life that. > Are you sure you told your customers about the alternatives? Like dynamic addressing? Like having connectivity to the entire Internet? This isn't new, this is old hat static addresses! How is it different? What gives _more_ here? I don't see anything worthwhile! > The RIPE NCC believes it can dicate the business model we use, which > has been established for > 3.5 years. This is unlikely to happen. > There is this misconception on your part that you have a _right_ to succeed in business, at the expense of the rest of us. > Please read the policies again. You policy uses words like "strongly > discouraged" for static IP allocation, not "disallowed". You have > attempted to strongly discourage us, we have not been so discouraged, > and now give up and give us the address space we are *entitled* to. > You have another misconception that there is an _entitlement_ to Internet access, at the expense of the rest of us. > > What we do *not* do is consider *individual* interests of some over > > the ones of others. If we would do that we would eliminate our > > "raison d'etre". > > Why not. We are not a communist society are we ? I dunno about _your_ society, but the Internet Community requires cooperation. Call it communistic or socialistic as you like. The net won't work without it. Your "priveleges" end when you affect someone else. And you are affecting me, buddy, and I don't like it one bit! Perhaps you should go build your own internet, like MicroSoft.... Again, I applaud RIPE!!! Bill.Simpson(a)um.cc.umich.edu Key fingerprint = 2E 07 23 03 C5 62 70 D3 59 B1 4F 5E 1D C2 C1 A2

2 1

Re: Creative routing (was Re: Policy Statement ...)
by Sean Doran 27 Jan '96

27 Jan '96

Well, there's an alternate tactic for a tiny tiny company. MCI Sprint | / The Site-----BBN / \ Alternet ANS 1/ Pick a provider from whom to acquire a tiny amount of aggregatable address space. 2/ Choose a community attribute which you tag on your prefixes. The easiest would probably be "no-export". The ideal would be one meaning "export only to my set of providers". 3/ router bgp X neighbor ProviderX route-map set-community out neighbor ProviderX send-community neighbor ProviderX filter-list 1 out ... ip as-path access-list 1 permit ^$ ip as-path access-list 1 deny .* route-map set-community permit 10 set community <value> 4/ each provider, at each interchange router bgp Y neighbor PeerA route-map policy out neighbor PeerA send-community neighbor PeerB route-map policy out neighbor PeerB send-community ... neighbor AnotherPeer route-map other-policy out ... route-map policy permit X match community <value> set community no-export ... route-map other-policy deny X match community <value> 5/ on ONLY the provider supplying addresses, configure at (or very near) *each* interchange point this: ip route CIDR-SUPERBLOCK MASK null0 router bgp M network CIDR-SUPERBLOCK mask MASK It's important that the route for CIDR-SUPERBLOCK never fully vanish, or you lose connectivity to your non-providers. Hence the provider you choose address-space from should have a good record of knowing what it's doing and always having at least one path by which to announce the CIDR-SUPERBLOCK to the world. That's about the only big qualification. There. Now you have fully redundant connectivity among all your providers. Your address space is aggregated everywhere except in your set of providers. Each of your providers will carry at least two prefixes: the CIDR superblock and the much longer end-site prefix. Each provider advertises reachability for your prefix to each of your other providers; however, the rest of the world sees only the CIDR-SUPERBLOCK. If a packet hits the router announcing the superblock and that router has no route to the long prefix, it probably will be hearing the more-specific announcements from at least one of your other peers, and will hand traffic to them. You can even play games with AS-path lengths on the more-specific prefix in order to select which provider will handle the bulk of traffic from the set of people at interexchange points who are not your providers and therefore not receiving the most-specific prefix. And all sorts of other nifty hacks. I bet it's even fairly easy for most providers to attach a cost on all the activities needed to support this, so you could end up proving Yakov's thoughts about the Push operation. It won't be cheap. This is very-brain-and-slightly-CPU-intensive. Dear small company needing a /28 and comparing itself to Netscape: please forward my standard consulting fee (a pound of good European chocolate) to my office address when you have a moment. Sean.

1 0

Re: Policy Statement on Address Space Allocations
by jnc＠ginger.lcs.mit.edu 27 Jan '96

27 Jan '96

<I'm mostly sitting this one out, guys and gals... Been there, done that, have *all* the T-shirts, way too many times... I know I should really just ignore Tim, sending him replies just keeps him going, but this one was too food to pass up. For now I'll be totally civil, and let Sean handle the ridicule and abuse approach... :-> From: Tim Bass (from cais.com) <cais(a)dune.silkroad.com> There are at least five hierarchical routing architectures that are not CIDR based To start with, CIDR is not a "routing architecture", it's an addressing scheme; routing architectures are pretty much orthagonal. I.e. you could run a hierarchical link-state system sort of like OSPF in the Internet with the exact same addressing as we have today (of course, you'd have to add more levels of areas to the protocol, etc). So, assuming you meant "five hierachical addressing schemes", could you enumerate them for the rest of us? I can think of only one addressing scheme which is really significantly different from CIDR (Landmark doesn't count, it's basically CIDR with diffuse boundaries), and that's Geographic. What is hard to understand is why men and women with intelligent brains believe that there is only 'one way, one religion' to do hierarchical routing. You need to distinguish between routing, and the addresing structure it uses. There are numerous ways to do the routing (i.e. the calculation of paths and/or routing table entries, such as destination-vector, link-state, etc), but there seems to be only one way to make the addressing work for very large networks, and that is to use the approach in CIDR. I am quite sure that the most vocal advocates of CIDR have read very little historical documents outside of the IETF RFCs. Oh, really? I guess I don't count as a very vocal advocate of CIDR... and I guess the same goes for Tony and Yakov. Hi guys! :-) I highly recommend some time spent in review of the principals of hierarchical routing; graph theory; queuing systems; dynamic programming and others as well as the marginalia of journal articles on the subject. Queueing systems aren't much use for this aspect of routing. Noel

1 0

Re: Policy Statement on Address Space Allocations
by Vadim Antonov 27 Jan '96

27 Jan '96

>Then, some of you will ask how to enforce this. Once every so often, you >dump the BGP routing tables from strategic routers. If you see any >non-matching prefixes, you send an email to the network coordinator for >the allocated block giving them a set amount of time to clean it up. Any >routes which are not cleaned up by the deadline are added to a filter >list which could be carried on routers. Sorry, *who* gets to play the net politzai? Registries have no control over service providers, and service providers have insufficient human resources to do that (and most won't do that anyway). Note that updating exterior policy filters by a large ISP involves carefully planned and timed update on some dozen-odd routers, so it is not done often, and certainly won't be done just to punish some clueless luser. We'll be back shortly after the expected RA advertisement break... --vadim Not speaking for Sprint.

5 4

Re: Policy Statement on Address Space Allocations
by Vadim Antonov 27 Jan '96

27 Jan '96

Peter had other ideas about net politzai candidacies :) --vadim Sorry, *who* gets to play the net politzai? Well, I think someone who has considerable experience with a totalitarian regime and a secret police state would be appropriate, wouldn't you, Vadim? ;-) Tony

2 1