On Fri, Jul 17, 1998 at 01:56:06PM +1200, Simon Blake wrote:
Hey team, sorry for the delay getting back.
How does this sound for an initial allocation of numbers for Citylink, on the ex DCC network:
202.7.0.1-15 Citylink Admin 202.7.0.16-31 Reserved 202.7.0.32-47 Netlink 202.7.0.48-63 Reserved 202.7.0.64-79 Actrix 202.7.0.80-95 Reserved 202.7.0.96-111 Clear 202.7.0.112-127 Reserved 202.7.0.128-143 Iconz 202.7.0.144-159 Reserved 202.7.0.160-175 Saturn 202.7.0.176-191 Reserved 202.7.0.192-207 Paradise 202.7.0.208-223 Reserved 202.7.0.224-239 Non ISP users 202.7.0.240-254 Reserved
Mask in use will still be 255.255.255.0, so you can use every number in each range. Each ISP has a range reserved for further expansion, although some will get used for other ISP's should they join.
Just to confirm, these are to be used for peering between ISPs only? Or are these to be used for numbering customers' routers as well? If the former, then these look like good-sized blocks. If the latter, they look a bit small :)
I've almost got the DNS servers going for the in-addr.arpa delegation (ie, the servers are going, I just haven't talked to Rex / APNIC / INTERNIC about changing the servers), in the interim please let me know what numbers you allocate.
Incidentally, the original block suggested by Rex was a /23, wasn't it?
In the more modern RIPE db notation, that's
202.7.0.0 - 202.7.1.255
That gives plenty of room for growth without impinging on those "reserved"
bits. Also if everybody uses 255.255.254.0 as a subnet mask from the word
go, it might save some hassle/confusion in the future?
Joe
--
Joe Abley