Re: Policy Statement on Address Space Allocations
Original message <4D07037D30@hq.mainet.com> From: "Vincent J. Bono" <VBONO@hq.mai.net> Date: Jan 26, 20:57 Subject: Re: Policy Statement on Address Space Allocations
...
How about trying to prevent the static assignment of addresses to dial-in customers? This chews IP space like there was no tomorrow...
-- End of excerpt from "Vincent J. Bono"
Actually, I suspect that's one of the MOST efficient uses of addresses. We fill a handful of class C equivalents with our static-IP single-address dialup customers, but those are filled to capacity and used daily, whereas most of our small-business customers have an entire class C equivalent each, and only have a dozen hosts, if that, on their LAN so far. I feel much better about using 254/256 addresses serving 254 customers than I do about using 12/256 addresses serving 1 customer. As for the whole routing issue, I'm VERY sad to see so many people in support of address assignment and routing policy that effectively locks out smaller providers. Were we starting today, rather than back in 1993, we'd be stuck with our original provider, or face renumbering if we wanted to switch to a higher-performance provider AND connect to MAE-West, as we've done. If word gets out that going with a small provider == having to renumber your corporate hosts regularly, big providers will have effectively locked small players out of the market... which helps their pocketbooks at the expense of a lot of other people. At this rate we're going to see the policy change to "each RBOC gets a /7 out of the old class A space, and then that's it" -matthew kaufman matthew@scruz.net
On Fri, 26 Jan 1996, Matthew Kaufman wrote:
We fill a handful of class C equivalents with our static-IP single-address dialup customers, but those are filled to capacity and used daily, whereas most of our small-business customers have an entire class C equivalent each, and only have a dozen hosts, if that, on their LAN so far.
Any particular reason why you don't assign them a /26 or such? -dorian
I can't speak for Matthew, but many smallish ISPs have legacy /24 allocations from using Livingston Portmasters and IRXes before they could do CIDR (I *think* they solved that problem, but I don't know for sure). -george
On Fri, 26 Jan 1996, George Herbert wrote:
I can't speak for Matthew, but many smallish ISPs have legacy /24 allocations from using Livingston Portmasters and IRXes before they could do CIDR (I *think* they solved that problem, but I don't know for sure).
If that's the case, it's understandable. We had devil of a time trying to get longer than /24s to work with cheap equipment some high schools bought to do their internal networks. Legacy equipment not being able to do that is something you can't do anything about, but it's time vendors learned what CIDR is... -dorian ______________________________________________________________________________ Dorian Kim Email: dorian@cic.net 2901 Hubbard Drive Network Engineer Phone: (313)998-6976 Ann Arbor MI 48105 CICNet Network Systems Fax: (313)998-6105 http://www.cic.net/~dorian
] Legacy equipment not being able to do that is something you can't do ] anything about, but it's time vendors learned what CIDR is... Noone in the world complained that Windows 95 couldn't read apple IIe diskettes. Why should they complain when their antiquated equipment doesn't work in the big I? -alan
The Livingston products are not antiquated; they are in fact very up to date and selling like hotcakes, though they are annoyingly flawed from a CIDR viewpoint. In particular, the IRX router is about half the price of a Cisco 2500 most of the time, and the Portmaster dialup servers are worlds more attractive than any non-rackmount integrated alternatives, under $100 a port. It would be fair to say that Livingston has been a reasonably large part of the success of small and midsized ISPs recently. All the more important for them to get into CIDRizing their software, but... -george
On Sat, 27 Jan 1996, Alan Hannan wrote:
] Legacy equipment not being able to do that is something you can't do ] anything about, but it's time vendors learned what CIDR is...
Noone in the world complained that Windows 95 couldn't read apple IIe diskettes.
Why should they complain when their antiquated equipment doesn't work in the big I?
Because the Big I is supposed to be standards based, unlike Apples, oranges, and windows, and we evolve our standards, we should be making provisions for legacy equipments. Current equipment that do not work, however, have no excuses. -dorian
I can't speak for Matthew, but many smallish ISPs have legacy /24 allocations from using Livingston Portmasters and IRXes before they could do CIDR (I *think* they solved that problem, but I don't know for sure).
-george
I think the problem was with variable-sized subnets within a /24, not with subnetting at all, but I could be wrong. Avi
On Sat, 27 Jan 1996, Avi Freedman wrote:
I can't speak for Matthew, but many smallish ISPs have legacy /24 allocations from using Livingston Portmasters and IRXes before they could do CIDR (I *think* they solved that problem, but I don't know for sure).
I think the problem was with variable-sized subnets within a /24, not with subnetting at all, but I could be wrong.
</lurk> The problem with Livingstons is not that you cannot subnet, but that you cannot variably subnet as noted by Avi above. <lurk> rus (who runs nothing but Livingston and wishes he could do variable length subnetting) Russ Pagenkopf (406) 542-0838 Internet Services Montana (ism.net) Hardware and Business Manager Connecting the World to Montana All questions can be answered thus. NO. YES. MAYBE. EH?
I can't speak for Matthew, but many smallish ISPs have legacy /24 allocations from using Livingston Portmasters and IRXes before they could do CIDR (I *think* they solved that problem, but I don't know for sure).
-george
I think the problem was with variable-sized subnets within a /24, not with subnetting at all, but I could be wrong.
Please review RFC 1879 for the particulars on certain existing equipment providers and their abilities to support near-term addresing proposals. -- --bill
As I understand it, the primary issue with big-backbone-ISPs getting big chunks and startup ISPs not getting seperate chunks is that the small ISPs often grow big and want to do things like multihome. I know that's what has happened with scruz.net, where Matthew's speaking from, and several other ISPs I know of. As I understand it, people are generally reluctant to break up a large CIDR block to let some of it leave because it introduces at least 2 new routes globally... you end up with 3 routes, the block above the missing chunk, the block below the missing chunk, and the missing chunk from the new backbone provider. This is considered bad. It is not, however, completely necessary. Consider this as an option. Small ISPs signing up with their backbones agree to a form of semi-portability of addresses. The small ISP agrees that they will for (n years) maintain a direct IP link into backbone's network which can be used for getting packets to the block allocated from backbone's big CIDR blocks. This can be of arbitrarily slow speed if need be, or contractually obligated to be a 56k or greater, or T1 or whatever. Implimentation detail. In exchange, backbone agrees to artificially inflate the reachability cost in BGP advertisements to the large block and to allow small ISP to have any other backbone advertise the specific block at an easier to reach priority level. This allows the small ISP to dual home, or switch primary home, and sort of take their address with them (in that the new backbone can advertise the sub-block more attractively, thus making traffic most likely to flow that way). It also allows the origional backbone to not break up its block in its own announcements, and thus minimizes the number of total announcements made globally to no more than 2... one for the origional block, and a higher priority one for the sub-block which migrated. This would be no more advertisements than the case in which small ISP got its own space to start with and got it routed, and is actually easier on small ISP at the beginning. ISPs which have gone dual homed, connected to interchange points, etc. are likely to be able to justify /18 and up allocations directly from the NIC, and can slowly phase out their legacy blocks at that time. They can at their option renumber their internal hosts into their "own" space at that time, or not. They can let customers keep the origional space they were allocated, as routing for it is guaranteed one way or another. Or they can give customers the option to renumber into space the now midsized ISP has better, more direct control over. To avoid excessive headache, backbones should probably ONLY offer this sort of deal to bona-fide ISPs (of any size), not end-user customers. Comments? -george william herbert gherbert@crl.com
participants (7)
-
Alan Hannan
-
Avi Freedman
-
bmanning@ISI.EDU
-
Dorian Kim
-
George Herbert
-
matthew@scruz.net
-
Russ Pagenkopf