[arin-ppml] Draft Policy 2009-1: Transfer Policy -Revisedandforwarded to the Board

[Ted Mittelstaedt]

My phone is the original Moto Q running Windows Mobile 5.
Incidentally, I really prefer it over the new Q's because
the new Q's don't have a headphone jack anymore, although
that's neither here nor there.

Anyway, I checked again and your right - but, the phone does
get IPv4 dynamically assigned  (out of the 99.200.0.0/13 range).
Normally, there is no IP address on it.

Ted 

> -----Original Message-----
> From: George, Wes E [NTK] [mailto:Wesley.E.George at sprint.com] 
> Sent: Friday, May 08, 2009 12:06 PM
> To: Ted Mittelstaedt
> Cc: 'arin ppml'
> Subject: RE: [arin-ppml] Draft Policy 2009-1: Transfer Policy 
> -Revisedandforwarded to the Board
> 
> Ted,
> 
> If "my phone" = the aforementioned Moto Q on the Sprint 
> network, I can say with 100% certainty that you are *not* 
> doing exclusively IPv6 on your phone today. WinMo6 does 
> support 6to4 (2002:), and since we're assigning externally 
> routable IPv4 addresses to our customer devices, it *should* 
> be able to reach IPv6 addresses via 6to4 even though the 
> underlying network doesn't support IPv6. It likely even 
> prefers IPv6 addresses when they're available, but there is 
> not a standard IPv6 address (2001: or 2600:) being assigned 
> (yet), and certainly no IPv6-speaking device on Sprint's 
> network that could seamlessly translate between IPv6 and 
> IPv4, especially for things like SSH.
> I *wish* we were that far along already and that it was 
> working that well.
> 
> Wes George
> 
> -----Original Message-----
> From: Ted Mittelstaedt [mailto:tedm at ipinc.net]
> Sent: Friday, May 08, 2009 2:11 PM
> To: George, Wes E [NTK]; 'William Herrin'; 'Martin Hannigan'
> Cc: 'arin ppml'
> Subject: RE: [arin-ppml] Draft Policy 2009-1: Transfer Policy 
> -Revisedandforwarded to the Board
> 
>  > To your second point, this isn't really about widgets sitting
> > in a warehouse. It's the phone already in your hand. I 
> heard word that 
> > we had been asking vendors for IPv6 at least as a roadmap 
> item in in 
> > mobile devices for probably 2 years, but not every vendor 
> was able to 
> > necessarily deliver, and the ones that did may have had varying 
> > degrees of success in a complete and functional IPv6 implementation.
> 
> My Sprint Motorola Q that's a few years old is IPv6
> 
> > The expectation
> > is that attrition of old devices will partially solve this 
> problem by 
> > creating an installed base that does support IPv6 and (hopefully) 
> > needs an IPv4 address less often if at all.
> > But, depending on how often devices roll over, that may not 
> reduce the 
> > IPv4-using population enough either. Even then, that only puts this 
> > particular application on a par with the rest of the PC-using 
> > population: IPv6 is supported, but is only useful if we ensure that 
> > either a) every possible destination our users might go to is 
> > IPv6-capable or b) that there is some sort of intermediate 
> device that 
> > allows an IPv6-only device to reach IPv4-only websites.
> 
> I believe that is how Sprint does it with my phone.
> 
> > I fully expect that there will be classes of devices that can be 
> > IPv6-only either because they only need to reach IPv6 content or 
> > because the content that they reach can be proxied through an 
> > IPv6-to-IPv4 NAT/ALG, but not all devices will fall into that 
> > category.
> 
> On my phone I have a web browser, e-mail client, SSH client, 
> FTP client, RSS reader.  What else do I need?  My phone does 
> NOT have an IPv4 number on it, this I know from digging into it.
> 
> Ted
> 
> 
> 
> This e-mail may contain Sprint Nextel Company proprietary 
> information intended for the sole use of the recipient(s). 
> Any use by others is prohibited. If you are not the intended 
> recipient, please contact the sender and delete all copies of 
> the message.
> 
> 
>