Comment in line...
On 4 Apr 2016 18:19, "Ratliff, Stanley" <sratliff@xxxxxxxxxxx> wrote:
<mailto:charles.perkins@xxxxxxxxxxxxx>> wrote:
Sent from my iPhone
On Apr 4, 2016, at 6:17 PM, Charlie Perkins <charles.perkins@xxxxxxxxxxxxx
responses below would be quite simple to include (e.g., about whether RREQ
Hello Lotte,
I'm definitely O.K. with publishing ASAP. Some of the text in my
contentious amongst ourselves, because I am worried that it will look like
A possibly good resolution is better than nothing, unless it is
not very much text.
So I would ask for people to comment on my proposed resolutions. It's
charles.perkins@xxxxxxxxxxxxx<mailto:charles.perkins@xxxxxxxxxxxxx>>:
Regards,
Charlie P.
On 4/4/2016 1:29 PM, Lotte Steenbrink wrote:
Hi Charlie,
Am 04.04.2016 um 22:23 schrieb Charlie Perkins <
O.K., right? A bit of follow-up...
Hello Lotte,
Thanks for getting this ready. For the TODOs, partial resolutions are
think we have to resolve all of them in order to publish. Let’s get what we
I think it’s better to fully resolve them in one go :) Also, I don’t
be defined in Route Error Generation section JWD TODO: why there? If you
Valid route
A route that can be used for forwarding. (the deleted part should
should be defined in Route Error Generation section JWD TODO)
I'm O.K. with the cross-reference. What else is needed?
Unreachable Address
An address reported in a Route Error message. (the deleted part
as is.
Actually, I don't think anything more is really needed. This can be left
(consider adding a maximum single hop value JWD TODO)
This would be a bad idea
Why?
Stan
are being waited on? JWD TODO)
RREQ_Gen awaits reception of a Route Reply message (RREP) containing
a route toward TargAddr. (is there some table that lists routes that
good. Otherwise, the discovery times out and presumably a retry happens up
I don't see the need for such a table. If the RREP arrives, the route is
outlines which messages are more important but now how to decide to allow
(There is no defined behavior here. Approaching the limit? Section 6.5
to {1/CONTROL_TRAFFIC_LIMIT}, and discarding messages when the queue was
As I understand it, we decided on queueing things, limiting transmission
limit? and 6.5 doesn’t disalow anything JWD TODO)
(this again doesn’t describe a defined behaivor. approaching athe
metric routes in that they will be selected regardless of the time. Not a
Similarly as the last comment, right?
There might be a problem with very short validity times on very low
absolutely DO want to pick the smallest metric even if just for long enough
I do not see what issues could be caused. Under some metrics, we
AODVv2 parameterization.
Unless you would like to start defining a socket interface for dynamic
associated with this AckReq JWD TODO)
(same as before JWD TODO)
so shouldn't be counted as increasing the total...
(THere needs to be some sort of table which is updated with timer
something I should do?
What is the current status of this? Has anything been written? Is it
TLVs for use with RREQ JWD TODO?)
(this ins’t mandatory, right? Just AODVv2 doesn’t define any message
O.K.?
"AODVv2 does not define any Message TLVs for an RREQ message"... is this
message"... is this O.K.?
An RREP contains no Message TLVs.
(This isn’t mandatory is it? just none are defined by AODVv2. JWD TODO?)
Similarly, "AODVv2 does not define any Message TLVs for an RREP
message"... is this O.K.?
An RREP_Ack contains no Message TLVs.
(Mandatory or just not defined? JWD TODO?)
Similarly, "AODVv2 does not define any Message TLVs for an RREP_Ack
such a TLV block in the future.
An RREP_Ack contains no Address Block.
(Mandatory or just not defined? Guessing mandatory on this one. JWD TODO)
8.3.4. Address Block TLV Block
An RREP_Ack contains no Address Block TLV Block.
(Mandatory or just not defined? Guessing mandatory on this one. JWD TODO)
Aren't these the same? Isn't the same resolution? Someone could write
to publish asap, I thought I’d give you a quick status update and wait for
Regards,
Charlie P.
On 4/4/2016 12:54 PM, Lotte Steenbrink wrote:
Hi all,
since we’re allowed to submit Drafts again now (I think) and we decided
Justin’s review if you want to look for the remaining 26 TODOs, it’s the
DONE:
————
* All JWD!s are resolved now
* out of 90 JWD and JWD! comments, 64 are done (I’ve attached my copy of
* added revised security considerationsWe decided to add a separate
TO DO:
————
* Most notable of the 26 JWDs that are yet to be resolved:
+ (is there some table that lists routes that are being waited on? JWD)
RREP table that lists them and I’ve volunteered to write textfor that, but every time I set out to do that,
I got more confused… I’m starting to worry about the amount oftables AODVv2 needs by now, and
I’ve been picking Vickys brain on how to achieve storing thatinfo without having to add another table,
but it’s an ongoing process.„[aodvv2-discuss] Re: Justin's review"
+ the approaching the limit thing we’re currently discussing in
* some TODOs in security considerations (see github)multiplexer wording, so that hasn’t changed yet
* still waiting for Chris’ feedback regarding the revised 5444
* Make it more clear that AODVv2 currently doesn’t support RREQs forprefixes to make Thomas happy (I’m planning to do that tomorrow afternoon)
What do you think?
Regards,
Lotte
_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________