Re: New Version Notification for draft-koodli-ipv6-in-mobile-networks-02

[Cameron Byrne <[e-mail]>]

On Fri, Apr 16, 2010 at 2:25 AM,  <[e-mail]> wrote:
> Hi Rajeev, all,
>
> I'm worried about the on-demand DHCP based address allocation descriptions herein.
>
> Majority of 3GPP devices do not implement DHCP at all today for 3GPP access, because it is optional and gives very little when compared to mandatory PPP-like address allocation during bearer establishment procedures.
>
> Introduction of DHCP for significant host population (to get statistical savings) just for the deferred IPv4 address allocation feature does not sound right thing to do for me.
>
> We should be adding IPv6 features to hosts, not IPv4 features.
>

Teemu, many handsets have DHCP for  the WiFi.  I agree with you in
principle somewhat (many transition steps add IPv4 functions), but i
believe the reality makes your point moot in many relevant cases.  I
strongly feel the transient on-demand IPv4 connection that  Rajeev has
suggested is very useful in IPv4 constrained environments that require
always-on connectivity (IMS ...).  I believe the on-demand IPv4
address can help address the IPv4 literal issue that is described in
draft-wing-behave-http-ip-address-literals, similar to a
dial-on-demand function... the handset always has a path to IPv4, but
the PDP is only setup when a packet needs to be transmitted.

Prior to release 7, i believe this is easy to control (give back ipv4
quickly) since we can configure the handset to terminate idle IPv4 PDP
quickly while the IPv6 is always up.  Once to release 8 and we have
dual-stack bearers, i am not sure the best way to address the
on-demand use of a transient IPv4 address.

Would you suggest the EPS bearer be re-established / re-negotiated to
deliver the IPv4 and IPv6 addresses over PCO- IE?  Is it possible to
send / request PCO-IE without dropping the original EPS bearer?

Cameron

ps.  This type of discussion is why the WG should accept this draft



> Best regards,
>
> Teemu
>
>> -----Original Message-----
>> From: [e-mail] [mailto:[e-mail]] On
>> Behalf Of ext Rajeev Koodli
>> Sent: 16. huhtikuuta 2010 01:05
>> To: [e-mail]
>> Subject: FW: New Version Notification for draft-koodli-ipv6-in-mobile-
>> networks-02
>>
>>
>> Hello folks,
>>
>> I was asked at the Anaheim meeting to clarify the intended audience for
>> this
>> ID, which I have done in the Introduction; this document can be a
>> useful
>> reference for service providers and network designers.
>> This ID does not propose any new protocols or suggest any new protocol
>> work.
>>
>> I also got a good review from Mohamed Boucadier (thanks!) which I have
>> addressed.
>>
>> It seemed there was good interest that this ID is useful.
>>
>> So, Chairs: how do we proceed?
>>
>> Thanks,
>>
>> -Rajeev
>>
>> http://tools.ietf.org/html/draft-koodli-ipv6-in-mobile-networks-02
>>
>>
>>
>> ------ Forwarded Message
>> From: IETF I-D Submission Tool <[e-mail]>
>> Date: Tue, 13 Apr 2010 16:30:59 -0700 (PDT)
>> To: Rajeev Koodli <[e-mail]>
>> Subject: New Version Notification for
>> draft-koodli-ipv6-in-mobile-networks-02
>>
>>
>> A new version of I-D, draft-koodli-ipv6-in-mobile-networks-02.txt has
>> been
>> successfully submitted by Rajeev Koodli and posted to the IETF
>> repository.
>>
>> Filename:  draft-koodli-ipv6-in-mobile-networks
>> Revision:  02
>> Title:   Mobile Networks Considerations for IPv6 Deployment
>> Creation_date:  2010-04-14
>> WG ID:   Independent Submission
>> Number_of_pages: 15
>>
>> Abstract:
>> Mobile Internet access from smartphones and other mobile devices is
>> accelerating the exhaustion of IPv4 addresses.  IPv6 is widely seen
>> as crucial for the continued operation and growth of the Internet,
>> and in particular, it is critical in mobile networks.  This document
>> discusses the issues that arise when deploying IPv6 in mobile
>> networks.  Hence, this document can be a useful reference for service
>> providers and network designers.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
>>
>> ------ End of Forwarded Message
>>
>
>
>