- NZNOG - lists.nznog.org

Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion)
by Scott Weeks 29 Nov '06

29 Nov '06

--- richardn(a)cs.waikato.ac.nz wrote:---------------------- From: Richard Nelson <richardn(a)cs.waikato.ac.nz> While not wanting to spoil a good discussion with facts, there is a presentation on Comcast's plans for IPv6 from a recent NANOG here: http://www.nanog.org/mtg-0606/durand.html The summary is 20 million customers * 2.5 set-tops/customer * 2 IPs/box = 100million IPs. The network design requires unique IPs. The ran out of 10net in 2005 and have got a large part of 73net from ARIN. Their long term solution (new services = more IPs/customer) is IPv6. ----------------------------------------------------------- This was discussed earlier in the recent flurry of email on the subject. Also, this is why I was asking about VPRNs. However, I missed the part on why STBs need unique IPs or why they need 2 per box. scott

3 2

Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion)
by Scott Weeks 29 Nov '06

29 Nov '06

--- aj(a)sneep.net wrote: From: Alastair Johnson <aj(a)sneep.net> Scott Weeks wrote: : Finally, with VPRNs addresses could be reused. Just put : the customers in different VPRNs and duplicate the address : scheme. It's 'divide and conquer' methodology. I'm a : noobie to VPRNs, so flame me if this isn't feasible. I have : doused my flameproof underpants with beer, so I'm protected... :-) :: Oh yes. This is a valid methodology. Also, you don't :: really need every subscriber to be uniquely addressed across :: your entire network - to the closest PoP site or Super-PoP site :: is sufficient, depending on your topology. :: :: Of course, from your Ethernet switch/DSLAM/FTTx node/whatever, :: you know where and who the subscriber is, so you're not reliant :: on IP addressing to authorize content access, either.... Thanks for the answer. So, it seems that all customer's STBs could be put in as many VPRNs as necessary to divide them into groups such that RFC1918 space is never exhausted and each customer could get one (or as many as they request) IP address that's publically routable for their internet connectivity. Thus, if the Very Giant ISPs designed their network in this manner, IPv4 would take them as far as they need. Yes? scott

3 2

Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion)
by Scott Weeks 29 Nov '06

29 Nov '06

--- gerard(a)face.co.nz wrote: From: Gerard Creamer <gerard(a)face.co.nz> On 30/11/2006 7:41 a.m., Scott Weeks wrote: > Thanks for the answer. So, it seems that all customer's STBs could be put in as many VPRNs as necessary to divide them into groups such that RFC1918 space is never exhausted and each customer could get one (or as many as they request) IP address that's publically routable for their internet connectivity. Excuse my ignorance, but I'm having trouble finding useful information on what a VPRN (Virtual Private Remote Network) is - I could guess, based on my understanding of VPNs and NAT (as it appears to be used as a NAT replacement in context??), but that might be dangerous - any pointers to useful resources would be appreciated. ---------------------------------------------- My apologies, it stands for Virtual Private Routed Network. It's also known by many other names: RFC2547bis, IP Based Virtual Private Network; BGP/MPLS VPNs, Layer 3 VPNs, etc. Here's a link that looks good, though I haven't read it yet: www.spirentcom.com/documents/760.pdf scott

1 0

VPRN
by Gerard Creamer 29 Nov '06

29 Nov '06

On 30/11/2006 7:41 a.m., Scott Weeks wrote: > Thanks for the answer. So, it seems that all customer's STBs could be > put in as many VPRNs as necessary to divide them into groups such that > RFC1918 space is never exhausted and each customer could get one (or > as many as they request) IP address that's publically routable for > their internet connectivity. Excuse my ignorance again, but I'm having trouble finding useful information on what a VPRN (Virtual Private Remote Network) is - I could guess, based on my understanding of VPNs and NAT (as it appears to be used as a NAT replacement in context??), but that might be dangerous - any pointers to useful resources would be appreciated. Thanks, Gerard

1 0

Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion)
by chris＠chrishellberg.com 29 Nov '06

29 Nov '06

