Lotte,
I don't see that this went anywhere but aodvv2-discuss. Shouldn't it have gone
to manet?
Regards,
Stan
-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Lotte Steenbrink
Sent: Friday, February 19, 2016 10:06 AM
To: manet@xxxxxxxx
Subject: [aodvv2-discuss] AODVv2: Security considerations update
Hi all,
in the interest of transparency, we (the AODVv2 author team) want to send
out more updates on what we've been doing, and this is the first of these e-
mails. We've restructured (and sometimes rewritten) our security
considerations a bit and added a subsection about the Trust Model, and we'd
love to hear your opinions on those changes. You can find the result and a
diff to the current considerations in the attachments. (the formatting was
done manually, so it might be a bit wonky)
Some notes:
* This is all work in progress, so please poke holes into it where you can!
* While (afaik) the Availability/Confidentiality/Integrity model may be
considered a bit dated, I thought it might be a good starting point.
* I was wondering if "Encryption will not only protect against unauthorized
devices obtaining
information about network topology" isn't a tad too short and bold- maybe
we could add a clarification along the lines of:
Encryption will not only make it more difficult for unauthorized devices to
obtain
information about network topology but will also ensure that only trusted
routers participate in routing operations: When messages are encrypted,
a malicious observer would have to monitor the entire network to
understand
its topology and traffic flow. And even then, due to the hop by hop
nature of the protocol and the fact that messages are regenerated rather
than forwarded (resulting in a different payload every time),
following the path of a message would be hard if its transmission is not
the only encrypted traffic produced by the network.
Regards,
Lotte
