Subject: Re: [netlmm] Re: DHCPv6 deployment in PMIPv6 domain and SDO

From: Alexandru Petrescu <[email-masked]>
Date: Thu, 20 Sep 2007 16:23:58 +0200

Chowdhury, Kuntal wrote:
> 
>> -----Original Message----- From: Alexandru Petrescu
>> [mailto:[email-masked]] Sent: Wednesday, September
>> 19, 2007 4:15 PM To: Chowdhury, Kuntal Cc: Alper Yegin;
>> [email-masked]; Julien Laganier Subject: Re: [netlmm] Re: DHCPv6
>> deployment in PMIPv6 domain and SDO
>> 
>> Chowdhury, Kuntal wrote:
>>>> -----Original Message----- From: Alexandru Petrescu
>>>> [mailto:[email-masked]] Sent: Wednesday,
>>>> September 19, 2007 10:01 AM To: Alper Yegin Cc:
>>>> [email-masked]; 'Julien Laganier' Subject: [netlmm] Re: DHCPv6
>>>> deployment in PMIPv6 domain and SDO
>>>> 
>>>> Alper Yegin wrote:
>>>>>>> There are alternative approaches. Different DHCP servers
>>>>>>> (e.g., ones collocated with the MAGs) can be used as long
>>>>>>> as they can
> be
>>>>>>> dynamically-provisioned with the MN configuration
>>>>>>> parameters, for example, during network access
>>>>>>> authentication.
>>>>>> What's 'dynamically-provisioned'?  Is it a SDO-specific
> mechanism?
>>>>>> I don't know how a deployer would like to deploy a DHCP
>>>>>> Server in each MAG without mentioning how these pools of
>>>>>> addresses are dynamically provisioned.
>>>>> It's typically done via AAA. For example, sending
> Framed-IP-Address
>>>>> via RADIUS is for configuring that IP address via DHCP (or
>>>>> PPP).
>>>> Any deployed system today with wireless point-to-point links
>>>> using Framed-IP-Address via RADIUS gives that IP address to
>>>> mobile with
>>> DHCP?
>>>> I thought all are PPP.
>>>> 
>>>> I've framed my mind to think that if wireless access link is 
>>>> point-to-point then it's PPP, and if it's shared medium wifi
>>>> then
> it's
>>>> DHCP; never otherwise.
>>>> 
>>> [KC>] Nope...there are p2p wireless access links (3GPP, WiMAX)
>>> out there where PPP is not used.
>> 
>> Ok.  And on these links (3GPP, WiMAX) is DHCP used by the mobile? 
>> Because on GPRS and UMTS the mobile doesn't use DHCP.
>> 
> [KC>]
> 
> 3GPP: not in Rel7. In Rel8, DHCP may be used.

When?

> WiMAX: yes for IPv4. For IPv6, SLAAC is used to configure the IPv6 
> global address.

(Ok, so here we have a distinction from WiMAX for IPv6 vs IPv4 on the
  access link.  Our discussion can be different whether when we talk DHCP
  for PMIP6 draft or DHCP for v4-for-PMIP6 draft.)

For IPv6: IETF's 16ng wg specifies IPv6-over-IPCS to be either SLAAC or 
DHCPv6.  IEEE 802.16 too.  WiMax apparently requires only SLAAC, and not 
DHCP.  WiMax uses 802.16.

Should we advise WiMax to use DHCPv6 in addition to SLAAC?  Or should we 
advise 16ng WG to not use DHCPv6 for IPv6-over-IPCS?  Or should we 
advise IEEE 802.16 to not use DHCPv6 in the network-entry procedure?

Then what should we implement?

Alex

> 
> 
>> Alex
>> 
>>>> Alex
>>>> 
>>>> 
>>>> 
> ______________________________________________________________________
> 
>>>> This email has been scanned by the MessageLabs Email Security
> System.
>>>> For more information please visit
>>>> http://www.messagelabs.com/email
>>>> 
> ______________________________________________________________________
> 
>>>> _______________________________________________ netlmm mailing
>>>> list [email-masked] 
>>>> https://www1.ietf.org/mailman/listinfo/netlmm
>>> 
>>> "This email message and any attachments are confidential
>>> information
> of
>> Starent Networks, Corp. The information transmitted may not be used
>> to create or change any contractual obligations of Starent
>> Networks,
> Corp.
>> Any review, retransmission, dissemination or other use of, or
>> taking
> of
>> any action in reliance upon this e-mail and its attachments by
>> persons
> or
>> entities other than the intended recipient is prohibited. If you
>> are
> not
>> the intended recipient, please notify the sender immediately -- by 
>> replying to this message or by sending an email to 
>> [email-masked] -- and destroy all copies of this
> message
>> and any attachments without reading or disclosing their contents.
> Thank
>> you."
>> 
>> ______________________________________________________________________
>>  This email has been scanned by the MessageLabs Email Security
>> System. For more information please visit
>> http://www.messagelabs.com/email 
>> ______________________________________________________________________
>> 
> 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

_______________________________________________
netlmm mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/netlmm