My mail app doesn't do quoting sorry :( Peter, Agree, it's not black and white and you raise many pertinent questions. But one of the governing factors should be that a shortage of addresses[1] shouldn't restrict my network design. Not saying that you need to be wasteful. Just that NAT or some proxy equivalent shouldn't be the the solution to the address squeeze[1]. /Chris [1] maybe there is an address shortage, maybe there isn't..not terribly important for this point. ----- Original Message ---- From: Peter Youngquest <peter(a)mynetworks.co.nz> To: NZNOG <nznog(a)list.waikato.ac.nz> Sent: Wednesday, November 29, 2006 8:50:35 PM Subject: Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion) As much as I find this topic boring :-) I doubt the answer is as black and white as some would like. Exposing the evolving subscriber premise to the "world" as such may reduce some problems but obviously increases others. I think it is fair to say alot of this is a balancing game. If you expose the subscriber premise to the service core (CSCF sort of area) you increase loading at the service core. This is not a good thing considering the stability of these pieces of the network at this stage. No vendor rants to that statement pls. IMS/SIP gateways are being developed that reduce Service Core loading but still how much of the home is exposed and how much isn't. Also there are a number of initiatives working currently to further define the home, how the CPE will interact with upstream - each other, QoS on the home segment etc etc If the subscriber premise is exposed to network and as Dave pointed out earlier there are a number of less than trivial considerations. Address management, device management, Security,introducing new devices to the home (another Dick Smith VoIP phone), point of demarcation etc etc. Also is there a need to expose all the devices globally. STBs would only need visibility to the service providers, VoIP phones to the SBC/SBG, fridge to the mail server :-D Also there are the various styles of network connectivity: - single pipe, MUX UNI that will have impact on the addressing schemes. To state that having "20million subs and requiring v6 for management" as a poster child for v6 is not a good look. There are other ways of approaching this - distribution and hierarchy to me sounds feasible. Last time I looked the sky is above us. What is happening is we are moving into an interesting time where the evolution of the subscriber premise will very much determine how the networks will look. Rgds Peter

3 2

Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion)
by chris＠chrishellberg.com 29 Nov '06

29 Nov '06

I quite like the idea of being able to give every device behind a CPE a globally routable address. If there is a way to avoid NAT in the first place (also 1918 if that's how you're forced to do CPE management), v6 seems like an obvious alternative. Unless I'm mistaken that the RIR would happily allocate enough addresses for a /29 per household? The content is what drives the business decisions, so if the problem of accessing V4 content were magic-ed away, I'm not seeing why the bashing on V6. Should I come to more nznogs for the answer? /Chris ----- Original Message ---- From: Alastair Johnson <aj(a)sneep.net> To: nznog(a)list.waikato.ac.nz Sent: Wednesday, November 29, 2006 1:50:24 PM Subject: Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion) Philip D'Ath wrote: > I don't know how more obvious it can be made. > > It's solving the looming problem of the IPv4 address pool being > exhausted in the next 3 to 6 years. > > Is not complete lack of Internet connectivity for new customers not a > good enough reason? I think the subject line says it all, on that particular topic. V6 seems to largely be a problem looking for a solution at this point in time. Need to support 25 million CPE devices? There are ways to do that, and many vendors are falling over themselves to help you. STBs? No problem. Triple/quad/quinta-plays? Got it covered. While I don't doubt that IPv6 will eventually become the widespread protocol, do you REALLY see that happening before 2020-ish? At which point the carriers will be able to make a premium selling v4 service, because by gosh there will be a lot of legacy networks out there needing it. But that's a completely separate topic. aj. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Posting and quoting
by Ian Batterbee 29 Nov '06

29 Nov '06

Hi everyone, It would be greatly appreciated if everyone posting would make the effort to remove any unnecessary quoted text from their reply before hitting send, as it is quite hard to spot the bits that are new when reading the list in digest form, with the same paragraphs repeating again and again at the end of postings. I realise some people are already doing this. Feel free to flame me for making a such a request, but address such flames to /dev/null Thanks

1 0

Re: [nznog] IPv4 Exhaustion
by Scott Weeks 28 Nov '06

28 Nov '06

--- andrew(a)etc.gen.nz wrote: : There are some DSL providers in some Asian countries : who are very interested in IPv6 because they've almost : exhausted 10/8 and weren't able to receive a public /8.[1] I can't imagine any Asian country's ISP that has used 16777216 IPs. Even so, they could still have 1114112 more IPs by using 192.168/16 and 172.16/12. Do you have a pointer to which provider this is? scott --- andrew(a)etc.gen.nz wrote: From: Andrew Ruthven <andrew(a)etc.gen.nz> To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] IPv4 Exhaustion Date: Wed, 29 Nov 2006 09:17:18 +1300 On Wed, 2006-11-29 at 08:12 +1300, Robert Gray wrote: > Philip D'Ath wrote: > > > I think the board of directors will flip, and tell you to find a > > solution, as not growing the business will not be considered an option. There are some DSL providers in some Asian countries who are very interested in IPv6 because they've almost exhausted 10/8 and weren't able to receive a public /8.[1] > I'd check that the board were happy that your customers won't be able to > host web sites or email servers that can be seen in v4 space or even run > p2p apps with v4 customers. > > When I looked at v6 some 10 years ago (I bought a book) it seemed to me > that the world all had to change together and that's not a cutover I can > see working too well. There is an education network in Catalonia that is IPv6 only[2]. They are using proxies to allow access to the traditional IPv4 Internet for specific applications. So there is no need for the entire world to cutover at once. And as Philip says, dual-stack is probably the method that a lot of companies that are transitioning will use. Cheers! [1] This was in March in this year, so they've probably exhausted it by now. [2] http://www.iepg.org/november2004/deploying_5000_ipv6_sites.pdf - This slideshow is from 2004, but Jordi was saying during March that they had rolled out the network. I haven't been able to find anything to back this up... -- Andrew Ruthven, Wellington, New Zealand At home: andrew(a)etc.gen.nz | This space intentionally | left blank. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion)
by Scott Weeks 28 Nov '06

