[Mipshop] Re: AD review of draft-ietf-mipshop-handover-key

Sure.

            jak

----- Original Message ----- 
From: "Jari Arkko" <jari.arkko@piuha.net>
To: <draft-ietf-mipshop-handover-key@tools.ietf.org>
Cc: "Mipshop" <mipshop@ietf.org>
Sent: Wednesday, October 31, 2007 1:43 PM
Subject: Re: AD review of draft-ietf-mipshop-handover-key

Thanks for the update.

The new draft solves my AD review issues, almost.
The one issue that still remains is that the explanation
on the use of SEND for securing AR's messages claims
that the AR must use a CGA. I believe this is incorrect,
and it is sufficient for the certified public key to be
used as a source address, as it is in SEND. I entered
the following edit to the tracker:

OLD:
     The AR MUST use the CGA constructed from its
     certified key as the source address for the PrRtAdv and include a
     SEND  CGA  Option  and  a  SEND  Signature  Option  with  the  SEND
     signature of the message.
NEW:
     The AR MUST have a certificate suitable for a SEND-capable router,
     support SEND certificate discovery, and include a SEND  CGA
     Option  and  a  SEND  Signature  Option  in the PrRtAdv messages
     it sends. Similarly, the mobile nodes MUST be configured with
     one or more SEND trust anchors so that they can verify these
     messages.

In any case, I'm sending the draft forward. If you can, update
the draft with this change so that other readers get it as well.
If not, the change will be retained as an RFC Editor note in
the tracker.

Jari

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