Let's talk text (was Re: EAP over IKEv2 as the defaultmechanism for HMIPv6)

James Kempf wrote:
> - I think the text should point to 
> draft-ietf-mip6-ikev2-ipsec-07.txt, 
> draft-ietf-mip6-bootstrapping-split-03.txt, and 
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt (if
relevant) and 
> specify what details in those drafts can be reused for
HMIP 
> security and 
> what details need to be changed (if anything) and what
those 
> changes are.

This makes sense IMHO, but wouldn't those drafts be
normative
references, i.e., wouldn't there be a problem to progress
HMIP as
proposed standard before the bootstrapping mechanisms are at
the same
standards level?

And do you mean reuse of HMIP security-related bootstrapping
mechabisms
(Ipsec SA setup and auth/authz with MSA) only or also other
bootstrapping mechanisms such as HA(->MAP) address
discovery and
HoA(->RCoA) assignment? The latter should be applicable
as well and it
might be valuable to consider them as an option in addition
to the
mechanisms specified in 4140.

Regards,

Kilian





_______________________________________________
Mipshop mailing list
Mipshopietf.org
https:
//www1.ietf.org/mailman/listinfo/mipshop

Kilian Weniger wrote:
> James Kempf wrote:
>> - I think the text should point to 
>> draft-ietf-mip6-ikev2-ipsec-07.txt, 
>> draft-ietf-mip6-bootstrapping-split-03.txt, and 
>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
(if relevant) and 
>> specify what details in those drafts can be reused
for HMIP 
>> security and 
>> what details need to be changed (if anything) and
what those 
>> changes are.
> 
> This makes sense IMHO, but wouldn't those drafts be
normative
> references, i.e., wouldn't there be a problem to
progress HMIP as
> proposed standard before the bootstrapping mechanisms
are at the same
> standards level?

the above three drafts are all targeted as proposed
standards and they are further ahead in the process
too. so that shouldnt be a problem.

Vijay

> 
> And do you mean reuse of HMIP security-related
bootstrapping mechabisms
> (Ipsec SA setup and auth/authz with MSA) only or also
other
> bootstrapping mechanisms such as HA(->MAP) address
discovery and
> HoA(->RCoA) assignment? The latter should be
applicable as well and it
> might be valuable to consider them as an option in
addition to the
> mechanisms specified in 4140.
> 
> Regards,
> 
> Kilian
> 
> 
> 
> 
> 
> _______________________________________________
> Mipshop mailing list
> Mipshopietf.org
> https:
//www1.ietf.org/mailman/listinfo/mipshop


_______________________________________________
Mipshop mailing list
Mipshopietf.org
https:
//www1.ietf.org/mailman/listinfo/mipshop