28 Nov '06

Thanks Joe, I must've misunderstood other mailing list's discussions. I thought small-fry ISPs were forced to have only one upstream and only the biggies were able to have more than one. I mean to multi-home to many different providers and an IX or two just like I do today, BTW. Thanks for setting me on the right thought-path and apologies to the list for any confusion. scott --- jabley(a)ca.afilias.info wrote: From: Joe Abley <jabley(a)ca.afilias.info> To: surfer(a)mauigateway.com Cc: <nznog(a)list.waikato.ac.nz> Subject: Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion) Date: Tue, 28 Nov 2006 19:10:53 -0500 Scott! On 28-Nov-2006, at 18:07, Scott Weeks wrote: > : The past 10+ years of work on IPv6 nee IPng have taught > : many lessons about what will and will not work (and more > : importantly what will be accepted or not). > > Exactly. I NEED to multihome. I won't accept not being able to do > that. No provider is going to be good enough that I trust ALL of > my connectivity with them and no one else. That settles it right > there. A protocol should not dictate my business practice. You can multi-home in v6 in precisely the same way as you do in v4 if you're an ISP, under all RIR policies. This also goes for anybody who qualified for v4 PI assignments in the ARIN region (so, end users too, at least those who qualify for sufficient addresses to want to multi-home with PI v4 space). Other regions will presumably follow suit if their respective memberships want that to happen. The ability to multi-home using PA v6 space (as is commonly done in the v4 network) depends on deployed filtering practice. Currently, it doesn't work very well; however, if there was pressure from an actual customer base, it could well be that it would work more often. Neither of these require any additional protocol development or implementation effort, and both ought to be very familiar to anybody who is multi-homed using v4. Nothing until this sentence has had anything to do with shim6, for example. There are lots of arguments for why v6 won't/shouldn't/can't succeed as a replacement for v4, but multi-homing is barely one of them. Joe

1 0

Re: [nznog] IPv4 Exhaustion
by Scott Weeks 28 Nov '06

28 Nov '06

--- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> : : 17 million addresses is simply not enough for a country the size of the : US (and many others). They already have 100 million set top box's : deployed. :-) RFC1918 space is used within a network only. Not across networks. So, one network's IPTV customer can have the same STB IP address as another's when the RCF1918 space is used. You stream from your head-end to your customers only, so there's no need for public IP addressing. The traffic stays within a particular network. That is, unless you're talking about broadcasting on the internet to any STB in the world, or something like that. : Sorry, didn't realise you intended the email to be private. It seemed : of a nature that would interest other people in this thread. It's ok. I was unsure if everyone wanted to hear my non-beer-goggled responses. Responses are so much more interesting when typed while one's beer-goggled... ;-) scott -----Original Message----- From: Scott Weeks [mailto:surfer(a)mauigateway.com] : The release of IP based set top box's and : the like is going to make the problem worse. :: Do you mean for IPTV? I use 1918 space for them and :: a public IP for the DSL router. I haven't used extra :: IPs for triple play stuff. --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> : : Think 20 years down the track. : : Mobile phones and IP set top boxes are likely to : EXCEED the size of the RFC1918 address space. : There simply wont be enough of it. Well, I guess I don't mind a private email going public... There're about 17891328 RFC1918 IPs. Let's say you're going to use 7891328 IPs for internal addressing issues. That still leaves 10 million STB IP addresses for your network. scott --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> To: surfer(a)mauigateway.com Cc: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] IPv4 Exhaustion Date: Wed, 29 Nov 2006 07:47:59 +1300 Think 20 years down the track. Mobile phones and IP set top boxes are likely to EXCEED the size of the RFC1918 address space. There simply wont be enough of it. -----Original Message----- From: Scott Weeks [mailto:surfer(a)mauigateway.com] Sent: Wednesday, 29 November 2006 7:24 a.m. To: Philip D'Ath Subject: Re: [nznog] IPv4 Exhaustion Hello, : The release of IP based set top box's and : the like is going to make the problem worse. Do you mean for IPTV? I use 1918 space for them and a public IP for the DSL router. I haven't used extra IPs for triple play stuff. scott --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> To: jamie.baddeley(a)vpc.co.nz Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] IPv4 Exhaustion Date: Tue, 28 Nov 2006 21:33:07 +1300 The number of mobile devices with IP addresses now exceeds the number of traditional internet hosts. The gap between these two is growing. Mobile carriers have a more urgent need to use IPv6. The release of IP based set top box's and the like is going to make the problem worse. -----Original Message----- One question that I'd have is how much of that IPv4 space is used, planned to be used, or will never be used? And then I'd ask that same question to APNIC members in NZ who've got IPv4 assignments. And then I'd ask the cellular providers who shall remain unnamed that recently started announcing a /16 of v4 what their expectations of that v4 assignment lifetime is. That's 'the canary in the mine' IMHO. > > Notwithstanding, its still pretty hard to find an upstream provider offering > end to end IPv6 in or from NZ. > > Some of the debate on IPv4 exhaustion is pretty abstract, with some > alarmists saying the end is nigh, others saying that shortage of space will > lead to a secondary and valuable market for selling the space etc. > > It occurs to me that IPv6 is inevitable, its not a question of if, but a > question of when. I agree. Though there comes a point where the When is so far away, it starts to look like an If :-) > > To that end, is there an enthusiasm within the NOG for NZ to be leaders, or > are we content to be followers in the transition? That's a fair question. Whilst there's seems to be no real solid business case to deploy it in the short term or a reason to entertain the idea, frankly at this point in proceedings being a watcher, or follower as you put it, is probably a sensible thing to do for *some* operators. Now if we could convince *the rest of the world* to pay NZ to be a self contained, network of networks v6 test-bed that is an entirely different matter. That would certainly be worth leading on, and I'd be fairly excited about that. jamie _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

