RE: DHCP-Diameter application for MIPv6 bootstrapping

Saumya,

Please see inline... 

> -----Original Message-----
> From: Upadhyaya Saumya-a20369 [mailto:saumya@xxxxxxxxxxxx] 
> Sent: Wednesday, August 09, 2006 7:04 AM
> To: mip6@xxxxxxxx
> Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
> 
> Kuntal,
> 
> In our approach, the MN is authenticated in the home domain. 

Isn't that always the case? The HAAA is in the home domain of the MN,
right?

> We mainly discuss DHCP authentication. This can be done in 
> addition to the authentication done at the NAS.
> 

I am not sure about the use case where the MN will be required to
authenticate twice to get access and obtain DHCP info. 
Someone may find such use case, but I have not seen one yet. If the
authentication function at the NAS does not exist and the DHCP
server is exposed to the public internet, may be such scheme is
desirable.

> In addition, we discuss the establishment of a security 
> association Dynamically between the DHCP Server and Client. 
> The DHCP options required for establishing this security 
> association are discussed in 
> http://www.ietf.org/internet-drafts/draft-ram-dhc-dhcpv6-aakey-00.txt
> 

This means yet another SA setup requirement for the MN. Normally the MN
gets authenticated at the NAS (PDSN, GGSN, ASN-GW) in most of the
wireless data networks today.

> - Saumya
> 
>  
> 
>  
> 
> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@xxxxxxxxxxxxxxxxxxx]
> Sent: Monday, August 07, 2006 8:33 PM
> To: Upadhyaya Saumya-a20369; mip6@xxxxxxxx
> Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
> 
> Saumya,
> 
> In your proposal, do you envision any kind of authentication 
> at the DHCP server for the MN prior to assigning the MN HA, 
> HoA info? What is the likelihood that operators will 
> authenticate the MN at the DHCP server instead of or in 
> addition to the NAS (EAP-authenticator)?
> 
> There was a proposal a while back to use DHCP delayed 
> authentication scheme to perform MIP6 bootstrapping. Here is 
> the link of the expired
> I-D:
> 
> http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mi
> p6-boot-ar
> ch-dhcp-00.txt
> 
> Have you looked at this one? 
> 
> -Kuntal
> 
> > -----Original Message-----
> > From: Upadhyaya Saumya-a20369 [mailto:saumya@xxxxxxxxxxxx]
> > Sent: Monday, August 07, 2006 8:23 AM
> > To: mip6@xxxxxxxx
> > Subject: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
> > 
> > Hi Vijay,
> > 
> > We have gone over the listed drafts.
> > 
> > In our approach, we propose that the DHCP server contains a 
> AAA client 
> > which can thereby obtain the messages from either a local 
> entity (say, 
> > the AAAF/Local Diameter Proxy/NAS) or a home entity (say, the
> AAAH/Home
> > Diameter Server). This is in contrast to 
> > draft-ietf-dime-mip6-integrated-00 which proposes to obtain the 
> > bootstrapping parameters till the NAS using Diameter-EAP 
> and proposes 
> > that the NAS behave as a DHCP Relay. In our approach, the NAS can
> remain
> > independent of DHCP and need not perform any operations on the DHCP 
> > packets that it relays.
> > 
> > In our approach, we propose that the MN makes use of DHCP to obtain
> the
> > bootstrapping parameters irrespective of the network architecture 
> > (split/integrated).
> > 
> > In the draft [draft-ram-dhc-dhcpv6-diam-app-00], we define 
> a Diameter 
> > DHCP Application which could be used to obtain the MIPv6 
> bootstrapping 
> > parameters from the MSA.
> > 
> > Regards,
> > Saumya
> > 
> > Date: Fri, 4 Aug 2006 08:08:42 -0700
> > From: "Vijay Devarapalli" <Vijay.Devarapalli@xxxxxxxxxxxxx>
> > Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
> > To: "Upadhyaya Saumya-a20369" <saumya@xxxxxxxxxxxx>,        
> <mip6@xxxxxxxx>
> > Message-ID:
> > 
> > <C8E1D942CB394746BE5CFEB7D97610E701D993AF@xxxxxxxxxxxxxxxxxxxxxxx>
> > Content-Type: text/plain;   charset="iso-8859-1"
> > 
> > Hi Saumya,
> > 
> > the work on this is being done in the DIME WG. take a look at
> >
> http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integ
> rated-00.t
> > xt
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt
> > 
> > Vijay
> > 
> > 
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@xxxxxxxx
> > https://www1.ietf.org/mailman/listinfo/mip6
> 
> 
> "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 
> postmaster@xxxxxxxxxxxxxxxxxxx -- and destroy all copies of 
> this message and any attachments without reading or 
> disclosing their contents. Thank you."
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@xxxxxxxx
> https://www1.ietf.org/mailman/listinfo/mip6
>