Hi Lotte,
On Thu, Apr 16, 2015 at 3:07 PM, Lotte Steenbrink <
lotte.steenbrink@xxxxxxxxxxxx> wrote:
Hi Vicky, hi all,
Am 16.04.2015 um 15:58 schrieb Victoria Mercieca <vmercieca0@xxxxxxxxx>:
Hi all,
While going through the draft I've come up with a load of questions and
notes. Addressing these will make the draft more complete and resolve some
of the ambiguity which might affect an implementation.
I'm going to divide these into a number of emails so that it should be
easier to follow each discussion.
This email is about Sequence numbers (Section 6.4 in Version 9a or Section
4.4 in Version 9b):
1. The draft says we can use multiple SeqNums ("one per IP address").
What if there are multiple IP addresses on each interface - should they
have a SeqNum each, or share one SeqNum? Should it be one SeqNum per
interface? Or since we associate the SeqNum with a route to a Router
Client, should it be one SeqNum per Router Client?
2. If using multiple SeqNums, should we store the sequence number in
the interfaces list? (I have said we could do this in the draft)
3. When sending a RREQ on multiple interfaces, would the sequence
number be the same in all of them?
4. When sending retries for a RREQ, is the SeqNum updated?
5. Is TargSeqNum ever used in the RREQ? Is it something to do with
iRREP? If so should we have references to it in the main text?
Henning and I were wondering the same thing... We couldn't figure out
where TargSeqNum was actually used. Do we still need this feature?
Lotte
Comments welcome :-)
Kind regards,
Vicky.