5 4

Re: [nznog] Fwd: RE: IPv4 Exhaustion
by Scott Weeks 28 Nov '06

28 Nov '06

--- ender(a)paradise.gen.nz wrote: From: David Robb <ender(a)paradise.gen.nz> On Tue, 28 Nov 2006, Scott Weeks wrote: > Comcast has all of them in one AS? Similarly, China will have all 1B > customers in one AS? If not, they can use the same 1918 space in each > one. Also, Comcast are not going to have 100M IPTV subscribers. I got > this from www.ncta.com/ContentView.aspx?contentId=2685 : Which is more complicated? Managing overlapping address blocks, : probably in a system which was never designed to do that, or : moving to a unique IP address per endpoint? (Also probably in a : system which was never designed for IPv6) I would think moving a network that supports many tens of millions of customers to IPv6 would be more complicated than readdressing 1918 space (probably via DHCP) to be non-overlapping. scott

1 0

Fwd: RE: IPv4 Exhaustion
by Scott Weeks 28 Nov '06

28 Nov '06

Oops, I didn't send this one to the list. scott --- pid(a)ifm.net.nz wrote: : Let's take a specific example. Comcast have 100 million : customers on their own, in their one single network. : This is a single operator. : : Lets assume that in 10 years time China has 1 billion : set top box's. : : RFC1918 is not big enough. IPv4 is barely big enough. : It has to go to IPv6. Comcast has all of them in one AS? Similarly, China will have all 1B customers in one AS? If not, they can use the same 1918 space in each one. Also, Comcast are not going to have 100M IPTV subscribers. I got this from www.ncta.com/ContentView.aspx?contentId=2685 "In 2001, partly in response to those demands, AT&T agreed to fold its cable systems with those of Comcast Corp., creating the largest ever cable operator with more than 22 million customers." "Cable’s high-speed Internet service ended the quarter (Third Quarter of 2005) with 24.3 million subscribers, and the number of digital cable customers had grown to 27.6 million." This is in the US only, though. scott -----Original Message----- From: Scott Weeks [mailto:surfer(a)mauigateway.com] Sent: Wednesday, 29 November 2006 8:59 a.m. To: Philip D'Ath Cc: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] IPv4 Exhaustion --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> : : 17 million addresses is simply not enough for a country the size of the : US (and many others). They already have 100 million set top box's : deployed. :-) RFC1918 space is used within a network only. Not across networks. So, one network's IPTV customer can have the same STB IP address as another's when the RCF1918 space is used. You stream from your head-end to your customers only, so there's no need for public IP addressing. The traffic stays within a particular network. That is, unless you're talking about broadcasting on the internet to any STB in the world, or something like that. : Sorry, didn't realise you intended the email to be private. It seemed : of a nature that would interest other people in this thread. It's ok. I was unsure if everyone wanted to hear my non-beer-goggled responses. Responses are so much more interesting when typed while one's beer-goggled... ;-) scott -----Original Message----- From: Scott Weeks [mailto:surfer(a)mauigateway.com] : The release of IP based set top box's and : the like is going to make the problem worse. :: Do you mean for IPTV? I use 1918 space for them and :: a public IP for the DSL router. I haven't used extra :: IPs for triple play stuff. --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> : : Think 20 years down the track. : : Mobile phones and IP set top boxes are likely to : EXCEED the size of the RFC1918 address space. : There simply wont be enough of it. Well, I guess I don't mind a private email going public... There're about 17891328 RFC1918 IPs. Let's say you're going to use 7891328 IPs for internal addressing issues. That still leaves 10 million STB IP addresses for your network. scott --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> To: surfer(a)mauigateway.com Cc: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] IPv4 Exhaustion Date: Wed, 29 Nov 2006 07:47:59 +1300 Think 20 years down the track. Mobile phones and IP set top boxes are likely to EXCEED the size of the RFC1918 address space. There simply wont be enough of it. -----Original Message----- From: Scott Weeks [mailto:surfer(a)mauigateway.com] Sent: Wednesday, 29 November 2006 7:24 a.m. To: Philip D'Ath Subject: Re: [nznog] IPv4 Exhaustion Hello, : The release of IP based set top box's and : the like is going to make the problem worse. Do you mean for IPTV? I use 1918 space for them and a public IP for the DSL router. I haven't used extra IPs for triple play stuff. scott --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> To: jamie.baddeley(a)vpc.co.nz Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] IPv4 Exhaustion Date: Tue, 28 Nov 2006 21:33:07 +1300 The number of mobile devices with IP addresses now exceeds the number of traditional internet hosts. The gap between these two is growing. Mobile carriers have a more urgent need to use IPv6. The release of IP based set top box's and the like is going to make the problem worse. -----Original Message----- One question that I'd have is how much of that IPv4 space is used, planned to be used, or will never be used? And then I'd ask that same question to APNIC members in NZ who've got IPv4 assignments. And then I'd ask the cellular providers who shall remain unnamed that recently started announcing a /16 of v4 what their expectations of that v4 assignment lifetime is. That's 'the canary in the mine' IMHO. > > Notwithstanding, its still pretty hard to find an upstream provider offering > end to end IPv6 in or from NZ. > > Some of the debate on IPv4 exhaustion is pretty abstract, with some > alarmists saying the end is nigh, others saying that shortage of space will > lead to a secondary and valuable market for selling the space etc. > > It occurs to me that IPv6 is inevitable, its not a question of if, but a > question of when. I agree. Though there comes a point where the When is so far away, it starts to look like an If :-) > > To that end, is there an enthusiasm within the NOG for NZ to be leaders, or > are we content to be followers in the transition? That's a fair question. Whilst there's seems to be no real solid business case to deploy it in the short term or a reason to entertain the idea, frankly at this point in proceedings being a watcher, or follower as you put it, is probably a sensible thing to do for *some* operators. Now if we could convince *the rest of the world* to pay NZ to be a self contained, network of networks v6 test-bed that is an entirely different matter. That would certainly be worth leading on, and I'd be fairly excited about that. jamie _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Re: [nznog] IPv4 Exhaustion
by Scott Weeks 28 Nov '06

