Re: [manet] Message integrity and message mutability (was RE: draft-ietf-manet-aodvv2-13 review - a couple of big ticket Items)

[Justin Dean <[e-mail]>]

On Mon, Apr 25, 2016 at 10:51 AM, Dearlove, Christopher (UK) <
[e-mail]> wrote:

> I has to go back to Victoria’s summary here. It says:
>
>
>
> 2) C creates the RREP. Since it doesnt know if the link to B is
> bidirectional, it includes the AckReq (an address to indicate that it
> expects to receive a RREP_Ack from B).
>
>
>
> That doesn’t actually indicate if that’s C’s address or B’s address being
> included. I’d assumed it was C’s address. Your comment makes sense if it’s
> B’s address. Reading again, I think you’re probably right. But only
> probably. Can we confirm that.
>
>
>
> I assume you meant that the RREP (not RREP_Ack) is multicast. There’s a
> bit of a chicken and egg problem here. We do know how we want to unicast.
>
> Yes I meant RREP and not RREP_Ack.

>
>
>From 7.2.3 again

The procedure for RREP regeneration is as follows:

   1.  If the link to the next hop router toward OrigAddr is not known
       to be bidirectional, include the AckReq with the address of the
       intended next hop router

 2. Set AddressList, PrefixLengthList, TargSeqNum and MetricType to

       the values in the received RREP

   3.  Set TargMetric := LocalRoute[TargAddr].Metric


4.  If the received RREP contains a ValidityTime, or if the
       regenerating router wishes to limit the time that it will offer a
       route to TargAddr (and any other addresses included in the given
       prefix length), the regenerated RREP MUST include ValidityTime

       *  The ValidityTime is either the time limit the previous AODVv2
          router specified, or the time limit this router wishes to
          impose, whichever is lower.