RE: draft-patel-mipv6-nai-option-00.txt

Alper,

To allow dynamic HA and HoA with IKEv1, NAI and HoA are used during IKEv1
phase1 and phase2 exchanges respectively. Subsequently the SPD and SAD are
updated with HoA and may be with NAI (used during IKE). The presence of HoA
in the SPD selector field will allow proper IPsec SA to be applied to the
received BU. Therefore, I think HoA is the only client ID required in the BU
if IPsec is used.

-Kuntal

>-----Original Message-----
>From: Alper Yegin [mailto:alper.yegin@xxxxxxxxxxx] 
>Sent: Wednesday, July 28, 2004 3:46 PM
>To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; mip6@xxxxxxxx
>Subject: RE: [Mip6] draft-patel-mipv6-nai-option-00.txt
>
>
>Hi Kuntal,
>
>> >Hello,
>> >
>> >While we are breaking away from using a home address as the only MN 
>> >identifier,
>> 
>> Can't we use FQDN or NAI as MN identifier during ISAKMP exchange?
>
>I think we still need an identifier along with the BU. I don't 
>know how you can get away without having one used along the BU.
>
>> > we might as well not limit ourselves to
>> >NAI only. I'd recommend defining a TLV for MN identifier, that can 
>> >carry FQDN and opaque types in addition to NAI and IPv6 address 
>> >types.
>> >
>> 
>> I see no problem adding that. Do you think an opaque TLV of type
>"string"
>> would suffice?
>
>Alper
>
>
>
>> 
>> >Alper
>> >
>> >
>> >
>> >_______________________________________________
>> >Mip6 mailing list
>> >Mip6@xxxxxxxx
>> >https://www1.ietf.org/mailman/listinfo/mip6
>> >
>
>