28 Nov '06

-----Original Message----- From: Scott Weeks [mailto:surfer(a)mauigateway.com] : The release of IP based set top box's and : the like is going to make the problem worse. :: Do you mean for IPTV? I use 1918 space for them and :: a public IP for the DSL router. I haven't used extra :: IPs for triple play stuff. --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> : : Think 20 years down the track. : : Mobile phones and IP set top boxes are likely to : EXCEED the size of the RFC1918 address space. : There simply wont be enough of it. Well, I guess I don't mind a private email going public... There're about 17891328 RFC1918 IPs. Let's say you're going to use 7891328 IPs for internal addressing issues. That still leaves 10 million STB IP addresses for your network. scott --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> To: surfer(a)mauigateway.com Cc: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] IPv4 Exhaustion Date: Wed, 29 Nov 2006 07:47:59 +1300 Think 20 years down the track. Mobile phones and IP set top boxes are likely to EXCEED the size of the RFC1918 address space. There simply wont be enough of it. -----Original Message----- From: Scott Weeks [mailto:surfer(a)mauigateway.com] Sent: Wednesday, 29 November 2006 7:24 a.m. To: Philip D'Ath Subject: Re: [nznog] IPv4 Exhaustion Hello, : The release of IP based set top box's and : the like is going to make the problem worse. Do you mean for IPTV? I use 1918 space for them and a public IP for the DSL router. I haven't used extra IPs for triple play stuff. scott --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> To: jamie.baddeley(a)vpc.co.nz Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] IPv4 Exhaustion Date: Tue, 28 Nov 2006 21:33:07 +1300 The number of mobile devices with IP addresses now exceeds the number of traditional internet hosts. The gap between these two is growing. Mobile carriers have a more urgent need to use IPv6. The release of IP based set top box's and the like is going to make the problem worse. -----Original Message----- One question that I'd have is how much of that IPv4 space is used, planned to be used, or will never be used? And then I'd ask that same question to APNIC members in NZ who've got IPv4 assignments. And then I'd ask the cellular providers who shall remain unnamed that recently started announcing a /16 of v4 what their expectations of that v4 assignment lifetime is. That's 'the canary in the mine' IMHO. > > Notwithstanding, its still pretty hard to find an upstream provider offering > end to end IPv6 in or from NZ. > > Some of the debate on IPv4 exhaustion is pretty abstract, with some > alarmists saying the end is nigh, others saying that shortage of space will > lead to a secondary and valuable market for selling the space etc. > > It occurs to me that IPv6 is inevitable, its not a question of if, but a > question of when. I agree. Though there comes a point where the When is so far away, it starts to look like an If :-) > > To that end, is there an enthusiasm within the NOG for NZ to be leaders, or > are we content to be followers in the transition? That's a fair question. Whilst there's seems to be no real solid business case to deploy it in the short term or a reason to entertain the idea, frankly at this point in proceedings being a watcher, or follower as you put it, is probably a sensible thing to do for *some* operators. Now if we could convince *the rest of the world* to pay NZ to be a self contained, network of networks v6 test-bed that is an entirely different matter. That would certainly be worth leading on, and I'd be fairly excited about that. jamie _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Re: [nznog] IPv4 Exhaustion
by Philip D'Ath 28 Nov '06

