Hi all,
iirc, our consensus is to get a new Draft out as soon as we can… In order to
get that done, I’ve got a few issues I feel personally responsible for but I’ll
need your help with, so I thought I’d send a quick reminder since we’re all
busy people and E-mails get lost quickly:
1. Security Considerations TODOs:
There are still a lot of TODOs in our Security Considerations (see
http://ietf.10.n7.nabble.com/attachment/488740/1/13.%20Security%20Considerations_v3.txt
). I put them there because I either couldn’t figure out the answer myself, or
because I wasn’t sure if my answer was good enough. If you could have a look at
them and send me any proposals for update (or a yay/nay, for example concerning
(- is this sufficient? Am I overlooking a way to prevent this here?) in 13.1.1
Denial of Service), that’d be super helpful.
2. Resolving all JWD!s:
The critical issues raised by Justin that I have not resolved yet are:
(How does one know which outgoing interface is the neighbor associated with?
This seems like a very LARGE missing piece of required information JWD!)
(How is this done? There is no table with recently sent RERR messages to check.
There needs to be though. JWD!)
(AODVv2_INTERFACES isn’t defined before now it should be. Also what does this
configuration consist of? Also is the list empty if there is only one
interface? JWD!)
These all depend on Text promised by Charlie– I think the first one is part of
a bigger discussion (the „is using MAC addresses a good idea/super painful“
one, iirc), but we still need to drill down on the Language that describes the
*exact formatting* of the InterfaceSet (which is currently held in the thread
„Definition for AODVv2_INTERFACES“). That would also resolve the third issue.
Charlie, did you find the time to write said text yet? I f you didn’t and won’t
please say so, and in this case, does anybody else have the time? I can try,
but I’m not quite sure about the quality I’ll be able to deliver, so somebody
is going to have to volunteer to proofread that stuff.
Best regards,
Lotte
