Hello folks,
I think the change in terminology is fine, either way.
Will the new draft be out today?
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>
<mailto: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.