28 Nov '06

Think 20 years down the track. Mobile phones and IP set top boxes are likely to EXCEED the size of the RFC1918 address space. There simply wont be enough of it. -----Original Message----- From: Scott Weeks [mailto:surfer(a)mauigateway.com] Sent: Wednesday, 29 November 2006 7:24 a.m. To: Philip D'Ath Subject: Re: [nznog] IPv4 Exhaustion Hello, : The release of IP based set top box's and : the like is going to make the problem worse. Do you mean for IPTV? I use 1918 space for them and a public IP for the DSL router. I haven't used extra IPs for triple play stuff. scott --- pid(a)ifm.net.nz wrote: From: Philip D'Ath <pid(a)ifm.net.nz> To: jamie.baddeley(a)vpc.co.nz Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] IPv4 Exhaustion Date: Tue, 28 Nov 2006 21:33:07 +1300 The number of mobile devices with IP addresses now exceeds the number of traditional internet hosts. The gap between these two is growing. Mobile carriers have a more urgent need to use IPv6. The release of IP based set top box's and the like is going to make the problem worse. -----Original Message----- One question that I'd have is how much of that IPv4 space is used, planned to be used, or will never be used? And then I'd ask that same question to APNIC members in NZ who've got IPv4 assignments. And then I'd ask the cellular providers who shall remain unnamed that recently started announcing a /16 of v4 what their expectations of that v4 assignment lifetime is. That's 'the canary in the mine' IMHO. > > Notwithstanding, its still pretty hard to find an upstream provider offering > end to end IPv6 in or from NZ. > > Some of the debate on IPv4 exhaustion is pretty abstract, with some > alarmists saying the end is nigh, others saying that shortage of space will > lead to a secondary and valuable market for selling the space etc. > > It occurs to me that IPv6 is inevitable, its not a question of if, but a > question of when. I agree. Though there comes a point where the When is so far away, it starts to look like an If :-) > > To that end, is there an enthusiasm within the NOG for NZ to be leaders, or > are we content to be followers in the transition? That's a fair question. Whilst there's seems to be no real solid business case to deploy it in the short term or a reason to entertain the idea, frankly at this point in proceedings being a watcher, or follower as you put it, is probably a sensible thing to do for *some* operators. Now if we could convince *the rest of the world* to pay NZ to be a self contained, network of networks v6 test-bed that is an entirely different matter. That would certainly be worth leading on, and I'd be fairly excited about that. jamie _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

[semi-ot] 0800 number ownership
by Jasper Bryant-Greene 27 Nov '06

27 Nov '06

Hi all, excuse the OT post, but not sure where else to turn. Not really something the helpdesks wish to help with. I currently have 0800 service provided by a company called Supra Limited, run by a certain airline-company-hoax-monger from Nelson [1]. I have serious concerns about the stability of this company. Given that this company does not answer its phones at any time of day or night, does not return emails, and the owner appears to be an 18-year-old who has disappeared off the face of the earth, is there a way to get my 0800 number back? It's still working, but as far as I'm concerned these guys could stop paying the bills at any time, and then it will be down while I sort things out. Any ideas, anyone that can help? Replies off-list. Once again, excuse the OT post. [1] http://www.google.co.nz/search?q=Lamar+Hargreaves should provide some hilarity. -- Jasper Bryant-Greene Director Album Limited jasper(a)albumltd.co.nz +64 21 708 334 / 0800 425 286 http://www.albumltd.co.nz/

