Hi all
So having checked one more time with Stan and Rick as to their understanding of
the outcome of this afternoons meeting (because on closer examination I was
unsure), the MUST statement should remain, but also the additional text Charlie
submits is also valid with the SHOULD translated to MUST, so the text was
The IAR MUST respond to
RREQ on behalf of all Internet destinations, i.e., destinations not
on the configured 191.0.2.0/24 <http://191.0.2.0/24> subnet.
The IAR MUST respond to RREQ on behalf of all Internet destinations,
i.e., destinations not on the configured 191.0.2.0/24
<http://191.0.2.0/24> subnet. The IAR
MUST be configured so that it does not respond to RREQ for addresses
within the AODVv2 manet (here, 191.0.2.0/24 <http://191.0.2.0/24>).
On 21 Jul 2015, at 17:10, John Dowdell <john.dowdell486@xxxxxxxxx> wrote:
Charlie et al
Sounds good. There is a timely reminder on the meeting list about IP
addresses reserved for documentation (and therefore may not be routable), so
should we call up the RFC that does this reservation?
RFC5737 I believe, which states that the address block Charlie mentions below
is allocated to documentation purposes.
Regards
John
On 21 Jul 2015, at 16:14, Stan Ratliff <ratliffstan@xxxxxxxxx
<mailto:ratliffstan@xxxxxxxxx>> wrote:
---------- Forwarded message ----------
From: FreeLists Mailing List Manager <ecartis@xxxxxxxxxxxxx
<mailto:ecartis@xxxxxxxxxxxxx>>
Date: Tue, Jul 21, 2015 at 9:53 AM
Subject: aodvv2-discuss: charliep51@xxxxxxxxxxxxx
<mailto:charliep51@xxxxxxxxxxxxx> post needs approval
To: aodvv2-discuss-moderators@xxxxxxxxxxxxx
<mailto:aodvv2-discuss-moderators@xxxxxxxxxxxxx>
This message was received for a list you are a moderator on, and
was marked for moderation due to the following reason:
Non-member submission to closed-post list.
To approve this message and have it go out on the list, forward this to
aodvv2-discuss-repost@xxxxxxxxxxxxx
<mailto:aodvv2-discuss-repost@xxxxxxxxxxxxx>
If you wish to decline the post, change the 'apppost' below to 'delpost'.
If you wish to edit the post, change it to 'modpost' and edit the message
as needed - not all mail programs will work with modpost.
DO NOT DELETE THE FOLLOWING LINE. Ecartis needs it.
// apppost 55AE4EC7:19B8.1:nbqiiqvfphff
From charliep51@xxxxxxxxxxxxx <mailto:charliep51@xxxxxxxxxxxxx> Tue Jul 21
09:53:11 2015
Return-Path: <charliep51@xxxxxxxxxxxxx <mailto:charliep51@xxxxxxxxxxxxx>>
X-Original-To: aodvv2-discuss@xxxxxxxxxxxxx
<mailto:aodvv2-discuss@xxxxxxxxxxxxx>
Delivered-To: aodvv2-discuss@xxxxxxxxxxxxx
<mailto:aodvv2-discuss@xxxxxxxxxxxxx>
Received: from localhost (localhost [127.0.0.1])
by turing.freelists.org <//turing.freelists.org/> (Avenir
Technologies Mail Multiplex) with ESMTP id 747D62D056
for <aodvv2-discuss@xxxxxxxxxxxxx
<mailto:aodvv2-discuss@xxxxxxxxxxxxx>>; Tue, 21 Jul 2015 09:53:11 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at turing.freelists.org
<//turing.freelists.org/>
Received: from turing.freelists.org <//turing.freelists.org/>
([127.0.0.1])
by localhost (turing.freelists.org <//turing.freelists.org/>
[127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id DnDO4wgp6pjv for <aodvv2-discuss@xxxxxxxxxxxxx
<mailto:aodvv2-discuss@xxxxxxxxxxxxx>>;
Tue, 21 Jul 2015 09:53:11 -0400 (EDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net
<http://elasmtp-kukur.atl.sa.earthlink.net/>
(elasmtp-kukur.atl.sa.earthlink.net
<http://elasmtp-kukur.atl.sa.earthlink.net/> [209.86.89.65])
by turing.freelists.org <//turing.freelists.org/> (Avenir
Technologies Mail Multiplex) with ESMTP id 47CA32D044
for <aodvv2-discuss@xxxxxxxxxxxxx
<mailto:aodvv2-discuss@xxxxxxxxxxxxx>>; Tue, 21 Jul 2015 09:53:10 -0400 (EDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=dk20050327; d=earthlink.net <http://earthlink.net/>;
b=FtftppFi+5R+eHWPtMgar2/FKuzm0I1PZVNfsG2fiyGXOxJ+20IHFWfmMRETJVnZ;
h=Received:To:From:Subject:Message-ID:Date:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [31.133.163.161]
by elasmtp-kukur.atl.sa.earthlink.net
<http://elasmtp-kukur.atl.sa.earthlink.net/> with esmtpsa
(TLSv1:AES128-SHA:128)
(Exim 4.67)
(envelope-from <charliep51@xxxxxxxxxxxxx
<mailto:charliep51@xxxxxxxxxxxxx>>)
id 1ZHXyo-0005YJ-FZ
for aodvv2-discuss@xxxxxxxxxxxxx
<mailto:aodvv2-discuss@xxxxxxxxxxxxx>; Tue, 21 Jul 2015 09:53:10 -0400
To: "aodvv2-discuss@xxxxxxxxxxxxx <mailto:aodvv2-discuss@xxxxxxxxxxxxx>"
<aodvv2-discuss@xxxxxxxxxxxxx <mailto:aodvv2-discuss@xxxxxxxxxxxxx>>
From: Charlie Perkins <charliep51@xxxxxxxxxxxxx
<mailto:charliep51@xxxxxxxxxxxxx>>
Subject: Statement for IAR restriction
Message-ID: <55AE4EC4.5000604@xxxxxxxxxxxxx
<mailto:55AE4EC4.5000604@xxxxxxxxxxxxx>>
Date: Tue, 21 Jul 2015 06:53:08 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace:
5a185a306015b1a28a306fc704168558239a348a220c26090d67e853cbc57c73092cd273c56215e5a7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 31.133.163.161
Hello folks,
The existing sentence:
The IAR MUST respond to
RREQ on behalf of all Internet destinations, i.e., destinations not
on the configured 191.0.2.0/24 <http://191.0.2.0/24> subnet.
The replacement:
The IAR SHOULD respond to RREQ on behalf of all Internet destinations,
i.e., destinations not on the configured 191.0.2.0/24
<http://191.0.2.0/24> subnet. The IAR
SHOULD be configured so that it does not respond to RREQ for addresses
within the AODVv2 manet (here, 191.0.2.0/24 <http://191.0.2.0/24>).
Regards,
Charlie P.
// eompost 55AE4EC7:19B8.1:nbqiiqvfphff
