- NZNOG - lists.nznog.org

Another Topic
by Peter Youngquest 29 Nov '06

29 Nov '06

Hey All I am personally bored with the IPV4-6 discussion, but while everyone is up and talking. What is everyones opinion in regard to PBT. Does this have a place, can it work happily as a feeder into an MPLS cloud or will it remove the need for MPLS. Rgds Peter

4 5

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 28 Nov '06

28 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 28 Nov '06

28 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