3 2

Re: [nznog] Observation
by Martin Kealey 27 Nov '06

27 Nov '06

> > Just an observation: if ISPs are planning on introducing measures such > > as hardware spam filters that drop connections without the standard SMTP > > response code, or greylisting, or similar measures likely to have > > widespread effect, a simple post to this list detailing what is about to > > happen would probably save a lot of people a lot of time :) LARTs will be applied in appropriate places... :-) > And/or they could just answer postmaster@, like good little > mail admins. As of my arrival, that is being done here at Ihug; I apologise on behalf of my predecessors for not doing so. And now that I've cleared out the 119000 messages in the postmaster mailbox, you might get some answers. :-) -Martin

1 0

Observation
by Jasper Bryant-Greene 27 Nov '06

27 Nov '06

Just an observation: if ISPs are planning on introducing measures such as hardware spam filters that drop connections without the standard SMTP response code, or greylisting, or similar measures likely to have widespread effect, a simple post to this list detailing what is about to happen would probably save a lot of people a lot of time :) -- Jasper Bryant-Greene Director Album Limited jasper(a)albumltd.co.nz +64 21 708 334 / 0800 425 286 http://www.albumltd.co.nz/

2 1

Ihug mail admins
by TreeNet Admin 26 Nov '06

26 Nov '06

Could one of you in charge of the ihug mail servers please contact me. You may need to use abuse(a)treenetnz.com. AYJ Treehouse Networks Ltd.

3 2

Searching For ...
by David Farrar 26 Nov '06

26 Nov '06

To keep this slightly on-topic I'll promise to shout a beer at the next NZNOG Conference to anyone who can supply an e-mail address or other contact details for any of the people below. Rex Croft, ex Wai Uni Alan Marsden, ex pl.net Chris Tyler, ex-Xtra Peter Whimp, ex Tuia Patrick O'Brien, ex Domainz Tim & Nick Wood, ex Ihug Responses directly to me would be great. Many thanks David Farrar

3 2

Xtra mail admin
by Jasper Bryant-Greene 26 Nov '06

26 Nov '06

Can a mail admin from Xtra please contact me off list. Thanks -- Jasper Bryant-Greene Director Album Limited jasper(a)albumltd.co.nz +64 21 708 334 / 0800 425 286 http://www.albumltd.co.nz/

1 0

Re: [nznog] [Fwd: [Computer-support] Greylisting - one day after]
by Richard 23 Nov '06

23 Nov '06

Hi Russell Russell Fulton wrote: > This might be of interest to NZNOG members -- we have just > implemented grey listing for some addresses and the results have been > dramatic to say the least... Likewise, I've been using greylisting on my various domains, some of which have been receiving spam for many years, for a year or so now. The initial results were staggering, but in recent months I've started to get a trickle comiag through again - looks like the scum are searching for open relays again. Still, at least *that* problem isn't as big as it once was. Cheers Richard -- Richard Stevenson Freelance Unix geek 027 285 5873

7 7

ihug email
by Jasper Bryant-Greene 22 Nov '06

22 Nov '06

Could someone from ihug please contact me off-list regarding your email servers. Thanks -- Jasper Bryant-Greene Director Album Limited jasper(a)albumltd.co.nz +64 21 708 334 / 0800 425 286 http://www.albumltd.co.nz/

1 0

Government changes 2.3 GHz rules (and other bands)
by Ian McDonald 22 Nov '06

22 Nov '06

