On Fri, 3 Jul 1998, Simon Blake wrote:

Seriously, anybody have a good feeling for how Citylink should administer these numbers? My first thought was to hand them out in blocks of 16 to the ISP's, who can then use them to number their clients routers, and notify us of additions so that we can update forward and reverse DNS records. Alternatively, we could hand them out /32 at a time as we do new connections (and back fill for existing connections, obviously). Preferences?

Handing out blocks of 16 to ISPs would probably ease the workload on you CityLink people, and would let ISPs connect people quickly without having to wait for addresses to be allocated. I would suggest that all the addresses in a block of 16 should be accounted for for CityLink's records before any more blocks are allocated - this will let you keep the DNS up-to-date. Speaking of the DNS, are CityLink going to be running their own nameserver? Or do you intend to handle the DNS through an ISP? Joe -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

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. 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. Cheers Si On Fri, 3 Jul 1998, Simon Blake wrote:

On Wed, 1 Jul 1998, Joe Abley wrote:

...

On Wed, 1 Jul 1998, Rex Croft, 07 838 4597 wrote:

...

Looking through my "IP to delete" mail folder I found:

Dunedin City Council 202.7.0.0 - 202.7.1.0

This was returned to us years ago.

Please feel free to use this address space for WIX.

Rex, you are a truely marvelous person. All not in favour, keep quiet :)

I want to know how many other /24's Rex has stashed away at home - enough to start RexNIC? :-)

Seriously, anybody have a good feeling for how Citylink should administer these numbers? My first thought was to hand them out in blocks of 16 to the ISP's, who can then use them to number their clients routers, and notify us of additions so that we can update forward and reverse DNS records. Alternatively, we could hand them out /32 at a time as we do new connections (and back fill for existing connections, obviously). Preferences?

Cheers Si

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

Hey all On Fri, 17 Jul 1998, Joe Abley wrote:

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?

Customers as well - the aim is to get one IP range that contains the bulk of the connections to Citylink.

If the former, then these look like good-sized blocks. If the latter, they look a bit small :)

Indeed, but they're not actually subnets, if one ISP doesn't use all it's numbers Citylink can assign some of them to another.

...

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

Urrgh, my mistake, you're quite correct. I'll do another allocation shortly.

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?

The reservation was for each ISP to grow into, they weren't being reserved for any other purpose. A /23 makes me much happier - with the speed with which Citylink is growing, 253 connections isn't that far away... Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

On Fri, Jul 17, 1998 at 03:15:27PM +1200, Simon Blake wrote:

Righto, second effort

202.7.0.0-202.7.1.255 is the range

202.7.0.0 is the network number 202.7.1.255 is the broadcast address 255.255.254.0 is the network mask

[snip!]

202.7.0.192-207 Clear 202.7.0.208-255 Reserved

I would like the following assigned for CLEAR's IP backbone deployment in Wellington, ready for our production WIX access being fully functional (which should happen early next week, depending on how much sleep Richard feels like getting ;) -- 202.7.0.192 ba1-atm1-0-2.lmtn.clix.net.nz 202.7.0.193 ba2-atm1-0-2.lmtn.clix.net.nz (*) 202.7.0.194 gos1.lmtn.clix.net.nz (*) planned but not currently live. Note the records shown above are not currently active in our nameservers (but will be early next week assuming all this is ok with the CNH people). I would prefer the relevant PTR records in the 0.7.202.in-addr.arpa zone to refer to the clix.net.nz names above, but am happy to comply with whatever structure develops, e.g. 192.0.7.202.in-addr.arpa. IN PTR clix1.wix.net.nz. 193.0.7.202.in-addr.arpa. IN PTR clix2.wix.net.nz. 194.0.7.202.in-addr.arpa. IN PTR clix3.wix.net.nz. We have had our WIX-facing interfaces configured in NetLink's interim 203.97.132.192/28 block, but as our WIX access wasn't live last week there seems little point in using them now that we have a new range to play with (thanks Andy - you can have those addresses back now :) CALL FOR BGP PEERS! Would anybody interested in network peering with CLIX across WIX please drop me a note? Pre-requisites at this stage are: 1. An interface on WIX numbered within the new 202.7.0.0/23 block 2. A router which speaks BGP v4 3. A globally unique autonomous system number 4. A list of the route objects to be advertised to CLIX 5. Problem escalation contact details, 24/7 if available CLIX operates BGP route filtering with all BGP peers to protect the network from finger trouble. We will be looking in the future at building route filters directly from policy obtained from one of the public routing registries, but I expect these filter lists to be hand-edited to start with. We will be applying route dampening penalties against flapping BGP advertisements, and do not intend to accept advertisements with a wider prefix than 24 bits. We will not provide transit to any other autonomous systems (domestic or international) unless an appropriate customer relationship exists with CLEAR. Note! These requirements are NOT being proposed as a multilateral peering policy across WIX - far from it, these are requirements for peering with CLEAR only. Other providers and network operators will have their own arrangements. -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/

On Wed, 1 Jul 1998, Richard Naylor wrote:

...

Please feel free to use this address space for WIX.

excellent fellow - the hidden joys that lurk in old email files :-)

Please consider the range acquired and I'll be in touch asap with the routes etc.....

What do you mean by "routes"? Surely the only route we need is for all participating ISPs to keep a /23 for that block in their interior protocols, and to be careful about advertising it to anybody else? Or have I got the wrong end of the stick again? Groan... Everything to do with Wellington is _sooo_ confusing to this particular poor naive Aucklander :) Joe -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog