RE: [Mip6] Comments on jee-mip6-bootstrap-pana

hi alper, 

when i read the draft i came accross the same questions. 

i like your pull (instead of the push approach). this might also work nicely
with <draft-ietf-mip6-auth-protocol-00.txt>. 

i wasn't sure how and when the MIPv6-AAA-Key is computed as well. 

a minor correction to your mail: the diameter application ships the
parameters to the PAA (and not to the mobile node). this is the reason why a
pana protocol is required which carries the parameters finally to the end
host. this is probably the most important difference with regard to the
<draft-giaretta-mip6-authorization-eap> draft.

ciao
hannes

ps: it might be good to reference an old draft
<draft-le-aaa-diameter-mobileipv6-02.txt> which proposed the same approach.
i also remember that julien published a draft with a similar idea some time
ago. 

> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@samsung.com] 
> Sent: Dienstag, 02. November 2004 02:23
> To: mip6@ietf.org
> Subject: [Mip6] Comments on jee-mip6-bootstrap-pana
> 
> Hello,
> 
> Here are some comments and questions on the 
> draft-jee-mip6-bootstrap-pana-00.txt.
> 
> - I see the new Diameter application has two functionalities. 
> Regarding the delivery of the bootstrapping information to 
> the MN, I was wondering if we could get away with not 
> defining new commands, but instead piggybacking on existing 
> NAS application? The bootstrapping information could be 
> delivered to the NAS as part of the mobile's profile.
> 
> - The other functionality is the push of bootstrapping 
> information from AAAh to HA. This is carried in serial with 
> the (in fact, in the middle
> of) network access AAA. I think it could be done in parallel, 
> or even after the network access AAA. If you use a pull model 
> instead of the push, this part gets aligned with the 
> yegin-mip6-aaa-fwk.
> 
> - I didn't quite understand how the MN obtains/computes the 
> MIPv6-AAA-Key. It is only provided with the MIPv6-AAA-Key-Id, 
> and that's not sufficient to derive the key.
> 
> Thanks in advance.
> 
> Alper
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6