>From http://www.beehive.govt.nz/ViewDocument.aspx?DocumentID=27807 Government promotes wireless broadband investment The government's decision to reallocate spectrum for wireless broadband is another essential step in providing New Zealanders with better, more competitive access to broadband, says Communications Minister David Cunliffe. The decision will see spectrum in the 2.3 GHz range – suitable for such emerging wireless broadband applications as WiMAX – put up for auction in early 2007. While current right-holders do not have to give up their rights before they expire in 2010, some may choose to do so. It is expected that some of the 2.3 GHz spectrum could be available for development immediately after the auction, enabling early development of new broadband wireless services. Other decisions include making a 16MHz block as a "managed park" suitable for local and regional broadband operations, and developing policies to facilitate future use of other spectrum suitable for broadband wireless access (BWA). Along with the other recent measures to develop a vibrant, competitive ICT sector, the availability of additional broadband wireless spectrum will help unlock the potential of these new technologies, and aid New Zealand's economic transformation into an innovative and creative knowledge-based economy. "This decision reflects the fairest and most effective way of giving new and existing wireless broadband services providers the opportunity to develop this very important spectrum for broadband in New Zealand," Mr Cunliffe said. "BWA technology for this band is only just starting to become available. It is critical that we create the right conditions for its future deployment by giving a wide range of players the opportunity and the certainty they need to make a long-term investment." "How we run the process and allocate the rights will obviously be critical. A spectrum cap of 30 MHz per operator – which generally accepted industry standards indicate would be ample – would ensure at least three separate lots of spectrum will be on offer. Successful purchasers will be required to implement services within a specified period." This announcement reaffirms a 2004 government decision that existing rights would not be renewed when they expire in 2010. It follows public consultation in which industry feedback showed strong support for immediate reallocation of this spectrum. Background information: Summary of decisions Allocation of the 2.3 GHz spectrum Up to eight 10 MHz-wide management rights in the 2.3 GHz band will be reallocated by auction as soon as is practicable. A 16 MHz block will be made available as a managed spectrum park from 2010, or earlier if available. The Ministry of Economic Development expects to conduct the auction in the first quarter of 2007, with the following conditions: * a spectrum cap of 30 MHz per operator will apply for two years from the date of allocation; and * right-holders will be required to implement services within a specified period or face revocation. Subject to discussions with right-holders for early relinquishment of their current 2.3 GHz spectrum rights, some of the auctioned spectrum rights will be available for use immediately after the auction, while a smaller amount may not become available until current rights expire in 2010. Transition plan for 2.5 GHz spectrum Spectrum at 2.5 GHz is suitable for BWA technology in a manner equivalent to the 2.3 GHz band, but the band is currently used for television outside broadcasting (e.g. linking back to the studio). The ministry will develop and implement a transition plan, in consultation with stakeholders, to make this band available for future BWA allocation, once technical parameters have been determined at the World Radio Conference in 2007. New General User Licences at 5.4 GHz and 60 GHz The ministry intends to create a general user licence ('public park' licence) to facilitate the deployment of BWA services at 5.4 GHz by June 2007, subject to suitable protection for existing radar applications in the band. A general user licence will also be issued for BWA services at 60 GHz by June 2007, with conditions that balance technical neutrality with spectrum utility and efficiency. 70, 80, 90 GHz and other bands There are at present no policies for licensing of the 70, 80 and 90 GHz bands, but interest in using these bands for BWA is becoming evident. In anticipation of future demand, the ministry is developing policy proposals for these bands. There is some interest in other bands, including projected changes to the existing 921 to 929 MHz general user licence and the 10.5 GHz bands. Policy and technical work for these bands is continuing. -- Ian McDonald Web: http://wand.net.nz/~iam4 Blog: http://imcdnzl.blogspot.com WAND Network Research Group Department of Computer Science University of Waikato New Zealand

1 0

NZNOG 2007: CFP: Network Systems Administration MiniConf
by Ewen McNeill 22 Nov '06

22 Nov '06

Call for Presentations for NZNOG 2007: Network Systems Administration Mini-Conference In conjunction with the NZNOG 2007 conference (http://www.nznog.org/) we will be holding a network systems administration mini-conference on the tutorial day, Wednesday 2007-01-31. The NZNOG 2007 conference will be held in Palmerston North between 2007-01-31 and 2007-02-02. Registration at the NZNOG 2007 conference is a mandatory prerequisite for attendence at the mini-conference; we expect there will be no additional charge. The mini-conference's focus is on "Layer 7" issues to do with network and ISP operations, including providing customer services (email, DNS, etc) and provisioning and management topics. We are now seeking proposals for presentations at the mini-conference. We have openings for: - 50-60 minute full presentations - 25-30 minute half presentations - 5-10 minute "lightning talks" Presentations are expected to be directed at a technical audience, and focused on a system administration area related to network or ISP operations. Some possible topics: - Email servers and spam filtering techniques - DNS servers, registry systems - server security and best sysadmin practices in an internet provider environment - VoIP servers - network management / monitoring tools - RADIUS/TACACS - Netflow, routing, and traffic analysis tools - server tuning for high performance networking - provisioning tools - honeypots and other security techniques - network based storage - high availability and disaster recovery for network services - virtual machine technology for network services - *nix based routing and fire-walling - tools you need that you may not know about We are happy to discuss the suitability of other topics with intending presenters. Timeline: - proposals due by 2006-12-04 - selection advised by 2006-12-11 - draft program published by 2006-12-18 - presentations 2007-01-31 Please send all proposals and questions to <talks(a)nznog.miniconf.org> Simon Lyall and Ewen McNeill, Conveeners

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Nov '06

21 Nov '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS7657 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR REPLACED BY: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink descr: WIX peering at '202.7.0.32' descr: see Citylink RT job #7338 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS7657 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061122 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: advertised to AS9439 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 97.64.46.0/24^24-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 203.118.144.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061116 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set advertised to AS9439 by Cafenet-Free - AS23754 members: 198.48.3.192/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061122 source: NZRR

1 0