Re: [manet] AODVv2 responses to recent comments

[Abdussalam Baryun <[e-mail]>]

Hi All,

I did not read on the list that AODVv2 has problems in loops (IMO: no
participant reported this), it may happen outside the IETF because some
people may not understand AODV and we can advise them. I don't know why
participants are discussing a loop-problem that was not reported in details
in IETF.

Sorry that I don't understand the discussion of a problem that was not
defined, please help (I hope the participant that has the loop-problem to
respond because I still don't know who was the implementor)

AB

AB

On Thu, Mar 17, 2016 at 6:45 PM, <[e-mail]> wrote:

>
> On 17 Mar 2016, at 17:40, Dearlove, Christopher (UK) <
> [e-mail]> wrote:
>
> There is a problem when you have information that isn’t public. Though if
> it’s sent to you wearing IETF hat, is it covered by Note Well?
>
>
> This is actually an interesting point. As one of the WG chairs is also an
> author, I would assume that he’d have been a recipient of this information,
> and that therefore very much should be covered by Note Well?
>
> But let’s suppose you’ve decided you can’t give details. You probably can
> still say “Someone has raised an issue with us, we’re trying to get it
> handled.”. What you (one) can definitely do is bear that in mind and not
> makes statements that will later appear to be at odds with what you then
> knew.
>
> I’m still not clear as to whether there was a late discovered real problem
> that needed fixing.
>
>
> I’m with you on that one, coming down on the “…need to be convinced” side
> of the fence, however.
>
> Thomas
>
>
> *--*
>
>
>
>
> *Christopher DearloveSenior Principal EngineerBAE Systems Applied
> Intelligence Laboratories*
>
> *__________________________________________________________________________*
> *T*:  [phone]  |  *E: *[e-mail]
>
> BAE Systems Applied Intelligence, Chelmsford Technology Park, Great
> Baddow, Chelmsford, Essex CM2 8HN.
> www.baesystems.com/ai
> BAE Systems Applied Intelligence Limited
> Registered in England & Wales No: 01337451
>
> Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP
>
> *From:* Lotte Steenbrink [mailto:[e-mail]
> <[e-mail]>]
> *Sent:* 17 March 2016 16:19
> *To:* Dearlove, Christopher (UK)
> *Cc:* Charlie Perkins; manet
> *Subject:* Re: [manet] AODVv2 responses to recent comments
>
>
> **** WARNING ****
>
> *This message originates from outside our organisation, either from an
> external partner or the internet.*
>
> *Consider carefully whether you should click on any links, open any
> attachments or reply.For information regarding **Red Flags** that you can
> look out for in emails you receive, click here
> <http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Red%20Flags.pdf>.*
> *If you feel the email is suspicious, please follow this process
> <http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf>.*
> Hello Christopher,
>
>
> Am 16.03.2016 um 18:22 schrieb Dearlove, Christopher (UK) <
> [e-mail]>:
>
> I haven’t followed the example (I hope to find time - but that’s true of
> too many things, with DLEP ahead of AODVv2 on this list).
>
> But we have a loop, a pretty fundamental problem in a routing algorithm,
> being discussed by the authors off-list,
>
>
> If we could’ve, I would’ve loved to share this with the list immediately.
> I’m not sure if there’s a procedure for this kind of situation we should’ve
> followed? If there is, I’d be more than happy to learn from it and do
> better next time.
>
>
> while in parallel assuring the list that “Other discussion about routing
> loops has not identified routing loop problems in the existing
> specification.” (see email chain below).
>
>
> I think we have a real problem with what’s wanting to advance to Proposed
> Standard soon, in terms of process and confidence.
>
>
> I think I understand where your worries come from. However, I do think our
> efforts to improve our communication are visible, and apart from the
> communication delay, the fact that this research exists actually improves
> my confidence in the document: It found loops that were (imho) pretty
> tricky to come up with by thinking hard about the problem alone, and we’ve
> been able to fix them, making AODVv2 more solid.
>
>
>
> (I still haven’t managed to even write up comments on the perhaps one
> third of the draft I have read through yet.)
>
> Personally, I’d be happy to go through them in chunks as well :) Maybe
> that could also speed up the back and forth of „x isn’t quite right“ „would
> y resolve the issue?“ „yes/no“, which would in turn speed up the progress
> of this document? Anyhow, all feedback is very welcome.
>
> Best regards,
> Lotte Steenbrink
>
>
>
>
>
> *--*
>
>
>
>
> *Christopher DearloveSenior Principal EngineerBAE Systems Applied
> Intelligence Laboratories*
>
> *__________________________________________________________________________*
> *T*:  [phone]  |  *E: *[e-mail]
>
> BAE Systems Applied Intelligence, Chelmsford Technology Park, Great
> Baddow, Chelmsford, Essex CM2 8HN.
> www.baesystems.com/ai
> BAE Systems Applied Intelligence Limited
> Registered in England & Wales No: 01337451
>
> Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP
>
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
> _______________________________________________
> manet mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/manet
>
>
>
> _______________________________________________
> manet mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/manet
>
>