Hello Lotte,
Since it's a conceptual list, for interoperability I don't think it
matters what we specify. But for concreteness we can specify that the
conceptual list always has to contain one interface. If the implementer
writes code so that the list may be actually empty when there's one
interface, that's fine with me.
Regards,
Charlie P.
On 3/22/2016 3:35 AM, Lotte Steenbrink wrote:
Hi Charlie, hi all,
Am 21.03.2016 um 19:08 schrieb Charlie Perkins <charles.perkins@xxxxxxxxxxxxx <mailto:charles.perkins@xxxxxxxxxxxxx>>:
Hello folks,
I think the change in terminology is fine, either way.
Okay, change made. :) However, the text you’ve suggested doesn’t specify what the entries of the set should look like, and if I remember it correctly, that was the criticism we’ve received. I’m assuming an entry would contain something like
* Interface.id : the indentifier of the interface configured for use by AODVv2. Since the format of these identifiers is system-dependent, this field MAY be extended. This has no impact on interoperability.
But that’s only what I’d need to implement this for RIOT… Do the entries need to contain anything else?
Also, Justin asked
Also is the list empty if there is only one interface?
– what’s the answer to that? (I’d say the list SHOULD be empty then as it seems like a waste of space)
Will the new draft be out today?
Nope, I was waiting to hear back from Justin and Christopher– and also the Security Considerations have some TODOs to resolve, so if anyone has time to look at that… ;)
Regards,
Lotte
Regards,
Charlie P.
On 3/20/2016 4:12 AM, Victoria Mercieca wrote:
Hi Lotte,
I'd be happy with it becoming InterfaceSet for consistency, would that be an easy change to make?
Regards,
Vicky
On Sat, Mar 19, 2016 at 10:35 AM, Lotte Steenbrink <lotte.steenbrink@xxxxxxxxxxxx <mailto:lotte.steenbrink@xxxxxxxxxxxx>> wrote:
Hi all,
thinking about it again… Why is the set (or list? charlie’s text
has both words… I’m guessing it’s a set though?) called
AODVv2_INTERFACES, which looks like a constant, instead of
InterfaceSet, like the other sets and lists we have? Is it
because it’s administratively configured and doesn’t change? Or
something else? Or is it more or less random?
Regards,
Lotte
Am 17.03.2016 um 11:31 schrieb Charlie Perkins
<charles.perkins@xxxxxxxxxxxxx
<mailto:charles.perkins@xxxxxxxxxxxxx>>:
Hello Lotte,
Here's what I sent earlier:
-------- Forwarded Message --------
Subject: Definition for AODVv2_INTERFACES
Date: Fri, 4 Mar 2016 15:38:15 -0800
From: Charlie Perkins <charliep51@xxxxxxxxxxxxx>
To: aodvv2-discuss@xxxxxxxxxxxxx
<mailto:aodvv2-discuss@xxxxxxxxxxxxx>
<aodvv2-discuss@xxxxxxxxxxxxx>
<mailto:aodvv2-discuss@xxxxxxxxxxxxx>
Hello folks,
As promised, here is a definition:
> AODVv2_INTERFACES: the set of all network interfaces supporting AODVv2
In order to be more pleasing to more people, Section 4.1 should be revised:
> A list of the AODVv2 router's interfaces that support AODVv2 MUST
> be configured in the
> AODVv2_INTERFACES list.
Regards,
Charlie P.
