
From nobody Tue Sep  2 08:23:49 2014
Return-Path: <robert.g.cole.civ@mail.mil>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 398091A0798 for <manet@ietfa.amsl.com>; Tue,  2 Sep 2014 08:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.669
X-Spam-Level: 
X-Spam-Status: No, score=-0.669 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xxfd4m07ztPr for <manet@ietfa.amsl.com>; Tue,  2 Sep 2014 08:23:44 -0700 (PDT)
Received: from upbd19pa14.eemsg.mail.mil (upbd19pa14.eemsg.mail.mil [214.24.27.89]) by ietfa.amsl.com (Postfix) with ESMTP id 8E21E1A0977 for <manet@ietf.org>; Tue,  2 Sep 2014 08:23:43 -0700 (PDT)
Received: from edge-cols02.mail.mil ([131.64.104.103]) by upbd19pa14.eemsg.mail.mil with ESMTP; 02 Sep 2014 15:23:41 +0000
Received: from UCOLHPMO.easf.csd.disa.mil (131.64.104.43) by edge-cols02.mail.mil (131.64.104.103) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 2 Sep 2014 15:23:40 +0000
Received: from UCOLHPKT.easf.csd.disa.mil ([169.254.2.144]) by ucolhpmo.easf.csd.disa.mil ([131.64.104.43]) with mapi id 14.03.0174.001; Tue, 2 Sep 2014 15:23:38 +0000
From: "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil>
To: manet <manet@ietf.org>
Thread-Topic: REPORT-MIB --- update? (UNCLASSIFIED)
Thread-Index: Ac/GwchpuXI+pWCbQ4iCar1Du+toWw==
Date: Tue, 2 Sep 2014 15:23:05 +0000
Message-ID: <B9468E58D6A0A84AAD66FE4E694BEABB753AA46D@ucolhpkt.easf.csd.disa.mil>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [131.64.22.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/GQOjQSrapcRs0t1Opk6RvaLrKbk
Cc: "Macker, Joseph P CIV \(US\)" <joseph.macker@nrl.navy.mil>, Andy Bierman <andy@yumaworks.com>
Subject: [manet] REPORT-MIB --- update? (UNCLASSIFIED)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2014 15:23:47 -0000

Classification: UNCLASSIFIED
Caveats: NONE

To all:

I did not want to comment on the questions regarding the status of the REPO=
RT-MIB definition until I had pretty much wrapped up the SMF-MIB (which I b=
elieve is close to publication).

With the permission of the working group and the chairs, I would like to pr=
oceed with the design and development of the REPORT-MIB?

The hold up over the last year has been the appropriate architecture for th=
e REPORT-MIB.  It was initially designed following RMON II tables.  Last ye=
ar Andy suggested (based upon conversations with others involved with the D=
ISMAN WG years ago) that we should base the REPORT-MIB on the DISMAN base o=
f MIBs.  I believe I now know how to accomplish this and I would like to re=
write the report-mib-04 within the context of the DISMAN MIBs, e.g., EVENT-=
MIB, EXPRESSION-MIB, etc.

So if this is OK with the group, I need a few weeks to work up the 04 versi=
on of the REPORT-MIB draft and post by the end of September.

Thanks, Bob


US Army CERDEC
QUEST Program, S&TCD
APG, MD

(c) 443.910.4420
(o) 443.395.8744
robert.g.cole@us.army.mil



Classification: UNCLASSIFIED
Caveats: NONE



From nobody Tue Sep  2 09:19:04 2014
Return-Path: <comcom_osn_special@iit.cnr.it>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F9211A04D2 for <manet@ietfa.amsl.com>; Tue,  2 Sep 2014 09:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.022
X-Spam-Level: **
X-Spam-Status: No, score=2.022 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.668, T_FROM_MISSP_DKIM=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnLNYgy4n1nm for <manet@ietfa.amsl.com>; Tue,  2 Sep 2014 09:19:00 -0700 (PDT)
Received: from mxbk.iit.cnr.it (mxbk.iit.cnr.it [146.48.98.159]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 961BF1A0311 for <manet@ietf.org>; Tue,  2 Sep 2014 09:18:58 -0700 (PDT)
Received: from turig.iit.cnr.it (turig.iit.cnr.it [146.48.98.70]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxbk.iit.cnr.it (Postfix) with ESMTPSA id 2BB38C09C6 for <manet@ietf.org>; Tue,  2 Sep 2014 18:18:56 +0200 (CEST)
Date: Tue, 02 Sep 2014 18:34:01 +0200
From: Valerio Arnaboldi<comcom_osn_special@iit.cnr.it>
To: manet@ietf.org
Message-ID: <5405f179.Koxiz66svJlgIb66%comcom_osn_special@iit.cnr.it>
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/mXh5gfd44qpJpC5FRSLcr6gsOPA
Subject: [manet] Elsevier ComCom Special Issue on Online Social Networks
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2014 16:19:02 -0000

CALL FOR PAPERS

Elsevier - Computer Communications Journal
Special Issue on
Online Social Networks
http://www.journals.elsevier.com/computer-communications/call-for-papers/special-issue-on-online-social-networks1/

Submission Deadline: 19 October 2014	 

Online Social Networks are a massively successful phenomenon, used by
billions of users to interact. Nowadays they are key platforms for,
among others, content dissemination, social and professional networking,
recommendation, scouting, alerting, and political campaigns. The
research interest in OSNs is multi-faceted, and exploits an unmatched
source of large-scale data about the human behavior. It spans a number
of disciplines, across numerous fields in and beyond computer science,
all the way up to the analysis of human social relationships and how
they evolve and mature over time. Moreover, the pervasive presence of
users' mobile devices (e.g., smartphones) has opened new avenues in the
design of mobile social networking services, and in the study of the
interplay between mobility and social interactions. Research in OSN is a
fertile ground also for industry, to develop innovative ideas fostering
the design of the new generation of communication platforms and their
services.

This special issue seeks contributions pushing the state of the art in
all facets of Online Social Networks highlighted above. We also
encourage original work based on an interdisciplinary research (at the
boundary between computer science and humanistic disciplines such as
sociology and anthropology) where quantitative evidence is available
demonstrating the mutual advantage of such an approach. Therefore,
purely methodological papers or papers that do not present quantitative
results with real Online or Mobile Social Networking technologies are
considered out of scope. Moreover, special attention is expected in
interpreting the proposed research results in order to shed light
towards what users may need and wish in terms of novel, practical
services and application.

Topics of interest include (but are not limited to) the following:
- Design of OSN platforms based on human behavioural models
- Analysis of OSN users' behaviour and its evolution over time
- Comparison of human social behaviour in Online and "offline" Social
Networks, and across OSNs
- Impact of Online Social Networks on human social behaviour
- Analysis of the use of social-networking sites in the urban context
- OSNs for supporting novel, social-oriented applications and services
- Mobile and Location-aware Online Social Networks
- OSN services enabled by the analysis of mobility and social behaviour
- Crowdsourcing for Online and Mobile Social Networks
- Dynamics of trends, information and opinion diffusion in OSN
- Smart recommendations and advertising in Online Social Networks
- Information extraction and search in Online Social Networks
- Privacy in management and analysis of Online and Mobile Social
Networks data
- Privacy, Security, Trust and Reputation in Online Social Networks
- Prevention of misbehaviours (spamming, phishing, ...) in Online Social
Networks
- Modelling of Online Social Networks characteristics and mechanisms
- Graph analysis applied to Online Social Networks
- Complex networks techniques applied to the investigation of OSN
- Data Mining and Machine Learning to gain novel insights on Online
Social Networks
- Novel distributed solutions for designing, supporting and operating
Online Social Networks
- Networking, computation and data infrastructure support for Online
Social Network systems


Schedule
Submission deadline: 19 October 2014
Author notification: 31 January 2015
Revised paper due: 15 March 2015
Final author notification: 15 April 2015
Publication (tentative): 3rd Quarter 2015

Guest Editors
Xiaoming Fu, Georg-August-University of Goettingen, Germany
Andrea Passarella, IIT-CNR, Italy
Daniele Quercia, Yahoo Labs, Spain
Alessandra Sala, Bell Labs, Ireland
Thorsten Strufe, TU Dresden, Germany

Instructions for submission
---------------------------
Manuscripts must not have been previously published nor currently under
review by other journals or conferences. If prior work was published in
a conference, the submitted manuscript should include a substantial
extension of at least 35% novel contributions. In this case, authors are
also required to submit their published conference articles and a
summary document explaining the enhancements made in the journal
version.

Papers must be submitted through the Computer Communications website at
http://ees.elsevier.com/comcom, where guidelines for manuscript
preparation can also be found
(http://www.elsevier.com/journals/computer-communications/0140-3664/guide-for-authors).
To ensure that all manuscripts are correctly identified for consideration
by the Special Issue, the authors should select "Special Issue: OSN"
when they reach the "Article Type" step in the submission process. 

For further information, please contact the guest editors at
comcomsi_osn at iit.cnr.it


From nobody Wed Sep  3 01:16:35 2014
Return-Path: <ulrich@herberg.name>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 631E11A8705 for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 01:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UYmc_9KvB8XT for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 01:16:29 -0700 (PDT)
Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3A9C1A8719 for <manet@ietf.org>; Wed,  3 Sep 2014 01:15:06 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id la4so8516380vcb.29 for <manet@ietf.org>; Wed, 03 Sep 2014 01:15:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=H3NzZnzUY2jw2x3N7H1DjI4cB1OY081NrWDS+x7thUk=; b=UKeXOJZZp8Ye0YyQ2MrfAM873t6VTvhPZGUthvUuPmM2Zj3sT29AsnTJdswblfypNE /RWuqUi7Znv7crGBkkqkG4gAxtvYBHiRNaLZm7nRdUflwh+2wAtafmxZ1pFrNXf8i/xq K/iA24aZBZR0QwjyTzIkAzvV8t4R3OnTbn81Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=H3NzZnzUY2jw2x3N7H1DjI4cB1OY081NrWDS+x7thUk=; b=PF6CSEGvvwi6pXgQNDa34Z09D0O5sC08yZDB4zPcYabO/LfdX+/P27WJpxz1wxsFRP FlxdFsIwGaS4jgIGDXa4kptOKcYW/ViqgVmIJkd1y0+w3NAskj3SJUkhyRozA40En1Rh UIBNhIQJ2pa4PKDcJ0yniSRjMaC37Fmx7Sr6mxgNYIgmsrz1E5PZ+NIe/YUzBtiSjEmO tOsyhHrFZ9hUBAhBjOdXSUz9u9pPfy5w1AaMxFmtsY5RZ6YT/5khEhO+ZNFXmh8qACRU JOFTDDqP19anKbc5RvaqliaRD+Dh/Yek+VfD73UZSbzsUj9zTwK/zeGFCeZusLk6HiLW wRZw==
X-Gm-Message-State: ALoCoQnKt61Q4BdWSpRkKDnmifcP4TgQqseJ8xEDExcH3rKQo47GNtfaBARwb9XTgYShMvV92C4m
MIME-Version: 1.0
X-Received: by 10.52.138.210 with SMTP id qs18mr8719037vdb.18.1409732105854; Wed, 03 Sep 2014 01:15:05 -0700 (PDT)
Received: by 10.220.70.196 with HTTP; Wed, 3 Sep 2014 01:15:05 -0700 (PDT)
In-Reply-To: <B9468E58D6A0A84AAD66FE4E694BEABB753AA46D@ucolhpkt.easf.csd.disa.mil>
References: <B9468E58D6A0A84AAD66FE4E694BEABB753AA46D@ucolhpkt.easf.csd.disa.mil>
Date: Wed, 3 Sep 2014 10:15:05 +0200
Message-ID: <CAK=bVC8nUQ+PUcKC3zjg07B_8O9VrB4AiwcdEburhZDXK=6a+g@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/8VYOrQPRkMxSUjh75kMTNaXlxKI
Cc: manet <manet@ietf.org>, "Macker, Joseph P CIV \(US\)" <joseph.macker@nrl.navy.mil>, Andy Bierman <andy@yumaworks.com>
Subject: Re: [manet] REPORT-MIB --- update? (UNCLASSIFIED)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 08:16:31 -0000

Hi Bob,

sounds good to me. Please proceed.

Best regards
Ulrich

On Tue, Sep 2, 2014 at 5:23 PM, Cole, Robert G CIV USARMY CERDEC (US)
<robert.g.cole.civ@mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> To all:
>
> I did not want to comment on the questions regarding the status of the RE=
PORT-MIB definition until I had pretty much wrapped up the SMF-MIB (which I=
 believe is close to publication).
>
> With the permission of the working group and the chairs, I would like to =
proceed with the design and development of the REPORT-MIB?
>
> The hold up over the last year has been the appropriate architecture for =
the REPORT-MIB.  It was initially designed following RMON II tables.  Last =
year Andy suggested (based upon conversations with others involved with the=
 DISMAN WG years ago) that we should base the REPORT-MIB on the DISMAN base=
 of MIBs.  I believe I now know how to accomplish this and I would like to =
rewrite the report-mib-04 within the context of the DISMAN MIBs, e.g., EVEN=
T-MIB, EXPRESSION-MIB, etc.
>
> So if this is OK with the group, I need a few weeks to work up the 04 ver=
sion of the REPORT-MIB draft and post by the end of September.
>
> Thanks, Bob
>
>
> US Army CERDEC
> QUEST Program, S&TCD
> APG, MD
>
> (c) 443.910.4420
> (o) 443.395.8744
> robert.g.cole@us.army.mil
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Wed Sep  3 06:43:03 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6458C1A0302 for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 06:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UAcii2eLdyer for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 06:42:59 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D9251A02FC for <manet@ietf.org>; Wed,  3 Sep 2014 06:42:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id CF2161BC6F4B; Wed,  3 Sep 2014 06:42:58 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 5939B1BC6F3B; Wed,  3 Sep 2014 06:42:56 -0700 (PDT)
From: Thomas Clausen <thomas@thomasclausen.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <D144571D-7902-473C-AF8B-C51570A5774E@thomasclausen.org>
Date: Wed, 3 Sep 2014 15:42:54 +0200
To: manet IETF <manet@ietf.org>, draft-ietf-manet-ibs@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/CsPoJB2vbGjg0dkOjwaZQi0hR5Q
Subject: [manet] IPR question on draft-ietf-manet-ibs for shepherd writeup
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 13:43:00 -0000

I have been assigned as document shepherd for draft-ietf-manet-ibs, and =
am in the process of producing my review and document write-up.

As part of the document shepherd writeup, confirmation is sought by the =
shepherd  regarding IPR:

	o	Can each author of the document confirm that any and all =
IPR disclosures have been filed, according to BCP 78 and 79?

The write-up is ready otherwise, and will be posted as soon as the above =
question has been clarified and a final review completed.

Respectfully,

Thomas=


From nobody Wed Sep  3 08:02:57 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B11EE1A701A for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 08:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.868
X-Spam-Level: 
X-Spam-Status: No, score=-4.868 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DT70PRNNNzVH for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 08:02:53 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7CDB1A8735 for <manet@ietf.org>; Wed,  3 Sep 2014 08:01:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.04,457,1406588400"; d="scan'208";a="400310619"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 03 Sep 2014 16:01:49 +0100
X-IronPort-AV: E=Sophos;i="5.04,457,1406588400"; d="scan'208";a="71645837"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasodc005.greenlnk.net with ESMTP; 03 Sep 2014 16:01:49 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.140]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0174.001; Wed, 3 Sep 2014 16:01:49 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Thomas Clausen <thomas@thomasclausen.org>, manet IETF <manet@ietf.org>, "draft-ietf-manet-ibs@tools.ietf.org" <draft-ietf-manet-ibs@tools.ietf.org>
Thread-Topic: [manet] IPR question on draft-ietf-manet-ibs for shepherd writeup
Thread-Index: AQHPx3z/BCouFnXiIEu4jwetqDOLRJvve9HA
Date: Wed, 3 Sep 2014 15:01:49 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D32F2F@GLKXM0002V.GREENLNK.net>
References: <D144571D-7902-473C-AF8B-C51570A5774E@thomasclausen.org>
In-Reply-To: <D144571D-7902-473C-AF8B-C51570A5774E@thomasclausen.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/kZWuK_6xP-4UJvC69zAChY-lImY
Subject: Re: [manet] IPR question on draft-ietf-manet-ibs for shepherd writeup
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 15:02:55 -0000

I am not aware of any IPR held by BAE Systems that covers this document.

There may or may not be applicable IPR through this document's use of RFC 6=
507. This is not IPR that is covered by sections 6.1.1 or 6.1.2 of BCP 79 a=
s applied to me. I make no statement of any form as to the existence or val=
idity of any such IPR claims.

-- =

Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Thomas Clausen
Sent: 03 September 2014 14:43
To: manet IETF; draft-ietf-manet-ibs@tools.ietf.org
Subject: [manet] IPR question on draft-ietf-manet-ibs for shepherd writeup

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

I have been assigned as document shepherd for draft-ietf-manet-ibs, and am =
in the process of producing my review and document write-up.

As part of the document shepherd writeup, confirmation is sought by the she=
pherd  regarding IPR:

	o	Can each author of the document confirm that any and all IPR disclosures=
 have been filed, according to BCP 78 and 79?

The write-up is ready otherwise, and will be posted as soon as the above qu=
estion has been clarified and a final review completed.

Respectfully,

Thomas
_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet

********************************************************************
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.
********************************************************************


From nobody Wed Sep  3 08:12:21 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F1A61A03C2 for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 08:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVvozHgGq1Sa for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 08:12:17 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED4AA1A877D for <manet@ietf.org>; Wed,  3 Sep 2014 08:05:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 72B4B1BC6FFD; Wed,  3 Sep 2014 08:05:33 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id C2C731BC6FF3; Wed,  3 Sep 2014 08:05:31 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Thomas Clausen <thomas@thomasclausen.org>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D32F2F@GLKXM0002V.GREENLNK.net>
Date: Wed, 3 Sep 2014 17:05:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B94787A0-A7B3-4417-820F-E4147D9F2D8B@thomasclausen.org>
References: <D144571D-7902-473C-AF8B-C51570A5774E@thomasclausen.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D32F2F@GLKXM0002V.GREENLNK.net>
To: Christopher Dearlove <chris.dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/4WVxw2QF9w8nT57BK1np_eY72sY
Cc: "draft-ietf-manet-ibs@tools.ietf.org" <draft-ietf-manet-ibs@tools.ietf.org>, manet IETF <manet@ietf.org>
Subject: Re: [manet] IPR question on draft-ietf-manet-ibs for shepherd writeup
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 15:12:19 -0000

Thank you, this is quite sufficient.

On Sep 3, 2014, at 17:01, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:

> I am not aware of any IPR held by BAE Systems that covers this =
document.
>=20
> There may or may not be applicable IPR through this document's use of =
RFC 6507. This is not IPR that is covered by sections 6.1.1 or 6.1.2 of =
BCP 79 as applied to me. I make no statement of any form as to the =
existence or validity of any such IPR claims.
>=20
> --=20
> Christopher Dearlove
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>=20
>=20
> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Thomas =
Clausen
> Sent: 03 September 2014 14:43
> To: manet IETF; draft-ietf-manet-ibs@tools.ietf.org
> Subject: [manet] IPR question on draft-ietf-manet-ibs for shepherd =
writeup
>=20
> ----------------------! WARNING ! ---------------------- This message =
originates from outside our organisation, either from an external =
partner or from the internet.
> Consider carefully whether you should click on any links, open any =
attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for =
instructions on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> I have been assigned as document shepherd for draft-ietf-manet-ibs, =
and am in the process of producing my review and document write-up.
>=20
> As part of the document shepherd writeup, confirmation is sought by =
the shepherd  regarding IPR:
>=20
> 	o	Can each author of the document confirm that any and all =
IPR disclosures have been filed, according to BCP 78 and 79?
>=20
> The write-up is ready otherwise, and will be posted as soon as the =
above question has been clarified and a final review completed.
>=20
> Respectfully,
>=20
> Thomas
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>=20
> ********************************************************************
> 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.
> ********************************************************************
>=20


From nobody Wed Sep  3 10:40:39 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07A5A1A03A3 for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 10:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLgEDeOPpTdp for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 10:40:36 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9572B1A0394 for <manet@ietf.org>; Wed,  3 Sep 2014 10:40:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 67C8C1BC70A6; Wed,  3 Sep 2014 10:40:36 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 44D5C1BC7091; Wed,  3 Sep 2014 10:40:33 -0700 (PDT)
From: Thomas Clausen <thomas@thomasclausen.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Sep 2014 19:40:30 +0200
Message-Id: <BC28F83B-EFD8-4720-BF4F-76099B93F866@thomasclausen.org>
To: Joe Macker <joseph.macker@nrl.navy.mil>, Stan Ratliff <sratliff@cisco.com>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/6GJqzyarhSaO5oRZ4kRw4z_Pb6E
Cc: "<manet-chairs@tools.ietf.org>" <manet-chairs@tools.ietf.org>, manet IETF <manet@ietf.org>
Subject: [manet] Request to Designated Experts for IANA registrations made in draft-ietf-manet-ibs
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 17:40:38 -0000

Note: this email is directed to the Designated Experts, and is copied to =
the MANET WG mailing list, and other recipients =93for information only=94=
 =97 this is not a consensus call ;)

Dear Designated Experts for =
http://www.iana.org/assignments/manet-parameters/manet-parameters.xhtml#cr=
yptographic-algorithm

I am the document shepherd for draft-ietf-manet-ibs, which has been WG =
Last Called in the MANET working group.

That document requests registrations from the registry  =
http://www.iana.org/assignments/manet-parameters/manet-parameters.xhtml#cr=
yptographic-algorithm, for which the registration procedure is =93Expert =
Review=94 and where you are indicated as the Designated Experts.

This registry is created by [RFC7182], with Expert Review Guidelines =
given in https://tools.ietf.org/html/rfc7182#section-13.1 =97 which =
suggests a few additional considerations, and then points to =
http://tools.ietf.org/html/rfc5444#section-6.1 for further Expert Review =
Guidelines.

Would the Designated Experts be so kind as to let me know if you agree, =
or not, to the assignments made in draft-ietf-manet-ibs ?

Thank you in advance,

Thomas=


From nobody Wed Sep  3 12:18:21 2014
Return-Path: <joseph.macker@nrl.navy.mil>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 623041A6EF5 for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 12:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.868
X-Spam-Level: 
X-Spam-Status: No, score=-4.868 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hr2ksfdvpEAK for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 12:18:17 -0700 (PDT)
Received: from ccs.nrl.navy.mil (mx0.ccs.nrl.navy.mil [132.250.118.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 956771A0B7E for <manet@ietf.org>; Wed,  3 Sep 2014 12:18:17 -0700 (PDT)
Received: from m22jm.itd.nrl.navy.mil (m22jm.itd.nrl.navy.mil [132.250.92.50]) by ccs.nrl.navy.mil (8.14.4/8.14.4) with ESMTP id s83JIADE012983 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 3 Sep 2014 15:18:11 -0400
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Joe Macker <joseph.macker@nrl.navy.mil>
In-Reply-To: <BC28F83B-EFD8-4720-BF4F-76099B93F866@thomasclausen.org>
Date: Wed, 3 Sep 2014 15:18:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C18CE56C-77E0-454F-9F17-ED2CC215E620@nrl.navy.mil>
References: <BC28F83B-EFD8-4720-BF4F-76099B93F866@thomasclausen.org>
To: Thomas Clausen <thomas@thomasclausen.org>, "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1878.6)
X-CCS-MailScanner: No viruses found.
X-CCS-MailScanner-Info: See: http://www.nrl.navy.mil/ccs/support/email
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/om4YpucIK3D5wVYaNUZ_ObhxvoI
Cc: "<manet-chairs@tools.ietf.org>" <manet-chairs@tools.ietf.org>, manet IETF <manet@ietf.org>, Stan Ratliff <sratliff@cisco.com>
Subject: Re: [manet] Request to Designated Experts for IANA registrations made in draft-ietf-manet-ibs
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 19:18:19 -0000

Upon review, I feel the assignments proposed are agreeable.

-Joe
On Sep 3, 2014, at 1:40 PM, Thomas Clausen <thomas@thomasclausen.org> =
wrote:

> Note: this email is directed to the Designated Experts, and is copied =
to the MANET WG mailing list, and other recipients =93for information =
only=94 =97 this is not a consensus call ;)
>=20
> Dear Designated Experts for =
http://www.iana.org/assignments/manet-parameters/manet-parameters.xhtml#cr=
yptographic-algorithm
>=20
> I am the document shepherd for draft-ietf-manet-ibs, which has been WG =
Last Called in the MANET working group.
>=20
> That document requests registrations from the registry  =
http://www.iana.org/assignments/manet-parameters/manet-parameters.xhtml#cr=
yptographic-algorithm, for which the registration procedure is =93Expert =
Review=94 and where you are indicated as the Designated Experts.
>=20
> This registry is created by [RFC7182], with Expert Review Guidelines =
given in https://tools.ietf.org/html/rfc7182#section-13.1 =97 which =
suggests a few additional considerations, and then points to =
http://tools.ietf.org/html/rfc5444#section-6.1 for further Expert Review =
Guidelines.
>=20
> Would the Designated Experts be so kind as to let me know if you =
agree, or not, to the assignments made in draft-ietf-manet-ibs ?
>=20
> Thank you in advance,
>=20
> Thomas


From nobody Wed Sep  3 12:20:13 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73C0F1A6F0E for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 12:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JONLtAUuOOKE for <manet@ietfa.amsl.com>; Wed,  3 Sep 2014 12:20:07 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9BE21A6F06 for <manet@ietf.org>; Wed,  3 Sep 2014 12:20:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id AFDD81BC7139; Wed,  3 Sep 2014 12:20:06 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 0F2EA1BC7133; Wed,  3 Sep 2014 12:20:06 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (11D257)
In-Reply-To: <C18CE56C-77E0-454F-9F17-ED2CC215E620@nrl.navy.mil>
Date: Wed, 3 Sep 2014 21:20:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <70C920EE-4DEE-42A7-AB9C-7171495E51B1@thomasclausen.org>
References: <BC28F83B-EFD8-4720-BF4F-76099B93F866@thomasclausen.org> <C18CE56C-77E0-454F-9F17-ED2CC215E620@nrl.navy.mil>
To: Joe Macker <joseph.macker@nrl.navy.mil>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/1cbajemYlBFoYsfoXZT-Hn9TOQk
Cc: "<manet-chairs@tools.ietf.org>" <manet-chairs@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <Chris.Dearlove@baesystems.com>, manet IETF <manet@ietf.org>, Stan Ratliff <sratliff@cisco.com>
Subject: Re: [manet] Request to Designated Experts for IANA registrations made in draft-ietf-manet-ibs
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 19:20:10 -0000

Thank you, Joe, I will record so in the shepherd write-up.

Thomas


Sent from my iPad

> On 03 Sep 2014, at 21:18, Joe Macker <joseph.macker@nrl.navy.mil> wrote:
>=20
> Upon review, I feel the assignments proposed are agreeable.
>=20
> -Joe
>> On Sep 3, 2014, at 1:40 PM, Thomas Clausen <thomas@thomasclausen.org> wro=
te:
>>=20
>> Note: this email is directed to the Designated Experts, and is copied to t=
he MANET WG mailing list, and other recipients =E2=80=9Cfor information only=
=E2=80=9D =E2=80=94 this is not a consensus call ;)
>>=20
>> Dear Designated Experts for http://www.iana.org/assignments/manet-paramet=
ers/manet-parameters.xhtml#cryptographic-algorithm
>>=20
>> I am the document shepherd for draft-ietf-manet-ibs, which has been WG La=
st Called in the MANET working group.
>>=20
>> That document requests registrations from the registry  http://www.iana.o=
rg/assignments/manet-parameters/manet-parameters.xhtml#cryptographic-algorit=
hm, for which the registration procedure is =E2=80=9CExpert Review=E2=80=9D a=
nd where you are indicated as the Designated Experts.
>>=20
>> This registry is created by [RFC7182], with Expert Review Guidelines give=
n in https://tools.ietf.org/html/rfc7182#section-13.1 =E2=80=94 which sugges=
ts a few additional considerations, and then points to http://tools.ietf.org=
/html/rfc5444#section-6.1 for further Expert Review Guidelines.
>>=20
>> Would the Designated Experts be so kind as to let me know if you agree, o=
r not, to the assignments made in draft-ietf-manet-ibs ?
>>=20
>> Thank you in advance,
>>=20
>> Thomas
>=20


From nobody Thu Sep  4 06:43:06 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8684B1A88BF for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 06:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gK8h359CiLuK for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 06:43:03 -0700 (PDT)
Received: from mailb1.tigertech.net (mailb1.tigertech.net [208.80.4.153]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5114B1A88BE for <manet@ietf.org>; Thu,  4 Sep 2014 06:43:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb1.tigertech.net (Postfix) with ESMTP id 26349D40CED; Thu,  4 Sep 2014 06:43:03 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at mailb1.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb1.tigertech.net (Postfix) with ESMTPSA id 3C296D407A8; Thu,  4 Sep 2014 06:43:00 -0700 (PDT)
From: Thomas Clausen <thomas@thomasclausen.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE74605E-65D0-47E0-A8A2-4A45FB602B5A@thomasclausen.org>
Date: Thu, 4 Sep 2014 15:42:57 +0200
To: manet IETF <manet@ietf.org>, draft-ietf-manet-ibs@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/_lPWFSqfuZRsYycKdV1T0iL9yyo
Subject: [manet] Document Shepherd Review fixes for draft-ietf-manet-ibs-02
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 13:43:04 -0000

Dear All,

As part of the Document Shepherd review, I have identified the following =
nits that I would like to request be fixed in a new revision, prior to =
recommending it for IESG evaluation.=20

Note:
	o	these issues are all editorial =93nits=94=20
	o	none are of technical or protocol significance

But in order to make AD and IESG processing as smooth as possible, I =
would like to see these issues fixed before the Publication Request is =
made.

Nits:

	1)	Ulrich Herberg and Jiazi Yi=92s reviews pointed out, =
during WGLC, a few typo=92s and punctuation issues, that should be =
folded in:
			=
http://www.ietf.org/mail-archive/web/manet/current/msg16790.html
			=
http://www.ietf.org/mail-archive/web/manet/current/msg16789.html
		Note that the discussion in that thread indicates =
agreement on most, but not all, of the suggestions.

	2)	There is an IANA registry naming error

		OLD:
			IANA has, in accordance with [RFC7182], defined =
a registry
		        "Cryptographic Functions" under "Mobile Ad Hoc =
NETwork Functions".
			IANA is requested to make two new allocations =
from this registry, and
			modify the unassigned range, as indicated.

		NEW:
			IANA has, in accordance with [RFC7182], defined =
a registry
		        "Cryptographic Functions" under "Mobile Ad Hoc =
NETwork Parameters".
			IANA is requested to make two new allocations =
from this registry, and
			modify the unassigned range, as indicated.

	3)	The abstract contains [=85] references =97 IDNITS =
complains about that, stating
		that one shall not use citations in an abstract but =
plain name document references
		(i.e. RFC7182, and not [RFC7182]).

	4)	If the AD advice that =93Updates 7182=94 is the right =
approach, then the abstract needs
		to state this, as well as the document header =97 =
currently, the document header=20
		states this, but the abstract does not.

It should be an easy fix, and once a -03 hits the repositories, I will =
verify it against -02 and send out the Shepherd Writeup.

Respectfully,

Thomas


From nobody Thu Sep  4 06:58:32 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9E41A88E2; Thu,  4 Sep 2014 06:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Opgee54ap_jF; Thu,  4 Sep 2014 06:58:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B3BCF1A88DA; Thu,  4 Sep 2014 06:58:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140904135819.7323.26150.idtracker@ietfa.amsl.com>
Date: Thu, 04 Sep 2014 06:58:19 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/8WvE0iMdHQIbENLuK03WBTx2Edo
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-ibs-03.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 13:58:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

        Title           : Identity-Based Signatures for MANET Routing Protocols
        Author          : Christopher Dearlove
	Filename        : draft-ietf-manet-ibs-03.txt
	Pages           : 16
	Date            : 2014-09-04

Abstract:
   This document updates RFC7182, which specifies a framework for, and
   specific examples of, integrity check values (ICVs) for packets and
   messages using the generalized packet/message format specified in
   RFC5444.  It does so by defining an additional cryptographic function
   that allows the creation of an ICV that is an identity-based
   signature, defined according to the ECCSI (Elliptic Curve-Based
   Certificateless Signatures for Identity-Based Encryption) algorithm
   specified in RFC6507.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-ibs/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-manet-ibs-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-ibs-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Sep  4 07:00:41 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20ECF1A0338 for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 07:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.568
X-Spam-Level: 
X-Spam-Status: No, score=-7.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p8VTwEPI25p0 for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 07:00:35 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B68C21A88AD for <manet@ietf.org>; Thu,  4 Sep 2014 07:00:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.04,466,1406588400"; d="scan'208";a="474097803"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 04 Sep 2014 15:00:23 +0100
X-IronPort-AV: E=Sophos;i="5.04,466,1406588400"; d="scan'208";a="64094265"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 04 Sep 2014 15:00:23 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.140]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0174.001; Thu, 4 Sep 2014 15:00:23 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Thomas Clausen <thomas@thomasclausen.org>, manet IETF <manet@ietf.org>, "draft-ietf-manet-ibs@tools.ietf.org" <draft-ietf-manet-ibs@tools.ietf.org>
Thread-Topic: [manet] Document Shepherd Review fixes for draft-ietf-manet-ibs-02
Thread-Index: AQHPyEY3RxezSVihz0ieRAL1lH+vvJvw/x7Q
Date: Thu, 4 Sep 2014 14:00:21 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3447F@GLKXM0002V.GREENLNK.net>
References: <CE74605E-65D0-47E0-A8A2-4A45FB602B5A@thomasclausen.org>
In-Reply-To: <CE74605E-65D0-47E0-A8A2-4A45FB602B5A@thomasclausen.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/EinQtVx1L3HlUHCXIgvdDXsOAgc
Subject: Re: [manet] Document Shepherd Review fixes for draft-ietf-manet-ibs-02
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 14:00:39 -0000

I have submitted a -03 that addresses all of these points. (I actually had =
a version I thought I'd already posted but hadn't that did point 1.)

Thanks to Thomas for catching 2 and 3.

Point 4 I've adopted a least effort approach of a word change in abstract. =
I can live either way, I just don't feel like changing and then potentially=
 having to change back.

-- =

Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Thomas Clausen
Sent: 04 September 2014 14:43
To: manet IETF; draft-ietf-manet-ibs@tools.ietf.org
Subject: [manet] Document Shepherd Review fixes for draft-ietf-manet-ibs-02

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

Dear All,

As part of the Document Shepherd review, I have identified the following ni=
ts that I would like to request be fixed in a new revision, prior to recomm=
ending it for IESG evaluation. =


Note:
	o	these issues are all editorial "nits" =

	o	none are of technical or protocol significance

But in order to make AD and IESG processing as smooth as possible, I would =
like to see these issues fixed before the Publication Request is made.

Nits:

	1)	Ulrich Herberg and Jiazi Yi's reviews pointed out, during WGLC, a few t=
ypo's and punctuation issues, that should be folded in:
			http://www.ietf.org/mail-archive/web/manet/current/msg16790.html
			http://www.ietf.org/mail-archive/web/manet/current/msg16789.html
		Note that the discussion in that thread indicates agreement on most, but =
not all, of the suggestions.

	2)	There is an IANA registry naming error

		OLD:
			IANA has, in accordance with [RFC7182], defined a registry
		        "Cryptographic Functions" under "Mobile Ad Hoc NETwork Functions".
			IANA is requested to make two new allocations from this registry, and
			modify the unassigned range, as indicated.

		NEW:
			IANA has, in accordance with [RFC7182], defined a registry
		        "Cryptographic Functions" under "Mobile Ad Hoc NETwork Parameters=
".
			IANA is requested to make two new allocations from this registry, and
			modify the unassigned range, as indicated.

	3)	The abstract contains [.] references - IDNITS complains about that, sta=
ting
		that one shall not use citations in an abstract but plain name document r=
eferences
		(i.e. RFC7182, and not [RFC7182]).

	4)	If the AD advice that "Updates 7182" is the right approach, then the ab=
stract needs
		to state this, as well as the document header - currently, the document h=
eader =

		states this, but the abstract does not.

It should be an easy fix, and once a -03 hits the repositories, I will veri=
fy it against -02 and send out the Shepherd Writeup.

Respectfully,

Thomas

_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet

********************************************************************
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.
********************************************************************


From nobody Thu Sep  4 07:01:50 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E1631A88BF for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 07:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vpdaXoGojGXz for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 07:01:42 -0700 (PDT)
Received: from mailb1.tigertech.net (mailb1.tigertech.net [208.80.4.153]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C17741A0338 for <manet@ietf.org>; Thu,  4 Sep 2014 07:01:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb1.tigertech.net (Postfix) with ESMTP id 7C1C6D45615; Thu,  4 Sep 2014 07:01:41 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at mailb1.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb1.tigertech.net (Postfix) with ESMTPSA id 5C067D40CED; Thu,  4 Sep 2014 07:01:38 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Thomas Clausen <thomas@thomasclausen.org>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3447F@GLKXM0002V.GREENLNK.net>
Date: Thu, 4 Sep 2014 16:01:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7123166F-FEB7-4786-86F8-4A4B706D7C1C@thomasclausen.org>
References: <CE74605E-65D0-47E0-A8A2-4A45FB602B5A@thomasclausen.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3447F@GLKXM0002V.GREENLNK.net>
To: Christopher Dearlove <chris.dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/D1RCwi8fqYAM4VKm-JYSyy6e8Xk
Cc: "draft-ietf-manet-ibs@tools.ietf.org" <draft-ietf-manet-ibs@tools.ietf.org>, manet IETF <manet@ietf.org>
Subject: Re: [manet] Document Shepherd Review fixes for draft-ietf-manet-ibs-02
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 14:01:48 -0000

Chris,

Thank you for being so reactive. I will do a final check.

Thomas

On Sep 4, 2014, at 16:00, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:

> I have submitted a -03 that addresses all of these points. (I actually =
had a version I thought I'd already posted but hadn't that did point 1.)
>=20
> Thanks to Thomas for catching 2 and 3.
>=20
> Point 4 I've adopted a least effort approach of a word change in =
abstract. I can live either way, I just don't feel like changing and =
then potentially having to change back.
>=20
> --=20
> Christopher Dearlove
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>=20
> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Thomas =
Clausen
> Sent: 04 September 2014 14:43
> To: manet IETF; draft-ietf-manet-ibs@tools.ietf.org
> Subject: [manet] Document Shepherd Review fixes for =
draft-ietf-manet-ibs-02
>=20
> ----------------------! WARNING ! ---------------------- This message =
originates from outside our organisation, either from an external =
partner or from the internet.
> Consider carefully whether you should click on any links, open any =
attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for =
instructions on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> Dear All,
>=20
> As part of the Document Shepherd review, I have identified the =
following nits that I would like to request be fixed in a new revision, =
prior to recommending it for IESG evaluation.=20
>=20
> Note:
> 	o	these issues are all editorial "nits"=20
> 	o	none are of technical or protocol significance
>=20
> But in order to make AD and IESG processing as smooth as possible, I =
would like to see these issues fixed before the Publication Request is =
made.
>=20
> Nits:
>=20
> 	1)	Ulrich Herberg and Jiazi Yi's reviews pointed out, =
during WGLC, a few typo's and punctuation issues, that should be folded =
in:
> 			=
http://www.ietf.org/mail-archive/web/manet/current/msg16790.html
> 			=
http://www.ietf.org/mail-archive/web/manet/current/msg16789.html
> 		Note that the discussion in that thread indicates =
agreement on most, but not all, of the suggestions.
>=20
> 	2)	There is an IANA registry naming error
>=20
> 		OLD:
> 			IANA has, in accordance with [RFC7182], defined =
a registry
> 		        "Cryptographic Functions" under "Mobile Ad Hoc =
NETwork Functions".
> 			IANA is requested to make two new allocations =
from this registry, and
> 			modify the unassigned range, as indicated.
>=20
> 		NEW:
> 			IANA has, in accordance with [RFC7182], defined =
a registry
> 		        "Cryptographic Functions" under "Mobile Ad Hoc =
NETwork Parameters".
> 			IANA is requested to make two new allocations =
from this registry, and
> 			modify the unassigned range, as indicated.
>=20
> 	3)	The abstract contains [.] references - IDNITS complains =
about that, stating
> 		that one shall not use citations in an abstract but =
plain name document references
> 		(i.e. RFC7182, and not [RFC7182]).
>=20
> 	4)	If the AD advice that "Updates 7182" is the right =
approach, then the abstract needs
> 		to state this, as well as the document header - =
currently, the document header=20
> 		states this, but the abstract does not.
>=20
> It should be an easy fix, and once a -03 hits the repositories, I will =
verify it against -02 and send out the Shepherd Writeup.
>=20
> Respectfully,
>=20
> Thomas
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>=20
> ********************************************************************
> 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.
> ********************************************************************
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep  4 07:14:50 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B708B1A88D6 for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 07:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-MTTic5bGxY for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 07:14:44 -0700 (PDT)
Received: from mailb1.tigertech.net (mailb1.tigertech.net [208.80.4.153]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66FF01A88CB for <manet@ietf.org>; Thu,  4 Sep 2014 07:14:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb1.tigertech.net (Postfix) with ESMTP id 17E1BD556CD; Thu,  4 Sep 2014 07:14:44 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at mailb1.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb1.tigertech.net (Postfix) with ESMTPSA id C63E2D407A8; Thu,  4 Sep 2014 07:14:39 -0700 (PDT)
From: Thomas Clausen <thomas@thomasclausen.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3532D7DB-146D-4D08-A64D-7BB22D217522"
Message-Id: <FD76C330-A7EB-4281-A784-14C27C0374F8@thomasclausen.org>
Date: Thu, 4 Sep 2014 16:14:36 +0200
To: manet IETF <manet@ietf.org>, "<manet-chairs@tools.ietf.org>" <manet-chairs@tools.ietf.org>, draft-ietf-manet-ibs@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/st5BGkgj3Or6ZuiCiTt5-GoeOQI
Subject: [manet] Document Shepherd Write-Up for draft-ietf-manet-ibs
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 14:14:47 -0000

--Apple-Mail=_3532D7DB-146D-4D08-A64D-7BB22D217522
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Dear All,

First, thank you Chris for being responsive to review comments, and =
spinning a new version so quickly.=20

This allows me to post the document shepherd review. I believe that =
inserting the write-up in the tracker, and proceeding to request =
publication befalls on the WG chairs/secretary:

	I hereby respectfully request that publication be requested for =
this document.

Respectfully,

Thomas

=3D=3D=3D

Document Shepherd Write-Up for draft-ietf-manet-ibs-03

(1) What type of RFC is being requested (BCP, Proposed Standard, =
Internet Standard, Informational, Experimental, or Historic)? Why is =
this the proper type of RFC? Is this type of RFC indicated in the title =
page header?

     The intended status is =93Proposed Standard=94,=20
     and this is indicated in the title page header.
(2) The IESG approval announcement includes a Document Announcement =
Write-Up. Please provide such a Document Announcement Write-Up. Recent =
examples can be found in the "Action" announcements for approved =
documents. The approval announcement contains the following sections:

Technical Summary:

     This document builds on RFC7182 and RFC6507, and
     provides a framework for using Identity-Based
     Signatures in MANET routing protocols.

Working Group Summary:

     The document was presented at the WG meeting at=20
     IETF=9290, and had reasonable discussion both before
     and after this meeting. There were significant=20
     expression of support for adoption as WG document,
     a couple of reviews posted after adoption, which were
     addressed. On the author=92s initiative, external
     verification of the example provided in Appendix A
     was sought from a crypto-expert.

     WGLC saw positive support for publication, with=20
     nobody appearing to be =93in the rough"

Document Quality:
Are there existing implementations of the protocol? Have a significant =
number of vendors indicated their plan to implement the specification? =
Are there any reviewers that merit special mention as having done a =
thorough review, e.g., one that resulted in important changes or a =
conclusion that the document had no substantive issues? If there was a =
MIB Doctor, Media Type or other expert review, what was its course =
(briefly)? In the case of a Media Type review, on what date was the =
request posted?

     There are existing implementations of this extension=20
     mechanism, known to the document shepherd.=20

     Dr. Benjamin Smith provided independent verification=20
     of the example provided in Appendix A, and is=20
     recognized for this in the acknowledgements.

     No media type, nor MIB doctor, review done, as this
     was not needed

Personnel:

Who is the Document Shepherd? Who is the Responsible Area Director?

     The document shepherd is:
          Thomas Clausen

     The responsible Area Director is:
          Adrian Farrell


(3) Briefly describe the review of this document that was performed by =
the Document Shepherd. If this version of the document is not ready for =
publication, please explain why the document is being forwarded to the =
IESG.

     The document shepherd performed a total of five
     reviews of this document, during WG processing:

     1) Initially, prior to WG adoption

     2) Extensively, following WG adoption, providing        =20
        substantial comments

     3) Extensively, following the author addressed the=20
        review comments from 2), to satisfaction

     4) Extensively, once WGLC was terminated, considering
        WGLC comments received, which resulted in a=20
        document revision (-03) fixing nits, format=20
        issues, and a reference issue.

     5) Finally, a review of the -03 version

     The document shepherd estimates, that the -03 version
     of the document is technically identical to the -02
     version which was WGLCed.

     The document shepherd believes, that the -03 version
     of the document is ready for being forwarded to the
     IESG.

(4) Does the document Shepherd have any concerns about the depth or =
breadth of the reviews that have been performed?

     The document shepherd is satisfied that sufficient
     reviews have been performed.

(5) Do portions of the document need review from a particular or from =
broader perspective, e.g., security, operational complexity, AAA, DNS, =
DHCP, XML, or internationalization? If so, describe the review that took =
place.

     This document addresses security, within the=20
     framework set forth in RFC7182, and uses RFC6507
     for the cryptographic functions. Both RFC7182 and
     RFC6507 has received extensive scrutiny from the=20
     security community.

     As such, the document shepherd believes that the
     habitual SEC-DIR review for standards track documents
     is expected =97 but that no additional reviews are
     necessary, nor beneficial.

(6) Describe any specific concerns or issues that the Document Shepherd =
has with this document that the Responsible Area Director and/or the =
IESG should be aware of? For example, perhaps he or she is uncomfortable =
with certain parts of the document, or has concerns whether there really =
is a need for it. In any event, if the WG has discussed those issues and =
has indicated that it still wishes to advance the document, detail those =
concerns here.

     The document shepherd raised, in his review,
     (http://www.ietf.org/mail-archive/web/manet/current/msg16728.html)
     the question of if =93Updates RFC7182=94 is appropriate.

     The document author and the document shepherd both
     are =93on the balance=94 as to if it is, or is not

     Both parties, however, believe that either way is=20
     tolerable, and agreed to seek advice from the=20
     responsible AD on this particular matter
     (http://www.ietf.org/mail-archive/web/manet/current/msg16728.html)

     The argument for =93is not appropriate=94 goes like this:

          What this document does is:
               (i)  only things permissible by RFC7182, and=20
               (ii) makes registration from IANA registries=20
                    set up by RFC7182
                    (noting, of course, that RFC7181 doesn=92t=20
                     =93Updates 5444=94 when making registrations=20
                     for TC messages from the repositories
                     set up by RFC5444 as a case of precedent)

     The argument for =93is appropriate=94 is, that the=20
     way this document interprets <key-id> might not=20
     be as is described in RFC7182.

(7) Has each author confirmed that any and all appropriate IPR =
disclosures required for full conformance with the provisions of BCP 78 =
and BCP 79 have already been filed. If not, explain why?

     The author has confirmed to not be aware of any
     IPR that requires disclosure regarding this specific
     documents.

(8) Has an IPR disclosure been filed that references this document? If =
so, summarize any WG discussion and conclusion regarding the IPR =
disclosures.

     There have been no IPR disclosures filed that
     reference this document.

(9) How solid is the WG consensus behind this document? Does it =
represent the strong concurrence of a few individuals, with others being =
silent, or does the WG as a whole understand and agree with it?

     As described under Working Group Summary, the
     consensus behind this document appears quite solid.

(10) Has anyone threatened an appeal or otherwise indicated extreme =
discontent? If so, please summarise the areas of conflict in separate =
email messages to the Responsible Area Director. (It should be in a =
separate email because this questionnaire is publicly available.)

     There have been no threats of appeal raised, nor
     has any extreme discontent been indicated.

(11) Identify any ID nits the Document Shepherd has found in this =
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts =
Checklist). Boilerplate checks are not enough; this check needs to be =
thorough.

     IDNITS raises only concerns on a DOWNREF, addressed
     in 15) below.

(12) Describe how the document meets any required formal review =
criteria, such as the MIB Doctor, media type, and URI type reviews.

     Such reviews are not required for this document.

(13) Have all references within this document been identified as either =
normative or informative?

     Yes.
(14) Are there normative references to documents that are not ready for =
advancement or are otherwise in an unclear state? If such normative =
references exist, what is the plan for their completion?

     No.

(15) Are there downward normative references references (see RFC 3967)? =
If so, list these downward references to support the Area Director in =
the Last Call procedure.

     This document, intended for publication on std.=20
     track, has a downref to RFC6507, which is published=20
     as informational.=20

     RFC6507 does not appear in the downrefergistry
     (http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry)
     and must thus be explicitly called out in the=20
     IETF Last Call.

(16) Will publication of this document change the status of any existing =
RFCs? Are those RFCs listed on the title page header, listed in the =
abstract, and discussed in the introduction? If the RFCs are not listed =
in the Abstract and Introduction, explain why, and point to the part of =
the document where the relationship of this document to the other RFCs =
is discussed. If this information is not in the document, explain why =
the WG considers it unnecessary.=20

     Advice from the responsible AD is sought on if=20
     this document =93Updates RFC7182=94, or not, as=20
     previously indicated.=20

     If, on the responsible ADs advice, this document
     updates RFC7182, then this is called out in the
     appropriate places.

(17) Describe the Document Shepherd's review of the IANA considerations =
section, especially with regard to its consistency with the body of the =
document. Confirm that all protocol extensions that the document makes =
are associated with the appropriate reservations in IANA registries. =
Confirm that any referenced IANA registries have been clearly =
identified. Confirm that newly created IANA registries include a =
detailed specification of the initial contents for the registry, that =
allocations procedures for future registrations are defined, and a =
reasonable name for the new registry has been suggested (see RFC 5226).

     All protocol extensions that the document makes, are
     associated with the appropriate reservations

     Referenced IANA registries have been clearly=20
     identified

     No new IANA registries are created

     The designated expert for the registry confirmed on
     14/09/03 that he finds the registrations
     requested in this document as aggreable:

     http://www.ietf.org/mail-archive/web/manet/current/msg16912.html

(18) List any new IANA registries that require Expert Review for future =
allocations. Provide any public guidance that the IESG would find useful =
in selecting the IANA Experts for these new registries.

     No new IANA registries are created.

(19) Describe reviews and automated checks performed by the Document =
Shepherd to validate sections of the document written in a formal =
language, such as XML code, BNF rules, MIB definitions, etc.=20

     No such checks required nor performed: no XML code,=20
     BNF rules, MIB definitions, or other formal language=20
     for which automatic checks exist, is included in this=20
     document.



--Apple-Mail=_3532D7DB-146D-4D08-A64D-7BB22D217522
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Dear =
All,<div><br></div><div>First, thank you Chris for being responsive to =
review comments, and spinning a new version so =
quickly.&nbsp;</div><div><br></div><div>This allows me to post the =
document shepherd review. I believe that inserting the write-up in the =
tracker, and proceeding to request publication befalls on the WG =
chairs/secretary:</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><u><b>I hereby respectfully =
request that publication be requested for this =
document.</b></u></div><div><br></div><div>Respectfully,</div><div><br></d=
iv><div>Thomas</div><div><br></div><div>=3D=3D=3D</div><div><!--?xml =
version=3D"1.0" encoding=3D"UTF-8" standalone=3D"no"?-->

<div style=3D"font-family: Arial; font-size: medium;"><font face=3D"Andale=
 Mono"><br class=3D"Apple-interchange-newline"><span style=3D"font-size: =
12px;">Document Shepherd Write-Up for =
draft-ietf-manet-ibs-03</span></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">(1) What type =
of RFC is being requested (BCP, Proposed Standard, Internet Standard, =
Informational, Experimental, or Historic)? Why is this the proper type =
of RFC? Is this type of RFC indicated in the title page =
header?</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The intended =
status is&nbsp;=93Proposed Standard=94,&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;and this is indicated in the title page header.</font></div><p =
style=3D"font-family: Arial; background-color: rgb(255, 255, =
255);"><font face=3D"Andale Mono">(2) The IESG approval announcement =
includes a Document Announcement Write-Up. Please provide such a =
Document Announcement Write-Up. Recent examples can be found in the =
"Action" announcements for approved documents. The approval announcement =
contains the following sections:</font></p><p style=3D"font-family: =
Arial; background-color: rgb(255, 255, 255);"><font face=3D"Andale =
Mono">Technical Summary:</font></p><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;This document =
builds on RFC7182 and RFC6507, and</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;provides a =
framework for using Identity-Based</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;Signatures in =
MANET routing protocols.</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">Working Group =
Summary:<br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The document was =
presented at the WG meeting at&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;IETF=9290, and had reasonable discussion both =
before</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale=
 Mono">&nbsp; &nbsp; &nbsp;and after this meeting. There were =
significant&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;expression of support for =
adoption as WG document,</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;a couple of =
reviews posted after adoption, which were</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;addressed. On the author=92s initiative, external</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;verification of the example provided in Appendix =
A</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono">&nbsp; &nbsp; &nbsp;was&nbsp;sought from a =
crypto-expert.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;WGLC saw positive =
support for publication, with&nbsp;</font></div><div style=3D"font-family:=
 Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;nobody&nbsp;appearing to be&nbsp;=93in the rough"</font></div><div =
style=3D"font-family: Arial;"><span style=3D"background-color: rgb(255, =
255, 255);"><font face=3D"Andale Mono"><br></font></span></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono"><span =
style=3D"background-color: rgb(255, 255, 255);">Document =
Quality:</span><br></font></div><p style=3D"font-family: Arial; =
background-color: rgb(255, 255, 255);"><font face=3D"Andale Mono">Are =
there existing implementations of the protocol? Have a significant =
number of vendors indicated their plan to implement the specification? =
Are there any reviewers that merit special mention as having done a =
thorough review, e.g., one that resulted in important changes or a =
conclusion that the document had no substantive issues? If there was a =
MIB Doctor, Media Type or other expert review, what was its course =
(briefly)? In the case of a Media Type review, on what date was the =
request posted?</font></p><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;There are existing =
implementations of this extension&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;mechanism, known to the document shepherd.&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;Dr. Benjamin Smith provided =
independent verification&nbsp;</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;of the example =
provided in Appendix A, and is&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;recognized for this in the acknowledgements.</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;No media type, nor MIB doctor, =
review done, as this</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;was not =
needed</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale=
 Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">Personnel:</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">Who is the =
Document Shepherd? Who is the Responsible Area =
Director?</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The document =
shepherd is:</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Thomas =
Clausen</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The responsible =
Area Director is:</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Adrian =
Farrell</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">(3) Briefly =
describe the review of this document that was performed by the Document =
Shepherd. If this version of the document is not ready for publication, =
please explain why the document is being forwarded to the =
IESG.</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The document shepherd performed =
a total of five</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;reviews of this document, =
during WG processing:</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;1) Initially, prior to WG adoption</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;2) Extensively, following WG =
adoption, providing &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp; &nbsp; substantial comments</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;3) Extensively, following the author addressed =
the&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; review comments from =
2), to satisfaction</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;4) Extensively, =
once WGLC was terminated, considering</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp; &nbsp; WGLC comments received, which resulted in =
a&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; document revision (-03) =
fixing nits, format&nbsp;</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; =
issues,&nbsp;and a reference issue.</font></div><div style=3D"font-family:=
 Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;5) Finally, a review of the -03 version</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The document shepherd =
estimates, that the -03 version</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;of the document =
is technically identical to the -02</font></div><div style=3D"font-family:=
 Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;version which =
was WGLCed.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The document =
shepherd believes, that the&nbsp;-03 version</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;of the document is ready for being forwarded to =
the</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono">&nbsp; &nbsp; &nbsp;IESG.</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">(4) Does the =
document Shepherd have any concerns about the depth or breadth of the =
reviews that have been performed?</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;The document shepherd is satisfied that =
sufficient</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;reviews have been =
performed.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">(5) Do portions of the document need =
review from a particular or from broader perspective, e.g., security, =
operational complexity, AAA, DNS, DHCP, XML, or internationalization? If =
so, describe the review that took place.</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;This document =
addresses&nbsp;security, within the&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;framework set forth in RFC7182, and =
uses&nbsp;RFC6507</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;for the cryptographic =
functions. Both RFC7182 and</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;RFC6507 has =
received extensive scrutiny from the&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;security community.</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;As such, the document shepherd believes that the</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;habitual SEC-DIR review for standards track =
documents</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;is expected&nbsp;=97 but that =
no additional reviews are</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;necessary, nor =
beneficial.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">(6) Describe any specific concerns or =
issues that the Document Shepherd has with this document that the =
Responsible Area Director and/or the IESG should be aware of? For =
example, perhaps he or she is uncomfortable with certain parts of the =
document, or has concerns whether there really is a need for it. In any =
event, if the WG has discussed those issues and has indicated that it =
still wishes to advance the document, detail those concerns =
here.</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The document shepherd raised, =
in his review,</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;(<a =
href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16728.html">=
http://www.ietf.org/mail-archive/web/manet/current/msg16728.html</a>)</fon=
t></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono">&nbsp; &nbsp; &nbsp;the question of if&nbsp;=93Updates RFC7182=94 =
is appropriate.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The document =
author and the document shepherd both</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;are&nbsp;=93on the balance=94 as to if it is, or is =
not</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><div><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;Both parties, however, believe =
that either way is&nbsp;<br></font></div><div><font face=3D"Andale =
Mono">&nbsp; &nbsp; &nbsp;tolerable, and agreed to seek advice from =
the&nbsp;</font></div><div><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;responsible AD on this particular matter</font></div><div><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;(<a =
href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16728.html">=
http://www.ietf.org/mail-archive/web/manet/current/msg16728.html</a>)</fon=
t></div></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The argument for&nbsp;=93is not =
appropriate=94 goes like this:</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><div><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; What this document does =
is:</font></div><div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(i)&nbsp; only things permissible by =
RFC7182, and&nbsp;</font></div><div><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ii) makes registration =
from IANA registries&nbsp;</font></div><div><font face=3D"Andale =
Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; set up by RFC7182</font></div><div><font face=3D"Andale =
Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; (noting, of course, that RFC7181 =
doesn=92t&nbsp;</font></div><div><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=93Updates 5444=94&nbsp;when making =
registrations&nbsp;</font></div><div><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;for =
TC messages from the repositories</font></div><div><font face=3D"Andale =
Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;set up by RFC5444 as a case of =
precedent)</font></div><div><font face=3D"Andale =
Mono"><br></font></div><div><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;The argument for&nbsp;=93is appropriate=94 is, that =
the&nbsp;</font></div><div><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;way this document interprets&nbsp;&lt;key-id&gt; might =
not&nbsp;</font></div><div><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;be as is described in RFC7182.</font></div></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">(7) Has each author confirmed that any and all =
appropriate IPR disclosures required for full conformance with the =
provisions of BCP 78 and BCP 79 have already been filed. If not, explain =
why?</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The author has confirmed to not =
be aware of any</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;IPR that requires disclosure =
regarding this specific</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;documents.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><p style=3D"font-family: Arial; =
background-color: rgb(255, 255, 255);"><font face=3D"Andale Mono">(8) =
Has an IPR disclosure been filed that references this document? If so, =
summarize any WG discussion and conclusion regarding the IPR =
disclosures.</font></p><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;There have been no IPR =
disclosures filed that</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;reference this =
document.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">(9) How solid is the WG consensus =
behind this document? Does it represent the strong concurrence of a few =
individuals, with others being silent, or does the WG as a whole =
understand and agree with it?</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;As described under Working Group Summary, the</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;consensus behind this document appears quite =
solid.</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale=
 Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">(10) Has anyone threatened an appeal or otherwise =
indicated extreme discontent? If so, please summarise the areas of =
conflict in separate email messages to the Responsible Area Director. =
(It should be in a separate email because this questionnaire is publicly =
available.)</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;There have been =
no threats of appeal raised, nor</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;has any extreme =
discontent been indicated.</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">(11) Identify =
any ID nits the Document Shepherd has found in this document. =
(See&nbsp;<a =
href=3D"http://www.ietf.org/tools/idnits/">http://www.ietf.org/tools/idnit=
s/</a>&nbsp;and the Internet-Drafts Checklist). Boilerplate checks are =
not enough; this check needs to be thorough.</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;IDNITS raises only concerns on =
a DOWNREF, addressed</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;in 15) =
below.</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale=
 Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">(12) Describe how the document meets any required =
formal review criteria, such as the MIB Doctor, media type, and URI type =
reviews.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;Such reviews are =
not required for this document.</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">(13) Have all =
references within this document been identified as either normative or =
informative?</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;Yes.</font></div><p style=3D"font-family: Arial; background-color: =
rgb(255, 255, 255);"><font face=3D"Andale Mono">(14) Are there normative =
references to documents that are not ready for advancement or are =
otherwise in an unclear state? If such normative references exist, what =
is the plan for their completion?</font></p><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;No.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">(15) Are there downward normative =
references references (see RFC 3967)? If so, list these downward =
references to support the Area Director in the Last Call =
procedure.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;This document, =
intended for publication on std.&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;track, has a&nbsp;downref to RFC6507, which is =
published&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;as =
informational.&nbsp;</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;RFC6507 does not appear in the downrefergistry</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;(<a =
href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry">h=
ttp://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry</a>)</font>=
</div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono">&nbsp; &nbsp; &nbsp;and must thus be explicitly called out in =
the&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;IETF Last =
Call.</font></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">(16) Will publication of this document change the =
status of any existing RFCs? Are those RFCs listed on the title page =
header, listed in the abstract, and discussed in the introduction? If =
the RFCs are not listed in the Abstract and Introduction, explain why, =
and point to the part of the document where the relationship of this =
document to the other RFCs is discussed. If this information is not in =
the document, explain why the WG considers it =
unnecessary.&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;Advice from =
the&nbsp;responsible AD is sought on if&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;this document&nbsp;=93Updates RFC7182=94, or not, =
as&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;previously =
indicated.&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;If, on the =
responsible ADs&nbsp;advice, this document</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;updates RFC7182, then this is called out in the</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;appropriate places.</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">(17) Describe =
the Document Shepherd's review of the IANA considerations section, =
especially with regard to its consistency with the body of the document. =
Confirm that all protocol extensions that the document makes are =
associated with the appropriate reservations in IANA registries. Confirm =
that any referenced IANA registries have been clearly identified. =
Confirm that newly created IANA registries include a detailed =
specification of the initial contents for the registry, that allocations =
procedures for future registrations are defined, and a reasonable name =
for the new registry has been suggested (see RFC 5226).</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;All protocol extensions that =
the document makes, are</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;associated with =
the appropriate reservations</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;Referenced IANA registries have been =
clearly&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;identified</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;No new IANA registries are =
created</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The designated =
expert for the registry confirmed on</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;14/09/03 that he finds the registrations</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;requested in this document as aggreable:</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;<a =
href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16912.html">=
http://www.ietf.org/mail-archive/web/manet/current/msg16912.html</a></font=
></div><div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">(18) List any new IANA registries that require =
Expert Review for future allocations. Provide any public guidance that =
the IESG would find useful in selecting the IANA Experts for these new =
registries.</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono"><br></font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;No new IANA =
registries are created.</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono"><br></font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">(19) Describe =
reviews and automated checks performed by the Document Shepherd to =
validate sections of the document written in a formal language, such as =
XML code, BNF rules, MIB definitions, etc.&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;No such checks&nbsp;required =
nor performed: no XML code,&nbsp;</font></div><div style=3D"font-family: =
Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;BNF rules, MIB =
definitions, or other formal language&nbsp;</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp; =
&nbsp;for which automatic checks exist, is included in =
this&nbsp;</font></div><div style=3D"font-family: Arial;"><font =
face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;document.</font></div><div =
style=3D"font-family: Arial;"><font face=3D"Andale =
Mono"><br></font></div><div style=3D"font-family: Arial; font-size: =
medium;"><font face=3D"Andale =
Mono"><br></font></div></div></body></html>=

--Apple-Mail=_3532D7DB-146D-4D08-A64D-7BB22D217522--



From nobody Thu Sep  4 08:43:01 2014
Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3341A034A for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 08:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.168
X-Spam-Level: 
X-Spam-Status: No, score=-15.168 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJRfMF6xr1xm for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 08:42:55 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2B51A0255 for <manet@ietf.org>; Thu,  4 Sep 2014 08:42:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=44998; q=dns/txt; s=iport; t=1409845375; x=1411054975; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=R6cDpwk6yPYB+QrAfXfVMb+WYHCUQIdKg9wu0nh5BOc=; b=lCLM1rdxUW3Tz+BN6uvQa52+O921yQQDDsvHWCgjWqcOWj0j0lKkCUa5 73a+9z9Y2r+vyDy7AxPe4f2Aja+SNk006eqp47G+O0mRhfJBHNmDiRpPs 8W0PYoCDupeoqHlH+JVt/noFk9nBweR1OxnfFweZ3HlKlqg9yf1KPd5Dv Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlcFAN+HCFStJA2F/2dsb2JhbABPAQmCR0ZTVwTGP4Fph0wBgQUWd4QEAQEEDgwTOAYHBxACAQg4AQYHMhQRAgQOBQkLiC4NvQYBF41HgSQGAQkCAU8GAYMvgR0FjymCFYQwhn6BW5NHg2FsAYEHJByBBwEBAQ
X-IronPort-AV: E=Sophos; i="5.04,466,1406592000"; d="scan'208,217"; a="74952791"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-3.cisco.com with ESMTP; 04 Sep 2014 15:42:54 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s84FgrDk019487 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 4 Sep 2014 15:42:53 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Thu, 4 Sep 2014 10:42:53 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Thomas Clausen <thomas@thomasclausen.org>
Thread-Topic: Document Shepherd Write-Up for draft-ietf-manet-ibs
Thread-Index: AQHPyEqdXAoeHBwh90u27xmDMzmyg5vxcQIA
Date: Thu, 4 Sep 2014 15:42:53 +0000
Message-ID: <EC6E48C5-9207-4955-B526-390A8C913590@cisco.com>
References: <FD76C330-A7EB-4281-A784-14C27C0374F8@thomasclausen.org>
In-Reply-To: <FD76C330-A7EB-4281-A784-14C27C0374F8@thomasclausen.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.102.40.190]
Content-Type: multipart/alternative; boundary="_000_EC6E48C592074955B526390A8C913590ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/LXQvP3onItkQ3vhDvBaM7kPrkAw
Cc: "<manet-chairs@tools.ietf.org>" <manet-chairs@tools.ietf.org>, "<draft-ietf-manet-ibs@tools.ietf.org>" <draft-ietf-manet-ibs@tools.ietf.org>, manet IETF <manet@ietf.org>
Subject: Re: [manet] Document Shepherd Write-Up for draft-ietf-manet-ibs
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 15:42:59 -0000

--_000_EC6E48C592074955B526390A8C913590ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Thomas,

I've put your shepherd's writeup into the data tracker for the draft, and h=
ave requested IESG publication. Thank you for volunteering to be the docume=
nt shepherd on this.

Regards,
Stan


On Sep 4, 2014, at 10:14 AM, Thomas Clausen <thomas@thomasclausen.org<mailt=
o:thomas@thomasclausen.org>> wrote:

Dear All,

First, thank you Chris for being responsive to review comments, and spinnin=
g a new version so quickly.

This allows me to post the document shepherd review. I believe that inserti=
ng the write-up in the tracker, and proceeding to request publication befal=
ls on the WG chairs/secretary:

I hereby respectfully request that publication be requested for this docume=
nt.

Respectfully,

Thomas

=3D=3D=3D

Document Shepherd Write-Up for draft-ietf-manet-ibs-03

(1) What type of RFC is being requested (BCP, Proposed Standard, Internet S=
tandard, Informational, Experimental, or Historic)? Why is this the proper =
type of RFC? Is this type of RFC indicated in the title page header?

     The intended status is =93Proposed Standard=94,
     and this is indicated in the title page header.

(2) The IESG approval announcement includes a Document Announcement Write-U=
p. Please provide such a Document Announcement Write-Up. Recent examples ca=
n be found in the "Action" announcements for approved documents. The approv=
al announcement contains the following sections:

Technical Summary:

     This document builds on RFC7182 and RFC6507, and
     provides a framework for using Identity-Based
     Signatures in MANET routing protocols.

Working Group Summary:

     The document was presented at the WG meeting at
     IETF=9290, and had reasonable discussion both before
     and after this meeting. There were significant
     expression of support for adoption as WG document,
     a couple of reviews posted after adoption, which were
     addressed. On the author=92s initiative, external
     verification of the example provided in Appendix A
     was sought from a crypto-expert.

     WGLC saw positive support for publication, with
     nobody appearing to be =93in the rough"

Document Quality:

Are there existing implementations of the protocol? Have a significant numb=
er of vendors indicated their plan to implement the specification? Are ther=
e any reviewers that merit special mention as having done a thorough review=
, e.g., one that resulted in important changes or a conclusion that the doc=
ument had no substantive issues? If there was a MIB Doctor, Media Type or o=
ther expert review, what was its course (briefly)? In the case of a Media T=
ype review, on what date was the request posted?

     There are existing implementations of this extension
     mechanism, known to the document shepherd.

     Dr. Benjamin Smith provided independent verification
     of the example provided in Appendix A, and is
     recognized for this in the acknowledgements.

     No media type, nor MIB doctor, review done, as this
     was not needed

Personnel:

Who is the Document Shepherd? Who is the Responsible Area Director?

     The document shepherd is:
          Thomas Clausen

     The responsible Area Director is:
          Adrian Farrell


(3) Briefly describe the review of this document that was performed by the =
Document Shepherd. If this version of the document is not ready for publica=
tion, please explain why the document is being forwarded to the IESG.

     The document shepherd performed a total of five
     reviews of this document, during WG processing:

     1) Initially, prior to WG adoption

     2) Extensively, following WG adoption, providing
        substantial comments

     3) Extensively, following the author addressed the
        review comments from 2), to satisfaction

     4) Extensively, once WGLC was terminated, considering
        WGLC comments received, which resulted in a
        document revision (-03) fixing nits, format
        issues, and a reference issue.

     5) Finally, a review of the -03 version

     The document shepherd estimates, that the -03 version
     of the document is technically identical to the -02
     version which was WGLCed.

     The document shepherd believes, that the -03 version
     of the document is ready for being forwarded to the
     IESG.

(4) Does the document Shepherd have any concerns about the depth or breadth=
 of the reviews that have been performed?

     The document shepherd is satisfied that sufficient
     reviews have been performed.

(5) Do portions of the document need review from a particular or from broad=
er perspective, e.g., security, operational complexity, AAA, DNS, DHCP, XML=
, or internationalization? If so, describe the review that took place.

     This document addresses security, within the
     framework set forth in RFC7182, and uses RFC6507
     for the cryptographic functions. Both RFC7182 and
     RFC6507 has received extensive scrutiny from the
     security community.

     As such, the document shepherd believes that the
     habitual SEC-DIR review for standards track documents
     is expected =97 but that no additional reviews are
     necessary, nor beneficial.

(6) Describe any specific concerns or issues that the Document Shepherd has=
 with this document that the Responsible Area Director and/or the IESG shou=
ld be aware of? For example, perhaps he or she is uncomfortable with certai=
n parts of the document, or has concerns whether there really is a need for=
 it. In any event, if the WG has discussed those issues and has indicated t=
hat it still wishes to advance the document, detail those concerns here.

     The document shepherd raised, in his review,
     (http://www.ietf.org/mail-archive/web/manet/current/msg16728.html)
     the question of if =93Updates RFC7182=94 is appropriate.

     The document author and the document shepherd both
     are =93on the balance=94 as to if it is, or is not

     Both parties, however, believe that either way is
     tolerable, and agreed to seek advice from the
     responsible AD on this particular matter
     (http://www.ietf.org/mail-archive/web/manet/current/msg16728.html)

     The argument for =93is not appropriate=94 goes like this:

          What this document does is:
               (i)  only things permissible by RFC7182, and
               (ii) makes registration from IANA registries
                    set up by RFC7182
                    (noting, of course, that RFC7181 doesn=92t
                     =93Updates 5444=94 when making registrations
                     for TC messages from the repositories
                     set up by RFC5444 as a case of precedent)

     The argument for =93is appropriate=94 is, that the
     way this document interprets <key-id> might not
     be as is described in RFC7182.

(7) Has each author confirmed that any and all appropriate IPR disclosures =
required for full conformance with the provisions of BCP 78 and BCP 79 have=
 already been filed. If not, explain why?

     The author has confirmed to not be aware of any
     IPR that requires disclosure regarding this specific
     documents.


(8) Has an IPR disclosure been filed that references this document? If so, =
summarize any WG discussion and conclusion regarding the IPR disclosures.

     There have been no IPR disclosures filed that
     reference this document.

(9) How solid is the WG consensus behind this document? Does it represent t=
he strong concurrence of a few individuals, with others being silent, or do=
es the WG as a whole understand and agree with it?

     As described under Working Group Summary, the
     consensus behind this document appears quite solid.

(10) Has anyone threatened an appeal or otherwise indicated extreme discont=
ent? If so, please summarise the areas of conflict in separate email messag=
es to the Responsible Area Director. (It should be in a separate email beca=
use this questionnaire is publicly available.)

     There have been no threats of appeal raised, nor
     has any extreme discontent been indicated.

(11) Identify any ID nits the Document Shepherd has found in this document.=
 (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist).=
 Boilerplate checks are not enough; this check needs to be thorough.

     IDNITS raises only concerns on a DOWNREF, addressed
     in 15) below.

(12) Describe how the document meets any required formal review criteria, s=
uch as the MIB Doctor, media type, and URI type reviews.

     Such reviews are not required for this document.

(13) Have all references within this document been identified as either nor=
mative or informative?

     Yes.

(14) Are there normative references to documents that are not ready for adv=
ancement or are otherwise in an unclear state? If such normative references=
 exist, what is the plan for their completion?

     No.

(15) Are there downward normative references references (see RFC 3967)? If =
so, list these downward references to support the Area Director in the Last=
 Call procedure.

     This document, intended for publication on std.
     track, has a downref to RFC6507, which is published
     as informational.

     RFC6507 does not appear in the downrefergistry
     (http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry)
     and must thus be explicitly called out in the
     IETF Last Call.

(16) Will publication of this document change the status of any existing RF=
Cs? Are those RFCs listed on the title page header, listed in the abstract,=
 and discussed in the introduction? If the RFCs are not listed in the Abstr=
act and Introduction, explain why, and point to the part of the document wh=
ere the relationship of this document to the other RFCs is discussed. If th=
is information is not in the document, explain why the WG considers it unne=
cessary.

     Advice from the responsible AD is sought on if
     this document =93Updates RFC7182=94, or not, as
     previously indicated.

     If, on the responsible ADs advice, this document
     updates RFC7182, then this is called out in the
     appropriate places.

(17) Describe the Document Shepherd's review of the IANA considerations sec=
tion, especially with regard to its consistency with the body of the docume=
nt. Confirm that all protocol extensions that the document makes are associ=
ated with the appropriate reservations in IANA registries. Confirm that any=
 referenced IANA registries have been clearly identified. Confirm that newl=
y created IANA registries include a detailed specification of the initial c=
ontents for the registry, that allocations procedures for future registrati=
ons are defined, and a reasonable name for the new registry has been sugges=
ted (see RFC 5226).

     All protocol extensions that the document makes, are
     associated with the appropriate reservations

     Referenced IANA registries have been clearly
     identified

     No new IANA registries are created

     The designated expert for the registry confirmed on
     14/09/03 that he finds the registrations
     requested in this document as aggreable:

     http://www.ietf.org/mail-archive/web/manet/current/msg16912.html

(18) List any new IANA registries that require Expert Review for future all=
ocations. Provide any public guidance that the IESG would find useful in se=
lecting the IANA Experts for these new registries.

     No new IANA registries are created.

(19) Describe reviews and automated checks performed by the Document Shephe=
rd to validate sections of the document written in a formal language, such =
as XML code, BNF rules, MIB definitions, etc.

     No such checks required nor performed: no XML code,
     BNF rules, MIB definitions, or other formal language
     for which automatic checks exist, is included in this
     document.




--_000_EC6E48C592074955B526390A8C913590ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <3E619FCD787C944394E465D84103F540@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Thomas,&nbsp;
<div><br>
</div>
<div>I've put your shepherd's writeup into the data tracker for the draft, =
and have requested IESG publication. Thank you for volunteering to be the d=
ocument shepherd on this.&nbsp;</div>
<div><br>
</div>
<div>Regards,</div>
<div>Stan</div>
<div><br>
</div>
<div><br>
<div>
<div>
<div>On Sep 4, 2014, at 10:14 AM, Thomas Clausen &lt;<a href=3D"mailto:thom=
as@thomasclausen.org">thomas@thomasclausen.org</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
Dear All,
<div><br>
</div>
<div>First, thank you Chris for being responsive to review comments, and sp=
inning a new version so quickly.&nbsp;</div>
<div><br>
</div>
<div>This allows me to post the document shepherd review. I believe that in=
serting the write-up in the tracker, and proceeding to request publication =
befalls on the WG chairs/secretary:</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span><u><b>=
I hereby respectfully request that publication be requested for this docume=
nt.</b></u></div>
<div><br>
</div>
<div>Respectfully,</div>
<div><br>
</div>
<div>Thomas</div>
<div><br>
</div>
<div>=3D=3D=3D</div>
<div><!--?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"no"?-->
<div style=3D"font-family: Arial; font-size: medium;"><font face=3D"Andale =
Mono"><br class=3D"Apple-interchange-newline">
<span style=3D"font-size: 12px;">Document Shepherd Write-Up for draft-ietf-=
manet-ibs-03</span></font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(1) What type=
 of RFC is being requested (BCP, Proposed Standard, Internet Standard, Info=
rmational, Experimental, or Historic)? Why is this the proper type of RFC? =
Is this type of RFC indicated in the
 title page header?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The intended status is&nbsp;=93Proposed Standard=94,&nbsp;</font></d=
iv>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;and this is indicated in the title page header.</font></div>
<p style=3D"font-family: Arial; background-color: rgb(255, 255, 255);"><fon=
t face=3D"Andale Mono">(2) The IESG approval announcement includes a Docume=
nt Announcement Write-Up. Please provide such a Document Announcement Write=
-Up. Recent examples can be found in
 the &quot;Action&quot; announcements for approved documents. The approval =
announcement contains the following sections:</font></p>
<p style=3D"font-family: Arial; background-color: rgb(255, 255, 255);"><fon=
t face=3D"Andale Mono">Technical Summary:</font></p>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;This document builds on RFC7182 and RFC6507, and</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;provides a framework for using Identity-Based</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;Signatures in MANET routing protocols.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">Working Group=
 Summary:<br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The document was presented at the WG meeting at&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;IETF=9290, and had reasonable discussion both before</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;and after this meeting. There were significant&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;expression of support for adoption as WG document,</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;a couple of reviews posted after adoption, which were</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;addressed. On the author=92s initiative, external</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;verification of the example provided in Appendix A</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;was&nbsp;sought from a crypto-expert.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;WGLC saw positive support for publication, with&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;nobody&nbsp;appearing to be&nbsp;=93in the rough&quot;</font></div>
<div style=3D"font-family: Arial;"><span style=3D"background-color: rgb(255=
, 255, 255);"><font face=3D"Andale Mono"><br>
</font></span></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><span style=
=3D"background-color: rgb(255, 255, 255);">Document Quality:</span><br>
</font></div>
<p style=3D"font-family: Arial; background-color: rgb(255, 255, 255);"><fon=
t face=3D"Andale Mono">Are there existing implementations of the protocol? =
Have a significant number of vendors indicated their plan to implement the =
specification? Are there any reviewers
 that merit special mention as having done a thorough review, e.g., one tha=
t resulted in important changes or a conclusion that the document had no su=
bstantive issues? If there was a MIB Doctor, Media Type or other expert rev=
iew, what was its course (briefly)?
 In the case of a Media Type review, on what date was the request posted?</=
font></p>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;There are existing implementations of this extension&nbsp;</font></d=
iv>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;mechanism, known to the document shepherd.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;Dr. Benjamin Smith provided independent verification&nbsp;</font></d=
iv>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;of the example provided in Appendix A, and is&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;recognized for this in the acknowledgements.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;No media type, nor MIB doctor, review done, as this</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;was not needed</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">Personnel:</f=
ont></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">Who is the Do=
cument Shepherd? Who is the Responsible Area Director?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The document shepherd is:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; Thomas Clausen</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The responsible Area Director is:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; Adrian Farrell</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(3) Briefly d=
escribe the review of this document that was performed by the Document Shep=
herd. If this version of the document is not ready for publication, please =
explain why the document is being forwarded
 to the IESG.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The document shepherd performed a total of five</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;reviews of this document, during WG processing:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;1) Initially, prior to WG adoption</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;2) Extensively, following WG adoption, providing &nbsp; &nbsp; &nbsp=
; &nbsp;&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp; &nbsp; substantial comments</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;3) Extensively, following the author addressed the&nbsp;</font></div=
>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp; &nbsp; review comments from 2), to satisfaction</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;4) Extensively, once WGLC was terminated, considering</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp; &nbsp; WGLC comments received, which resulted in a&nbsp;</font></di=
v>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp; &nbsp; document revision (-03) fixing nits, format&nbsp;</font></di=
v>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp; &nbsp; issues,&nbsp;and a reference issue.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;5) Finally, a review of the -03 version</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The document shepherd estimates, that the -03 version</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;of the document is technically identical to the -02</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;version which was WGLCed.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The document shepherd believes, that the&nbsp;-03 version</font></di=
v>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;of the document is ready for being forwarded to the</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;IESG.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(4) Does the =
document Shepherd have any concerns about the depth or breadth of the revie=
ws that have been performed?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The document shepherd is satisfied that sufficient</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;reviews have been performed.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(5) Do portio=
ns of the document need review from a particular or from broader perspectiv=
e, e.g., security, operational complexity, AAA, DNS, DHCP, XML, or internat=
ionalization? If so, describe the review
 that took place.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;This document addresses&nbsp;security, within the&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;framework set forth in RFC7182, and uses&nbsp;RFC6507</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;for the cryptographic functions. Both RFC7182 and</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;RFC6507 has received extensive scrutiny from the&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;security community.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;As such, the document shepherd believes that the</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;habitual SEC-DIR review for standards track documents</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;is expected&nbsp;=97 but that no additional reviews are</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;necessary, nor beneficial.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(6) Describe =
any specific concerns or issues that the Document Shepherd has with this do=
cument that the Responsible Area Director and/or the IESG should be aware o=
f? For example, perhaps he or she is
 uncomfortable with certain parts of the document, or has concerns whether =
there really is a need for it. In any event, if the WG has discussed those =
issues and has indicated that it still wishes to advance the document, deta=
il those concerns here.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The document shepherd raised, in his review,</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;(<a href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16=
728.html">http://www.ietf.org/mail-archive/web/manet/current/msg16728.html<=
/a>)</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;the question of if&nbsp;=93Updates RFC7182=94 is appropriate.</font>=
</div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The document author and the document shepherd both</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;are&nbsp;=93on the balance=94 as to if it is, or is not</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;">
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;Both parties, however, =
believe that either way is&nbsp;<br>
</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;tolerable, and agreed t=
o seek advice from the&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;responsible AD on this =
particular matter</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;(<a href=3D"http://www.=
ietf.org/mail-archive/web/manet/current/msg16728.html">http://www.ietf.org/=
mail-archive/web/manet/current/msg16728.html</a>)</font></div>
</div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The argument for&nbsp;=93is not appropriate=94 goes like this:</font=
></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;">
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; What thi=
s document does is:</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp;(i)&nbsp; only things permissible by RFC7182, and&nbsp;</font><=
/div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp;(ii) makes registration from IANA registries&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; set up by RFC7182</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; (noting, of course, that RFC7181 doesn=92t&nbsp;=
</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=93Updates 5444=94&nbsp;when making regist=
rations&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp;for TC messages from the repositories</fon=
t></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp;set up by RFC5444 as a case of precedent)<=
/font></div>
<div><font face=3D"Andale Mono"><br>
</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The argument for&nbsp;=
=93is appropriate=94 is, that the&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;way this document inter=
prets&nbsp;&lt;key-id&gt; might not&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;be as is described in R=
FC7182.</font></div>
</div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(7) Has each =
author confirmed that any and all appropriate IPR disclosures required for =
full conformance with the provisions of BCP 78 and BCP 79 have already been=
 filed. If not, explain why?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The author has confirmed to not be aware of any</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;IPR that requires disclosure regarding this specific</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;documents.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<p style=3D"font-family: Arial; background-color: rgb(255, 255, 255);"><fon=
t face=3D"Andale Mono">(8) Has an IPR disclosure been filed that references=
 this document? If so, summarize any WG discussion and conclusion regarding=
 the IPR disclosures.</font></p>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;There have been no IPR disclosures filed that</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;reference this document.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(9) How solid=
 is the WG consensus behind this document? Does it represent the strong con=
currence of a few individuals, with others being silent, or does the WG as =
a whole understand and agree with it?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;As described under Working Group Summary, the</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;consensus behind this document appears quite solid.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(10) Has anyo=
ne threatened an appeal or otherwise indicated extreme discontent? If so, p=
lease summarise the areas of conflict in separate email messages to the Res=
ponsible Area Director. (It should be
 in a separate email because this questionnaire is publicly available.)</fo=
nt></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;There have been no threats of appeal raised, nor</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;has any extreme discontent been indicated.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(11) Identify=
 any ID nits the Document Shepherd has found in this document. (See&nbsp;<a=
 href=3D"http://www.ietf.org/tools/idnits/">http://www.ietf.org/tools/idnit=
s/</a>&nbsp;and the Internet-Drafts Checklist).
 Boilerplate checks are not enough; this check needs to be thorough.</font>=
</div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;IDNITS raises only concerns on a DOWNREF, addressed</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;in 15) below.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(12) Describe=
 how the document meets any required formal review criteria, such as the MI=
B Doctor, media type, and URI type reviews.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;Such reviews are not required for this document.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(13) Have all=
 references within this document been identified as either normative or inf=
ormative?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;Yes.</font></div>
<p style=3D"font-family: Arial; background-color: rgb(255, 255, 255);"><fon=
t face=3D"Andale Mono">(14) Are there normative references to documents tha=
t are not ready for advancement or are otherwise in an unclear state? If su=
ch normative references exist, what
 is the plan for their completion?</font></p>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;No.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(15) Are ther=
e downward normative references references (see RFC 3967)? If so, list thes=
e downward references to support the Area Director in the Last Call procedu=
re.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;This document, intended for publication on std.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;track, has a&nbsp;downref to RFC6507, which is published&nbsp;</font=
></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;as informational.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;RFC6507 does not appear in the downrefergistry</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;(<a href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefR=
egistry">http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry</a=
>)</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;and must thus be explicitly called out in the&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;IETF Last Call.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(16) Will pub=
lication of this document change the status of any existing RFCs? Are those=
 RFCs listed on the title page header, listed in the abstract, and discusse=
d in the introduction? If the RFCs are
 not listed in the Abstract and Introduction, explain why, and point to the=
 part of the document where the relationship of this document to the other =
RFCs is discussed. If this information is not in the document, explain why =
the WG considers it unnecessary.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;Advice from the&nbsp;responsible AD is sought on if&nbsp;</font></di=
v>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;this document&nbsp;=93Updates RFC7182=94, or not, as&nbsp;</font></d=
iv>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;previously indicated.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;If, on the responsible ADs&nbsp;advice, this document</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;updates RFC7182, then this is called out in the</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;appropriate places.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(17) Describe=
 the Document Shepherd's review of the IANA considerations section, especia=
lly with regard to its consistency with the body of the document. Confirm t=
hat all protocol extensions that the
 document makes are associated with the appropriate reservations in IANA re=
gistries. Confirm that any referenced IANA registries have been clearly ide=
ntified. Confirm that newly created IANA registries include a detailed spec=
ification of the initial contents
 for the registry, that allocations procedures for future registrations are=
 defined, and a reasonable name for the new registry has been suggested (se=
e RFC 5226).</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;All protocol extensions that the document makes, are</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;associated with the appropriate reservations</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;Referenced IANA registries have been clearly&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;identified</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;No new IANA registries are created</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;The designated expert for the registry confirmed on</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;14/09/03 that he finds the registrations</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;requested in this document as aggreable:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;<a href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg169=
12.html">http://www.ietf.org/mail-archive/web/manet/current/msg16912.html</=
a></font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(18) List any=
 new IANA registries that require Expert Review for future allocations. Pro=
vide any public guidance that the IESG would find useful in selecting the I=
ANA Experts for these new registries.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;No new IANA registries are created.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(19) Describe=
 reviews and automated checks performed by the Document Shepherd to validat=
e sections of the document written in a formal language, such as XML code, =
BNF rules, MIB definitions, etc.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;No such checks&nbsp;required nor performed: no XML code,&nbsp;</font=
></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;BNF rules, MIB definitions, or other formal language&nbsp;</font></d=
iv>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;for which automatic checks exist, is included in this&nbsp;</font></=
div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; &nbsp;=
 &nbsp;document.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial; font-size: medium;"><font face=3D"Andale =
Mono"><br>
</font></div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>

--_000_EC6E48C592074955B526390A8C913590ciscocom_--


From nobody Thu Sep  4 08:45:12 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2C31A8978 for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 08:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yodEIF29dhzw for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 08:45:05 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 635071A8992 for <manet@ietf.org>; Thu,  4 Sep 2014 08:44:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 3BD5E240759; Thu,  4 Sep 2014 08:44:20 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 7260E240685; Thu,  4 Sep 2014 08:44:17 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_83C5799E-2FA2-4BF0-97E1-3439F45D63BE"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Thomas Clausen <thomas@thomasclausen.org>
In-Reply-To: <EC6E48C5-9207-4955-B526-390A8C913590@cisco.com>
Date: Thu, 4 Sep 2014 17:44:14 +0200
Message-Id: <FC28B914-8698-4804-AA43-3A4EAD869CB0@thomasclausen.org>
References: <FD76C330-A7EB-4281-A784-14C27C0374F8@thomasclausen.org> <EC6E48C5-9207-4955-B526-390A8C913590@cisco.com>
To: Stan Ratliff <sratliff@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/wjGOfayuy8YtojbdUA1TRN4NGHQ
Cc: "<manet-chairs@tools.ietf.org>" <manet-chairs@tools.ietf.org>, "<draft-ietf-manet-ibs@tools.ietf.org>" <draft-ietf-manet-ibs@tools.ietf.org>, manet IETF <manet@ietf.org>
Subject: Re: [manet] Document Shepherd Write-Up for draft-ietf-manet-ibs
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 15:45:09 -0000

--Apple-Mail=_83C5799E-2FA2-4BF0-97E1-3439F45D63BE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Stan,

Thank you for advancing this. I shall keep on top of the document, =
authors, and ADs, and report back as things progress.

Thomas

On Sep 4, 2014, at 17:42, Stan Ratliff (sratliff) <sratliff@cisco.com> =
wrote:

> Thomas,=20
>=20
> I've put your shepherd's writeup into the data tracker for the draft, =
and have requested IESG publication. Thank you for volunteering to be =
the document shepherd on this.=20
>=20
> Regards,
> Stan
>=20
>=20
> On Sep 4, 2014, at 10:14 AM, Thomas Clausen <thomas@thomasclausen.org> =
wrote:
>=20
>> Dear All,
>>=20
>> First, thank you Chris for being responsive to review comments, and =
spinning a new version so quickly.=20
>>=20
>> This allows me to post the document shepherd review. I believe that =
inserting the write-up in the tracker, and proceeding to request =
publication befalls on the WG chairs/secretary:
>>=20
>> I hereby respectfully request that publication be requested for this =
document.
>>=20
>> Respectfully,
>>=20
>> Thomas
>>=20
>> =3D=3D=3D
>>=20
>> Document Shepherd Write-Up for draft-ietf-manet-ibs-03
>>=20
>> (1) What type of RFC is being requested (BCP, Proposed Standard, =
Internet Standard, Informational, Experimental, or Historic)? Why is =
this the proper type of RFC? Is this type of RFC indicated in the title =
page header?
>>=20
>>      The intended status is =93Proposed Standard=94,=20
>>      and this is indicated in the title page header.
>> (2) The IESG approval announcement includes a Document Announcement =
Write-Up. Please provide such a Document Announcement Write-Up. Recent =
examples can be found in the "Action" announcements for approved =
documents. The approval announcement contains the following sections:
>>=20
>> Technical Summary:
>>=20
>>      This document builds on RFC7182 and RFC6507, and
>>      provides a framework for using Identity-Based
>>      Signatures in MANET routing protocols.
>>=20
>> Working Group Summary:
>>=20
>>      The document was presented at the WG meeting at=20
>>      IETF=9290, and had reasonable discussion both before
>>      and after this meeting. There were significant=20
>>      expression of support for adoption as WG document,
>>      a couple of reviews posted after adoption, which were
>>      addressed. On the author=92s initiative, external
>>      verification of the example provided in Appendix A
>>      was sought from a crypto-expert.
>>=20
>>      WGLC saw positive support for publication, with=20
>>      nobody appearing to be =93in the rough"
>>=20
>> Document Quality:
>> Are there existing implementations of the protocol? Have a =
significant number of vendors indicated their plan to implement the =
specification? Are there any reviewers that merit special mention as =
having done a thorough review, e.g., one that resulted in important =
changes or a conclusion that the document had no substantive issues? If =
there was a MIB Doctor, Media Type or other expert review, what was its =
course (briefly)? In the case of a Media Type review, on what date was =
the request posted?
>>=20
>>      There are existing implementations of this extension=20
>>      mechanism, known to the document shepherd.=20
>>=20
>>      Dr. Benjamin Smith provided independent verification=20
>>      of the example provided in Appendix A, and is=20
>>      recognized for this in the acknowledgements.
>>=20
>>      No media type, nor MIB doctor, review done, as this
>>      was not needed
>>=20
>> Personnel:
>>=20
>> Who is the Document Shepherd? Who is the Responsible Area Director?
>>=20
>>      The document shepherd is:
>>           Thomas Clausen
>>=20
>>      The responsible Area Director is:
>>           Adrian Farrell
>>=20
>>=20
>> (3) Briefly describe the review of this document that was performed =
by the Document Shepherd. If this version of the document is not ready =
for publication, please explain why the document is being forwarded to =
the IESG.
>>=20
>>      The document shepherd performed a total of five
>>      reviews of this document, during WG processing:
>>=20
>>      1) Initially, prior to WG adoption
>>=20
>>      2) Extensively, following WG adoption, providing        =20
>>         substantial comments
>>=20
>>      3) Extensively, following the author addressed the=20
>>         review comments from 2), to satisfaction
>>=20
>>      4) Extensively, once WGLC was terminated, considering
>>         WGLC comments received, which resulted in a=20
>>         document revision (-03) fixing nits, format=20
>>         issues, and a reference issue.
>>=20
>>      5) Finally, a review of the -03 version
>>=20
>>      The document shepherd estimates, that the -03 version
>>      of the document is technically identical to the -02
>>      version which was WGLCed.
>>=20
>>      The document shepherd believes, that the -03 version
>>      of the document is ready for being forwarded to the
>>      IESG.
>>=20
>> (4) Does the document Shepherd have any concerns about the depth or =
breadth of the reviews that have been performed?
>>=20
>>      The document shepherd is satisfied that sufficient
>>      reviews have been performed.
>>=20
>> (5) Do portions of the document need review from a particular or from =
broader perspective, e.g., security, operational complexity, AAA, DNS, =
DHCP, XML, or internationalization? If so, describe the review that took =
place.
>>=20
>>      This document addresses security, within the=20
>>      framework set forth in RFC7182, and uses RFC6507
>>      for the cryptographic functions. Both RFC7182 and
>>      RFC6507 has received extensive scrutiny from the=20
>>      security community.
>>=20
>>      As such, the document shepherd believes that the
>>      habitual SEC-DIR review for standards track documents
>>      is expected =97 but that no additional reviews are
>>      necessary, nor beneficial.
>>=20
>> (6) Describe any specific concerns or issues that the Document =
Shepherd has with this document that the Responsible Area Director =
and/or the IESG should be aware of? For example, perhaps he or she is =
uncomfortable with certain parts of the document, or has concerns =
whether there really is a need for it. In any event, if the WG has =
discussed those issues and has indicated that it still wishes to advance =
the document, detail those concerns here.
>>=20
>>      The document shepherd raised, in his review,
>>      =
(http://www.ietf.org/mail-archive/web/manet/current/msg16728.html)
>>      the question of if =93Updates RFC7182=94 is appropriate.
>>=20
>>      The document author and the document shepherd both
>>      are =93on the balance=94 as to if it is, or is not
>>=20
>>      Both parties, however, believe that either way is=20
>>      tolerable, and agreed to seek advice from the=20
>>      responsible AD on this particular matter
>>      =
(http://www.ietf.org/mail-archive/web/manet/current/msg16728.html)
>>=20
>>      The argument for =93is not appropriate=94 goes like this:
>>=20
>>           What this document does is:
>>                (i)  only things permissible by RFC7182, and=20
>>                (ii) makes registration from IANA registries=20
>>                     set up by RFC7182
>>                     (noting, of course, that RFC7181 doesn=92t=20
>>                      =93Updates 5444=94 when making registrations=20
>>                      for TC messages from the repositories
>>                      set up by RFC5444 as a case of precedent)
>>=20
>>      The argument for =93is appropriate=94 is, that the=20
>>      way this document interprets <key-id> might not=20
>>      be as is described in RFC7182.
>>=20
>> (7) Has each author confirmed that any and all appropriate IPR =
disclosures required for full conformance with the provisions of BCP 78 =
and BCP 79 have already been filed. If not, explain why?
>>=20
>>      The author has confirmed to not be aware of any
>>      IPR that requires disclosure regarding this specific
>>      documents.
>>=20
>> (8) Has an IPR disclosure been filed that references this document? =
If so, summarize any WG discussion and conclusion regarding the IPR =
disclosures.
>>=20
>>      There have been no IPR disclosures filed that
>>      reference this document.
>>=20
>> (9) How solid is the WG consensus behind this document? Does it =
represent the strong concurrence of a few individuals, with others being =
silent, or does the WG as a whole understand and agree with it?
>>=20
>>      As described under Working Group Summary, the
>>      consensus behind this document appears quite solid.
>>=20
>> (10) Has anyone threatened an appeal or otherwise indicated extreme =
discontent? If so, please summarise the areas of conflict in separate =
email messages to the Responsible Area Director. (It should be in a =
separate email because this questionnaire is publicly available.)
>>=20
>>      There have been no threats of appeal raised, nor
>>      has any extreme discontent been indicated.
>>=20
>> (11) Identify any ID nits the Document Shepherd has found in this =
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts =
Checklist). Boilerplate checks are not enough; this check needs to be =
thorough.
>>=20
>>      IDNITS raises only concerns on a DOWNREF, addressed
>>      in 15) below.
>>=20
>> (12) Describe how the document meets any required formal review =
criteria, such as the MIB Doctor, media type, and URI type reviews.
>>=20
>>      Such reviews are not required for this document.
>>=20
>> (13) Have all references within this document been identified as =
either normative or informative?
>>=20
>>      Yes.
>> (14) Are there normative references to documents that are not ready =
for advancement or are otherwise in an unclear state? If such normative =
references exist, what is the plan for their completion?
>>=20
>>      No.
>>=20
>> (15) Are there downward normative references references (see RFC =
3967)? If so, list these downward references to support the Area =
Director in the Last Call procedure.
>>=20
>>      This document, intended for publication on std.=20
>>      track, has a downref to RFC6507, which is published=20
>>      as informational.=20
>>=20
>>      RFC6507 does not appear in the downrefergistry
>>      =
(http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry)
>>      and must thus be explicitly called out in the=20
>>      IETF Last Call.
>>=20
>> (16) Will publication of this document change the status of any =
existing RFCs? Are those RFCs listed on the title page header, listed in =
the abstract, and discussed in the introduction? If the RFCs are not =
listed in the Abstract and Introduction, explain why, and point to the =
part of the document where the relationship of this document to the =
other RFCs is discussed. If this information is not in the document, =
explain why the WG considers it unnecessary.=20
>>=20
>>      Advice from the responsible AD is sought on if=20
>>      this document =93Updates RFC7182=94, or not, as=20
>>      previously indicated.=20
>>=20
>>      If, on the responsible ADs advice, this document
>>      updates RFC7182, then this is called out in the
>>      appropriate places.
>>=20
>> (17) Describe the Document Shepherd's review of the IANA =
considerations section, especially with regard to its consistency with =
the body of the document. Confirm that all protocol extensions that the =
document makes are associated with the appropriate reservations in IANA =
registries. Confirm that any referenced IANA registries have been =
clearly identified. Confirm that newly created IANA registries include a =
detailed specification of the initial contents for the registry, that =
allocations procedures for future registrations are defined, and a =
reasonable name for the new registry has been suggested (see RFC 5226).
>>=20
>>      All protocol extensions that the document makes, are
>>      associated with the appropriate reservations
>>=20
>>      Referenced IANA registries have been clearly=20
>>      identified
>>=20
>>      No new IANA registries are created
>>=20
>>      The designated expert for the registry confirmed on
>>      14/09/03 that he finds the registrations
>>      requested in this document as aggreable:
>>=20
>>      http://www.ietf.org/mail-archive/web/manet/current/msg16912.html
>>=20
>> (18) List any new IANA registries that require Expert Review for =
future allocations. Provide any public guidance that the IESG would find =
useful in selecting the IANA Experts for these new registries.
>>=20
>>      No new IANA registries are created.
>>=20
>> (19) Describe reviews and automated checks performed by the Document =
Shepherd to validate sections of the document written in a formal =
language, such as XML code, BNF rules, MIB definitions, etc.=20
>>=20
>>      No such checks required nor performed: no XML code,=20
>>      BNF rules, MIB definitions, or other formal language=20
>>      for which automatic checks exist, is included in this=20
>>      document.
>>=20
>>=20
>=20


--Apple-Mail=_83C5799E-2FA2-4BF0-97E1-3439F45D63BE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Stan,<div><br></div><div>Thank you for advancing =
this. I shall keep on top of the document, authors, and ADs, and report =
back as things =
progress.</div><div><br></div><div>Thomas</div><div><br><div><div>On Sep =
4, 2014, at 17:42, Stan Ratliff (sratliff) &lt;<a =
href=3D"mailto:sratliff@cisco.com">sratliff@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DWindows-1252">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Thomas,&nbsp;
<div><br>
</div>
<div>I've put your shepherd's writeup into the data tracker for the =
draft, and have requested IESG publication. Thank you for volunteering =
to be the document shepherd on this.&nbsp;</div>
<div><br>
</div>
<div>Regards,</div>
<div>Stan</div>
<div><br>
</div>
<div><br>
<div>
<div>
<div>On Sep 4, 2014, at 10:14 AM, Thomas Clausen &lt;<a =
href=3D"mailto:thomas@thomasclausen.org">thomas@thomasclausen.org</a>&gt; =
wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;">
Dear All,
<div><br>
</div>
<div>First, thank you Chris for being responsive to review comments, and =
spinning a new version so quickly.&nbsp;</div>
<div><br>
</div>
<div>This allows me to post the document shepherd review. I believe that =
inserting the write-up in the tracker, and proceeding to request =
publication befalls on the WG chairs/secretary:</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre"></span><u><b>I hereby respectfully request =
that publication be requested for this document.</b></u></div>
<div><br>
</div>
<div>Respectfully,</div>
<div><br>
</div>
<div>Thomas</div>
<div><br>
</div>
<div>=3D=3D=3D</div>
<div><!--?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"no"?-->
<div style=3D"font-family: Arial; font-size: inherit;"><font =
face=3D"Andale Mono"><br class=3D"Apple-interchange-newline">
<span style=3D"font-size: 12px;">Document Shepherd Write-Up for =
draft-ietf-manet-ibs-03</span></font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(1) What =
type of RFC is being requested (BCP, Proposed Standard, Internet =
Standard, Informational, Experimental, or Historic)? Why is this the =
proper type of RFC? Is this type of RFC indicated in the
 title page header?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The intended status is&nbsp;=93Proposed =
Standard=94,&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;and this is indicated in the title page =
header.</font></div><p style=3D"font-family: Arial; background-color: =
rgb(255, 255, 255);"><font face=3D"Andale Mono">(2) The IESG approval =
announcement includes a Document Announcement Write-Up. Please provide =
such a Document Announcement Write-Up. Recent examples can be found in
 the "Action" announcements for approved documents. The approval =
announcement contains the following sections:</font></p><p =
style=3D"font-family: Arial; background-color: rgb(255, 255, =
255);"><font face=3D"Andale Mono">Technical Summary:</font></p>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;This document builds on RFC7182 and RFC6507, =
and</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;provides a framework for using Identity-Based</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;Signatures in MANET routing protocols.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">Working =
Group Summary:<br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The document was presented at the WG meeting =
at&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;IETF=9290, and had reasonable discussion both =
before</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;and after this meeting. There were =
significant&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;expression of support for adoption as WG =
document,</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;a couple of reviews posted after adoption, which =
were</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;addressed. On the author=92s initiative, =
external</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;verification of the example provided in Appendix =
A</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;was&nbsp;sought from a crypto-expert.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;WGLC saw positive support for publication, =
with&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;nobody&nbsp;appearing to be&nbsp;=93in the =
rough"</font></div>
<div style=3D"font-family: Arial;"><span style=3D"background-color: =
rgb(255, 255, 255);"><font face=3D"Andale Mono"><br>
</font></span></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><span =
style=3D"background-color: rgb(255, 255, 255);">Document =
Quality:</span><br>
</font></div><p style=3D"font-family: Arial; background-color: rgb(255, =
255, 255);"><font face=3D"Andale Mono">Are there existing =
implementations of the protocol? Have a significant number of vendors =
indicated their plan to implement the specification? Are there any =
reviewers
 that merit special mention as having done a thorough review, e.g., one =
that resulted in important changes or a conclusion that the document had =
no substantive issues? If there was a MIB Doctor, Media Type or other =
expert review, what was its course (briefly)?
 In the case of a Media Type review, on what date was the request =
posted?</font></p>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;There are existing implementations of this =
extension&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;mechanism, known to the document =
shepherd.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;Dr. Benjamin Smith provided independent =
verification&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;of the example provided in Appendix A, and =
is&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;recognized for this in the acknowledgements.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;No media type, nor MIB doctor, review done, as =
this</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;was not needed</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale =
Mono">Personnel:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">Who is the =
Document Shepherd? Who is the Responsible Area Director?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The document shepherd is:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; Thomas Clausen</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The responsible Area Director is:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; Adrian Farrell</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(3) =
Briefly describe the review of this document that was performed by the =
Document Shepherd. If this version of the document is not ready for =
publication, please explain why the document is being forwarded
 to the IESG.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The document shepherd performed a total of =
five</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;reviews of this document, during WG =
processing:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;1) Initially, prior to WG adoption</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;2) Extensively, following WG adoption, providing &nbsp; =
&nbsp; &nbsp; &nbsp;&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; substantial comments</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;3) Extensively, following the author addressed =
the&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; review comments from 2), to =
satisfaction</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;4) Extensively, once WGLC was terminated, =
considering</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; WGLC comments received, which resulted in =
a&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; document revision (-03) fixing nits, =
format&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp; &nbsp; issues,&nbsp;and a reference issue.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;5) Finally, a review of the -03 version</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The document shepherd estimates, that the -03 =
version</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;of the document is technically identical to the =
-02</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;version which was WGLCed.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The document shepherd believes, that the&nbsp;-03 =
version</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;of the document is ready for being forwarded to =
the</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;IESG.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(4) Does =
the document Shepherd have any concerns about the depth or breadth of =
the reviews that have been performed?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The document shepherd is satisfied that =
sufficient</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;reviews have been performed.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(5) Do =
portions of the document need review from a particular or from broader =
perspective, e.g., security, operational complexity, AAA, DNS, DHCP, =
XML, or internationalization? If so, describe the review
 that took place.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;This document addresses&nbsp;security, within =
the&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;framework set forth in RFC7182, and =
uses&nbsp;RFC6507</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;for the cryptographic functions. Both RFC7182 =
and</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;RFC6507 has received extensive scrutiny from =
the&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;security community.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;As such, the document shepherd believes that =
the</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;habitual SEC-DIR review for standards track =
documents</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;is expected&nbsp;=97 but that no additional reviews =
are</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;necessary, nor beneficial.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(6) =
Describe any specific concerns or issues that the Document Shepherd has =
with this document that the Responsible Area Director and/or the IESG =
should be aware of? For example, perhaps he or she is
 uncomfortable with certain parts of the document, or has concerns =
whether there really is a need for it. In any event, if the WG has =
discussed those issues and has indicated that it still wishes to advance =
the document, detail those concerns here.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The document shepherd raised, in his review,</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;(<a =
href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16728.html">=
http://www.ietf.org/mail-archive/web/manet/current/msg16728.html</a>)</fon=
t></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;the question of if&nbsp;=93Updates RFC7182=94 is =
appropriate.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The document author and the document shepherd =
both</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;are&nbsp;=93on the balance=94 as to if it is, or is =
not</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;">
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;Both parties, =
however, believe that either way is&nbsp;<br>
</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;tolerable, and =
agreed to seek advice from the&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;responsible AD on =
this particular matter</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;(<a =
href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16728.html">=
http://www.ietf.org/mail-archive/web/manet/current/msg16728.html</a>)</fon=
t></div>
</div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The argument for&nbsp;=93is not appropriate=94 goes like =
this:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;">
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; What =
this document does is:</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(i)&nbsp; only things permissible by RFC7182, =
and&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(ii) makes registration from IANA =
registries&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; set up by RFC7182</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (noting, of course, that RFC7181 =
doesn=92t&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=93Updates 5444=94&nbsp;when =
making registrations&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;for TC messages from the =
repositories</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;set up by RFC5444 as a case of =
precedent)</font></div>
<div><font face=3D"Andale Mono"><br>
</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;The argument =
for&nbsp;=93is appropriate=94 is, that the&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;way this document =
interprets&nbsp;&lt;key-id&gt; might not&nbsp;</font></div>
<div><font face=3D"Andale Mono">&nbsp; &nbsp; &nbsp;be as is described =
in RFC7182.</font></div>
</div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(7) Has =
each author confirmed that any and all appropriate IPR disclosures =
required for full conformance with the provisions of BCP 78 and BCP 79 =
have already been filed. If not, explain why?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The author has confirmed to not be aware of =
any</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;IPR that requires disclosure regarding this =
specific</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;documents.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div><p style=3D"font-family: Arial; background-color: rgb(255, =
255, 255);"><font face=3D"Andale Mono">(8) Has an IPR disclosure been =
filed that references this document? If so, summarize any WG discussion =
and conclusion regarding the IPR disclosures.</font></p>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;There have been no IPR disclosures filed that</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;reference this document.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(9) How =
solid is the WG consensus behind this document? Does it represent the =
strong concurrence of a few individuals, with others being silent, or =
does the WG as a whole understand and agree with it?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;As described under Working Group Summary, the</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;consensus behind this document appears quite =
solid.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(10) Has =
anyone threatened an appeal or otherwise indicated extreme discontent? =
If so, please summarise the areas of conflict in separate email messages =
to the Responsible Area Director. (It should be
 in a separate email because this questionnaire is publicly =
available.)</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;There have been no threats of appeal raised, =
nor</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;has any extreme discontent been indicated.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(11) =
Identify any ID nits the Document Shepherd has found in this document. =
(See&nbsp;<a =
href=3D"http://www.ietf.org/tools/idnits/">http://www.ietf.org/tools/idnit=
s/</a>&nbsp;and the Internet-Drafts Checklist).
 Boilerplate checks are not enough; this check needs to be =
thorough.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;IDNITS raises only concerns on a DOWNREF, =
addressed</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;in 15) below.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(12) =
Describe how the document meets any required formal review criteria, =
such as the MIB Doctor, media type, and URI type reviews.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;Such reviews are not required for this =
document.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(13) Have =
all references within this document been identified as either normative =
or informative?</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;Yes.</font></div><p style=3D"font-family: Arial; =
background-color: rgb(255, 255, 255);"><font face=3D"Andale Mono">(14) =
Are there normative references to documents that are not ready for =
advancement or are otherwise in an unclear state? If such normative =
references exist, what
 is the plan for their completion?</font></p>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;No.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(15) Are =
there downward normative references references (see RFC 3967)? If so, =
list these downward references to support the Area Director in the Last =
Call procedure.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;This document, intended for publication on =
std.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;track, has a&nbsp;downref to RFC6507, which is =
published&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;as informational.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;RFC6507 does not appear in the downrefergistry</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;(<a =
href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry">h=
ttp://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry</a>)</font>=
</div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;and must thus be explicitly called out in =
the&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;IETF Last Call.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(16) Will =
publication of this document change the status of any existing RFCs? Are =
those RFCs listed on the title page header, listed in the abstract, and =
discussed in the introduction? If the RFCs are
 not listed in the Abstract and Introduction, explain why, and point to =
the part of the document where the relationship of this document to the =
other RFCs is discussed. If this information is not in the document, =
explain why the WG considers it unnecessary.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;Advice from the&nbsp;responsible AD is sought on =
if&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;this document&nbsp;=93Updates RFC7182=94, or not, =
as&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;previously indicated.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;If, on the responsible ADs&nbsp;advice, this =
document</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;updates RFC7182, then this is called out in =
the</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;appropriate places.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(17) =
Describe the Document Shepherd's review of the IANA considerations =
section, especially with regard to its consistency with the body of the =
document. Confirm that all protocol extensions that the
 document makes are associated with the appropriate reservations in IANA =
registries. Confirm that any referenced IANA registries have been =
clearly identified. Confirm that newly created IANA registries include a =
detailed specification of the initial contents
 for the registry, that allocations procedures for future registrations =
are defined, and a reasonable name for the new registry has been =
suggested (see RFC 5226).</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;All protocol extensions that the document makes, =
are</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;associated with the appropriate reservations</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;Referenced IANA registries have been =
clearly&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;identified</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;No new IANA registries are created</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;The designated expert for the registry confirmed =
on</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;14/09/03 that he finds the registrations</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;requested in this document as aggreable:</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;<a =
href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16912.html">=
http://www.ietf.org/mail-archive/web/manet/current/msg16912.html</a></font=
></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(18) List =
any new IANA registries that require Expert Review for future =
allocations. Provide any public guidance that the IESG would find useful =
in selecting the IANA Experts for these new registries.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;No new IANA registries are created.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">(19) =
Describe reviews and automated checks performed by the Document Shepherd =
to validate sections of the document written in a formal language, such =
as XML code, BNF rules, MIB definitions, etc.&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;No such checks&nbsp;required nor performed: no XML =
code,&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;BNF rules, MIB definitions, or other formal =
language&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;for which automatic checks exist, is included in =
this&nbsp;</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono">&nbsp; =
&nbsp; &nbsp;document.</font></div>
<div style=3D"font-family: Arial;"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family: Arial; font-size: inherit;"><font =
face=3D"Andale Mono"><br>
</font></div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>

</blockquote></div><br></div></body></html>=

--Apple-Mail=_83C5799E-2FA2-4BF0-97E1-3439F45D63BE--



From nobody Thu Sep  4 09:50:07 2014
Return-Path: <jpmacker@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8A5E1A8797 for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 09:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NYqTL3LCm4AV for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 09:49:55 -0700 (PDT)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E24D1A875B for <manet@ietf.org>; Thu,  4 Sep 2014 09:49:46 -0700 (PDT)
Received: by mail-qg0-f49.google.com with SMTP id j107so10105051qga.8 for <manet@ietf.org>; Thu, 04 Sep 2014 09:49:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YmukRsb0hD90wxwr6H1Wl/A8+w/2+OUceIk2v1FPcms=; b=mDiR0R0FKW98APX2XEc2VN1iC+9m+YgGPb8XDi/C1Iq5UCt73e9BVyifTe2XruIX0l 5jno5nqBADANf8Ht/65a7Tt3FOnbJ6Z8Yq/TgroPkVkahiO7+qs6r6EBLGhyBEMeCWWm Fjf5QfiplgFWrjgvwjIDchcOVSwVvYnrLBjel6xHBX58Io+lbQN1PnrRgpQljieuRcvN 6cFHNTYKMf3i65vIGdeXMrKeBI6hOO5XCzEPnMvjny0c2wBPl5RFRi6Ce5g+ptn2HfID 8ggiaRn3PYS1Ly47t0LQ9YQzsNyOv4lceWXpSEFk1/7v9mZRhhigljmKvQbLhjrz4RyL UJoA==
MIME-Version: 1.0
X-Received: by 10.140.21.177 with SMTP id 46mr8531517qgl.90.1409849386150; Thu, 04 Sep 2014 09:49:46 -0700 (PDT)
Received: by 10.140.101.140 with HTTP; Thu, 4 Sep 2014 09:49:46 -0700 (PDT)
In-Reply-To: <EC6E48C5-9207-4955-B526-390A8C913590@cisco.com>
References: <FD76C330-A7EB-4281-A784-14C27C0374F8@thomasclausen.org> <EC6E48C5-9207-4955-B526-390A8C913590@cisco.com>
Date: Thu, 4 Sep 2014 12:49:46 -0400
Message-ID: <CAHA-Tp4ix906Ej2g22yJo4e8R11M-eeSDsJCNBW+ks1-CRKMig@mail.gmail.com>
From: Joseph Macker <jpmacker@gmail.com>
To: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c13986d938f20502402300
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/qbRe0ZKV9tfhKsLy9dFgPgQ7wws
Cc: "<manet-chairs@tools.ietf.org>" <manet-chairs@tools.ietf.org>, "<draft-ietf-manet-ibs@tools.ietf.org>" <draft-ietf-manet-ibs@tools.ietf.org>, manet IETF <manet@ietf.org>, Thomas Clausen <thomas@thomasclausen.org>
Subject: Re: [manet] Document Shepherd Write-Up for draft-ietf-manet-ibs
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 16:50:01 -0000

--001a11c13986d938f20502402300
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Ditto on thanks.
-Joe


On Thu, Sep 4, 2014 at 11:42 AM, Stan Ratliff (sratliff) <sratliff@cisco.co=
m
> wrote:

>  Thomas,
>
>  I've put your shepherd's writeup into the data tracker for the draft,
> and have requested IESG publication. Thank you for volunteering to be the
> document shepherd on this.
>
>  Regards,
> Stan
>
>
>  On Sep 4, 2014, at 10:14 AM, Thomas Clausen <thomas@thomasclausen.org>
> wrote:
>
>  Dear All,
>
>  First, thank you Chris for being responsive to review comments, and
> spinning a new version so quickly.
>
>  This allows me to post the document shepherd review. I believe that
> inserting the write-up in the tracker, and proceeding to request
> publication befalls on the WG chairs/secretary:
>
>  *I hereby respectfully request that publication be requested for this
> document.*
>
>  Respectfully,
>
>  Thomas
>
>  =3D=3D=3D
>
> Document Shepherd Write-Up for draft-ietf-manet-ibs-03
>
>  (1) What type of RFC is being requested (BCP, Proposed Standard,
> Internet Standard, Informational, Experimental, or Historic)? Why is this
> the proper type of RFC? Is this type of RFC indicated in the title page
> header?
>
>       The intended status is =E2=80=9CProposed Standard=E2=80=9D,
>      and this is indicated in the title page header.
>
> (2) The IESG approval announcement includes a Document Announcement
> Write-Up. Please provide such a Document Announcement Write-Up. Recent
> examples can be found in the "Action" announcements for approved document=
s.
> The approval announcement contains the following sections:
>
> Technical Summary:
>      This document builds on RFC7182 and RFC6507, and
>      provides a framework for using Identity-Based
>      Signatures in MANET routing protocols.
>
>  Working Group Summary:
>
>       The document was presented at the WG meeting at
>      IETF=E2=80=9990, and had reasonable discussion both before
>      and after this meeting. There were significant
>      expression of support for adoption as WG document,
>      a couple of reviews posted after adoption, which were
>      addressed. On the author=E2=80=99s initiative, external
>      verification of the example provided in Appendix A
>      was sought from a crypto-expert.
>
>       WGLC saw positive support for publication, with
>      nobody appearing to be =E2=80=9Cin the rough"
>
>  Document Quality:
>
> Are there existing implementations of the protocol? Have a significant
> number of vendors indicated their plan to implement the specification? Ar=
e
> there any reviewers that merit special mention as having done a thorough
> review, e.g., one that resulted in important changes or a conclusion that
> the document had no substantive issues? If there was a MIB Doctor, Media
> Type or other expert review, what was its course (briefly)? In the case o=
f
> a Media Type review, on what date was the request posted?
>      There are existing implementations of this extension
>      mechanism, known to the document shepherd.
>
>       Dr. Benjamin Smith provided independent verification
>      of the example provided in Appendix A, and is
>      recognized for this in the acknowledgements.
>
>       No media type, nor MIB doctor, review done, as this
>      was not needed
>
>  Personnel:
>
>  Who is the Document Shepherd? Who is the Responsible Area Director?
>
>       The document shepherd is:
>           Thomas Clausen
>
>       The responsible Area Director is:
>           Adrian Farrell
>
>
>  (3) Briefly describe the review of this document that was performed by
> the Document Shepherd. If this version of the document is not ready for
> publication, please explain why the document is being forwarded to the IE=
SG.
>
>       The document shepherd performed a total of five
>      reviews of this document, during WG processing:
>
>       1) Initially, prior to WG adoption
>
>       2) Extensively, following WG adoption, providing
>         substantial comments
>
>       3) Extensively, following the author addressed the
>         review comments from 2), to satisfaction
>
>       4) Extensively, once WGLC was terminated, considering
>         WGLC comments received, which resulted in a
>         document revision (-03) fixing nits, format
>         issues, and a reference issue.
>
>       5) Finally, a review of the -03 version
>
>       The document shepherd estimates, that the -03 version
>      of the document is technically identical to the -02
>      version which was WGLCed.
>
>       The document shepherd believes, that the -03 version
>      of the document is ready for being forwarded to the
>      IESG.
>
>  (4) Does the document Shepherd have any concerns about the depth or
> breadth of the reviews that have been performed?
>
>       The document shepherd is satisfied that sufficient
>      reviews have been performed.
>
>  (5) Do portions of the document need review from a particular or from
> broader perspective, e.g., security, operational complexity, AAA, DNS,
> DHCP, XML, or internationalization? If so, describe the review that took
> place.
>
>       This document addresses security, within the
>      framework set forth in RFC7182, and uses RFC6507
>      for the cryptographic functions. Both RFC7182 and
>      RFC6507 has received extensive scrutiny from the
>      security community.
>
>       As such, the document shepherd believes that the
>      habitual SEC-DIR review for standards track documents
>      is expected =E2=80=94 but that no additional reviews are
>      necessary, nor beneficial.
>
>  (6) Describe any specific concerns or issues that the Document Shepherd
> has with this document that the Responsible Area Director and/or the IESG
> should be aware of? For example, perhaps he or she is uncomfortable with
> certain parts of the document, or has concerns whether there really is a
> need for it. In any event, if the WG has discussed those issues and has
> indicated that it still wishes to advance the document, detail those
> concerns here.
>
>       The document shepherd raised, in his review,
>      (http://www.ietf.org/mail-archive/web/manet/current/msg16728.html)
>      the question of if =E2=80=9CUpdates RFC7182=E2=80=9D is appropriate.
>
>       The document author and the document shepherd both
>      are =E2=80=9Con the balance=E2=80=9D as to if it is, or is not
>
>       Both parties, however, believe that either way is
>       tolerable, and agreed to seek advice from the
>      responsible AD on this particular matter
>      (http://www.ietf.org/mail-archive/web/manet/current/msg16728.html)
>
>       The argument for =E2=80=9Cis not appropriate=E2=80=9D goes like thi=
s:
>
>            What this document does is:
>                (i)  only things permissible by RFC7182, and
>                (ii) makes registration from IANA registries
>                     set up by RFC7182
>                     (noting, of course, that RFC7181 doesn=E2=80=99t
>                      =E2=80=9CUpdates 5444=E2=80=9D when making registrat=
ions
>                      for TC messages from the repositories
>                      set up by RFC5444 as a case of precedent)
>
>       The argument for =E2=80=9Cis appropriate=E2=80=9D is, that the
>      way this document interprets <key-id> might not
>      be as is described in RFC7182.
>
>  (7) Has each author confirmed that any and all appropriate IPR
> disclosures required for full conformance with the provisions of BCP 78 a=
nd
> BCP 79 have already been filed. If not, explain why?
>
>       The author has confirmed to not be aware of any
>      IPR that requires disclosure regarding this specific
>      documents.
>
>  (8) Has an IPR disclosure been filed that references this document? If
> so, summarize any WG discussion and conclusion regarding the IPR
> disclosures.
>      There have been no IPR disclosures filed that
>      reference this document.
>
>  (9) How solid is the WG consensus behind this document? Does it
> represent the strong concurrence of a few individuals, with others being
> silent, or does the WG as a whole understand and agree with it?
>
>       As described under Working Group Summary, the
>      consensus behind this document appears quite solid.
>
>  (10) Has anyone threatened an appeal or otherwise indicated extreme
> discontent? If so, please summarise the areas of conflict in separate ema=
il
> messages to the Responsible Area Director. (It should be in a separate
> email because this questionnaire is publicly available.)
>
>       There have been no threats of appeal raised, nor
>      has any extreme discontent been indicated.
>
>  (11) Identify any ID nits the Document Shepherd has found in this
> document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
> Checklist). Boilerplate checks are not enough; this check needs to be
> thorough.
>
>       IDNITS raises only concerns on a DOWNREF, addressed
>      in 15) below.
>
>  (12) Describe how the document meets any required formal review
> criteria, such as the MIB Doctor, media type, and URI type reviews.
>
>       Such reviews are not required for this document.
>
>  (13) Have all references within this document been identified as either
> normative or informative?
>
>       Yes.
>
> (14) Are there normative references to documents that are not ready for
> advancement or are otherwise in an unclear state? If such normative
> references exist, what is the plan for their completion?
>      No.
>
>  (15) Are there downward normative references references (see RFC 3967)?
> If so, list these downward references to support the Area Director in the
> Last Call procedure.
>
>       This document, intended for publication on std.
>      track, has a downref to RFC6507, which is published
>      as informational.
>
>       RFC6507 does not appear in the downrefergistry
>      (http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry)
>      and must thus be explicitly called out in the
>      IETF Last Call.
>
>  (16) Will publication of this document change the status of any existing
> RFCs? Are those RFCs listed on the title page header, listed in the
> abstract, and discussed in the introduction? If the RFCs are not listed i=
n
> the Abstract and Introduction, explain why, and point to the part of the
> document where the relationship of this document to the other RFCs is
> discussed. If this information is not in the document, explain why the WG
> considers it unnecessary.
>
>       Advice from the responsible AD is sought on if
>      this document =E2=80=9CUpdates RFC7182=E2=80=9D, or not, as
>      previously indicated.
>
>       If, on the responsible ADs advice, this document
>      updates RFC7182, then this is called out in the
>      appropriate places.
>
>  (17) Describe the Document Shepherd's review of the IANA considerations
> section, especially with regard to its consistency with the body of the
> document. Confirm that all protocol extensions that the document makes ar=
e
> associated with the appropriate reservations in IANA registries. Confirm
> that any referenced IANA registries have been clearly identified. Confirm
> that newly created IANA registries include a detailed specification of th=
e
> initial contents for the registry, that allocations procedures for future
> registrations are defined, and a reasonable name for the new registry has
> been suggested (see RFC 5226).
>
>       All protocol extensions that the document makes, are
>      associated with the appropriate reservations
>
>       Referenced IANA registries have been clearly
>      identified
>
>       No new IANA registries are created
>
>       The designated expert for the registry confirmed on
>      14/09/03 that he finds the registrations
>      requested in this document as aggreable:
>
>       http://www.ietf.org/mail-archive/web/manet/current/msg16912.html
>
>  (18) List any new IANA registries that require Expert Review for future
> allocations. Provide any public guidance that the IESG would find useful =
in
> selecting the IANA Experts for these new registries.
>
>       No new IANA registries are created.
>
>  (19) Describe reviews and automated checks performed by the Document
> Shepherd to validate sections of the document written in a formal languag=
e,
> such as XML code, BNF rules, MIB definitions, etc.
>
>       No such checks required nor performed: no XML code,
>      BNF rules, MIB definitions, or other formal language
>      for which automatic checks exist, is included in this
>      document.
>
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--001a11c13986d938f20502402300
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Ditto on thanks.<div>-Joe</div></div><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Thu, Sep 4, 2014 at 11:42 AM, S=
tan Ratliff (sratliff) <span dir=3D"ltr">&lt;<a href=3D"mailto:sratliff@cis=
co.com" target=3D"_blank">sratliff@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Thomas,=C2=A0
<div><br>
</div>
<div>I&#39;ve put your shepherd&#39;s writeup into the data tracker for the=
 draft, and have requested IESG publication. Thank you for volunteering to =
be the document shepherd on this.=C2=A0</div>
<div><br>
</div>
<div>Regards,</div>
<div>Stan</div><div><div class=3D"h5">
<div><br>
</div>
<div><br>
<div>
<div>
<div>On Sep 4, 2014, at 10:14 AM, Thomas Clausen &lt;<a href=3D"mailto:thom=
as@thomasclausen.org" target=3D"_blank">thomas@thomasclausen.org</a>&gt; wr=
ote:</div>
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap:break-word">
Dear All,
<div><br>
</div>
<div>First, thank you Chris for being responsive to review comments, and sp=
inning a new version so quickly.=C2=A0</div>
<div><br>
</div>
<div>This allows me to post the document shepherd review. I believe that in=
serting the write-up in the tracker, and proceeding to request publication =
befalls on the WG chairs/secretary:</div>
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span><u><b>I hereby respectfull=
y request that publication be requested for this document.</b></u></div>
<div><br>
</div>
<div>Respectfully,</div>
<div><br>
</div>
<div>Thomas</div>
<div><br>
</div>
<div>=3D=3D=3D</div>
<div>
<div style=3D"font-family:Arial;font-size:medium"><font face=3D"Andale Mono=
"><br>
<span style=3D"font-size:12px">Document Shepherd Write-Up for draft-ietf-ma=
net-ibs-03</span></font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(1) What type o=
f RFC is being requested (BCP, Proposed Standard, Internet Standard, Inform=
ational, Experimental, or Historic)? Why is this the proper type of RFC? Is=
 this type of RFC indicated in the
 title page header?</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The intended status is=C2=A0=E2=80=9CProposed Standard=E2=80=9D,=C2=
=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0and this is indicated in the title page header.</font></div>
<p style=3D"font-family:Arial;background-color:rgb(255,255,255)"><font face=
=3D"Andale Mono">(2) The IESG approval announcement includes a Document Ann=
ouncement Write-Up. Please provide such a Document Announcement Write-Up. R=
ecent examples can be found in
 the &quot;Action&quot; announcements for approved documents. The approval =
announcement contains the following sections:</font></p>
<p style=3D"font-family:Arial;background-color:rgb(255,255,255)"><font face=
=3D"Andale Mono">Technical Summary:</font></p>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0This document builds on RFC7182 and RFC6507, and</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0provides a framework for using Identity-Based</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0Signatures in MANET routing protocols.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">Working Group S=
ummary:<br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The document was presented at the WG meeting at=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0IETF=E2=80=9990, and had reasonable discussion both before</font></di=
v>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0and after this meeting. There were significant=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0expression of support for adoption as WG document,</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0a couple of reviews posted after adoption, which were</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0addressed. On the author=E2=80=99s initiative, external</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0verification of the example provided in Appendix A</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0was=C2=A0sought from a crypto-expert.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0WGLC saw positive support for publication, with=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0nobody=C2=A0appearing to be=C2=A0=E2=80=9Cin the rough&quot;</font></=
div>
<div style=3D"font-family:Arial"><span style=3D"background-color:rgb(255,25=
5,255)"><font face=3D"Andale Mono"><br>
</font></span></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><span style=3D"=
background-color:rgb(255,255,255)">Document Quality:</span><br>
</font></div>
<p style=3D"font-family:Arial;background-color:rgb(255,255,255)"><font face=
=3D"Andale Mono">Are there existing implementations of the protocol? Have a=
 significant number of vendors indicated their plan to implement the specif=
ication? Are there any reviewers
 that merit special mention as having done a thorough review, e.g., one tha=
t resulted in important changes or a conclusion that the document had no su=
bstantive issues? If there was a MIB Doctor, Media Type or other expert rev=
iew, what was its course (briefly)?
 In the case of a Media Type review, on what date was the request posted?</=
font></p>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0There are existing implementations of this extension=C2=A0</font></di=
v>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0mechanism, known to the document shepherd.=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0Dr. Benjamin Smith provided independent verification=C2=A0</font></di=
v>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0of the example provided in Appendix A, and is=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0recognized for this in the acknowledgements.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0No media type, nor MIB doctor, review done, as this</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0was not needed</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">Personnel:</fon=
t></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">Who is the Docu=
ment Shepherd? Who is the Responsible Area Director?</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The document shepherd is:</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Thomas Clausen</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The responsible Area Director is:</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Adrian Farrell</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(3) Briefly des=
cribe the review of this document that was performed by the Document Shephe=
rd. If this version of the document is not ready for publication, please ex=
plain why the document is being forwarded
 to the IESG.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The document shepherd performed a total of five</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0reviews of this document, during WG processing:</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A01) Initially, prior to WG adoption</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A02) Extensively, following WG adoption, providing =C2=A0 =C2=A0 =C2=A0=
 =C2=A0=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 substantial comments</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A03) Extensively, following the author addressed the=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 review comments from 2), to satisfaction</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A04) Extensively, once WGLC was terminated, considering</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 WGLC comments received, which resulted in a=C2=A0</font></div=
>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 document revision (-03) fixing nits, format=C2=A0</font></div=
>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 issues,=C2=A0and a reference issue.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A05) Finally, a review of the -03 version</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The document shepherd estimates, that the -03 version</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0of the document is technically identical to the -02</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0version which was WGLCed.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The document shepherd believes, that the=C2=A0-03 version</font></div=
>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0of the document is ready for being forwarded to the</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0IESG.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(4) Does the do=
cument Shepherd have any concerns about the depth or breadth of the reviews=
 that have been performed?</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The document shepherd is satisfied that sufficient</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0reviews have been performed.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(5) Do portions=
 of the document need review from a particular or from broader perspective,=
 e.g., security, operational complexity, AAA, DNS, DHCP, XML, or internatio=
nalization? If so, describe the review
 that took place.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0This document addresses=C2=A0security, within the=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0framework set forth in RFC7182, and uses=C2=A0RFC6507</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0for the cryptographic functions. Both RFC7182 and</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0RFC6507 has received extensive scrutiny from the=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0security community.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0As such, the document shepherd believes that the</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0habitual SEC-DIR review for standards track documents</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0is expected=C2=A0=E2=80=94 but that no additional reviews are</font><=
/div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0necessary, nor beneficial.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(6) Describe an=
y specific concerns or issues that the Document Shepherd has with this docu=
ment that the Responsible Area Director and/or the IESG should be aware of?=
 For example, perhaps he or she is
 uncomfortable with certain parts of the document, or has concerns whether =
there really is a need for it. In any event, if the WG has discussed those =
issues and has indicated that it still wishes to advance the document, deta=
il those concerns here.</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The document shepherd raised, in his review,</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0(<a href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg167=
28.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/manet/curre=
nt/msg16728.html</a>)</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0the question of if=C2=A0=E2=80=9CUpdates RFC7182=E2=80=9D is appropri=
ate.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The document author and the document shepherd both</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0are=C2=A0=E2=80=9Con the balance=E2=80=9D as to if it is, or is not</=
font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial">
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0Both parties, however, =
believe that either way is=C2=A0<br>
</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0tolerable, and agreed t=
o seek advice from the=C2=A0</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0responsible AD on this =
particular matter</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0(<a href=3D"http://www.=
ietf.org/mail-archive/web/manet/current/msg16728.html" target=3D"_blank">ht=
tp://www.ietf.org/mail-archive/web/manet/current/msg16728.html</a>)</font><=
/div>
</div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The argument for=C2=A0=E2=80=9Cis not appropriate=E2=80=9D goes like =
this:</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial">
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 What thi=
s document does is:</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0(i)=C2=A0 only things permissible by RFC7182, and=C2=A0</font>=
</div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0(ii) makes registration from IANA registries=C2=A0</font></div=
>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 set up by RFC7182</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (noting, of course, that RFC7181 doesn=E2=80=99=
t=C2=A0</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=9CUpdates 5444=E2=80=9D=C2=A0when =
making registrations=C2=A0</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0for TC messages from the repositories</fo=
nt></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0set up by RFC5444 as a case of precedent)=
</font></div>
<div><font face=3D"Andale Mono"><br>
</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0The argument for=C2=A0=
=E2=80=9Cis appropriate=E2=80=9D is, that the=C2=A0</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0way this document inter=
prets=C2=A0&lt;key-id&gt; might not=C2=A0</font></div>
<div><font face=3D"Andale Mono">=C2=A0 =C2=A0 =C2=A0be as is described in R=
FC7182.</font></div>
</div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(7) Has each au=
thor confirmed that any and all appropriate IPR disclosures required for fu=
ll conformance with the provisions of BCP 78 and BCP 79 have already been f=
iled. If not, explain why?</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The author has confirmed to not be aware of any</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0IPR that requires disclosure regarding this specific</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0documents.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<p style=3D"font-family:Arial;background-color:rgb(255,255,255)"><font face=
=3D"Andale Mono">(8) Has an IPR disclosure been filed that references this =
document? If so, summarize any WG discussion and conclusion regarding the I=
PR disclosures.</font></p>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0There have been no IPR disclosures filed that</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0reference this document.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(9) How solid i=
s the WG consensus behind this document? Does it represent the strong concu=
rrence of a few individuals, with others being silent, or does the WG as a =
whole understand and agree with it?</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0As described under Working Group Summary, the</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0consensus behind this document appears quite solid.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(10) Has anyone=
 threatened an appeal or otherwise indicated extreme discontent? If so, ple=
ase summarise the areas of conflict in separate email messages to the Respo=
nsible Area Director. (It should be
 in a separate email because this questionnaire is publicly available.)</fo=
nt></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0There have been no threats of appeal raised, nor</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0has any extreme discontent been indicated.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(11) Identify a=
ny ID nits the Document Shepherd has found in this document. (See=C2=A0<a h=
ref=3D"http://www.ietf.org/tools/idnits/" target=3D"_blank">http://www.ietf=
.org/tools/idnits/</a>=C2=A0and the Internet-Drafts Checklist).
 Boilerplate checks are not enough; this check needs to be thorough.</font>=
</div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0IDNITS raises only concerns on a DOWNREF, addressed</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0in 15) below.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(12) Describe h=
ow the document meets any required formal review criteria, such as the MIB =
Doctor, media type, and URI type reviews.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0Such reviews are not required for this document.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(13) Have all r=
eferences within this document been identified as either normative or infor=
mative?</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0Yes.</font></div>
<p style=3D"font-family:Arial;background-color:rgb(255,255,255)"><font face=
=3D"Andale Mono">(14) Are there normative references to documents that are =
not ready for advancement or are otherwise in an unclear state? If such nor=
mative references exist, what
 is the plan for their completion?</font></p>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0No.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(15) Are there =
downward normative references references (see RFC 3967)? If so, list these =
downward references to support the Area Director in the Last Call procedure=
.</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0This document, intended for publication on std.=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0track, has a=C2=A0downref to RFC6507, which is published=C2=A0</font>=
</div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0as informational.=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0RFC6507 does not appear in the downrefergistry</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0(<a href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRe=
gistry" target=3D"_blank">http://trac.tools.ietf.org/group/iesg/trac/wiki/D=
ownrefRegistry</a>)</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0and must thus be explicitly called out in the=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0IETF Last Call.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(16) Will publi=
cation of this document change the status of any existing RFCs? Are those R=
FCs listed on the title page header, listed in the abstract, and discussed =
in the introduction? If the RFCs are
 not listed in the Abstract and Introduction, explain why, and point to the=
 part of the document where the relationship of this document to the other =
RFCs is discussed. If this information is not in the document, explain why =
the WG considers it unnecessary.=C2=A0</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0Advice from the=C2=A0responsible AD is sought on if=C2=A0</font></div=
>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0this document=C2=A0=E2=80=9CUpdates RFC7182=E2=80=9D, or not, as=C2=
=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0previously indicated.=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0If, on the responsible ADs=C2=A0advice, this document</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0updates RFC7182, then this is called out in the</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0appropriate places.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(17) Describe t=
he Document Shepherd&#39;s review of the IANA considerations section, espec=
ially with regard to its consistency with the body of the document. Confirm=
 that all protocol extensions that the
 document makes are associated with the appropriate reservations in IANA re=
gistries. Confirm that any referenced IANA registries have been clearly ide=
ntified. Confirm that newly created IANA registries include a detailed spec=
ification of the initial contents
 for the registry, that allocations procedures for future registrations are=
 defined, and a reasonable name for the new registry has been suggested (se=
e RFC 5226).</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0All protocol extensions that the document makes, are</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0associated with the appropriate reservations</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0Referenced IANA registries have been clearly=C2=A0</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0identified</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0No new IANA registries are created</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0The designated expert for the registry confirmed on</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A014/09/03 that he finds the registrations</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0requested in this document as aggreable:</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0<a href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg1691=
2.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/manet/curren=
t/msg16912.html</a></font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(18) List any n=
ew IANA registries that require Expert Review for future allocations. Provi=
de any public guidance that the IESG would find useful in selecting the IAN=
A Experts for these new registries.</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0No new IANA registries are created.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">(19) Describe r=
eviews and automated checks performed by the Document Shepherd to validate =
sections of the document written in a formal language, such as XML code, BN=
F rules, MIB definitions, etc.=C2=A0</font></div>

<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0No such checks=C2=A0required nor performed: no XML code,=C2=A0</font>=
</div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0BNF rules, MIB definitions, or other formal language=C2=A0</font></di=
v>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0for which automatic checks exist, is included in this=C2=A0</font></d=
iv>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono">=C2=A0 =C2=A0 =
=C2=A0document.</font></div>
<div style=3D"font-family:Arial"><font face=3D"Andale Mono"><br>
</font></div>
<div style=3D"font-family:Arial;font-size:medium"><font face=3D"Andale Mono=
"><br>
</font></div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div></div></div>

<br>_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>

--001a11c13986d938f20502402300--


From nobody Thu Sep  4 10:06:08 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFC241A006B for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 10:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.57
X-Spam-Level: 
X-Spam-Status: No, score=-107.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvzqNvy2uG7D for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 10:06:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2F41F1A0031 for <manet@ietf.org>; Thu,  4 Sep 2014 10:06:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4B678180450; Thu,  4 Sep 2014 10:05:12 -0700 (PDT)
To: macker@itd.nrl.navy.mil, akatlas@gmail.com, adrian@olddog.co.uk, sratliff@cisco.com, macker@itd.nrl.navy.mil
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140904170512.4B678180450@rfc-editor.org>
Date: Thu,  4 Sep 2014 10:05:12 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/G5XXI5ekGvQBtoxUL2l5XV2p3uk
Cc: manet@ietf.org, rfc-editor@rfc-editor.org
Subject: [manet] [Editorial Errata Reported] RFC6621 (4098)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 17:06:07 -0000

The following errata report has been submitted for RFC6621,
"Simplified Multicast Forwarding".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6621&eid=4098

--------------------------------------
Type: Editorial
Reported by: Joe Macker <jpmacker@gmail.com>

Section: Appendix B

Original Text
-------------
This distributed relay set selection technique has been shown to 
approximate a minimal connected dominating set (MCDS) in [JLMV02].

Corrected Text
--------------
This distributed relay set selection technique has been shown to 
approximate a minimum connected dominating set (MCDS) in [JLMV02].

Notes
-----
Minimum connected dominating set [1] is the established terminology and 
minimal was an editorial error.

[1] Sampathkumar, E.; Walikar, HB (1979), 
"The connected domination number of a graph", J. Math. Phys. Sci 13 (6): 607â€“613.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6621 (draft-ietf-manet-smf-14)
--------------------------------------
Title               : Simplified Multicast Forwarding
Publication Date    : May 2012
Author(s)           : J. Macker, Ed.
Category            : EXPERIMENTAL
Source              : Mobile Ad-hoc Networks
Area                : Routing
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Sep  4 14:17:01 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB7681A0175 for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 14:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T8A5L8hAcNyM for <manet@ietfa.amsl.com>; Thu,  4 Sep 2014 14:16:49 -0700 (PDT)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25C161A017A for <manet@ietf.org>; Thu,  4 Sep 2014 14:16:48 -0700 (PDT)
Received: by mail-yk0-f179.google.com with SMTP id 142so6406211ykq.24 for <manet@ietf.org>; Thu, 04 Sep 2014 14:16:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qj3FKBa357Wvtot29rHc/aM2qjdXC+91SIWo+/ukdXQ=; b=zUwakMAd9xkpmg9+yusfRlMPMy7hlvuX0EV9b63MSJJtRc/4yzlIG/uqFq7qYsj4lT Pd7jEWKZKMsh0RVvPj8LkHX8wPhbi2Q7lbOvhalLGsRD2xD9tZWTNCzV5YtYnUrIaNhT dRYypraA3Jyam49US8u2MquDl9g/scivgFZltIfxNEzuHNBx7Qm+ep3gamRNxIDMCTE9 790Vgu0LFCXtb+tQLZ6ZE2eAYNvXhYiIj5vPS9JswznLKkDm/MnXhbbQXGpSTgZotChN pZ41e2Y6P0YjUiTw74Tzw4VK1l2d6ccZhg3e9LGdirysEdgy6LjXFksKq2E+W+h1rUM1 ihbw==
MIME-Version: 1.0
X-Received: by 10.236.135.212 with SMTP id u60mr5452340yhi.118.1409865407429;  Thu, 04 Sep 2014 14:16:47 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Thu, 4 Sep 2014 14:16:47 -0700 (PDT)
In-Reply-To: <B9468E58D6A0A84AAD66FE4E694BEABB753AA46D@ucolhpkt.easf.csd.disa.mil>
References: <B9468E58D6A0A84AAD66FE4E694BEABB753AA46D@ucolhpkt.easf.csd.disa.mil>
Date: Thu, 4 Sep 2014 23:16:47 +0200
Message-ID: <CADnDZ8-JQTuWChLfCbVpEzw45aHP-cF9=cL_r76Qf+YW5KuygA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Cole, Robert G CIV USARMY CERDEC (US)" <robert.g.cole.civ@mail.mil>
Content-Type: multipart/alternative; boundary=20cf301af867ca83ad050243dece
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/M-xyDVr0NqAaADjkSKPSwhKnywU
Cc: manet <manet@ietf.org>, Andy Bierman <andy@yumaworks.com>, draft-ietf-manet-report-mib@tools.ietf.org
Subject: Re: [manet] REPORT-MIB --- update? (UNCLASSIFIED)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 21:16:56 -0000

--20cf301af867ca83ad050243dece
Content-Type: text/plain; charset=UTF-8

Hi Robert,

I am trying to track the discussions for this draft (not easy to track them
in IETF WG). However, I want to ask about the reason for changing draft
direction. There were some questions not answered/discussed by WG in
IETF meeting 87. Comments below,

On Tuesday, September 2, 2014, Cole, Robert G CIV USARMY CERDEC (US) wrote:

> Classification: UNCLASSIFIED
> Caveats: NONE
>
> To all:
>
> I did not want to comment on the questions regarding the status of the
> REPORT-MIB definition until I had pretty much wrapped up the SMF-MIB (which
> I believe is close to publication).


Do you mean Thomas's questions [2, 3]?


> With the permission of the working group and the chairs, I would like to
> proceed with the design and development of the REPORT-MIB?


I support that.


>
> The hold up over the last year has been the appropriate architecture for
> the REPORT-MIB.  It was initially designed following RMON II tables.  Last
> year Andy suggested (based upon conversations with others involved with the
> DISMAN WG years ago) that we should base the REPORT-MIB on the DISMAN base
> of MIBs.


Why was that suggestion appropriate? I tried to find the suggestion input
in IETF, but failed to find Andy's input. What is wrong with it based
on RMON?


>  I believe I now know how to accomplish this and I would like to rewrite
> the report-mib-04 within the context of the DISMAN MIBs, e.g., EVENT-MIB,
> EXPRESSION-MIB, etc.


I prefer we discuss it first because report-mob-03 is WG doc and not sure
of the answers of the questions you referred to (you may mean [1, 2,
3]). So I Disagree to change our work context before a reason discussion (I
may missed the discussion but still looking for it). I hope we start with
one new version -04 with only additions then we discuss changes in next
versions.


>
> So if this is OK with the group, I need a few weeks to work up the 04
> version of the REPORT-MIB draft and post by the end of September.


IMHO It is ok to add context not change/delete previous context if we have
not discussed.

Thanks for your input.
AB


[1]. http://www.ietf.org/mail-archive/web/manet/current/msg15963.html

[2]. http://www.ietf.org/mail-archive/web/manet/current/msg16503.html

[3]. Minutes of IETF 87 MANET WG meeting, (chair section, MANET management
section).

--20cf301af867ca83ad050243dece
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Robert,<div><br></div><div>I am trying to track the discussions for this=
 draft (not easy to track them in IETF WG).=C2=A0However, I want to ask abo=
ut the reason for changing draft direction. There were some questions not a=
nswered/discussed by WG in IETF=C2=A0meeting 87.=C2=A0Comments below,<br>
<br>On Tuesday, September 2, 2014, Cole, Robert G CIV USARMY CERDEC (US)  w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Classification: UNCLASSIFIED<br>

Caveats: NONE<br>
<br>
To all:<br>
<br>
I did not want to comment on the questions regarding the status of the REPO=
RT-MIB definition until I had pretty much wrapped up the SMF-MIB (which I b=
elieve is close to publication).</blockquote><div><br></div><div>Do you mea=
n Thomas&#39;s questions=C2=A0[2, 3]?</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<br>
With the permission of the working group and the chairs, I would like to pr=
oceed with the design and development of the REPORT-MIB?</blockquote><div><=
br></div>I support that.=C2=A0<br><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">



<br>
The hold up over the last year has been the appropriate architecture for th=
e REPORT-MIB.=C2=A0 It was initially designed following RMON II tables.=C2=
=A0 Last year Andy suggested (based upon conversations with others involved=
 with the DISMAN WG years ago) that we should base the REPORT-MIB on the DI=
SMAN base of MIBs.=C2=A0</blockquote>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"></blockquote><div><br></div><div>Why was tha=
t suggestion appropriate? I tried to find the suggestion input in IETF,=C2=
=A0but failed to find Andy&#39;s=C2=A0input. What is wrong with it=C2=A0bas=
ed on=C2=A0RMON?</div>


<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">=C2=A0I believe I now know =
how to accomplish this and I would like to rewrite the report-mib-04 within=
 the context of the DISMAN MIBs, e.g., EVENT-MIB, EXPRESSION-MIB, etc.</blo=
ckquote>


<div><br></div><div>I prefer we discuss it first because report-mob-03 is W=
G doc and not sure of the answers of the questions you=C2=A0referred to (yo=
u may=C2=A0mean [1, 2, 3]).=C2=A0So I=C2=A0Disagree to change our work cont=
ext before a=C2=A0reason=C2=A0discussion (I may missed the discussion but s=
till looking for it). I hope we start with one new version -04 with only ad=
ditions then we discuss changes in next versions.=C2=A0</div>

<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So if this is OK with the group, I need a few weeks to work up the 04 versi=
on of the REPORT-MIB draft and post by the end of September.</blockquote><d=
iv><br></div><div>IMHO=C2=A0It is ok to add context not change/delete previ=
ous context if we have not discussed.=C2=A0</div>

<div><br></div><div>Thanks for your input.=C2=A0</div><div>AB</div><div><br=
></div><div><br></div><div>[1].=C2=A0<a href=3D"http://www.ietf.org/mail-ar=
chive/web/manet/current/msg15963.html">http://www.ietf.org/mail-archive/web=
/manet/current/msg15963.html</a></div>
<div><br></div><div>[2].=C2=A0<a href=3D"http://www.ietf.org/mail-archive/w=
eb/manet/current/msg16503.html">http://www.ietf.org/mail-archive/web/manet/=
current/msg16503.html</a></div><div><br></div><div>[3]. Minutes of IETF 87=
=C2=A0MANET WG=C2=A0meeting,=C2=A0(chair section,=C2=A0MANET management sec=
tion).=C2=A0</div>

</div>

--20cf301af867ca83ad050243dece--


From nobody Fri Sep  5 07:51:07 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED6911A0705; Fri,  5 Sep 2014 07:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tj3KF7MBc2uF; Fri,  5 Sep 2014 07:51:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C0221A0703; Fri,  5 Sep 2014 07:50:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140905145058.30100.85477.idtracker@ietfa.amsl.com>
Date: Fri, 05 Sep 2014 07:50:58 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ueeR62-204q8tqzf7RhoqwZz73I
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-nhdp-optimization-03.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 14:51:03 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

        Title           : An Optimization for the MANET Neighborhood Discovery Protocol (NHDP)
        Authors         : Christopher Dearlove
                          Thomas Heide Clausen
	Filename        : draft-ietf-manet-nhdp-optimization-03.txt
	Pages           : 10
	Date            : 2014-09-05

Abstract:
   The link quality mechanism of the MANET Neighborhood Discovery
   Protocol (NHDP) enables "ignoring" some 1-hop neighbors if the
   measured link quality from that 1-hop neighbor is below an acceptable
   threshold, while still retaining the corresponding link information
   as acquired from HELLO message exchange.  This allows immediate
   reinstatement of the 1-hop neighbor if the link quality later
   improves sufficiently.

   NHDP also collects information about symmetric 2-hop neighbors.
   However it specifies that if a link from a symmetric 1-hop neighbor
   ceases being symmetric, including while "ignored" as described above,
   then corresponding symmetric 2-hop neighbors are removed.  This may
   lead to symmetric 2-hop neighborhood information being permanently
   removed (until further HELLO messages are received) if the link
   quality of a symmetric 1-hop neighbor drops below the acceptable
   threshold, even if only for a moment.

   This specification updates RFC6130 "Mobile Ad Hoc Network (MANET)
   Neighborhood Discovery Protocol (NHDP)", and RFC7181 "The Optimized
   Link State Routing Protocol version 2 (OLSRv2)" to permit retaining,
   but ignoring, symmetric 2-hop information when the link quality from
   the corresponding 1-hop neighbor drops below the acceptable
   threshold.  This allows immediate reinstatement of the symmetric
   2-hop neighbor if the link quality later improves sufficiently, thus
   making the symmetric 2-hop neighborhood more "robust".


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-optimization/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-manet-nhdp-optimization-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-nhdp-optimization-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Sep  5 07:57:07 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A105F1A06F6 for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 07:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.567
X-Spam-Level: 
X-Spam-Status: No, score=-7.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xZU6eEEGjyiV for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 07:57:02 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAB051A02FC for <manet@ietf.org>; Fri,  5 Sep 2014 07:57:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.04,473,1406588400";  d="scan'208,217";a="400954589"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 05 Sep 2014 15:56:59 +0100
X-IronPort-AV: E=Sophos; i="5.04,473,1406588400"; d="scan'208,217"; a="71945636"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasodc005.greenlnk.net with ESMTP; 05 Sep 2014 15:56:59 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.140]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.03.0174.001; Fri, 5 Sep 2014 15:56:59 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: New version of NHDP optimisation
Thread-Index: Ac/JGXRDDO7KaynjRXGpUc2L5NkaFQ==
Date: Fri, 5 Sep 2014 14:56:58 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479DGLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/Ox_yEbrcdQixKhqwidqnw-jeWPg
Subject: [manet] New version of NHDP optimisation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 14:57:04 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479DGLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

One small change (of a false to a true) pointed out by Ulrich. I'm not awar=
e of anything else that needs auctioning, please let me (or Thomas, as I am=
 taking a week's break in which I'll try not to check here) know if not.

--
Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

********************************************************************
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.
********************************************************************

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479DGLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">One small change (of a false to a true) pointed out =
by Ulrich. I&#8217;m not aware of anything else that needs auctioning, plea=
se let me (or Thomas, as I am taking a week&#8217;s break in which I&#8217;=
ll try not to check here) know if not.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">-- <o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christopher Dearlove<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Senior Principal Engin=
eer, Information Assurance Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: &#43;44 1245 242194&nbsp;|&nbsp; Fax: &#43;44 1245 242124<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"mailto:chri=
s.dearlove@baesystems.com"><span style=3D"color:#1F497D;text-decoration:non=
e">chris.dearlove@baesystems.com</span></a> | http://www.baesystems.com<br>
<br>
</span><span style=3D"color:#1F497D">BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479DGLKXM0002VGREEN_--


From nobody Fri Sep  5 08:17:13 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC461A0713 for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 08:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MzmQyH4IwtMt for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 08:17:11 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44A3C1A0712 for <manet@ietf.org>; Fri,  5 Sep 2014 08:17:11 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id i17so12313567qcy.5 for <manet@ietf.org>; Fri, 05 Sep 2014 08:17:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=sx421ZEOUI3OCM6s8bcfM5h9fONYbHBQbQFq0jwr2CM=; b=ftfOaupjmkmtf5XrXXPSqM9lbGLC/AQ1XwMbDlmD409AI0tUzoykgnxvs/ttx5I6wi ZFX3ytzMpFpTuGjRecpbmuzc1MNsj2a5NXXjvDWvpWU5G6hnHzW9JrevM1sRCLmEvDf9 Xw48K6OX+/wE4w+CyjpdGi0eEuH9ABCN6NRwsLAHDIPVRdCk1mdnqGyHYMnUsuhsqdQT 4hCq1l9JpliS0i8slHfgb4UIYOxHKz16h9FVdbgIdQaIZ0fZt2xp7ljPXrH2x5Q/CcdZ vOBRVwNkl0RztN2PBZBIXtC29quwKmACuU1JoBCaoRMDTgsMk6U+r+dPEdtEenIER5iT 33hA==
X-Received: by 10.140.106.66 with SMTP id d60mr1062762qgf.23.1409930229867; Fri, 05 Sep 2014 08:17:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Fri, 5 Sep 2014 08:16:48 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 5 Sep 2014 17:16:48 +0200
Message-ID: <CAGnRvur99U4Vh2bDRik79yZ_-EapieHkgyd8_X2CxZhxqxd-LA@mail.gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/JBu11vOKA6Njz2RwGL0UeGsFDMs
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] New version of NHDP optimisation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 15:17:12 -0000

On Fri, Sep 5, 2014 at 4:56 PM, Dearlove, Christopher (UK)
<chris.dearlove@baesystems.com> wrote:
> One small change (of a false to a true) pointed out by Ulrich. I=E2=80=99=
m not aware
> of anything else that needs auctioning, please let me (or Thomas, as I am
> taking a week=E2=80=99s break in which I=E2=80=99ll try not to check here=
) know if not.

Just as a comment, this HTML-Mail was displayed nearly unreadable in Linux.=
..

Henning


From nobody Fri Sep  5 09:36:00 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB231A0AE1 for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 09:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFe5R8x96cdb for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 09:35:58 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D80311A0739 for <manet@ietf.org>; Fri,  5 Sep 2014 09:35:57 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id n3so48322wiv.17 for <manet@ietf.org>; Fri, 05 Sep 2014 09:35:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:mime-version:content-type:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kkbGw/iIXYMcqGH0/6eOiezgbcG4XQmU2BzWTbte+6I=; b=aJgL16nxz3KpDSzlktvXHQPZOepwjlHYR4cDtaGEYWf1CR5AC6lH+7QfGTcJMf6NW5 yjnKas3OnDQ9o41k0pCTZzhJuyheTLzuQyxB91WF0TLzxziWU6LK03wLWhxNCTkUwY76 unP7EntAFFULhCWmzkHHusCSNbYz7FO99Ns1lcb+HLwz1r5zX7YbDwD0KKWhkhpt3fdU EfA8QWYTDbyIaUjhIyOspjBS14yqLRVLZiI95MOyNzEYADWnHaoTDhqTaOfsUGMRbC6+ qFLVqatEzdyrdlWY6BBgQsQb7Ac6104bNJMhjCqWqV1PvATW+FldQ6uYvUoE3/X943RR CE3A==
X-Received: by 10.180.9.144 with SMTP id z16mr5203737wia.26.1409934956481; Fri, 05 Sep 2014 09:35:56 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id fc3sm2359478wib.6.2014.09.05.09.35.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Sep 2014 09:35:55 -0700 (PDT)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
X-Google-Original-From: Christopher Dearlove <chris@mnemosyne.demon.co.uk>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <CAGnRvur99U4Vh2bDRik79yZ_-EapieHkgyd8_X2CxZhxqxd-LA@mail.gmail.com>
Date: Fri, 5 Sep 2014 17:35:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F72EA4AC-38B9-439C-B488-27499129B127@mnemosyne.demon.co.uk>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net> <CAGnRvur99U4Vh2bDRik79yZ_-EapieHkgyd8_X2CxZhxqxd-LA@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/NWFOJeQSIIZ4uR4iPxbwNNuu330
Cc: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] New version of NHDP optimisation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 16:35:59 -0000

On 5 Sep 2014, at 16:16, Henning Rogge wrote:
> Just as a comment, this HTML-Mail was displayed nearly unreadable in =
Linux...

Odd, nothing done differently than usual (excepting the cases I change =
to plain text, which I do inconsistently), done with a standard tool =
(Outlook) and reads fine on this Unix (Mac) machine.=


From nobody Fri Sep  5 09:48:13 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A55A1A071C for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 09:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n7GVYL6CoIXh for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 09:48:06 -0700 (PDT)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C02F1A0464 for <manet@ietf.org>; Fri,  5 Sep 2014 09:48:06 -0700 (PDT)
Received: by mail-qa0-f49.google.com with SMTP id s7so7231976qap.22 for <manet@ietf.org>; Fri, 05 Sep 2014 09:48:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5CtmEGlU2BWUcwT8HGJE7MhWKvBd7gJzwUY4WfxKojQ=; b=JNMmakc3XDxZqaJ5v3JT8sP2LfvcAPU16OZlzlqESR+KoeLmvJvFVgV1UyhsPc9OH9 tEp1FpReyHgcq3SX1Dm9zoxzIX+yv6BSFPxCUjKfq3USzO3H8fGIIkUpU39+ue8Pr/Ja 9xuDfKoMuusD0NxfzQcV2QAuMpk07t9bNJ+d2cCsfGXUzL5W6r+74Z1U0KNV+xLdJzDR ijfZKimMRsW4N9gbV60tKwP9a97H8aBvwWIFnolMUHGdJe04o33ODYAb3nq90+39kYJS Yjmqokl9BFi1+dMQLzbDClnxoRQeXDFIRDJVC9SploIVkY0wKdj2STorPIrG+arfktyj RTlA==
X-Received: by 10.140.106.66 with SMTP id d60mr1763054qgf.23.1409935684543; Fri, 05 Sep 2014 09:48:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Fri, 5 Sep 2014 09:47:44 -0700 (PDT)
In-Reply-To: <F72EA4AC-38B9-439C-B488-27499129B127@mnemosyne.demon.co.uk>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net> <CAGnRvur99U4Vh2bDRik79yZ_-EapieHkgyd8_X2CxZhxqxd-LA@mail.gmail.com> <F72EA4AC-38B9-439C-B488-27499129B127@mnemosyne.demon.co.uk>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 5 Sep 2014 18:47:44 +0200
Message-ID: <CAGnRvuon=RVRRHn35MHF=OBJMu3nYcD_w02nuaTmpQ4m1KWGXQ@mail.gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/RofutA_TidmnOxs0Gboe4Pp6rLQ
Cc: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] New version of NHDP optimisation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 16:48:08 -0000

https://drive.google.com/file/d/0B73bEek-LDc5d2dBYldIM0FjdTA/edit?usp=sharing

Thats how it looked on GMail (on Chrome on Linux)... ^^

Henning

On Fri, Sep 5, 2014 at 6:35 PM, Christopher Dearlove
<christopher.dearlove@gmail.com> wrote:
> On 5 Sep 2014, at 16:16, Henning Rogge wrote:
>> Just as a comment, this HTML-Mail was displayed nearly unreadable in Linux...
>
> Odd, nothing done differently than usual (excepting the cases I change to plain text, which I do inconsistently), done with a standard tool (Outlook) and reads fine on this Unix (Mac) machine.


From nobody Fri Sep  5 10:59:37 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132F31A0AF8 for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 10:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeN9Czwzttez for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 10:59:33 -0700 (PDT)
Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C9C61A0AE9 for <manet@ietf.org>; Fri,  5 Sep 2014 10:59:33 -0700 (PDT)
Received: by mail-yk0-f174.google.com with SMTP id 10so7247631ykt.33 for <manet@ietf.org>; Fri, 05 Sep 2014 10:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+SdqCBY2j0WSF0GyyKTxz5yopZOASDO08skumpmIugo=; b=Bb6cugUzXaRVfMhUj9fb9tJzXKbSSbXcxVlZ2J9tIWcL/cc5FeUY4kahRmevZ+PGEY di7zICgymigOiua8ysIrT8+IAd+Jwn52TBrsHrz92xBq+zs2leAzRbK+ox05K1+C2NUJ +PY5NCmFuPpOAhZv9dNcfwNz1dxqzDhGFie2YcFwUjVN89bLqr3py9KYXtCgRGnI3tMs M9XZHU5shuO2pmGq0mjfkcdtMTQ4W15pyYbNq4N/3B0Va2wAlEpZzyf/aJ76WSgVdKhl ITrCwIvmk7yiVeFQplUnYbDyZeGgqq64T4aAYJoBUXflS9bHNCCUA4g40ytOVZ6waJYO 5T/A==
MIME-Version: 1.0
X-Received: by 10.236.131.194 with SMTP id m42mr5109695yhi.31.1409939972778; Fri, 05 Sep 2014 10:59:32 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 5 Sep 2014 10:59:32 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net>
Date: Fri, 5 Sep 2014 19:59:32 +0200
Message-ID: <CADnDZ8-0AXJeEjfL4cfSbsYh=H5iqxm4wRO0ovzXVL53M9kd8g@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=20cf301b67253b719b0502553bc2
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/F4M1JUnxYkf86N8vk7WthzNbxJ4
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: [manet]  New version of NHDP optimisation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 17:59:36 -0000

--20cf301b67253b719b0502553bc2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I was disappointed after my analysis, however, it is good we can see
some progress. Editors may think that it is small change but in the routing
world it is not small. I was using that in my analysis that you may not
understood and you were responding as that my analysis was not correct [1].
Now authors/someone may recognised their error in the draft after my
analysis which was refused by WG editor [1]. I hope that future WG editors
consider all participants' inputs without refusing any analysis until they
have made sure they have no mistakes.

Thanks that you made a change.

AB

[1] http://www.ietf.org/mail-archive/web/manet/current/msg16868.html

On Friday, September 5, 2014, Dearlove, Christopher (UK) wrote:

>  One small change (of a false to a true) pointed out by Ulrich.
>
>
Not small change  for me. I don't see Ulrich's input, but it is after my
analysis which he may recognised. Thanks Ulrich.


>  I=E2=80=99m not aware of anything else that needs auctioning, please let=
 me (or
> Thomas, as I am taking a week=E2=80=99s break in which I=E2=80=99ll try n=
ot to check here)
> know if not.
>
>
>
> --
>
> Christopher Dearlove
>
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
>
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
>
> ********************************************************************
> 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.
> ********************************************************************
>

--20cf301b67253b719b0502553bc2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I was disappointed after my analysis, however, it is good we can see some=
=C2=A0progress.=C2=A0Editors<span></span>=C2=A0may think that=C2=A0it is sm=
all change=C2=A0but in the routing world it is not small. I was using that =
in my analysis that you may=C2=A0not understood and you were responding as =
that my analysis was not correct [1]. Now authors/someone=C2=A0may=C2=A0rec=
ognised their=C2=A0error in the draft after my analysis which was refused b=
y WG editor [1]. I hope that future WG=C2=A0editors consider all participan=
ts&#39; inputs=C2=A0without refusing any=C2=A0analysis until they have made=
 sure they have no mistakes.=C2=A0<div><br></div><div>Thanks that you made =
a=C2=A0change.=C2=A0<br><span></span><div><br></div><div>AB</div><div><br><=
/div><div>[1]=C2=A0<a href=3D"http://www.ietf.org/mail-archive/web/manet/cu=
rrent/msg16868.html">http://www.ietf.org/mail-archive/web/manet/current/msg=
16868.html</a><br><br>On Friday, September 5, 2014, Dearlove, Christopher (=
UK)  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">One small change (of a false to a true) pointed out =
by Ulrich.</p><p class=3D"MsoNormal"></p></div></div></blockquote><div><br>=
</div><div>Not small change=C2=A0=C2=A0for me. I=C2=A0don&#39;t see Ulrich&=
#39;s input, but it is after my analysis which he may recognised. Thanks Ul=
rich.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lan=
g=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal">=C2=
=A0I=E2=80=99m not aware of anything else that needs auctioning, please let=
 me (or Thomas, as I am taking a week=E2=80=99s break in which I=E2=80=99ll=
 try not to check here) know if not.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">-- <u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">Christopher Dearlove<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">Senior Principal Engin=
eer, Information Assurance Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: +44 1245 242194=C2=A0|=C2=A0 Fax: +44 1245 242124<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><a><span style=3D"colo=
r:#1f497d;text-decoration:none">chris.dearlove@baesystems.com</span></a> | =
<a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesyste=
ms.com</a><br>
<br>
</span><span style=3D"color:#1f497d">BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></d=
iv>

</blockquote></div>
</div>

--20cf301b67253b719b0502553bc2--


From nobody Fri Sep  5 11:04:04 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46A4A1A0B79 for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 11:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uTztADwNvfOa for <manet@ietfa.amsl.com>; Fri,  5 Sep 2014 11:03:57 -0700 (PDT)
Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com [IPv6:2607:f8b0:4002:c07::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1BFA1A02E2 for <manet@ietf.org>; Fri,  5 Sep 2014 11:03:56 -0700 (PDT)
Received: by mail-yk0-f170.google.com with SMTP id 142so7330821ykq.29 for <manet@ietf.org>; Fri, 05 Sep 2014 11:03:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m67yYIpazG0/oR6QVsqf6Eux2y7S+TB4j5WX2dmuS7U=; b=HhDYD1UFUjmEEc6DhXWHh6sdp9diTtOHu9Lby9cBGo7S2VN0E0OcXdSxIrJwqE+h2L x0HkWz0U9XxZpingGPTuXq7Cl/J4qXw5jQtB61p26WO8SzzMsDgUUIEVW25ljpVK9MeA qFJvCBxxBiDzaPqIAa5fo82cm3/tTHnjnoBIdjTbnOY4uFghEzL7dQrziDlIh6aTZyoo 6MipMFTCnv0WQq0DwLLIyJscfld73W8+zmB9y1UytJnmhNmxklra1Mrcw49Wa/QKWmgj xU00VDvkaBWHt2DxKt2uQ4gnHvnOqPCCxccSxfMy3Fw0kAIwfWsO7rWGL+VDa387Vl65 ODaw==
MIME-Version: 1.0
X-Received: by 10.236.67.73 with SMTP id i49mr13672057yhd.17.1409940235902; Fri, 05 Sep 2014 11:03:55 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 5 Sep 2014 11:03:55 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D20BE1@GLKXM0002V.GREENLNK.net>
References: <066.245678a3beb580a2324b5f543ed942a8@trac.tools.ietf.org> <3EF88342-669E-47F9-BCB4-C45BFBC7B217@mnemosyne.demon.co.uk> <CADnDZ8-=GYqS07xynbBOY6KK8fbd-fFor-i1UrAuT2R6VUtd7g@mail.gmail.com> <037A3801-B720-472A-ACB9-0785E5571244@thomasclausen.org> <CADnDZ88Axh45F8NN74zg=n2YDhLoH+D9-FgfVoDpshLFTgvyGw@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D20348@GLKXM0002V.GREENLNK.net> <CADnDZ8_N+FdjWTdHCsuJRqfgGaAhXjKgFMgAQZe+b6m0GtT45g@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D203F5@GLKXM0002V.GREENLNK.net> <CADnDZ89v8B7A3a=OeZ=gAf_28vbeyNR3yTqYVpESWFYUEyOZ-Q@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D20BE1@GLKXM0002V.GREENLNK.net>
Date: Fri, 5 Sep 2014 20:03:55 +0200
Message-ID: <CADnDZ88WqVC9WGk_o5cvQ7XaWtqJJUB_7z3Pp-DBbb3Ay0OubQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=089e01176241ea69750502554af0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/hm6L5xM2x21I2XxdKs3wMEhuQoE
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #51 (nhdp-optimization): Analysis of OLSRv2/NHDP-optimized Handling neighbor connection with link quality change
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 18:04:01 -0000

--089e01176241ea69750502554af0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thursday, August 14, 2014, Dearlove, Christopher (UK) wrote:

>  The flaws in your analysis have been pointed out several times. I=E2=80=
=99m not
> going to repeat them.
>
>
>
>
You made today an important change and revision to the draft. Thanks for
changes to the flaw in the draft. I will do another analysis to see if
there is no more.

AB

> --
>
> Christopher Dearlove
>
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
>
> chris.dearlove@baesystems.com
> <javascript:_e(%7B%7D,'cvml','chris.dearlove@baesystems.com');> |
> http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
>
> *From:* Abdussalam Baryun [mailto:abdussalambaryun@gmail.com
> <javascript:_e(%7B%7D,'cvml','abdussalambaryun@gmail.com');>]
> *Sent:* 14 August 2014 06:27
> *To:* Dearlove, Christopher (UK)
> *Cc:* Thomas Clausen; Christopher Dearlove; manet@ietf.org
> <javascript:_e(%7B%7D,'cvml','manet@ietf.org');>
> *Subject:* [manet] #51 (nhdp-optimization): Analysis of
> OLSRv2/NHDP-optimized Handling neighbor connection with link quality chan=
ge
>
>
>
> WG to analyse the packet loss problem for this optimization. All MANETs
> have packet lost but the proposed optimized routers need to avoid its
> possible increase.
>
> On Monday, August 11, 2014, Dearlove, Christopher (UK) wrote:
>
> There is no need (or even advantage) to change (amending suggests a
> problem, which there isn=E2=80=99t) the draft based on anything you have =
posted.
>
> You did not analyse by saying no need or isn't a problem. IMHO there is
> the packet loss problem because router A when recovered it considers C as
> reached through B but B has the link B-C as lost. The optimization
> improves packet delay issues but increases packet loss or decreases
> average delivery rate for the MANET that has many optimiz-routers.
>
>
>
> There isn=E2=80=99t even anything that could be changed because, and let=
=E2=80=99s say it
> again, link quality information is not communicated.
>
>  This draft has no update to nhdp's information
> exchange communication, and I did not mention communication. The
> performance difference between normal router and optimize-router is withi=
n
> packet-delay and packet-loss. However, the draft gives the opportunity
> that each optimize-router may change its link information which may loose
> consistency with its neighbours' information, so packets can get lost wit=
h
> higher possibility. I will look into the draft's update
> of nhdp/olsv2 algorithm and see if I can solve the issue without
> communicating any info.
>
>
>
> AB
>
>
>
> ********************************************************************
> 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.
> ********************************************************************
>

--089e01176241ea69750502554af0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Thursday, August 14, 2014, Dearlove, Christopher (UK)  wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The flaws in your analysi=
s have been pointed out several times. I=E2=80=99m not going to repeat them=
.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"></p></div></div></blockquote><div><br></div><d=
iv>You made today an important change and revision to the draft. Thanks for=
 changes to the flaw in the draft. I will do another analysis to see if the=
re is no more.=C2=A0=C2=A0</div><div><br></div><div>AB=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><d=
iv><p class=3D"MsoNormal"></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">--
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Christopher Dearlove<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Senior Principal Engineer=
, Information Assurance Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: +44 1245 242194=C2=A0|=C2=A0 Fax: +44 1245 242124<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><a href=3D"javascript:_e(=
%7B%7D,&#39;cvml&#39;,&#39;chris.dearlove@baesystems.com&#39;);" target=3D"=
_blank"><span style=3D"color:#1f497d;text-decoration:none">chris.dearlove@b=
aesystems.com</span></a>
 | <a href=3D"http://www.baesystems.com" target=3D"_blank">http://www.baesy=
stems.com</a><br>
<br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1f497d">BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Abdussalam Baryun [mailto:<a href=3D"javascript:_e(%7=
B%7D,&#39;cvml&#39;,&#39;abdussalambaryun@gmail.com&#39;);" target=3D"_blan=
k">abdussalambaryun@gmail.com</a>]
<br>
<b>Sent:</b> 14 August 2014 06:27<br>
<b>To:</b> Dearlove, Christopher (UK)<br>
<b>Cc:</b> Thomas Clausen; Christopher Dearlove; <a href=3D"javascript:_e(%=
7B%7D,&#39;cvml&#39;,&#39;manet@ietf.org&#39;);" target=3D"_blank">manet@ie=
tf.org</a><br>
<b>Subject:</b> [manet] #51 (nhdp-optimization): Analysis of OLSRv2/NHDP-op=
timized Handling neighbor connection with link quality change<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">WG to analyse the packet loss problem for this optim=
ization. All MANETs have packet lost but the proposed=C2=A0optimized=C2=A0r=
outers need to avoid its possible=C2=A0increase.=C2=A0<br>
<br>
On Monday, August 11, 2014, Dearlove, Christopher (UK) wrote:<u></u><u></u>=
</p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is no need (or even=
 advantage) to change (amending suggests a problem, which there isn=E2=80=
=99t) the
 draft based on anything you have posted.</span><u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">You did not analyse by saying no need or isn&#39;t a=
 problem.=C2=A0IMHO there=C2=A0is the=C2=A0packet loss problem because rout=
er A when recovered it considers C as reached through B=C2=A0but B has the =
link B-C as lost. The optimization improves=C2=A0packet delay issues
 but increases packet loss or decreases average=C2=A0delivery rate for the=
=C2=A0MANET that has many optimiz-routers.=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There isn=E2=80=99t even =
anything that could be changed because, and let=E2=80=99s say it again, lin=
k quality information
 is not communicated.=C2=A0</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">This draft has no update to nhdp&#39;s=C2=A0informat=
ion exchange=C2=A0communication,=C2=A0and I did not mention communication. =
The performance difference between normal router and optimize-router is wit=
hin packet-delay and packet-loss.=C2=A0However, the draft
 gives the opportunity that=C2=A0each optimize-router=C2=A0may change its l=
ink=C2=A0information which may loose consistency with its neighbours&#39; i=
nformation, so packets can get lost with higher possibility.=C2=A0I will lo=
ok into the draft&#39;s update of=C2=A0nhdp/olsv2=C2=A0algorithm and see
 if I can solve the issue without communicating any info.=C2=A0<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">AB<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></d=
iv>

</blockquote>

--089e01176241ea69750502554af0--


From nobody Sat Sep  6 04:21:03 2014
Return-Path: <ulrich@herberg.name>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92C601A02E5 for <manet@ietfa.amsl.com>; Sat,  6 Sep 2014 04:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.323
X-Spam-Level: *
X-Spam-Status: No, score=1.323 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dp24zgkvKpOa for <manet@ietfa.amsl.com>; Sat,  6 Sep 2014 04:21:00 -0700 (PDT)
Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB5951A0053 for <manet@ietf.org>; Sat,  6 Sep 2014 04:20:59 -0700 (PDT)
Received: by mail-vc0-f178.google.com with SMTP id la4so13497448vcb.37 for <manet@ietf.org>; Sat, 06 Sep 2014 04:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=K2S3o2AYTTKBKWMxRQOTcNuIu8fZhhMUGkuOnkqeK/8=; b=mGuo1l8rsgQiUPJjnn+TaJVJ0wiyAHa92N13DC46vv+jwLVHpTteUgCwf2yd+230Le oCyK+/zQ9SoMFQBuzlEvlWhJ2S0l8KGgKLa8aKqiykfEKrqm8oAkeWMs8GwNV4nJTDCv 9keTJoV50akYd0zCeT2ARjT5+P6PfNb4lyJpQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=K2S3o2AYTTKBKWMxRQOTcNuIu8fZhhMUGkuOnkqeK/8=; b=Y+vEl6JHxjsBqxKgFRPudDNyczTUOnYqOEX2tVuJulF0J5fisXOzMsFVoFLWgparRt jePPkkicp/eJRSnqVE4d5rTqOgWHoqYpCJVzKf6yGIjGAgcWaLPRGzCADOgkALWgskvK JPtATgBy5nJ74xmNpOvMNikD0HANBcNGdyLKng8lZ4H4C6Q4UEotYJFrtm/C98Vpl9wo px1scggXjdwiJeGcitIWgIwn+XT29EfX6f+jY8FoUV6po2Cvy12NpDy0IlKdCzSkn4U9 x6Idqdg4fLyoTV4TA98bCr8Yyn7hZx7AgOeJlvvUfx29GYqW60g8t+7t9nlbPoE7Ydny y6mg==
X-Gm-Message-State: ALoCoQlcM4c0kT8WMB6xkTHFj817LCSyhEiQpJ/U80S2yTufcrLLRnb5KmUwaav1J5lu7bWZsrfW
MIME-Version: 1.0
X-Received: by 10.52.102.204 with SMTP id fq12mr12811284vdb.26.1410002458462;  Sat, 06 Sep 2014 04:20:58 -0700 (PDT)
Received: by 10.220.70.196 with HTTP; Sat, 6 Sep 2014 04:20:58 -0700 (PDT)
Received: by 10.220.70.196 with HTTP; Sat, 6 Sep 2014 04:20:58 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D3479D@GLKXM0002V.GREENLNK.net>
Date: Sat, 6 Sep 2014 13:20:58 +0200
Message-ID: <CAK=bVC8wmuJrhXei=D3ctdxMDPRhfxotO4szxyNqNW5H6u3z9w@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: Christopher Dearlove <chris.dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=001a1133ee10ab6677050263c7f1
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/VjPOCFjDjHiF68tpQmB6mRgx01E
Cc: manet@ietf.org
Subject: Re: [manet] New version of NHDP optimisation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Sep 2014 11:21:01 -0000

--001a1133ee10ab6677050263c7f1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks for fixing this. I will proceed with the write-up.

Regards
Ulrich
On Sep 5, 2014 4:57 PM, "Dearlove, Christopher (UK)" <
chris.dearlove@baesystems.com> wrote:

>  One small change (of a false to a true) pointed out by Ulrich. I=E2=80=
=99m not
> aware of anything else that needs auctioning, please let me (or Thomas, a=
s
> I am taking a week=E2=80=99s break in which I=E2=80=99ll try not to check=
 here) know if not.
>
>
>
> --
>
> Christopher Dearlove
>
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
>
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
>
> ********************************************************************
> 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
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--001a1133ee10ab6677050263c7f1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Thanks for fixing this. I will proceed with the write-up.</p=
>
<p dir=3D"ltr">Regards<br>
Ulrich</p>
<div class=3D"gmail_quote">On Sep 5, 2014 4:57 PM, &quot;Dearlove, Christop=
her (UK)&quot; &lt;<a href=3D"mailto:chris.dearlove@baesystems.com">chris.d=
earlove@baesystems.com</a>&gt; wrote:<br type=3D"attribution"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">One small change (of a false to a true) pointed out =
by Ulrich. I=E2=80=99m not aware of anything else that needs auctioning, pl=
ease let me (or Thomas, as I am taking a week=E2=80=99s break in which I=E2=
=80=99ll try not to check here) know if not.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">-- <u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">Christopher Dearlove<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">Senior Principal Engin=
eer, Information Assurance Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194" value=3D"+441245242194" target=
=3D"_blank">+44 1245 242194</a>=C2=A0|=C2=A0 Fax: <a href=3D"tel:%2B44%2012=
45%20242124" value=3D"+441245242124" target=3D"_blank">+44 1245 242124</a><=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><a href=3D"mailto:chri=
s.dearlove@baesystems.com" target=3D"_blank"><span style=3D"color:#1f497d;t=
ext-decoration:none">chris.dearlove@baesystems.com</span></a> | <a href=3D"=
http://www.baesystems.com" target=3D"_blank">http://www.baesystems.com</a><=
br>
<br>
</span><span style=3D"color:#1f497d">BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></d=
iv>

<br>_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div>

--001a1133ee10ab6677050263c7f1--


From nobody Sun Sep  7 13:21:48 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5D331A06B7 for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 13:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HZriUkMwf0O for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 13:21:45 -0700 (PDT)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D4AA1A06FB for <manet@ietf.org>; Sun,  7 Sep 2014 13:21:44 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id f10so876924yha.11 for <manet@ietf.org>; Sun, 07 Sep 2014 13:21:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cttRWD9cmi+c3eSvNSnhMw/yjHGZx+2fCPheOl7RuLg=; b=RysI/mxBTDrY8fUg7CSd6iIZUem+gc5VxDPdmpyh2X8gCT4gKYjzKL3cj1bQ2CF99z KnnIC+2t8w3l9GdK0AoSmPx5U/EJHr0/Xe/SuilrAyWQ8I0WPsWFt39voLb9LJHH3cDs PFj58eBaetX0checyDeCdbuc6DSn8YStnmBrQtq2dCy6xFlau9n0jS+VCFHocpt/eY4m vlnF2Fi6al2PzvZZlutxsM0aP325xDCiDj+l5bQvORLK66eptNRZ8274lxU/dB2ySuZY WWmgbCJG6DR8KsPlQT5FrNbeFy0Htjws/uESwpcg0v6CAQ0XAzSJRk8i4KSzx1F9GNci nxpQ==
MIME-Version: 1.0
X-Received: by 10.236.66.142 with SMTP id h14mr7357051yhd.104.1410121304351; Sun, 07 Sep 2014 13:21:44 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Sun, 7 Sep 2014 13:21:44 -0700 (PDT)
In-Reply-To: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org>
References: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org>
Date: Sun, 7 Sep 2014 22:21:44 +0200
Message-ID: <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary=001a1133c92e6fa9f205027f7330
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ee4jah4Xp_Mrsz2pNpkGvOm6_3U
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>
Subject: Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 20:21:46 -0000

--001a1133c92e6fa9f205027f7330
Content-Type: text/plain; charset=UTF-8

On Thursday, April 3, 2014, manet issue tracker wrote:

> #33: RFC 5444 processing constraint
>
>  (Thomas Clausen)
>  I have a general concern about how this protocol imposes constraints
>  on RFC5444 usage, which precludes co-existence with other RFC5444
>  protocols running on the same device.


You refer to which device (is it device with many routings) and still IETF
has no RFC specifying rules for handling other RFC5444 protocols
together running on same device. So that is future possible technology.


>  Let me give an example hereof, from Section 5.4:
>
>
>  {{{
>                  When multiple messages are aggregated into a single packet
>                  according to RFC 5444 formatting, and the aggregation of
>                  messages is also authenticated (e.g., with IPsec), and the
>                  IP destination is multiple hops away, it becomes
>  infeasible
>                  to delete individual messages.  In such cases, instead of
>                  deleting individual messages, they are maintained in the
>                  aggregation of messages, but simply ignored for further
>                  processing.  In such cases where individual messages
>  cannot
>                  be deleted, in this document "disregarded" means
>  "ignored".
>                  Otherwise, any such "disregarded" AODVv2 messages SHOULD
>  be
>                  deleted from the aggregated messages in the RFC 5444
>  packet.
>  }}}
>
>  An RFC5444 packet is *never* to be sent more than one hop.
>  ... A router receives an RFC5444 packet, decapsulates
>  it, process each message (if appropriate), the owner process of each
>  message identifies which messages are to be forwarded (if appropriate),
>  hands those off to the appropriate "message multiplexing engine" which
>  packs those messages up in a new RFC5444 packet, and transmits that
>  new RFC5444 packet.


There is no 5444 multiplexing methods specified in IETF.  However, I think
it is wrong designing protocols depending on formats, we design protocols
then our formats and our multiplexing depend on our protocols.


>  Also, in RFC5444 messages, addresses are contained in address blocks.
>  There is no semantics associated with an address being in one address
>  block, or in another (in fact, (re-)organising addresses into address
>  blocks is one of the tricks to use to obtain more compact messages).
>  Likewise, there is no semantics associated with an address being first,
>  last, or in any other position in an address block: the ordering of
>  addresses in an address block carries no semantics.


You base your definition on which RFC, I think each protocol defines its
own semantics as noticed by RFC5444.


>
>  Therefore, writing something like this:
>
>
>  {{{
>                  RteMsg.Address[i] denotes the [i]th address in an RFC 5444
>                  AddrBlk of the RteMsg. RteMsg.PrefixLength[i] denotes the
>                  associated prefix length for RteMsg.Address[i], and
>                  RteMsg.{field} denotes the corresponding value in the
>  named
>                  AddrTLV block associated with RteMsg.Address[i].
>  }}}
>
>
>  makes no sense whatsoever (aside from the fact that I do not understand
>  the notation !RteMsg.{field} - that would indicate a "field" in a
>  message, not in an attribute associated with an address).
>
>  Let me give one more example, from section 9:
>
>
>  {{{
>             If a message with an unknown type is received, the message is
>             disregarded.
>  }}}
>
>
>  An implementation of this specification will (according to RFC5444)
>  "own", and therefore get messages that this protocol has gotten
>  assigned by IANA, say, RREQ/RREP/RERR/RREP_ACK.  Messages of any
>  other Message Types will not (again, according to RFC5444) be
>  delivered to an implementation of this protocol.
>
>  Therefore, this protocol <should not>
>  specify discarding any message types other than those than it "owns".


Disregard does not mean drop, so those messages are still in
next 5444 packet. This comes back to multiplexing by ownership or not,
which that is not specified yet so we leave it for another future draft for
multiplexing. We need to focus this reactive standard not make it
complicated.

AB

--001a1133c92e6fa9f205027f7330
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Thursday, April 3, 2014, manet issue tracker  wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">#33: RFC 5444 processing constraint<br>
<br>
=C2=A0(Thomas Clausen)<br>
=C2=A0I have a general concern about how this protocol imposes constraints<=
br>
=C2=A0on RFC5444 usage, which precludes co-existence with other RFC5444<br>
=C2=A0protocols running on the same device.</blockquote><div><br></div><div=
>You refer to which device (is it device with many routings)=C2=A0and still=
 IETF has no RFC specifying rules for handling=C2=A0other RFC5444 protocols=
 together=C2=A0running on same device. So that is future possible technolog=
y.=C2=A0</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
=C2=A0Let me give an example hereof, from Section 5.4:<br>
<br>
<br>
=C2=A0{{{<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0When multiple=
 messages are aggregated into a single packet<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0according to =
RFC 5444 formatting, and the aggregation of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0messages is a=
lso authenticated (e.g., with IPsec), and the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IP destinatio=
n is multiple hops away, it becomes<br>
=C2=A0infeasible<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0to delete ind=
ividual messages.=C2=A0 In such cases, instead of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0deleting indi=
vidual messages, they are maintained in the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0aggregation o=
f messages, but simply ignored for further<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0processing.=
=C2=A0 In such cases where individual messages<br>
=C2=A0cannot<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0be deleted, i=
n this document &quot;disregarded&quot; means<br>
=C2=A0&quot;ignored&quot;.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Otherwise, an=
y such &quot;disregarded&quot; AODVv2 messages SHOULD<br>
=C2=A0be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0deleted from =
the aggregated messages in the RFC 5444<br>
=C2=A0packet.<br>
=C2=A0}}}<br>
<br>
=C2=A0An RFC5444 packet is *never* to be sent more than one hop.<br>
=C2=A0... A router receives an RFC5444 packet, decapsulates<br>
=C2=A0it, process each message (if appropriate), the owner process of each<=
br>
=C2=A0message identifies which messages are to be forwarded (if appropriate=
),<br>
=C2=A0hands those off to the appropriate &quot;message multiplexing engine&=
quot; which<br>
=C2=A0packs those messages up in a new RFC5444 packet, and transmits that<b=
r>
=C2=A0new RFC5444 packet.</blockquote><div><br></div><div>There is no 5444=
=C2=A0multiplexing methods=C2=A0specified in IETF. =C2=A0However, I think i=
t is wrong designing protocols depending on formats, we design protocols th=
en our formats and our multiplexing depend on our protocols.=C2=A0</div><di=
v><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
<br>
=C2=A0Also, in RFC5444 messages, addresses are contained in address blocks.=
<br>
=C2=A0There is no semantics associated with an address being in one address=
<br>
=C2=A0block, or in another (in fact, (re-)organising addresses into address=
<br>
=C2=A0blocks is one of the tricks to use to obtain more compact messages).<=
br>
=C2=A0Likewise, there is no semantics associated with an address being firs=
t,<br>
=C2=A0last, or in any other position in an address block: the ordering of<b=
r>
=C2=A0addresses in an address block carries no semantics.</blockquote><div>=
<br></div><div>You base your definition on which RFC, I think each protocol=
 defines its own semantics as noticed by RFC5444.=C2=A0</div><div>=C2=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
<br>
=C2=A0Therefore, writing something like this:<br>
<br>
<br>
=C2=A0{{{<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0RteMsg.Addres=
s[i] denotes the [i]th address in an RFC 5444<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0AddrBlk of th=
e RteMsg. RteMsg.PrefixLength[i] denotes the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0associated pr=
efix length for RteMsg.Address[i], and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0RteMsg.{field=
} denotes the corresponding value in the<br>
=C2=A0named<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0AddrTLV block=
 associated with RteMsg.Address[i].<br>
=C2=A0}}}<br>
<br>
<br>
=C2=A0makes no sense whatsoever (aside from the fact that I do not understa=
nd<br>
=C2=A0the notation !RteMsg.{field} - that would indicate a &quot;field&quot=
; in a<br>
=C2=A0message, not in an attribute associated with an address).<br>
<br>
=C2=A0Let me give one more example, from section 9:<br>
<br>
<br>
=C2=A0{{{<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 If a message with an unknown type=
 is received, the message is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 disregarded.<br>
=C2=A0}}}<br>
<br>
<br>
=C2=A0An implementation of this specification will (according to RFC5444)<b=
r>
=C2=A0&quot;own&quot;, and therefore get messages that this protocol has go=
tten<br>
=C2=A0assigned by IANA, say, RREQ/RREP/RERR/RREP_ACK.=C2=A0 Messages of any=
<br>
=C2=A0other Message Types will not (again, according to RFC5444) be<br>
=C2=A0delivered to an implementation of this protocol.<br>
<br>
=C2=A0Therefore, this protocol &lt;should not&gt;<br>
=C2=A0specify discarding any message types other than those than it &quot;o=
wns&quot;.</blockquote><div><br></div><div>Disregard does not mean drop, so=
 those messages are still in next=C2=A05444=C2=A0packet.=C2=A0This comes ba=
ck to multiplexing by ownership or not, which that is not specified yet so=
=C2=A0we leave it for another future=C2=A0draft for multiplexing. We need t=
o focus this reactive standard not make it complicated.=C2=A0</div><div><br=
></div><div>AB=C2=A0</div>

--001a1133c92e6fa9f205027f7330--


From nobody Sun Sep  7 13:46:40 2014
Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 175231A070A for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 13:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.152
X-Spam-Level: 
X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JoJgAcn6z9Oy for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 13:46:37 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD07A1A03B5 for <manet@ietf.org>; Sun,  7 Sep 2014 13:46:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14839; q=dns/txt; s=iport; t=1410122796; x=1411332396; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dxq3MB/07fl0hkdBmZVxr4QNAWiLjHK/vPDZbJV86Lw=; b=edSV0LMLGN6rNOUadI5h7lyQHczMyPZIwEVkI10UDeoUl58brZYESfL6 Xb+0agpUy0NM8qFQZVKH213O5SFGW0eZ7JjXo8ayS2xGWEVlQf94KRe9s krKpVoko6Ne6Jfh11HCvtft/znskzvhMiwygFOLkVj8pZgwvnDDFbrNUk g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkkFAOnCDFStJA2J/2dsb2JhbABYgw1TVwTJXwEJh0wBgQgWeIQEAQEEAQEBZAcLEAIBCD8HIQYLFBECBA4FiC4DEQ21AA2GWgETBIwegQKCLQeDL4EdBZFAiSKCEI5zhjmDYWyBSIEHAQEB
X-IronPort-AV: E=Sophos; i="5.04,483,1406592000"; d="scan'208,217"; a="75741509"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-6.cisco.com with ESMTP; 07 Sep 2014 20:46:35 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s87KkZPG009777 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 7 Sep 2014 20:46:35 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0195.001; Sun, 7 Sep 2014 15:46:35 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: [manet] #33 (aodvv2): RFC 5444 processing constraint
Thread-Index: AQHPytlg/Co7QO4hukqKH7t4FFH2D5v2d70A
Date: Sun, 7 Sep 2014 20:46:35 +0000
Message-ID: <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com>
References: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org> <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com>
In-Reply-To: <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.214.150]
Content-Type: multipart/alternative; boundary="_000_199428A626FB445183F966E90B3EA287ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/WWlBp0XYkSnFuTKR4TRJXqNzosI
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 20:46:39 -0000

--_000_199428A626FB445183F966E90B3EA287ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Abdussalam,

On Sep 7, 2014, at 4:21 PM, Abdussalam Baryun <abdussalambaryun@gmail.com<m=
ailto:abdussalambaryun@gmail.com>> wrote:



On Thursday, April 3, 2014, manet issue tracker wrote:
#33: RFC 5444 processing constraint

 (Thomas Clausen)
 I have a general concern about how this protocol imposes constraints
 on RFC5444 usage, which precludes co-existence with other RFC5444
 protocols running on the same device.

You refer to which device (is it device with many routings) and still IETF =
has no RFC specifying rules for handling other RFC5444 protocols together r=
unning on same device. So that is future possible technology.


I do not understand what you wrote above. RFC5444 is specified as a "MUST" =
for all routing protocols *coming from the MANET WG*. As for other protocol=
s (e.g. OSPF), there are no rules because there is no intersection.


 Let me give an example hereof, from Section 5.4:


 {{{
                 When multiple messages are aggregated into a single packet
                 according to RFC 5444 formatting, and the aggregation of
                 messages is also authenticated (e.g., with IPsec), and the
                 IP destination is multiple hops away, it becomes
 infeasible
                 to delete individual messages.  In such cases, instead of
                 deleting individual messages, they are maintained in the
                 aggregation of messages, but simply ignored for further
                 processing.  In such cases where individual messages
 cannot
                 be deleted, in this document "disregarded" means
 "ignored".
                 Otherwise, any such "disregarded" AODVv2 messages SHOULD
 be
                 deleted from the aggregated messages in the RFC 5444
 packet.
 }}}

 An RFC5444 packet is *never* to be sent more than one hop.
 ... A router receives an RFC5444 packet, decapsulates
 it, process each message (if appropriate), the owner process of each
 message identifies which messages are to be forwarded (if appropriate),
 hands those off to the appropriate "message multiplexing engine" which
 packs those messages up in a new RFC5444 packet, and transmits that
 new RFC5444 packet.

There is no 5444 multiplexing methods specified in IETF.  However, I think =
it is wrong designing protocols depending on formats, we design protocols t=
hen our formats and our multiplexing depend on our protocols.


RFC5444 itself describes ways that multiple (MANET WG-developed) protocols =
can be multiplexed.


 Also, in RFC5444 messages, addresses are contained in address blocks.
 There is no semantics associated with an address being in one address
 block, or in another (in fact, (re-)organising addresses into address
 blocks is one of the tricks to use to obtain more compact messages).
 Likewise, there is no semantics associated with an address being first,
 last, or in any other position in an address block: the ordering of
 addresses in an address block carries no semantics.

You base your definition on which RFC, I think each protocol defines its ow=
n semantics as noticed by RFC5444.

I believe that to be incorrect - the notion is that:
(1)  RFC5444 is specified as a MUST for all MANET WG-developed routing prot=
ocols.
(2)  RFC5444 expresses no semantics with regard to ordering of address bloc=
ks in messages.
(3)  If the proposed protocol (in this case, AODVv2), imposes ordering of a=
ddress blocks, then it (AODVv2) is incorrectly implementing RFC5444.



 Therefore, writing something like this:


 {{{
                 RteMsg.Address[i] denotes the [i]th address in an RFC 5444
                 AddrBlk of the RteMsg. RteMsg.PrefixLength[i] denotes the
                 associated prefix length for RteMsg.Address[i], and
                 RteMsg.{field} denotes the corresponding value in the
 named
                 AddrTLV block associated with RteMsg.Address[i].
 }}}


 makes no sense whatsoever (aside from the fact that I do not understand
 the notation !RteMsg.{field} - that would indicate a "field" in a
 message, not in an attribute associated with an address).

 Let me give one more example, from section 9:


 {{{
            If a message with an unknown type is received, the message is
            disregarded.
 }}}


 An implementation of this specification will (according to RFC5444)
 "own", and therefore get messages that this protocol has gotten
 assigned by IANA, say, RREQ/RREP/RERR/RREP_ACK.  Messages of any
 other Message Types will not (again, according to RFC5444) be
 delivered to an implementation of this protocol.

 Therefore, this protocol <should not>
 specify discarding any message types other than those than it "owns".

Disregard does not mean drop, so those messages are still in next 5444 pack=
et. This comes back to multiplexing by ownership or not, which that is not =
specified yet so we leave it for another future draft for multiplexing. We =
need to focus this reactive standard not make it complicated.

Again, I respectfully disagree. A deployment model to envision is a router,=
 running both OLSRv2 and AODVv2. Both of those protocols share a transport =
using RFC5444 to a second router, which is also running both protocols. The=
 "multiplexing" being spoken of would be a mix of OLSRv2 and AODVv2 message=
s, bundled up into an RFC5444 packet.

Regards,
Stan




AB
_______________________________________________
manet mailing list
manet@ietf.org<mailto:manet@ietf.org>
https://www.ietf.org/mailman/listinfo/manet


--_000_199428A626FB445183F966E90B3EA287ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <E5191FF58DE3C64496DB3DF99E4B151B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Abdussalam,&nbsp;
<div><br>
<div>
<div>On Sep 7, 2014, at 4:21 PM, Abdussalam Baryun &lt;<a href=3D"mailto:ab=
dussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><br>
<br>
On Thursday, April 3, 2014, manet issue tracker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
#33: RFC 5444 processing constraint<br>
<br>
&nbsp;(Thomas Clausen)<br>
&nbsp;I have a general concern about how this protocol imposes constraints<=
br>
&nbsp;on RFC5444 usage, which precludes co-existence with other RFC5444<br>
&nbsp;protocols running on the same device.</blockquote>
<div><br>
</div>
<div>You refer to which device (is it device with many routings)&nbsp;and s=
till IETF has no RFC specifying rules for handling&nbsp;other RFC5444 proto=
cols together&nbsp;running on same device. So that is future possible techn=
ology.&nbsp;</div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<div>I do not understand what you wrote above. RFC5444 is specified as a &q=
uot;MUST&quot; for all routing protocols *coming from the MANET WG*. As for=
 other protocols (e.g. OSPF), there are no rules because there is no inters=
ection.&nbsp;</div>
<br>
<blockquote type=3D"cite">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
&nbsp;Let me give an example hereof, from Section 5.4:<br>
<br>
<br>
&nbsp;{{{<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;When multiple=
 messages are aggregated into a single packet<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;according to =
RFC 5444 formatting, and the aggregation of<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;messages is a=
lso authenticated (e.g., with IPsec), and the<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IP destinatio=
n is multiple hops away, it becomes<br>
&nbsp;infeasible<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;to delete ind=
ividual messages.&nbsp; In such cases, instead of<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;deleting indi=
vidual messages, they are maintained in the<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;aggregation o=
f messages, but simply ignored for further<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;processing.&n=
bsp; In such cases where individual messages<br>
&nbsp;cannot<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;be deleted, i=
n this document &quot;disregarded&quot; means<br>
&nbsp;&quot;ignored&quot;.<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Otherwise, an=
y such &quot;disregarded&quot; AODVv2 messages SHOULD<br>
&nbsp;be<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;deleted from =
the aggregated messages in the RFC 5444<br>
&nbsp;packet.<br>
&nbsp;}}}<br>
<br>
&nbsp;An RFC5444 packet is *never* to be sent more than one hop.<br>
&nbsp;... A router receives an RFC5444 packet, decapsulates<br>
&nbsp;it, process each message (if appropriate), the owner process of each<=
br>
&nbsp;message identifies which messages are to be forwarded (if appropriate=
),<br>
&nbsp;hands those off to the appropriate &quot;message multiplexing engine&=
quot; which<br>
&nbsp;packs those messages up in a new RFC5444 packet, and transmits that<b=
r>
&nbsp;new RFC5444 packet.</blockquote>
<div><br>
</div>
<div>There is no 5444&nbsp;multiplexing methods&nbsp;specified in IETF. &nb=
sp;However, I think it is wrong designing protocols depending on formats, w=
e design protocols then our formats and our multiplexing depend on our prot=
ocols.&nbsp;</div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<div>RFC5444 itself describes ways that multiple (MANET WG-developed) proto=
cols can be multiplexed.</div>
<br>
<blockquote type=3D"cite">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
&nbsp;Also, in RFC5444 messages, addresses are contained in address blocks.=
<br>
&nbsp;There is no semantics associated with an address being in one address=
<br>
&nbsp;block, or in another (in fact, (re-)organising addresses into address=
<br>
&nbsp;blocks is one of the tricks to use to obtain more compact messages).<=
br>
&nbsp;Likewise, there is no semantics associated with an address being firs=
t,<br>
&nbsp;last, or in any other position in an address block: the ordering of<b=
r>
&nbsp;addresses in an address block carries no semantics.</blockquote>
<div><br>
</div>
<div>You base your definition on which RFC, I think each protocol defines i=
ts own semantics as noticed by RFC5444.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>I believe that to be incorrect - the notion is that:</div>
<div>(1) &nbsp;RFC5444 is specified as a MUST for all MANET WG-developed ro=
uting protocols.</div>
<div>(2) &nbsp;RFC5444 expresses no semantics with regard to ordering of ad=
dress blocks in messages.</div>
<div>(3) &nbsp;If the proposed protocol (in this case, AODVv2), imposes ord=
ering of address blocks, then it (AODVv2) is incorrectly implementing RFC54=
44.&nbsp;</div>
<br>
<blockquote type=3D"cite">
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
&nbsp;Therefore, writing something like this:<br>
<br>
<br>
&nbsp;{{{<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;RteMsg.Addres=
s[i] denotes the [i]th address in an RFC 5444<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AddrBlk of th=
e RteMsg. RteMsg.PrefixLength[i] denotes the<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;associated pr=
efix length for RteMsg.Address[i], and<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;RteMsg.{field=
} denotes the corresponding value in the<br>
&nbsp;named<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AddrTLV block=
 associated with RteMsg.Address[i].<br>
&nbsp;}}}<br>
<br>
<br>
&nbsp;makes no sense whatsoever (aside from the fact that I do not understa=
nd<br>
&nbsp;the notation !RteMsg.{field} - that would indicate a &quot;field&quot=
; in a<br>
&nbsp;message, not in an attribute associated with an address).<br>
<br>
&nbsp;Let me give one more example, from section 9:<br>
<br>
<br>
&nbsp;{{{<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; If a message with an unknown type=
 is received, the message is<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; disregarded.<br>
&nbsp;}}}<br>
<br>
<br>
&nbsp;An implementation of this specification will (according to RFC5444)<b=
r>
&nbsp;&quot;own&quot;, and therefore get messages that this protocol has go=
tten<br>
&nbsp;assigned by IANA, say, RREQ/RREP/RERR/RREP_ACK.&nbsp; Messages of any=
<br>
&nbsp;other Message Types will not (again, according to RFC5444) be<br>
&nbsp;delivered to an implementation of this protocol.<br>
<br>
&nbsp;Therefore, this protocol &lt;should not&gt;<br>
&nbsp;specify discarding any message types other than those than it &quot;o=
wns&quot;.</blockquote>
<div><br>
</div>
<div>Disregard does not mean drop, so those messages are still in next&nbsp=
;5444&nbsp;packet.&nbsp;This comes back to multiplexing by ownership or not=
, which that is not specified yet so&nbsp;we leave it for another future&nb=
sp;draft for multiplexing. We need to focus this reactive
 standard not make it complicated.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>Again, I respectfully disagree. A deployment model to envision is a ro=
uter, running both OLSRv2 and AODVv2. Both of those protocols share a trans=
port using RFC5444 to a second router, which is also running both protocols=
. The &quot;multiplexing&quot; being spoken
 of would be a mix of OLSRv2 and AODVv2 messages, bundled up into an RFC544=
4 packet.&nbsp;</div>
<div><br>
</div>
<div>Regards,</div>
<div>Stan</div>
<div><br>
</div>
<div><br>
</div>
<br>
<blockquote type=3D"cite">
<div><br>
</div>
<div>AB&nbsp;</div>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/manet<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_199428A626FB445183F966E90B3EA287ciscocom_--


From nobody Sun Sep  7 13:55:33 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B911A03B5 for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 13:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uyEFfO-nn9oz for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 13:55:28 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36A8E1A06A4 for <manet@ietf.org>; Sun,  7 Sep 2014 13:55:27 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id ex7so1524466wid.2 for <manet@ietf.org>; Sun, 07 Sep 2014 13:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=6d/LKbqnZV4oVfuIX3t72cvs7V7udekW/MXj8AQtI3I=; b=yWl3Y8+xF6bsF/kPnAa6EXRvVyWBg2T8zWnoLGKJUwnNW6lDStbiTGi1oBV66Y9/uz p646TJkb1YZVTHmyBDNDdrDdrLmHJECqosoem7pDodTorLiezT9fga9XV4Q8g/yQY1Iv jjvFY1tGAgsNZ3obdDyiMr/9iSJPoyOlrrWHdKJftw8NxXnTLyuB7tvRXSfsXhKR1RZd PIaJIuV5A1fHNPSjx/iODLfULQl8L/GKd1IPmPSYEvRI8cHszm3IHA0VRVTFXsycDy3Y +NB3ezYAdRmCc40ZzrNC74LK6pOJJpLCkasVIMWv7GK1gFkAxawzq0h9Nj15YEVwLmjL Gi9w==
X-Received: by 10.180.75.17 with SMTP id y17mr17674053wiv.3.1410123325766; Sun, 07 Sep 2014 13:55:25 -0700 (PDT)
Received: from [192.168.254.1] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id wx3sm8862781wjc.19.2014.09.07.13.55.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 07 Sep 2014 13:55:24 -0700 (PDT)
References: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org> <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com> <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-4E80B292-9FA3-4388-932C-0D1A18CF9AF3
Content-Transfer-Encoding: 7bit
Message-Id: <A5DD62E7-82EC-4ACF-8A71-A9ADF81827A8@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Sun, 7 Sep 2014 21:55:21 +0100
To: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/9ZuXpQeuKMqaaODg3JxEQMwqJhc
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 20:55:32 -0000

--Apple-Mail-4E80B292-9FA3-4388-932C-0D1A18CF9AF3
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

As Stan has said, with one addition (unless Stan said it and I missed it). 5=
444 describes how messages can be multiplexed. 5498 says (as part of its usi=
ng of the MANET protocol or port) you must use that multiplexing method. The=
 WG has decided that means the protocols it is developing (with the obvious e=
xception of DLEP that isn't a MANET routing protocol).

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 7 Sep 2014, at 21:46, "Stan Ratliff (sratliff)" <sratliff@cisco.com> wr=
ote:
>=20
> Abdussalam,=20
>=20
>> On Sep 7, 2014, at 4:21 PM, Abdussalam Baryun <abdussalambaryun@gmail.com=
> wrote:
>>=20
>>=20
>>=20
>>> On Thursday, April 3, 2014, manet issue tracker wrote:
>>> #33: RFC 5444 processing constraint
>>>=20
>>>  (Thomas Clausen)
>>>  I have a general concern about how this protocol imposes constraints
>>>  on RFC5444 usage, which precludes co-existence with other RFC5444
>>>  protocols running on the same device.
>>=20
>> You refer to which device (is it device with many routings) and still IET=
F has no RFC specifying rules for handling other RFC5444 protocols together r=
unning on same device. So that is future possible technology.=20
>=20
> I do not understand what you wrote above. RFC5444 is specified as a "MUST"=
 for all routing protocols *coming from the MANET WG*. As for other protocol=
s (e.g. OSPF), there are no rules because there is no intersection.=20
>=20
>>>=20
>>>  Let me give an example hereof, from Section 5.4:
>>>=20
>>>=20
>>>  {{{
>>>                  When multiple messages are aggregated into a single pac=
ket
>>>                  according to RFC 5444 formatting, and the aggregation o=
f
>>>                  messages is also authenticated (e.g., with IPsec), and t=
he
>>>                  IP destination is multiple hops away, it becomes
>>>  infeasible
>>>                  to delete individual messages.  In such cases, instead o=
f
>>>                  deleting individual messages, they are maintained in th=
e
>>>                  aggregation of messages, but simply ignored for further=

>>>                  processing.  In such cases where individual messages
>>>  cannot
>>>                  be deleted, in this document "disregarded" means
>>>  "ignored".
>>>                  Otherwise, any such "disregarded" AODVv2 messages SHOUL=
D
>>>  be
>>>                  deleted from the aggregated messages in the RFC 5444
>>>  packet.
>>>  }}}
>>>=20
>>>  An RFC5444 packet is *never* to be sent more than one hop.
>>>  ... A router receives an RFC5444 packet, decapsulates
>>>  it, process each message (if appropriate), the owner process of each
>>>  message identifies which messages are to be forwarded (if appropriate),=

>>>  hands those off to the appropriate "message multiplexing engine" which
>>>  packs those messages up in a new RFC5444 packet, and transmits that
>>>  new RFC5444 packet.
>>=20
>> There is no 5444 multiplexing methods specified in IETF.  However, I thin=
k it is wrong designing protocols depending on formats, we design protocols t=
hen our formats and our multiplexing depend on our protocols.=20
>=20
> RFC5444 itself describes ways that multiple (MANET WG-developed) protocols=
 can be multiplexed.
>=20
>>>=20
>>>  Also, in RFC5444 messages, addresses are contained in address blocks.
>>>  There is no semantics associated with an address being in one address
>>>  block, or in another (in fact, (re-)organising addresses into address
>>>  blocks is one of the tricks to use to obtain more compact messages).
>>>  Likewise, there is no semantics associated with an address being first,=

>>>  last, or in any other position in an address block: the ordering of
>>>  addresses in an address block carries no semantics.
>>=20
>> You base your definition on which RFC, I think each protocol defines its o=
wn semantics as noticed by RFC5444.=20
>=20
> I believe that to be incorrect - the notion is that:
> (1)  RFC5444 is specified as a MUST for all MANET WG-developed routing pro=
tocols.
> (2)  RFC5444 expresses no semantics with regard to ordering of address blo=
cks in messages.
> (3)  If the proposed protocol (in this case, AODVv2), imposes ordering of a=
ddress blocks, then it (AODVv2) is incorrectly implementing RFC5444.=20
>=20
>> =20
>>>=20
>>>  Therefore, writing something like this:
>>>=20
>>>=20
>>>  {{{
>>>                  RteMsg.Address[i] denotes the [i]th address in an RFC 5=
444
>>>                  AddrBlk of the RteMsg. RteMsg.PrefixLength[i] denotes t=
he
>>>                  associated prefix length for RteMsg.Address[i], and
>>>                  RteMsg.{field} denotes the corresponding value in the
>>>  named
>>>                  AddrTLV block associated with RteMsg.Address[i].
>>>  }}}
>>>=20
>>>=20
>>>  makes no sense whatsoever (aside from the fact that I do not understand=

>>>  the notation !RteMsg.{field} - that would indicate a "field" in a
>>>  message, not in an attribute associated with an address).
>>>=20
>>>  Let me give one more example, from section 9:
>>>=20
>>>=20
>>>  {{{
>>>             If a message with an unknown type is received, the message i=
s
>>>             disregarded.
>>>  }}}
>>>=20
>>>=20
>>>  An implementation of this specification will (according to RFC5444)
>>>  "own", and therefore get messages that this protocol has gotten
>>>  assigned by IANA, say, RREQ/RREP/RERR/RREP_ACK.  Messages of any
>>>  other Message Types will not (again, according to RFC5444) be
>>>  delivered to an implementation of this protocol.
>>>=20
>>>  Therefore, this protocol <should not>
>>>  specify discarding any message types other than those than it "owns".
>>=20
>> Disregard does not mean drop, so those messages are still in next 5444 pa=
cket. This comes back to multiplexing by ownership or not, which that is not=
 specified yet so we leave it for another future draft for multiplexing. We n=
eed to focus this reactive standard not make it complicated.=20
>=20
> Again, I respectfully disagree. A deployment model to envision is a router=
, running both OLSRv2 and AODVv2. Both of those protocols share a transport u=
sing RFC5444 to a second router, which is also running both protocols. The "=
multiplexing" being spoken of would be a mix of OLSRv2 and AODVv2 messages, b=
undled up into an RFC5444 packet.=20
>=20
> Regards,
> Stan
>=20
>=20
>=20
>>=20
>> AB=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-4E80B292-9FA3-4388-932C-0D1A18CF9AF3
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>As Stan has said, with one addition (unless Stan said it and I missed it). 5444 describes how messages can be multiplexed. 5498 says (as part of its using of the MANET protocol or port) you must use that multiplexing method. The WG has decided that means the protocols it is developing (with the obvious exception of DLEP that isn't a MANET routing protocol).<br><br>-- &nbsp;<div>Christopher Dearlove</div><div><a href="mailto:christopher.dearlove@gmail.com">christopher.dearlove@gmail.com</a> (iPhone)</div><div><a href="mailto:chris@mnemosyne.demon.co.uk">chris@mnemosyne.demon.co.uk</a> (home)</div></div><div><br>On 7 Sep 2014, at 21:46, "Stan Ratliff (sratliff)" &lt;<a href="mailto:sratliff@cisco.com">sratliff@cisco.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div>

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">


Abdussalam,&nbsp;
<div><br>
<div>
<div>On Sep 7, 2014, at 4:21 PM, Abdussalam Baryun &lt;<a href="mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><br>
<br>
On Thursday, April 3, 2014, manet issue tracker wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
#33: RFC 5444 processing constraint<br>
<br>
&nbsp;(Thomas Clausen)<br>
&nbsp;I have a general concern about how this protocol imposes constraints<br>
&nbsp;on RFC5444 usage, which precludes co-existence with other RFC5444<br>
&nbsp;protocols running on the same device.</blockquote>
<div><br>
</div>
<div>You refer to which device (is it device with many routings)&nbsp;and still IETF has no RFC specifying rules for handling&nbsp;other RFC5444 protocols together&nbsp;running on same device. So that is future possible technology.&nbsp;</div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<div>I do not understand what you wrote above. RFC5444 is specified as a "MUST" for all routing protocols *coming from the MANET WG*. As for other protocols (e.g. OSPF), there are no rules because there is no intersection.&nbsp;</div>
<br>
<blockquote type="cite">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&nbsp;Let me give an example hereof, from Section 5.4:<br>
<br>
<br>
&nbsp;{{{<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;When multiple messages are aggregated into a single packet<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;according to RFC 5444 formatting, and the aggregation of<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;messages is also authenticated (e.g., with IPsec), and the<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IP destination is multiple hops away, it becomes<br>
&nbsp;infeasible<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;to delete individual messages.&nbsp; In such cases, instead of<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;deleting individual messages, they are maintained in the<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;aggregation of messages, but simply ignored for further<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;processing.&nbsp; In such cases where individual messages<br>
&nbsp;cannot<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;be deleted, in this document "disregarded" means<br>
&nbsp;"ignored".<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Otherwise, any such "disregarded" AODVv2 messages SHOULD<br>
&nbsp;be<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;deleted from the aggregated messages in the RFC 5444<br>
&nbsp;packet.<br>
&nbsp;}}}<br>
<br>
&nbsp;An RFC5444 packet is *never* to be sent more than one hop.<br>
&nbsp;... A router receives an RFC5444 packet, decapsulates<br>
&nbsp;it, process each message (if appropriate), the owner process of each<br>
&nbsp;message identifies which messages are to be forwarded (if appropriate),<br>
&nbsp;hands those off to the appropriate "message multiplexing engine" which<br>
&nbsp;packs those messages up in a new RFC5444 packet, and transmits that<br>
&nbsp;new RFC5444 packet.</blockquote>
<div><br>
</div>
<div>There is no 5444&nbsp;multiplexing methods&nbsp;specified in IETF. &nbsp;However, I think it is wrong designing protocols depending on formats, we design protocols then our formats and our multiplexing depend on our protocols.&nbsp;</div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<div>RFC5444 itself describes ways that multiple (MANET WG-developed) protocols can be multiplexed.</div>
<br>
<blockquote type="cite">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&nbsp;Also, in RFC5444 messages, addresses are contained in address blocks.<br>
&nbsp;There is no semantics associated with an address being in one address<br>
&nbsp;block, or in another (in fact, (re-)organising addresses into address<br>
&nbsp;blocks is one of the tricks to use to obtain more compact messages).<br>
&nbsp;Likewise, there is no semantics associated with an address being first,<br>
&nbsp;last, or in any other position in an address block: the ordering of<br>
&nbsp;addresses in an address block carries no semantics.</blockquote>
<div><br>
</div>
<div>You base your definition on which RFC, I think each protocol defines its own semantics as noticed by RFC5444.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>I believe that to be incorrect - the notion is that:</div>
<div>(1) &nbsp;RFC5444 is specified as a MUST for all MANET WG-developed routing protocols.</div>
<div>(2) &nbsp;RFC5444 expresses no semantics with regard to ordering of address blocks in messages.</div>
<div>(3) &nbsp;If the proposed protocol (in this case, AODVv2), imposes ordering of address blocks, then it (AODVv2) is incorrectly implementing RFC5444.&nbsp;</div>
<br>
<blockquote type="cite">
<div>&nbsp;</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&nbsp;Therefore, writing something like this:<br>
<br>
<br>
&nbsp;{{{<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;RteMsg.Address[i] denotes the [i]th address in an RFC 5444<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AddrBlk of the RteMsg. RteMsg.PrefixLength[i] denotes the<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;associated prefix length for RteMsg.Address[i], and<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;RteMsg.{field} denotes the corresponding value in the<br>
&nbsp;named<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AddrTLV block associated with RteMsg.Address[i].<br>
&nbsp;}}}<br>
<br>
<br>
&nbsp;makes no sense whatsoever (aside from the fact that I do not understand<br>
&nbsp;the notation !RteMsg.{field} - that would indicate a "field" in a<br>
&nbsp;message, not in an attribute associated with an address).<br>
<br>
&nbsp;Let me give one more example, from section 9:<br>
<br>
<br>
&nbsp;{{{<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; If a message with an unknown type is received, the message is<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; disregarded.<br>
&nbsp;}}}<br>
<br>
<br>
&nbsp;An implementation of this specification will (according to RFC5444)<br>
&nbsp;"own", and therefore get messages that this protocol has gotten<br>
&nbsp;assigned by IANA, say, RREQ/RREP/RERR/RREP_ACK.&nbsp; Messages of any<br>
&nbsp;other Message Types will not (again, according to RFC5444) be<br>
&nbsp;delivered to an implementation of this protocol.<br>
<br>
&nbsp;Therefore, this protocol &lt;should not&gt;<br>
&nbsp;specify discarding any message types other than those than it "owns".</blockquote>
<div><br>
</div>
<div>Disregard does not mean drop, so those messages are still in next&nbsp;5444&nbsp;packet.&nbsp;This comes back to multiplexing by ownership or not, which that is not specified yet so&nbsp;we leave it for another future&nbsp;draft for multiplexing. We need to focus this reactive
 standard not make it complicated.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>Again, I respectfully disagree. A deployment model to envision is a router, running both OLSRv2 and AODVv2. Both of those protocols share a transport using RFC5444 to a second router, which is also running both protocols. The "multiplexing" being spoken
 of would be a mix of OLSRv2 and AODVv2 messages, bundled up into an RFC5444 packet.&nbsp;</div>
<div><br>
</div>
<div>Regards,</div>
<div>Stan</div>
<div><br>
</div>
<div><br>
</div>
<br>
<blockquote type="cite">
<div><br>
</div>
<div>AB&nbsp;</div>
_______________________________________________<br>
manet mailing list<br>
<a href="mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote>
</div>
<br>
</div>


</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>manet mailing list</span><br><span><a href="mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet</a></span><br></div></blockquote></body></html>
--Apple-Mail-4E80B292-9FA3-4388-932C-0D1A18CF9AF3--


From nobody Sun Sep  7 13:57:02 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E58C1A00F1 for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 13:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.162
X-Spam-Level: **
X-Spam-Status: No, score=2.162 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, SUBJ_AS_SEEN=1.461] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 87GrE6Q8kjCy for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 13:56:59 -0700 (PDT)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BF7A1A067D for <manet@ietf.org>; Sun,  7 Sep 2014 13:56:58 -0700 (PDT)
Received: by mail-yh0-f47.google.com with SMTP id c41so8719304yho.34 for <manet@ietf.org>; Sun, 07 Sep 2014 13:56:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bvwe6fKMjwwrWNLh6kpCcnFPtpDBk1mRVU95BeWTmEM=; b=OhSPye1RBdgOuyCCXVEgaWtV3Bk2JZ8qdWIV2vDOTLJVn7JrEV83dK5/LrqTiow8KL HK4GOLww6Zuplw/kR+Dk2LKZLacA08mSAKF+pXT6EvzRrMAITbcdU0DvEjgTwoiEpov6 jC7vRWG4EifbOOFFUkCqVUcKl0p38tcc2DIpm7UaGMMOPe0rEMENnj2XMN5W8yhFsCrV PniYVphJLpNrJXFCwB0/+/l71gD8DtR0yo/dTkgqWvM0gsRlkowHioWxc0w43/ptH6u9 027ESw00CZ2aeuSbAi6pwVfQMcxUqwjKtiKX29wCOnY9TCvgE1u6/CxuuyJW6MpS0AWP R6uQ==
MIME-Version: 1.0
X-Received: by 10.236.3.8 with SMTP id 8mr35590210yhg.3.1410123418130; Sun, 07 Sep 2014 13:56:58 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Sun, 7 Sep 2014 13:56:58 -0700 (PDT)
In-Reply-To: <CD943CDC-C8B8-449A-9B75-6B57623A35EF@thomasclausen.org>
References: <CA+-pDCfjvA7TLy6b0RKc0HwpSUtECWsjPxDeo4o6g9KtTjJF9Q@mail.gmail.com> <CADnDZ8_k8fY6zoWpZR5=+cjNscyEUErFFrqN-Rh-q6NayUFa-g@mail.gmail.com> <CD943CDC-C8B8-449A-9B75-6B57623A35EF@thomasclausen.org>
Date: Sun, 7 Sep 2014 22:56:58 +0200
Message-ID: <CADnDZ8_TsaXYwui+QkxoHoeAtrfCsovVreCSp6vCJetwuVaWGA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Clausen <thomas@thomasclausen.org>
Content-Type: multipart/alternative; boundary=001a113676266d5fe005027ff106
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/Po0SYpZG5DjJCtdeQkbnJfNC950
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] MANET action items (as seen by Justin Dean)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 20:57:00 -0000

--001a113676266d5fe005027ff106
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Thomas,

Sorry for the delay. I agree that we work together for progress of
WG drafts. My respond and comments below.

On Monday, July 28, 2014, Thomas Clausen wrote:

> Abdussalam,
>
> On Jul 23, 2014, at 14:18, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
>
> On Tue, Jul 22, 2014 at 10:35 PM, Justin Dean <bebemaster@gmail.com>
> wrote:
>
>> Notes on action items coming out of the MANET working group meeting.
>> (this list is not exhaustive of the topics covered in the meeting)
>>
>> 1) A suggestion was made to ask Stan if dlep editing help would be
>> helpful. If yes who should that person(s) be?
>>
>> 2) What to do with the report MIB; Kill, finish, revise?
>>
>> 3) Request for WG adoption of SMF sec threat document was made.  No one
>> in the room had read the draft, but there was positive room reaction to
>> adopting a document with this subject and no negative reaction as measur=
ed
>> by hum.  Please read the draft and comment.
>>
>
> The WG should read the draft and discuss before adopting or humming and I
> hope the chairs consider the high volume of drafts to give me more time
> before their decisions.
>
>
> The documents were submitted well in advance of the meeting, before the
> document submission deadline that precedes all IETF meetings, and were
> announced on the list at about the same time.
>

I really think there are limits for any WG/individual of work item volume
in and out. However, it was just my comment to clarify I am not responsible
for missing deadline dates of WG Calls. If our calls are serious then it
should consider abilities. However, that may make my reviews get late in
IETF LC.


> There were not a whole lot of new WG documents in MANET this time around,
> and there were no updates to two of the documents which otherwise are WG
> documents, made before that official deadline =E2=80=94 compared to other=
 WGs, I
> don=E2=80=99t think that this can be considered a particularly high volum=
e of
> drafts, and the drafts are not particularly complex nor wrong either.
>

If WG agrees I don't mind but just I made clear my comment on the thread.


>  6) Request for WG adoption of OLSRv2 multi-path for experimental status
>> was made.  No one in the room had read the draft, there was mixed but
>> positive reaction as measured by hum.  Please read the draft and comment=
.
>>
>
> I reject until we get time to review and do our priorities on other draft=
s.
>
>
> I agree, that it would be good to see forward progress on the documents,
> for which there has been none.
>
> As you have no doubt also observed, for both draft-ietf-manet-aodvv2 and
> draft-ietf-manet-dlep, there have been ample feedback and reviews given o=
n
> the mailing list, but (for the former) that feedback has not been reflect=
ed
> in the recent versions of the document, and (for the latter) there has be=
en
> no new version for a while (but, a lot of good discussion).
>
> While the authors of these two documents work to figure out to spin new
> revisions among themselves, revisions which fold in all the feedback that
> the WG has provided, the rest of the WG can=E2=80=99t be expected to simp=
ly idle
> when there=E2=80=99re other things to do.
>
> Perhaps your volunteering to help the authors of draft-ietf-manet-aodvv2
> and draft-ietf-manet-dlep in the editorial process might be a way for you
> to contribute to making progress?
>

I am doing my best volunteering these drafts and for all other WG drafts,
but trying to cope with WGLCs as well. However, I think our milestones to
meet are more important than meeting deadlines of WG calls.


>
> 7) Request for WG adoption of ODMRP was made.  Discussion within the room
>> touched upon the charter and was generally positive to multicast work bu=
t
>> again charter. No hum was held.
>>
>
> I dont support adopting reactive multicast until we finish the reactive
> standard
>
>
> For what it=E2=80=99s worth, there=E2=80=99s actually no dependency betwe=
en ODMRP and the
> reactive unicast protocol
>

Both are reactive and both are with similar applicability use, so from user
point of view if more dependent possibilities may make advantages to both.

=E2=80=94 I would even make the case that ODMRP would work quite nicely on =
a
> network on which OLSRv2 provides unicast routing, since ODMRP in that cas=
e
> could take advantage of OLSRv2=E2=80=99s optimized flooding (for example)=
 for
> diffusing its control messages and maintaining link status tracking.
>

Ok, we can make it for that applicability use case, which is reasonable for
me as 7181 is completed and being accepted.

AB


>
>

--001a113676266d5fe005027ff106
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Thomas,<div><br></div><div>Sorry for the delay. I agree that we work tog=
ether for progress of WG=C2=A0drafts.=C2=A0My respond and comments below.=
=C2=A0<br><br>On Monday, July 28, 2014, Thomas Clausen  wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><div style=3D"word-wrap:break-word">
Abdussalam,<div><br><div><div>On Jul 23, 2014, at 14:18, Abdussalam Baryun =
&lt;<a>abdussalambaryun@gmail.com</a>&gt; wrote:</div>
<br><blockquote type=3D"cite"><div dir=3D"ltr">
<div class=3D"gmail_quote">On Tue, Jul 22, 2014 at 10:35 PM, Justin Dean <s=
pan dir=3D"ltr">&lt;<a>bebemaster@gmail.com</a>&gt;</span> wrote:<br>

<blockquote style=3D"border-left-color:rgb(204,204,204);border-left-width:1=
px;border-left-style:solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class=
=3D"gmail_quote">
<div dir=3D"ltr">Notes on action items coming out of the MANET working grou=
p meeting. (this list is not exhaustive of the topics covered in the meetin=
g)<br><br>
<div>1) A suggestion was made to ask Stan if dlep editing help would be hel=
pful. If yes who should that person(s) be?<br><br>2) What to do with the re=
port MIB; Kill, finish, revise?<br><br>3) Request for WG adoption of SMF se=
c threat document was made. =C2=A0No one in the room had read the draft, bu=
t there was positive room reaction to adopting a document with this subject=
 and no negative reaction as measured by hum. =C2=A0Please read the draft a=
nd comment.<br>

</div></div></blockquote>
<div>=C2=A0</div>
<div>The WG should read the draft and discuss before adopting or humming an=
d I hope the chairs consider the high volume of drafts to give me more time=
 before their decisions.</div>
</div></div></blockquote><div><br></div>The documents were submitted well i=
n advance of the meeting, before the document submission deadline that prec=
edes all IETF meetings, and were announced on the list at about the same ti=
me.</div>
</div></div></blockquote><div><br></div><div>I really think there are limit=
s for any WG/individual=C2=A0of work=C2=A0item=C2=A0volume in and out. Howe=
ver, it was just my comment to clarify I am not responsible for missing dea=
dline dates of WG Calls. If our=C2=A0calls are serious then it should consi=
der abilities. However, that=C2=A0may make my=C2=A0reviews get late=C2=A0in=
 IETF LC.=C2=A0</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div><div><br></div><div>There were not=
 a whole lot of new WG documents in MANET this time around, and there were =
no updates to two of the documents which otherwise are WG documents, made b=
efore that official deadline =E2=80=94 compared to other WGs, I don=E2=80=
=99t think that this can be considered a particularly high volume of drafts=
, and the drafts are not particularly complex nor wrong either.</div></div>=
</div></blockquote><div><br></div><div>If WG agrees I don&#39;t mind but ju=
st I made clear my comment on the thread.=C2=A0=C2=A0</div><div><br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>
<div><br></div><div><blockquote type=3D"cite"><div dir=3D"ltr"><div class=
=3D"gmail_quote">
<blockquote style=3D"border-left-color:rgb(204,204,204);border-left-width:1=
px;border-left-style:solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class=
=3D"gmail_quote">
<div dir=3D"ltr">
<div>6) Request for WG adoption of OLSRv2 multi-path for experimental statu=
s was made. =C2=A0No one in the room had read the draft, there was mixed bu=
t positive reaction as measured by hum. =C2=A0Please read the draft and com=
ment.<br>

</div></div></blockquote>
<div>=C2=A0</div>
<div>I reject until we get time to review and do our priorities on other dr=
afts.</div>
</div></div></blockquote><div><br></div><div>I agree, that it would be good=
 to see forward progress on the documents, for which there has been none.=
=C2=A0</div><div><br></div><div>As you have no doubt also observed, for bot=
h draft-ietf-manet-aodvv2 and draft-ietf-manet-dlep, there have been ample =
feedback and reviews given on the mailing list, but (for the former) that f=
eedback has not been reflected in the recent versions of the document, and =
(for the latter) there has been no new version for a while (but, a lot of g=
ood discussion).</div>
<div><br></div><div>While the authors of these two documents work to figure=
 out to spin new revisions among themselves, revisions which fold in all th=
e feedback that the WG has provided, the rest of the WG can=E2=80=99t be ex=
pected to simply idle when there=E2=80=99re other things to do.</div>
<div><br></div><div>Perhaps your volunteering to help the authors of draft-=
ietf-manet-aodvv2 and draft-ietf-manet-dlep in the editorial process might =
be a way for you to contribute to making progress?</div></div></div></div><=
/blockquote><div><br></div><div>I am doing my best volunteering these draft=
s and=C2=A0for all other=C2=A0WG=C2=A0drafts, but trying to cope with WGLCs=
 as well. However, I think our milestones to meet=C2=A0are more important t=
han meeting deadlines of=C2=A0WG=C2=A0calls.=C2=A0</div><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><div>
<div><br></div><blockquote type=3D"cite"><div dir=3D"ltr"><div class=3D"gma=
il_quote"><blockquote style=3D"border-left-color:rgb(204,204,204);border-le=
ft-width:1px;border-left-style:solid;margin:0px 0px 0px 0.8ex;padding-left:=
1ex" class=3D"gmail_quote">
<div dir=3D"ltr"><div>7) Request for WG adoption of ODMRP was made. =C2=A0D=
iscussion within the room touched upon the charter and was generally positi=
ve to multicast work but again charter. No hum was held.</div></div></block=
quote>

<div>=C2=A0</div>
<div>I dont support adopting reactive multicast until we finish the reactiv=
e standard</div></div></div></blockquote><div><br></div>For what it=E2=80=
=99s worth, there=E2=80=99s actually no dependency between ODMRP and the re=
active unicast protocol=C2=A0</div><div></div></div></div></blockquote><div=
><br></div><div>Both are reactive and both are with similar=C2=A0applicabil=
ity use, so from user point of view if more=C2=A0dependent possibilities ma=
y make advantages to both.=C2=A0</div><div><br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div style=3D"word-wrap:break-word"><div><div>=E2=80=94 I would ev=
en make the case that ODMRP would work quite nicely on a network on which O=
LSRv2 provides unicast routing, since ODMRP in that case could take advanta=
ge of OLSRv2=E2=80=99s optimized flooding (for example) for diffusing its c=
ontrol messages and maintaining link status tracking.=C2=A0</div></div></di=
v></blockquote><div><br></div><div>Ok, we can make it for that applicabilit=
y use case, which is reasonable for me as 7181 is completed and being accep=
ted.=C2=A0</div><div><br></div><div>AB</div><div>=C2=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div style=3D"word-wrap:break-word"><div><br></div></div><=
/blockquote></div>

--001a113676266d5fe005027ff106--


From nobody Sun Sep  7 15:01:53 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB4E1A00D8 for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 15:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qBokkFMogWwy for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 15:01:49 -0700 (PDT)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 154BD1A00AF for <manet@ietf.org>; Sun,  7 Sep 2014 15:01:49 -0700 (PDT)
Received: by mail-yk0-f178.google.com with SMTP id q200so8266852ykb.23 for <manet@ietf.org>; Sun, 07 Sep 2014 15:01:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CyKpdbFWfMdk+RrVgktkVPEAUH+9GUNuI4Z4Y+Xk5Dg=; b=Z86cgqkiVw7aDdtVuXMDAlqQTiYp1booMG6IHx98XVjWih88lkcS28UoNbHv2BbPzy fSRh0ATzuR+EpIjlR2xwFURIvadReUhIlJNZzKXYh8zlcO4JfyZRqcMoXM8r3Bd34cG2 50YEw2t7k1fOxtCZpJZEHHFt1+HMTSCnORORvq9SIhC3mL7yyovbhN8bRtXL2CjTJ3oX gVIlVfmmMois4buEM5H5sqsC3DdGdM72Y3o7o5hvOaFQOegSm/I+GFmonvk4G9TQ0t40 MQFGHuXd33qI1Os+SW1uNJGzx3Q/tk3eI9bXRWxyW03IOU3OKcrEPiAAEtL+Twr1q6p0 Bwvw==
MIME-Version: 1.0
X-Received: by 10.236.62.226 with SMTP id y62mr34883053yhc.69.1410127308094; Sun, 07 Sep 2014 15:01:48 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Sun, 7 Sep 2014 15:01:48 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECF7@GLKXM0002V.GREENLNK.net>
References: <061.89377601617f43ae76e225162010f923@trac.tools.ietf.org> <53CC9987.6060104@computer.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECF7@GLKXM0002V.GREENLNK.net>
Date: Mon, 8 Sep 2014 00:01:48 +0200
Message-ID: <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=089e0115ee46499010050280d9f0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/VT-T0MC_xfv2-W9FAreVFCmfcvI
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 22:01:51 -0000

--089e0115ee46499010050280d9f0
Content-Type: text/plain; charset=UTF-8

Hi Chris,

I think you may misunderstand MANET  reactive routing. I don't see your
reply answers the editor question of examples of AODVv2 needs from IP or
ICMP. You mention that the protocol needs to see ICMP, what is the problem
with that as RFC3561 already has similar issue and already accepted by WG.

AB

On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:

> Just for a start you also need to know that IP routes are requested, that
> packets are flowing, and to have the ability to queue packets. I'm pretty
> sure not all of those are mandated by IP. The routing protocol also needs
> to see ICMP messages - is that normal?
>
> As I said, it's a matter of what the whole architecture looks like.


I think MANET still did not specify its whole architecture.


>
> --
> Christopher Dearlove
> Senior Principal Engineer, Information Assurance Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
> -----Original Message-----
> From: Charles E. Perkins [mailto:charliep@computer.org]
> Sent: 21 July 2014 05:40
> To: manet@ietf.org; draft-ietf-manet-aodvv2@tools.ietf.org; Dearlove,
> Christopher (UK)
> Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP
> (submitted for Chris Dearlove)
>
> ----------------------! WARNING ! ---------------------- This message
> originates from outside our organisation, either from an external partner
> or from the internet.
> Consider carefully whether you should click on any links, open any
> attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for instructions
> on reporting suspicious email messages.
> --------------------------------------------------------
>
> Hello Chris,
>
> I am pretty sure that the only things needed from IP and ICMP are features
> that are already mandated by IP (including ICMP).  If there were danger
> that AODVv2 might require optional features of IP or optional features of
> ICMP, I could understand your concern.  As it is, I do not understand
> exactly what is needed to enhance implementability of the specification.
>
> The only thing expected from ICMP is delivery of Destination Unreachable
> (Type 3 Code 1).  Is this something that implementations are unlikely to
> provide?
>
> I am confused about what (other than ICMP) AODVv2 "needs" from IP that
> could cause a problem.  True, we do expect IP to find the proper outgoing
> interface, and to perform longest-prefix-first matching, and so on...
>
> Do you have an example of some other protocol specification that lists
> these kinds of dependencies?
>
>
> On 7/20/2014 8:42 PM, manet issue tracker wrote:
> > #46: What is needed from IP and ICMP (submitted for Chris Dearlove)
> >
> >   The protocol needs many things from IP, such as failed routing
> >   notification, and interacts with it in ways such as queuing packets.
> >   It also interacts (sends and receives) with ICMP, and I'm not sure
> >   what else. This needs to be put together, so the reader can see what
> >   is needed to be able to implement this.
> >
>
> --
> Regards,
> Charlie P.
>
> ********************************************************************
> 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
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--089e0115ee46499010050280d9f0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Chris,<div><br></div><div>I think you may misunderstand MANET=C2=A0=C2=
=A0reactive routing. I don&#39;t see your reply answers the editor question=
 of examples of AODVv2 needs from IP or ICMP. You mention that the protocol=
 needs to see ICMP, what is the problem with that as=C2=A0RFC3561 already h=
as similar issue and already accepted by WG.=C2=A0</div><div><br></div><div=
>AB<br><br>On Tuesday, July 22, 2014, Dearlove, Christopher (UK)  wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Just for a start you also need to know that=
 IP routes are requested, that packets are flowing, and to have the ability=
 to queue packets. I&#39;m pretty sure not all of those are mandated by IP.=
 The routing protocol also needs to see ICMP messages - is that normal?<br>
<br>
As I said, it&#39;s a matter of what the whole architecture looks like.</bl=
ockquote><div><br></div><div>I think MANET still did not specify its whole =
architecture.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Information Assurance Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: +44 1245 242194=C2=A0|=C2=A0 Fax: +44 1245 242124<br>
<a>chris.dearlove@baesystems.com</a>=C2=A0| <a href=3D"http://www.baesystem=
s.com" target=3D"_blank">http://www.baesystems.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<br>
From: Charles E. Perkins [mailto:<a>charliep@computer.org</a>]<br>
Sent: 21 July 2014 05:40<br>
To: <a>manet@ietf.org</a>; <a>draft-ietf-manet-aodvv2@tools.ietf.org</a>; D=
earlove, Christopher (UK)<br>
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitt=
ed for Chris Dearlove)<br>
<br>
----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.<br>
Consider carefully whether you should click on any links, open any attachme=
nts or reply.<br>
Follow the &#39;Report Suspicious Emails&#39; link on IT matters for instru=
ctions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
Hello Chris,<br>
<br>
I am pretty sure that the only things needed from IP and ICMP are features =
that are already mandated by IP (including ICMP).=C2=A0 If there were dange=
r that AODVv2 might require optional features of IP or optional features of=
 ICMP, I could understand your concern.=C2=A0 As it is, I do not understand=
 exactly what is needed to enhance implementability of the specification.<b=
r>
<br>
The only thing expected from ICMP is delivery of Destination Unreachable (T=
ype 3 Code 1).=C2=A0 Is this something that implementations are unlikely to=
 provide?<br>
<br>
I am confused about what (other than ICMP) AODVv2 &quot;needs&quot; from IP=
 that could cause a problem.=C2=A0 True, we do expect IP to find the proper=
 outgoing interface, and to perform longest-prefix-first matching, and so o=
n...<br>
<br>
Do you have an example of some other protocol specification that lists thes=
e kinds of dependencies?<br>
<br>
<br>
On 7/20/2014 8:42 PM, manet issue tracker wrote:<br>
&gt; #46: What is needed from IP and ICMP (submitted for Chris Dearlove)<br=
>
&gt;<br>
&gt;=C2=A0 =C2=A0The protocol needs many things from IP, such as failed rou=
ting<br>
&gt;=C2=A0 =C2=A0notification, and interacts with it in ways such as queuin=
g packets.<br>
&gt;=C2=A0 =C2=A0It also interacts (sends and receives) with ICMP, and I&#3=
9;m not sure<br>
&gt;=C2=A0 =C2=A0what else. This needs to be put together, so the reader ca=
n see what<br>
&gt;=C2=A0 =C2=A0is needed to be able to implement this.<br>
&gt;<br>
<br>
--<br>
Regards,<br>
Charlie P.<br>
<br>
********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<br>
_______________________________________________<br>
manet mailing list<br>
<a>manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div>

--089e0115ee46499010050280d9f0--


From nobody Sun Sep  7 15:07:00 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D668A1A071C for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 15:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dF0cNcyOcBrk for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 15:06:55 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4CFE1A00D8 for <manet@ietf.org>; Sun,  7 Sep 2014 15:06:54 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id m15so665134wgh.20 for <manet@ietf.org>; Sun, 07 Sep 2014 15:06:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=4jE5ZB4ehom1aqPHIlNtXq0aJmWXebDVOr2PnUfEG48=; b=fvzxVC0cuFsjDnn5rD8lDO2wxoOZDCI30Czkzf4eunUxWS2nQv1gqjUhF4B4ow7i6S OOz+j6F15ax4Piua5xneW0sfqrbyhmEuJ/3LdZVkuNOHod8wXuoG0G1zg8boo9qWCEyf nO8qDeiwOUV2y/3987mcuBCQqcOpFwEmJBi4LCK/6Qt1beJ+osvpbOWwPNKfTuiXbN2S u+QA1Ai/2PwlCjt4mgRNa8bLoBI0Ci6jT9Xap0sVNttFmjAdysTMBgAB7g08Jcc3YRlt GO8SA2LWiclZ+S3xHddfEGCnsZZOXeQmnYxMUI9TriyIuclq+Qs6ZZX+Vydn6JIjeVeW 072w==
X-Received: by 10.195.11.200 with SMTP id ek8mr30541472wjd.85.1410127613411; Sun, 07 Sep 2014 15:06:53 -0700 (PDT)
Received: from [192.168.254.1] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id lh11sm9586524wic.17.2014.09.07.15.06.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 07 Sep 2014 15:06:51 -0700 (PDT)
References: <061.89377601617f43ae76e225162010f923@trac.tools.ietf.org> <53CC9987.6060104@computer.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECF7@GLKXM0002V.GREENLNK.net> <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-2F28088B-DA7B-4E19-9BA1-5E1CA64BE0C3
Content-Transfer-Encoding: 7bit
Message-Id: <27C653BA-BCF1-48BA-819B-FC7CFC89AD72@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Sun, 7 Sep 2014 23:06:50 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/Rqn4k7WdYT8yMUP8xifSUCl5hQY
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 22:06:58 -0000

--Apple-Mail-2F28088B-DA7B-4E19-9BA1-5E1CA64BE0C3
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

First, I think you'll find I understand everything a lot better than either y=
ou do, or you think I do.

Second, AODV was an experimental protocol. AODVv2 is aiming at Proposed Stan=
dard. Which requires a higher standard - which it doesn't meet, AODVv1 was a=
ctually better specified than AODVv2 is.

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 7 Sep 2014, at 23:01, Abdussalam Baryun <abdussalambaryun@gmail.com> wr=
ote:
>=20
> Hi Chris,
>=20
> I think you may misunderstand MANET  reactive routing. I don't see your re=
ply answers the editor question of examples of AODVv2 needs from IP or ICMP.=
 You mention that the protocol needs to see ICMP, what is the problem with t=
hat as RFC3561 already has similar issue and already accepted by WG.=20
>=20
> AB
>=20
>> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>> Just for a start you also need to know that IP routes are requested, that=
 packets are flowing, and to have the ability to queue packets. I'm pretty s=
ure not all of those are mandated by IP. The routing protocol also needs to s=
ee ICMP messages - is that normal?
>>=20
>> As I said, it's a matter of what the whole architecture looks like.
>=20
> I think MANET still did not specify its whole architecture.=20
> =20
>>=20
>> --
>> Christopher Dearlove
>> Senior Principal Engineer, Information Assurance Group
>> Communications, Networks and Image Analysis Capability
>> BAE Systems Advanced Technology Centre
>> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
>> Tel: +44 1245 242194 |  Fax: +44 1245 242124
>> chris.dearlove@baesystems.com | http://www.baesystems.com
>>=20
>> BAE Systems (Operations) Limited
>> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
, Farnborough, Hants, GU14 6YU, UK
>> Registered in England & Wales No: 1996687
>>=20
>>=20
>> -----Original Message-----
>> From: Charles E. Perkins [mailto:charliep@computer.org]
>> Sent: 21 July 2014 05:40
>> To: manet@ietf.org; draft-ietf-manet-aodvv2@tools.ietf.org; Dearlove, Chr=
istopher (UK)
>> Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submi=
tted for Chris Dearlove)
>>=20
>> ----------------------! WARNING ! ---------------------- This message ori=
ginates from outside our organisation, either from an external partner or fr=
om the internet.
>> Consider carefully whether you should click on any links, open any attach=
ments or reply.
>> Follow the 'Report Suspicious Emails' link on IT matters for instructions=
 on reporting suspicious email messages.
>> --------------------------------------------------------
>>=20
>> Hello Chris,
>>=20
>> I am pretty sure that the only things needed from IP and ICMP are feature=
s that are already mandated by IP (including ICMP).  If there were danger th=
at AODVv2 might require optional features of IP or optional features of ICMP=
, I could understand your concern.  As it is, I do not understand exactly wh=
at is needed to enhance implementability of the specification.
>>=20
>> The only thing expected from ICMP is delivery of Destination Unreachable (=
Type 3 Code 1).  Is this something that implementations are unlikely to prov=
ide?
>>=20
>> I am confused about what (other than ICMP) AODVv2 "needs" from IP that co=
uld cause a problem.  True, we do expect IP to find the proper outgoing inte=
rface, and to perform longest-prefix-first matching, and so on...
>>=20
>> Do you have an example of some other protocol specification that lists th=
ese kinds of dependencies?
>>=20
>>=20
>> On 7/20/2014 8:42 PM, manet issue tracker wrote:
>> > #46: What is needed from IP and ICMP (submitted for Chris Dearlove)
>> >
>> >   The protocol needs many things from IP, such as failed routing
>> >   notification, and interacts with it in ways such as queuing packets.
>> >   It also interacts (sends and receives) with ICMP, and I'm not sure
>> >   what else. This needs to be put together, so the reader can see what
>> >   is needed to be able to implement this.
>> >
>>=20
>> --
>> Regards,
>> Charlie P.
>>=20
>> ********************************************************************
>> 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
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-2F28088B-DA7B-4E19-9BA1-5E1CA64BE0C3
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>First, I think you'll find I understan=
d everything a lot better than either you do, or you think I do.</div><div><=
br></div><div>Second, AODV was an experimental protocol. AODVv2 is aiming at=
 Proposed Standard. Which requires a higher standard - which it doesn't meet=
, AODVv1 was actually better specified than AODVv2 is.<br><br>-- &nbsp;<div>=
Christopher Dearlove</div><div><a href=3D"mailto:christopher.dearlove@gmail.=
com">christopher.dearlove@gmail.com</a> (iPhone)</div><div><a href=3D"mailto=
:chris@mnemosyne.demon.co.uk">chris@mnemosyne.demon.co.uk</a> (home)</div></=
div><div><br>On 7 Sep 2014, at 23:01, Abdussalam Baryun &lt;<a href=3D"mailt=
o:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:<br><=
br></div><blockquote type=3D"cite"><div>Hi Chris,<div><br></div><div>I think=
 you may misunderstand MANET&nbsp;&nbsp;reactive routing. I don't see your r=
eply answers the editor question of examples of AODVv2 needs from IP or ICMP=
. You mention that the protocol needs to see ICMP, what is the problem with t=
hat as&nbsp;RFC3561 already has similar issue and already accepted by WG.&nb=
sp;</div><div><br></div><div>AB<br><br>On Tuesday, July 22, 2014, Dearlove, C=
hristopher (UK)  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just for a start yo=
u also need to know that IP routes are requested, that packets are flowing, a=
nd to have the ability to queue packets. I'm pretty sure not all of those ar=
e mandated by IP. The routing protocol also needs to see ICMP messages - is t=
hat normal?<br>
<br>
As I said, it's a matter of what the whole architecture looks like.</blockqu=
ote><div><br></div><div>I think MANET still did not specify its whole archit=
ecture.&nbsp;</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Information Assurance Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: +44 1245 242194&nbsp;|&nbsp; Fax: +44 1245 242124<br>
<a>chris.dearlove@baesystems.com</a>&nbsp;| <a href=3D"http://www.baesystems=
.com" target=3D"_blank">http://www.baesystems.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Fa=
rnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<br>
From: Charles E. Perkins [mailto:<a>charliep@computer.org</a>]<br>
Sent: 21 July 2014 05:40<br>
To: <a>manet@ietf.org</a>; <a>draft-ietf-manet-aodvv2@tools.ietf.org</a>; De=
arlove, Christopher (UK)<br>
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitte=
d for Chris Dearlove)<br>
<br>
----------------------! WARNING ! ---------------------- This message origin=
ates from outside our organisation, either from an external partner or from t=
he internet.<br>
Consider carefully whether you should click on any links, open any attachmen=
ts or reply.<br>
Follow the 'Report Suspicious Emails' link on IT matters for instructions on=
 reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
Hello Chris,<br>
<br>
I am pretty sure that the only things needed from IP and ICMP are features t=
hat are already mandated by IP (including ICMP).&nbsp; If there were danger t=
hat AODVv2 might require optional features of IP or optional features of ICM=
P, I could understand your concern.&nbsp; As it is, I do not understand exac=
tly what is needed to enhance implementability of the specification.<br>
<br>
The only thing expected from ICMP is delivery of Destination Unreachable (Ty=
pe 3 Code 1).&nbsp; Is this something that implementations are unlikely to p=
rovide?<br>
<br>
I am confused about what (other than ICMP) AODVv2 "needs" from IP that could=
 cause a problem.&nbsp; True, we do expect IP to find the proper outgoing in=
terface, and to perform longest-prefix-first matching, and so on...<br>
<br>
Do you have an example of some other protocol specification that lists these=
 kinds of dependencies?<br>
<br>
<br>
On 7/20/2014 8:42 PM, manet issue tracker wrote:<br>
&gt; #46: What is needed from IP and ICMP (submitted for Chris Dearlove)<br>=

&gt;<br>
&gt;&nbsp; &nbsp;The protocol needs many things from IP, such as failed rout=
ing<br>
&gt;&nbsp; &nbsp;notification, and interacts with it in ways such as queuing=
 packets.<br>
&gt;&nbsp; &nbsp;It also interacts (sends and receives) with ICMP, and I'm n=
ot sure<br>
&gt;&nbsp; &nbsp;what else. This needs to be put together, so the reader can=
 see what<br>
&gt;&nbsp; &nbsp;is needed to be able to implement this.<br>
&gt;<br>
<br>
--<br>
Regards,<br>
Charlie P.<br>
<br>
********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<br>
_______________________________________________<br>
manet mailing list<br>
<a>manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>manet mailing list</span><br><sp=
an><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mai=
lman/listinfo/manet</a></span><br></div></blockquote></body></html>=

--Apple-Mail-2F28088B-DA7B-4E19-9BA1-5E1CA64BE0C3--


From nobody Sun Sep  7 15:08:19 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 176C81A00D8 for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 15:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MU4deCxs5bFf for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 15:08:15 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F13B31A00AF for <manet@ietf.org>; Sun,  7 Sep 2014 15:08:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id D38261BC83A1; Sun,  7 Sep 2014 15:08:14 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 979061BC83A0; Sun,  7 Sep 2014 15:08:13 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-E2070EAC-A1D2-4A98-BF85-FD37F31CE34A
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (11D257)
In-Reply-To: <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com>
Date: Mon, 8 Sep 2014 00:08:10 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <EC3ED700-C32C-4EAA-BB92-E2E53538B20F@thomasclausen.org>
References: <061.89377601617f43ae76e225162010f923@trac.tools.ietf.org> <53CC9987.6060104@computer.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECF7@GLKXM0002V.GREENLNK.net> <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/z5XaFWZPsRZ__ddl2eD6a4hj9jw
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 22:08:17 -0000

--Apple-Mail-E2070EAC-A1D2-4A98-BF85-FD37F31CE34A
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable


> On 08 Sep 2014, at 00:01, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
>=20
> Hi Chris,
>=20
> I think you may misunderstand MANET  reactive routing.

I sincerely doubt that Chris misunderstands MANET routing (reactive, or othe=
rwise)  ... in fact, he's co-author of the majority of RFCs produced by the M=
ANET wg, so I think that he's been around the field by now...

> I don't see your reply answers the editor question of examples of AODVv2 n=
eeds from IP or ICMP. You mention that the protocol needs to see ICMP, what i=
s the problem with that as RFC3561 already has similar issue and already acc=
epted by WG.=20

1) RFC3561 is an experimental RFC

2) The fact that there is a problem in RFC3561 is no excuse for repeating th=
at same problem
    in a subsequent protocol description.

Thomas

>=20
> AB
>=20
>> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>> Just for a start you also need to know that IP routes are requested, that=
 packets are flowing, and to have the ability to queue packets. I'm pretty s=
ure not all of those are mandated by IP. The routing protocol also needs to s=
ee ICMP messages - is that normal?
>>=20
>> As I said, it's a matter of what the whole architecture looks like.
>=20
> I think MANET still did not specify its whole architecture.=20
> =20
>>=20
>> --
>> Christopher Dearlove
>> Senior Principal Engineer, Information Assurance Group
>> Communications, Networks and Image Analysis Capability
>> BAE Systems Advanced Technology Centre
>> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
>> Tel: +44 1245 242194 |  Fax: +44 1245 242124
>> chris.dearlove@baesystems.com | http://www.baesystems.com
>>=20
>> BAE Systems (Operations) Limited
>> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
, Farnborough, Hants, GU14 6YU, UK
>> Registered in England & Wales No: 1996687
>>=20
>>=20
>> -----Original Message-----
>> From: Charles E. Perkins [mailto:charliep@computer.org]
>> Sent: 21 July 2014 05:40
>> To: manet@ietf.org; draft-ietf-manet-aodvv2@tools.ietf.org; Dearlove, Chr=
istopher (UK)
>> Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submi=
tted for Chris Dearlove)
>>=20
>> ----------------------! WARNING ! ---------------------- This message ori=
ginates from outside our organisation, either from an external partner or fr=
om the internet.
>> Consider carefully whether you should click on any links, open any attach=
ments or reply.
>> Follow the 'Report Suspicious Emails' link on IT matters for instructions=
 on reporting suspicious email messages.
>> --------------------------------------------------------
>>=20
>> Hello Chris,
>>=20
>> I am pretty sure that the only things needed from IP and ICMP are feature=
s that are already mandated by IP (including ICMP).  If there were danger th=
at AODVv2 might require optional features of IP or optional features of ICMP=
, I could understand your concern.  As it is, I do not understand exactly wh=
at is needed to enhance implementability of the specification.
>>=20
>> The only thing expected from ICMP is delivery of Destination Unreachable (=
Type 3 Code 1).  Is this something that implementations are unlikely to prov=
ide?
>>=20
>> I am confused about what (other than ICMP) AODVv2 "needs" from IP that co=
uld cause a problem.  True, we do expect IP to find the proper outgoing inte=
rface, and to perform longest-prefix-first matching, and so on...
>>=20
>> Do you have an example of some other protocol specification that lists th=
ese kinds of dependencies?
>>=20
>>=20
>> On 7/20/2014 8:42 PM, manet issue tracker wrote:
>> > #46: What is needed from IP and ICMP (submitted for Chris Dearlove)
>> >
>> >   The protocol needs many things from IP, such as failed routing
>> >   notification, and interacts with it in ways such as queuing packets.
>> >   It also interacts (sends and receives) with ICMP, and I'm not sure
>> >   what else. This needs to be put together, so the reader can see what
>> >   is needed to be able to implement this.
>> >
>>=20
>> --
>> Regards,
>> Charlie P.
>>=20
>> ********************************************************************
>> 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
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-E2070EAC-A1D2-4A98-BF85-FD37F31CE34A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><br></div><div>On 08 Sep 2014, at 00:0=
1, Abdussalam Baryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">abdus=
salambaryun@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite">=
<div>Hi Chris,<div><br></div><div>I think you may misunderstand MANET&nbsp;&=
nbsp;reactive routing. </div></div></blockquote><div><br></div><div>I sincer=
ely doubt that Chris misunderstands MANET routing (reactive, or otherwise) &=
nbsp;... in fact, he's co-author of the majority of RFCs produced by the MAN=
ET wg, so I think that he's been around the field by now...</div><div><br></=
div><blockquote type=3D"cite"><div><div>I don't see your reply answers the e=
ditor question of examples of AODVv2 needs from IP or ICMP. You mention that=
 the protocol needs to see ICMP, what is the problem with that as&nbsp;RFC35=
61 already has similar issue and already accepted by WG.&nbsp;</div></div></=
blockquote><div><br></div>1) RFC3561 is an experimental RFC<div><br><div>2) T=
he fact that there is a problem in RFC3561 is no excuse for repeating that s=
ame problem</div><div>&nbsp; &nbsp; in a subsequent protocol description.</d=
iv><div><br></div><div>Thomas</div><div><br><blockquote type=3D"cite"><div><=
div><br></div><div>AB<br><br>On Tuesday, July 22, 2014, Dearlove, Christophe=
r (UK)  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">Just for a start you also ne=
ed to know that IP routes are requested, that packets are flowing, and to ha=
ve the ability to queue packets. I'm pretty sure not all of those are mandat=
ed by IP. The routing protocol also needs to see ICMP messages - is that nor=
mal?<br>
<br>
As I said, it's a matter of what the whole architecture looks like.</blockqu=
ote><div><br></div><div>I think MANET still did not specify its whole archit=
ecture.&nbsp;</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Information Assurance Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: +44 1245 242194&nbsp;|&nbsp; Fax: +44 1245 242124<br>
<a>chris.dearlove@baesystems.com</a>&nbsp;| <a href=3D"http://www.baesystems=
.com" target=3D"_blank">http://www.baesystems.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Fa=
rnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
-----Original Message-----<br>
From: Charles E. Perkins [mailto:<a>charliep@computer.org</a>]<br>
Sent: 21 July 2014 05:40<br>
To: <a>manet@ietf.org</a>; <a>draft-ietf-manet-aodvv2@tools.ietf.org</a>; De=
arlove, Christopher (UK)<br>
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitte=
d for Chris Dearlove)<br>
<br>
----------------------! WARNING ! ---------------------- This message origin=
ates from outside our organisation, either from an external partner or from t=
he internet.<br>
Consider carefully whether you should click on any links, open any attachmen=
ts or reply.<br>
Follow the 'Report Suspicious Emails' link on IT matters for instructions on=
 reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
Hello Chris,<br>
<br>
I am pretty sure that the only things needed from IP and ICMP are features t=
hat are already mandated by IP (including ICMP).&nbsp; If there were danger t=
hat AODVv2 might require optional features of IP or optional features of ICM=
P, I could understand your concern.&nbsp; As it is, I do not understand exac=
tly what is needed to enhance implementability of the specification.<br>
<br>
The only thing expected from ICMP is delivery of Destination Unreachable (Ty=
pe 3 Code 1).&nbsp; Is this something that implementations are unlikely to p=
rovide?<br>
<br>
I am confused about what (other than ICMP) AODVv2 "needs" from IP that could=
 cause a problem.&nbsp; True, we do expect IP to find the proper outgoing in=
terface, and to perform longest-prefix-first matching, and so on...<br>
<br>
Do you have an example of some other protocol specification that lists these=
 kinds of dependencies?<br>
<br>
<br>
On 7/20/2014 8:42 PM, manet issue tracker wrote:<br>
&gt; #46: What is needed from IP and ICMP (submitted for Chris Dearlove)<br>=

&gt;<br>
&gt;&nbsp; &nbsp;The protocol needs many things from IP, such as failed rout=
ing<br>
&gt;&nbsp; &nbsp;notification, and interacts with it in ways such as queuing=
 packets.<br>
&gt;&nbsp; &nbsp;It also interacts (sends and receives) with ICMP, and I'm n=
ot sure<br>
&gt;&nbsp; &nbsp;what else. This needs to be put together, so the reader can=
 see what<br>
&gt;&nbsp; &nbsp;is needed to be able to implement this.<br>
&gt;<br>
<br>
--<br>
Regards,<br>
Charlie P.<br>
<br>
********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<br>
_______________________________________________<br>
manet mailing list<br>
<a>manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>manet mailing list</span><br><sp=
an><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mai=
lman/listinfo/manet</a></span><br></div></blockquote></div></div></body></ht=
ml>=

--Apple-Mail-E2070EAC-A1D2-4A98-BF85-FD37F31CE34A--


From nobody Sun Sep  7 23:01:06 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB8B71A6F13 for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 23:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z_saGj8dev6p for <manet@ietfa.amsl.com>; Sun,  7 Sep 2014 23:01:03 -0700 (PDT)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D4031A6F12 for <manet@ietf.org>; Sun,  7 Sep 2014 23:01:03 -0700 (PDT)
Received: by mail-qc0-f181.google.com with SMTP id i17so14739831qcy.40 for <manet@ietf.org>; Sun, 07 Sep 2014 23:01:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=sFFMjqTKU36QbdFWzSrZMuD0w9I2A4wylpxFscJ12t4=; b=lU8ErChU4uB/95I9Dp8dM65St0x040jK0nvtdWL6E6+/0uA9ewuogm/q93yA9kLN6S KeR8pZpoMHDuVHCls00vHXZAGb3cUTIg4w/Z/cE17lQzoql/8hJl4iHiuL7Li2mJbWYf 4tvoHoxnaiK7ZG1FpE4BOjnMXraP6iZ/JM3lRodjnnSHinUcvIeWZnfQTmZykWcNsgaS X+HneO0X5i3lsB9uQ7SQ9GK7sK0qwOsAG2W1pbHuEiAzoq4mGnbnhapiBNqrVTYnyULm 5d0P+URGXoT2tunf30aH9mGxRLAUmd9qPT5UG8iOTQNO8pCSIEkrO2HYZi5HFLu3jRZ7 T89A==
X-Received: by 10.140.86.6 with SMTP id o6mr37880144qgd.71.1410156062581; Sun, 07 Sep 2014 23:01:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Sun, 7 Sep 2014 23:00:42 -0700 (PDT)
In-Reply-To: <A5DD62E7-82EC-4ACF-8A71-A9ADF81827A8@gmail.com>
References: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org> <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com> <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com> <A5DD62E7-82EC-4ACF-8A71-A9ADF81827A8@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Mon, 8 Sep 2014 08:00:42 +0200
Message-ID: <CAGnRvuo3+MHAka8xPHdT3tboPx-7C2n-MmUKQ==ORhsd7TO8Rg@mail.gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/1RP4wqwzcYRWmLiK4hqLoRvw3dc
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>, "Stan Ratliff \(sratliff\)" <sratliff@cisco.com>
Subject: Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 06:01:05 -0000

On Sun, Sep 7, 2014 at 10:55 PM, Christopher Dearlove
<christopher.dearlove@gmail.com> wrote:
> As Stan has said, with one addition (unless Stan said it and I missed it).
> 5444 describes how messages can be multiplexed. 5498 says (as part of its
> using of the MANET protocol or port) you must use that multiplexing method.
> The WG has decided that means the protocols it is developing (with the
> obvious exception of DLEP that isn't a MANET routing protocol).

There is also the point that the whole focus on a TLV based format
becomes mostly pointless when you put that much information into
non-tlv parts like element order that you loose too much flexibility
and extensibility.

One of the "lesson learned" from RFC3626 was that you should never
assume that you know what you need in a protocol. RFC3626 allowed a
add new messages to the protocol, but it didn't allow to add
information to existing messages. RFC5444 (as a packet format) tries
to solve this problem.

Henning Rogge


From nobody Mon Sep  8 05:47:53 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1962E1A8799 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 05:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_35=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NwSsYCmUAQD for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 05:47:49 -0700 (PDT)
Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 252251A87A5 for <manet@ietf.org>; Mon,  8 Sep 2014 05:47:48 -0700 (PDT)
Received: by mail-yk0-f177.google.com with SMTP id 79so2047829ykr.8 for <manet@ietf.org>; Mon, 08 Sep 2014 05:47:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O0fEoakFUi+hTPHvFR5t/8R5Ds4pd5tRPYycZcDGLMs=; b=iyxas/FOhQ8IMZZt4vifwHL8kaQ0CitUh/EvqjqqsL7zI2xWwPaI4NKPpCx1VuWjiz EmsOjn53XK/WX74wVBVSat2vNN6fbJczv7+YZoGBDEzKmas0OWkSREz6zS8ttFSa0ITb 8DtFOA7lh7Y8O/K1ARuN6UP8daxMjWfZCy/xIZuDzvo19MEG9iyhi7sCA8zvqNs2IaMF YPPLn56L4cVC3+n0xnOzAtUCGUgvAm/tRnLnirdqf7sKvcLkYYDo0PxHyc2CulP5HvDu r5XwOJ6s9t9WIQhrKzLr3FiFg1hxff+6GXiuqB/en8jl4VVIBdX8ghghUn1ZSExLFqvq pE6w==
MIME-Version: 1.0
X-Received: by 10.236.120.101 with SMTP id o65mr268505yhh.166.1410180466865; Mon, 08 Sep 2014 05:47:46 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Mon, 8 Sep 2014 05:47:46 -0700 (PDT)
In-Reply-To: <061.6938ca142d915a879b2e5bc46f790232@trac.tools.ietf.org>
References: <061.6938ca142d915a879b2e5bc46f790232@trac.tools.ietf.org>
Date: Mon, 8 Sep 2014 14:47:46 +0200
Message-ID: <CADnDZ89ivqZOH6S9vPQ9W34P8GK8ja_U=y8Z-+xJTxmeXFx+vQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: manet@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/1cYHOZ6dNoDLGBpCaKVPOmKLaOg
Cc: draft-ietf-manet-aodvv2@tools.ietf.org
Subject: Re: [manet] #32 (aodvv2): Multicast transmission
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 12:47:50 -0000

On 4/3/14, manet issue tracker <trac+manet@trac.tools.ietf.org> wrote:
> #32: Multicast transmission
>
>  (Thomas Clausen)
>
>  Section 5.4:
>
>  {{{
>                  In order to reduce multicast overhead, retransmitting
>                  multicast packets in MANETs SHOULD be done according to
>                  methods specified in [RFC6621]
>  }}}
>
>
>  What happens if that "SHOULD" is not done? Does it break interoperability?

The draft guides to RFC6621 as reducing overhead option. There is no
break from my understandning. If you have break example or analysis
please provide for progress.

 That multicast-overhead is a multicast protocol problem not this
draft problem. Reactive multicast can be done in future after
finishing this. I know that multicast in reactive protocol is
important that is why I suggested before to the WG that we postpone
any reactive multicast work until we finish this work (I argued with
Thomas this issue). Do you mean RFC6621 did not consider reactive
protocol use of it, if that is the meaning then we should update
RFC6621 to consider that.

>  Also, RFC6621 is not std.track, so this is a downref that requires special
>  handling. I note that SHOULD is a fairly strong normative statement, but
>  the RFC6621 is cited as an informational reference. This does not appear
>  appropriate.

I am not sure about that normative issues. But I see there is a
condition as if you want to reduce overhead then go for RFC6621. I
don't mind that we edit that "SHOULD" into "should".

>
>  And finally, RFC6621 specifies a number of different algorithms and modes
>  of operation, some of which require additional signalling.  For
>  interoperable implementations to result, this is insufficient.

I suggest we add that the draft does not go into details of RFC6621
modes, I suggest that to be done in another draft.

AB


From nobody Mon Sep  8 06:47:30 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A9FA1A8824 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 06:47:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AmUfTFnyz4Y0 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 06:47:27 -0700 (PDT)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6116A1A8822 for <manet@ietf.org>; Mon,  8 Sep 2014 06:47:27 -0700 (PDT)
Received: by mail-yh0-f47.google.com with SMTP id c41so9051881yho.6 for <manet@ietf.org>; Mon, 08 Sep 2014 06:47:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ycnWKHLpgB5Ky6FmTAuljq9ihqEAuFXnKEZqQxKwXFs=; b=xaSC/b8QjCJwjoDcTGlSZdEc3n5mH0jmDlggneZ46zrHEQ5u74RJEiZQgjL+eCqa+I CB/B8mCKUzhn+t6DAIQf39rF/NCAL0AFxZs6xGfYtAtgwufMQBqThBhv9zR36HN5mTT5 ufAN1kXAGpszhznmr5/tCRU0PceqhFoPMYzdj7npM3r58OwaEqIxujKccCkZ7FuUvF7K TSa9+ga/s0P/y4dyaj9T1xB7yI7twVa9mUL8lrnEFqzJbwbi7yfvOKw9g3dkppfxwszR 9Yl4wHMTgLKL/Ie0FARGI76NnefY/fXzAxAEWP3Ne7/L+Y/PwrIIIF3ERbYyCTMR7aqJ +bcw==
MIME-Version: 1.0
X-Received: by 10.236.222.103 with SMTP id s97mr4816516yhp.106.1410184046661;  Mon, 08 Sep 2014 06:47:26 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Mon, 8 Sep 2014 06:47:26 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net>
Date: Mon, 8 Sep 2014 15:47:26 +0200
Message-ID: <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/dKpZoeKwonL8gITUq_AkUnh9UYY
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 13:47:29 -0000

> On Mon, Jul 21, 2014 at 5:40 AM, manet issue tracker
> <trac+manet@trac.tools.ietf.org<mailto:trac+manet@trac.tools.ietf.org>>
> wrote:
> #45: RFC 5498 non-compliance (submitted for Chris Dearlove)
>
>  The document is completely noncompliant with the RFC 5444 multiplexing
>  mechanism, mandated by RFC 5498 (on the manet port/protocol). It does
>  many things that are not within its competence.
>
On 7/21/14, Charles E. Perkins <charliep@computer.org> wrote:
>
> Hello Chris,
>
> The document states:
>
>>    In its default mode of operation, AODVv2 sends messages using the
>>    parameters for port number and IP protocol specified in [RFC5498] to
>>    carry protocol packets.  By default, AODVv2 messages are sent with
>>    the IP destination address set to the link-local multicast address
>>    LL-MANET-Routers [RFC5498] unless otherwise specified. Therefore,
>>    all AODVv2 routers MUST subscribe to LL-MANET-Routers [RFC5498] to
>>    receiving AODVv2 messages.
>
> So, I suspect the problem lies elsewhere.  Could you point to the
> noncompliant part of the AODVv2 specification, and the protocol
> mandate for which the AODVv2 specification is noncompliant?
>

On 7/22/14, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> wrote:
> The quoted text is irrelevant to this point.
>
> As has been said many times, packets belong to the multiplexer, messages to
> the protocol. There are many pieces of text specifying things about packets
> that are out of the competence of the protocol. I'm afraid I stopped marking
> them on my copy.
>
> (For exactly how the protocol can interact with packets, see 5444.)
>


I don't think packets should only blong to multiplexer/parsers.
5444-Packets COULD be generated by protocols not only multiplexer.
IMHO, There is no specification that states that 5444-packets are
generated only by parsers/multiplexer (If I am wrong please point to
it). The RFC5444-packet is for the protocol-designer to define not the
parser-designer. The parser-designer needs to follow the
protocol-designer. You cannot force a router vendor to not define its
own 5444-packets for its routing protocol. I remember that within the
Packet-bb submission (now is RFC5444) there was a discussion between
Teco and Thomas that there are many issues related to parsing and
multiplexing that this RFC5444/Packet-bb-draft does not specify and
did not solve. This issue needs more discussion in the WG, because I
don't find consensus on the issue.

On 7/22/14, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> wrote:
> RFC5444 describes a multiplexing process. It is not required purely in its
> own terms.

Yes it is not required because RFC5444 is just format standard,
RFC5444 is not parsing standard, RFC5444 is not a packet-multiplex
standard. The multiplex in just explained in appendix which is not
normative, and IMHO the WG did not agree on specific multiplexing
standard. One participant yesterday mentioned the multiplex as in that
Appendix is a MUST, which I disagree.

> But RFC 5498 make it mandatory for any protocol using the
> port/protocol allocated by that RFC. And the WG has agreed that all routing
> protocols developed have to be able (at least) to use that port/protocol.

RFC5498 is for one one RFC5444 packet, please note that RFC5444 is a
general packet format, protocols can define their own
packets/messages. I understand that you suggest unifying the packet
for all MANET protocols but that is not specified in RFC5444. RFC5444
already states clearly that packets/messages are formated but parsing
is general-logic and independent from protocol. In IETF 5444 parsing
is not specified yet, just logic. see below:


{{{

The specification has been explicitly designed with the following
properties, listed in no particular order, in mind:

Parsing logic - The notation used in this specification facilitates
generic, protocol-independent parsing logic.

Extensibility - Packets and messages defined by a protocol using
this specification are extensible by defining new messages and new
TLVs. Protocols using this specification will be able to
correctly identify and skip such new messages and TLVs, while
correctly parsing the remainder of the packet and message.

}}}

It does not state unify parsing as general but just general parsing to
be independent, so we design AODVv2 independently from parsing and
even independent of multiplexing packets.

I suggest we work on this draft AODVv2 independently from
parsing/multiplexing as the RFC5444 suggested which AODVv2 uses
correctly so far by my understandning and no much answers received for
editor questions related to the draft.

Best Regards,
AB


From nobody Mon Sep  8 08:26:17 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D36351A885A for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 08:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ufYQmeKAAA3 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 08:26:13 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F3A71A8872 for <manet@ietf.org>; Mon,  8 Sep 2014 08:26:13 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id bs8so2867600wib.9 for <manet@ietf.org>; Mon, 08 Sep 2014 08:26:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:mime-version:content-type:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=x0eM1hF18C1p1pSg0RKdFy50dal0O+yc2C2NI0MuDvk=; b=ZdsohRs+EL/5Z8acWVfNClJUUFd4T8xbXX7mPig9t2qZHBr8eekQDzKP1G+JymBBK4 tUmhwGFXyACDizQMBW16PoAqynDWBmFKp7omdmXimW27yizygdXOmiyG4eMgDWNLtvhX H9sD4Wnv1ZKMDNPEpo0tujH5G9WNqqYhqV0Xlzxt2oBrxDJQKtrk/Sa+mOyTZeb5Els4 rXcbGzZjeKOvCFSE3hyQNYMr/sjKmNBBmA0Pjw5d7oAGEuXWR3SjX4pMQgmbrL57MxKK 9ovKjZY8K8CWxUOS2rzOyF3aBy6GFyfIchrld2Jwxq5ZacPEUFN3iECVHtfUAc5BKpxS +RSg==
X-Received: by 10.194.71.74 with SMTP id s10mr4389803wju.116.1410189971915; Mon, 08 Sep 2014 08:26:11 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id eh3sm12119395wic.4.2014.09.08.08.26.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 08:26:10 -0700 (PDT)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
X-Google-Original-From: Christopher Dearlove <chris@mnemosyne.demon.co.uk>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com>
Date: Mon, 8 Sep 2014 16:26:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/P2Mo3UB-Em3sPCxOGKqT0ySkd0o
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 15:26:16 -0000

Really, I'm not wading through all that, as it becomes apparent early on =
that it misses the whole point.
- 5444 defines a packet/message format,
- 5444 defines how that can be used by a multiplexer. Yes, at this point =
that's optional.
- 5498 makes use of that multiplexing approach mandatory on the manet =
protocol/port.
- The WG (in agreement with ADs etc.) has decided that MANET routing =
protocols it designs are to use the manet protocol/port.

Put all that together, and you have the state of play. Doesn't matter if =
you don't think that's so or not. It is.

Of course anyone can use 5444 for some other purpose. Various options =
here. But none what's being discussed.

As for AODVv2 being noncompliant with 5444/5498, yes it is. It simple =
terms, packets belong to the multiplexer, messages belong to a protocol. =
So AODVv2 can define messages. It doesn't define packets. It can (and =
this is specified) get read access to the packet header, and (also =
specified) provide TLVs for the packet header as well as providing =
messages for packets. But that's not what's done either.

On 8 Sep 2014, at 14:47, Abdussalam Baryun wrote:

>> On Mon, Jul 21, 2014 at 5:40 AM, manet issue tracker
>> =
<trac+manet@trac.tools.ietf.org<mailto:trac+manet@trac.tools.ietf.org>>
>> wrote:
>> #45: RFC 5498 non-compliance (submitted for Chris Dearlove)
>>=20
>> The document is completely noncompliant with the RFC 5444 =
multiplexing
>> mechanism, mandated by RFC 5498 (on the manet port/protocol). It does
>> many things that are not within its competence.
>>=20
> On 7/21/14, Charles E. Perkins <charliep@computer.org> wrote:
>>=20
>> Hello Chris,
>>=20
>> The document states:
>>=20
>>>  In its default mode of operation, AODVv2 sends messages using the
>>>  parameters for port number and IP protocol specified in [RFC5498] =
to
>>>  carry protocol packets.  By default, AODVv2 messages are sent with
>>>  the IP destination address set to the link-local multicast address
>>>  LL-MANET-Routers [RFC5498] unless otherwise specified. Therefore,
>>>  all AODVv2 routers MUST subscribe to LL-MANET-Routers [RFC5498] to
>>>  receiving AODVv2 messages.
>>=20
>> So, I suspect the problem lies elsewhere.  Could you point to the
>> noncompliant part of the AODVv2 specification, and the protocol
>> mandate for which the AODVv2 specification is noncompliant?
>>=20
>=20
> On 7/22/14, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> =
wrote:
>> The quoted text is irrelevant to this point.
>>=20
>> As has been said many times, packets belong to the multiplexer, =
messages to
>> the protocol. There are many pieces of text specifying things about =
packets
>> that are out of the competence of the protocol. I'm afraid I stopped =
marking
>> them on my copy.
>>=20
>> (For exactly how the protocol can interact with packets, see 5444.)
>>=20
>=20
>=20
> I don't think packets should only blong to multiplexer/parsers.
> 5444-Packets COULD be generated by protocols not only multiplexer.
> IMHO, There is no specification that states that 5444-packets are
> generated only by parsers/multiplexer (If I am wrong please point to
> it). The RFC5444-packet is for the protocol-designer to define not the
> parser-designer. The parser-designer needs to follow the
> protocol-designer. You cannot force a router vendor to not define its
> own 5444-packets for its routing protocol. I remember that within the
> Packet-bb submission (now is RFC5444) there was a discussion between
> Teco and Thomas that there are many issues related to parsing and
> multiplexing that this RFC5444/Packet-bb-draft does not specify and
> did not solve. This issue needs more discussion in the WG, because I
> don't find consensus on the issue.
>=20
> On 7/22/14, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> =
wrote:
>> RFC5444 describes a multiplexing process. It is not required purely =
in its
>> own terms.
>=20
> Yes it is not required because RFC5444 is just format standard,
> RFC5444 is not parsing standard, RFC5444 is not a packet-multiplex
> standard. The multiplex in just explained in appendix which is not
> normative, and IMHO the WG did not agree on specific multiplexing
> standard. One participant yesterday mentioned the multiplex as in that
> Appendix is a MUST, which I disagree.
>=20
>> But RFC 5498 make it mandatory for any protocol using the
>> port/protocol allocated by that RFC. And the WG has agreed that all =
routing
>> protocols developed have to be able (at least) to use that =
port/protocol.
>=20
> RFC5498 is for one one RFC5444 packet, please note that RFC5444 is a
> general packet format, protocols can define their own
> packets/messages. I understand that you suggest unifying the packet
> for all MANET protocols but that is not specified in RFC5444. RFC5444
> already states clearly that packets/messages are formated but parsing
> is general-logic and independent from protocol. In IETF 5444 parsing
> is not specified yet, just logic. see below:
>=20
>=20
> {{{
>=20
> The specification has been explicitly designed with the following
> properties, listed in no particular order, in mind:
>=20
> Parsing logic - The notation used in this specification facilitates
> generic, protocol-independent parsing logic.
>=20
> Extensibility - Packets and messages defined by a protocol using
> this specification are extensible by defining new messages and new
> TLVs. Protocols using this specification will be able to
> correctly identify and skip such new messages and TLVs, while
> correctly parsing the remainder of the packet and message.
>=20
> }}}
>=20
> It does not state unify parsing as general but just general parsing to
> be independent, so we design AODVv2 independently from parsing and
> even independent of multiplexing packets.
>=20
> I suggest we work on this draft AODVv2 independently from
> parsing/multiplexing as the RFC5444 suggested which AODVv2 uses
> correctly so far by my understandning and no much answers received for
> editor questions related to the draft.
>=20
> Best Regards,
> AB
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Mon Sep  8 09:19:28 2014
Return-Path: <john.dowdell.ietf@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA921A8898 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 09:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLR08pz8Enyy for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 09:19:21 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 673591A8894 for <manet@ietf.org>; Mon,  8 Sep 2014 09:19:21 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id cc10so2988510wib.10 for <manet@ietf.org>; Mon, 08 Sep 2014 09:19:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=EWgNjXVITgJcAKtMSE5WX2JYEJpYFGV17dg3jXcin3A=; b=oJPvvYhgQlE5sTHQvqr0NFAazy0+5fHHPLoyhTnI1JCKCvQ0GU4a4Zud3LpOnXUHoR AN8xy5T7SctmjfakhEV9GsaYsIMpOShXySEMnE2fZG5AQdKAUzX6vj8VF0XHRhmqA2p0 oA5p744p+EpikkrWdo1U4yHItQ3u9AIknZeb4/M8S57SAsRnU8zB/LeTSNnyfxpJ2XcU o0E6/VH8luhgYZQ1VTQoSQoCzMerc4olpiO/Du4Wty+IitVJHJNRX9EFdDuxNTlP4It7 3AYffDpouDKueEJItUwv+nPeCLx4eoW9MIYYjTaJKC6V124cgiEb7QrAqkCwptTtq96D yi8A==
X-Received: by 10.181.5.42 with SMTP id cj10mr23608678wid.52.1410193160055; Mon, 08 Sep 2014 09:19:20 -0700 (PDT)
Received: from [10.0.4.178] ([217.158.48.187]) by mx.google.com with ESMTPSA id ba3sm12269267wib.10.2014.09.08.09.19.19 for <manet@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Sep 2014 09:19:19 -0700 (PDT)
Message-ID: <540DD706.5080203@gmail.com>
Date: Mon, 08 Sep 2014 17:19:18 +0100
From: John Dowdell <john.dowdell.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: manet@ietf.org
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk>
In-Reply-To: <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/3Ku9hiXq51ub0KdC8nID7OmFvTk
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 16:19:24 -0000

All

As part of ongoing author work on AODVv2, I am looking at the 
relationship between RFC5444 and AODVv2 right now. Hopefully we will 
have some material to discuss at the next meeting. In the meantime, 
constructive advice is welcome, both on and off-list.

John

On 08/09/14 16:26, Christopher Dearlove wrote:
> Really, I'm not wading through all that, as it becomes apparent early on that it misses the whole point.
> - 5444 defines a packet/message format,
> - 5444 defines how that can be used by a multiplexer. Yes, at this point that's optional.
> - 5498 makes use of that multiplexing approach mandatory on the manet protocol/port.
> - The WG (in agreement with ADs etc.) has decided that MANET routing protocols it designs are to use the manet protocol/port.
>
> Put all that together, and you have the state of play. Doesn't matter if you don't think that's so or not. It is.
>
> Of course anyone can use 5444 for some other purpose. Various options here. But none what's being discussed.
>
> As for AODVv2 being noncompliant with 5444/5498, yes it is. It simple terms, packets belong to the multiplexer, messages belong to a protocol. So AODVv2 can define messages. It doesn't define packets. It can (and this is specified) get read access to the packet header, and (also specified) provide TLVs for the packet header as well as providing messages for packets. But that's not what's done either.
>
> On 8 Sep 2014, at 14:47, Abdussalam Baryun wrote:
>
>>> On Mon, Jul 21, 2014 at 5:40 AM, manet issue tracker
>>> <trac+manet@trac.tools.ietf.org<mailto:trac+manet@trac.tools.ietf.org>>
>>> wrote:
>>> #45: RFC 5498 non-compliance (submitted for Chris Dearlove)
>>>
>>> The document is completely noncompliant with the RFC 5444 multiplexing
>>> mechanism, mandated by RFC 5498 (on the manet port/protocol). It does
>>> many things that are not within its competence.
>>>
>> On 7/21/14, Charles E. Perkins <charliep@computer.org> wrote:
>>> Hello Chris,
>>>
>>> The document states:
>>>
>>>>   In its default mode of operation, AODVv2 sends messages using the
>>>>   parameters for port number and IP protocol specified in [RFC5498] to
>>>>   carry protocol packets.  By default, AODVv2 messages are sent with
>>>>   the IP destination address set to the link-local multicast address
>>>>   LL-MANET-Routers [RFC5498] unless otherwise specified. Therefore,
>>>>   all AODVv2 routers MUST subscribe to LL-MANET-Routers [RFC5498] to
>>>>   receiving AODVv2 messages.
>>> So, I suspect the problem lies elsewhere.  Could you point to the
>>> noncompliant part of the AODVv2 specification, and the protocol
>>> mandate for which the AODVv2 specification is noncompliant?
>>>
>> On 7/22/14, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> wrote:
>>> The quoted text is irrelevant to this point.
>>>
>>> As has been said many times, packets belong to the multiplexer, messages to
>>> the protocol. There are many pieces of text specifying things about packets
>>> that are out of the competence of the protocol. I'm afraid I stopped marking
>>> them on my copy.
>>>
>>> (For exactly how the protocol can interact with packets, see 5444.)
>>>
>>
>> I don't think packets should only blong to multiplexer/parsers.
>> 5444-Packets COULD be generated by protocols not only multiplexer.
>> IMHO, There is no specification that states that 5444-packets are
>> generated only by parsers/multiplexer (If I am wrong please point to
>> it). The RFC5444-packet is for the protocol-designer to define not the
>> parser-designer. The parser-designer needs to follow the
>> protocol-designer. You cannot force a router vendor to not define its
>> own 5444-packets for its routing protocol. I remember that within the
>> Packet-bb submission (now is RFC5444) there was a discussion between
>> Teco and Thomas that there are many issues related to parsing and
>> multiplexing that this RFC5444/Packet-bb-draft does not specify and
>> did not solve. This issue needs more discussion in the WG, because I
>> don't find consensus on the issue.
>>
>> On 7/22/14, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> wrote:
>>> RFC5444 describes a multiplexing process. It is not required purely in its
>>> own terms.
>> Yes it is not required because RFC5444 is just format standard,
>> RFC5444 is not parsing standard, RFC5444 is not a packet-multiplex
>> standard. The multiplex in just explained in appendix which is not
>> normative, and IMHO the WG did not agree on specific multiplexing
>> standard. One participant yesterday mentioned the multiplex as in that
>> Appendix is a MUST, which I disagree.
>>
>>> But RFC 5498 make it mandatory for any protocol using the
>>> port/protocol allocated by that RFC. And the WG has agreed that all routing
>>> protocols developed have to be able (at least) to use that port/protocol.
>> RFC5498 is for one one RFC5444 packet, please note that RFC5444 is a
>> general packet format, protocols can define their own
>> packets/messages. I understand that you suggest unifying the packet
>> for all MANET protocols but that is not specified in RFC5444. RFC5444
>> already states clearly that packets/messages are formated but parsing
>> is general-logic and independent from protocol. In IETF 5444 parsing
>> is not specified yet, just logic. see below:
>>
>>
>> {{{
>>
>> The specification has been explicitly designed with the following
>> properties, listed in no particular order, in mind:
>>
>> Parsing logic - The notation used in this specification facilitates
>> generic, protocol-independent parsing logic.
>>
>> Extensibility - Packets and messages defined by a protocol using
>> this specification are extensible by defining new messages and new
>> TLVs. Protocols using this specification will be able to
>> correctly identify and skip such new messages and TLVs, while
>> correctly parsing the remainder of the packet and message.
>>
>> }}}
>>
>> It does not state unify parsing as general but just general parsing to
>> be independent, so we design AODVv2 independently from parsing and
>> even independent of multiplexing packets.
>>
>> I suggest we work on this draft AODVv2 independently from
>> parsing/multiplexing as the RFC5444 suggested which AODVv2 uses
>> correctly so far by my understandning and no much answers received for
>> editor questions related to the draft.
>>
>> Best Regards,
>> AB
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Mon Sep  8 10:21:00 2014
Return-Path: <charliep@computer.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 386C41A0019 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c69Mt1cHwTxV for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:20:57 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 0177E1A0013 for <manet@ietf.org>; Mon,  8 Sep 2014 10:20:56 -0700 (PDT)
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1XR2cV-0003mt-QC; Mon, 08 Sep 2014 13:20:52 -0400
Message-ID: <540DE570.2040006@computer.org>
Date: Mon, 08 Sep 2014 10:20:48 -0700
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Blue Skies
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
References: <061.89377601617f43ae76e225162010f923@trac.tools.ietf.org><53CC9987.6060104@computer.org><B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECF7@GLKXM0002V.GREENLNK.net> <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com>
In-Reply-To: <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030209070107030305050702"
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac72337f320e55d7bdf1b37c7676318df35350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/tzZ-jPniuXayOpNSghgMGNFkQzM
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, manet@ietf.org
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 17:20:58 -0000

This is a multi-part message in MIME format.
--------------030209070107030305050702
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Hello folks,

I did not follow-up on this in July because I didn't see exactly
what I needed to respond to.  But since there is more discussion
I'll give it a try anyway.

On 9/7/2014 3:01 PM, Abdussalam Baryun wrote:
> Hi Chris,
>
> I think you may misunderstand MANET  reactive routing. I don't see 
> your reply answers the editor question of examples of AODVv2 needs 
> from IP or ICMP. You mention that the protocol needs to see ICMP, what 
> is the problem with that as RFC3561 already has similar issue and 
> already accepted by WG.
>
> AB
>
> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>
>     Just for a start you also need to know that IP routes are
>     requested, that packets are flowing, and to have the ability to
>     queue packets.
>

Here I am not sure who "you" is, but perhaps I will reformulate
to hazard a guess at an answer...

On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote something 
that Charlie interprets as follows:
> AODVv2 needs the following:
>     - information that IP routes are requested
>     - information that packets are flowing
>     - the ability to queue packets.


Tautologically, a reactive protocol reacts when a route is needed.
One might say that a route is requested when an application tries to
send a packet.  The fundamental concept of reactive routing is to
avoid creating routes that are not needed, and the way that has been
used to know whether a route is needed is when an application tries
to send a packet.

If an application tries to send a packet, and the route is available, the
packet has to wait until the route is available.  So, yes, queuing a
packet is needed.

This has been known for 20 years.



>     I'm pretty sure not all of those are mandated by IP. The routing
>     protocol also needs to see ICMP messages - is that normal?
>

As a matter of fact, looking at the state of routing in the Internet,
reactive routing is not normal.  So, no, these ideas are not normal,
depending on your definition.  However, if you restrict your determination
of "normality" to the space of reactive protocols, then yes, these
ideas and techniques are quite normal.

This has also been the case for a very long time.

>
>     As I said, it's a matter of what the whole architecture looks like.
>
>

I'm not sure what to make of this...


-- 
Regards,
Charlie P.


--------------030209070107030305050702
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    Hello folks,<br>
    <br>
    I did not follow-up on this in July because I didn't see exactly<br>
    what I needed to respond to.Â  But since there is more discussion<br>
    I'll give it a try anyway.<br>
    <br>
    <div class="moz-cite-prefix">On 9/7/2014 3:01 PM, Abdussalam Baryun
      wrote:<br>
    </div>
    <blockquote
cite="mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com"
      type="cite">Hi Chris,
      <div><br>
      </div>
      <div>I think you may misunderstand MANETÂ Â reactive routing. I
        don't see your reply answers the editor question of examples of
        AODVv2 needs from IP or ICMP. You mention that the protocol
        needs to see ICMP, what is the problem with that asÂ RFC3561
        already has similar issue and already accepted by WG.Â </div>
      <div><br>
      </div>
      <div>AB<br>
        <br>
        On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Just for a
          start you also need to know that IP routes are requested, that
          packets are flowing, and to have the ability to queue packets.</blockquote>
      </div>
    </blockquote>
    <br>
    Here I am not sure who "you" is, but perhaps I will reformulate<br>
    to hazard a guess at an answer...<br>
    <br>
    On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote
    something that Charlie interprets as follows:<br>
    <blockquote type="cite">AODVv2 needs the following:<br>
      Â Â Â  - information that IP routes are requested<br>
      Â Â Â  - information that packets are flowing<br>
      Â Â Â  - the ability to queue packets.</blockquote>
    <br>
    <br>
    Tautologically, a reactive protocol reacts when a route is needed.<br>
    One might say that a route is requested when an application tries to<br>
    send a packet.Â  The fundamental concept of reactive routing is to<br>
    avoid creating routes that are not needed, and the way that has been<br>
    used to know whether a route is needed is when an application tries<br>
    to send a packet.<br>
    <br>
    If an application tries to send a packet, and the route is
    available, the<br>
    packet has to wait until the route is available.Â  So, yes, queuing a<br>
    packet is needed.<br>
    <br>
    This has been known for 20 years.<br>
    <br>
    <br>
    <br>
    <blockquote
cite="mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com"
      type="cite">
      <div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex"> I'm pretty
          sure not all of those are mandated by IP. The routing protocol
          also needs to see ICMP messages - is that normal?<br>
        </blockquote>
      </div>
    </blockquote>
    <br>
    As a matter of fact, looking at the state of routing in the
    Internet,<br>
    reactive routing is not normal.Â  So, no, these ideas are not normal,<br>
    depending on your definition.Â  However, if you restrict your
    determination<br>
    of "normality" to the space of reactive protocols, then yes, these<br>
    ideas and techniques are quite normal.<br>
    <br>
    This has also been the case for a very long time.<br>
    <br>
    <blockquote
cite="mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com"
      type="cite">
      <div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <br>
          As I said, it's a matter of what the whole architecture looks
          like.</blockquote>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    I'm not sure what to make of this...<br>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Regards,
Charlie P.</pre>
  </body>
</html>

--------------030209070107030305050702--


From nobody Mon Sep  8 10:34:57 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38EFA1A001A for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WytUjlJ0Pl4s for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:34:54 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id E53A91A003A for <manet@ietf.org>; Mon,  8 Sep 2014 10:34:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=lrDFbUAfhcU2BjTFSvIic7oVZWW2voJe9RyKd9bhHiFgaBWRXsjb4zLYFsy2N7cj; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XR2q0-0005oT-BT; Mon, 08 Sep 2014 13:34:48 -0400
Message-ID: <540DE8B6.504@earthlink.net>
Date: Mon, 08 Sep 2014 10:34:46 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christopher Dearlove <christopher.dearlove@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk>
In-Reply-To: <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac79ffdfd9f77b04e0c1c6fcbd589cf2a95350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/hELqBb4cFSBJOI2aW5UO9xmu_vA
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 17:34:56 -0000

Hello Chris,

To my understanding, AODVv2 does indeed specify messages, not packets.
A long time ago, we had the luxury of sending packets, but for quite a while
now the AODVv2 specification has been rewritten to specify the messages
instead.  We will be happy to fix language in the specification 
remaining that
might be confusing.

A new revision should be out before long.  But if you want to check
the current version for this point, any constructive suggestions will be
appreciated.

Regards,
Charlie P.


On 9/8/2014 8:26 AM, Christopher Dearlove wrote:
> Really, I'm not wading through all that, as it becomes apparent early on that it misses the whole point.
> - 5444 defines a packet/message format,
> - 5444 defines how that can be used by a multiplexer. Yes, at this point that's optional.
> - 5498 makes use of that multiplexing approach mandatory on the manet protocol/port.
> - The WG (in agreement with ADs etc.) has decided that MANET routing protocols it designs are to use the manet protocol/port.
>
> Put all that together, and you have the state of play. Doesn't matter if you don't think that's so or not. It is.
>
> Of course anyone can use 5444 for some other purpose. Various options here. But none what's being discussed.
>
> As for AODVv2 being noncompliant with 5444/5498, yes it is. It simple terms, packets belong to the multiplexer, messages belong to a protocol. So AODVv2 can define messages. It doesn't define packets. It can (and this is specified) get read access to the packet header, and (also specified) provide TLVs for the packet header as well as providing messages for packets. But that's not what's done either.
>
> On 8 Sep 2014, at 14:47, Abdussalam Baryun wrote:
>
>>> On Mon, Jul 21, 2014 at 5:40 AM, manet issue tracker
>>> <trac+manet@trac.tools.ietf.org<mailto:trac+manet@trac.tools.ietf.org>>
>>> wrote:
>>> #45: RFC 5498 non-compliance (submitted for Chris Dearlove)
>>>
>>> The document is completely noncompliant with the RFC 5444 multiplexing
>>> mechanism, mandated by RFC 5498 (on the manet port/protocol). It does
>>> many things that are not within its competence.
>>>
>> On 7/21/14, Charles E. Perkins <charliep@computer.org> wrote:
>>> Hello Chris,
>>>
>>> The document states:
>>>
>>>>   In its default mode of operation, AODVv2 sends messages using the
>>>>   parameters for port number and IP protocol specified in [RFC5498] to
>>>>   carry protocol packets.  By default, AODVv2 messages are sent with
>>>>   the IP destination address set to the link-local multicast address
>>>>   LL-MANET-Routers [RFC5498] unless otherwise specified. Therefore,
>>>>   all AODVv2 routers MUST subscribe to LL-MANET-Routers [RFC5498] to
>>>>   receiving AODVv2 messages.
>>> So, I suspect the problem lies elsewhere.  Could you point to the
>>> noncompliant part of the AODVv2 specification, and the protocol
>>> mandate for which the AODVv2 specification is noncompliant?
>>>
>> On 7/22/14, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> wrote:
>>> The quoted text is irrelevant to this point.
>>>
>>> As has been said many times, packets belong to the multiplexer, messages to
>>> the protocol. There are many pieces of text specifying things about packets
>>> that are out of the competence of the protocol. I'm afraid I stopped marking
>>> them on my copy.
>>>
>>> (For exactly how the protocol can interact with packets, see 5444.)
>>>
>>
>> I don't think packets should only blong to multiplexer/parsers.
>> 5444-Packets COULD be generated by protocols not only multiplexer.
>> IMHO, There is no specification that states that 5444-packets are
>> generated only by parsers/multiplexer (If I am wrong please point to
>> it). The RFC5444-packet is for the protocol-designer to define not the
>> parser-designer. The parser-designer needs to follow the
>> protocol-designer. You cannot force a router vendor to not define its
>> own 5444-packets for its routing protocol. I remember that within the
>> Packet-bb submission (now is RFC5444) there was a discussion between
>> Teco and Thomas that there are many issues related to parsing and
>> multiplexing that this RFC5444/Packet-bb-draft does not specify and
>> did not solve. This issue needs more discussion in the WG, because I
>> don't find consensus on the issue.
>>
>> On 7/22/14, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> wrote:
>>> RFC5444 describes a multiplexing process. It is not required purely in its
>>> own terms.
>> Yes it is not required because RFC5444 is just format standard,
>> RFC5444 is not parsing standard, RFC5444 is not a packet-multiplex
>> standard. The multiplex in just explained in appendix which is not
>> normative, and IMHO the WG did not agree on specific multiplexing
>> standard. One participant yesterday mentioned the multiplex as in that
>> Appendix is a MUST, which I disagree.
>>
>>> But RFC 5498 make it mandatory for any protocol using the
>>> port/protocol allocated by that RFC. And the WG has agreed that all routing
>>> protocols developed have to be able (at least) to use that port/protocol.
>> RFC5498 is for one one RFC5444 packet, please note that RFC5444 is a
>> general packet format, protocols can define their own
>> packets/messages. I understand that you suggest unifying the packet
>> for all MANET protocols but that is not specified in RFC5444. RFC5444
>> already states clearly that packets/messages are formated but parsing
>> is general-logic and independent from protocol. In IETF 5444 parsing
>> is not specified yet, just logic. see below:
>>
>>
>> {{{
>>
>> The specification has been explicitly designed with the following
>> properties, listed in no particular order, in mind:
>>
>> Parsing logic - The notation used in this specification facilitates
>> generic, protocol-independent parsing logic.
>>
>> Extensibility - Packets and messages defined by a protocol using
>> this specification are extensible by defining new messages and new
>> TLVs. Protocols using this specification will be able to
>> correctly identify and skip such new messages and TLVs, while
>> correctly parsing the remainder of the packet and message.
>>
>> }}}
>>
>> It does not state unify parsing as general but just general parsing to
>> be independent, so we design AODVv2 independently from parsing and
>> even independent of multiplexing packets.
>>
>> I suggest we work on this draft AODVv2 independently from
>> parsing/multiplexing as the RFC5444 suggested which AODVv2 uses
>> correctly so far by my understandning and no much answers received for
>> editor questions related to the draft.
>>
>> Best Regards,
>> AB
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>


From nobody Mon Sep  8 10:45:31 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A641A0099 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id apMuzgogbApP for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:45:27 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02E861A00C2 for <manet@ietf.org>; Mon,  8 Sep 2014 10:45:26 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id t60so1503985wes.33 for <manet@ietf.org>; Mon, 08 Sep 2014 10:45:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=bRT+UF2ZXMUbnai7Q5/IQTwNVEMdFwxkRRYTasm/mAc=; b=xRXJHO6Tv9kjpQN6EwQP3pqTFQqPtO5cfkD4VrrFMxv1mMZirRw112Fktuzj8nNv08 yZkdg36pubzbTXCwq8PzNNjS7VbkcrF3TY8BLWPxP9JRZi5jtvPG4yIlvjrDCmaow0Jp oknkkaaH/Y39zcnWimHC8Z1W2eDFVg5c5sOS9cZNle5KjObIA7X8g+fKpRbqob3AguQn Wzh8z2MnjAANbLBAYXYbRV4uYVLsJVo/un4IZJGrI8ts4BbMLza/oqkV7PB5IltIQk5x zmDefbVGXgtJIGnne00tScpdjwcI7Ls/O1ZVFCzuq3kGegHk1Lx+sN20lmPkCH0objR8 U2mA==
X-Received: by 10.194.71.11 with SMTP id q11mr35443577wju.33.1410198325230; Mon, 08 Sep 2014 10:45:25 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id o3sm12505149wiy.18.2014.09.08.10.45.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 10:45:24 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2D9BBBE9-9B38-45DD-8B53-DB233B0351E6"
From: Christopher Dearlove <christopher.dearlove@gmail.com>
In-Reply-To: <540DE570.2040006@computer.org>
Date: Mon, 8 Sep 2014 18:45:20 +0100
Message-Id: <781FDD4B-A719-4FBA-AA38-A04377B886B4@gmail.com>
References: <061.89377601617f43ae76e225162010f923@trac.tools.ietf.org><53CC9987.6060104@computer.org><B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECF7@GLKXM0002V.GREENLNK.net> <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com> <540DE570.2040006@computer.org>
To: Charles E. Perkins <charliep@computer.org>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/IVDJLPHMCsGyy5n5nAfbqCZ9lO4
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 17:45:29 -0000

--Apple-Mail=_2D9BBBE9-9B38-45DD-8B53-DB233B0351E6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I'm really not able t check the full context here, as I'm on holiday =
this week.

I think that "you" was colloquially the routing protocol.

But the point is, as you agree, this is not normal in the Internet. =
Doesn't matter if this has been known in the ad hoc routing field for 20 =
years. This is intended to be a proposed standard in what is the wider =
Internet community. Which experience has shown is not familiar with =
these matters, or various other things, some of them simpler.

This needs specifying for that reason. And also because people who want =
to implement it know what capabilities they need. If they need queueing =
in the IP stack they need to be told they need queuing in the IP stack. =
And that makes it clear this needs to be more than a routing protocol if =
that capability is not available as standard, which I think you just =
agreed it's not. Knowledge in the ad hoc routing community isn't enough.


On 8 Sep 2014, at 18:20, Charles E. Perkins wrote:

>=20
> Hello folks,
>=20
> I did not follow-up on this in July because I didn't see exactly
> what I needed to respond to.  But since there is more discussion
> I'll give it a try anyway.
>=20
> On 9/7/2014 3:01 PM, Abdussalam Baryun wrote:
>> Hi Chris,
>>=20
>> I think you may misunderstand MANET  reactive routing. I don't see =
your reply answers the editor question of examples of AODVv2 needs from =
IP or ICMP. You mention that the protocol needs to see ICMP, what is the =
problem with that as RFC3561 already has similar issue and already =
accepted by WG.=20
>>=20
>> AB
>>=20
>> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>> Just for a start you also need to know that IP routes are requested, =
that packets are flowing, and to have the ability to queue packets.
>=20
> Here I am not sure who "you" is, but perhaps I will reformulate
> to hazard a guess at an answer...
>=20
> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote something =
that Charlie interprets as follows:
>> AODVv2 needs the following:
>>     - information that IP routes are requested
>>     - information that packets are flowing
>>     - the ability to queue packets.
>=20
>=20
> Tautologically, a reactive protocol reacts when a route is needed.
> One might say that a route is requested when an application tries to
> send a packet.  The fundamental concept of reactive routing is to
> avoid creating routes that are not needed, and the way that has been
> used to know whether a route is needed is when an application tries
> to send a packet.
>=20
> If an application tries to send a packet, and the route is available, =
the
> packet has to wait until the route is available.  So, yes, queuing a
> packet is needed.
>=20
> This has been known for 20 years.
>=20
>=20
>=20
>> I'm pretty sure not all of those are mandated by IP. The routing =
protocol also needs to see ICMP messages - is that normal?
>=20
> As a matter of fact, looking at the state of routing in the Internet,
> reactive routing is not normal.  So, no, these ideas are not normal,
> depending on your definition.  However, if you restrict your =
determination
> of "normality" to the space of reactive protocols, then yes, these
> ideas and techniques are quite normal.
>=20
> This has also been the case for a very long time.
>=20
>>=20
>> As I said, it's a matter of what the whole architecture looks like.
>>=20
>=20
> I'm not sure what to make of this...
>=20
>=20
> --=20
> Regards,
> Charlie P.
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


--Apple-Mail=_2D9BBBE9-9B38-45DD-8B53-DB233B0351E6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>I'm really not able t check the full context here, as I'm on =
holiday this week.</div><div><br></div><div>I think that "you" was =
colloquially the routing protocol.</div><div><br></div><div>But the =
point is, as you agree, this is not normal in the Internet. Doesn't =
matter if this has been known in the ad hoc routing field for 20 years. =
This is intended to be a proposed standard in what is the wider Internet =
community. Which experience has shown is not familiar with these =
matters, or various other things, some of them =
simpler.</div><div><br></div><div>This needs specifying for that reason. =
And also because people who want to implement it know what capabilities =
they need. If they need queueing in the IP stack they need to be told =
they need queuing in the IP stack. And that makes it clear this needs to =
be more than a routing protocol if that capability is not available as =
standard, which I think you just agreed it's not. Knowledge in the ad =
hoc routing community isn't enough.</div><div><br></div><br><div><div>On =
8 Sep 2014, at 18:20, Charles E. Perkins wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    Hello folks,<br>
    <br>
    I did not follow-up on this in July because I didn't see exactly<br>
    what I needed to respond to.&nbsp; But since there is more =
discussion<br>
    I'll give it a try anyway.<br>
    <br>
    <div class=3D"moz-cite-prefix">On 9/7/2014 3:01 PM, Abdussalam =
Baryun
      wrote:<br>
    </div>
    <blockquote =
cite=3D"mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=3DV4z9jMp3NXixQ@mail.gma=
il.com" type=3D"cite">Hi Chris,
      <div><br>
      </div>
      <div>I think you may misunderstand MANET&nbsp;&nbsp;reactive =
routing. I
        don't see your reply answers the editor question of examples of
        AODVv2 needs from IP or ICMP. You mention that the protocol
        needs to see ICMP, what is the problem with that as&nbsp;RFC3561
        already has similar issue and already accepted by =
WG.&nbsp;</div>
      <div><br>
      </div>
      <div>AB<br>
        <br>
        On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:<br>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Just for a
          start you also need to know that IP routes are requested, that
          packets are flowing, and to have the ability to queue =
packets.</blockquote>
      </div>
    </blockquote>
    <br>
    Here I am not sure who "you" is, but perhaps I will reformulate<br>
    to hazard a guess at an answer...<br>
    <br>
    On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote
    something that Charlie interprets as follows:<br>
    <blockquote type=3D"cite">AODVv2 needs the following:<br>
      &nbsp;&nbsp;&nbsp; - information that IP routes are requested<br>
      &nbsp;&nbsp;&nbsp; - information that packets are flowing<br>
      &nbsp;&nbsp;&nbsp; - the ability to queue packets.</blockquote>
    <br>
    <br>
    Tautologically, a reactive protocol reacts when a route is =
needed.<br>
    One might say that a route is requested when an application tries =
to<br>
    send a packet.&nbsp; The fundamental concept of reactive routing is =
to<br>
    avoid creating routes that are not needed, and the way that has =
been<br>
    used to know whether a route is needed is when an application =
tries<br>
    to send a packet.<br>
    <br>
    If an application tries to send a packet, and the route is
    available, the<br>
    packet has to wait until the route is available.&nbsp; So, yes, =
queuing a<br>
    packet is needed.<br>
    <br>
    This has been known for 20 years.<br>
    <br>
    <br>
    <br>
    <blockquote =
cite=3D"mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=3DV4z9jMp3NXixQ@mail.gma=
il.com" type=3D"cite">
      <div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex"> I'm pretty
          sure not all of those are mandated by IP. The routing protocol
          also needs to see ICMP messages - is that normal?<br>
        </blockquote>
      </div>
    </blockquote>
    <br>
    As a matter of fact, looking at the state of routing in the
    Internet,<br>
    reactive routing is not normal.&nbsp; So, no, these ideas are not =
normal,<br>
    depending on your definition.&nbsp; However, if you restrict your
    determination<br>
    of "normality" to the space of reactive protocols, then yes, =
these<br>
    ideas and techniques are quite normal.<br>
    <br>
    This has also been the case for a very long time.<br>
    <br>
    <blockquote =
cite=3D"mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=3DV4z9jMp3NXixQ@mail.gma=
il.com" type=3D"cite">
      <div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <br>
          As I said, it's a matter of what the whole architecture looks
          like.</blockquote>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    I'm not sure what to make of this...<br>
    <br>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Regards,
Charlie P.</pre>
  </div>

_______________________________________________<br>manet mailing =
list<br><a =
href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/manet<br></blockquote></div><br></body></html>=

--Apple-Mail=_2D9BBBE9-9B38-45DD-8B53-DB233B0351E6--


From nobody Mon Sep  8 10:47:57 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55BF31A00C2 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTlf0MlDYgcB for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:47:54 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 013F91A00B0 for <manet@ietf.org>; Mon,  8 Sep 2014 10:47:53 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id k14so1101642wgh.22 for <manet@ietf.org>; Mon, 08 Sep 2014 10:47:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CqB4slA/oC2j0slF0gjgdlqqYLOV0GMJIw7N6LmTfrw=; b=FkAdYV0cTnpsgSfNu6wjGT3En5AsvmKTL/4KCk2avZ/mx4/c/3fFN6WaHSUdm9nVUz GlYrP4ORJQvBWReUD27Cua3SsYf6MDxkeRzvL63drRZwPEQ2waOtYTVxqV548Zh77xTt LTM5YVYvUnAe2mdbJKaebV6VNldXvLSzR4t7aU4z3FvdUMgQGIgAWvVVSCn24UpGyOnh 2IkqxamYb4HsMsmL8GkOnbOqKa3mgNbzLHuBSJ3XbZjitugGuH9kPh0J3G0KOZV1lWF+ sOMXBF+7NHvL/RlSLfFNyy1vJ4zLvCOqiGD1P8y1MqUhD6MkYJ9Q1hdbpDWJpX3ckeEb PvJg==
X-Received: by 10.180.75.17 with SMTP id y17mr24153420wiv.3.1410198472592; Mon, 08 Sep 2014 10:47:52 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id v4sm11911879wjv.6.2014.09.08.10.47.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 10:47:51 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Christopher Dearlove <christopher.dearlove@gmail.com>
In-Reply-To: <540DE8B6.504@earthlink.net>
Date: Mon, 8 Sep 2014 18:47:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net>
To: Charlie Perkins <charles.perkins@earthlink.net>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/4yJYsaGukK-roOX0VQEZZ33CfYs
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 17:47:55 -0000

On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
> To my understanding, AODVv2 does indeed specify messages, not packets.

Not the version that was current when I wrote my comments. I haven't =
checked if that was the most recent now or not. But it doesn't sound as =
if you are suggesting there have been recent changes in that area.


From nobody Mon Sep  8 10:57:40 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB8D1A014E for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hwGlu-Kq-KZJ for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 10:57:38 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 1AAC41A0158 for <manet@ietf.org>; Mon,  8 Sep 2014 10:57:29 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=tr4xsUKJG8qqiCw1xpZKecUE37bj+2+ZAjTSZOB0wcKguGqqloDfSAzy4pHuZKTl; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XR3Bw-0007tP-NI; Mon, 08 Sep 2014 13:57:28 -0400
Message-ID: <540DEE07.1000405@earthlink.net>
Date: Mon, 08 Sep 2014 10:57:27 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christopher Dearlove <christopher.dearlove@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com>
In-Reply-To: <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7f804a0fea839f3d2d5d18f2dfaa569ad350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/XCN7j0YhW2sS6OMi9X8h6hRJgLY
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 17:57:39 -0000

Hello Chris,

Yes, there have been several recent changes, included in the last
version, and most likely some more to be included in the upcoming
version.  The intention is to completely avoid any confusion.

Regards,
Charlie P.


On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>> To my understanding, AODVv2 does indeed specify messages, not packets.
> Not the version that was current when I wrote my comments. I haven't checked if that was the most recent now or not. But it doesn't sound as if you are suggesting there have been recent changes in that area.
>
>


From nobody Mon Sep  8 11:12:33 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEFE1A0217 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 11:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hmEA9ovNrAlh for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 11:12:23 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D42C71A0248 for <manet@ietf.org>; Mon,  8 Sep 2014 11:12:22 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id m15so1925979wgh.32 for <manet@ietf.org>; Mon, 08 Sep 2014 11:12:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PMJzxJfqm0mIHl0TuhJ3Ajx0JAueC8wZ4ouGC4XhE2E=; b=B9AgzKeSvcmJ6SDb5xZE6xDW/1MOcNP9KH1ddGjyUokV5khWByU1/DdTlyiyDhLskM 42EFwpuXeFUw1iG1TWxdcIRNnlrRxJod925RFLDP2TT2M7adm1tvq4NTO0pww2MSdMRU rjpZP0sKLXgymCby5rQN1sLQT6hRxXm3eL/TU4mW0JG+ycNeLgJO4wpqB6pl1VlWmWe9 HPIzp6BWffIUZYir2iQ6Zf+rN+WQTwmf6WasAKJarZvpI5A5Zb30zIGZaB+kliKVSpa0 LluiVQGxx4/tE6Dm1hMFoo1ZFpWBxZQgW3OJMa0lWgMb9yx1v6+rhaslIPnoOvSgb/GX RUFg==
X-Received: by 10.194.243.230 with SMTP id xb6mr6577006wjc.100.1410199941403;  Mon, 08 Sep 2014 11:12:21 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id pk9sm11970445wjb.16.2014.09.08.11.12.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 11:12:20 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Christopher Dearlove <christopher.dearlove@gmail.com>
In-Reply-To: <540DEE07.1000405@earthlink.net>
Date: Mon, 8 Sep 2014 19:12:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net>
To: Charlie Perkins <charles.perkins@earthlink.net>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/RXIombUvRKLrfee9S8w-f0-LsUE
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 18:12:31 -0000

Well, you'll forgive me for commenting on the version that was newest =
when I made my original comments, not a then-future version.

A quick skim shows the second paragraph of section 5.4 is outside AODV's =
competence, but at the point I stopped skimming that was the main point =
I noted.


On 8 Sep 2014, at 18:57, Charlie Perkins wrote:

>=20
> Hello Chris,
>=20
> Yes, there have been several recent changes, included in the last
> version, and most likely some more to be included in the upcoming
> version.  The intention is to completely avoid any confusion.
>=20
> Regards,
> Charlie P.
>=20
>=20
> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>> To my understanding, AODVv2 does indeed specify messages, not =
packets.
>> Not the version that was current when I wrote my comments. I haven't =
checked if that was the most recent now or not. But it doesn't sound as =
if you are suggesting there have been recent changes in that area.
>>=20
>>=20
>=20


From nobody Mon Sep  8 11:19:59 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 368341A0262 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 11:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7zfvV9A5SkSq for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 11:19:45 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id AEDAF1A0271 for <manet@ietf.org>; Mon,  8 Sep 2014 11:19:44 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ZaOcOYMlN5tFNue8HHVBVfGK65WmgPRwHbAxYOMJrNPRwEOKW67E9NDUocQ++PDQ; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XR3X7-0004zE-9P; Mon, 08 Sep 2014 14:19:21 -0400
Message-ID: <540DF327.70901@earthlink.net>
Date: Mon, 08 Sep 2014 11:19:19 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christopher Dearlove <christopher.dearlove@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com>
In-Reply-To: <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7c21fc28d9bc44f94f0e817d9d76217a1350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/kvkDPZTXs652G2WRbClIigu0I7E
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 18:19:52 -0000

Hello Chris,

No offense taken, so no forgiveness needed.

I don't think that RFC 5444 procludes AODVv2
from specifying adherence to RFC 5082, if that was
the intention of your remark...

Regards,
Charlie P.


On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
> Well, you'll forgive me for commenting on the version that was newest when I made my original comments, not a then-future version.
>
> A quick skim shows the second paragraph of section 5.4 is outside AODV's competence, but at the point I stopped skimming that was the main point I noted.
>
>
> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>
>> Hello Chris,
>>
>> Yes, there have been several recent changes, included in the last
>> version, and most likely some more to be included in the upcoming
>> version.  The intention is to completely avoid any confusion.
>>
>> Regards,
>> Charlie P.
>>
>>
>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>> To my understanding, AODVv2 does indeed specify messages, not packets.
>>> Not the version that was current when I wrote my comments. I haven't checked if that was the most recent now or not. But it doesn't sound as if you are suggesting there have been recent changes in that area.
>>>
>>>
>


From nobody Mon Sep  8 11:57:59 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B5731A0324 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 11:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Y65hbIdeWcj for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 11:57:57 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D0471A0328 for <manet@ietf.org>; Mon,  8 Sep 2014 11:57:57 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id e4so3235362wiv.8 for <manet@ietf.org>; Mon, 08 Sep 2014 11:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JkuGxR9l6ZYOA8N6OPvOdlsB/dkmkf8UWGXcz90L0Ao=; b=yA6+wD3VNj+M4BrV9/iyL5LVLCMFGq+9oM+jjg9RtAsEh5FGiLV879nRuz5+OlJqhW 9dc0B4KPqovIusolvg2j5ym4mpw1x+BRD46FDDJhCIfWNjZ/+2xeIAtIkcEQBXAaMv+E hxVN6QlgIymk1Ctua1h1y7K6Jrq2Hmgl3+SFAm8Uw7K6dOjle2+X1a1Qfa2kB/bfjNmD k3/+fMcUZmdB0ka0HaocDm5pQEYXUd6tUO0i1rm3u6miL5RhPrlW5kx03DabstHOkJHN VtRSaUu744OhWkOBjFDFG+QWr9vH0MbViepDPdBeo72ecttDQ7KRZMaGEhqvwbalFz6l Cqjg==
X-Received: by 10.181.12.7 with SMTP id em7mr25458702wid.57.1410202676075; Mon, 08 Sep 2014 11:57:56 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id i6sm10285952wib.7.2014.09.08.11.57.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 11:57:54 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Christopher Dearlove <christopher.dearlove@gmail.com>
In-Reply-To: <540DF327.70901@earthlink.net>
Date: Mon, 8 Sep 2014 19:57:51 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net>
To: Charlie Perkins <charles.perkins@earthlink.net>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/4AHgSA-fMApdqhO2Uo_VRUhFlM4
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 18:57:59 -0000

Actually, it was. AODVv2 can't adhere to RFC 5082. It has to be the 5444 =
multiplexer that does or doesn't adhere to it. It's probably not =
specified whether it does or not (it certainly isn't specified that it =
does., It might say TTL =3D 1, I don't recall right now,

There are then choices:
- Write something new to mandate all implementations of the 5444 =
multiplexer to adhere to 5082. I would be strongly against that.
- Put a recommendation (i.e. a should) into AODVv2 that the 5444 =
multiplexer it uses should adhere to 5082. Not my first choice.
- Put a requirement (i.e a must) into AODVv22 that the 5444 multiplexer =
it uses must adhere to 5082. I would be strongly against that too.
- Leave it up to whoever implements the 5444 multiplexer, which already =
is required to fulfil the key requirement here (that packets only travel =
one logical hop - but physical hops?)

Te question is, why is AODVv2 any more needing of this than anything =
else? If it's not, then the issue definitely becomes one of point 4.

Now providing advice about the 5444 multiplexer, including any reference =
to 5082, is really the job of another document on broader 5444 advice. =
One that is bubbling up the 5444 authors' (at least) priority list. I =
don't have a position currently on what emphasis should be put on 5082 =
in such a document, and I don't know anyone else's views on that matter =
either.


On 8 Sep 2014, at 19:19, Charlie Perkins wrote:

> Hello Chris,
>=20
> No offense taken, so no forgiveness needed.
>=20
> I don't think that RFC 5444 procludes AODVv2
> from specifying adherence to RFC 5082, if that was
> the intention of your remark...
>=20
> Regards,
> Charlie P.
>=20
>=20
> On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
>> Well, you'll forgive me for commenting on the version that was newest =
when I made my original comments, not a then-future version.
>>=20
>> A quick skim shows the second paragraph of section 5.4 is outside =
AODV's competence, but at the point I stopped skimming that was the main =
point I noted.
>>=20
>>=20
>> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>>=20
>>> Hello Chris,
>>>=20
>>> Yes, there have been several recent changes, included in the last
>>> version, and most likely some more to be included in the upcoming
>>> version.  The intention is to completely avoid any confusion.
>>>=20
>>> Regards,
>>> Charlie P.
>>>=20
>>>=20
>>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>>> To my understanding, AODVv2 does indeed specify messages, not =
packets.
>>>> Not the version that was current when I wrote my comments. I =
haven't checked if that was the most recent now or not. But it doesn't =
sound as if you are suggesting there have been recent changes in that =
area.
>>>>=20
>>>>=20
>>=20
>=20


From nobody Mon Sep  8 13:21:58 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 945BF1A030E for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 13:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o47J7eZwMIYB for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 13:21:49 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id 94A371A0300 for <manet@ietf.org>; Mon,  8 Sep 2014 13:21:49 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=W6DZes6bA8DeX9knw/iWkKlke8Etot/yAc2HZlSUFJtscMTTtroB4jceZPvIb+mX; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XR5RZ-00061S-Ns; Mon, 08 Sep 2014 16:21:45 -0400
Message-ID: <540E0FD8.2060402@earthlink.net>
Date: Mon, 08 Sep 2014 13:21:44 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christopher Dearlove <christopher.dearlove@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com>
In-Reply-To: <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7d1b5903872a52c9558ed9dd5c3becba8350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ky-BqH1a_TsuBRxxRAhYEJ_TIC8
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 20:21:54 -0000

Hello Chris,

In general, if a routing protocol cannot specify TTL=255,
then something is definitely broken.  Message bundling
is not a good enough excuse for disabling this function.

AODVv2 specifically does need the functionality, and so
the general statement does have a relevant specific
example.

Regards,
Charlie P.


On 9/8/2014 11:57 AM, Christopher Dearlove wrote:
> Actually, it was. AODVv2 can't adhere to RFC 5082. It has to be the 5444 multiplexer that does or doesn't adhere to it. It's probably not specified whether it does or not (it certainly isn't specified that it does., It might say TTL = 1, I don't recall right now,
>
> There are then choices:
> - Write something new to mandate all implementations of the 5444 multiplexer to adhere to 5082. I would be strongly against that.
> - Put a recommendation (i.e. a should) into AODVv2 that the 5444 multiplexer it uses should adhere to 5082. Not my first choice.
> - Put a requirement (i.e a must) into AODVv22 that the 5444 multiplexer it uses must adhere to 5082. I would be strongly against that too.
> - Leave it up to whoever implements the 5444 multiplexer, which already is required to fulfil the key requirement here (that packets only travel one logical hop - but physical hops?)
>
> Te question is, why is AODVv2 any more needing of this than anything else? If it's not, then the issue definitely becomes one of point 4.
>
> Now providing advice about the 5444 multiplexer, including any reference to 5082, is really the job of another document on broader 5444 advice. One that is bubbling up the 5444 authors' (at least) priority list. I don't have a position currently on what emphasis should be put on 5082 in such a document, and I don't know anyone else's views on that matter either.
>
>
> On 8 Sep 2014, at 19:19, Charlie Perkins wrote:
>
>> Hello Chris,
>>
>> No offense taken, so no forgiveness needed.
>>
>> I don't think that RFC 5444 procludes AODVv2
>> from specifying adherence to RFC 5082, if that was
>> the intention of your remark...
>>
>> Regards,
>> Charlie P.
>>
>>
>> On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
>>> Well, you'll forgive me for commenting on the version that was newest when I made my original comments, not a then-future version.
>>>
>>> A quick skim shows the second paragraph of section 5.4 is outside AODV's competence, but at the point I stopped skimming that was the main point I noted.
>>>
>>>
>>> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>>>
>>>> Hello Chris,
>>>>
>>>> Yes, there have been several recent changes, included in the last
>>>> version, and most likely some more to be included in the upcoming
>>>> version.  The intention is to completely avoid any confusion.
>>>>
>>>> Regards,
>>>> Charlie P.
>>>>
>>>>
>>>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>>>> To my understanding, AODVv2 does indeed specify messages, not packets.
>>>>> Not the version that was current when I wrote my comments. I haven't checked if that was the most recent now or not. But it doesn't sound as if you are suggesting there have been recent changes in that area.
>>>>>
>>>>>
>


From nobody Mon Sep  8 13:58:31 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C32041A038F for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 13:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JHQKu1WYKvXg for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 13:58:27 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95A301A038A for <manet@ietf.org>; Mon,  8 Sep 2014 13:58:26 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id u56so2042850wes.24 for <manet@ietf.org>; Mon, 08 Sep 2014 13:58:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=LG5giZEwprRQWWfLauFOv3AxQadiL3mRV76QieiSupQ=; b=xWkixZ25cFROYpB9sg3RjtMuaTvCFpsShvs9LBsa5kGa1m3CmY9txQ6RdnWDtf/464 G2d8xc4CU/5jvpK05cmpVzP6jUN+TL5NXyDNg5yT94ZorroSirpgLcjG7rGauqZMK/o/ 6uYAkv2xkSnhGt9nYY3nYSq351GKCyV5A+xrbfXVY40G5UYyGWSjq/jbAevjZlUjokYR leroWTfnEIf8selXcq5T2JXYRpNFVtJnyy5yje5OtLQyWqM5dqkM1ME5kX6Od8zGPC1S f+bfl1jvC5wRzTZu60cEZeDdSugB/cD+2zLkxXgrSTfxTYNIz+erbP0HmV0aUQyUf9iY xxtg==
X-Received: by 10.194.78.170 with SMTP id c10mr37925888wjx.22.1410209905303; Mon, 08 Sep 2014 13:58:25 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id k10sm12397989wjb.28.2014.09.08.13.58.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 13:58:23 -0700 (PDT)
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <540E0FD8.2060402@earthlink.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Mon, 8 Sep 2014 21:58:21 +0100
To: Charlie Perkins <charles.perkins@earthlink.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/2IGc6wcDN0WhQAIZaTqqz7fvBdM
Cc: "<draft-ietf-manet-aodvv2@tools.ietf.org>" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, "<manet@ietf.org>" <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 20:58:31 -0000

Why does AODVv2 need this functionality any more than, say, NHDP, OLSRv2 or S=
MF? 5444 packets are meant to travel only one hop, it's part of the multiple=
xer design. If 5082 helps ensure this, this is something to apply at that le=
vel. This is not and cannot be an AODVv2 function, because AODVv2 isn't in c=
hange of packets.

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 8 Sep 2014, at 21:21, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
> Hello Chris,
>=20
> In general, if a routing protocol cannot specify TTL=3D255,
> then something is definitely broken.  Message bundling
> is not a good enough excuse for disabling this function.
>=20
> AODVv2 specifically does need the functionality, and so
> the general statement does have a relevant specific
> example.
>=20
> Regards,
> Charlie P.
>=20
>=20
>> On 9/8/2014 11:57 AM, Christopher Dearlove wrote:
>> Actually, it was. AODVv2 can't adhere to RFC 5082. It has to be the 5444 m=
ultiplexer that does or doesn't adhere to it. It's probably not specified wh=
ether it does or not (it certainly isn't specified that it does., It might s=
ay TTL =3D 1, I don't recall right now,
>>=20
>> There are then choices:
>> - Write something new to mandate all implementations of the 5444 multiple=
xer to adhere to 5082. I would be strongly against that.
>> - Put a recommendation (i.e. a should) into AODVv2 that the 5444 multiple=
xer it uses should adhere to 5082. Not my first choice.
>> - Put a requirement (i.e a must) into AODVv22 that the 5444 multiplexer i=
t uses must adhere to 5082. I would be strongly against that too.
>> - Leave it up to whoever implements the 5444 multiplexer, which already i=
s required to fulfil the key requirement here (that packets only travel one l=
ogical hop - but physical hops?)
>>=20
>> Te question is, why is AODVv2 any more needing of this than anything else=
? If it's not, then the issue definitely becomes one of point 4.
>>=20
>> Now providing advice about the 5444 multiplexer, including any reference t=
o 5082, is really the job of another document on broader 5444 advice. One th=
at is bubbling up the 5444 authors' (at least) priority list. I don't have a=
 position currently on what emphasis should be put on 5082 in such a documen=
t, and I don't know anyone else's views on that matter either.
>>=20
>>=20
>>> On 8 Sep 2014, at 19:19, Charlie Perkins wrote:
>>>=20
>>> Hello Chris,
>>>=20
>>> No offense taken, so no forgiveness needed.
>>>=20
>>> I don't think that RFC 5444 procludes AODVv2
>>> from specifying adherence to RFC 5082, if that was
>>> the intention of your remark...
>>>=20
>>> Regards,
>>> Charlie P.
>>>=20
>>>=20
>>>> On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
>>>> Well, you'll forgive me for commenting on the version that was newest w=
hen I made my original comments, not a then-future version.
>>>>=20
>>>> A quick skim shows the second paragraph of section 5.4 is outside AODV'=
s competence, but at the point I stopped skimming that was the main point I n=
oted.
>>>>=20
>>>>=20
>>>>> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>>>>>=20
>>>>> Hello Chris,
>>>>>=20
>>>>> Yes, there have been several recent changes, included in the last
>>>>> version, and most likely some more to be included in the upcoming
>>>>> version.  The intention is to completely avoid any confusion.
>>>>>=20
>>>>> Regards,
>>>>> Charlie P.
>>>>>=20
>>>>>=20
>>>>>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>>>>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>>>>> To my understanding, AODVv2 does indeed specify messages, not packet=
s.
>>>>>> Not the version that was current when I wrote my comments. I haven't c=
hecked if that was the most recent now or not. But it doesn't sound as if yo=
u are suggesting there have been recent changes in that area.
>=20


From nobody Mon Sep  8 13:59:32 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839091A037C for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 13:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJ8FuX8Whft9 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 13:59:29 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB2261A0376 for <manet@ietf.org>; Mon,  8 Sep 2014 13:59:28 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id u56so2051190wes.38 for <manet@ietf.org>; Mon, 08 Sep 2014 13:59:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:from:subject:date:to; bh=92y21x8FmLWPrdlaEdOS+lyn+cZY/hJKHmVWo6bjiPU=; b=YvNFYWUa1orx5rtQw1klki8lR9u5yfdPkE8Fc0lfnksTUtoPYuF0bMKEaw4NGb6Tqy D/SIaD+pczdHxPn+2DlyEulxvXrgOLpXSp9ApYlilJ2qa1WQAngLWuMiTUluyUJMQ5v5 +yK8kXZnHGsWjRuy6xDTJ67H06zmWbsUeSZCZ4niRuhj9OkHniT2iqSMXdkoiNDRsVOd aE0v9nGEI6aNdY5NKox98ifxlyZMuj4g3HkhsjWPKAjtbBl/NjKYDGHENKtrI1V40v2Q L7Si7db5HGMlhaFqjRnjMtP5kAg+m3S4aUVKt2SStIvTjWAENGGZ4lxhCNV9zMZxTH3e RwGQ==
X-Received: by 10.180.189.14 with SMTP id ge14mr24297048wic.36.1410209967422;  Mon, 08 Sep 2014 13:59:27 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id et1sm12416278wjd.11.2014.09.08.13.59.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 13:59:26 -0700 (PDT)
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net>
In-Reply-To: <540E0FD8.2060402@earthlink.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <82A4E015-7500-4C4A-892A-827DBBCA6AB0@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Mon, 8 Sep 2014 21:59:23 +0100
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/CI084QixdXNud_J8RybMDvOjexM
Cc: "<draft-ietf-manet-aodvv2@tools.ietf.org>" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, "<manet@ietf.org>" <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 20:59:30 -0000

Why does AODVv2 need this functionality?

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)
> On 8 Sep 2014, at 21:21, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
> Hello Chris,
>=20
> In general, if a routing protocol cannot specify TTL=3D255,
> then something is definitely broken.  Message bundling
> is not a good enough excuse for disabling this function.
>=20
> AODVv2 specifically does need the functionality, and so
> the general statement does have a relevant specific
> example.
>=20
> Regards,
> Charlie P.
>=20
>=20
>> On 9/8/2014 11:57 AM, Christopher Dearlove wrote:
>> Actually, it was. AODVv2 can't adhere to RFC 5082. It has to be the 5444 m=
ultiplexer that does or doesn't adhere to it. It's probably not specified wh=
ether it does or not (it certainly isn't specified that it does., It might s=
ay TTL =3D 1, I don't recall right now,
>>=20
>> There are then choices:
>> - Write something new to mandate all implementations of the 5444 multiple=
xer to adhere to 5082. I would be strongly against that.
>> - Put a recommendation (i.e. a should) into AODVv2 that the 5444 multiple=
xer it uses should adhere to 5082. Not my first choice.
>> - Put a requirement (i.e a must) into AODVv22 that the 5444 multiplexer i=
t uses must adhere to 5082. I would be strongly against that too.
>> - Leave it up to whoever implements the 5444 multiplexer, which already i=
s required to fulfil the key requirement here (that packets only travel one l=
ogical hop - but physical hops?)
>>=20
>> Te question is, why is AODVv2 any more needing of this than anything else=
? If it's not, then the issue definitely becomes one of point 4.
>>=20
>> Now providing advice about the 5444 multiplexer, including any reference t=
o 5082, is really the job of another document on broader 5444 advice. One th=
at is bubbling up the 5444 authors' (at least) priority list. I don't have a=
 position currently on what emphasis should be put on 5082 in such a documen=
t, and I don't know anyone else's views on that matter either.
>>=20
>>=20
>>> On 8 Sep 2014, at 19:19, Charlie Perkins wrote:
>>>=20
>>> Hello Chris,
>>>=20
>>> No offense taken, so no forgiveness needed.
>>>=20
>>> I don't think that RFC 5444 procludes AODVv2
>>> from specifying adherence to RFC 5082, if that was
>>> the intention of your remark...
>>>=20
>>> Regards,
>>> Charlie P.
>>>=20
>>>=20
>>>> On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
>>>> Well, you'll forgive me for commenting on the version that was newest w=
hen I made my original comments, not a then-future version.
>>>>=20
>>>> A quick skim shows the second paragraph of section 5.4 is outside AODV'=
s competence, but at the point I stopped skimming that was the main point I n=
oted.
>>>>=20
>>>>=20
>>>>> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>>>>>=20
>>>>> Hello Chris,
>>>>>=20
>>>>> Yes, there have been several recent changes, included in the last
>>>>> version, and most likely some more to be included in the upcoming
>>>>> version.  The intention is to completely avoid any confusion.
>>>>>=20
>>>>> Regards,
>>>>> Charlie P.
>>>>>=20
>>>>>=20
>>>>>>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>>>>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>>>>> To my understanding, AODVv2 does indeed specify messages, not packet=
s.
>>>>>> Not the version that was current when I wrote my comments. I haven't c=
hecked if that was the most recent now or not. But it doesn't sound as if yo=
u are suggesting there have been recent changes in that area.
>=20


From nobody Mon Sep  8 14:19:28 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19A151A0354 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 14:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H1RyMk7QFLTM for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 14:19:23 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB441A02E1 for <manet@ietf.org>; Mon,  8 Sep 2014 14:19:22 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=tx2KM0Aj7rsbELbaeTWwRc0qV+xSxa35N2gqzkEu4WlLseUsT9Z5iH6Wzlt/Num8; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XR6Ku-0004iM-2d; Mon, 08 Sep 2014 17:18:56 -0400
Message-ID: <540E1D3E.9050703@earthlink.net>
Date: Mon, 08 Sep 2014 14:18:54 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christopher Dearlove <christopher.dearlove@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com>
In-Reply-To: <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac76000598460abaf425e71fd4c88bd5028350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/4VIcglWY_ZTGVPZCbEEa4f_kMvQ
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 21:19:26 -0000

Hello Chris,

AODVv2 needs the functionality because it relies on
reverse path forwarding.

AODVv2 should be able to control the dissemination of
AODVv2 messages, and since AODVv2 messages are contained
in packets, then it seems that AODVv2 ought to be able to
specify how packets containing AODVv2 messages are to
be disseminated.

In RFC 5444, one finds the following:

>     Messages are designed to be able to be forwarded over one or more
>     logical hops, in a new packet for each logical hop.  Each logical hop
>     may consist of one or more IP hops.

I admit that this passage may be interpreted in various different ways.
But to me it meant that AODVv2 needs to make sure that there would
just be one hop.  The term "logical hop" isn't defined in the document,
and I'm sure we could both write down multiple reasonable definitions
for the term.  Overlay networks come to mind, or multi-link Ethernet
media, or ...

Regards,
Charlie P.



On 9/8/2014 1:58 PM, Christopher Dearlove wrote:
> Why does AODVv2 need this functionality any more than, say, NHDP, OLSRv2 or SMF? 5444 packets are meant to travel only one hop, it's part of the multiplexer design. If 5082 helps ensure this, this is something to apply at that level. This is not and cannot be an AODVv2 function, because AODVv2 isn't in change of packets.
>
> --
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>
>> On 8 Sep 2014, at 21:21, Charlie Perkins <charles.perkins@earthlink.net> wrote:
>>
>> Hello Chris,
>>
>> In general, if a routing protocol cannot specify TTL=255,
>> then something is definitely broken.  Message bundling
>> is not a good enough excuse for disabling this function.
>>
>> AODVv2 specifically does need the functionality, and so
>> the general statement does have a relevant specific
>> example.
>>
>> Regards,
>> Charlie P.
>>
>>
>>> On 9/8/2014 11:57 AM, Christopher Dearlove wrote:
>>> Actually, it was. AODVv2 can't adhere to RFC 5082. It has to be the 5444 multiplexer that does or doesn't adhere to it. It's probably not specified whether it does or not (it certainly isn't specified that it does., It might say TTL = 1, I don't recall right now,
>>>
>>> There are then choices:
>>> - Write something new to mandate all implementations of the 5444 multiplexer to adhere to 5082. I would be strongly against that.
>>> - Put a recommendation (i.e. a should) into AODVv2 that the 5444 multiplexer it uses should adhere to 5082. Not my first choice.
>>> - Put a requirement (i.e a must) into AODVv22 that the 5444 multiplexer it uses must adhere to 5082. I would be strongly against that too.
>>> - Leave it up to whoever implements the 5444 multiplexer, which already is required to fulfil the key requirement here (that packets only travel one logical hop - but physical hops?)
>>>
>>> Te question is, why is AODVv2 any more needing of this than anything else? If it's not, then the issue definitely becomes one of point 4.
>>>
>>> Now providing advice about the 5444 multiplexer, including any reference to 5082, is really the job of another document on broader 5444 advice. One that is bubbling up the 5444 authors' (at least) priority list. I don't have a position currently on what emphasis should be put on 5082 in such a document, and I don't know anyone else's views on that matter either.
>>>
>>>
>>>> On 8 Sep 2014, at 19:19, Charlie Perkins wrote:
>>>>
>>>> Hello Chris,
>>>>
>>>> No offense taken, so no forgiveness needed.
>>>>
>>>> I don't think that RFC 5444 procludes AODVv2
>>>> from specifying adherence to RFC 5082, if that was
>>>> the intention of your remark...
>>>>
>>>> Regards,
>>>> Charlie P.
>>>>
>>>>
>>>>> On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
>>>>> Well, you'll forgive me for commenting on the version that was newest when I made my original comments, not a then-future version.
>>>>>
>>>>> A quick skim shows the second paragraph of section 5.4 is outside AODV's competence, but at the point I stopped skimming that was the main point I noted.
>>>>>
>>>>>
>>>>>> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>>>>>>
>>>>>> Hello Chris,
>>>>>>
>>>>>> Yes, there have been several recent changes, included in the last
>>>>>> version, and most likely some more to be included in the upcoming
>>>>>> version.  The intention is to completely avoid any confusion.
>>>>>>
>>>>>> Regards,
>>>>>> Charlie P.
>>>>>>
>>>>>>
>>>>>>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>>>>>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>>>>>> To my understanding, AODVv2 does indeed specify messages, not packets.
>>>>>>> Not the version that was current when I wrote my comments. I haven't checked if that was the most recent now or not. But it doesn't sound as if you are suggesting there have been recent changes in that area.


From nobody Mon Sep  8 14:43:53 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1C891A03E5 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 14:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A3J3ODQJNfUE for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 14:43:50 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6359B1A039D for <manet@ietf.org>; Mon,  8 Sep 2014 14:43:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 3D9E31D89FA; Mon,  8 Sep 2014 14:43:50 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 89B6E1C0184; Mon,  8 Sep 2014 14:43:49 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (11D257)
In-Reply-To: <540E1D3E.9050703@earthlink.net>
Date: Mon, 8 Sep 2014 23:43:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0F4658F-03C7-4E9A-9448-ACF601241163@thomasclausen.org>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net>
To: Charlie Perkins <charles.perkins@earthlink.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/E05l-y_5Xf7cVQtJoSvM_dFCjxM
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>, manet-ads <manet-ads@tools.ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 21:43:52 -0000

> On 08 Sep 2014, at 23:18, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
> Hello Chris,
>=20
> AODVv2 needs the functionality because it relies on
> reverse path forwarding.
>=20
> AODVv2 should be able to control the dissemination of
> AODVv2 messages, and since AODVv2 messages are contained
> in packets, then it seems that AODVv2 ought to be able to
> specify how packets containing AODVv2 messages are to
> be disseminated.

Having designed reactive protocols within the RFC5444 framework, I can attes=
t to the fact that there are no obstacles posed by the use of RFC5444-messag=
es on this (or any other) points. Indeed, using RFC5444 messages for this is=
 both straight-forward and intuitive.

There is absolutely no technical reason to want to "re-define" or "re-interp=
ret", or "interpret in a non-generic, non-interoperable form" RFC5444.=20

None. Nada. There's tons of running, deployed code that testifies to this.

Years have passed, and this point of RFC5444/RFC5498 compliance has been dis=
cussed, explained, explained again, and again, and again, yet we're still se=
eing a non-compliant specification, and we are still arguing this issue. Wit=
h the same arguments brought forward by the current authors of the reactive p=
rotocol specification, and the same patient explanations from the WG partici=
pants.

I am utterly befuddled as to why the authors of this particular specificatio=
n are so insistent on going against what appears to be overwhelming WG conse=
nsus, as well as the body of RFCs published by this WG. I even believe that o=
ne of the chairs, years ago (!), reminded the authors of this fact.

Respectfully,

Thomas

> In RFC 5444, one finds the following:
>=20
>>   Messages are designed to be able to be forwarded over one or more
>>   logical hops, in a new packet for each logical hop.  Each logical hop
>>   may consist of one or more IP hops.
>=20
> I admit that this passage may be interpreted in various different ways.
> But to me it meant that AODVv2 needs to make sure that there would
> just be one hop.  The term "logical hop" isn't defined in the document,
> and I'm sure we could both write down multiple reasonable definitions
> for the term.  Overlay networks come to mind, or multi-link Ethernet
> media, or ...
>=20
> Regards,
> Charlie P.
>=20
>=20
>=20
>> On 9/8/2014 1:58 PM, Christopher Dearlove wrote:
>> Why does AODVv2 need this functionality any more than, say, NHDP, OLSRv2 o=
r SMF? 5444 packets are meant to travel only one hop, it's part of the multi=
plexer design. If 5082 helps ensure this, this is something to apply at that=
 level. This is not and cannot be an AODVv2 function, because AODVv2 isn't i=
n change of packets.
>>=20
>> --
>> Christopher Dearlove
>> christopher.dearlove@gmail.com (iPhone)
>> chris@mnemosyne.demon.co.uk (home)
>>=20
>>> On 8 Sep 2014, at 21:21, Charlie Perkins <charles.perkins@earthlink.net>=
 wrote:
>>>=20
>>> Hello Chris,
>>>=20
>>> In general, if a routing protocol cannot specify TTL=3D255,
>>> then something is definitely broken.  Message bundling
>>> is not a good enough excuse for disabling this function.
>>>=20
>>> AODVv2 specifically does need the functionality, and so
>>> the general statement does have a relevant specific
>>> example.
>>>=20
>>> Regards,
>>> Charlie P.
>>>=20
>>>=20
>>>> On 9/8/2014 11:57 AM, Christopher Dearlove wrote:
>>>> Actually, it was. AODVv2 can't adhere to RFC 5082. It has to be the 544=
4 multiplexer that does or doesn't adhere to it. It's probably not specified=
 whether it does or not (it certainly isn't specified that it does., It migh=
t say TTL =3D 1, I don't recall right now,
>>>>=20
>>>> There are then choices:
>>>> - Write something new to mandate all implementations of the 5444 multip=
lexer to adhere to 5082. I would be strongly against that.
>>>> - Put a recommendation (i.e. a should) into AODVv2 that the 5444 multip=
lexer it uses should adhere to 5082. Not my first choice.
>>>> - Put a requirement (i.e a must) into AODVv22 that the 5444 multiplexer=
 it uses must adhere to 5082. I would be strongly against that too.
>>>> - Leave it up to whoever implements the 5444 multiplexer, which already=
 is required to fulfil the key requirement here (that packets only travel on=
e logical hop - but physical hops?)
>>>>=20
>>>> Te question is, why is AODVv2 any more needing of this than anything el=
se? If it's not, then the issue definitely becomes one of point 4.
>>>>=20
>>>> Now providing advice about the 5444 multiplexer, including any referenc=
e to 5082, is really the job of another document on broader 5444 advice. One=
 that is bubbling up the 5444 authors' (at least) priority list. I don't hav=
e a position currently on what emphasis should be put on 5082 in such a docu=
ment, and I don't know anyone else's views on that matter either.
>>>>=20
>>>>=20
>>>>> On 8 Sep 2014, at 19:19, Charlie Perkins wrote:
>>>>>=20
>>>>> Hello Chris,
>>>>>=20
>>>>> No offense taken, so no forgiveness needed.
>>>>>=20
>>>>> I don't think that RFC 5444 procludes AODVv2
>>>>> from specifying adherence to RFC 5082, if that was
>>>>> the intention of your remark...
>>>>>=20
>>>>> Regards,
>>>>> Charlie P.
>>>>>=20
>>>>>=20
>>>>>> On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
>>>>>> Well, you'll forgive me for commenting on the version that was newest=
 when I made my original comments, not a then-future version.
>>>>>>=20
>>>>>> A quick skim shows the second paragraph of section 5.4 is outside AOD=
V's competence, but at the point I stopped skimming that was the main point I=
 noted.
>>>>>>=20
>>>>>>=20
>>>>>>> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>>>>>>>=20
>>>>>>> Hello Chris,
>>>>>>>=20
>>>>>>> Yes, there have been several recent changes, included in the last
>>>>>>> version, and most likely some more to be included in the upcoming
>>>>>>> version.  The intention is to completely avoid any confusion.
>>>>>>>=20
>>>>>>> Regards,
>>>>>>> Charlie P.
>>>>>>>=20
>>>>>>>=20
>>>>>>>>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>>>>>>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>>>>>>> To my understanding, AODVv2 does indeed specify messages, not pack=
ets.
>>>>>>>> Not the version that was current when I wrote my comments. I haven'=
t checked if that was the most recent now or not. But it doesn't sound as if=
 you are suggesting there have been recent changes in that area.
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Mon Sep  8 14:52:46 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE5AE1A02A5 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 14:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Or_iApuRenW0 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 14:52:34 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52F0D1A03CA for <manet@ietf.org>; Mon,  8 Sep 2014 14:52:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 27EBB261119; Mon,  8 Sep 2014 14:52:34 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 6758C1D89FA; Mon,  8 Sep 2014 14:52:33 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (11D257)
In-Reply-To: <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com>
Date: Mon, 8 Sep 2014 23:52:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A9BDE93-9BF1-47D2-B50A-6A4BF6FD6F6C@thomasclausen.org>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/xWed572qvZxqLev38spMqEmDCAo
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "<draft-ietf-manet-aodvv2@tools.ietf.org>" <draft-ietf-manet-aodvv2@tools.ietf.org>, "<manet@ietf.org>" <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 21:52:36 -0000

> On 08 Sep 2014, at 22:58, Christopher Dearlove <christopher.dearlove@gmail=
.com> wrote:
>=20
> Why does AODVv2 need this functionality any more than, say, NHDP, OLSRv2 o=
r SMF? 5444 packets are meant to travel only one hop, it's part of the multi=
plexer design. If 5082 helps ensure this, this is something to apply at that=
 level. This is not and cannot be an AODVv2 function, because AODVv2 isn't i=
n change of packets.
>=20

The above is, probably, the most concise way of summarizing this fact. I am i=
n full agreement with Chris here.

I'll add that, having designed and implemented reactive protocols using RFC5=
444, that it is perfectly feasible, even easy, to do so, and respect the 549=
8/5444 architecture.

Thomas

> -- =20
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>=20
>> On 8 Sep 2014, at 21:21, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>>=20
>> Hello Chris,
>>=20
>> In general, if a routing protocol cannot specify TTL=3D255,
>> then something is definitely broken.  Message bundling
>> is not a good enough excuse for disabling this function.
>>=20
>> AODVv2 specifically does need the functionality, and so
>> the general statement does have a relevant specific
>> example.
>>=20
>> Regards,
>> Charlie P.
>>=20
>>=20
>>> On 9/8/2014 11:57 AM, Christopher Dearlove wrote:
>>> Actually, it was. AODVv2 can't adhere to RFC 5082. It has to be the 5444=
 multiplexer that does or doesn't adhere to it. It's probably not specified w=
hether it does or not (it certainly isn't specified that it does., It might s=
ay TTL =3D 1, I don't recall right now,
>>>=20
>>> There are then choices:
>>> - Write something new to mandate all implementations of the 5444 multipl=
exer to adhere to 5082. I would be strongly against that.
>>> - Put a recommendation (i.e. a should) into AODVv2 that the 5444 multipl=
exer it uses should adhere to 5082. Not my first choice.
>>> - Put a requirement (i.e a must) into AODVv22 that the 5444 multiplexer i=
t uses must adhere to 5082. I would be strongly against that too.
>>> - Leave it up to whoever implements the 5444 multiplexer, which already i=
s required to fulfil the key requirement here (that packets only travel one l=
ogical hop - but physical hops?)
>>>=20
>>> Te question is, why is AODVv2 any more needing of this than anything els=
e? If it's not, then the issue definitely becomes one of point 4.
>>>=20
>>> Now providing advice about the 5444 multiplexer, including any reference=
 to 5082, is really the job of another document on broader 5444 advice. One t=
hat is bubbling up the 5444 authors' (at least) priority list. I don't have a=
 position currently on what emphasis should be put on 5082 in such a documen=
t, and I don't know anyone else's views on that matter either.
>>>=20
>>>=20
>>>> On 8 Sep 2014, at 19:19, Charlie Perkins wrote:
>>>>=20
>>>> Hello Chris,
>>>>=20
>>>> No offense taken, so no forgiveness needed.
>>>>=20
>>>> I don't think that RFC 5444 procludes AODVv2
>>>> from specifying adherence to RFC 5082, if that was
>>>> the intention of your remark...
>>>>=20
>>>> Regards,
>>>> Charlie P.
>>>>=20
>>>>=20
>>>>> On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
>>>>> Well, you'll forgive me for commenting on the version that was newest w=
hen I made my original comments, not a then-future version.
>>>>>=20
>>>>> A quick skim shows the second paragraph of section 5.4 is outside AODV=
's competence, but at the point I stopped skimming that was the main point I=
 noted.
>>>>>=20
>>>>>=20
>>>>>> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>>>>>>=20
>>>>>> Hello Chris,
>>>>>>=20
>>>>>> Yes, there have been several recent changes, included in the last
>>>>>> version, and most likely some more to be included in the upcoming
>>>>>> version.  The intention is to completely avoid any confusion.
>>>>>>=20
>>>>>> Regards,
>>>>>> Charlie P.
>>>>>>=20
>>>>>>=20
>>>>>>>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>>>>>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>>>>>> To my understanding, AODVv2 does indeed specify messages, not packe=
ts.
>>>>>>> Not the version that was current when I wrote my comments. I haven't=
 checked if that was the most recent now or not. But it doesn't sound as if y=
ou are suggesting there have been recent changes in that area.
>>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Mon Sep  8 14:59:48 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF7C71A03A8 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 14:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMzfqmpGB6AD for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 14:59:44 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 187F11A0323 for <manet@ietf.org>; Mon,  8 Sep 2014 14:59:43 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id k14so1380305wgh.0 for <manet@ietf.org>; Mon, 08 Sep 2014 14:59:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=nDOn9Mh+LErLHaa/dK/sr80v44NrZANdGtf4/GsjiMo=; b=EgDIunXzl6mtwBdATo76fKiJtoWCgRKPIjp6hEJlAVNfPfuW0/elTMY8kj4ZJ4rHJ4 VWxesSYMnET6FHCazDyH0klXXWjtDkq0c+ZIVMi6uTMDMmja/+Ngb+9yI2CXLdOJPVYt q1sN+zE45L/cNCEhH//zlPOwthHH9cjrUiIiR/T2axig2SzMtx58e0SvMR+2wOch7cgP qjPkTcV6gJCJpnWAe2anPZRxwNeSnl4XvpMa9KI/qeqYdtoEO+fS4plBaeSaGlSfOiGl Hbhe65bIZPm5dPTu7raG3QPYoZVxszbh46cNq+DaHHAz4P9NKsAJmDGCxcSXzkrPMwH6 CBOg==
X-Received: by 10.180.101.65 with SMTP id fe1mr25983981wib.53.1410213582674; Mon, 08 Sep 2014 14:59:42 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id ga9sm12522199wjb.45.2014.09.08.14.59.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 14:59:41 -0700 (PDT)
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <540E1D3E.9050703@earthlink.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <5023618F-C58D-404D-8539-FF0CEABA1B27@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Mon, 8 Sep 2014 22:59:39 +0100
To: Charlie Perkins <charles.perkins@earthlink.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/oRPUbUsdXz5Mqw3S0uLjb5u1PCI
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 21:59:47 -0000

This is no different to NHDP's requirements (which may use the IP packet sou=
rce address). It is, as I have said, a 5444 multiplexing issue.

It does, I agree open up the question as to what one logical hop means preci=
sely. Right now I forget why that distinction was put in 5444, I think was a=
 requirement from outside the authors.

But this is not specific to AODVv2, nor does it make 5082 mandatory, that's j=
ust one way to achieve this. And it's just not acceptable for AODVv2 to atte=
mpt to control packets, because what if another protocol tries doing the sam=
e, inconsistently.

Rather the starting point should be what are the actual requirements (which a=
re as you note about the properties that make reverse path forwarding workin=
g).

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 8 Sep 2014, at 22:18, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
> Hello Chris,
>=20
> AODVv2 needs the functionality because it relies on
> reverse path forwarding.
>=20
> AODVv2 should be able to control the dissemination of
> AODVv2 messages, and since AODVv2 messages are contained
> in packets, then it seems that AODVv2 ought to be able to
> specify how packets containing AODVv2 messages are to
> be disseminated.
>=20
> In RFC 5444, one finds the following:
>=20
>>    Messages are designed to be able to be forwarded over one or more
>>    logical hops, in a new packet for each logical hop.  Each logical hop
>>    may consist of one or more IP hops.
>=20
> I admit that this passage may be interpreted in various different ways.
> But to me it meant that AODVv2 needs to make sure that there would
> just be one hop.  The term "logical hop" isn't defined in the document,
> and I'm sure we could both write down multiple reasonable definitions
> for the term.  Overlay networks come to mind, or multi-link Ethernet
> media, or ...
>=20
> Regards,
> Charlie P.
>=20
>=20
>=20
>> On 9/8/2014 1:58 PM, Christopher Dearlove wrote:
>> Why does AODVv2 need this functionality any more than, say, NHDP, OLSRv2 o=
r SMF? 5444 packets are meant to travel only one hop, it's part of the multi=
plexer design. If 5082 helps ensure this, this is something to apply at that=
 level. This is not and cannot be an AODVv2 function, because AODVv2 isn't i=
n change of packets.
>>=20
>> --
>> Christopher Dearlove
>> christopher.dearlove@gmail.com (iPhone)
>> chris@mnemosyne.demon.co.uk (home)
>>=20
>>> On 8 Sep 2014, at 21:21, Charlie Perkins <charles.perkins@earthlink.net>=
 wrote:
>>>=20
>>> Hello Chris,
>>>=20
>>> In general, if a routing protocol cannot specify TTL=3D255,
>>> then something is definitely broken.  Message bundling
>>> is not a good enough excuse for disabling this function.
>>>=20
>>> AODVv2 specifically does need the functionality, and so
>>> the general statement does have a relevant specific
>>> example.
>>>=20
>>> Regards,
>>> Charlie P.
>>>=20
>>>=20
>>>> On 9/8/2014 11:57 AM, Christopher Dearlove wrote:
>>>> Actually, it was. AODVv2 can't adhere to RFC 5082. It has to be the 544=
4 multiplexer that does or doesn't adhere to it. It's probably not specified=
 whether it does or not (it certainly isn't specified that it does., It migh=
t say TTL =3D 1, I don't recall right now,
>>>>=20
>>>> There are then choices:
>>>> - Write something new to mandate all implementations of the 5444 multip=
lexer to adhere to 5082. I would be strongly against that.
>>>> - Put a recommendation (i.e. a should) into AODVv2 that the 5444 multip=
lexer it uses should adhere to 5082. Not my first choice.
>>>> - Put a requirement (i.e a must) into AODVv22 that the 5444 multiplexer=
 it uses must adhere to 5082. I would be strongly against that too.
>>>> - Leave it up to whoever implements the 5444 multiplexer, which already=
 is required to fulfil the key requirement here (that packets only travel on=
e logical hop - but physical hops?)
>>>>=20
>>>> Te question is, why is AODVv2 any more needing of this than anything el=
se? If it's not, then the issue definitely becomes one of point 4.
>>>>=20
>>>> Now providing advice about the 5444 multiplexer, including any referenc=
e to 5082, is really the job of another document on broader 5444 advice. One=
 that is bubbling up the 5444 authors' (at least) priority list. I don't hav=
e a position currently on what emphasis should be put on 5082 in such a docu=
ment, and I don't know anyone else's views on that matter either.
>>>>=20
>>>>=20
>>>>> On 8 Sep 2014, at 19:19, Charlie Perkins wrote:
>>>>>=20
>>>>> Hello Chris,
>>>>>=20
>>>>> No offense taken, so no forgiveness needed.
>>>>>=20
>>>>> I don't think that RFC 5444 procludes AODVv2
>>>>> from specifying adherence to RFC 5082, if that was
>>>>> the intention of your remark...
>>>>>=20
>>>>> Regards,
>>>>> Charlie P.
>>>>>=20
>>>>>=20
>>>>>> On 9/8/2014 11:12 AM, Christopher Dearlove wrote:
>>>>>> Well, you'll forgive me for commenting on the version that was newest=
 when I made my original comments, not a then-future version.
>>>>>>=20
>>>>>> A quick skim shows the second paragraph of section 5.4 is outside AOD=
V's competence, but at the point I stopped skimming that was the main point I=
 noted.
>>>>>>=20
>>>>>>=20
>>>>>>> On 8 Sep 2014, at 18:57, Charlie Perkins wrote:
>>>>>>>=20
>>>>>>> Hello Chris,
>>>>>>>=20
>>>>>>> Yes, there have been several recent changes, included in the last
>>>>>>> version, and most likely some more to be included in the upcoming
>>>>>>> version.  The intention is to completely avoid any confusion.
>>>>>>>=20
>>>>>>> Regards,
>>>>>>> Charlie P.
>>>>>>>=20
>>>>>>>=20
>>>>>>>>> On 9/8/2014 10:47 AM, Christopher Dearlove wrote:
>>>>>>>>> On 8 Sep 2014, at 18:34, Charlie Perkins wrote:
>>>>>>>>> To my understanding, AODVv2 does indeed specify messages, not pack=
ets.
>>>>>>>> Not the version that was current when I wrote my comments. I haven'=
t checked if that was the most recent now or not. But it doesn't sound as if=
 you are suggesting there have been recent changes in that area.
>=20


From nobody Mon Sep  8 15:03:09 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B39121A0267 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 15:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4e92fAY4qoL for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 15:03:02 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99FC31A03A8 for <manet@ietf.org>; Mon,  8 Sep 2014 15:03:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 729F91C0466; Mon,  8 Sep 2014 15:03:02 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id D47A21C0184; Mon,  8 Sep 2014 15:03:00 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-F756EB58-E8F7-4292-9695-D9B31DBF07DE
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (11D257)
In-Reply-To: <781FDD4B-A719-4FBA-AA38-A04377B886B4@gmail.com>
Date: Tue, 9 Sep 2014 00:02:58 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <30F476FB-8197-46AB-9EBD-2F45F5ABDDD9@thomasclausen.org>
References: <061.89377601617f43ae76e225162010f923@trac.tools.ietf.org> <53CC9987.6060104@computer.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECF7@GLKXM0002V.GREENLNK.net> <CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=V4z9jMp3NXixQ@mail.gmail.com> <540DE570.2040006@computer.org> <781FDD4B-A719-4FBA-AA38-A04377B886B4@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/t1Z9wvEd_f0_vTHc3Vovl8GcSXA
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>, manet-ads <manet-ads@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #46 (aodvv2): What is needed from IP and ICMP (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 22:03:06 -0000

--Apple-Mail-F756EB58-E8F7-4292-9695-D9B31DBF07DE
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Agree fully with Chris.

Reactive MANET protocol does "Weird Things" and have "Weird Interaction" wit=
h respect to the network layer, IP, and the forwarding path for data -- "Wei=
rd" in comparison with that which is "usual IP" (such as what a proactive ro=
uting protocol does), at least.

Different reactive protocols are doing different "Weird Things" and have dif=
ferent "Weird Interactions", of course. That's expected.

If considering implementing, deploying, a given reactive protocol on a given=
 platform, it is imperative to have those things clearly spelled out - in a f=
irst order, to understand if it is even feasible, second if it is a good ide=
a to do so. A good place to do so is the "Applicability Statement" of a prot=
ocol specification.

For starters, as Perkins describes reactive protocol behavior in the below, t=
he "best effort" semantics is if not suspended, then substantially re-interp=
reted by having a device queue packets for which it has no matching routing t=
able entries.=20

Similarly, as Perkins describes reactive protocol behavior in the below, rou=
ting table "misses" somehow must be intercepted and signaled to the routing p=
rocess, which must do something (generate control plane traffic). That, too,=
 is a departure from how IP routing (usually) works.

I am not judging if this is a good or a bad thing to do -- but if it is done=
, then it most definitely, absolutely, needs to be called out.

And, this is another of those things that the WG has been requesting for yea=
rs, with the same arguments, and which the current authors of the reactive W=
G protocol specification continues to ignore.=20

Respectfully,

Thomas


> On 08 Sep 2014, at 19:45, Christopher Dearlove <christopher.dearlove@gmail=
.com> wrote:
>=20
> I'm really not able t check the full context here, as I'm on holiday this w=
eek.
>=20
> I think that "you" was colloquially the routing protocol.
>=20
> But the point is, as you agree, this is not normal in the Internet. Doesn'=
t matter if this has been known in the ad hoc routing field for 20 years. Th=
is is intended to be a proposed standard in what is the wider Internet commu=
nity. Which experience has shown is not familiar with these matters, or vari=
ous other things, some of them simpler.
>=20
> This needs specifying for that reason. And also because people who want to=
 implement it know what capabilities they need. If they need queueing in the=
 IP stack they need to be told they need queuing in the IP stack. And that m=
akes it clear this needs to be more than a routing protocol if that capabili=
ty is not available as standard, which I think you just agreed it's not. Kno=
wledge in the ad hoc routing community isn't enough.
>=20
>=20
>> On 8 Sep 2014, at 18:20, Charles E. Perkins wrote:
>>=20
>>=20
>> Hello folks,
>>=20
>> I did not follow-up on this in July because I didn't see exactly
>> what I needed to respond to.  But since there is more discussion
>> I'll give it a try anyway.
>>=20
>>> On 9/7/2014 3:01 PM, Abdussalam Baryun wrote:
>>> Hi Chris,
>>>=20
>>> I think you may misunderstand MANET  reactive routing. I don't see your r=
eply answers the editor question of examples of AODVv2 needs from IP or ICMP=
. You mention that the protocol needs to see ICMP, what is the problem with t=
hat as RFC3561 already has similar issue and already accepted by WG.=20
>>>=20
>>> AB
>>>=20
>>>> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>>>> Just for a start you also need to know that IP routes are requested, th=
at packets are flowing, and to have the ability to queue packets.
>>=20
>> Here I am not sure who "you" is, but perhaps I will reformulate
>> to hazard a guess at an answer...
>>=20
>> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote something tha=
t Charlie interprets as follows:
>>> AODVv2 needs the following:
>>>     - information that IP routes are requested
>>>     - information that packets are flowing
>>>     - the ability to queue packets.
>>=20
>>=20
>> Tautologically, a reactive protocol reacts when a route is needed.
>> One might say that a route is requested when an application tries to
>> send a packet.  The fundamental concept of reactive routing is to
>> avoid creating routes that are not needed, and the way that has been
>> used to know whether a route is needed is when an application tries
>> to send a packet.
>>=20
>> If an application tries to send a packet, and the route is available, the=

>> packet has to wait until the route is available.  So, yes, queuing a
>> packet is needed.
>>=20
>> This has been known for 20 years.
>>=20
>>=20
>>=20
>>>> I'm pretty sure not all of those are mandated by IP. The routing protoc=
ol also needs to see ICMP messages - is that normal?
>>=20
>> As a matter of fact, looking at the state of routing in the Internet,
>> reactive routing is not normal.  So, no, these ideas are not normal,
>> depending on your definition.  However, if you restrict your determinatio=
n
>> of "normality" to the space of reactive protocols, then yes, these
>> ideas and techniques are quite normal.
>>=20
>> This has also been the case for a very long time.
>>=20
>>>>=20
>>>> As I said, it's a matter of what the whole architecture looks like.
>>>=20
>>=20
>> I'm not sure what to make of this...
>>=20
>>=20
>> --=20
>> Regards,
>> Charlie P.
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-F756EB58-E8F7-4292-9695-D9B31DBF07DE
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Agree fully with Chris.</div><div><br>=
</div><div>Reactive MANET protocol does "Weird Things" and have "Weird Inter=
action" with respect to the network layer, IP, and the forwarding path for d=
ata -- "Weird" in comparison with that which is "usual IP" (such as what a p=
roactive routing protocol does), at least.</div><div><br></div><div>Differen=
t reactive protocols are doing different "Weird Things" and have different "=
Weird Interactions", of course. That's expected.</div><div><br></div><div>If=
 considering implementing, deploying, a given reactive protocol on a given p=
latform, it is imperative to have those things clearly spelled out - in a fi=
rst order, to understand if it is even feasible, second if it is a good idea=
 to do so. A good place to do so is the "Applicability Statement" of a proto=
col specification.</div><div><br></div><div>For starters, as Perkins describ=
es reactive protocol behavior in the below, the "best effort" semantics is i=
f not suspended, then substantially re-interpreted by having a device queue p=
ackets for which it has no matching routing table entries.&nbsp;</div><div><=
br></div><div>Similarly, as Perkins describes reactive protocol behavior in t=
he below, routing table "misses" somehow must be intercepted and signaled to=
 the routing process, which must do something (generate control plane traffi=
c). That, too, is a departure from how IP routing (usually) works.</div><div=
><br></div><div>I am not judging if this is a good or a bad thing to do -- b=
ut if it is done, then it most definitely, absolutely, needs to be called ou=
t.</div><div><br></div><div>And, this is another of those things that the WG=
 has been requesting for years, with the same arguments, and which the curre=
nt authors of the reactive WG protocol specification continues to ignore.&nb=
sp;</div><div><br></div><div>Respectfully,</div><div><br></div><div>Thomas</=
div><div><br></div><div><br></div><div>On 08 Sep 2014, at 19:45, Christopher=
 Dearlove &lt;<a href=3D"mailto:christopher.dearlove@gmail.com">christopher.=
dearlove@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><di=
v><div>I'm really not able t check the full context here, as I'm on holiday t=
his week.</div><div><br></div><div>I think that "you" was colloquially the r=
outing protocol.</div><div><br></div><div>But the point is, as you agree, th=
is is not normal in the Internet. Doesn't matter if this has been known in t=
he ad hoc routing field for 20 years. This is intended to be a proposed stan=
dard in what is the wider Internet community. Which experience has shown is n=
ot familiar with these matters, or various other things, some of them simple=
r.</div><div><br></div><div>This needs specifying for that reason. And also b=
ecause people who want to implement it know what capabilities they need. If t=
hey need queueing in the IP stack they need to be told they need queuing in t=
he IP stack. And that makes it clear this needs to be more than a routing pr=
otocol if that capability is not available as standard, which I think you ju=
st agreed it's not. Knowledge in the ad hoc routing community isn't enough.<=
/div><div><br></div><br><div><div>On 8 Sep 2014, at 18:20, Charles E. Perkin=
s wrote:</div><br class=3D"Apple-interchange-newline"><blockquote type=3D"ci=
te">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    Hello folks,<br>
    <br>
    I did not follow-up on this in July because I didn't see exactly<br>
    what I needed to respond to.&nbsp; But since there is more discussion<br=
>
    I'll give it a try anyway.<br>
    <br>
    <div class=3D"moz-cite-prefix">On 9/7/2014 3:01 PM, Abdussalam Baryun
      wrote:<br>
    </div>
    <blockquote cite=3D"mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=3DV4z9jMp3=
NXixQ@mail.gmail.com" type=3D"cite">Hi Chris,
      <div><br>
      </div>
      <div>I think you may misunderstand MANET&nbsp;&nbsp;reactive routing. I=

        don't see your reply answers the editor question of examples of
        AODVv2 needs from IP or ICMP. You mention that the protocol
        needs to see ICMP, what is the problem with that as&nbsp;RFC3561
        already has similar issue and already accepted by WG.&nbsp;</div>
      <div><br>
      </div>
      <div>AB<br>
        <br>
        On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:<br>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Just for a
          start you also need to know that IP routes are requested, that
          packets are flowing, and to have the ability to queue packets.</bl=
ockquote>
      </div>
    </blockquote>
    <br>
    Here I am not sure who "you" is, but perhaps I will reformulate<br>
    to hazard a guess at an answer...<br>
    <br>
    On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote
    something that Charlie interprets as follows:<br>
    <blockquote type=3D"cite">AODVv2 needs the following:<br>
      &nbsp;&nbsp;&nbsp; - information that IP routes are requested<br>
      &nbsp;&nbsp;&nbsp; - information that packets are flowing<br>
      &nbsp;&nbsp;&nbsp; - the ability to queue packets.</blockquote>
    <br>
    <br>
    Tautologically, a reactive protocol reacts when a route is needed.<br>
    One might say that a route is requested when an application tries to<br>=

    send a packet.&nbsp; The fundamental concept of reactive routing is to<b=
r>
    avoid creating routes that are not needed, and the way that has been<br>=

    used to know whether a route is needed is when an application tries<br>
    to send a packet.<br>
    <br>
    If an application tries to send a packet, and the route is
    available, the<br>
    packet has to wait until the route is available.&nbsp; So, yes, queuing a=
<br>
    packet is needed.<br>
    <br>
    This has been known for 20 years.<br>
    <br>
    <br>
    <br>
    <blockquote cite=3D"mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=3DV4z9jMp3=
NXixQ@mail.gmail.com" type=3D"cite">
      <div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex"> I'm pretty
          sure not all of those are mandated by IP. The routing protocol
          also needs to see ICMP messages - is that normal?<br>
        </blockquote>
      </div>
    </blockquote>
    <br>
    As a matter of fact, looking at the state of routing in the
    Internet,<br>
    reactive routing is not normal.&nbsp; So, no, these ideas are not normal=
,<br>
    depending on your definition.&nbsp; However, if you restrict your
    determination<br>
    of "normality" to the space of reactive protocols, then yes, these<br>
    ideas and techniques are quite normal.<br>
    <br>
    This has also been the case for a very long time.<br>
    <br>
    <blockquote cite=3D"mid:CADnDZ8__AOXO6ti8C3u8qtpHNfxMGbZkQSBj=3DV4z9jMp3=
NXixQ@mail.gmail.com" type=3D"cite">
      <div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <br>
          As I said, it's a matter of what the whole architecture looks
          like.</blockquote>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    I'm not sure what to make of this...<br>
    <br>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Regards,
Charlie P.</pre>
  </div>

_______________________________________________<br>manet mailing list<br><a h=
ref=3D"mailto:manet@ietf.org">manet@ietf.org</a><br><a href=3D"https://www.i=
etf.org/mailman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet<=
/a><br></blockquote></div><br></div></blockquote><blockquote type=3D"cite"><=
div><span>_______________________________________________</span><br><span>ma=
net mailing list</span><br><span><a href=3D"mailto:manet@ietf.org">manet@iet=
f.org</a></span><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/m=
anet">https://www.ietf.org/mailman/listinfo/manet</a></span><br></div></bloc=
kquote></body></html>=

--Apple-Mail-F756EB58-E8F7-4292-9695-D9B31DBF07DE--


From nobody Mon Sep  8 17:58:30 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 283E71A034E for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 17:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IIbV-QZpc7rZ for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 17:58:20 -0700 (PDT)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 362611A034D for <manet@ietf.org>; Mon,  8 Sep 2014 17:58:20 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id f73so831116yha.25 for <manet@ietf.org>; Mon, 08 Sep 2014 17:58:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=f1EOrL/BRPYvxzFUVdtkh7plkrgZgLj9jF+8uXSHVC8=; b=J9H3fN+D28RJVDDGrE0SzjERLuZ5Ukego7WcDCtyvHok/P32FeO8I84NW28tGvBxOw V+iFK8v4ljSsJwfgqar3CyByPu6bmkYRI7wNjhj0Py7aBUxQxJ7yzH4+5jv6/mDEz3Kr MSwkalp7mPxIvcSzQwFKln3CkymWzVuKdFaX64AW0YBVlBmcN6TDrSOtauxnEwhu/0HF 5bfG/vsWjlbmtZs+gCb0Mf+CWKLVyLaHLZeTdjnwgd2N0GougI55dlTDc0Tb0BsSaHb5 b0Cy0PKXylHeNNuCb2ZKjp7agfQVWYJwrURIAllOtipOsWJe/qelij/ngM/wQnFHv1CC 66Ag==
MIME-Version: 1.0
X-Received: by 10.236.133.165 with SMTP id q25mr45806859yhi.62.1410224299280;  Mon, 08 Sep 2014 17:58:19 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Mon, 8 Sep 2014 17:58:19 -0700 (PDT)
In-Reply-To: <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com>
References: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org> <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com> <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com>
Date: Tue, 9 Sep 2014 02:58:19 +0200
Message-ID: <CADnDZ8_xaaBT8D_5w-Z99SEOQ=2JFTRKnHOpES576g-CRppVXg@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
Content-Type: multipart/alternative; boundary=20cf303a32c96992160502976e1a
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/mA7stxwfpBY2lndBOVKSbBW6mLc
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 00:58:24 -0000

--20cf303a32c96992160502976e1a
Content-Type: text/plain; charset=UTF-8

Hi Stan,


On Sunday, September 7, 2014, Stan Ratliff (sratliff) wrote:

>  Abdussalam,
>
>  On Sep 7, 2014, at 4:21 PM, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
>
>
>
> On Thursday, April 3, 2014, manet issue tracker wrote:
>
>> #33: RFC 5444 processing constraint
>>
>>  (Thomas Clausen)
>>  I have a general concern about how this protocol imposes constraints
>>  on RFC5444 usage, which precludes co-existence with other RFC5444
>>  protocols running on the same device.
>
>
>  You refer to which device (is it device with many routings) and still
> IETF has no RFC specifying rules for handling other RFC5444 protocols
> together running on same device. So that is future possible technology.
>
>
>  I do not understand what you wrote above. RFC5444 is specified as a
> "MUST" for all routing protocols *coming from the MANET WG*. As for other
> protocols (e.g. OSPF), there are no rules because there is no intersection.
>

I mean As if we have hybrid manet how devices will multiplex 5444 packets.
We still are not looking into hybrid routing issues. Yes RFC5444 specifies
formats for MANET protocols, however, IMHO it states that each protocol
defines its own messages and packets in some format conditions (i.
e, RFC5444) but not specifies multiplexing methods of those general format.


>
>
>>  Let me give an example hereof, from Section 5.4:
>>
>>
>>  {{{
>>                  When multiple messages are aggregated into a single
>> packet
>>                  according to RFC 5444 formatting, and the aggregation of
>>                  messages is also authenticated (e.g., with IPsec), and
>> the
>>                  IP destination is multiple hops away, it becomes
>>  infeasible
>>                  to delete individual messages.  In such cases, instead of
>>                  deleting individual messages, they are maintained in the
>>                  aggregation of messages, but simply ignored for further
>>                  processing.  In such cases where individual messages
>>  cannot
>>                  be deleted, in this document "disregarded" means
>>  "ignored".
>>                  Otherwise, any such "disregarded" AODVv2 messages SHOULD
>>  be
>>                  deleted from the aggregated messages in the RFC 5444
>>  packet.
>>  }}}
>>
>>  An RFC5444 packet is *never* to be sent more than one hop.
>>  ... A router receives an RFC5444 packet, decapsulates
>>  it, process each message (if appropriate), the owner process of each
>>  message identifies which messages are to be forwarded (if appropriate),
>>  hands those off to the appropriate "message multiplexing engine" which
>>  packs those messages up in a new RFC5444 packet, and transmits that
>>  new RFC5444 packet.
>
>
>  There is no 5444 multiplexing methods specified in IETF.  However, I
> think it is wrong designing protocols depending on formats, we design
> protocols then our formats and our multiplexing depend on our protocols.
>
>
>  RFC5444 itself describes ways that multiple (MANET WG-developed)
> protocols can be multiplexed.
>

As optional not mandatory. RFC5444 seems independent to parser methods and
routing protocols. Yes if we require multiple protocols cooperation then
the parser needs to be specified for that job not the routing protocols.
RFC5444 states that parser is independent of protocols. For hybrid
routing protocol drafts we must specify parser.


>
>
>>  Also, in RFC5444 messages, addresses are contained in address blocks.
>>  There is no semantics associated with an address being in one address
>>  block, or in another (in fact, (re-)organising addresses into address
>>  blocks is one of the tricks to use to obtain more compact messages).
>>  Likewise, there is no semantics associated with an address being first,
>>  last, or in any other position in an address block: the ordering of
>>  addresses in an address block carries no semantics.
>
>
>  You base your definition on which RFC, I think each protocol defines its
> own semantics as noticed by RFC5444.
>
>
>  I believe that to be incorrect - the notion is that:
> (1)  RFC5444 is specified as a MUST for all MANET WG-developed routing
> protocols.
>

This point is not against my input. I agree. So AODVv2 is using RFC5444 but
why we stick it to the parser. Chris input is explaining as packets are
only created at parsers but I think that RFC5444 does give option to
protocols to create packets as well. The process of only parsers do the job
of packing is not specified on RFC5444 nor in RFC5498.


> (2)  RFC5444 expresses no semantics with regard to ordering of address
> blocks in messages.
>

I know that it only gives syntax and conditions. So this is not against my
input also. So each protocol can use 5444 with each having their own
semantic of their messages/information (and even their way of packing their
information).

(3)  If the proposed protocol (in this case, AODVv2), imposes ordering of
> address blocks, then it (AODVv2) is incorrectly implementing RFC5444.
>

Not sure why you think that way. RFC5444 is not against ordering inside
a block. IMHO You misunderstood the ordering, because it is inside the one
address-block. So I agree we don't have ordering of blocks in RFC5444 and
also AODVv2 draft does not say ordering blocks.



>
>
>
>>
>>  Therefore, writing something like this:
>>
>>
>>  {{{
>>                  RteMsg.Address[i] denotes the [i]th address in an RFC
>> 5444
>>                  AddrBlk of the RteMsg. RteMsg.PrefixLength[i] denotes the
>>                  associated prefix length for RteMsg.Address[i], and
>>                  RteMsg.{field} denotes the corresponding value in the
>>  named
>>                  AddrTLV block associated with RteMsg.Address[i].
>>  }}}
>>
>>
>>  makes no sense whatsoever (aside from the fact that I do not understand
>>  the notation !RteMsg.{field} - that would indicate a "field" in a
>>  message, not in an attribute associated with an address).
>>
>>  Let me give one more example, from section 9:
>>
>>
>>  {{{
>>             If a message with an unknown type is received, the message is
>>             disregarded.
>>  }}}
>>
>>
>>  An implementation of this specification will (according to RFC5444)
>>  "own", and therefore get messages that this protocol has gotten
>>  assigned by IANA, say, RREQ/RREP/RERR/RREP_ACK.  Messages of any
>>  other Message Types will not (again, according to RFC5444) be
>>  delivered to an implementation of this protocol.
>>
>>  Therefore, this protocol <should not>
>>  specify discarding any message types other than those than it "owns".
>
>
>  Disregard does not mean drop, so those messages are still in
> next 5444 packet. This comes back to multiplexing by ownership or not,
> which that is not specified yet so we leave it for another future draft for
> multiplexing. We need to focus this reactive standard not make it
> complicated.
>
>
>  Again, I respectfully disagree. A deployment model to envision is a
> router, running both OLSRv2 and AODVv2. Both of those protocols share a
> transport using RFC5444 to a second router, which is also running both
> protocols. The "multiplexing" being spoken of would be a mix of OLSRv2 and
> AODVv2 messages, bundled up into an RFC5444 packet.
>

Ok, to be more general and to serve majority users of AODVv2 and more
security consideration.  we need to consider that some users don't want
such mix network and some do. First if users are wanting your mix scenario
then they go for a parser that is unified for both protocols ( this
case routers need same multiplexing method otherwise they don't work
), while parsers are independent of protocols as RFC5444 says. If the
AODVv2 sends a packet then parser is able to do packing again locally with
adding other messages if available. Secondly,  users don't want to use
specific unified parser dependence, so just the one protocol packing with
its user method for security purpose. This way we have more independence
for this AODVv2.

AB


>
>

--20cf303a32c96992160502976e1a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Stan,<div><br><br>On Sunday, September 7, 2014, Stan Ratliff (sratliff) =
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Abdussalam,=C2=A0
<div><br>
<div>
<div>On Sep 7, 2014, at 4:21 PM, Abdussalam Baryun &lt;<a>abdussalambaryun@=
gmail.com</a>&gt; wrote:</div>
<br>
<blockquote type=3D"cite"><br>
<br>
On Thursday, April 3, 2014, manet issue tracker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
#33: RFC 5444 processing constraint<br>
<br>
=C2=A0(Thomas Clausen)<br>
=C2=A0I have a general concern about how this protocol imposes constraints<=
br>
=C2=A0on RFC5444 usage, which precludes co-existence with other RFC5444<br>
=C2=A0protocols running on the same device.</blockquote>
<div><br>
</div>
<div>You refer to which device (is it device with many routings)=C2=A0and s=
till IETF has no RFC specifying rules for handling=C2=A0other RFC5444 proto=
cols together=C2=A0running on same device. So that is future possible techn=
ology.=C2=A0</div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<div>I do not understand what you wrote above. RFC5444 is specified as a &q=
uot;MUST&quot; for all routing protocols *coming from the MANET WG*. As for=
 other protocols (e.g. OSPF), there are no rules because there is no inters=
ection.=C2=A0</div></div></div></div></blockquote><div><br></div><div>I mea=
n As if we have hybrid manet=C2=A0how devices will multiplex 5444 packets. =
We still are=C2=A0not looking into hybrid routing issues.=C2=A0Yes RFC5444 =
specifies formats=C2=A0for MANET protocols, however, IMHO=C2=A0it states=C2=
=A0that each protocol defines its own=C2=A0messages and packets in=C2=A0som=
e format=C2=A0conditions (i. e,=C2=A0RFC5444)=C2=A0but not specifies multip=
lexing methods of those general format.=C2=A0</div><div></div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div=
><div>
<br>
<blockquote type=3D"cite">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
=C2=A0Let me give an example hereof, from Section 5.4:<br>
<br>
<br>
=C2=A0{{{<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0When multiple=
 messages are aggregated into a single packet<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0according to =
RFC 5444 formatting, and the aggregation of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0messages is a=
lso authenticated (e.g., with IPsec), and the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IP destinatio=
n is multiple hops away, it becomes<br>
=C2=A0infeasible<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0to delete ind=
ividual messages.=C2=A0 In such cases, instead of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0deleting indi=
vidual messages, they are maintained in the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0aggregation o=
f messages, but simply ignored for further<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0processing.=
=C2=A0 In such cases where individual messages<br>
=C2=A0cannot<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0be deleted, i=
n this document &quot;disregarded&quot; means<br>
=C2=A0&quot;ignored&quot;.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Otherwise, an=
y such &quot;disregarded&quot; AODVv2 messages SHOULD<br>
=C2=A0be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0deleted from =
the aggregated messages in the RFC 5444<br>
=C2=A0packet.<br>
=C2=A0}}}<br>
<br>
=C2=A0An RFC5444 packet is *never* to be sent more than one hop.<br>
=C2=A0... A router receives an RFC5444 packet, decapsulates<br>
=C2=A0it, process each message (if appropriate), the owner process of each<=
br>
=C2=A0message identifies which messages are to be forwarded (if appropriate=
),<br>
=C2=A0hands those off to the appropriate &quot;message multiplexing engine&=
quot; which<br>
=C2=A0packs those messages up in a new RFC5444 packet, and transmits that<b=
r>
=C2=A0new RFC5444 packet.</blockquote>
<div><br>
</div>
<div>There is no 5444=C2=A0multiplexing methods=C2=A0specified in IETF. =C2=
=A0However, I think it is wrong designing protocols depending on formats, w=
e design protocols then our formats and our multiplexing depend on our prot=
ocols.=C2=A0</div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<div>RFC5444 itself describes ways that multiple (MANET WG-developed) proto=
cols can be multiplexed.</div></div></div></div></blockquote><div><br></div=
><div>As optional not mandatory. RFC5444 seems independent to parser method=
s and routing protocols.=C2=A0Yes if we require multiple protocols cooperat=
ion then the parser needs to be specified for that job=C2=A0not the routing=
=C2=A0protocols. RFC5444 states that parser is independent of protocols. Fo=
r hybrid routing=C2=A0protocol drafts we must specify parser.=C2=A0</div><d=
iv>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break=
-word"><div><div>
<br>
<blockquote type=3D"cite">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
=C2=A0Also, in RFC5444 messages, addresses are contained in address blocks.=
<br>
=C2=A0There is no semantics associated with an address being in one address=
<br>
=C2=A0block, or in another (in fact, (re-)organising addresses into address=
<br>
=C2=A0blocks is one of the tricks to use to obtain more compact messages).<=
br>
=C2=A0Likewise, there is no semantics associated with an address being firs=
t,<br>
=C2=A0last, or in any other position in an address block: the ordering of<b=
r>
=C2=A0addresses in an address block carries no semantics.</blockquote>
<div><br>
</div>
<div>You base your definition on which RFC, I think each protocol defines i=
ts own semantics as noticed by RFC5444.=C2=A0</div>
</blockquote>
<div><br>
</div>
<div>I believe that to be incorrect - the notion is that:</div>
<div>(1) =C2=A0RFC5444 is specified as a MUST for all MANET WG-developed ro=
uting protocols.</div></div></div></div></blockquote><div>=C2=A0</div><div>=
This point is not against my input. I agree. So AODVv2 is using RFC5444 but=
 why we stick it to the parser. Chris input is explaining as packets are on=
ly created at parsers but I think that RFC5444 does give option to protocol=
s to create packets as well. The process of only parsers do the job of pack=
ing is not specified on RFC5444 nor in RFC5498.=C2=A0</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><d=
iv>
<div>(2) =C2=A0RFC5444 expresses no semantics with regard to ordering of ad=
dress blocks in messages.</div></div></div></div></blockquote><div><br></di=
v><div>I know that it only gives syntax and conditions. So this is not agai=
nst my input also. So each protocol can use 5444 with each having their own=
 semantic of their messages/information (and even their=C2=A0way of packing=
 their information).=C2=A0</div><div><br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div style=3D"word-wrap:break-word"><div><div>
<div>(3) =C2=A0If the proposed protocol (in this case, AODVv2), imposes ord=
ering of address blocks, then it (AODVv2) is incorrectly implementing RFC54=
44.=C2=A0</div></div></div></div></blockquote><div><br></div><div>Not sure =
why you think that way. RFC5444 is not against ordering inside a=C2=A0block=
.=C2=A0IMHO=C2=A0You misunderstood the ordering, because it=C2=A0is inside =
the one address-block. So I agree=C2=A0we don&#39;t have ordering of blocks=
 in RFC5444 and also AODVv2 draft=C2=A0does not say ordering blocks.=C2=A0<=
/div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div st=
yle=3D"word-wrap:break-word"><div><div>
<br>
<blockquote type=3D"cite">
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
=C2=A0Therefore, writing something like this:<br>
<br>
<br>
=C2=A0{{{<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0RteMsg.Addres=
s[i] denotes the [i]th address in an RFC 5444<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0AddrBlk of th=
e RteMsg. RteMsg.PrefixLength[i] denotes the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0associated pr=
efix length for RteMsg.Address[i], and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0RteMsg.{field=
} denotes the corresponding value in the<br>
=C2=A0named<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0AddrTLV block=
 associated with RteMsg.Address[i].<br>
=C2=A0}}}<br>
<br>
<br>
=C2=A0makes no sense whatsoever (aside from the fact that I do not understa=
nd<br>
=C2=A0the notation !RteMsg.{field} - that would indicate a &quot;field&quot=
; in a<br>
=C2=A0message, not in an attribute associated with an address).<br>
<br>
=C2=A0Let me give one more example, from section 9:<br>
<br>
<br>
=C2=A0{{{<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 If a message with an unknown type=
 is received, the message is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 disregarded.<br>
=C2=A0}}}<br>
<br>
<br>
=C2=A0An implementation of this specification will (according to RFC5444)<b=
r>
=C2=A0&quot;own&quot;, and therefore get messages that this protocol has go=
tten<br>
=C2=A0assigned by IANA, say, RREQ/RREP/RERR/RREP_ACK.=C2=A0 Messages of any=
<br>
=C2=A0other Message Types will not (again, according to RFC5444) be<br>
=C2=A0delivered to an implementation of this protocol.<br>
<br>
=C2=A0Therefore, this protocol &lt;should not&gt;<br>
=C2=A0specify discarding any message types other than those than it &quot;o=
wns&quot;.</blockquote>
<div><br>
</div>
<div>Disregard does not mean drop, so those messages are still in next=C2=
=A05444=C2=A0packet.=C2=A0This comes back to multiplexing by ownership or n=
ot, which that is not specified yet so=C2=A0we leave it for another future=
=C2=A0draft for multiplexing. We need to focus this reactive
 standard not make it complicated.=C2=A0</div>
</blockquote>
<div><br>
</div>
<div>Again, I respectfully disagree. A deployment model to envision is a ro=
uter, running both OLSRv2 and AODVv2. Both of those protocols share a trans=
port using RFC5444 to a second router, which is also running both protocols=
. The &quot;multiplexing&quot; being spoken
 of would be a mix of OLSRv2 and AODVv2 messages, bundled up into an RFC544=
4 packet.=C2=A0</div></div></div></div></blockquote><div><br></div><div>Ok,=
 to be more general and to serve majority=C2=A0users of AODVv2 and more sec=
urity consideration.=C2=A0=C2=A0we need to consider that some users don&#39=
;t want such mix network and some do. First if users are wanting your=C2=A0=
mix scenario then they go for a parser that is unified for both protocols (=
=C2=A0this case=C2=A0routers need same multiplexing method otherwise they d=
on&#39;t work ),=C2=A0while parsers are independent of protocols as RFC5444=
 says. If the AODVv2 sends a packet then parser is able to do packing again=
 locally=C2=A0with adding other messages if available.=C2=A0Secondly, =C2=
=A0users don&#39;t want to use specific unified=C2=A0parser dependence,=C2=
=A0so=C2=A0just the one=C2=A0protocol packing with its user method for secu=
rity purpose.=C2=A0This way we have more independence for this AODVv2.=C2=
=A0</div><div><br></div><div>AB</div><div><br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div style=3D"word-wrap:break-word"><div><div><div><br></div></div>=
<br>
</div>
</div>

</blockquote></div>

--20cf303a32c96992160502976e1a--


From nobody Mon Sep  8 18:15:31 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E7881A0311 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 18:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qBmfGgvSTPXk for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 18:15:19 -0700 (PDT)
Received: from mail-yh0-x229.google.com (mail-yh0-x229.google.com [IPv6:2607:f8b0:4002:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F5FC1A02BE for <manet@ietf.org>; Mon,  8 Sep 2014 18:15:19 -0700 (PDT)
Received: by mail-yh0-f41.google.com with SMTP id t59so1269614yho.28 for <manet@ietf.org>; Mon, 08 Sep 2014 18:15:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=keOYZkfoxs5cs10tj//6tctCmiFL4YkDwSLzEREnIqA=; b=kMLBaf4VZ8+oWKApWe+FHZMsjv4knllSxM5ekuCP8z/RRyvwH1Th1/MgS9V/dYCObl n9FDoLGeZyJNtom2G3xijyl+H/0WFWBqAoy2pJ+N+awa25QN/+NDeJXGZdaxtbEC5Pfp oibcQczbEABePvXP4VTJ3Ryh8YXT4praGL4qDThHCRTO9NzXsPIfsdS7AzIP6JoNds2Y F2fduT5wJnCZYYof0p+oil8JWShhWj1Ar3ywUVPM1BQ903ZnRqS1/qcc1QcjlGKaHIh8 GIb7NZxbpfeZjDWGzyHmXjUlBb5xBUxhu7+B8MdrOTCTGxm3yKXQLCnO6fwyPDYF0gu6 DazQ==
MIME-Version: 1.0
X-Received: by 10.236.83.129 with SMTP id q1mr76648yhe.124.1410225318486; Mon, 08 Sep 2014 18:15:18 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Mon, 8 Sep 2014 18:15:18 -0700 (PDT)
In-Reply-To: <A5DD62E7-82EC-4ACF-8A71-A9ADF81827A8@gmail.com>
References: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org> <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com> <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com> <A5DD62E7-82EC-4ACF-8A71-A9ADF81827A8@gmail.com>
Date: Tue, 9 Sep 2014 03:15:18 +0200
Message-ID: <CADnDZ89-c61ViZ3xWb6GUKur4bV2djca-jovrsx9G-4+sB_VkQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: multipart/alternative; boundary=20cf301af7db29f085050297abd1
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/YpqRDHWyCQ9N9eLTVOEU3-CJFpE
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 01:15:25 -0000

--20cf301af7db29f085050297abd1
Content-Type: text/plain; charset=UTF-8

On Sunday, September 7, 2014, Christopher Dearlove wrote:

> As Stan has said, with one addition (unless Stan said it and I missed it).
> 5444 describes how messages can be multiplexed.
>

5444 describes syntax not semantics of packing information, it also does
not describe multiplexing as not owned by protocols. So you argue that
AODVv2 draft should not mention packets as if RFC5444 means that packets
are only for parsers.



> 5498 says (as part of its using of the MANET protocol or port) you must
> use that multiplexing method.
>

IMHO It says we must use that specified syntax of information. And if using
many routing protocols in same network yes you must use unified parser (to
reduce overheads).

The multiplexing needs to be unified when you want to mix routing protocols
but if you don't want that for security purposes then leave
unified multiplexing, just use the routing protocol and put your new secure
packing. Parser and multiplexing needs a separate draft because there are
many problems with it and many considerations.

AB

>

--20cf301af7db29f085050297abd1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Sunday, September 7, 2014, Christopher Dearlove  wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"auto"><div>As Stan has said, with one=
 addition (unless Stan said it and I missed it). 5444 describes how message=
s can be multiplexed.=C2=A0</div></div></blockquote><div><br></div><div>544=
4 describes syntax not semantics of packing information, it also does not d=
escribe multiplexing as not owned by protocols. So you argue that AODVv2 dr=
aft should not mention packets as if RFC5444 means that packets are only fo=
r parsers.=C2=A0=C2=A0</div><div><br></div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div dir=3D"auto"><div>5498 says (as part of its using of t=
he MANET protocol or port) you must use that multiplexing method.=C2=A0</di=
v><div></div></div></blockquote><div><br></div><div>IMHO=C2=A0It says we mu=
st use that specified syntax of information. And if using many routing prot=
ocols=C2=A0in same network yes you must use unified parser (to reduce overh=
eads).=C2=A0</div><div><br></div><div>The multiplexing needs to be unified =
when you want to mix routing protocols but if you don&#39;t want that for s=
ecurity purposes then leave unified=C2=A0multiplexing, just use the routing=
=C2=A0protocol and put your new secure packing. Parser and multiplexing nee=
ds a separate draft because there are many problems with it and many consid=
erations.=C2=A0</div><div><br></div><div>AB</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"auto"><blockquote type=3D"cite"><div></div><blockquote typ=
e=3D"cite"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"></blockquote></blockquote><blockq=
uote type=3D"cite"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></blockquote=
><blockquote type=3D"cite"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></bl=
ockquote><blockquote type=3D"cite"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockq=
uote></blockquote><blockquote type=3D"cite"></blockquote></blockquote></div=
></blockquote>

--20cf301af7db29f085050297abd1--


From nobody Mon Sep  8 18:36:17 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8821A030A for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 18:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qTmpndDA7EY4 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 18:36:13 -0700 (PDT)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71DBF1A0353 for <manet@ietf.org>; Mon,  8 Sep 2014 18:36:11 -0700 (PDT)
Received: by mail-yh0-f47.google.com with SMTP id c41so9663455yho.20 for <manet@ietf.org>; Mon, 08 Sep 2014 18:36:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xyWYNGgiZ+jYtUq1nfshB0IsDExp81jahu16+qLlfSA=; b=LcshvlvI6q1jktpNTeguY3KvjlQWrWng48guJV/TsBKxclMmA8K17er2GWrawoERoJ YdeT2eowq3wNZ+AjV3dOlLyo8ru1ynqqKKw7UiqKcI3zO8cZypQO7X1Q6RPTLk7sAi87 YGftDcETjg3E5xKMFq/f6xoe3+B03G0kRk9zxKOntbPlcDY5wTAGfHSnRgnWU8o4eK/z pm3+hw0EaJzi02mKUSafHD4HhNT7pVWeU26cVv5faeRZrSo5s3xYR2ln7BjLX3Ry5/6E HooCEvZnOrBsFqSgTyygHabU4s/DRdBJ6vjuOsegpXppCGcGXTBdG71M4fqHtjq8AjF8 o4ig==
MIME-Version: 1.0
X-Received: by 10.236.141.148 with SMTP id g20mr41850938yhj.34.1410226570713;  Mon, 08 Sep 2014 18:36:10 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Mon, 8 Sep 2014 18:36:10 -0700 (PDT)
In-Reply-To: <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk>
Date: Tue, 9 Sep 2014 03:36:10 +0200
Message-ID: <CADnDZ89DKyuf66_+oJ+p65qu=QDZxjdJBJvSQugLi7ydBd3RCw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: multipart/alternative; boundary=20cf303b3e25ccde63050297f5f3
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/iyQJzDqV0_3IQUui_u1X1rtsDF4
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 01:36:15 -0000

--20cf303b3e25ccde63050297f5f3
Content-Type: text/plain; charset=UTF-8

Just my last comment in this ticket.

On Monday, September 8, 2014, Christopher Dearlove wrote:

> Really, I'm not wading through all that, as it becomes apparent early on
> that it misses the whole point.
> - 5444 defines a packet/message format,
> - 5444 defines how that can be used by a multiplexer. Yes, at this point
> that's optional.
> - 5498 makes use of that multiplexing approach mandatory on the manet
> protocol/port.
>
>
5498 does not specify for information-multiplexers but it specifies for
routing-protocols. Those allocations are owned by the routing protocols not
by the multiplexers. However, if we consider a use case of many routing
protocols sharing the MANET, then we must have unified multiplexer using
that allocated  port as 5498 state for routing.

RFC5498 can have an update to add another port with same ip number for
other purposes that mentions multiplexers use.

AB



>


>
>
>
>
>
>
>

--20cf303b3e25ccde63050297f5f3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Just my last comment in this ticket.=C2=A0<br><br>On Monday, September 8, 2=
014, Christopher Dearlove  wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Really,=
 I&#39;m not wading through all that, as it becomes apparent early on that =
it misses the whole point.<br>
- 5444 defines a packet/message format,<br>
- 5444 defines how that can be used by a multiplexer. Yes, at this point th=
at&#39;s optional.<br>
- 5498 makes use of that multiplexing approach mandatory on the manet proto=
col/port.<br><br></blockquote><div>=C2=A0</div><div>5498 does not specify f=
or information-multiplexers but it specifies for routing-protocols. Those a=
llocations are owned by the routing protocols not by the multiplexers. Howe=
ver, if we consider a use case of many routing protocols sharing the MANET,=
 then=C2=A0we must have unified multiplexer using that=C2=A0allocated=C2=A0=
=C2=A0port as 5498 state for routing.=C2=A0</div><div><br></div><div>RFC549=
8 can have an update to add=C2=A0another port with same ip number for other=
 purposes that mentions multiplexers use.=C2=A0</div><div><br></div><div>AB=
</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></bloc=
kquote><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>=
=C2=A0<br>=C2=A0<br><br>=C2=A0<br>
<br>
</blockquote>

--20cf303b3e25ccde63050297f5f3--


From nobody Mon Sep  8 18:51:57 2014
Return-Path: <bebemaster@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D598D1A0311 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 18:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jv07Mxj400kz for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 18:51:54 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96F521A034E for <manet@ietf.org>; Mon,  8 Sep 2014 18:51:53 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id pn19so18507182lab.4 for <manet@ietf.org>; Mon, 08 Sep 2014 18:51:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=o0Tldp+sQ0h1BGRXV+7yJrhN/W9kU4Os37nE5QFsbTc=; b=mBEeyIo5Qv5Z9Hq1E40gJVFLBumVZfjFlOune23wJ49+UZXsXRDDyjEXSuhvB3iDd7 R0ig9eUWva0h4YezdGtxJ22URO7UhBFYbTS05Zk4n5NYNPO3Cs1ZHyv5u9Lw0qETSp8b 1I9J2GcT0GidyVLoi8KVMPR94d70XMIBNwYGofwmBOy/i4QKZT4yYFY3KCvxtET0WSTv JRkK4dNS2uDRstAvRk6XhTH9/8AOrXkel75s+r329rkMFP5wX82Tr5pYZEfEDSh9eNTc 5Hdg8gxvkuwfHiviCFxNqbKzkrMZEgGNV5AR8A+gwIJ8u4Mm5h/fDw47TmuHts3xFaEG b9uw==
MIME-Version: 1.0
X-Received: by 10.152.10.203 with SMTP id k11mr16754668lab.30.1410227511817; Mon, 08 Sep 2014 18:51:51 -0700 (PDT)
Received: by 10.152.170.135 with HTTP; Mon, 8 Sep 2014 18:51:51 -0700 (PDT)
In-Reply-To: <CADnDZ89DKyuf66_+oJ+p65qu=QDZxjdJBJvSQugLi7ydBd3RCw@mail.gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <CADnDZ89DKyuf66_+oJ+p65qu=QDZxjdJBJvSQugLi7ydBd3RCw@mail.gmail.com>
Date: Mon, 8 Sep 2014 21:51:51 -0400
Message-ID: <CA+-pDCdxYAwjs9gmpK7o_FNdkmK9dmsoqbUFqJjOKHo8QeOSPQ@mail.gmail.com>
From: Justin Dean <bebemaster@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=001a113340cae4fbb20502982dd0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/eSATNj-5WFYcthJYxYhZsGZY7yQ
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 01:51:56 -0000

--001a113340cae4fbb20502982dd0
Content-Type: text/plain; charset=UTF-8

I think that some of us are missing the forest while looking at the trees.
The reasons for RFC5498 multiplexing requirement IS important and we should
just go opening up/asking for new ports.  One of the reasons it's there is
that so multiple different MANET protocols can work with each other with
minimal issues.  We do this already with NHDP and OLSRv2 and NHDP and SMF
TLV extensions and it's a very good thing.

The root of the issue is assigning semantics to the order of the addresses
which AODVv2 currently does and in doing so breaks multiplexer
implementations (mine included) the work around of throwing out the
multiplexer to get around this is wrongheaded as there are also very good
reasons (one of which Henning pointed out, future proofing by containing
information within tlvs and not by position); Other reasons include,
multiplexer reuse which enables both multi-protocol packaging (fewer
packets), code reuse (minor), packet compression in the address blocks
(potential large gain), and packet compression in the TLV space (also
potential large gain).

We (read MANET wg) came up with these requirements for very specific
reasons and at this point I see no reason let alone any compelling reason
to ignore or work around them.  If AODVv2 can get this right and abide by
the MANET design requirements it will in fact be a better protocol for it;
these aren't trivial meaningless requirements.

Justin

On Mon, Sep 8, 2014 at 9:36 PM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> Just my last comment in this ticket.
>
> On Monday, September 8, 2014, Christopher Dearlove wrote:
>
>> Really, I'm not wading through all that, as it becomes apparent early on
>> that it misses the whole point.
>> - 5444 defines a packet/message format,
>> - 5444 defines how that can be used by a multiplexer. Yes, at this point
>> that's optional.
>> - 5498 makes use of that multiplexing approach mandatory on the manet
>> protocol/port.
>>
>>
> 5498 does not specify for information-multiplexers but it specifies for
> routing-protocols. Those allocations are owned by the routing protocols not
> by the multiplexers. However, if we consider a use case of many routing
> protocols sharing the MANET, then we must have unified multiplexer using
> that allocated  port as 5498 state for routing.
>
> RFC5498 can have an update to add another port with same ip number for
> other purposes that mentions multiplexers use.
>
> AB
>
>
>
>>
>
>
>>
>>
>>
>>
>>
>>
>>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--001a113340cae4fbb20502982dd0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>I think that some of us are missing the forest w=
hile looking at the trees. The reasons for RFC5498 multiplexing requirement=
 IS important and we should just go opening up/asking for new ports.=C2=A0 =
One of the reasons it&#39;s there is that so multiple different MANET proto=
cols can work with each other with minimal issues.=C2=A0 We do this already=
 with NHDP and OLSRv2 and NHDP and SMF TLV extensions and it&#39;s a very g=
ood thing.=C2=A0 <br><br></div>The root of the issue is assigning semantics=
 to the order of the addresses which AODVv2 currently does and in doing so =
breaks multiplexer implementations (mine included) the work around of throw=
ing out the multiplexer to get around this is wrongheaded as there are also=
 very good reasons (one of which Henning pointed out, future proofing by co=
ntaining information within tlvs and not by position); Other reasons includ=
e, multiplexer reuse which enables both multi-protocol packaging (fewer pac=
kets), code reuse (minor), packet compression in the address blocks (potent=
ial large gain), and packet compression in the TLV space (also potential la=
rge gain).=C2=A0 <br><br>We (read MANET wg) came up with these requirements=
 for very specific reasons and at this point I see no reason let alone any =
compelling reason to ignore or work around them.=C2=A0 If AODVv2 can get th=
is right and abide by the MANET design requirements it will in fact be a be=
tter protocol for it; these aren&#39;t trivial meaningless requirements.<br=
><br></div>Justin<br></div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Mon, Sep 8, 2014 at 9:36 PM, Abdussalam Baryun <span dir=3D"lt=
r">&lt;<a href=3D"mailto:abdussalambaryun@gmail.com" target=3D"_blank">abdu=
ssalambaryun@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Just my last comment in this ticket.=C2=A0<span class=3D""><br><br>On M=
onday, September 8, 2014, Christopher Dearlove  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Really, I&#39;m not wading through all that, as it becomes ap=
parent early on that it misses the whole point.<br>
- 5444 defines a packet/message format,<br>
- 5444 defines how that can be used by a multiplexer. Yes, at this point th=
at&#39;s optional.<br>
- 5498 makes use of that multiplexing approach mandatory on the manet proto=
col/port.<br><br></blockquote><div>=C2=A0</div></span><div>5498 does not sp=
ecify for information-multiplexers but it specifies for routing-protocols. =
Those allocations are owned by the routing protocols not by the multiplexer=
s. However, if we consider a use case of many routing protocols sharing the=
 MANET, then=C2=A0we must have unified multiplexer using that=C2=A0allocate=
d=C2=A0=C2=A0port as 5498 state for routing.=C2=A0</div><div><br></div><div=
>RFC5498 can have an update to add=C2=A0another port with same ip number fo=
r other purposes that mentions multiplexers use.=C2=A0</div><div><br></div>=
<div>AB</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
></blockquote><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><br>=C2=A0<br>=C2=A0<br><br>=C2=A0<br>
<br>
</blockquote>
<br>_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>

--001a113340cae4fbb20502982dd0--


From nobody Mon Sep  8 21:33:55 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 509081A0351 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 21:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A-ZTRW6zz0oO for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 21:33:51 -0700 (PDT)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1269A1A02F3 for <manet@ietf.org>; Mon,  8 Sep 2014 21:33:50 -0700 (PDT)
Received: by mail-qg0-f50.google.com with SMTP id z60so1355589qgd.23 for <manet@ietf.org>; Mon, 08 Sep 2014 21:33:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1xU73iiG2Jmo9DBz1G3xS4rqJtLz1Hlauiryw5ADHrc=; b=NNneQtDAovhArngpmhMareQi51okr/8hsL6J0B6szOSJuMC7PwuOpFEdp6/rWw6t01 9bEOJrNcBq5bKAwASvbIxubcmi4rbgUA/eMLGmCcOgnV0sqVHMDPbQgRhoxe+wznAkQM Smxrr80wKpwwRGJxGhzhm8/O1QgQj9Li49ZTn/YwC0qgpw6vsGA+76jLochMAu9lyYwW Xt2oY38D1kEvfRYYvZWttYBatIIUN8HVnGIHeceHQTPrjHTN0TLETeUHGirVRzQ1M9AS waN39ZhNNMDpWT2bR0SOyXGgnCKB8IC6dwWF8yCi/uBy/56zUlmaDt1suRGda1C7jmvj WnnA==
X-Received: by 10.224.114.74 with SMTP id d10mr47240105qaq.33.1410237229767; Mon, 08 Sep 2014 21:33:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Mon, 8 Sep 2014 21:33:29 -0700 (PDT)
In-Reply-To: <540E1D3E.9050703@earthlink.net>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 9 Sep 2014 06:33:29 +0200
Message-ID: <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com>
To: Charlie Perkins <charles.perkins@earthlink.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/Cz5MzRFhqlAvPVCHFdUfk7YV9s0
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 04:33:52 -0000

On Mon, Sep 8, 2014 at 11:18 PM, Charlie Perkins
<charles.perkins@earthlink.net> wrote:
> Hello Chris,
>
> AODVv2 needs the functionality because it relies on
> reverse path forwarding.

So you would say AODVv2 cannot work without the IP-TTL=255 setting? I
would disagree. IP-TTL=1 and/or a linklocal multicast address work
similarly.

I think the IP-TTL=255 is an optional "security feature" on RFC5444
packet level, trying to make it harder for computers more than one hop
away to deliver an IP packet (not impossible, there might be tricks
with IPIP tunnels that work). If this is true, it might fit into a
'security considerations' section or the document, or even better put
into a "RFC5444 packet security" draft" of its own, that describes
best practices and possible options how to handle the packet output of
the multiplexer for all protocols using RFC5444.

Henning Rogge


From nobody Mon Sep  8 22:52:49 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB3D1A0921 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 22:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JHKfaGDpNCP6 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 22:52:46 -0700 (PDT)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 280191A093B for <manet@ietf.org>; Mon,  8 Sep 2014 22:52:46 -0700 (PDT)
Received: by mail-qg0-f47.google.com with SMTP id i50so2352491qgf.20 for <manet@ietf.org>; Mon, 08 Sep 2014 22:52:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fo7D6uQ0X0pXUXM7FNkRtMDMJf2aMwZML6QzItJZIbg=; b=IAuu+z2Utfgr5yqlgpJTeT6ZYDpPvcbBOVcsBB8S0gOPiDBsklVONf6m6IcLd2pyVN Qb4/aQNCMcdKqp7NSFCGFdHz4S7rS6ZCTVFgDZImlU79D6NbcU55lHB52df3A1OIAYtD 7vmVGLDprwJA4sbRhTcPCoBRNHIWptvISuZgfGXc8Gcg47Ggf+OWkZoahmFiNpSpjmxF Qy/EKxMDDNqeEQcjXXRQwKOwme2MQqFFQRQLdd3uieZBqj9CZx1O6Gcbq4ePnNIbgAHf jURAK2celXBzKQQaV+GRjNFo9kBLq5XQ6MpmDEikPsLgZcPB1McO5SVNu5rWiKxp3WoG kBEg==
X-Received: by 10.140.94.1 with SMTP id f1mr20271606qge.41.1410241964217; Mon, 08 Sep 2014 22:52:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Mon, 8 Sep 2014 22:52:24 -0700 (PDT)
In-Reply-To: <540E9302.5060506@earthlink.net>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 9 Sep 2014 07:52:24 +0200
Message-ID: <CAGnRvupW4vq9Uo74i_x_ujVpj7h-3o9sMTiJFsyaKZ4GRBq-AA@mail.gmail.com>
To: Charlie Perkins <charles.perkins@earthlink.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/rCIs2dvaLWxibEFa0Vd5EsJO-uM
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 05:52:47 -0000

On Tue, Sep 9, 2014 at 7:41 AM, Charlie Perkins
<charles.perkins@earthlink.net> wrote:
>
> Hello Henning,
>
> I didn't say it could not work without TTL=255.

Good.

(skipping the rest of the paragraph)

> However, I think it is pretty bad when a message bundling system
> imposes these collateral constraints.  I reckon it was another
> unintended consequence.

requiring a certain IP-TTL is a constraint too.

> There's nothing wrong with attempting to use multiple security
> measures.  As far as I know, it's usually considered praiseworthy.

Its a BAD thing to make one weak security option mandatory as part of
the core protocol.

I don't see any real advantage of this TTL-magic, other then preparing
for a mesh node malfunctioning. Its strange on IPv4 and its even silly
on IPv6 where we have recognizable linklocal multicast addresses (the
LL_MANET multicast address is one of them). If you expect your
neighbor mesh nodes forwarding linklocal multicast traffic you have
other problems than looking at the TTL field.

Either put it into the "security considerations" as one option to do
it or write (as most other protocols of this WG) a security
considerations draft, either on protocol level or on RFC5444 packet
level.

Henning Rogge


From nobody Mon Sep  8 22:56:46 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAD3A1A0A92 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 22:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6WyUVh2mYE5L for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 22:56:42 -0700 (PDT)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C47B1A0970 for <manet@ietf.org>; Mon,  8 Sep 2014 22:56:42 -0700 (PDT)
Received: by mail-qg0-f53.google.com with SMTP id z107so16211843qgd.26 for <manet@ietf.org>; Mon, 08 Sep 2014 22:56:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1pGeqLOrnnEJ4TccnLN7Rv+jPFAIUD1rwUPp//Zl31c=; b=KHN4bISqREjRAIRWnesVp6b5BTx1CPogIGOB0RpjB2wWGJ4JITR8YwQrfXvkaXsM2Z eacRHMFP+zOEY5a8SeR+Bj+PFV9hBpAMJZ/upq9Rz/uOx2aiKTqPLun1akzimOBa+oYy iR69D0SPoRPTf97Qkuhmue6G3wMXnmPMGkoGd8fMSwA8zw5tlOqS1cZAdp4IKNKkH9NU aZNcsrWOJxtYG/CnPCYiHXSgCiPf6ZRwojc3ZaRGm84l4q578k6wtPrY3QUbkUQKqitC Qvjqh1LuFg0lTf5ZTGTLIZM6j69C/ruP2kS2pn8zuLxvDHDuXhwc6Y8lRYS1TcQLdvDo HxTg==
X-Received: by 10.224.162.196 with SMTP id w4mr47328647qax.60.1410242201616; Mon, 08 Sep 2014 22:56:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Mon, 8 Sep 2014 22:56:21 -0700 (PDT)
In-Reply-To: <CADnDZ89-c61ViZ3xWb6GUKur4bV2djca-jovrsx9G-4+sB_VkQ@mail.gmail.com>
References: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org> <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com> <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com> <A5DD62E7-82EC-4ACF-8A71-A9ADF81827A8@gmail.com> <CADnDZ89-c61ViZ3xWb6GUKur4bV2djca-jovrsx9G-4+sB_VkQ@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 9 Sep 2014 07:56:21 +0200
Message-ID: <CAGnRvurv43p=XPMW+UZerUCwd+o351jeUE7k22G8KCXCiifdCw@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/hxlfheJKGqrLMngwGUqPBw37t8I
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 05:56:44 -0000

On Tue, Sep 9, 2014 at 3:15 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
>> 5498 says (as part of its using of the MANET protocol or port) you must
>> use that multiplexing method.
>
> And if using many routing protocols in same network yes you must use unified parser (to
> reduce overheads).

Every OLSRv2 implementation out there is doing this anyways because
they have to combine the OLSRv2 protocol with the NHDP protocol.

Every SMF implementation that use a reduced flooding set by using MPRs
is doing this too (hint, its because of a second protocol called
NHDP).

Oh, using AODVv2 with proactive neighbor detection might make this
"two protocols" necessary too.

And my "NHDP dualstack" draft suggests doing it with multiple protocol
instances, one for IPv4 and one for IPv4.

You notice a pattern?

Henning Rogge


From nobody Mon Sep  8 23:00:27 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7B361A0AE4 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 23:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tEa7t_hKgxSu for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 23:00:21 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 0A2FB1A0ADD for <manet@ietf.org>; Mon,  8 Sep 2014 23:00:20 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=nZleVQvJsRYS6cuIiGCMp9NAtRywCdfzMEpt0M3ES6qUsGhLiaLhuFkJtEi2D0BZ; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.80]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XREBA-0001ue-H8; Tue, 09 Sep 2014 01:41:24 -0400
Message-ID: <540E9302.5060506@earthlink.net>
Date: Mon, 08 Sep 2014 22:41:22 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Henning Rogge <hrogge@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com>
In-Reply-To: <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac787fe42d47da841011435ff8e57213bf9350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/TfDwgiCQuDjll3x_R4rD1cZsRwg
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 06:00:24 -0000

Hello Henning,

I didn't say it could not work without TTL=255.  Of course it can.
It could work if there is a constraint that the number of bytes in
any message must be a factor of 7.  It could work if there is a constraint
that there must be no more than 295 bits set to a value of '1'.

However, I think it is pretty bad when a message bundling system
imposes these collateral constraints.  I reckon it was another
unintended consequence.

There's nothing wrong with attempting to use multiple security
measures.  As far as I know, it's usually considered praiseworthy.

Regards,
Charlie P.


On 9/8/2014 9:33 PM, Henning Rogge wrote:
> On Mon, Sep 8, 2014 at 11:18 PM, Charlie Perkins
> <charles.perkins@earthlink.net> wrote:
>> Hello Chris,
>>
>> AODVv2 needs the functionality because it relies on
>> reverse path forwarding.
> So you would say AODVv2 cannot work without the IP-TTL=255 setting? I
> would disagree. IP-TTL=1 and/or a linklocal multicast address work
> similarly.
>
> I think the IP-TTL=255 is an optional "security feature" on RFC5444
> packet level, trying to make it harder for computers more than one hop
> away to deliver an IP packet (not impossible, there might be tricks
> with IPIP tunnels that work). If this is true, it might fit into a
> 'security considerations' section or the document, or even better put
> into a "RFC5444 packet security" draft" of its own, that describes
> best practices and possible options how to handle the packet output of
> the multiplexer for all protocols using RFC5444.
>
> Henning Rogge
>


From nobody Mon Sep  8 23:29:58 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE6371A0AF2 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 23:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pWFZ0KyCWm5 for <manet@ietfa.amsl.com>; Mon,  8 Sep 2014 23:29:56 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 354CB1A0AEF for <manet@ietf.org>; Mon,  8 Sep 2014 23:29:56 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id u56so2465826wes.10 for <manet@ietf.org>; Mon, 08 Sep 2014 23:29:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=fxwTZ7SvHywUAr249lUfkxxleYe+ft306h+ZSpjKXm4=; b=ot9sXLf/KlRZFZlk3JYJbkNnR9S+na0P5tlP5mXudAvq9asxLEIYDowXDITV9grkMI A7sN7QN+Doz0JXZs0J6gDb7MBbhrxIZmdIgXl5QPyP0p0l1MUuthS+CFPof6WO2UCwm1 uHztqk9veXtkfyvvckcxrdF/gHpc/TdXgPBFd/yZqbBhNYmdYZaDMAs2dPvNWy35sUdi 3nvzYLsrCsTm/hOddVK78b1yCM1llDd9wSD6syqEMOHAFzidbkqvNg+msQEJ6REuFMhi NB4PPPpzFUOEbLbgLVzNxi7h768Psgx6rys7Kna1NDc4V2lYxp/b1GXtldNR8j4JOQDK izag==
X-Received: by 10.180.102.130 with SMTP id fo2mr28142878wib.29.1410244194880;  Mon, 08 Sep 2014 23:29:54 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id s7sm13584114wjo.48.2014.09.08.23.29.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Sep 2014 23:29:53 -0700 (PDT)
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <540E9302.5060506@earthlink.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Tue, 9 Sep 2014 07:29:51 +0100
To: Charlie Perkins <charles.perkins@earthlink.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/k31yVBRmj8-a2cDWWz4_XYXLS18
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 06:29:57 -0000

And no one has said its a bad idea to use 5082 (though it's not the only opt=
ion). Just that it's a 5444 multiplexer level decision, not an AODVv2 level d=
ecision.

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 9 Sep 2014, at 06:41, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
>=20
> Hello Henning,
>=20
> I didn't say it could not work without TTL=3D255.  Of course it can.
> It could work if there is a constraint that the number of bytes in
> any message must be a factor of 7.  It could work if there is a constraint=

> that there must be no more than 295 bits set to a value of '1'.
>=20
> However, I think it is pretty bad when a message bundling system
> imposes these collateral constraints.  I reckon it was another
> unintended consequence.
>=20
> There's nothing wrong with attempting to use multiple security
> measures.  As far as I know, it's usually considered praiseworthy.
>=20
> Regards,
> Charlie P.
>=20
>=20
>> On 9/8/2014 9:33 PM, Henning Rogge wrote:
>> On Mon, Sep 8, 2014 at 11:18 PM, Charlie Perkins
>> <charles.perkins@earthlink.net> wrote:
>>> Hello Chris,
>>>=20
>>> AODVv2 needs the functionality because it relies on
>>> reverse path forwarding.
>> So you would say AODVv2 cannot work without the IP-TTL=3D255 setting? I
>> would disagree. IP-TTL=3D1 and/or a linklocal multicast address work
>> similarly.
>>=20
>> I think the IP-TTL=3D255 is an optional "security feature" on RFC5444
>> packet level, trying to make it harder for computers more than one hop
>> away to deliver an IP packet (not impossible, there might be tricks
>> with IPIP tunnels that work). If this is true, it might fit into a
>> 'security considerations' section or the document, or even better put
>> into a "RFC5444 packet security" draft" of its own, that describes
>> best practices and possible options how to handle the packet output of
>> the multiplexer for all protocols using RFC5444.
>>=20
>> Henning Rogge
>=20


From nobody Tue Sep  9 07:36:39 2014
Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93F361A6F9D for <manet@ietfa.amsl.com>; Tue,  9 Sep 2014 07:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.152
X-Spam-Level: 
X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mqg5BvhDjGNj for <manet@ietfa.amsl.com>; Tue,  9 Sep 2014 07:36:36 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEC921A6F9C for <manet@ietf.org>; Tue,  9 Sep 2014 07:36:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5992; q=dns/txt; s=iport; t=1410273396; x=1411482996; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/Bglp5+MbL9L1UE0MSEbAargQnQWRamuE+op8+uaDKc=; b=e8BMs59Zce1T7bA0LYTo0ez9PzP3ZbZogerrR1kEus+nhj5u5HIzxhHs 2xQVdg+gy/F/7oEbSeWvj8PhOVuPf0pZVg0m7VMUPQFEnjKBOr+1/ikcr UotYD7qk2gISLczA73Eg7M3FZ5GvkOCgB3dOL1Ei+pqcUiikxt5VqPRcu s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiQFAA4QD1StJV2Z/2dsb2JhbABZgw2BKgTRcwGBDRZ4hAQBAQR5EAIBCD8HIREUEQIEDgWILgMRtXQNhl0BF4wegQKCLQeDL4EdBZFBiSKCEI5zhjuDYWyBSIEHAQEB
X-IronPort-AV: E=Sophos; i="5.04,491,1406592000"; d="scan'208,217"; a="76304780"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-5.cisco.com with ESMTP; 09 Sep 2014 14:36:35 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s89EaZ62023458 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Sep 2014 14:36:35 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0195.001; Tue, 9 Sep 2014 09:36:34 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: [manet] #33 (aodvv2): RFC 5444 processing constraint
Thread-Index: AQHPytlg/Co7QO4hukqKH7t4FFH2D5v2d70AgAHYrICAAOScgA==
Date: Tue, 9 Sep 2014 14:36:33 +0000
Message-ID: <ECF39819-7223-4407-8462-E6E68BEA41F7@cisco.com>
References: <061.a5ce40aa1d210c527317773533e6c828@trac.tools.ietf.org> <CADnDZ89PxvSRzU3P1L4fLuSFxFjFby2NLrt2w52eW9uV4xCcnw@mail.gmail.com> <199428A6-26FB-4451-83F9-66E90B3EA287@cisco.com> <CADnDZ8_xaaBT8D_5w-Z99SEOQ=2JFTRKnHOpES576g-CRppVXg@mail.gmail.com>
In-Reply-To: <CADnDZ8_xaaBT8D_5w-Z99SEOQ=2JFTRKnHOpES576g-CRppVXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.102.40.190]
Content-Type: multipart/alternative; boundary="_000_ECF39819722344078462E6E68BEA41F7ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/_P4LJQAOdZO1rebQbiBfaJub1rI
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 14:36:37 -0000

--_000_ECF39819722344078462E6E68BEA41F7ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


On Sep 8, 2014, at 8:58 PM, Abdussalam Baryun <abdussalambaryun@gmail.com<m=
ailto:abdussalambaryun@gmail.com>> wrote:

Disregard does not mean drop, so those messages are still in next 5444 pack=
et. This comes back to multiplexing by ownership or not, which that is not =
specified yet so we leave it for another future draft for multiplexing. We =
need to focus this reactive standard not make it complicated.

Again, I respectfully disagree. A deployment model to envision is a router,=
 running both OLSRv2 and AODVv2. Both of those protocols share a transport =
using RFC5444 to a second router, which is also running both protocols. The=
 "multiplexing" being spoken of would be a mix of OLSRv2 and AODVv2 message=
s, bundled up into an RFC5444 packet.

Ok, to be more general and to serve majority users of AODVv2 and more secur=
ity consideration.  we need to consider that some users don't want such mix=
 network and some do. First if users are wanting your mix scenario then the=
y go for a parser that is unified for both protocols ( this case routers ne=
ed same multiplexing method otherwise they don't work ), while parsers are =
independent of protocols as RFC5444 says. If the AODVv2 sends a packet then=
 parser is able to do packing again locally with adding other messages if a=
vailable. Secondly,  users don't want to use specific unified parser depend=
ence, so just the one protocol packing with its user method for security pu=
rpose. This way we have more independence for this AODVv2.


If a given protocol specification/design adheres to the RFC 5444 multiplexi=
ng as it should, then both of your scenarios above (e.g., "=85some users do=
n't want such mix network and some do.") work just fine. However, if a give=
n protocol specification does NOT adhere to the RFC 5444 multiplexing, it t=
hen PRECLUDES the protocol from being used in what you are calling a "mixed=
 network". In summary, adherence to the RFC 5444 multiplexing gives deploym=
ents MORE flexibility instead of less, and is, IMHO, the superior design ch=
oice.  As for your assertion that "=85users don't want to use specific unif=
ied parser dependence=85", I believe that is at best merely anecdotal, and =
at worst, completely baseless.

Regards,
Stan

--_000_ECF39819722344078462E6E68BEA41F7ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <58D0934C4B6C334F99C0DF1B2EF2232E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<br>
<div>
<div>On Sep 8, 2014, at 8:58 PM, Abdussalam Baryun &lt;<a href=3D"mailto:ab=
dussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; borde=
r-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style=
: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div style=3D"word-wrap:break-word">
<blockquote type=3D"cite">
<div><br>
</div>
<div>Disregard does not mean drop, so those messages are still in next&nbsp=
;5444&nbsp;packet.&nbsp;This comes back to multiplexing by ownership or not=
, which that is not specified yet so&nbsp;we leave it for another future&nb=
sp;draft for multiplexing. We need to focus this reactive
 standard not make it complicated.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>Again, I respectfully disagree. A deployment model to envision is a ro=
uter, running both OLSRv2 and AODVv2. Both of those protocols share a trans=
port using RFC5444 to a second router, which is also running both protocols=
. The &quot;multiplexing&quot; being spoken
 of would be a mix of OLSRv2 and AODVv2 messages, bundled up into an RFC544=
4 packet.&nbsp;</div>
</div>
</blockquote>
<div><br>
</div>
<div>Ok, to be more general and to serve majority&nbsp;users of AODVv2 and =
more security consideration.&nbsp;&nbsp;we need to consider that some users=
 don't want such mix network and some do. First if users are wanting your&n=
bsp;mix scenario then they go for a parser that is unified
 for both protocols (&nbsp;this case&nbsp;routers need same multiplexing me=
thod otherwise they don't work ),&nbsp;while parsers are independent of pro=
tocols as RFC5444 says. If the AODVv2 sends a packet then parser is able to=
 do packing again locally&nbsp;with adding other messages
 if available.&nbsp;Secondly, &nbsp;users don't want to use specific unifie=
d&nbsp;parser dependence,&nbsp;so&nbsp;just the one&nbsp;protocol packing w=
ith its user method for security purpose.&nbsp;This way we have more indepe=
ndence for this AODVv2.&nbsp;</div>
<div><br>
</div>
</blockquote>
<br>
</div>
<div>If a given protocol specification/design adheres to the RFC 5444 multi=
plexing as it should, then both of your scenarios above (e.g., &quot;=85som=
e users don't want such mix network and some do.&quot;) work just fine. How=
ever, if a given protocol specification does
 NOT adhere to the RFC 5444 multiplexing, it then PRECLUDES the protocol fr=
om being used in what you are calling a &quot;mixed network&quot;. In summa=
ry, adherence to the RFC 5444 multiplexing gives deployments MORE flexibili=
ty instead of less, and is, IMHO, the superior
 design choice. &nbsp;As for your assertion that &quot;=85users don't want =
to use specific unified parser dependence=85&quot;, I believe that is at be=
st merely anecdotal, and at worst, completely baseless.&nbsp;</div>
<div><br>
</div>
<div>Regards,</div>
<div>Stan</div>
</body>
</html>

--_000_ECF39819722344078462E6E68BEA41F7ciscocom_--


From nobody Tue Sep  9 12:10:57 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1481A0137 for <manet@ietfa.amsl.com>; Tue,  9 Sep 2014 12:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzMju7GzRTuB for <manet@ietfa.amsl.com>; Tue,  9 Sep 2014 12:10:40 -0700 (PDT)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F18FE1A0126 for <manet@ietf.org>; Tue,  9 Sep 2014 12:10:39 -0700 (PDT)
Received: by mail-yk0-f180.google.com with SMTP id q9so2366325ykb.11 for <manet@ietf.org>; Tue, 09 Sep 2014 12:10:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=3y+MCHSyufAreZAvslD7XHe4lUc0yRH9QUa7tQdKXwQ=; b=wENeZU8hpUqUegY70GfyoTYgpmwAxODrZb8ZBhj8R5nPqcRh0cnP2H9ZsOCauaQ83Y dSv76BVEGszlpbmqMVtzlte0eocL7LIb5R5NeKB4GNxWxoHeEFp9jek3TL91WoijsFx7 KfddTTQMsmdLnq0LvkmjxNv9P+eCzZ5eDdh40/5Y8SxmAemVb0/ZFB9OQcJCkznWhi9+ Meg/a2OY2rfluFk5NeDMTwy/+ihj5hDb70Mq37BgzzxMvK/YciXIubjdIZuIIpvnIL+I GBECot/779G34wDFYS3CQQJSIMQQ0vJMTjhHCkGy1gWF+xTB00eUW/6LxHGEMAf1Y4CL w7Eg==
MIME-Version: 1.0
X-Received: by 10.236.168.198 with SMTP id k46mr29645559yhl.54.1410289839122;  Tue, 09 Sep 2014 12:10:39 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Tue, 9 Sep 2014 12:10:39 -0700 (PDT)
Date: Tue, 9 Sep 2014 21:10:39 +0200
Message-ID: <CADnDZ8_5ZgESoBFAFLh-4oZG118XxeomnJpVRWq0tkBT86EbQw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
Content-Type: multipart/alternative; boundary=20cf3040e4a8e430f70502a6b0fc
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/qZQy66o_HWRwbQeprGoZzJvkoXs
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: [manet] RFC5444 packets for routing protocols (was Re: #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 19:10:43 -0000

--20cf3040e4a8e430f70502a6b0fc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think your understanding will not give opportunity for
future protocols to use its own packets or to use the 5444-packet with zero
messages (as RFC5444 defined this zero message possibility). Protocols
extensions may use exchange of 5444-packet with zero message, but if you
leave packets for only parsers then this limits the use of RFC5444 by
protocols, so they only define 5444-messages.

Comments below,

On Tuesday, September 9, 2014, Stan Ratliff (sratliff) wrote:

>
>  On Sep 8, 2014, at 8:58 PM, Abdussalam Baryun <abdussalambaryun@gmail.co=
m
> <javascript:_e(%7B%7D,'cvml','abdussalambaryun@gmail.com');>> wrote:
>
>
>>  Disregard does not mean drop, so those messages are still in
>> next 5444 packet. This comes back to multiplexing by ownership or not,
>> which that is not specified yet so we leave it for another future draft =
for
>> multiplexing. We need to focus this reactive standard not make it
>> complicated.
>>
>>
>>  Again, I respectfully disagree. A deployment model to envision is a
>> router, running both OLSRv2 and AODVv2. Both of those protocols share a
>> transport using RFC5444 to a second router, which is also running both
>> protocols. The "multiplexing" being spoken of would be a mix of OLSRv2 a=
nd
>> AODVv2 messages, bundled up into an RFC5444 packet.
>>
>
>  Ok, to be more general and to serve majority users of AODVv2 and more
> security consideration.  we need to consider that some users don't want
> such mix network and some do. First if users are wanting your mix scenari=
o
> then they go for a parser that is unified for both protocols ( this
> case routers need same multiplexing method otherwise they don't work
> ), while parsers are independent of protocols as RFC5444 says. If the
> AODVv2 sends a packet then parser is able to do packing again locally wit=
h
> adding other messages if available. Secondly,  users don't want to use
> specific unified parser dependence, so just the one protocol packing with
> its user method for security purpose. This way we have more independence
> for this AODVv2.
>
>
>  If a given protocol specification/design adheres to the RFC 5444
> multiplexing as it should, then both of your scenarios above (e.g., "=E2=
=80=A6some
> users don't want such mix network and some do.") work just fine.
>

But that limits the routing protocols use of 5444-packet as never they
should create packets. They will depend on parsers (even if one protocol is
running alone in the MANET) which can increase delays and maybe less QoS.
Designs need to be simple and the protocol packets are defined by protocols
not parsers.


> However, if a given protocol specification does NOT adhere to the RFC 544=
4
> multiplexing, it then PRECLUDES the protocol from being used in what you
> are calling a "mixed network".
>

No still we can use it in the mix, because the parser will understand
5444-packets. RFC5444 is for the protocol to define its packets not the
parser.

In summary, adherence to the RFC 5444 multiplexing gives deployments MORE
> flexibility instead of less, and is, IMHO, the superior design choice.  A=
s
> for your assertion that "=E2=80=A6users don't want to use specific unifie=
d parser
> dependenc=E2=80=A6", I believe that is at best merely anecdotal, and at w=
orst,
> completely baseless.
>

I think the use of RFC7181 is not flexible for users, because it depends on
the unified parser's packets, if parser fails/attacked then OLSRv2 fails.
IMHO, in future still 7181 will have more updates, which we had seen many
in short time.

AB

--20cf3040e4a8e430f70502a6b0fc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think your understanding will not give opportunity for future=C2=A0protoc=
ols=C2=A0to use its own packets or to use=C2=A0the 5444-packet with zero me=
ssages (as RFC5444 defined this zero message=C2=A0possibility). Protocols e=
xtensions may use exchange of 5444-packet with zero message, but if you lea=
ve packets for only=C2=A0parsers then this limits the use of RFC5444 by pro=
tocols, so they only define 5444-messages.=C2=A0<div><br></div><div>Comment=
s below,</div><div><br>On Tuesday, September 9, 2014, Stan Ratliff (sratlif=
f)  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
<br>
<div>
<div>On Sep 8, 2014, at 8:58 PM, Abdussalam Baryun &lt;<a href=3D"javascrip=
t:_e(%7B%7D,&#39;cvml&#39;,&#39;abdussalambaryun@gmail.com&#39;);" target=
=3D"_blank">abdussalambaryun@gmail.com</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<div style=3D"word-wrap:break-word">
<blockquote type=3D"cite">
<div><br>
</div>
<div>Disregard does not mean drop, so those messages are still in next=C2=
=A05444=C2=A0packet.=C2=A0This comes back to multiplexing by ownership or n=
ot, which that is not specified yet so=C2=A0we leave it for another future=
=C2=A0draft for multiplexing. We need to focus this reactive
 standard not make it complicated.=C2=A0</div>
</blockquote>
<div><br>
</div>
<div>Again, I respectfully disagree. A deployment model to envision is a ro=
uter, running both OLSRv2 and AODVv2. Both of those protocols share a trans=
port using RFC5444 to a second router, which is also running both protocols=
. The &quot;multiplexing&quot; being spoken
 of would be a mix of OLSRv2 and AODVv2 messages, bundled up into an RFC544=
4 packet.=C2=A0</div>
</div>
</blockquote>
<div><br>
</div>
<div>Ok, to be more general and to serve majority=C2=A0users of AODVv2 and =
more security consideration.=C2=A0=C2=A0we need to consider that some users=
 don&#39;t want such mix network and some do. First if users are wanting yo=
ur=C2=A0mix scenario then they go for a parser that is unified
 for both protocols (=C2=A0this case=C2=A0routers need same multiplexing me=
thod otherwise they don&#39;t work ),=C2=A0while parsers are independent of=
 protocols as RFC5444 says. If the AODVv2 sends a packet then parser is abl=
e to do packing again locally=C2=A0with adding other messages
 if available.=C2=A0Secondly, =C2=A0users don&#39;t want to use specific un=
ified=C2=A0parser dependence,=C2=A0so=C2=A0just the one=C2=A0protocol packi=
ng with its user method for security purpose.=C2=A0This way we have more in=
dependence for this AODVv2.=C2=A0</div>
<div><br>
</div>
</blockquote>
<br>
</div>
<div>If a given protocol specification/design adheres to the RFC 5444 multi=
plexing as it should, then both of your scenarios above (e.g., &quot;=E2=80=
=A6some users don&#39;t want such mix network and some do.&quot;) work just=
 fine.=C2=A0</div><div></div></div></blockquote><div><br></div><div>But tha=
t limits the routing=C2=A0protocols use of 5444-packet as never they should=
 create packets. They will depend on parsers (even if one protocol is runni=
ng alone in the MANET)=C2=A0which can increase delays and maybe less=C2=A0Q=
oS. Designs need to be simple and the protocol packets are defined by proto=
cols not parsers.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div style=3D"word-wrap:break-word"><div>However, if a given protocol spe=
cification does
 NOT adhere to the RFC 5444 multiplexing, it then PRECLUDES the protocol fr=
om being used in what you are calling a &quot;mixed network&quot;.=C2=A0</d=
iv></div></blockquote><div><br></div><div>No still we can use it in the mix=
, because the parser will understand 5444-packets.=C2=A0RFC5444 is for the =
protocol to define its packets not the parser.=C2=A0</div><div><br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>In su=
mmary, adherence to the RFC 5444 multiplexing gives deployments MORE flexib=
ility instead of less, and is, IMHO, the superior
 design choice. =C2=A0As for your assertion that &quot;=E2=80=A6users don&#=
39;t want to use specific unified parser dependenc=E2=80=A6&quot;, I believ=
e that is at best merely anecdotal, and at worst, completely baseless.=C2=
=A0</div></div></blockquote><div><br></div><div>I think the use of RFC7181 =
is not flexible for users,=C2=A0because it depends on the unified=C2=A0pars=
er&#39;s=C2=A0packets, if=C2=A0parser fails/attacked=C2=A0then OLSRv2 fails=
. IMHO, in=C2=A0future still 7181 will have more updates, which we had=C2=
=A0seen many in short time.=C2=A0</div><div><br></div><div>AB=C2=A0</div></=
div>

--20cf3040e4a8e430f70502a6b0fc--


From nobody Tue Sep  9 12:43:21 2014
Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15B7E1A0100 for <manet@ietfa.amsl.com>; Tue,  9 Sep 2014 12:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.152
X-Spam-Level: 
X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ebbFYHnF5Xzc for <manet@ietfa.amsl.com>; Tue,  9 Sep 2014 12:43:17 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9F051A01DD for <manet@ietf.org>; Tue,  9 Sep 2014 12:43:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12340; q=dns/txt; s=iport; t=1410291798; x=1411501398; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=fkn38wfNN+XDf/ggrqC9hllvtFU5TyAqaeqUBV4IoA8=; b=Gs7Y8R0LPmR2QHKjhcd01DbBssQrgRhLae+bk0qhvQihEF3qGEbQB+DC VvS+L0DB5ANfc2x6kK5M1wMnroI7kxfnN69vz2ddQ/U4T3bzfHJeP8hmP Gl2kzesKF6LwITUFIadQhxfJ6C3LMJCCE7y2hoXewv1h1qchtvWGh74o9 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUFABVYD1StJA2E/2dsb2JhbABZgw2BKgTRcgGBDRZ4hAQBAQR5EAIBCBIpBAchERQDDgIEDgWILgMRtj8Nhl0BFAMGjBiBAoFLEQFQB4MvgR0FkUGJIoIQjnOGO4IbgUZsgQ85gQcBAQE
X-IronPort-AV: E=Sophos;i="5.04,492,1406592000";  d="scan'208,217";a="353942944"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-4.cisco.com with ESMTP; 09 Sep 2014 19:43:01 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s89JgxDR018024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Sep 2014 19:42:59 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Tue, 9 Sep 2014 14:42:59 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: RFC5444 packets for routing protocols (was Re: [manet] #33 (aodvv2): RFC 5444 processing constraint
Thread-Index: AQHPzGG/QUV9nW7S40eLoHWlN5ZS+Zv5h5EA
Date: Tue, 9 Sep 2014 19:42:59 +0000
Message-ID: <9760F05C-41FF-4009-B1BF-9FF950B43F8B@cisco.com>
References: <CADnDZ8_5ZgESoBFAFLh-4oZG118XxeomnJpVRWq0tkBT86EbQw@mail.gmail.com>
In-Reply-To: <CADnDZ8_5ZgESoBFAFLh-4oZG118XxeomnJpVRWq0tkBT86EbQw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.102.40.190]
Content-Type: multipart/alternative; boundary="_000_9760F05C41FF4009B1BF9FF950B43F8Bciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ruCwZEi_enGflYoCt6T7HZ_wm00
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] RFC5444 packets for routing protocols (was Re: #33 (aodvv2): RFC 5444 processing constraint
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 19:43:19 -0000

--_000_9760F05C41FF4009B1BF9FF950B43F8Bciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


On Sep 9, 2014, at 3:10 PM, Abdussalam Baryun <abdussalambaryun@gmail.com<m=
ailto:abdussalambaryun@gmail.com>> wrote:

I think your understanding will not give opportunity for future protocols t=
o use its own packets or to use the 5444-packet with zero messages (as RFC5=
444 defined this zero message possibility). Protocols extensions may use ex=
change of 5444-packet with zero message, but if you leave packets for only =
parsers then this limits the use of RFC5444 by protocols, so they only defi=
ne 5444-messages.

Precisely. And that is what is currently mandated by the RFC5498: MANET WG =
developed routing protocols only define RFC5444 messages, NOT RFC5444 packe=
ts. And the rest of the push-back you're getting on the list indicates ther=
e is NO interest whatsoever in re-litigating that decision.


Comments below,

On Tuesday, September 9, 2014, Stan Ratliff (sratliff) wrote:

On Sep 8, 2014, at 8:58 PM, Abdussalam Baryun <abdussalambaryun@gmail.com<j=
avascript:_e(%7B%7D,'cvml','abdussalambaryun@gmail.com');>> wrote:

Disregard does not mean drop, so those messages are still in next 5444 pack=
et. This comes back to multiplexing by ownership or not, which that is not =
specified yet so we leave it for another future draft for multiplexing. We =
need to focus this reactive standard not make it complicated.

Again, I respectfully disagree. A deployment model to envision is a router,=
 running both OLSRv2 and AODVv2. Both of those protocols share a transport =
using RFC5444 to a second router, which is also running both protocols. The=
 "multiplexing" being spoken of would be a mix of OLSRv2 and AODVv2 message=
s, bundled up into an RFC5444 packet.

Ok, to be more general and to serve majority users of AODVv2 and more secur=
ity consideration.  we need to consider that some users don't want such mix=
 network and some do. First if users are wanting your mix scenario then the=
y go for a parser that is unified for both protocols ( this case routers ne=
ed same multiplexing method otherwise they don't work ), while parsers are =
independent of protocols as RFC5444 says. If the AODVv2 sends a packet then=
 parser is able to do packing again locally with adding other messages if a=
vailable. Secondly,  users don't want to use specific unified parser depend=
ence, so just the one protocol packing with its user method for security pu=
rpose. This way we have more independence for this AODVv2.


If a given protocol specification/design adheres to the RFC 5444 multiplexi=
ng as it should, then both of your scenarios above (e.g., "=85some users do=
n't want such mix network and some do.") work just fine.

But that limits the routing protocols use of 5444-packet as never they shou=
ld create packets. They will depend on parsers (even if one protocol is run=
ning alone in the MANET) which can increase delays and maybe less QoS. Desi=
gns need to be simple and the protocol packets are defined by protocols not=
 parsers.

What?!? There is no intersection with RFC5444 and QoS (or there needn't be)=
. RFC5444 serves as formats for the routing protocol only; the data-path (w=
hich is where you would apply QoS) uses standard switching/forwarding techn=
iques.


However, if a given protocol specification does NOT adhere to the RFC 5444 =
multiplexing, it then PRECLUDES the protocol from being used in what you ar=
e calling a "mixed network".

No still we can use it in the mix, because the parser will understand 5444-=
packets. RFC5444 is for the protocol to define its packets not the parser.

No, you can't.


In summary, adherence to the RFC 5444 multiplexing gives deployments MORE f=
lexibility instead of less, and is, IMHO, the superior design choice.  As f=
or your assertion that "=85users don't want to use specific unified parser =
dependenc=85", I believe that is at best merely anecdotal, and at worst, co=
mpletely baseless.

I think the use of RFC7181 is not flexible for users, because it depends on=
 the unified parser's packets, if parser fails/attacked then OLSRv2 fails. =
IMHO, in future still 7181 will have more updates, which we had seen many i=
n short time.

OK. You are free to hold that opinion - as I am free to disagree with it.  =
But again, other than your emails, I see no desire to re-open, re-discuss, =
and re-decide the current architecture of RFC5444 packets/messages/multiple=
xing. And unless (or until) there is wide-spread desire to re-open that deb=
ate, I see no useful purpose in continuing this email thread, because the a=
nswer to all of your opinions/concerns  is "RFC5444 is what it is, and RFC5=
498 is what *it* is."

IMHO, it's time to move on to other discussions.

Stan

--_000_9760F05C41FF4009B1BF9FF950B43F8Bciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <78FAFD5D0D77124FB54E65FC4F8C4812@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<br>
<div>
<div>On Sep 9, 2014, at 3:10 PM, Abdussalam Baryun &lt;<a href=3D"mailto:ab=
dussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">I think your understanding will not give opportun=
ity for future&nbsp;protocols&nbsp;to use its own packets or to use&nbsp;th=
e 5444-packet with zero messages (as RFC5444 defined this zero message&nbsp=
;possibility). Protocols extensions may use exchange of
 5444-packet with zero message, but if you leave packets for only&nbsp;pars=
ers then this limits the use of RFC5444 by protocols, so they only define 5=
444-messages.&nbsp;</blockquote>
<div><br>
</div>
<div>Precisely. And that is what is currently mandated by the RFC5498: MANE=
T WG developed routing protocols only define RFC5444 messages, NOT RFC5444 =
packets. And the rest of the push-back you're getting on the list indicates=
 there is NO interest whatsoever
 in re-litigating that decision.&nbsp;</div>
<br>
<blockquote type=3D"cite">
<div><br>
</div>
<div>Comments below,</div>
<div><br>
On Tuesday, September 9, 2014, Stan Ratliff (sratliff) wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; borde=
r-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style=
: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div style=3D"word-wrap:break-word"><br>
<div>
<div>On Sep 8, 2014, at 8:58 PM, Abdussalam Baryun &lt;<a href=3D"javascrip=
t:_e(%7B%7D,'cvml','abdussalambaryun@gmail.com');" target=3D"_blank">abduss=
alambaryun@gmail.com</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; borde=
r-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style=
: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div style=3D"word-wrap:break-word">
<blockquote type=3D"cite">
<div><br>
</div>
<div>Disregard does not mean drop, so those messages are still in next&nbsp=
;5444&nbsp;packet.&nbsp;This comes back to multiplexing by ownership or not=
, which that is not specified yet so&nbsp;we leave it for another future&nb=
sp;draft for multiplexing. We need to focus this reactive
 standard not make it complicated.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>Again, I respectfully disagree. A deployment model to envision is a ro=
uter, running both OLSRv2 and AODVv2. Both of those protocols share a trans=
port using RFC5444 to a second router, which is also running both protocols=
. The &quot;multiplexing&quot; being spoken
 of would be a mix of OLSRv2 and AODVv2 messages, bundled up into an RFC544=
4 packet.&nbsp;</div>
</div>
</blockquote>
<div><br>
</div>
<div>Ok, to be more general and to serve majority&nbsp;users of AODVv2 and =
more security consideration.&nbsp;&nbsp;we need to consider that some users=
 don't want such mix network and some do. First if users are wanting your&n=
bsp;mix scenario then they go for a parser that is unified
 for both protocols (&nbsp;this case&nbsp;routers need same multiplexing me=
thod otherwise they don't work ),&nbsp;while parsers are independent of pro=
tocols as RFC5444 says. If the AODVv2 sends a packet then parser is able to=
 do packing again locally&nbsp;with adding other messages
 if available.&nbsp;Secondly, &nbsp;users don't want to use specific unifie=
d&nbsp;parser dependence,&nbsp;so&nbsp;just the one&nbsp;protocol packing w=
ith its user method for security purpose.&nbsp;This way we have more indepe=
ndence for this AODVv2.&nbsp;</div>
<div><br>
</div>
</blockquote>
<br>
</div>
<div>If a given protocol specification/design adheres to the RFC 5444 multi=
plexing as it should, then both of your scenarios above (e.g., &quot;=85som=
e users don't want such mix network and some do.&quot;) work just fine.&nbs=
p;</div>
<div></div>
</div>
</blockquote>
<div><br>
</div>
<div>But that limits the routing&nbsp;protocols use of 5444-packet as never=
 they should create packets. They will depend on parsers (even if one proto=
col is running alone in the MANET)&nbsp;which can increase delays and maybe=
 less&nbsp;QoS. Designs need to be simple and the
 protocol packets are defined by protocols not parsers.&nbsp;</div>
</div>
</blockquote>
<div><br>
</div>
<div>What?!? There is no intersection with RFC5444 and QoS (or there needn'=
t be). RFC5444 serves as formats for the routing protocol only; the data-pa=
th (which is where you would apply QoS) uses standard switching/forwarding =
techniques.&nbsp;</div>
<br>
<blockquote type=3D"cite">
<div>
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">However, if a given protocol specificat=
ion does NOT adhere to the RFC 5444 multiplexing, it then PRECLUDES the pro=
tocol from being used in what you are calling a &quot;mixed network&quot;.&=
nbsp;</div>
</blockquote>
<div><br>
</div>
<div>No still we can use it in the mix, because the parser will understand =
5444-packets.&nbsp;RFC5444 is for the protocol to define its packets not th=
e parser.&nbsp;</div>
</div>
</blockquote>
<div><br>
</div>
<div>No, you can't.&nbsp;</div>
<br>
<blockquote type=3D"cite">
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">In summary, adherence to the RFC 5444 m=
ultiplexing gives deployments MORE flexibility instead of less, and is, IMH=
O, the superior design choice. &nbsp;As for your assertion that &quot;=85us=
ers don't want to use specific unified parser
 dependenc=85&quot;, I believe that is at best merely anecdotal, and at wor=
st, completely baseless.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>I think the use of RFC7181 is not flexible for users,&nbsp;because it =
depends on the unified&nbsp;parser's&nbsp;packets, if&nbsp;parser fails/att=
acked&nbsp;then OLSRv2 fails. IMHO, in&nbsp;future still 7181 will have mor=
e updates, which we had&nbsp;seen many in short time.&nbsp;</div>
</blockquote>
<br>
</div>
<div>OK. You are free to hold that opinion - as I am free to disagree with =
it. &nbsp;But again, other than your emails, I see no desire to re-open, re=
-discuss, and re-decide the current architecture of RFC5444 packets/message=
s/multiplexing. And unless (or until)
 there is wide-spread desire to re-open that debate, I see no useful purpos=
e in continuing this email thread, because the answer to all of your opinio=
ns/concerns &nbsp;is &quot;RFC5444 is what it is, and RFC5498 is what *it* =
is.&quot;</div>
<div><br>
</div>
<div>IMHO, it's time to move on to other discussions.&nbsp;</div>
<div><br>
</div>
<div>Stan</div>
</body>
</html>

--_000_9760F05C41FF4009B1BF9FF950B43F8Bciscocom_--


From nobody Wed Sep 10 05:54:36 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D86781A0079 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 05:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JfTqJNIezljh for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 05:54:33 -0700 (PDT)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 727A41A6FC2 for <manet@ietf.org>; Wed, 10 Sep 2014 05:54:33 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id c41so322019yho.18 for <manet@ietf.org>; Wed, 10 Sep 2014 05:54:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8Ed4DS5X4iu02cCxDjqJqB0DfgFaH66aPdTlhmQxvWg=; b=Mon63qgnaxwMwbb7h4ziunre7ffmNh75OGcD/GtIMxXIJD+kW3LVDktMmfjeJKNzsE jl7AtQOieKlLAqCAvgy1IDTi8iunTAOcWtabtgNC1+tYVpMBUQErISGsNrim/C/Dkc1v XwSgdB8w6cYC53DbHXAahBaKyGPXDJWtrOdVHeCiFil5Zni7RpRyIeMlyPKAF5AJIDb4 arPgXaMd47TR6elMOzJUjpmYupniF2+QDpzA3/StPHOEAoU/xgCtE191rVftpCdjW7VM fe5/v04W9LpNUGbhf07X2GrbX+HjVCV0CjLVbkX+l9Yms7vOPW1lkqQ19eBbqlt6sl0i yasw==
MIME-Version: 1.0
X-Received: by 10.236.123.228 with SMTP id v64mr59924159yhh.41.1410353672633;  Wed, 10 Sep 2014 05:54:32 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Wed, 10 Sep 2014 05:54:32 -0700 (PDT)
In-Reply-To: <53CC9339.50103@computer.org>
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org>
Date: Wed, 10 Sep 2014 14:54:32 +0200
Message-ID: <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Charles E. Perkins" <charliep@computer.org>
Content-Type: multipart/alternative; boundary=20cf301af543aa40a00502b58dbb
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/kcnlou1GB-IkVntFTkYNnS5qF9U
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 12:54:35 -0000

--20cf301af543aa40a00502b58dbb
Content-Type: text/plain; charset=UTF-8

I don't believe AODV only supports bidirectional, there are many work out
IETF done for that. I think there can be ways to make AODVv2 support
unidirectional paths as well. As links in MANET can be unidirectional
and/or bidirectional. For example, the RREQ message MUST indicate which
type of route communication it is requesting: bidirectional paths or
unidirectional paths or mix (what does authors/WG think?). We may need to
update RFC6130 for AODVv2 as well as done for OLSRv2.

On Monday, July 21, 2014, Charles E. Perkins wrote:

>
> Hello Chris,
>
> Perhaps it would be better to identify the proper protocol method as
> part of the applicability statement.  If no other means are available, then
> AODVv2 nodes could be required to use the blacklist mechanism, which
> is intended to provide bidirectionality.


Yes, ok, but I agree with Chris that the protocol needs to ensure
interoperability in all its normative body (e.g. the appendix is not
normative), so one required solution for the bidirectional issue, so all
implementations follow.


>
> It seems unwise to require additional protocol mechanisms for cases
> in which layer 2 already guarantees bidirectional links.  This could also
> be included as a statement within the applicability section.


Yes, agree.

AB

--20cf301af543aa40a00502b58dbb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I don&#39;t believe AODV only supports bidirectional, there are many work o=
ut IETF done for that. I=C2=A0think there can be ways to make AODVv2 suppor=
t unidirectional paths as well. As links in MANET=C2=A0can be unidirectiona=
l and/or=C2=A0bidirectional. For example,=C2=A0the RREQ message MUST indica=
te which type of route=C2=A0communication it is requesting:=C2=A0bidirectio=
nal paths=C2=A0or unidirectional paths or mix (what does authors/WG think?)=
.=C2=A0We may need to update RFC6130 for AODVv2=C2=A0as well as=C2=A0done f=
or OLSRv2.=C2=A0<br><br>On Monday, July 21, 2014, Charles E. Perkins  wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><br>
Hello Chris,<br>
<br>
Perhaps it would be better to identify the proper protocol method as<br>
part of the applicability statement.=C2=A0 If no other means are available,=
 then<br>
AODVv2 nodes could be required to use the blacklist mechanism, which<br>
is intended to provide bidirectionality.</blockquote><div><br></div><div>Ye=
s, ok, but I agree with Chris that the protocol needs to ensure interoperab=
ility in all its normative=C2=A0body (e.g. the=C2=A0appendix is not normati=
ve),=C2=A0so=C2=A0one required solution for the bidirectional=C2=A0issue, s=
o all implementations follow.=C2=A0<span></span></div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
<br>
It seems unwise to require additional protocol mechanisms for cases<br>
in which layer 2 already guarantees bidirectional links.=C2=A0 This could a=
lso<br>
be included as a statement within the applicability section.</blockquote><d=
iv><br></div><div>Yes, agree.=C2=A0</div><div>=C2=A0</div><div>AB</div>

--20cf301af543aa40a00502b58dbb--


From nobody Wed Sep 10 06:13:59 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85FD31A0077 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 06:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nwegLWdVCU3z for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 06:13:53 -0700 (PDT)
Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com [IPv6:2607:f8b0:4002:c07::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87CA21A007C for <manet@ietf.org>; Wed, 10 Sep 2014 06:13:40 -0700 (PDT)
Received: by mail-yk0-f170.google.com with SMTP id 19so2495755ykq.29 for <manet@ietf.org>; Wed, 10 Sep 2014 06:13:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=roBPXbkDgIORRSYqTEpAkYo/sTyhxDiLjzgGVh9Dhm4=; b=eQGAoPI6aDM6KpaTsamdd2M1BarZLUotxxBKUvAXHG6PmR5kDoj65vW5694HmfI/ce Nhu2x850zXmVLSv/J88/Yk5rOn8EAOuQVT429HQIrrMd5nSpcOdd7WBAxIYNPdZO4MiZ gcVQd4uBkMPlB6LxHK809QChfNxHeaX/TuptqTCT4ufHT+DgMUwemugb7+RNW+Hn6upB XQrRJq1YxuzETG353URq3IylpNcvwIVOHGBiClSuMbKDklfYIh8eNXcV6EiYcAWeSYah 8eiD6ZWumZ59e+c4e6TtCefpZjNjfimb0AX+hOhGNwZ3sX2v3E8OtcdqqoEU3i1mK3QK S/nQ==
MIME-Version: 1.0
X-Received: by 10.236.131.194 with SMTP id m42mr48463283yhi.31.1410354819706;  Wed, 10 Sep 2014 06:13:39 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Wed, 10 Sep 2014 06:13:39 -0700 (PDT)
In-Reply-To: <061.1b44a2845a63141c8adc66505db6419a@trac.tools.ietf.org>
References: <061.1b44a2845a63141c8adc66505db6419a@trac.tools.ietf.org>
Date: Wed, 10 Sep 2014 15:13:39 +0200
Message-ID: <CADnDZ8-GHcB8DviOr6W3y_50OWb_YRCapnPgU31GYwDnHLa_6w@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary=20cf301b67250934030502b5d20f
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/UaM196hYh8iS5ObOrhpCj8E4HMA
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>
Subject: Re: [manet] #34 (aodvv2): Section 13 must be removed
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 13:13:55 -0000

--20cf301b67250934030502b5d20f
Content-Type: text/plain; charset=UTF-8

I disagree with this proposed ticket or bug-issue.

On Thursday, April 3, 2014, manet issue tracker wrote:

> #34: Section 13 must be removed
>
>  (Thomas Clausen)
>  The whole of section 13 must be removed, with the exception of section
>  13.6 which is already covered by RFC5444.


RFC5444 is just format, has no functions and it does not specifying any
protocol. This section 13.6 is part of protocol.


All the other optional
>  mechanisms are either underspecified, with known problems in common
>  deployment topologies, or both. Further, they are clearly indicated
>  as "not needed" so why are they included?


They are not normative for protocol. What are problems you refer to, I
don't understand you. However, I don't find the indication "not needed".

AB

--20cf301b67250934030502b5d20f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I disagree with this proposed=C2=A0ticket or bug-issue.=C2=A0<div><br>On Th=
ursday, April 3, 2014, manet issue tracker  wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">#34: Section 13 must be removed<br>
<br>
=C2=A0(Thomas Clausen)<br>
=C2=A0The whole of section 13 must be removed, with the exception of sectio=
n<br>
=C2=A013.6 which is already covered by RFC5444.=C2=A0</blockquote><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"></blockquote><div><br></div><div>RFC5444 is just form=
at, has no functions and it does=C2=A0not specifying any protocol. This sec=
tion 13.6 is part of protocol.=C2=A0=C2=A0</div><div><br></div><div><br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">All the other optional<br>
=C2=A0mechanisms are either underspecified, with known problems in common<b=
r>
=C2=A0deployment topologies, or both. Further, they are clearly indicated<b=
r>
=C2=A0as &quot;not needed&quot; so why are they included?</blockquote><div>=
<br></div><div>They are not normative for protocol. What are problems you r=
efer to, I don&#39;t understand you.=C2=A0However,=C2=A0I don&#39;t find th=
e indication &quot;not needed&quot;.=C2=A0=C2=A0</div><div><br></div><div>A=
B</div></div>

--20cf301b67250934030502b5d20f--


From nobody Wed Sep 10 06:20:42 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 901101A00AD for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 06:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pvXSrWXtiwo7 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 06:20:38 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 602BA1A00A9 for <manet@ietf.org>; Wed, 10 Sep 2014 06:20:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 026B41BC0A1E; Wed, 10 Sep 2014 06:20:38 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id C29B91BC0A08; Wed, 10 Sep 2014 06:20:34 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E9013763-7470-4AFB-8929-16C08D77FB2A"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Thomas Clausen <thomas@thomasclausen.org>
In-Reply-To: <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com>
Date: Wed, 10 Sep 2014 15:20:31 +0200
Message-Id: <26B70768-2EEB-4FE5-AAA7-56E2B6265B36@thomasclausen.org>
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/jV7RqX9yVDaqmn0dHWa4LlWDGkg
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>, manet-ads <manet-ads@tools.ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 13:20:40 -0000

--Apple-Mail=_E9013763-7470-4AFB-8929-16C08D77FB2A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Sep 10, 2014, at 14:54, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> I don't believe AODV only supports bidirectional, there are many work =
out IETF done for that.

Right now, this protocol does not specify proper behavior in case links =
are not bidirectional. It does hand-waving of the =93can do this, can do =
that, or can do the other thing, or can think of something else =
entirely=94, but does not specify *one* way =97 which means that two =
implementations may do different, and non-interoperable, things.

This is one of the many examples of this protocol being way =
underspecified, which has been pointed out for many, many years, and =
which has not been addressed by the authors. If the authors truly =
doesn=92t know how to manage uni-directional links, or do not know which =
of the different options they wave around would make for a good default, =
then that is indicative of that this document perhaps is not mature =
enough to be advanced on Standards Track, and that more research, =
experimentation is needed =97 thus, making an Experimental RFC in the =
IRTF a perhaps better publication target and venue?

> I think there can be ways to make AODVv2 support unidirectional paths =
as well. As links in MANET can be unidirectional and/or bidirectional. =
For example, the RREQ message MUST indicate which type of route =
communication it is requesting: bidirectional paths or unidirectional =
paths or mix (what does authors/WG think?).=20

The use of unidirectional paths in a routing protocol is actually not =
trivial =97 there=92s been a lot of research work done in this area but, =
as far as I know, nothing conclusive has come from it.=20

The topic is not uninteresting, however, and I would suggest that:

	o	this reactive protocol, and its current specification =
(draft-ietf-manet-aodvv2) be=20
		moved to the IRTF, for intended publication as =
Experimental RFC

	o	as part of the development in the IRTF, the use of =
unidirectional paths be explored,
		and the utility of unidirectional paths be part of the =
experiment?

It sounds fairly close to what you suggest, doesn=92t it?=20

> We may need to update RFC6130 for AODVv2 as well as done for OLSRv2.=20=


No, we most definitely do not need to update RFC6130 for this purpose, =
there has been no arguments made that even suggest that this is =
necessary.

Best,

Thomas

> On Monday, July 21, 2014, Charles E. Perkins wrote:
>=20
> Hello Chris,
>=20
> Perhaps it would be better to identify the proper protocol method as
> part of the applicability statement.  If no other means are available, =
then
> AODVv2 nodes could be required to use the blacklist mechanism, which
> is intended to provide bidirectionality.
>=20
> Yes, ok, but I agree with Chris that the protocol needs to ensure =
interoperability in all its normative body (e.g. the appendix is not =
normative), so one required solution for the bidirectional issue, so all =
implementations follow.=20
> =20
>=20
> It seems unwise to require additional protocol mechanisms for cases
> in which layer 2 already guarantees bidirectional links.  This could =
also
> be included as a statement within the applicability section.
>=20
> Yes, agree.=20
> =20
> AB
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


--Apple-Mail=_E9013763-7470-4AFB-8929-16C08D77FB2A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Sep 10, 2014, at 14:54, Abdussalam =
Baryun &lt;<a =
href=3D"mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&=
gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">I don't believe AODV only supports bidirectional, there =
are many work out IETF done for that. </blockquote><div><br></div>Right =
now, this protocol does not specify proper behavior in case links are =
not bidirectional. It does hand-waving of the =93can do this, can do =
that, or can do the other thing, or can think of something else =
entirely=94, but does not specify *one* way =97 which means that two =
implementations may do different, and non-interoperable, =
things.</div><div><br></div><div>This is one of the many examples of =
this protocol being way underspecified, which has been pointed out for =
many, many years, and which has not been addressed by the authors. If =
the authors truly doesn=92t know how to manage uni-directional links, or =
do not know which of the different options they wave around would make =
for a good default, then that is indicative of that this document =
perhaps is not mature enough to be advanced on Standards Track, and that =
more research, experimentation is needed =97 thus, making an =
Experimental RFC in the IRTF a perhaps better publication target and =
venue?</div><div><br><blockquote type=3D"cite">I&nbsp;think there can be =
ways to make AODVv2 support unidirectional paths as well. As links in =
MANET&nbsp;can be unidirectional and/or&nbsp;bidirectional. For =
example,&nbsp;the RREQ message MUST indicate which type of =
route&nbsp;communication it is requesting:&nbsp;bidirectional =
paths&nbsp;or unidirectional paths or mix (what does authors/WG =
think?).&nbsp;</blockquote><div><br></div><div>The use of unidirectional =
paths in a routing protocol is actually not trivial =97 there=92s been a =
lot of research work done in this area but, as far as I know, nothing =
conclusive has come from it.&nbsp;</div><div><br></div>The topic is not =
uninteresting, however, and I would suggest =
that:</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>o<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>this reactive protocol, and its =
current specification (draft-ietf-manet-aodvv2) be&nbsp;</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>moved to the IRTF, for intended publication as Experimental =
RFC</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>o<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>as part of the development in the =
IRTF, the use of unidirectional paths be explored,</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>and the utility of unidirectional paths be part of the =
experiment?</div><div><br></div><div>It sounds fairly close to what you =
suggest, doesn=92t it?&nbsp;</div><div><br><blockquote type=3D"cite">We =
may need to update RFC6130 for AODVv2&nbsp;as well as&nbsp;done for =
OLSRv2.&nbsp;<br></blockquote><div><br></div>No, we most definitely do =
not need to update RFC6130 for this purpose, there has been no arguments =
made that even suggest that this is =
necessary.</div><div><br></div><div>Best,</div><div><br></div><div>Thomas<=
/div><div><br><blockquote type=3D"cite">On Monday, July 21, 2014, =
Charles E. Perkins  wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin: 0px 0px 0px 0.8ex; border-left-width: 1px; =
border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; position: static; z-index: auto;"><br>
Hello Chris,<br>
<br>
Perhaps it would be better to identify the proper protocol method as<br>
part of the applicability statement.&nbsp; If no other means are =
available, then<br>
AODVv2 nodes could be required to use the blacklist mechanism, which<br>
is intended to provide =
bidirectionality.</blockquote><div><br></div><div>Yes, ok, but I agree =
with Chris that the protocol needs to ensure interoperability in all its =
normative&nbsp;body (e.g. the&nbsp;appendix is not =
normative),&nbsp;so&nbsp;one required solution for the =
bidirectional&nbsp;issue, so all implementations =
follow.&nbsp;<span></span></div><div>&nbsp;</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<br>
It seems unwise to require additional protocol mechanisms for cases<br>
in which layer 2 already guarantees bidirectional links.&nbsp; This =
could also<br>
be included as a statement within the applicability =
section.</blockquote><div><br></div><div>Yes, =
agree.&nbsp;</div><div>&nbsp;</div><div>AB</div>
_______________________________________________<br>manet mailing =
list<br><a =
href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/manet<br></blockquote></div><br></body></html>=

--Apple-Mail=_E9013763-7470-4AFB-8929-16C08D77FB2A--


From nobody Wed Sep 10 06:25:56 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1C11A6FC5 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 06:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0eLffPTM9HIz for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 06:25:46 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DDEC1A00CF for <manet@ietf.org>; Wed, 10 Sep 2014 06:25:46 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id n12so6711537wgh.17 for <manet@ietf.org>; Wed, 10 Sep 2014 06:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=k6QCphmNirrFpQaIau1vyNl0fx9SHOT87GVU6O3yksw=; b=hS3DloWdoaEqi9BVDWuYIotQPbIScyvuTDz4p5FYxeDW4EG4Ao5neDEpz/KFRhhjlr qiZ0KOm+KI0rAjhokXqcs1hwIcAwfVjBWGfq/hSMBcLg+4TrVpiDwMwjW12bzzsEqIdn s+w2BAFNoWGrIdAdbq/stqWqX/VFJXtkAYFv2JY8XN+q6Unh9eLlMIfKUWZjQQqB4QAv jbgbB+s1j+uZ5HFfOQoca5hHFDQarwF0ET8VUPVnEp4CqnGI/9dkgV036jZBsn42gJHZ pL3xH6TgwzHFiyGNP4VayITHVd2YSUI1JP4Gr5FM6O4KdZgkPBSY5TZcmKx3qRX6Gl9B Y3JA==
X-Received: by 10.194.171.37 with SMTP id ar5mr49028395wjc.69.1410355544860; Wed, 10 Sep 2014 06:25:44 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id bj7sm2072590wjc.33.2014.09.10.06.25.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Sep 2014 06:25:43 -0700 (PDT)
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-92101646-E17E-4ED8-92D8-3DD86B18A59C
Content-Transfer-Encoding: 7bit
Message-Id: <4AE6555B-C2F9-4B7B-BF1F-18F4D912BAA0@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Wed, 10 Sep 2014 14:25:40 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/OSFEKA8-KFENDRaJd_C6e2YqUdk
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 13:25:51 -0000

--Apple-Mail-92101646-E17E-4ED8-92D8-3DD86B18A59C
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

First, no, nothing you have said is in any way an argument to update 6130 (N=
HDP), except of course that any protocol may define new TLVs to carry when u=
sed together with NHDP. But it's not obvious what that would be - NHDP alrea=
dy collects unidirectional information (at the receiver end of course). I'll=
 take that up after my second point.

Second, AODVv2 needs to either support or not support unidirectional links. I=
f it supports them, it needs to define how. If it doesn't support them it ne=
eds to have a defined interoperable mechanism to do so.

And that's where to start. What is required. Then how to do it, including wh=
at information is needed. At the abstract level. Then you can start thinking=
 about whether you can do that using NHDP, within existing AODVv2 messages, w=
ith new messages, etc. "We need to update 6130" isn't where to start, it's n=
ot even step two.

And there is an issue with using NHDP. It would convert AODVv2 from a reacti=
ve protocol to a hybrid one. Some of the reasons that a reactive protocol ma=
y be of interest are based on no transmissions with no data. Removing that a=
s even an option would make the protocol less applicable. Of course I have n=
o problem with using NHDP as an option. But the sort of option I'd want to s=
ee is one where if some routers decide to send HELLO messages and some don't=
 then the network still works at least as well as if none did. Which should b=
e to find routes where they are findable (maybe only using bidirectional lin=
ks) and not to fail because some links are unidirectional.

(How can that be done? No, I don't have a design. I just have a requirement.=
 Actually, summarising what the WG's reactive protocol requirements are more=
 precisely wouldn't be a bad, probably overdue, idea. I'm not suggesting a f=
ull blown draft - though one would be really good - but just basic bullet po=
ints. To address issues like unidirectional links and pure/hybrid reactivene=
ss. And what else? Note that my unidirectional link requirements would be: m=
ust function interoperably when some links are unidirectional, but using tho=
se unidirectional links, optional. The latter can definitely be debated. The=
 former is necessary.)

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 10 Sep 2014, at 13:54, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
>=20
> I don't believe AODV only supports bidirectional, there are many work out I=
ETF done for that. I think there can be ways to make AODVv2 support unidirec=
tional paths as well. As links in MANET can be unidirectional and/or bidirec=
tional. For example, the RREQ message MUST indicate which type of route comm=
unication it is requesting: bidirectional paths or unidirectional paths or m=
ix (what does authors/WG think?). We may need to update RFC6130 for AODVv2 a=
s well as done for OLSRv2.=20
>=20
>> On Monday, July 21, 2014, Charles E. Perkins wrote:
>>=20
>> Hello Chris,
>>=20
>> Perhaps it would be better to identify the proper protocol method as
>> part of the applicability statement.  If no other means are available, th=
en
>> AODVv2 nodes could be required to use the blacklist mechanism, which
>> is intended to provide bidirectionality.
>=20
> Yes, ok, but I agree with Chris that the protocol needs to ensure interope=
rability in all its normative body (e.g. the appendix is not normative), so o=
ne required solution for the bidirectional issue, so all implementations fol=
low.=20
> =20
>>=20
>> It seems unwise to require additional protocol mechanisms for cases
>> in which layer 2 already guarantees bidirectional links.  This could also=

>> be included as a statement within the applicability section.
>=20
> Yes, agree.=20
> =20
> AB
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-92101646-E17E-4ED8-92D8-3DD86B18A59C
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>First, no, nothing you have said is in=
 any way an argument to update 6130 (NHDP), except of course that any protoc=
ol may define new TLVs to carry when used together with NHDP. But it's not o=
bvious what that would be - NHDP already collects unidirectional information=
 (at the receiver end of course). I'll take that up after my second point.</=
div><div><br></div><div>Second, AODVv2 needs to either support or not suppor=
t unidirectional links. If it supports them, it needs to define how. If it d=
oesn't support them it needs to have a defined interoperable mechanism to do=
 so.</div><div><br></div><div>And that's where to start. What is required. T=
hen how to do it, including what information is needed. At the abstract leve=
l. Then you can start thinking about whether you can do that using NHDP, wit=
hin existing AODVv2 messages, with new messages, etc. "We need to update 613=
0" isn't where to start, it's not even step two.</div><div><br></div><div>An=
d there is an issue with using NHDP. It would convert AODVv2 from a reactive=
 protocol to a hybrid one. Some of the reasons that a reactive protocol may b=
e of interest are based on no transmissions with no data. Removing that as e=
ven an option would make the protocol less applicable. Of course I have no p=
roblem with using NHDP as an option. But the sort of option I'd want to see i=
s one where if some routers decide to send HELLO messages and some don't the=
n the network still works at least as well as if none did. Which should be t=
o find routes where they are findable (maybe only using bidirectional links)=
 and not to fail because some links are unidirectional.</div><div><br></div>=
<div>(How can that be done? No, I don't have a design. I just have a require=
ment. Actually, summarising what the WG's reactive protocol requirements are=
 more precisely wouldn't be a bad, probably overdue, idea. I'm not suggestin=
g a full blown draft - though one would be really good - but just basic bull=
et points. To address issues like unidirectional links and pure/hybrid react=
iveness. And what else? Note that my unidirectional link requirements would b=
e: must function interoperably when some links are unidirectional, but using=
 those unidirectional links, optional. The latter can definitely be debated.=
 The former is necessary.)<br><br>--&nbsp;<div>Christopher Dearlove</div><di=
v><a href=3D"mailto:christopher.dearlove@gmail.com">christopher.dearlove@gma=
il.com</a> (iPhone)</div><div><a href=3D"mailto:chris@mnemosyne.demon.co.uk"=
>chris@mnemosyne.demon.co.uk</a> (home)</div></div><div><br>On 10 Sep 2014, a=
t 13:54, Abdussalam Baryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com"=
>abdussalambaryun@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"=
cite"><div>I don't believe AODV only supports bidirectional, there are many w=
ork out IETF done for that. I&nbsp;think there can be ways to make AODVv2 su=
pport unidirectional paths as well. As links in MANET&nbsp;can be unidirecti=
onal and/or&nbsp;bidirectional. For example,&nbsp;the RREQ message MUST indi=
cate which type of route&nbsp;communication it is requesting:&nbsp;bidirecti=
onal paths&nbsp;or unidirectional paths or mix (what does authors/WG think?)=
.&nbsp;We may need to update RFC6130 for AODVv2&nbsp;as well as&nbsp;done fo=
r OLSRv2.&nbsp;<br><br>On Monday, July 21, 2014, Charles E. Perkins  wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><br>
Hello Chris,<br>
<br>
Perhaps it would be better to identify the proper protocol method as<br>
part of the applicability statement.&nbsp; If no other means are available, t=
hen<br>
AODVv2 nodes could be required to use the blacklist mechanism, which<br>
is intended to provide bidirectionality.</blockquote><div><br></div><div>Yes=
, ok, but I agree with Chris that the protocol needs to ensure interoperabil=
ity in all its normative&nbsp;body (e.g. the&nbsp;appendix is not normative)=
,&nbsp;so&nbsp;one required solution for the bidirectional&nbsp;issue, so al=
l implementations follow.&nbsp;<span></span></div><div>&nbsp;</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<br>
It seems unwise to require additional protocol mechanisms for cases<br>
in which layer 2 already guarantees bidirectional links.&nbsp; This could al=
so<br>
be included as a statement within the applicability section.</blockquote><di=
v><br></div><div>Yes, agree.&nbsp;</div><div>&nbsp;</div><div>AB</div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>manet mailing list</span><br><sp=
an><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mai=
lman/listinfo/manet</a></span><br></div></blockquote></body></html>=

--Apple-Mail-92101646-E17E-4ED8-92D8-3DD86B18A59C--


From nobody Wed Sep 10 08:31:09 2014
Return-Path: <john.dowdell.ietf@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C301A872E for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 08:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zReUrEx0wEIR for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 08:31:06 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 552851A03F5 for <manet@ietf.org>; Wed, 10 Sep 2014 08:31:06 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id m15so4663830wgh.19 for <manet@ietf.org>; Wed, 10 Sep 2014 08:31:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=OFjj5FLCo6+lKZ2hBtoKVB8PLE7sQKZ7ZE+jlE9zw+w=; b=yPVvBMCwbvpXstriTLXaNsKwdoXg7sWhqsL7JjjySEEFOnomPQGc9tt5aq+JSOI38j SfmbTCfLDVrx/XkSQ6OjP3/pdeeK9GD/ox5SU8ZyMqHoMO7JADVmDzyWg2wpAyPydy1C M6nBJyYpJMV5BMebV7ZoofvELPgYWqe5qVR0ycAor9pptGfdrdLhQpKjQY3ouN2jk4hp SJer6j3GokOeTOSG1wiyAnZJZ+hC8/uLa00NtMczw/ypI0ZacOcGnVQrrkl5+raZFSWY 0UjdE9Xmvx6uG/CYLUrGTP9VUq2V1EwZDKMZhp/4Xm3Ea2m66RTRHH41tXsATpovYXHE sueQ==
X-Received: by 10.194.236.132 with SMTP id uu4mr4139157wjc.108.1410363064968;  Wed, 10 Sep 2014 08:31:04 -0700 (PDT)
Received: from [10.0.4.178] ([217.158.48.187]) by mx.google.com with ESMTPSA id a19sm2851241wic.1.2014.09.10.08.31.04 for <manet@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Sep 2014 08:31:04 -0700 (PDT)
Message-ID: <54106EB7.9090705@gmail.com>
Date: Wed, 10 Sep 2014 16:31:03 +0100
From: John Dowdell <john.dowdell.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: manet@ietf.org
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com> <26B70768-2EEB-4FE5-AAA7-56E2B6265B36@thomasclausen.org>
In-Reply-To: <26B70768-2EEB-4FE5-AAA7-56E2B6265B36@thomasclausen.org>
Content-Type: multipart/alternative; boundary="------------040208050705040803060205"
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/LRBw3M9OSEpg0VVzJ4SvNUiHJvk
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 15:31:08 -0000

This is a multi-part message in MIME format.
--------------040208050705040803060205
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

All

As at draft-04, AODVv2 does not support unidirectional links. It is 
clearly stated in several sections, and in fact there is a test stated 
to specifically check whether a link is bidirectional or not.

Please do not argue further over whether AODVv2 supports this or that 
feature. The draft is under major review at this time, trying to take 
into account the very many comments that you have all kindly made. I 
fully agree with Thomas that supporting unidirectional links is 
non-trivial, and there is enough to do right now with the cycles 
available to the author team without adding this feature.

John

On 10/09/14 14:20, Thomas Clausen wrote:
>
> On Sep 10, 2014, at 14:54, Abdussalam Baryun 
> <abdussalambaryun@gmail.com <mailto:abdussalambaryun@gmail.com>> wrote:
>
>> I don't believe AODV only supports bidirectional, there are many work 
>> out IETF done for that. 
>
> Right now, this protocol does not specify proper behavior in case 
> links are not bidirectional. It does hand-waving of the “can do this, 
> can do that, or can do the other thing, or can think of something else 
> entirely”, but does not specify *one* way — which means that two 
> implementations may do different, and non-interoperable, things.
>
> This is one of the many examples of this protocol being way 
> underspecified, which has been pointed out for many, many years, and 
> which has not been addressed by the authors. If the authors truly 
> doesn’t know how to manage uni-directional links, or do not know which 
> of the different options they wave around would make for a good 
> default, then that is indicative of that this document perhaps is not 
> mature enough to be advanced on Standards Track, and that more 
> research, experimentation is needed — thus, making an Experimental RFC 
> in the IRTF a perhaps better publication target and venue?
>
>> I think there can be ways to make AODVv2 support unidirectional paths 
>> as well. As links in MANET can be unidirectional 
>> and/or bidirectional. For example, the RREQ message MUST indicate 
>> which type of route communication it is requesting: bidirectional 
>> paths or unidirectional paths or mix (what does authors/WG think?). 
>
> The use of unidirectional paths in a routing protocol is actually not 
> trivial — there’s been a lot of research work done in this area but, 
> as far as I know, nothing conclusive has come from it.
>
> The topic is not uninteresting, however, and I would suggest that:
>
> othis reactive protocol, and its current specification 
> (draft-ietf-manet-aodvv2) be
> moved to the IRTF, for intended publication as Experimental RFC
>
> oas part of the development in the IRTF, the use of unidirectional 
> paths be explored,
> and the utility of unidirectional paths be part of the experiment?
>
> It sounds fairly close to what you suggest, doesn’t it?
>
>> We may need to update RFC6130 for AODVv2 as well as done for OLSRv2.
>
> No, we most definitely do not need to update RFC6130 for this purpose, 
> there has been no arguments made that even suggest that this is necessary.
>
> Best,
>
> Thomas
>
>> On Monday, July 21, 2014, Charles E. Perkins wrote:
>>
>>
>>     Hello Chris,
>>
>>     Perhaps it would be better to identify the proper protocol method as
>>     part of the applicability statement.  If no other means are
>>     available, then
>>     AODVv2 nodes could be required to use the blacklist mechanism, which
>>     is intended to provide bidirectionality.
>>
>>
>> Yes, ok, but I agree with Chris that the protocol needs to ensure 
>> interoperability in all its normative body (e.g. the appendix is not 
>> normative), so one required solution for the bidirectional issue, so 
>> all implementations follow.
>>
>>
>>     It seems unwise to require additional protocol mechanisms for cases
>>     in which layer 2 already guarantees bidirectional links. This
>>     could also
>>     be included as a statement within the applicability section.
>>
>>
>> Yes, agree.
>> AB
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org <mailto:manet@ietf.org>
>> https://www.ietf.org/mailman/listinfo/manet
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


--------------040208050705040803060205
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    All<br>
    <br>
    As at draft-04, AODVv2 does not support unidirectional links. It is
    clearly stated in several sections, and in fact there is a test
    stated to specifically check whether a link is bidirectional or not.<br>
    <br>
    Please do not argue further over whether AODVv2 supports this or
    that feature. The draft is under major review at this time, trying
    to take into account the very many comments that you have all kindly
    made. I fully agree with Thomas that supporting unidirectional links
    is non-trivial, and there is enough to do right now with the cycles
    available to the author team without adding this feature.<br>
    <br>
    John<br>
    <br>
    <div class="moz-cite-prefix">On 10/09/14 14:20, Thomas Clausen
      wrote:<br>
    </div>
    <blockquote
      cite="mid:26B70768-2EEB-4FE5-AAA7-56E2B6265B36@thomasclausen.org"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <br>
      <div>
        <div>On Sep 10, 2014, at 14:54, Abdussalam Baryun &lt;<a
            moz-do-not-send="true"
            href="mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt;
          wrote:</div>
        <br class="Apple-interchange-newline">
        <blockquote type="cite">I don't believe AODV only supports
          bidirectional, there are many work out IETF done for that. </blockquote>
        <div><br>
        </div>
        Right now, this protocol does not specify proper behavior in
        case links are not bidirectional. It does hand-waving of the
        “can do this, can do that, or can do the other thing, or can
        think of something else entirely”, but does not specify *one*
        way — which means that two implementations may do different, and
        non-interoperable, things.</div>
      <div><br>
      </div>
      <div>This is one of the many examples of this protocol being way
        underspecified, which has been pointed out for many, many years,
        and which has not been addressed by the authors. If the authors
        truly doesn’t know how to manage uni-directional links, or do
        not know which of the different options they wave around would
        make for a good default, then that is indicative of that this
        document perhaps is not mature enough to be advanced on
        Standards Track, and that more research, experimentation is
        needed — thus, making an Experimental RFC in the IRTF a perhaps
        better publication target and venue?</div>
      <div><br>
        <blockquote type="cite">I think there can be ways to make AODVv2
          support unidirectional paths as well. As links in MANET can be
          unidirectional and/or bidirectional. For example, the RREQ
          message MUST indicate which type of route communication it is
          requesting: bidirectional paths or unidirectional paths or mix
          (what does authors/WG think?). </blockquote>
        <div><br>
        </div>
        <div>The use of unidirectional paths in a routing protocol is
          actually not trivial — there’s been a lot of research work
          done in this area but, as far as I know, nothing conclusive
          has come from it. </div>
        <div><br>
        </div>
        The topic is not uninteresting, however, and I would suggest
        that:</div>
      <div><br>
      </div>
      <div><span class="Apple-tab-span" style="white-space:pre"> </span>o<span
          class="Apple-tab-span" style="white-space:pre"> </span>this
        reactive protocol, and its current specification
        (draft-ietf-manet-aodvv2) be </div>
      <div><span class="Apple-tab-span" style="white-space:pre"> </span>moved
        to the IRTF, for intended publication as Experimental RFC</div>
      <div><br>
      </div>
      <div><span class="Apple-tab-span" style="white-space:pre"> </span>o<span
          class="Apple-tab-span" style="white-space:pre"> </span>as
        part of the development in the IRTF, the use of unidirectional
        paths be explored,</div>
      <div><span class="Apple-tab-span" style="white-space:pre"> </span>and
        the utility of unidirectional paths be part of the experiment?</div>
      <div><br>
      </div>
      <div>It sounds fairly close to what you suggest, doesn’t it? </div>
      <div><br>
        <blockquote type="cite">We may need to update RFC6130 for
          AODVv2 as well as done for OLSRv2. <br>
        </blockquote>
        <div><br>
        </div>
        No, we most definitely do not need to update RFC6130 for this
        purpose, there has been no arguments made that even suggest that
        this is necessary.</div>
      <div><br>
      </div>
      <div>Best,</div>
      <div><br>
      </div>
      <div>Thomas</div>
      <div><br>
        <blockquote type="cite">On Monday, July 21, 2014, Charles E.
          Perkins wrote:<br>
          <blockquote class="gmail_quote" style="margin: 0px 0px 0px
            0.8ex; border-left-width: 1px; border-left-color: rgb(204,
            204, 204); border-left-style: solid; padding-left: 1ex;
            position: static; z-index: auto;"><br>
            Hello Chris,<br>
            <br>
            Perhaps it would be better to identify the proper protocol
            method as<br>
            part of the applicability statement.  If no other means are
            available, then<br>
            AODVv2 nodes could be required to use the blacklist
            mechanism, which<br>
            is intended to provide bidirectionality.</blockquote>
          <div><br>
          </div>
          <div>Yes, ok, but I agree with Chris that the protocol needs
            to ensure interoperability in all its normative body (e.g.
            the appendix is not normative), so one required solution for
            the bidirectional issue, so all implementations follow. <span></span></div>
          <div> </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            It seems unwise to require additional protocol mechanisms
            for cases<br>
            in which layer 2 already guarantees bidirectional links. 
            This could also<br>
            be included as a statement within the applicability section.</blockquote>
          <div><br>
          </div>
          <div>Yes, agree. </div>
          <div> </div>
          <div>AB</div>
          _______________________________________________<br>
          manet mailing list<br>
          <a moz-do-not-send="true" href="mailto:manet@ietf.org">manet@ietf.org</a><br>
          <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet</a><br>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
manet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040208050705040803060205--


From nobody Wed Sep 10 08:56:15 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF1C91A8752 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 08:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O_tr9KJbfBiS for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 08:56:11 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ECD41A8754 for <manet@ietf.org>; Wed, 10 Sep 2014 08:56:10 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id x13so6394514wgg.33 for <manet@ietf.org>; Wed, 10 Sep 2014 08:56:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=zGKsBBu47nKA8/Ps93MC52i+THWC0KR/8QrMMZvl0hI=; b=iRfbW+2CXWewZ4pRwnaQGrK7DpwCu2XfpB7uB/4g0ITapdmGxfAI6qpO2LHQ4BjNer aPStfA4UHIN6mjMNgfTnzLDpSbU2k2Jorxb0WiHpxMSRsHa573NyqosmsJuLktNaOiyI 4NlNEKvqGBZRtSS4Uiiuy1qL2bJQvqAv9wRR/TprBY2+cYg9a8iEreojv2r7ItfUUQzd AOpQeRYGo+aNgc80SaFTzV6kptwsDe2S1ySxripSO1N+x6HLD3mLI4bV8nNWBuiw6ioP TJnmkjBs8QcKPzfnOjQ610Zow/eOWp4jJy1I0C5psZcl0Ll7Po0XaQyolpw09yK/Tuu1 2uPA==
X-Received: by 10.180.13.83 with SMTP id f19mr738660wic.80.1410364568881; Wed, 10 Sep 2014 08:56:08 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id pc6sm19022791wjb.43.2014.09.10.08.56.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Sep 2014 08:56:07 -0700 (PDT)
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com> <26B70768-2EEB-4FE5-AAA7-56E2B6265B36@thomasclausen.org> <54106EB7.9090705@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <54106EB7.9090705@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-B1483F72-1634-4691-B78A-186B01C1E1A2
Content-Transfer-Encoding: 7bit
Message-Id: <B10C5EB5-12F7-4681-B802-A510043ABF86@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Wed, 10 Sep 2014 16:56:04 +0100
To: John Dowdell <john.dowdell.ietf@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/wTf9zctgLEiJUlcQU4PLK2S1Iz8
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 15:56:13 -0000

--Apple-Mail-B1483F72-1634-4691-B78A-186B01C1E1A2
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

On unidirectional links, my point wasn't one of features, but one of necessi=
ty (use, or interoperably avoid). I'm sure that's clear to you, though the d=
raft up to now hasn't been good in this area. It may not be clear to everyon=
e posting.

However on whether the protocol should have a purely reactive mode of operat=
ion, I think this is quite appropriate for the WG to discuss, not just a "wa=
it and see what we offer you". Unless you can say there will be such a mode,=
 in which case I'll wait and see it.

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 10 Sep 2014, at 16:31, John Dowdell <john.dowdell.ietf@gmail.com> wrote=
:
>=20
> All
>=20
> As at draft-04, AODVv2 does not support unidirectional links. It is clearl=
y stated in several sections, and in fact there is a test stated to specific=
ally check whether a link is bidirectional or not.
>=20
> Please do not argue further over whether AODVv2 supports this or that feat=
ure. The draft is under major review at this time, trying to take into accou=
nt the very many comments that you have all kindly made. I fully agree with T=
homas that supporting unidirectional links is non-trivial, and there is enou=
gh to do right now with the cycles available to the author team without addi=
ng this feature.
>=20
> John
>=20
>> On 10/09/14 14:20, Thomas Clausen wrote:
>>=20
>>> On Sep 10, 2014, at 14:54, Abdussalam Baryun <abdussalambaryun@gmail.com=
> wrote:
>>>=20
>>> I don't believe AODV only supports bidirectional, there are many work ou=
t IETF done for that.
>>=20
>> Right now, this protocol does not specify proper behavior in case links a=
re not bidirectional. It does hand-waving of the =E2=80=9Ccan do this, can d=
o that, or can do the other thing, or can think of something else entirely=E2=
=80=9D, but does not specify *one* way =E2=80=94 which means that two implem=
entations may do different, and non-interoperable, things.
>>=20
>> This is one of the many examples of this protocol being way underspecifie=
d, which has been pointed out for many, many years, and which has not been a=
ddressed by the authors. If the authors truly doesn=E2=80=99t know how to ma=
nage uni-directional links, or do         not know which of the different op=
tions they wave around would make for a good default, then that is indicativ=
e of that this document perhaps is not mature enough to be advanced on Stand=
ards Track, and that more research, experimentation is needed =E2=80=94 thus=
, making an Experimental RFC in the IRTF a perhaps better publication target=
 and venue?
>>=20
>>> I think there can be ways to make AODVv2 support unidirectional paths as=
 well. As links in MANET can be unidirectional and/or bidirectional. For exa=
mple, the RREQ message MUST indicate which type of route communication it is=
 requesting: bidirectional paths or unidirectional paths or mix (what does a=
uthors/WG think?).=20
>>=20
>> The use of unidirectional paths in a routing protocol is actually not tri=
vial =E2=80=94 there=E2=80=99s been a lot of research work done in this area=
 but, as far as I know, nothing conclusive has come from it.=20
>>=20
>> The topic is not uninteresting, however, and I would suggest that:
>>=20
>>  o this reactive protocol, and its current specification (draft-ietf-mane=
t-aodvv2) be=20
>>  moved to the IRTF, for intended publication as Experimental RFC
>>=20
>>  o as part of the development in the IRTF, the use of unidirectional path=
s be explored,
>>  and the utility of unidirectional paths be part of the experiment?
>>=20
>> It sounds fairly close to what you suggest, doesn=E2=80=99t it?=20
>>=20
>>> We may need to update RFC6130 for AODVv2 as well as done for OLSRv2.=20
>>=20
>> No, we most definitely do not need to update RFC6130 for this purpose, th=
ere has been no arguments made that even suggest that this is necessary.
>>=20
>> Best,
>>=20
>> Thomas
>>=20
>>>> On Monday, July 21, 2014, Charles E. Perkins wrote:
>>>>=20
>>>> Hello Chris,
>>>>=20
>>>> Perhaps it would be better to identify the proper protocol method as
>>>> part of the applicability statement.  If no other means are available, t=
hen
>>>> AODVv2 nodes could be required to use the blacklist mechanism, which
>>>> is intended to provide bidirectionality.
>>>=20
>>> Yes, ok, but I agree with Chris that the protocol needs to ensure intero=
perability in all its normative body (e.g. the appendix is not normative), s=
o one required solution for the bidirectional issue, so all implementations f=
ollow.=20
>>> =20
>>>>=20
>>>> It seems unwise to require additional protocol mechanisms for cases
>>>> in which layer 2 already guarantees bidirectional links.  This could al=
so
>>>> be included as a statement within the applicability section.
>>>=20
>>> Yes, agree.=20
>>> =20
>>> AB
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>=20
>>=20
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-B1483F72-1634-4691-B78A-186B01C1E1A2
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>On unidirectional links, my point wasn=
't one of features, but one of necessity (use, or interoperably avoid). I'm s=
ure that's clear to you, though the draft up to now hasn't been good in this=
 area. It may not be clear to everyone posting.</div><div><br></div><div>How=
ever on whether the protocol should have a purely reactive mode of operation=
, I think this is quite appropriate for the WG to discuss, not just a "wait a=
nd see what we offer you". Unless you can say there will be such a mode, in w=
hich case I'll wait and see it.<br><br>--&nbsp;<div>Christopher Dearlove</di=
v><div><a href=3D"mailto:christopher.dearlove@gmail.com">christopher.dearlov=
e@gmail.com</a> (iPhone)</div><div><a href=3D"mailto:chris@mnemosyne.demon.c=
o.uk">chris@mnemosyne.demon.co.uk</a> (home)</div></div><div><br>On 10 Sep 2=
014, at 16:31, John Dowdell &lt;<a href=3D"mailto:john.dowdell.ietf@gmail.co=
m">john.dowdell.ietf@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D=
"cite"><div>
 =20
    <meta content=3D"text/html; charset=3Dwindows-1252" http-equiv=3D"Conten=
t-Type">
 =20
 =20
    All<br>
    <br>
    As at draft-04, AODVv2 does not support unidirectional links. It is
    clearly stated in several sections, and in fact there is a test
    stated to specifically check whether a link is bidirectional or not.<br>=

    <br>
    Please do not argue further over whether AODVv2 supports this or
    that feature. The draft is under major review at this time, trying
    to take into account the very many comments that you have all kindly
    made. I fully agree with Thomas that supporting unidirectional links
    is non-trivial, and there is enough to do right now with the cycles
    available to the author team without adding this feature.<br>
    <br>
    John<br>
    <br>
    <div class=3D"moz-cite-prefix">On 10/09/14 14:20, Thomas Clausen
      wrote:<br>
    </div>
    <blockquote cite=3D"mid:26B70768-2EEB-4FE5-AAA7-56E2B6265B36@thomasclaus=
en.org" type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html;
        charset=3Dwindows-1252">
      <br>
      <div>
        <div>On Sep 10, 2014, at 14:54, Abdussalam Baryun &lt;<a moz-do-not-=
send=3D"true" href=3D"mailto:abdussalambaryun@gmail.com">abdussalambaryun@gm=
ail.com</a>&gt;
          wrote:</div>
        <br class=3D"Apple-interchange-newline">
        <blockquote type=3D"cite">I don't believe AODV only supports
          bidirectional, there are many work out IETF done for that. </block=
quote>
        <div><br>
        </div>
        Right now, this protocol does not specify proper behavior in
        case links are not bidirectional. It does hand-waving of the
        =E2=80=9Ccan do this, can do that, or can do the other thing, or can=

        think of something else entirely=E2=80=9D, but does not specify *one=
*
        way =E2=80=94 which means that two implementations may do different,=
 and
        non-interoperable, things.</div>
      <div><br>
      </div>
      <div>This is one of the many examples of this protocol being way
        underspecified, which has been pointed out for many, many years,
        and which has not been addressed by the authors. If the authors
        truly doesn=E2=80=99t know how to manage uni-directional links, or d=
o
        not know which of the different options they wave around would
        make for a good default, then that is indicative of that this
        document perhaps is not mature enough to be advanced on
        Standards Track, and that more research, experimentation is
        needed =E2=80=94 thus, making an Experimental RFC in the IRTF a perh=
aps
        better publication target and venue?</div>
      <div><br>
        <blockquote type=3D"cite">I&nbsp;think there can be ways to make AOD=
Vv2
          support unidirectional paths as well. As links in MANET&nbsp;can b=
e
          unidirectional and/or&nbsp;bidirectional. For example,&nbsp;the RR=
EQ
          message MUST indicate which type of route&nbsp;communication it is=

          requesting:&nbsp;bidirectional paths&nbsp;or unidirectional paths o=
r mix
          (what does authors/WG think?).&nbsp;</blockquote>
        <div><br>
        </div>
        <div>The use of unidirectional paths in a routing protocol is
          actually not trivial =E2=80=94 there=E2=80=99s been a lot of resea=
rch work
          done in this area but, as far as I know, nothing conclusive
          has come from it.&nbsp;</div>
        <div><br>
        </div>
        The topic is not uninteresting, however, and I would suggest
        that:</div>
      <div><br>
      </div>
      <div><span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>=
o<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>this
        reactive protocol, and its current specification
        (draft-ietf-manet-aodvv2) be&nbsp;</div>
      <div><span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>=
moved
        to the IRTF, for intended publication as Experimental RFC</div>
      <div><br>
      </div>
      <div><span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>=
o<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>as
        part of the development in the IRTF, the use of unidirectional
        paths be explored,</div>
      <div><span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>=
and
        the utility of unidirectional paths be part of the experiment?</div>=

      <div><br>
      </div>
      <div>It sounds fairly close to what you suggest, doesn=E2=80=99t it?&n=
bsp;</div>
      <div><br>
        <blockquote type=3D"cite">We may need to update RFC6130 for
          AODVv2&nbsp;as well as&nbsp;done for OLSRv2.&nbsp;<br>
        </blockquote>
        <div><br>
        </div>
        No, we most definitely do not need to update RFC6130 for this
        purpose, there has been no arguments made that even suggest that
        this is necessary.</div>
      <div><br>
      </div>
      <div>Best,</div>
      <div><br>
      </div>
      <div>Thomas</div>
      <div><br>
        <blockquote type=3D"cite">On Monday, July 21, 2014, Charles E.
          Perkins wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px
            0.8ex; border-left-width: 1px; border-left-color: rgb(204,
            204, 204); border-left-style: solid; padding-left: 1ex;
            position: static; z-index: auto;"><br>
            Hello Chris,<br>
            <br>
            Perhaps it would be better to identify the proper protocol
            method as<br>
            part of the applicability statement.&nbsp; If no other means are=

            available, then<br>
            AODVv2 nodes could be required to use the blacklist
            mechanism, which<br>
            is intended to provide bidirectionality.</blockquote>
          <div><br>
          </div>
          <div>Yes, ok, but I agree with Chris that the protocol needs
            to ensure interoperability in all its normative&nbsp;body (e.g.
            the&nbsp;appendix is not normative),&nbsp;so&nbsp;one required s=
olution for
            the bidirectional&nbsp;issue, so all implementations follow.&nbs=
p;<span></span></div>
          <div>&nbsp;</div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            It seems unwise to require additional protocol mechanisms
            for cases<br>
            in which layer 2 already guarantees bidirectional links.&nbsp;
            This could also<br>
            be included as a statement within the applicability section.</bl=
ockquote>
          <div><br>
          </div>
          <div>Yes, agree.&nbsp;</div>
          <div>&nbsp;</div>
          <div>AB</div>
          _______________________________________________<br>
          manet mailing list<br>
          <a moz-do-not-send=3D"true" href=3D"mailto:manet@ietf.org">manet@i=
etf.org</a><br>
          <a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/ma=
ilman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet</a><br>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
manet mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:manet@ietf.org">manet@i=
etf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/list=
info/manet">https://www.ietf.org/mailman/listinfo/manet</a>
</pre>
    </blockquote>
    <br>
 =20

</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>manet mailing list</span><br><sp=
an><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mai=
lman/listinfo/manet</a></span><br></div></blockquote></body></html>=

--Apple-Mail-B1483F72-1634-4691-B78A-186B01C1E1A2--


From nobody Wed Sep 10 13:51:08 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 342111A8A82 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 13:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zypWui_9FjmP for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 13:51:04 -0700 (PDT)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3567D1A9247 for <manet@ietf.org>; Wed, 10 Sep 2014 13:50:35 -0700 (PDT)
Received: by mail-yk0-f172.google.com with SMTP id q9so3375138ykb.31 for <manet@ietf.org>; Wed, 10 Sep 2014 13:50:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=04Skaq6BH55lJixnrR25bEyEScUwH2VIkffUskPCMbA=; b=s+Aiz6S9UQd5tfpdwgaag/8eZPD44KW5b71pWoaL47S+/cIPZH+j/DKF4wGp5tdFve ZH5v2YWtWsRwd61//rvuCMCQrRlwovBQvz+m8aAQrc6IbVbXPScXBA3owjdoTQSAKtKp ZhStgkx3XVFkGoXTiiOW+l+wvn89n6fjXEbxcGVvisgox13YwLddJmxv0ki0qC7CDEdq f7Bf0d5ecuDx+H0H3hu386NtWGhT33su8Cx4MH8LHtQ0RRwSjd7kwrx2LkV7xl+xcIsy zBQdiyiWtTREC2mtTkvlLubZSOzr3f8HSNdlG4Q8KsgksRvRWe0d2PFcehw2w80LwDp/ BLJA==
MIME-Version: 1.0
X-Received: by 10.236.61.69 with SMTP id v45mr3570873yhc.130.1410382234512; Wed, 10 Sep 2014 13:50:34 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Wed, 10 Sep 2014 13:50:34 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECC2@GLKXM0002V.GREENLNK.net>
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECC2@GLKXM0002V.GREENLNK.net>
Date: Wed, 10 Sep 2014 22:50:34 +0200
Message-ID: <CADnDZ88OMOTUc7Btbf9TP57NT58R4Z4rM8t58mX-6=k21GPrDg@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=089e0160b5ce15f3a30502bc3402
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/bTO17rJo_nTUzwfQhwLy5ubMgzw
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 20:51:06 -0000

--089e0160b5ce15f3a30502bc3402
Content-Type: text/plain; charset=UTF-8

On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:

> The key thing is that two independent implementations need to interoperate
> and not use unidirectional links. At the moment that wouldn't happen.
>
>
In draft's applicability statement:

---- OLD EDIT-----

AODVv2 only supports bidirectional links.  In the case of possible
unidirectional links, either blacklists (see Section 5.2) or other
means (e.g. adjacency establishment with only neighboring routers that
have bidirectional communication as indicated by NHDP [RFC6130]) of
assuring and monitoring bidirectionality are recommended. Otherwise,
persistent packet loss or persistent protocol failures could occur.
The cost of bidirectional link L (denoted Cost(L)) may depend upon the
direction across the link for which the cost is measured.  If received
over a link that is unidirectional, metric information from incoming
AODVv2 messages SHOULD NOT be used for route table updates.


---- NEW EDIT -----

AODVv2 only supports bidirectional links.  In the case of possible
unidirectional links, the protocol MUST use blacklists (see Section
5.2), otherwise may use means (e.g. adjacency establishment with only
neighboring routers that have bidirectional communication as indicated
by NHDP [RFC6130]) of assuring and monitoring bidirectionality are
recommended. Otherwise, persistent packet loss or persistent protocol
failures could occur.

-------------

Move the below text to another suitable section which I recommend section 5.2.

{{{

The cost of bidirectional link L (denoted Cost(L)) may depend upon the
direction across the link for which the cost is measured.  If received
over a link that is unidirectional, metric information from incoming
AODVv2 messages SHOULD NOT be used for route table updates.

}}}


AB

--089e0160b5ce15f3a30502bc3402
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Tuesday, July 22, 2014, Dearlove, Christopher (UK)  wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">The key thing is that two independent implemen=
tations need to interoperate and not use unidirectional links. At the momen=
t that wouldn&#39;t happen.<br><br>
</blockquote><div><br></div><div>In draft&#39;s=C2=A0applicability statemen=
t:=C2=A0</div><div><br></div><div>---- OLD EDIT-----</div><div>
	=09
=09
=09
		<div class=3D"page" title=3D"Page 9">
			<div class=3D"section">
				<div class=3D"layoutArea">
					<div class=3D"column">
						<pre><span style=3D"font-size:10.000000pt;font-family:&#39;Courier&#3=
9;">AODVv2 only supports bidirectional links.  In the case of possible unid=
irectional links, either blacklists (see </span><span style=3D"font-size:10=
.000000pt;font-family:&#39;Courier&#39;;color:rgb(0.000000%,0.000000%,100.0=
00000%)">Section 5.2</span><span style=3D"font-size:10.000000pt;font-family=
:&#39;Courier&#39;">) or other means (e.g. adjacency establishment with onl=
y neighboring routers that have bidirectional communication as indicated by=
 NHDP [</span><span style=3D"font-size:10.000000pt;font-family:&#39;Courier=
&#39;;color:rgb(0.000000%,0.000000%,100.000000%)">RFC6130</span><span style=
=3D"font-size:10.000000pt;font-family:&#39;Courier&#39;">]) of assuring and=
 monitoring bidirectionality are recommended. Otherwise, persistent packet =
loss or persistent protocol failures could occur.  The cost of bidirectiona=
l link L (denoted Cost(L)) may depend upon the direction across the link fo=
r which the cost is measured.  If received over a link that is unidirection=
al, metric information from incoming AODVv2 messages SHOULD NOT be used for=
 route table updates.</span></pre></div></div></div></div></div><div><br></=
div><div>---- NEW EDIT -----=C2=A0</div><div><pre><font face=3D"Helvetica N=
eue, Helvetica, Arial, sans-serif" size=3D"3"><span style=3D"white-space:no=
rmal;background-color:rgba(255,255,255,0)">AODVv2 only supports bidirection=
al links.  In the case of possible unidirectional links, the protocol MUST=
=C2=A0use=C2=A0blacklists (see Section 5.2), otherwise=C2=A0may=C2=A0use=C2=
=A0means (e.g. adjacency establishment with only neighboring routers that h=
ave bidirectional communication as indicated by NHDP [RFC6130]) of assuring=
 and monitoring bidirectionality are recommended. Otherwise, persistent pac=
ket loss or persistent protocol failures could occur.=C2=A0 </span></font><=
/pre><pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" size=
=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,255,=
0)">-------------</span></font></pre><pre><font face=3D"Helvetica Neue, Hel=
vetica, Arial, sans-serif" size=3D"3"><span style=3D"white-space:normal;bac=
kground-color:rgba(255,255,255,0)">Move the below text to another suitable =
section which I recommend section 5.2.=C2=A0</span></font></pre><pre><font =
face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" size=3D"3"><span styl=
e=3D"white-space:normal;background-color:rgba(255,255,255,0)">{{{</span></f=
ont></pre><pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" =
size=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,=
255,0)">The cost of bidirectional link L (denoted Cost(L)) may depend upon =
the direction across the link for which the cost is measured.  If received =
over a link that is unidirectional, metric information from incoming AODVv2=
 messages SHOULD NOT be used for route table updates.</span></font></pre><p=
re><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" size=3D"3"><=
span style=3D"white-space:normal;background-color:rgba(255,255,255,0)">}}}<=
/span></font></pre><pre><font face=3D"Helvetica Neue, Helvetica, Arial, san=
s-serif" size=3D"3"><span style=3D"white-space:normal;background-color:rgba=
(255,255,255,0)"><br></span></font></pre><pre><font face=3D"Helvetica Neue,=
 Helvetica, Arial, sans-serif" size=3D"3"><span style=3D"white-space:normal=
;background-color:rgba(255,255,255,0)">AB</span></font></pre></div><div><br=
></div>

--089e0160b5ce15f3a30502bc3402--


From nobody Wed Sep 10 14:05:47 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C8A1A9248 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 14:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W5kyXRDEbI0N for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 14:05:44 -0700 (PDT)
Received: from mail-yh0-x229.google.com (mail-yh0-x229.google.com [IPv6:2607:f8b0:4002:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC1781A9246 for <manet@ietf.org>; Wed, 10 Sep 2014 14:05:44 -0700 (PDT)
Received: by mail-yh0-f41.google.com with SMTP id t59so2919043yho.0 for <manet@ietf.org>; Wed, 10 Sep 2014 14:05:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6lBHOEbYJnTpx4PxyvO9B/7dTxrbVASltB7B3hg+NR0=; b=skB0bZyhRPzWNkB2kXyYiJBXofPOeDl1nFaCDBsqDenQbx7PIHlrNK02Nb+IffFk5m sty/oHRHPj7xF030nPq2Vs0OlnA7K8xjvaqRuy87QvmjKc++mEf4vMhyiZ30fCXix6MZ 7yRXEUdRiVWqJg3wCFP1+CE3sy6ccrTbvmpY+y9u2x+uYNmVH2BQcEpkGdQ8aBGDfA95 uBNUlGPgr9nT5Jwt6WRIxsMsNKkGa5LQoOnNJZZ6f71ZRBDLkrcQJhutWftrs2tZ/Mb7 AGVHFhFSdobdTYQ1NAdtkwMkIwCU/Gel9LKsMrwhULUWwbJCpeC4aR2Dxaap4MKgLPT8 +TdQ==
MIME-Version: 1.0
X-Received: by 10.236.30.69 with SMTP id j45mr64594372yha.37.1410383143910; Wed, 10 Sep 2014 14:05:43 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Wed, 10 Sep 2014 14:05:43 -0700 (PDT)
In-Reply-To: <54106EB7.9090705@gmail.com>
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com> <26B70768-2EEB-4FE5-AAA7-56E2B6265B36@thomasclausen.org> <54106EB7.9090705@gmail.com>
Date: Wed, 10 Sep 2014 23:05:43 +0200
Message-ID: <CADnDZ88kVfGat=3ma6WmyDsuKCD+FGMjK66K3PfPE3tgtAp-gQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John Dowdell <john.dowdell.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=089e013cbfd04a43010502bc6a44
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/T3SnAZ2siihYcrY9mh9K7Rt_Apc
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 21:05:46 -0000

--089e013cbfd04a43010502bc6a44
Content-Type: text/plain; charset=UTF-8

Hi John,

I want progress so I will do many edits and discussion and want just to
help. Hope authors don't mind my participation.

On Wednesday, September 10, 2014, John Dowdell wrote:

>  All
>
> As at draft-04, AODVv2 does not support unidirectional links. It is
> clearly stated in several sections, and in fact there is a test stated to
> specifically check whether a link is bidirectional or not.
>

IMHO, MANET use case cannot exclude unidirectional possibility, anyway let
me follow authors. The draft is not clear that is why Chris had some
confusion on interoperability.

 In the draft in section 13.4, it discusses also mechanism of multicast
RREP which describe it can be used in unidirectional link purpose. So draft
saying somehow there can be some support of unidirectional links, but not
well described how to configure. My suggest for RREQ was valid because the
draft is not excluding unidirectional links as possibility.

Any way I gave my reaction for progress and will try to wait to see what
will happen to change draft as what WG/authors decide.

AB

>
>

--089e013cbfd04a43010502bc6a44
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi John,<div><br></div><div>I want progress so I will do many edits and dis=
cussion and want just=C2=A0to help. Hope authors don&#39;t mind my particip=
ation.=C2=A0<br><br>On Wednesday, September 10, 2014, John Dowdell  wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    All<br>
    <br>
    As at draft-04, AODVv2 does not support unidirectional links. It is
    clearly stated in several sections, and in fact there is a test
    stated to specifically check whether a link is bidirectional or not.</d=
iv></blockquote><div><br></div><div>IMHO, MANET use case cannot exclude uni=
directional possibility, anyway=C2=A0let me follow authors. The draft is no=
t clear that is why Chris had some confusion on interoperability.=C2=A0</di=
v><div><br></div><div>=C2=A0In the draft in section 13.4,=C2=A0it discusses=
 also mechanism of multicast RREP which describe it=C2=A0can be used in uni=
directional link purpose. So draft saying somehow there=C2=A0can be some su=
pport of unidirectional links, but not well described how to configure. My =
suggest for RREQ=C2=A0was=C2=A0valid because the draft is not excluding uni=
directional links as possibility.=C2=A0</div><div><br></div><div>Any way I =
gave my reaction for progress=C2=A0and=C2=A0will try to wait to see what wi=
ll happen to change draft=C2=A0as what WG/authors=C2=A0decide.</div><div><b=
r></div><div>AB</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text=3D"#000000" b=
gcolor=3D"#FFFFFF"><blockquote type=3D"cite"><div><blockquote type=3D"cite"=
></blockquote></div></blockquote><br>
  </div></blockquote><div><br></div><div>=C2=A0</div><div><br></div><div>=
=C2=A0</div></div>

--089e013cbfd04a43010502bc6a44--


From nobody Wed Sep 10 14:20:36 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 431C21A924F for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 14:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9OLKDQyplDSG for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 14:20:28 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69EFA1A9247 for <manet@ietf.org>; Wed, 10 Sep 2014 14:20:28 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id u56so5139558wes.10 for <manet@ietf.org>; Wed, 10 Sep 2014 14:20:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=UwvDnKwSTe/+48SHt6jhFepl3JGlW1UkEWn5oh26xgk=; b=J8l9byTpSw32ScWZ+aI6aCEOxsVofnxPnv86X1waqa0XmEVFZmXatnrR//V3v5XgVe KQQStoXNI3Ggy7olquBs0yyZcZJGjxi8HDvnSBG7gWEb/HzM9c1KFoRiz0Vx2Hj5zQ/h M3inlUmFjkjuvzUr6mKlRPtzrxgTCcUsYezuMZeGC8zo/YZATdrxAQa0pfoS3qUJemmE /r6bmZmX2HPlKtJ9wwMEv+lt6s2nVL4AKP5AoJXlr1LVwAB97DrffWx8BPs2TnYF6gEs UUFSAKUVOp+z9OCoVYva6XuDXsLiloCQOfRfRDTaG2tOXNAZuH/X4DriiWcCvjAOWmh/ j/1Q==
X-Received: by 10.194.9.228 with SMTP id d4mr6362287wjb.99.1410384027023; Wed, 10 Sep 2014 14:20:27 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id lh5sm19945521wjb.12.2014.09.10.14.20.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Sep 2014 14:20:25 -0700 (PDT)
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECC2@GLKXM0002V.GREENLNK.net> <CADnDZ88OMOTUc7Btbf9TP57NT58R4Z4rM8t58mX-6=k21GPrDg@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ88OMOTUc7Btbf9TP57NT58R4Z4rM8t58mX-6=k21GPrDg@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-76CC3CDD-D40A-4189-B724-7A29682CB614
Content-Transfer-Encoding: 7bit
Message-Id: <D6C0EF9E-17CE-4B93-80B9-FE4DF57BA62D@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Wed, 10 Sep 2014 22:20:22 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/Vgeoq-k47DFYtfT3hMaLyB7llJo
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 21:20:34 -0000

--Apple-Mail-76CC3CDD-D40A-4189-B724-7A29682CB614
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

That's addressed to me, but a misdirection in that regard. In this regard I'=
ve made comments, and as John said, let's see what the next draft brings. I'=
m not even sure which bits below have what status.

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 10 Sep 2014, at 21:50, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
>=20
>=20
>=20
>> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>> The key thing is that two independent implementations need to interoperat=
e and not use unidirectional links. At the moment that wouldn't happen.
>=20
> In draft's applicability statement:=20
>=20
> ---- OLD EDIT-----
> AODVv2 only supports bidirectional links.  In the case of possible unidire=
ctional links, either blacklists (see Section 5.2) or other means (e.g. adja=
cency establishment with only neighboring routers that have bidirectional co=
mmunication as indicated by NHDP [RFC6130]) of assuring and monitoring bidir=
ectionality are recommended. Otherwise, persistent packet loss or persistent=
 protocol failures could occur.  The cost of bidirectional link L (denoted C=
ost(L)) may depend upon the direction across the link for which the cost is m=
easured.  If received over a link that is unidirectional, metric information=
 from incoming AODVv2 messages SHOULD NOT be used for route table updates.
>=20
> ---- NEW EDIT -----=20
> AODVv2 only supports bidirectional links. In the case of possible unidirec=
tional links, the protocol MUST use blacklists (see Section 5.2), otherwise m=
ay use means (e.g. adjacency establishment with only neighboring routers tha=
t have bidirectional communication as indicated by NHDP [RFC6130]) of assuri=
ng and monitoring bidirectionality are recommended. Otherwise, persistent pa=
cket loss or persistent protocol failures could occur.=20
> -------------
> Move the below text to another suitable section which I recommend section 5=
.2.=20
> {{{
> The cost of bidirectional link L (denoted Cost(L)) may depend upon the dir=
ection across the link for which the cost is measured. If received over a li=
nk that is unidirectional, metric information from incoming AODVv2 messages S=
HOULD NOT be used for route table updates.
> }}}
>=20
> AB
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-76CC3CDD-D40A-4189-B724-7A29682CB614
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>That's addressed to me, but a misdirec=
tion in that regard. In this regard I've made comments, and as John said, le=
t's see what the next draft brings. I'm not even sure which bits below have w=
hat status.<br><br>-- &nbsp;<div>Christopher Dearlove</div><div><a href=3D"m=
ailto:christopher.dearlove@gmail.com">christopher.dearlove@gmail.com</a> (iP=
hone)</div><div><a href=3D"mailto:chris@mnemosyne.demon.co.uk">chris@mnemosy=
ne.demon.co.uk</a> (home)</div></div><div><br>On 10 Sep 2014, at 21:50, Abdu=
ssalam Baryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">abdussalamba=
ryun@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><b=
r><br>On Tuesday, July 22, 2014, Dearlove, Christopher (UK)  wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">The key thing is that two independent implementatio=
ns need to interoperate and not use unidirectional links. At the moment that=
 wouldn't happen.<br><br>
</blockquote><div><br></div><div>In draft's&nbsp;applicability statement:&nb=
sp;</div><div><br></div><div>---- OLD EDIT-----</div><div>
	=09
=09
=09
		<div class=3D"page" title=3D"Page 9">
			<div class=3D"section">
				<div class=3D"layoutArea">
					<div class=3D"column">
						<pre><span style=3D"font-si=
ze:10.000000pt;font-family:'Courier'">AODVv2 only supports bidirectional lin=
ks.  In the case of possible unidirectional links, either blacklists (see </=
span><span style=3D"font-size:10.000000pt;font-family:'Courier';color:rgb(0.=
000000%,0.000000%,100.000000%)">Section 5.2</span><span style=3D"font-size:1=
0.000000pt;font-family:'Courier'">) or other means (e.g. adjacency establish=
ment with only neighboring routers that have bidirectional communication as i=
ndicated by NHDP [</span><span style=3D"font-size:10.000000pt;font-family:'C=
ourier';color:rgb(0.000000%,0.000000%,100.000000%)">RFC6130</span><span styl=
e=3D"font-size:10.000000pt;font-family:'Courier'">]) of assuring and monitor=
ing bidirectionality are recommended. Otherwise, persistent packet loss or p=
ersistent protocol failures could occur.  The cost of bidirectional link L (=
denoted Cost(L)) may depend upon the direction across the link for which the=
 cost is measured.  If received over a link that is unidirectional, metric i=
nformation from incoming AODVv2 messages SHOULD NOT be used for route table u=
pdates.</span></pre></div></div></div></div></div><div><br></div><div>---- N=
EW EDIT -----&nbsp;</div><div><pre><font face=3D"Helvetica Neue, Helvetica, A=
rial, sans-serif" size=3D"3"><span style=3D"white-space:normal;background-co=
lor:rgba(255,255,255,0)">AODVv2 only supports bidirectional links.  In the c=
ase of possible unidirectional links, the protocol MUST&nbsp;use&nbsp;blackl=
ists (see Section 5.2), otherwise&nbsp;may&nbsp;use&nbsp;means (e.g. adjacen=
cy establishment with only neighboring routers that have bidirectional commu=
nication as indicated by NHDP [RFC6130]) of assuring and monitoring bidirect=
ionality are recommended. Otherwise, persistent packet loss or persistent pr=
otocol failures could occur.&nbsp; </span></font></pre><pre><font face=3D"He=
lvetica Neue, Helvetica, Arial, sans-serif" size=3D"3"><span style=3D"white-=
space:normal;background-color:rgba(255,255,255,0)">-------------</span></fon=
t></pre><pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" siz=
e=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,255,=
0)">Move the below text to another suitable section which I recommend sectio=
n 5.2.&nbsp;</span></font></pre><pre><font face=3D"Helvetica Neue, Helvetica=
, Arial, sans-serif" size=3D"3"><span style=3D"white-space:normal;background=
-color:rgba(255,255,255,0)">{{{</span></font></pre><pre><font face=3D"Helvet=
ica Neue, Helvetica, Arial, sans-serif" size=3D"3"><span style=3D"white-spac=
e:normal;background-color:rgba(255,255,255,0)">The cost of bidirectional lin=
k L (denoted Cost(L)) may depend upon the direction across the link for whic=
h the cost is measured.  If received over a link that is unidirectional, met=
ric information from incoming AODVv2 messages SHOULD NOT be used for route t=
able updates.</span></font></pre><pre><font face=3D"Helvetica Neue, Helvetic=
a, Arial, sans-serif" size=3D"3"><span style=3D"white-space:normal;backgroun=
d-color:rgba(255,255,255,0)">}}}</span></font></pre><pre><font face=3D"Helve=
tica Neue, Helvetica, Arial, sans-serif" size=3D"3"><span style=3D"white-spa=
ce:normal;background-color:rgba(255,255,255,0)"><br></span></font></pre><pre=
><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" size=3D"3"><spa=
n style=3D"white-space:normal;background-color:rgba(255,255,255,0)">AB</span=
></font></pre></div><div><br></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>manet mailing list</span><br><sp=
an><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mai=
lman/listinfo/manet</a></span><br></div></blockquote></body></html>=

--Apple-Mail-76CC3CDD-D40A-4189-B724-7A29682CB614--


From nobody Wed Sep 10 14:45:01 2014
Return-Path: <charliep@computer.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4507C1A0198 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 14:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fT_WeVjjGaw1 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 14:44:58 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id B2ECC1A0105 for <manet@ietf.org>; Wed, 10 Sep 2014 14:44:58 -0700 (PDT)
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1XRphB-00028Z-FZ; Wed, 10 Sep 2014 17:44:57 -0400
Message-ID: <5410C655.3090408@computer.org>
Date: Wed, 10 Sep 2014 14:44:53 -0700
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Blue Skies
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org><53CC9339.50103@computer.org> <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com>
In-Reply-To: <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000803060909050004090408"
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7aa9a42e603d0714bd44dc8886f08d51f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/lALIqkhf8EGs4KUR9z45AnjvvvE
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, manet@ietf.org
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 21:45:00 -0000

This is a multi-part message in MIME format.
--------------000803060909050004090408
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Hello Abdussalam,

The usual way for reactive protocols to offer operation
over unidirectional links is to have the RREP broadcast in
addition to broadcasting the RREQ.  That's an awfully
expensive operation to require when nodes already have
bidirectional links to their neighbors.  However, broadcast
RREP could be optional (and wouldn't affect interoperability
for bidirectional links, except for congestion).

Right now the document specifies a method for detecting
and avoiding unidirectional links, and I believe that is
appropriate for the current standard.

The idea of adding a bit to RREQ to request broadcast RREP
would work, and can easily be specified if approved by the
WG members.  It would probably affect only a remarkably
few lines of actual text in the document, and since the
mechanism has been studied quite a few times in the past
the results can be considered somewhat predictable.  But,
again, the extra congestion is a high price to pay unless it is
really needed to find unidirectional links -- which, by the
way, are likely to be more fragile as well.

Regards,
Charlie P.


On 9/10/2014 5:54 AM, Abdussalam Baryun wrote:
> I don't believe AODV only supports bidirectional, there are many work 
> out IETF done for that. I think there can be ways to make AODVv2 
> support unidirectional paths as well. As links in MANET can be 
> unidirectional and/or bidirectional. For example, the RREQ message 
> MUST indicate which type of route communication it is 
> requesting: bidirectional paths or unidirectional paths or mix (what 
> does authors/WG think?). We may need to update RFC6130 for AODVv2 as 
> well as done for OLSRv2.
>
> On Monday, July 21, 2014, Charles E. Perkins wrote:
>
>
>     Hello Chris,
>
>     Perhaps it would be better to identify the proper protocol method as
>     part of the applicability statement.  If no other means are
>     available, then
>     AODVv2 nodes could be required to use the blacklist mechanism, which
>     is intended to provide bidirectionality.
>
>
> Yes, ok, but I agree with Chris that the protocol needs to ensure 
> interoperability in all its normative body (e.g. the appendix is not 
> normative), so one required solution for the bidirectional issue, so 
> all implementations follow.
>
>
>     It seems unwise to require additional protocol mechanisms for cases
>     in which layer 2 already guarantees bidirectional links.  This
>     could also
>     be included as a statement within the applicability section.
>
>
> Yes, agree.
> AB

-- 
Regards,
Charlie P.


--------------000803060909050004090408
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    Hello Abdussalam,<br>
    <br>
    The usual way for reactive protocols to offer operation<br>
    over unidirectional links is to have the RREP broadcast in<br>
    addition to broadcasting the RREQ.Â  That's an awfully<br>
    expensive operation to require when nodes already have<br>
    bidirectional links to their neighbors.Â  However, broadcast<br>
    RREP could be optional (and wouldn't affect interoperability<br>
    for bidirectional links, except for congestion).<br>
    <br>
    Right now the document specifies a method for detecting<br>
    and avoiding unidirectional links, and I believe that is<br>
    appropriate for the current standard.<br>
    <br>
    The idea of adding a bit to RREQ to request broadcast RREP<br>
    would work, and can easily be specified if approved by the<br>
    WG members.Â  It would probably affect only a remarkably<br>
    few lines of actual text in the document, and since the<br>
    mechanism has been studied quite a few times in the past<br>
    the results can be considered somewhat predictable.Â  But,<br>
    again, the extra congestion is a high price to pay unless it is<br>
    really needed to find unidirectional links -- which, by the<br>
    way, are likely to be more fragile as well.<br>
    <br>
    Regards,<br>
    Charlie P.<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 9/10/2014 5:54 AM, Abdussalam Baryun
      wrote:<br>
    </div>
    <blockquote
cite="mid:CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com"
      type="cite">I don't believe AODV only supports bidirectional,
      there are many work out IETF done for that. IÂ think there can be
      ways to make AODVv2 support unidirectional paths as well. As links
      in MANETÂ can be unidirectional and/orÂ bidirectional. For
      example,Â the RREQ message MUST indicate which type of
      routeÂ communication it is requesting:Â bidirectional pathsÂ or
      unidirectional paths or mix (what does authors/WG think?).Â We may
      need to update RFC6130 for AODVv2Â as well asÂ done for OLSRv2.Â <br>
      <br>
      On Monday, July 21, 2014, Charles E. Perkins wrote:<br>
      <blockquote class="gmail_quote" style="margin:0 0 0
        .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
        Hello Chris,<br>
        <br>
        Perhaps it would be better to identify the proper protocol
        method as<br>
        part of the applicability statement.Â  If no other means are
        available, then<br>
        AODVv2 nodes could be required to use the blacklist mechanism,
        which<br>
        is intended to provide bidirectionality.</blockquote>
      <div><br>
      </div>
      <div>Yes, ok, but I agree with Chris that the protocol needs to
        ensure interoperability in all its normativeÂ body (e.g.
        theÂ appendix is not normative),Â soÂ one required solution for the
        bidirectionalÂ issue, so all implementations follow.Â <span></span></div>
      <div>Â </div>
      <blockquote class="gmail_quote" style="margin:0 0 0
        .8ex;border-left:1px #ccc solid;padding-left:1ex">
        <br>
        It seems unwise to require additional protocol mechanisms for
        cases<br>
        in which layer 2 already guarantees bidirectional links.Â  This
        could also<br>
        be included as a statement within the applicability section.</blockquote>
      <div><br>
      </div>
      <div>Yes, agree.Â </div>
      <div>Â </div>
      <div>AB</div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Regards,
Charlie P.</pre>
  </body>
</html>

--------------000803060909050004090408--


From nobody Wed Sep 10 15:53:48 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37F361A0354 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 15:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id flR94OXRyQfv for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 15:53:47 -0700 (PDT)
Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC93E1A02FB for <manet@ietf.org>; Wed, 10 Sep 2014 15:53:46 -0700 (PDT)
Received: by mail-yk0-f169.google.com with SMTP id 20so2154279yks.14 for <manet@ietf.org>; Wed, 10 Sep 2014 15:53:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nWJRt9eeBNZPvFx48XGxW+DInhoRaEoVLwjPFqDlw/w=; b=qJmRUKaIKP+U9KdBQmXZBRmFkIZNP3lv+fcQ6l3J4BOF6ibIxYi/eTDtOlmruS7fZi FpMuv4MHVWGKMUubBsKLNKm5bsiwKaqxWGYRaPmFJG1tyWVNc/zpbPKWzltCza2ZasZZ uASr8Fb3MewUjyWGDF0htAN92aKYGcEMKV9gsI3vX6b2hz0Q3PKrmnnjPpL8XeRyQo5d 7grt4aJcFMXrGJRYBAEfBREuJBoAqDOblK2TWs9vC1jbuduIyzGGUln6b2VprnfPhuJ+ l1WrAuPsSj6eKWvceIMG61sIoqLryJ3tVrEPqtintAV9AlUn8hjEAxebqLji7MXizhtl OIMA==
MIME-Version: 1.0
X-Received: by 10.236.121.44 with SMTP id q32mr64341739yhh.55.1410389626263; Wed, 10 Sep 2014 15:53:46 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Wed, 10 Sep 2014 15:53:46 -0700 (PDT)
In-Reply-To: <5410C655.3090408@computer.org>
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <CADnDZ8_ujvEJL1MzGxFrXbKDPSnsj-+RQZBxv_bszXFEKjbP=w@mail.gmail.com> <5410C655.3090408@computer.org>
Date: Thu, 11 Sep 2014 00:53:46 +0200
Message-ID: <CADnDZ88UyECPzeMKCtj+SjpJqhLWEHGV_b6jmx5x8vUcmWj1jA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Charles E. Perkins" <charliep@computer.org>
Content-Type: multipart/alternative; boundary=20cf300e512fab1de80502bdec35
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/zvPkfxLEGRF6yvkOLJ4mFGPS5yQ
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 22:53:48 -0000

--20cf300e512fab1de80502bdec35
Content-Type: text/plain; charset=UTF-8

Hi Charlie,

On Wednesday, September 10, 2014, Charles E. Perkins wrote:

>
> Hello Abdussalam,
>
> The usual way for reactive protocols to offer operation
> over unidirectional links is to have the RREP broadcast in
> addition to broadcasting the RREQ.  That's an awfully
> expensive operation to require when nodes already have
> bidirectional links to their neighbors.  However, broadcast
> RREP could be optional (and wouldn't affect interoperability
> for bidirectional links, except for congestion).
>
> Right now the document specifies a method for detecting
> and avoiding unidirectional links, and I believe that is
> appropriate for the current standard.
>

The subject says bidirectional paths, and my concern is also
considering unidirectional paths possibility. When draft says AODVv2 only
supports bidirectional links, I understand it as the links of the
originator router. So if originator knows its neighbours with
unidirectional then my suggestion can be valid and reasonable to solve
configuration of section 13.4.

However, I just gave my input suggestion, for this ticket.

AB

--20cf300e512fab1de80502bdec35
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Charlie,<br><br>On Wednesday, September 10, 2014, Charles E. Perkins  wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    Hello Abdussalam,<br>
    <br>
    The usual way for reactive protocols to offer operation<br>
    over unidirectional links is to have the RREP broadcast in<br>
    addition to broadcasting the RREQ.=C2=A0 That&#39;s an awfully<br>
    expensive operation to require when nodes already have<br>
    bidirectional links to their neighbors.=C2=A0 However, broadcast<br>
    RREP could be optional (and wouldn&#39;t affect interoperability<br>
    for bidirectional links, except for congestion).<br>
    <br>
    Right now the document specifies a method for detecting<br>
    and avoiding unidirectional links, and I believe that is<br>
    appropriate for the current standard.</div></blockquote><div><br></div>=
<div>The subject says bidirectional paths, and my concern is also consideri=
ng=C2=A0unidirectional paths=C2=A0possibility. When draft=C2=A0says=C2=A0AO=
DVv2 only supports bidirectional links, I understand it as the links of the=
 originator router.=C2=A0So if originator knows its neighbours with unidire=
ctional then my suggestion can be=C2=A0valid and reasonable to solve config=
uration of section 13.4.=C2=A0</div><div><br></div><div>However, I just gav=
e my input=C2=A0suggestion, for this ticket.=C2=A0</div><div><br></div><div=
>AB=C2=A0</div><div>=C2=A0</div>

--20cf300e512fab1de80502bdec35--


From nobody Wed Sep 10 16:02:41 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D80EB1A03B7 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 16:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8L8yKyk9uUYW for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 16:02:36 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8601A038C for <manet@ietf.org>; Wed, 10 Sep 2014 16:02:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=H7IKlXWXW/FyI/7sxjhcc9KrxjBGTuE5IoYdo4qBOgwlKb+84wNAvozA4QWDLS0i; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XRqtz-0004tR-15; Wed, 10 Sep 2014 19:02:15 -0400
Message-ID: <5410D875.9020706@earthlink.net>
Date: Wed, 10 Sep 2014 16:02:13 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Justin Dean <bebemaster@gmail.com>,  Abdussalam Baryun <abdussalambaryun@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <CADnDZ89DKyuf66_+oJ+p65qu=QDZxjdJBJvSQugLi7ydBd3RCw@mail.gmail.com> <CA+-pDCdxYAwjs9gmpK7o_FNdkmK9dmsoqbUFqJjOKHo8QeOSPQ@mail.gmail.com>
In-Reply-To: <CA+-pDCdxYAwjs9gmpK7o_FNdkmK9dmsoqbUFqJjOKHo8QeOSPQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac716debf34cf2eaf18377253abe4969ad0350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/gnAyiWwgLJGeCO_6lOHtBHl-9NM
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, manet@ietf.org
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 23:02:39 -0000

Hello Justin,

Follow up below, omitting some of your text...

On 9/8/2014 6:51 PM, Justin Dean wrote:
>
>
> The root of the issue is assigning semantics to the order of the 
> addresses which AODVv2 currently does

No, the addresses can appear in any order.  This was fixed a long time ago.

Regards,
Charlie P.


From nobody Wed Sep 10 16:15:25 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE751A03BB for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 16:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.753
X-Spam-Level: 
X-Spam-Status: No, score=-1.753 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKvbVJfjNfVT for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 16:15:23 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id 198191A03B7 for <manet@ietf.org>; Wed, 10 Sep 2014 16:15:23 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ekm3Bt4vY6atO7sWXnglcANHh96heXsRtwSXl488Tq0ob9n+Kl9GYa9iOYh4deE4; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XRr6f-0003xg-Vs; Wed, 10 Sep 2014 19:15:22 -0400
Message-ID: <5410DB88.3090902@earthlink.net>
Date: Wed, 10 Sep 2014 16:15:20 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Henning Rogge <hrogge@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <CAGnRvupW4vq9Uo74i_x_ujVpj7h-3o9sMTiJFsyaKZ4GRBq-AA@mail.gmail.com>
In-Reply-To: <CAGnRvupW4vq9Uo74i_x_ujVpj7h-3o9sMTiJFsyaKZ4GRBq-AA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7c75bfa7e3d7e4e7ab5694b301553d057350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ttP-BMK2ZV-Rs12hOnDJdDi7Yyk
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 23:15:24 -0000

Hello Henning,

On 9/8/2014 10:52 PM, Henning Rogge wrote:
>
>> However, I think it is pretty bad when a message bundling system
>> imposes these collateral constraints.  I reckon it was another
>> unintended consequence.
> requiring a certain IP-TTL is a constraint too.

This is mixing apples and oranges.

A *particular* routing protocol may well need be able to deal with
such matters.

An over-arching message-bundling protocol should never take
the permanent step of preventing all future routing protocols from
dealing with such matters.


>
>> There's nothing wrong with attempting to use multiple security
>> measures.  As far as I know, it's usually considered praiseworthy.
> Its a BAD thing to make one weak security option mandatory as part of
> the core protocol.

That's debatable, and I wonder why RFC 5082 would be published if
it were as bad as you say.  Indeed, if one has a network where most
of the routers obey the rules, the security option works O.K. as
designed.

For your more general point, it's basically incorrect I think.  For
instance, a 12-foot brick wall with machine gun turrets would make
my front door lock seem to be quite puny.  And most people consider
it mandatory to lock their front door.

And, even a simple unlocked door ought to be closed to provide the
small bit of security against skunks walking in the house.

This is a quite useful analogy.  Many times, small steps to improve
security are indeed additive, even if none is perfect by itself. For a
trivial example, one security mechanism may only work for wrongs
in the vertical direction, and another may only protect against
wrongs in horizontal directions.  With another few minutes work,
I reckon I could exhibit more relevant examples and I strongly
suspect you could also.


Regards,
Charlie P.


From nobody Wed Sep 10 16:17:15 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAD21A03CD for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 16:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wM3UAs99PGHn for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 16:17:13 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id AB2F31A038C for <manet@ietf.org>; Wed, 10 Sep 2014 16:17:13 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=h77s7A0ERiwPWHtZojZEGlpwMLhozQh6ge+evORTi4R8iYC/iJmysxfuN5hQmg6M; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XRr8S-0004x0-L7; Wed, 10 Sep 2014 19:17:12 -0400
Message-ID: <5410DBF7.2080405@earthlink.net>
Date: Wed, 10 Sep 2014 16:17:11 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christopher Dearlove <christopher.dearlove@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com>
In-Reply-To: <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac77cbc6b2f260909f2d48c9f2f4cb77dd4350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/uxXoSNVtLPlft6YeSXHtOXeY-ug
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 23:17:14 -0000

Hello Chris,

On 9/8/2014 11:29 PM, Christopher Dearlove wrote:
> And no one has said its a bad idea to use 5082 (though it's not the only option). Just that it's a 5444 multiplexer level decision, not an AODVv2 level decision.
>

That's fine with me.  How do I instruct RFC 5444 to set TTL==255?

Regards,
Charlie P.


From nobody Wed Sep 10 16:54:15 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 510421A0320 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 16:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8tV78wUh09F0 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 16:54:03 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E8A01A0197 for <manet@ietf.org>; Wed, 10 Sep 2014 16:54:03 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id z12so4800088wgg.4 for <manet@ietf.org>; Wed, 10 Sep 2014 16:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:from:subject:date:to; bh=zhragBLN2j+kLlmWB8HqrPTrWyUCdTXu4cHQy0aKK1g=; b=wFJqowiKC85rKvmYzyf2SC0oXHPRSc4DDNGBiqGcPCJqCpu1mOov0sz3XLgSMT9xl7 u5jPcsz/lwgSRYwCUTBC8cdy9CCmJTyYDMGGCKgJV5R0jPtTu63UQAxdyXiED80UUiv9 b0z9NTCy2Z0nQe6GLyxS/IYdOjWDFCrRL1pK7M9BLdniwNNplXxiGvhGzGuTP/6aIOQV iw1DEQ0EIVQNGiElDpQo3NeU/hSc4ae/iaG81qQDazs8kKVmaalaqEE2fRADYOY3tD+X SfDZzreb/vDP1kATJYJgQ51hqnxSRujHhPZlJ7jPEq8yTMOoDFOLd8iluQeoYLsjfOlm 13QA==
X-Received: by 10.180.211.233 with SMTP id nf9mr2763176wic.33.1410393241790; Wed, 10 Sep 2014 16:54:01 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id t9sm20246684wjf.41.2014.09.10.16.54.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Sep 2014 16:54:00 -0700 (PDT)
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net>
In-Reply-To: <5410DBF7.2080405@earthlink.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <30E24AA0-51B8-410A-A37E-649994CDE291@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Thu, 11 Sep 2014 00:53:57 +0100
To: Charlie Perkins <charles.perkins@earthlink.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/dKQbrZ2JyN2qyN59Kx17RWhcD3s
Cc: "<draft-ietf-manet-aodvv2@tools.ietf.org>" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 23:54:13 -0000

Now it depends who "I" is. If "I" is the overall system design you can do it=
 as part of that. If "I" is AODVv2, you don't. It's not within an individual=
 routing protocol's competence. Like many other things.

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 11 Sep 2014, at 00:17, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
>=20
> Hello Chris,
>=20
>> On 9/8/2014 11:29 PM, Christopher Dearlove wrote:
>> And no one has said its a bad idea to use 5082 (though it's not the only o=
ption). Just that it's a 5444 multiplexer level decision, not an AODVv2 leve=
l decision.
>=20
> That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255?
>=20
> Regards,
> Charlie P.
>=20


From nobody Wed Sep 10 22:25:07 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8641A0459 for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 22:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fz9hM82M8xvF for <manet@ietfa.amsl.com>; Wed, 10 Sep 2014 22:25:03 -0700 (PDT)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61FCB1A03C8 for <manet@ietf.org>; Wed, 10 Sep 2014 22:25:03 -0700 (PDT)
Received: by mail-qg0-f53.google.com with SMTP id q108so3095440qgd.12 for <manet@ietf.org>; Wed, 10 Sep 2014 22:25:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ObimMV+Ef1TiOHiP0sNGWhaE3QaBZbnAnuLIEaoiCTg=; b=UVRWi5/n7Fa78MeXu5Du6kjFVQMUxEgdabh5XzS1EvM9CzhinPuUj6dMzj6ZZetMw/ G+4u/BOaNTY6rWKLcbBEFbDv5MCo01NAsXXth4kWnV3bGVkm5+xTJw1yUW0z9SBpn/VI OeQUzuFnYX7902ApGnqDRa8OR/BaO+iL+q1gmuH+GcihB/GEBlo8HMdBgR1/AfSRVI1H xW/F0pke8jhc2Cx3lHW1bK1j1uFcHjY9OSL8j0lw3Kx8rF0TWJiyP4DCZNZtUy2dB46T 4PW85lzFFO20LMe0WrZY424O9mb/AM3YMkyTiSuZO3zFQ+kPBjXNPKdwqI/Rf2hogTPm jPaA==
X-Received: by 10.140.27.173 with SMTP id 42mr65813122qgx.59.1410413102639; Wed, 10 Sep 2014 22:25:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Wed, 10 Sep 2014 22:24:42 -0700 (PDT)
In-Reply-To: <5410DBF7.2080405@earthlink.net>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 11 Sep 2014 07:24:42 +0200
Message-ID: <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com>
To: Charlie Perkins <charles.perkins@earthlink.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/0fZVczXpArUK0d8zfkwjCBXASec
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 05:25:05 -0000

On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
<charles.perkins@earthlink.net> wrote:
>
> Hello Chris,
>
> That's fine with me.  How do I instruct RFC 5444 to set TTL==255?

On protocol level? Put it into the right document (e.g. the "rfc5444
security practices" or whatever).

On implementation level? Just as you do now, just a line of code in
the right place.

Would be the "use IP-TTL 255 as an additional security measurement"
part of the AODVv2 protocol? No, because the protocol should only deal
with the messages so its easy to mix with the other protocols using
RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
of symmetric links). But of course it would be part of some (maybe not
all) AODVv2 implementations (some might implement other security
measurements).

Henning Rogge


From nobody Thu Sep 11 02:57:53 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E1EA1A8919 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 02:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7YObcsVeUss for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 02:57:51 -0700 (PDT)
Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC9B41A8918 for <manet@ietf.org>; Thu, 11 Sep 2014 02:57:50 -0700 (PDT)
Received: by mail-yh0-f50.google.com with SMTP id 29so2839293yhl.23 for <manet@ietf.org>; Thu, 11 Sep 2014 02:57:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=isVu627Xtm4qHHgu0Nh67KC8MyGqHNvycsiO3TjgyA8=; b=buS4SFcK0t6HfWuUFO89Tv4suDbvj6e1vivyVxQ5Vl/GFJogVJCYLtgA7rvjIhjXVu xgO2IEMCYXDVrjLCEiVDkR+8Q4rdqbndUnLDQqyHNrHf7Cp4C0F+X1zb/TxOoCFT3ANu fm8HAQmagAPvGAR82BVuio6tJX2DTsLc0pIZmi+82QT9NcFvRVSaTnDfaUH6sU/H80B3 pZMVtpPxxryiHihV1+8Xk+KpXDDnWjBTnvrDPKhJIVdVj7aisHrw6ftKDurwLVyUg3L4 X0CpqvuD2bBYXS0eNTm8kIk9Zy2dgZfV3Ua8tzlD3D/3rhlEw1zXjFBGlZe085UxArv/ Cm7g==
MIME-Version: 1.0
X-Received: by 10.236.114.131 with SMTP id c3mr70325474yhh.56.1410429470255; Thu, 11 Sep 2014 02:57:50 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Thu, 11 Sep 2014 02:57:50 -0700 (PDT)
In-Reply-To: <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com>
Date: Thu, 11 Sep 2014 11:57:50 +0200
Message-ID: <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Content-Type: multipart/alternative; boundary=20cf303ea83a8e2ec40502c7335c
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/rNgRBxqMPJCaiUH_1kwGImhsLr4
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 09:57:52 -0000

--20cf303ea83a8e2ec40502c7335c
Content-Type: text/plain; charset=UTF-8

On Thursday, September 11, 2014, Henning Rogge wrote:

> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
> <charles.perkins@earthlink.net <javascript:;>> wrote:
> >
> > Hello Chris,
> >
> > That's fine with me.  How do I instruct RFC 5444 to set TTL==255?
>
> On protocol level? Put it into the right document (e.g. the "rfc5444
> security practices" or whatever).
>
> On implementation level? Just as you do now, just a line of code in
> the right place.



For interoperability purposes the right place is within AODVv2
implementation. For independent purposes the right place is AODVv2. Chris
answered it as part of overall-system but still no definition for that as
IETF standard, so does that mean writing another draft to update the
system.


>
> Would be the "use IP-TTL 255 as an additional security measurement"
> part of the AODVv2 protocol? No, because the protocol should only deal
> with the messages so its easy to mix with the other protocols using
> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
> of symmetric links).


Those protocols can be updated for AODVv2 functions. Those protocols are
servants to routing protocols so they should follow.


> But of course it would be part of some (maybe not
> all) AODVv2 implementations (some might implement other security
> measurements).


So do you agree the right place is AODVv2. Overall, this design problem is
because the WG wrongly decided to design the packet before the functions
and to make routing functions serve RFC5444 within a unified multiplex
method.

AB

--20cf303ea83a8e2ec40502c7335c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Thursday, September 11, 2014, Henning Rogge  wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins<br>
&lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;char=
les.perkins@earthlink.net&#39;)">charles.perkins@earthlink.net</a>&gt; wrot=
e:<br>
&gt;<br>
&gt; Hello Chris,<br>
&gt;<br>
&gt; That&#39;s fine with me.=C2=A0 How do I instruct RFC 5444 to set TTL=
=3D=3D255?<br>
<br>
On protocol level? Put it into the right document (e.g. the &quot;rfc5444<b=
r>
security practices&quot; or whatever).<br>
<br>
On implementation level? Just as you do now, just a line of code in<br>
the right place.</blockquote><div><br></div><div><br></div><div>For interop=
erability purposes the right place is within AODVv2 implementation. For ind=
ependent purposes the right place is AODVv2. Chris answered it as part of o=
verall-system but still no definition for that as IETF=C2=A0standard, so do=
es that mean writing another draft to update the system.=C2=A0</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
<br>
Would be the &quot;use IP-TTL 255 as an additional security measurement&quo=
t;<br>
part of the AODVv2 protocol? No, because the protocol should only deal<br>
with the messages so its easy to mix with the other protocols using<br>
RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection<br>
of symmetric links).=C2=A0</blockquote><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blo=
ckquote><div><br></div><div>Those protocols can be updated for AODVv2 funct=
ions. Those protocols are servants to routing protocols so they should=C2=
=A0follow.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But o=
f course it would be part of some (maybe not<br>
all) AODVv2 implementations (some might implement other security<br>
measurements).</blockquote><div><br></div><div>So do you agree the right pl=
ace is AODVv2. Overall, this design=C2=A0problem is because the WG wrongly =
decided to design the packet before the functions and to=C2=A0make routing =
functions serve RFC5444 within a unified multiplex method.=C2=A0</div><div>=
<br></div><div>AB=C2=A0</div>

--20cf303ea83a8e2ec40502c7335c--


From nobody Thu Sep 11 03:03:02 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D90771A8912 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 03:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qvTJcVfF3EdE for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 03:02:59 -0700 (PDT)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3B0E1A06C8 for <manet@ietf.org>; Thu, 11 Sep 2014 03:02:58 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id k48so4274125wev.27 for <manet@ietf.org>; Thu, 11 Sep 2014 03:02:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=8FNGPFocF+b3tA/XRXKYkxoNShPY8T9aG8w4mVFYXaM=; b=IcHszwhfOj+DaaWeRI9PU3tzgvzotraAh81guYNomPmSDnX55SJcvnn9RY3CU9X8jL +reraEf7g90OV7TppOv8d0rS3uWJTrWh7DPOuYYQJiVUqgTwOkfx56TmCRGn6KLjxZb1 aF8CveSuAc/DT2+L0GOhlYITigHjmqyfdO6EX6TlOmn0FQhC+F7Lu+s0Vr99K4u0X2d4 otpcNkOdvLTHuLbyWj3QMv9PN1GjkoTQP2Vh2JhDYnPnmmKxD3VWAai/WEWvlZqwJ6fS pB7MdXRh2+FhCBWDsUfnvYO5+uuvz8qs+fyBsJa6aeAdU4ghWcw6IqZgdNejOejfxXcH +X4g==
X-Received: by 10.180.223.68 with SMTP id qs4mr5573279wic.10.1410429777659; Thu, 11 Sep 2014 03:02:57 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id n3sm5393594wiy.10.2014.09.11.03.02.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 03:02:56 -0700 (PDT)
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-6250B984-CB94-41FF-8D8E-C1BBE806CFCA
Content-Transfer-Encoding: 7bit
Message-Id: <10DF7F11-9EB0-4332-9A42-176EB9E75B64@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Thu, 11 Sep 2014 11:02:53 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/apn6bK8UPL25tXegiIN-xP6Jw1w
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 10:03:01 -0000

--Apple-Mail-6250B984-CB94-41FF-8D8E-C1BBE806CFCA
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Henning is right, you are wrong. I could explain why, but that's already bee=
n done more than once.

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 11 Sep 2014, at 10:57, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
>=20
>=20
>=20
>> On Thursday, September 11, 2014, Henning Rogge wrote:
>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>> <charles.perkins@earthlink.net> wrote:
>> >
>> > Hello Chris,
>> >
>> > That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255?
>>=20
>> On protocol level? Put it into the right document (e.g. the "rfc5444
>> security practices" or whatever).
>>=20
>> On implementation level? Just as you do now, just a line of code in
>> the right place.
>=20
>=20
> For interoperability purposes the right place is within AODVv2 implementat=
ion. For independent purposes the right place is AODVv2. Chris answered it a=
s part of overall-system but still no definition for that as IETF standard, s=
o does that mean writing another draft to update the system.=20
> =20
>>=20
>> Would be the "use IP-TTL 255 as an additional security measurement"
>> part of the AODVv2 protocol? No, because the protocol should only deal
>> with the messages so its easy to mix with the other protocols using
>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>> of symmetric links).=20
>=20
>=20
> Those protocols can be updated for AODVv2 functions. Those protocols are s=
ervants to routing protocols so they should follow.=20
> =20
>> But of course it would be part of some (maybe not
>> all) AODVv2 implementations (some might implement other security
>> measurements).
>=20
> So do you agree the right place is AODVv2. Overall, this design problem is=
 because the WG wrongly decided to design the packet before the functions an=
d to make routing functions serve RFC5444 within a unified multiplex method.=
=20
>=20
> AB=20

--Apple-Mail-6250B984-CB94-41FF-8D8E-C1BBE806CFCA
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Henning is right, you are wrong. I could explain why, but that's already been done more than once.<br><br>--&nbsp;<div>Christopher Dearlove</div><div><a href="mailto:christopher.dearlove@gmail.com">christopher.dearlove@gmail.com</a> (iPhone)</div><div><a href="mailto:chris@mnemosyne.demon.co.uk">chris@mnemosyne.demon.co.uk</a> (home)</div></div><div><br>On 11 Sep 2014, at 10:57, Abdussalam Baryun &lt;<a href="mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><br><br>On Thursday, September 11, 2014, Henning Rogge  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins<br>
&lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'charles.perkins@earthlink.net')">charles.perkins@earthlink.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Hello Chris,<br>
&gt;<br>
&gt; That's fine with me.&nbsp; How do I instruct RFC 5444 to set TTL==255?<br>
<br>
On protocol level? Put it into the right document (e.g. the "rfc5444<br>
security practices" or whatever).<br>
<br>
On implementation level? Just as you do now, just a line of code in<br>
the right place.</blockquote><div><br></div><div><br></div><div>For interoperability purposes the right place is within AODVv2 implementation. For independent purposes the right place is AODVv2. Chris answered it as part of overall-system but still no definition for that as IETF&nbsp;standard, so does that mean writing another draft to update the system.&nbsp;</div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Would be the "use IP-TTL 255 as an additional security measurement"<br>
part of the AODVv2 protocol? No, because the protocol should only deal<br>
with the messages so its easy to mix with the other protocols using<br>
RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection<br>
of symmetric links).&nbsp;</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote><div><br></div><div>Those protocols can be updated for AODVv2 functions. Those protocols are servants to routing protocols so they should&nbsp;follow.&nbsp;</div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But of course it would be part of some (maybe not<br>
all) AODVv2 implementations (some might implement other security<br>
measurements).</blockquote><div><br></div><div>So do you agree the right place is AODVv2. Overall, this design&nbsp;problem is because the WG wrongly decided to design the packet before the functions and to&nbsp;make routing functions serve RFC5444 within a unified multiplex method.&nbsp;</div><div><br></div><div>AB&nbsp;</div>
</div></blockquote></body></html>
--Apple-Mail-6250B984-CB94-41FF-8D8E-C1BBE806CFCA--


From nobody Thu Sep 11 03:10:29 2014
Return-Path: <john.dowdell.ietf@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A23031A892A for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 03:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.888
X-Spam-Level: 
X-Spam-Status: No, score=-0.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6u7dVZJ13YE8 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 03:10:27 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4F201A8919 for <manet@ietf.org>; Thu, 11 Sep 2014 03:10:26 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id t60so5416995wes.25 for <manet@ietf.org>; Thu, 11 Sep 2014 03:10:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=21N89L2mMP6H0eVWg9zJ1xKsPGemwmkoV+64iPyGt/M=; b=lR9YFsVhEboGeRMVrcABYDELvVUcoqp65Irg4CqxcESiwP6zyPSrrD/xAGTgPHdme6 NF8DqBjDIM7aKZgOelolkaSCel9uuvJr5z5XD8t78ln6sXA9kxVt+gX+DnzBH2UAVGiY Is23xY5n2qEGSg9fnoPDF31+kKN9pCFkto6H5tx5Zg5ssKX1IXRPwlc9cA/EHcZZrkOC 4m+LZh8HYIhuZwHZ/ijEXwqmbbsq2f9HL7kbnzC+s4lBUFffkhUTdQGvD83cz2nuMmpv LLhaGQX4SnE4QfoIE0a7wxIZucaqDd2F3camgv8fR4osnW51QAQIMKYeu4fLP8iuZidw MoMQ==
X-Received: by 10.180.20.6 with SMTP id j6mr909005wie.64.1410430225149; Thu, 11 Sep 2014 03:10:25 -0700 (PDT)
Received: from [10.0.4.178] ([217.158.48.187]) by mx.google.com with ESMTPSA id g8sm991971wiy.19.2014.09.11.03.10.24 for <manet@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Sep 2014 03:10:24 -0700 (PDT)
Message-ID: <5411750F.9050303@gmail.com>
Date: Thu, 11 Sep 2014 11:10:23 +0100
From: John Dowdell <john.dowdell.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: manet@ietf.org
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECC2@GLKXM0002V.GREENLNK.net> <CADnDZ88OMOTUc7Btbf9TP57NT58R4Z4rM8t58mX-6=k21GPrDg@mail.gmail.com>
In-Reply-To: <CADnDZ88OMOTUc7Btbf9TP57NT58R4Z4rM8t58mX-6=k21GPrDg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050507000502020803000509"
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/UwkP4r1vbquZObIKKd_c0ej3xo4
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 10:10:28 -0000

This is a multi-part message in MIME format.
--------------050507000502020803000509
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Abdussalam

I have already spotted that one in my review and it has been discussed 
within the author team. But thanks anyway.

John

On 10/09/14 21:50, Abdussalam Baryun wrote:
>
>
> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>
>     The key thing is that two independent implementations need to
>     interoperate and not use unidirectional links. At the moment that
>     wouldn't happen.
>
>
> In draft's applicability statement:
>
> ---- OLD EDIT-----
> AODVv2 only supports bidirectional links.  In the case of possible unidirectional links, either blacklists (seeSection 5.2) or other means (e.g. adjacency establishment with only neighboring routers that have bidirectional communication as indicated by NHDP [RFC6130]) of assuring and monitoring bidirectionality are recommended. Otherwise, persistent packet loss or persistent protocol failures could occur.  The cost of bidirectional link L (denoted Cost(L)) may depend upon the direction across the link for which the cost is measured.  If received over a link that is unidirectional, metric information from incoming AODVv2 messages SHOULD NOT be used for route table updates.
>
> ---- NEW EDIT -----
> AODVv2 only supports bidirectional links.  In the case of possible unidirectional links, the protocol MUST use blacklists (see Section 5.2), otherwise may use means (e.g. adjacency establishment with only neighboring routers that have bidirectional communication as indicated by NHDP [RFC6130]) of assuring and monitoring bidirectionality are recommended. Otherwise, persistent packet loss or persistent protocol failures could occur.
> -------------
> Move the below text to another suitable section which I recommend section 5.2.
> {{{
> The cost of bidirectional link L (denoted Cost(L)) may depend upon the direction across the link for which the cost is measured.  If received over a link that is unidirectional, metric information from incoming AODVv2 messages SHOULD NOT be used for route table updates.
> }}}
>
> AB
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


--------------050507000502020803000509
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Abdussalam<br>
    <br>
    I have already spotted that one in my review and it has been
    discussed within the author team. But thanks anyway.<br>
    <br>
    John<br>
    <br>
    <div class="moz-cite-prefix">On 10/09/14 21:50, Abdussalam Baryun
      wrote:<br>
    </div>
    <blockquote
cite="mid:CADnDZ88OMOTUc7Btbf9TP57NT58R4Z4rM8t58mX-6=k21GPrDg@mail.gmail.com"
      type="cite"><br>
      <br>
      On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:<br>
      <blockquote class="gmail_quote" style="margin:0 0 0
        .8ex;border-left:1px #ccc solid;padding-left:1ex">The key thing
        is that two independent implementations need to interoperate and
        not use unidirectional links. At the moment that wouldn't
        happen.<br>
        <br>
      </blockquote>
      <div><br>
      </div>
      <div>In draft's applicability statement: </div>
      <div><br>
      </div>
      <div>---- OLD EDIT-----</div>
      <div>
        <div class="page" title="Page 9">
          <div class="section">
            <div class="layoutArea">
              <div class="column">
                <pre><span style="font-size:10.000000pt;font-family:'Courier'">AODVv2 only supports bidirectional links.  In the case of possible unidirectional links, either blacklists (see </span><span style="font-size:10.000000pt;font-family:'Courier';color:rgb(0.000000%,0.000000%,100.000000%)">Section 5.2</span><span style="font-size:10.000000pt;font-family:'Courier'">) or other means (e.g. adjacency establishment with only neighboring routers that have bidirectional communication as indicated by NHDP [</span><span style="font-size:10.000000pt;font-family:'Courier';color:rgb(0.000000%,0.000000%,100.000000%)">RFC6130</span><span style="font-size:10.000000pt;font-family:'Courier'">]) of assuring and monitoring bidirectionality are recommended. Otherwise, persistent packet loss or persistent protocol failures could occur.  The cost of bidirectional link L (denoted Cost(L)) may depend upon the direction across the link for which the cost is measured.  If received over a link that is 
 u
nidirectional, metric information from incoming AODVv2 messages SHOULD NOT be used for route table updates.</span></pre>
              </div>
            </div>
          </div>
        </div>
      </div>
      <div><br>
      </div>
      <div>---- NEW EDIT ----- </div>
      <div>
        <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">AODVv2 only supports bidirectional links.  In the case of possible unidirectional links, the protocol MUST use blacklists (see Section 5.2), otherwise may use means (e.g. adjacency establishment with only neighboring routers that have bidirectional communication as indicated by NHDP [RFC6130]) of assuring and monitoring bidirectionality are recommended. Otherwise, persistent packet loss or persistent protocol failures could occur.  </span></font></pre>
        <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">-------------</span></font></pre>
        <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">Move the below text to another suitable section which I recommend section 5.2. </span></font></pre>
        <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">{{{</span></font></pre>
        <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">The cost of bidirectional link L (denoted Cost(L)) may depend upon the direction across the link for which the cost is measured.  If received over a link that is unidirectional, metric information from incoming AODVv2 messages SHOULD NOT be used for route table updates.</span></font></pre>
        <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">}}}</span></font></pre>
        <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">
</span></font></pre>
        <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">AB</span></font></pre>
      </div>
      <div><br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
manet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050507000502020803000509--


From nobody Thu Sep 11 03:21:58 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8F661A8919 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 03:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJIidCg5YssP for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 03:21:55 -0700 (PDT)
Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96E551A06C8 for <manet@ietf.org>; Thu, 11 Sep 2014 03:21:55 -0700 (PDT)
Received: by mail-qc0-f171.google.com with SMTP id x3so21408761qcv.30 for <manet@ietf.org>; Thu, 11 Sep 2014 03:21:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=WcZBJbQoOIEIAwwATckI7czRp0Vcj+8T/VC2qmbTKgY=; b=IWWqLs57XCSSTyqvLWSok1xxrz5s/WNuC450H80m2WVcf/gJEjWzdRqIJPBKfBd6uk eRBbRMLkTHlNFsSZSu3uBzzg6Z5QAtN4q9OBWtp9Dm2wNwQ4+th0CxmFHn14Op8nopOF oQ58F0gjwMSRQOsFjhs1f16RYzCDfB6ewidusQVgWcoltqksDMSnOU+lQ/Eh9joNOgIp ejCSPsPbKPhweL21qT9jxPsOmFJ/5/X3/5pdj1WXNvVok466siz/NPCKstxckok0EGbu XhuhN5qAFYmKwltlwIhNNzntS8LQCDQlJJQp+qylOTHYLc5k0gueTSVWxxMks7Z3oINn htug==
X-Received: by 10.224.7.197 with SMTP id e5mr33987qae.58.1410430914833; Thu, 11 Sep 2014 03:21:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Thu, 11 Sep 2014 03:21:34 -0700 (PDT)
In-Reply-To: <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@mail.gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 11 Sep 2014 12:21:34 +0200
Message-ID: <CAGnRvuocJmN0rCWNoO0soOFKeuy00v6YNT=nZSk25hVM5b5mNQ@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/HalG6psUHmiZC6M7OUe3jGTbunA
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 10:21:56 -0000

On Thu, Sep 11, 2014 at 11:57 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> So do you agree the right place is AODVv2.

No, I do NOT.

Maybe you should try to read and understand my mail.

As I said, on protocol level (which means the RFCs defining the
protocol) the AODVv2 document is NOT the right place for this.

As for implementations... ALL routing protocol implementations are
drawing from multiple documents to do their job.

> Overall, this design problem is
> because the WG wrongly decided to design the packet before the functions and
> to make routing functions serve RFC5444 within a unified multiplex method.

The problem is that you just don't understand whats the reason behind
the document split.

In fact it would have been even better if the MPR handling woud also
have been split into its own document so it can be reused easier
without referring to the OLSRv2 RFC. Its works the way it is, but
splitting it would have been more elegant (but it would have delayed
OLSRv2 even more).

Henning Rogge


From nobody Thu Sep 11 04:13:11 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29D0F1A8930 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:13:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ezdp_ulEHnE5 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:13:00 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82DE41A8957 for <manet@ietf.org>; Thu, 11 Sep 2014 04:12:37 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id em10so3690676wid.16 for <manet@ietf.org>; Thu, 11 Sep 2014 04:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=muY62KuT1vHoo+ajxOEFM2zdkNH12OeqjQfJzM3lOww=; b=VM3Om3AIqZMVvYBuoVqOY9XlI6kowDbdj31dvHELLnAowVg9istWo2UgSldvOMeMh0 LGt9DIWpUbNRJD8/dY+M5Imcy2SSYQ+q0EUarrBNinIqQz6kJLbtZeOFlyJzhlGLs9pL VP8lFylJdIGh17Rpb0uRF3ZD9R2lV57Fka3qIQyZ1nIx27h4iy9vdZMD5gVCu3K9e4l2 nkRFFnhseohIW7Xzk2Oi/7p2YiBmZdy7d2YUSqtAGIa7VxYrtXnp32Djcyiyyk5qu1Rf ID3QRvmxXCjHHiIShE/Y0NxdpmtpoChRVnhlY+tnvFxIhCg4o5EkyLsXPt4XSslsI6UC OeGQ==
X-Received: by 10.180.160.229 with SMTP id xn5mr6137264wib.64.1410433956007; Thu, 11 Sep 2014 04:12:36 -0700 (PDT)
Received: from [192.168.254.1] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id cy10sm847981wjb.21.2014.09.11.04.12.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 04:12:35 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Christopher Dearlove <christopher.dearlove@gmail.com>
In-Reply-To: <CAGnRvuocJmN0rCWNoO0soOFKeuy00v6YNT=nZSk25hVM5b5mNQ@mail.gmail.com>
Date: Thu, 11 Sep 2014 12:12:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <02FA236C-E416-4D88-AAE0-CEF29AC1776F@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@mail.gmail.com> <CAGnRvuocJmN0rCWNoO0soOFKeuy00v6YNT=nZSk25hVM5b5mNQ@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/hLzLJHHOSa-f0S1jy26JxPzHv1c
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 11:13:07 -0000

Henning has addressed the other issues. I'll mention one.

On 11 Sep 2014, at 11:21, Henning Rogge wrote:
> In fact it would have been even better if the MPR handling woud also
> have been split into its own document so it can be reused easier
> without referring to the OLSRv2 RFC. Its works the way it is, but
> splitting it would have been more elegant (but it would have delayed
> OLSRv2 even more).

Completely agree. And in fact that's not the only thing I (we I believe) =
would have split out in an ideal world. Next on my list would be the =
processing and forwarding mechanism in OLSRv2 that is designed for use =
by message types other than just TC messages.

But we were delayed enough as it was.


From nobody Thu Sep 11 04:16:18 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 230CE1A06EB for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2U7s52SdlQm for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:16:15 -0700 (PDT)
Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C7C61A06D7 for <manet@ietf.org>; Thu, 11 Sep 2014 04:16:14 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id dc16so86889qab.20 for <manet@ietf.org>; Thu, 11 Sep 2014 04:16:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=oxV7LuypQNMBIsOzAUHVuWgVb/ig3nDwT7dseZrnMZs=; b=JBQOu3ZyQZESjlvjGyrfGBZIJWxxOI+5iYenyQY1AI5lr6BTav+ceSiBuRtwEjgeNq dNDhXBeTkJp0R+swyawGoQekq3DtAURAocNqoQQ297bO8eZ/Vf3hPz+nlqNkauPiNhG2 AInq50FRYlqwMyW6Eq7iXim09rQws+q2SEADpqdmXnGGlBuwgQuxxUHlaJeXoGKfs+DU oNEgD1kiF5Ldnq6wvZ0o0FTvbwUKyZDthKo7l/tqtne06TzD4BZ/cJ6HFI6acYaLi/YP JSZfvVcgy+0tySDOE0LFiu+MZoFWS2nZJ2gZ5Vz/fKFRDGmkEaZvHYOaFyZQsSc0xDxp nc1g==
X-Received: by 10.224.7.197 with SMTP id e5mr391706qae.58.1410434173418; Thu, 11 Sep 2014 04:16:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Thu, 11 Sep 2014 04:15:52 -0700 (PDT)
In-Reply-To: <02FA236C-E416-4D88-AAE0-CEF29AC1776F@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@mail.gmail.com> <CAGnRvuocJmN0rCWNoO0soOFKeuy00v6YNT=nZSk25hVM5b5mNQ@mail.gmail.com> <02FA236C-E416-4D88-AAE0-CEF29AC1776F@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 11 Sep 2014 13:15:52 +0200
Message-ID: <CAGnRvuptV4JYm1+W_9mhhsR0s3=+BjdjFvYDW00qVetX3cen3A@mail.gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/oSbRp6K2sfJ7E1h1Ui2ubd6iTgE
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 11:16:16 -0000

On Thu, Sep 11, 2014 at 1:12 PM, Christopher Dearlove
<christopher.dearlove@gmail.com> wrote:
> Henning has addressed the other issues. I'll mention one.
>
> On 11 Sep 2014, at 11:21, Henning Rogge wrote:
>> In fact it would have been even better if the MPR handling woud also
>> have been split into its own document so it can be reused easier
>> without referring to the OLSRv2 RFC. Its works the way it is, but
>> splitting it would have been more elegant (but it would have delayed
>> OLSRv2 even more).
>
> Completely agree. And in fact that's not the only thing I (we I believe) =
would have split out in an ideal world. Next on my list would be the proces=
sing and forwarding mechanism in OLSRv2 that is designed for use by message=
 types other than just TC messages.

In fact I moved both of them out of the OLSRv2 core code in my implementati=
on.

Henning Rogge


From nobody Thu Sep 11 04:25:20 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26A311A06FC for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DH0TVHfFlnvt for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:25:16 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 938651A06F2 for <manet@ietf.org>; Thu, 11 Sep 2014 04:25:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 6D884260EB7; Thu, 11 Sep 2014 04:25:16 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id B569E1C0899; Thu, 11 Sep 2014 04:25:14 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-23019BD3-D586-44C1-89C5-692B53B1900C
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (12A365)
In-Reply-To: <10DF7F11-9EB0-4332-9A42-176EB9E75B64@gmail.com>
Date: Thu, 11 Sep 2014 13:25:12 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <1FF3800C-471C-4097-AECC-D7A60D67D765@thomasclausen.org>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@ mail.gmail.com> <10DF7F11-9EB0-4332-9A42-176EB9E75B64@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/e0ARaz5f_YfotDCt1EBBrU2_o0A
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 11:25:18 -0000

--Apple-Mail-23019BD3-D586-44C1-89C5-692B53B1900C
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Agree with Chris and Henning here.

Sent from my iPad

> On 11 Sep 2014, at 12:02, Christopher Dearlove <christopher.dearlove@gmail=
.com> wrote:
>=20
> Henning is right, you are wrong. I could explain why, but that's already b=
een done more than once.
>=20
> --=20
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>=20
>> On 11 Sep 2014, at 10:57, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
>>=20
>>=20
>>=20
>>> On Thursday, September 11, 2014, Henning Rogge wrote:
>>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>>> <charles.perkins@earthlink.net> wrote:
>>> >
>>> > Hello Chris,
>>> >
>>> > That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255?
>>>=20
>>> On protocol level? Put it into the right document (e.g. the "rfc5444
>>> security practices" or whatever).
>>>=20
>>> On implementation level? Just as you do now, just a line of code in
>>> the right place.
>>=20
>>=20
>> For interoperability purposes the right place is within AODVv2 implementa=
tion. For independent purposes the right place is AODVv2. Chris answered it a=
s part of overall-system but still no definition for that as IETF standard, s=
o does that mean writing another draft to update the system.=20
>> =20
>>>=20
>>> Would be the "use IP-TTL 255 as an additional security measurement"
>>> part of the AODVv2 protocol? No, because the protocol should only deal
>>> with the messages so its easy to mix with the other protocols using
>>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>>> of symmetric links).=20
>>=20
>>=20
>> Those protocols can be updated for AODVv2 functions. Those protocols are s=
ervants to routing protocols so they should follow.=20
>> =20
>>> But of course it would be part of some (maybe not
>>> all) AODVv2 implementations (some might implement other security
>>> measurements).
>>=20
>> So do you agree the right place is AODVv2. Overall, this design problem i=
s because the WG wrongly decided to design the packet before the functions a=
nd to make routing functions serve RFC5444 within a unified multiplex method=
.=20
>>=20
>> AB=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-23019BD3-D586-44C1-89C5-692B53B1900C
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Agree with Chris and Henning here.<br>=
<br>Sent from my iPad</div><div><br>On 11 Sep 2014, at 12:02, Christopher De=
arlove &lt;<a href=3D"mailto:christopher.dearlove@gmail.com">christopher.dea=
rlove@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><=
meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><div=
>Henning is right, you are wrong. I could explain why, but that's already be=
en done more than once.<br><br>--&nbsp;<div>Christopher Dearlove</div><div><=
a href=3D"mailto:christopher.dearlove@gmail.com">christopher.dearlove@gmail.=
com</a> (iPhone)</div><div><a href=3D"mailto:chris@mnemosyne.demon.co.uk">ch=
ris@mnemosyne.demon.co.uk</a> (home)</div></div><div><br>On 11 Sep 2014, at 1=
0:57, Abdussalam Baryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">ab=
dussalambaryun@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cit=
e"><div><br><br>On Thursday, September 11, 2014, Henning Rogge  wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins=
<br>
&lt;<a href=3D"javascript:;" onclick=3D"_e(event, 'cvml', 'charles.perkins@e=
arthlink.net')">charles.perkins@earthlink.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Hello Chris,<br>
&gt;<br>
&gt; That's fine with me.&nbsp; How do I instruct RFC 5444 to set TTL=3D=3D2=
55?<br>
<br>
On protocol level? Put it into the right document (e.g. the "rfc5444<br>
security practices" or whatever).<br>
<br>
On implementation level? Just as you do now, just a line of code in<br>
the right place.</blockquote><div><br></div><div><br></div><div>For interope=
rability purposes the right place is within AODVv2 implementation. For indep=
endent purposes the right place is AODVv2. Chris answered it as part of over=
all-system but still no definition for that as IETF&nbsp;standard, so does t=
hat mean writing another draft to update the system.&nbsp;</div><div>&nbsp;<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<br>
Would be the "use IP-TTL 255 as an additional security measurement"<br>
part of the AODVv2 protocol? No, because the protocol should only deal<br>
with the messages so its easy to mix with the other protocols using<br>
RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection<br>
of symmetric links).&nbsp;</blockquote><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></block=
quote><div><br></div><div>Those protocols can be updated for AODVv2 function=
s. Those protocols are servants to routing protocols so they should&nbsp;fol=
low.&nbsp;</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But of course=
 it would be part of some (maybe not<br>
all) AODVv2 implementations (some might implement other security<br>
measurements).</blockquote><div><br></div><div>So do you agree the right pla=
ce is AODVv2. Overall, this design&nbsp;problem is because the WG wrongly de=
cided to design the packet before the functions and to&nbsp;make routing fun=
ctions serve RFC5444 within a unified multiplex method.&nbsp;</div><div><br>=
</div><div>AB&nbsp;</div>
</div></blockquote></div></blockquote><blockquote type=3D"cite"><div><span>_=
______________________________________________</span><br><span>manet mailing=
 list</span><br><span><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></=
span><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/manet">https=
://www.ietf.org/mailman/listinfo/manet</a></span><br></div></blockquote></bo=
dy></html>=

--Apple-Mail-23019BD3-D586-44C1-89C5-692B53B1900C--


From nobody Thu Sep 11 04:29:20 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC671A0ADC for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MZ69j-H5KWsQ for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:29:15 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ABDE1A0860 for <manet@ietf.org>; Thu, 11 Sep 2014 04:29:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 36B2F260EB7; Thu, 11 Sep 2014 04:29:15 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id B65E91C0899; Thu, 11 Sep 2014 04:29:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (12A365)
In-Reply-To: <02FA236C-E416-4D88-AAE0-CEF29AC1776F@gmail.com>
Date: Thu, 11 Sep 2014 13:29:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2630E3EB-4C79-4AE8-9D16-D3CBED5AB0A9@thomasclausen.org>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@ mail.gmail.com> <CAGnRvuocJmN0rCWNoO0soOFKeuy00v6YNT=nZSk25hVM5b5mNQ@mail.gmail.com> <02FA236C-E416-4D88-AAE0-CEF29AC1776F@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/xXu5XFxEXPXG6qDXgNPSN1m1_W4
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 11:29:17 -0000

> On 11 Sep 2014, at 13:12, Christopher Dearlove <christopher.dearlove@gmail=
.com> wrote:
>=20
> Henning has addressed the other issues. I'll mention one.
>=20
>> On 11 Sep 2014, at 11:21, Henning Rogge wrote:
>> In fact it would have been even better if the MPR handling woud also
>> have been split into its own document so it can be reused easier
>> without referring to the OLSRv2 RFC. Its works the way it is, but
>> splitting it would have been more elegant (but it would have delayed
>> OLSRv2 even more).
>=20
> Completely agree. And in fact that's not the only thing I (we I believe) w=
ould have split out in an ideal world. Next on my list would be the processi=
ng and forwarding mechanism in OLSRv2 that is designed for use by message ty=
pes other than just TC messages.
>=20
> But we were delayed enough as it was.
>=20

In an ideal world, once we have about 10 years of operational experience wit=
h OLSRv2 (so, let's pick that up in 2024...)  if we push this onto the next l=
evel on the standards track, that would be the occasion to re-visit this.=20=


But, FWIW, the processing/forwarding engine from OLSRv2, and the MPR handlin=
g, both are sufficiently generic to be useful factored out (similar to NHDP a=
nd packetbb). There are a couple of other things from OLSRv2, that I think w=
ould fall into that category, but that is for another discussion another tim=
e, and perhaps in another venue.

Thomas

> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 11 04:29:48 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABF11A0B7D for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9_nVMNbHDZ2B for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:29:44 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 366791A6F2D for <manet@ietf.org>; Thu, 11 Sep 2014 04:29:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 19D4C260EFE; Thu, 11 Sep 2014 04:29:33 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 968681C0899; Thu, 11 Sep 2014 04:29:32 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (12A365)
In-Reply-To: <CAGnRvuptV4JYm1+W_9mhhsR0s3=+BjdjFvYDW00qVetX3cen3A@mail.gmail.com>
Date: Thu, 11 Sep 2014 13:29:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1FA4EB79-735A-4148-ACE5-471513540EFA@thomasclausen.org>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@ mail.gmail.com> <CAGnRvuocJmN0rCWNoO0soOFKeuy00v6YNT=nZSk25hVM5b5mNQ@mail.gmail.com> <02FA236C-E416-4D88-AAE0-CEF29AC1776F@gmail.com> <CAGnRvuptV4JYm1+W_9mhhsR0s3=+BjdjFvYDW00qVetX3cen3A@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/iKIM_rqheotdHdFQgVEcdSz6puE
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 11:29:46 -0000

> On 11 Sep 2014, at 13:15, Henning Rogge <hrogge@gmail.com> wrote:
>=20
> On Thu, Sep 11, 2014 at 1:12 PM, Christopher Dearlove
> <christopher.dearlove@gmail.com> wrote:
>> Henning has addressed the other issues. I'll mention one.
>>=20
>>> On 11 Sep 2014, at 11:21, Henning Rogge wrote:
>>> In fact it would have been even better if the MPR handling woud also
>>> have been split into its own document so it can be reused easier
>>> without referring to the OLSRv2 RFC. Its works the way it is, but
>>> splitting it would have been more elegant (but it would have delayed
>>> OLSRv2 even more).
>>=20
>> Completely agree. And in fact that's not the only thing I (we I believe) w=
ould have split out in an ideal world. Next on my list would be the processi=
ng and forwarding mechanism in OLSRv2 that is designed for use by message ty=
pes other than just TC messages.
>=20
> In fact I moved both of them out of the OLSRv2 core code in my implementat=
ion.
>=20

I think that we all did ;)

Thomas

> Henning Rogge
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 11 04:46:09 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E6C61A8980 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eP82jQSke7_P for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 04:45:58 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC89B1A897F for <manet@ietf.org>; Thu, 11 Sep 2014 04:45:02 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id ex7so757451wid.3 for <manet@ietf.org>; Thu, 11 Sep 2014 04:44:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bdPG7NaznWLMBHzfYF4bt/21VTqCAcIyh2G3AXlihaQ=; b=siqa4iFohg7p44rUSlPCo/Gdcix5HQtxpIkDZOYbT+RAfsHOVF7ruxG/m/erWSw4g/ RWWNJ7IvrTKDMs58Qu3fl1d5n9oiBcq/Fs62jTGvt4Eu97lDdye5maS8zeqkI+r95We8 ppxsHqTI+HE0k/yEm7uKO+6t7jH5pqm9wVeAZwS87I/O12/GhHBJN3xzdDCFL8yObI15 L5FjFf7ErFCGjTNlfpXeDCcZ61azIXHez4g+axCI9DtuF65YjRAKIDtSWEBQpG9cN9LR xM66EiyhIdEgPI55D24B337KxEh57n89VR14Z57cQyenFpNmavLstU/Fvmajo+hTakJ6 tHTg==
X-Received: by 10.194.200.74 with SMTP id jq10mr599381wjc.110.1410435897527; Thu, 11 Sep 2014 04:44:57 -0700 (PDT)
Received: from [192.168.254.1] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id qd1sm1279883wic.8.2014.09.11.04.44.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 04:44:56 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Christopher Dearlove <christopher.dearlove@gmail.com>
In-Reply-To: <54117E3C.8040007@gmail.com>
Date: Thu, 11 Sep 2014 12:44:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A18C6C09-9F6A-44E3-8BFE-25C84BE3185B@gmail.com>
References: <54117E3C.8040007@gmail.com>
To: John Dowdell <john.dowdell.ietf@gmail.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/SwlyNjTnod5TJrUJUhl5BTYQcNQ
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] AODVv2 progress
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 11:46:06 -0000

(Changed to send to list, as someone else may find this useful. Or not. =
Written in a hurry, so apologies for any errors.)

Let me have a bash as Index Start and Index Stop. This will be an NHDP =
example for convenience.

Let's suppose we have five addresses in a single address block in a =
HELLO message. Two are local, three are neighbours'.

For the last three we want to associate a LINK_STATUS TLV with them.

Prior to RFC 7188 (which I will get back to) the definitely most =
efficient way to do this was to put these three addresses together, =
let's say after the two local addresses. Note that this doesn't violate =
the "don't use address order" rule, as no meaning is assigned to the =
position, just ordering allows us to create more efficient messages. We =
could put those three addresses first, third and fifth for a maximally =
inefficient message with three LINK_STATUS TLVs if we wanted to.

(As an aside, I have an implementation that is close, if not at, optimum =
for doing this for standard NHDP/OLSRv2 use. I know Henning has worked =
on a different approach also aimed at efficient messages, and if I guess =
right others have worked on this too.)

Anyway, so we now put the three messages in the last three places, =
numbered 2,3,4 (we number from zero).

So now we might have two cases. In the first, all have the same link =
status, say SYMMETRIC. We can create a single value LINK_STATUS TLV with =
two indices (indexes in the RFC, but that's written in American =
English), Index Start =3D 2, Index Stop =3D 4, value field SYMMETRIC. In =
the second, we create a multivalue TLV with value field (say) SYMMETRIC =
SYMMETRIC HEARD. That turns out to be more efficient than two single =
value TLVs doing the same job. (Single value TVs can win with lots of =
neighbours.)

Now with RFC 7188 we have another option. We could have a LINK_STATUS =
TLV covering all five addresses, which now no longer gain at all from =
ordering, but I'll stick to the same ordering for convenience. We need =
no indices and can have a multivalue TLV with value field UNSPECIFIED =
UNSPECIFIED SYMMETRIC SYMMETRIC HEARD (in the second example above).

(Actually with that 2+3 pattern, both options are equally efficient. =
With one more local address or all symmetric, and addresses organised, =
there's a win in not using UNSPECIFIED.)

Finally, if we want to just associate with a single address in a =
multiple address block, we can use a single index form with just one =
index (that is in effect both Index Start and Index Stop).

Some things to note
- The sender can play whatever games it likes in sorting or not, using =
or not using UNSPECIFIED, single value or multivalue TLVs, one TLV or =
many. It affects efficiency, but not meaning.
- Whether there are zero, one or two indices, and single or multiple =
values is signalled in the TLV flags octet.
- The receiver is simpler in that it just reads what's there and =
interprets it. Position is not used for meaning, except via indices =
telling you which addresses are covered.
- However, while the sender can choose not to use things, the receiver =
must be able to interpret whatever it gets. Including RFC 7188.
- The simplest approach is to take addresses as they come (unsorted) =
simply cover all addresses, not uses indices, use UNSPECIFIED as =
required, always use a multivalue TLV. Next simplest is that with some =
optimisation (strip leading trailing UNSPECIFIEDs, use single value if =
that now works).

In an ideal world, this is another of those things that at least =
something should be said in the =
still-intended-but-could-we-have-more-hours-in-the-day-please 5444 usage =
draft.=20

Hope that helps. There s an example HELLO message in RFC 6130. I think =
it includes indices, but it may not.


On 11 Sep 2014, at 11:49, John Dowdell wrote:

> All
>=20
> You already know that the AODVv2 draft is a large and complex =
document, and judging by the number of tickets and the high volume of =
discussions on the mailing list, a number of WG participants have a =
number of issues with the text. I have been working through the draft in =
recent weeks trying to make it more clear and consistent before trying =
to apply the comments on the list and the tracker. I'm not at the end of =
that first sweep yet.
>=20
> Trouble is, my cycles are currently limited to an average of 10-20% of =
my working week (which does not routinely include evenings or weekends) =
so progress is slow, particularly when my day job has a priority call. I =
am hoping that this situation will improve in 2015. That is not to say I =
am not committed to getting the draft finished. It is very unlikely that =
you will see a document that incorporates all your comments by the next =
meeting, but please do continue to discuss the content and suggest =
changes which will be incorporated at the appropriate time. If you are =
not happy with this situation you are, of course, free to discuss it =
with the co-chairs.
>=20
> I am also new to RFC5444, but I believe I have a reasonably good =
understanding of that now. If someone could explain to me how Index =
Start and Index Stop should be used, I'd have a better understanding.
>=20
> Thank you in advance for your patience and understanding.
>=20
> John


From nobody Thu Sep 11 06:01:42 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57ED1A6FC1 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 06:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KIY3JdBwORMi for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 06:01:34 -0700 (PDT)
Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E56E1A6F9E for <manet@ietf.org>; Thu, 11 Sep 2014 06:01:34 -0700 (PDT)
Received: by mail-yk0-f177.google.com with SMTP id 79so4658075ykr.22 for <manet@ietf.org>; Thu, 11 Sep 2014 06:01:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kaNI2go8zqtJEC1ueN0b6pB7u51YQJ5peLobSV6IMIo=; b=I1+1udxN4xBLl8N4xvKxIYrkpGNdaLKzrqnWwB300rJ1lvmxr6GV0j2Aji67LKJaIr fMuFSiYaStyxQPbqjuH2iZBkAHqsgiF7VmgylYm4ObMGKYfS9GFcNZfXdWWkShNQLwiJ KN30OTeQ6fu08QRfUXwLpZHDk9l0vnWNDCLN0IZnNMLAeXyGLBLJQLAxfEmqg83mcRoU xLJs1QdoXvBHYmxHZT9cAKdZidPE0Ku9HRy5vWOi/uGc/xOu6ER54A9y0qNPZcUJrx70 xb2UDDddKUEU9cXd7FNcPR0oVaeIU1l1HqO6F+wkzY1iAtH0FnylB95CVFJtFfHm0CSy jD3Q==
MIME-Version: 1.0
X-Received: by 10.236.39.178 with SMTP id d38mr686875yhb.121.1410440493515; Thu, 11 Sep 2014 06:01:33 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Thu, 11 Sep 2014 06:01:33 -0700 (PDT)
In-Reply-To: <5411750F.9050303@gmail.com>
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org> <53CC9339.50103@computer.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECC2@GLKXM0002V.GREENLNK.net> <CADnDZ88OMOTUc7Btbf9TP57NT58R4Z4rM8t58mX-6=k21GPrDg@mail.gmail.com> <5411750F.9050303@gmail.com>
Date: Thu, 11 Sep 2014 15:01:33 +0200
Message-ID: <CADnDZ8_6+5Zeq8o2EueFHOo7rbYRi+qqzBbLVMOUfFOTCM=2CA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John Dowdell <john.dowdell.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a1133789a97cc420502c9c42e
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/wZDySYaRfJRNCxxpvdewX7Pa8vA
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 13:01:41 -0000

--001a1133789a97cc420502c9c42e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi John,

I believe its WG work not author team work. My edit below was documented in
IETF for WG and is before WG editors action, because authors done their
discussion outside IETF. I will continue help the WG in this draft as it's
our work together and to making action per ticket for progress. So I
understand that authors agree with my edits action.

AB

On Thursday, September 11, 2014, John Dowdell wrote:

>  Abdussalam
>
> I have already spotted that one in my review and it has been discussed
> within the author team. But thanks anyway.
>
> John
>
> On 10/09/14 21:50, Abdussalam Baryun wrote:
>
>
>
> On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>
>> The key thing is that two independent implementations need to
>> interoperate and not use unidirectional links. At the moment that wouldn=
't
>> happen.
>>
>>
>  In draft's applicability statement:
>
>  ---- OLD EDIT-----
>
> AODVv2 only supports bidirectional links.  In the case of possible unidir=
ectional links, either blacklists (see Section 5.2) or other means (e.g. ad=
jacency establishment with only neighboring routers that have bidirectional=
 communication as indicated by NHDP [RFC6130]) of assuring and monitoring b=
idirectionality are recommended. Otherwise, persistent packet loss or persi=
stent protocol failures could occur.  The cost of bidirectional link L (den=
oted Cost(L)) may depend upon the direction across the link for which the c=
ost is measured.  If received over a link that is
>  u
> nidirectional, metric information from incoming AODVv2 messages SHOULD NO=
T be used for route table updates.
>
>
>  ---- NEW EDIT -----
>
> AODVv2 only supports bidirectional links.  In the case of possible unidir=
ectional links, the protocol MUST use blacklists (see Section 5.2), otherwi=
se may use means (e.g. adjacency establishment with only neighboring router=
s that have bidirectional communication as indicated by NHDP [RFC6130]) of =
assuring and monitoring bidirectionality are recommended. Otherwise, persis=
tent packet loss or persistent protocol failures could occur.
>
> -------------
>
> Move the below text to another suitable section which I recommend section=
 5.2.
>
> {{{
>
> The cost of bidirectional link L (denoted Cost(L)) may depend upon the di=
rection across the link for which the cost is measured.  If received over a=
 link that is unidirectional, metric information from incoming AODVv2 messa=
ges SHOULD NOT be used for route table updates.
>
> }}}
>
>  AB
>
>
>
>
> _______________________________________________
> manet mailing listmanet@ietf.org <javascript:_e(%7B%7D,'cvml','manet@ietf=
.org');>https://www.ietf.org/mailman/listinfo/manet
>
>
>

--001a1133789a97cc420502c9c42e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Hi John,</div><div><br></div><div>I believe its WG work not author tea=
m work.=C2=A0My edit below was documented in IETF for WG and is=C2=A0before=
 WG editors action, because authors done their discussion outside IETF. I w=
ill continue help the WG in this draft as it&#39;s our work together=C2=A0a=
nd to=C2=A0making action per ticket for progress. So I understand that auth=
ors agree with my edits action.=C2=A0</div><div><br></div><div>AB<br><br>On=
 Thursday, September 11, 2014, John Dowdell  wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    Abdussalam<br>
    <br>
    I have already spotted that one in my review and it has been
    discussed within the author team. But thanks anyway.<br>
    <br>
    John<br>
    <br>
    <div>On 10/09/14 21:50, Abdussalam Baryun
      wrote:<br>
    </div>
    <blockquote type=3D"cite"><br>
      <br>
      On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:<br>
      <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">The key thing
        is that two independent implementations need to interoperate and
        not use unidirectional links. At the moment that wouldn&#39;t
        happen.<br>
        <br>
      </blockquote>
      <div><br>
      </div>
      <div>In draft&#39;s=C2=A0applicability statement:=C2=A0</div>
      <div><br>
      </div>
      <div>---- OLD EDIT-----</div>
      <div>
        <div title=3D"Page 9">
          <div>
            <div>
              <div>
                <pre><span style=3D"font-size:10.000000pt;font-family:&#39;=
Courier&#39;">AODVv2 only supports bidirectional links.  In the case of pos=
sible unidirectional links, either blacklists (see </span><span style=3D"fo=
nt-size:10.000000pt;font-family:&#39;Courier&#39;;color:rgb(0.000000%,0.000=
000%,100.000000%)">Section 5.2</span><span style=3D"font-size:10.000000pt;f=
ont-family:&#39;Courier&#39;">) or other means (e.g. adjacency establishmen=
t with only neighboring routers that have bidirectional communication as in=
dicated by NHDP [</span><span style=3D"font-size:10.000000pt;font-family:&#=
39;Courier&#39;;color:rgb(0.000000%,0.000000%,100.000000%)">RFC6130</span><=
span style=3D"font-size:10.000000pt;font-family:&#39;Courier&#39;">]) of as=
suring and monitoring bidirectionality are recommended. Otherwise, persiste=
nt packet loss or persistent protocol failures could occur.  The cost of bi=
directional link L (denoted Cost(L)) may depend upon the direction across t=
he link for which the cost is measured.  If received over a link that is=20
 u
nidirectional, metric information from incoming AODVv2 messages SHOULD NOT =
be used for route table updates.</span></pre>
              </div>
            </div>
          </div>
        </div>
      </div>
      <div><br>
      </div>
      <div>---- NEW EDIT -----=C2=A0</div>
      <div>
        <pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" si=
ze=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,25=
5,0)">AODVv2 only supports bidirectional links.  In the case of possible un=
idirectional links, the protocol MUST=C2=A0use=C2=A0blacklists (see Section=
 5.2), otherwise=C2=A0may=C2=A0use=C2=A0means (e.g. adjacency establishment=
 with only neighboring routers that have bidirectional communication as ind=
icated by NHDP [RFC6130]) of assuring and monitoring bidirectionality are r=
ecommended. Otherwise, persistent packet loss or persistent protocol failur=
es could occur.=C2=A0 </span></font></pre>
        <pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" si=
ze=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,25=
5,0)">-------------</span></font></pre>
        <pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" si=
ze=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,25=
5,0)">Move the below text to another suitable section which I recommend sec=
tion 5.2.=C2=A0</span></font></pre>
        <pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" si=
ze=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,25=
5,0)">{{{</span></font></pre>
        <pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" si=
ze=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,25=
5,0)">The cost of bidirectional link L (denoted Cost(L)) may depend upon th=
e direction across the link for which the cost is measured.  If received ov=
er a link that is unidirectional, metric information from incoming AODVv2 m=
essages SHOULD NOT be used for route table updates.</span></font></pre>
        <pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" si=
ze=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,25=
5,0)">}}}</span></font></pre>
        <pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" si=
ze=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,25=
5,0)">
</span></font></pre>
        <pre><font face=3D"Helvetica Neue, Helvetica, Arial, sans-serif" si=
ze=3D"3"><span style=3D"white-space:normal;background-color:rgba(255,255,25=
5,0)">AB</span></font></pre>
      </div>
      <div><br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
manet mailing list
<a href=3D"javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;manet@ietf.org&#39;);" =
target=3D"_blank">manet@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a>
</pre>
    </blockquote>
    <br>
  </div>

</blockquote></div>

--001a1133789a97cc420502c9c42e--


From nobody Thu Sep 11 13:45:13 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE0591A01E4 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 13:45:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJ18TCiVOEki for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 13:45:09 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id E51A61A0154 for <manet@ietf.org>; Thu, 11 Sep 2014 13:45:02 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=jArCuWdy0BB1xkEUgZlCDgUrIoC5G15+GgJ7T0EKWaOauPm4jIL15+616OBfUtV0; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XSBEg-0004at-5m; Thu, 11 Sep 2014 16:44:58 -0400
Message-ID: <541209C8.9050407@earthlink.net>
Date: Thu, 11 Sep 2014 13:44:56 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Henning Rogge <hrogge@gmail.com>,  Christopher Dearlove <christopher.dearlove@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <CADnDZ89RCTRs+4xZCTBh2nXX_eGazKb5SxZfrra6_f2MU0XRqw@mail.gmail.com	> <CAGnRvuocJmN0rCWNoO0soOFKeuy00v6YNT=nZSk25hVM5b5mNQ@mail.gmail.com> <02FA236C-E416-4D88-AAE0-CEF29AC1776F@gmail.com> <CAGnRvuptV4JYm1+W_9mhhsR0s3=+BjdjFvYDW00qVetX3cen3A@mail.gmail.com>
In-Reply-To: <CAGnRvuptV4JYm1+W_9mhhsR0s3=+BjdjFvYDW00qVetX3cen3A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac79cb6c8a96c8a58b40fdc4c9add31b10a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/2Vezotd7h8zephmw7-D2CGUa4Xg
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 20:45:11 -0000

Hello Henning,

The intention is that AODVv2 should also be able to work using
MPRs for disseminating RREQ.  If there is anything in the specification
that would prohibit that, please let me know.

Regards,
Charlie P.


On 9/11/2014 4:15 AM, Henning Rogge wrote:
> On Thu, Sep 11, 2014 at 1:12 PM, Christopher Dearlove
> <christopher.dearlove@gmail.com> wrote:
>> Henning has addressed the other issues. I'll mention one.
>>
>> On 11 Sep 2014, at 11:21, Henning Rogge wrote:
>>> In fact it would have been even better if the MPR handling woud also
>>> have been split into its own document so it can be reused easier
>>> without referring to the OLSRv2 RFC. Its works the way it is, but
>>> splitting it would have been more elegant (but it would have delayed
>>> OLSRv2 even more).
>> Completely agree. And in fact that's not the only thing I (we I believe) would have split out in an ideal world. Next on my list would be the processing and forwarding mechanism in OLSRv2 that is designed for use by message types other than just TC messages.
> In fact I moved both of them out of the OLSRv2 core code in my implementation.
>
> Henning Rogge
>


From nobody Thu Sep 11 13:57:46 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01B3E1A024C for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 13:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEIOCWv5wHDg for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 13:57:41 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 647471A01E4 for <manet@ietf.org>; Thu, 11 Sep 2014 13:57:37 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=VEv9WXwxCIGUj6pA531AbINbIXGThESdIrkO+JF6vYYK8GHHFSHHCAd+1ugjJggS; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XSBQq-0001GL-3f; Thu, 11 Sep 2014 16:57:32 -0400
Message-ID: <54120CBB.80803@earthlink.net>
Date: Thu, 11 Sep 2014 13:57:31 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Henning Rogge <hrogge@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com>
In-Reply-To: <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7117026fc0a5f2ccbcb90991ad7c91c04350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/tQtsp3VyDKAeBho0QsRaCdmLzuM
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 20:57:44 -0000

Hello Henning,

On 9/10/2014 10:24 PM, Henning Rogge wrote:
> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
> <charles.perkins@earthlink.net> wrote:
>> Hello Chris,
>>
>> That's fine with me.  How do I instruct RFC 5444 to set TTL==255?
> On protocol level? Put it into the right document (e.g. the "rfc5444
> security practices" or whatever).

Seriously?  How would such a document be written so that sometimes
RFC 5444 would know to use this security practice (i.e., in the case of 
AODVv2)
and sometimes it would know not to do so?  Do we need to create a new
registry of [manet] protocols and have the security requirements of each
one tabulated for the benefit of RFC 5444?  This would be a new
feature potentially making earlier implementations noncompliant.

How about, in the meantime, if we create a new section in the AODVv2
document entitled "Recommended RFC 5444 security practices"?


>
> On implementation level? Just as you do now, just a line of code in
> the right place.

No problem, but presumably the implementation depends on the specification.

>
> Would be the "use IP-TTL 255 as an additional security measurement"
> part of the AODVv2 protocol? No, because the protocol should only deal
> with the messages so its easy to mix with the other protocols using
> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
> of symmetric links). But of course it would be part of some (maybe not
> all) AODVv2 implementations (some might implement other security
> measurements).

Some routing protocols might not need such a thing, or may
specify other mechanisms that effectively provide a security
superset.  However, I find the following to be confusing:

- routing protocol A needs security protections 'A', as specified
    by other IETF documents
- routing protocol B needs other security protections, not exactly
    the same as needed by A

Then, if one tries to live within the RFC 5444 constraints as
recently characterized,  I don't see how RFC 5444 can resolve
this without some instruction from the routing protocol.  This
would require new features.

Alternatively, we could say that RFC 5444 requires a whole new
set of security features tailored to the particular requirements
of message bundling and topology management.  Well, I guess
that would be great for some purposes, but I really think it is
the wrong approach.


Regards,
Charlie P.

PS.  There has been so much email on this topic that I might
         have overlooked something -- please send me a reminder
         in that case!




From nobody Thu Sep 11 14:06:25 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 517791A0264 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 14:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CjfDattm5EK6 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 14:06:21 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FE071A0267 for <manet@ietf.org>; Thu, 11 Sep 2014 14:06:15 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id x13so6869472wgg.11 for <manet@ietf.org>; Thu, 11 Sep 2014 14:06:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=tblCjm14xaONZ88jwiaPnonUrRjDhl3Id3nrdr7IZ94=; b=VPcxx2p2gzz9hO/PKFSkNJb8tCsr52IeRWNESSlbus4SSNIDyKC2TExIJCFgYZ0ngO koim5TA+AQO6+8FNGGr3ZswXfvwKEYyvt2SSowJdJaJrfNawFfk3Dl3A0sluJtHOLeEK WRtu4L4+XFmJ3z2iOyWEBaUfhuS4qYKkNDIf8bPB8tijhZkwQseAGFcD19UkouymscW9 jYdo8+tfwFkiIGRbbP7OlITH8dE9exdeUlqx1avaN2COPKBJM6w+joVeHzcClhib2VqM aq5uHs69Xzjv7a+Q//aqUnhZ0wEXCnZ1po9PfzGKyZsLhBhEf54LeQHJgtoAV/HDYBuS ycCw==
X-Received: by 10.180.86.195 with SMTP id r3mr10619864wiz.8.1410469574235; Thu, 11 Sep 2014 14:06:14 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id a5sm2416161wje.17.2014.09.11.14.06.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 14:06:12 -0700 (PDT)
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <54120CBB.80803@earthlink.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <54120CBB.80803@earthlink.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <E56B34BC-5CB1-480B-B380-97888AA1EE2E@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Thu, 11 Sep 2014 22:06:10 +0100
To: Charlie Perkins <charles.perkins@earthlink.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/62EgM2qFZZ48sSYGnH2ILnz6OE4
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 21:06:23 -0000

Once again, this is not specific to AODVv2. Why is it in any way different t=
o NHDP's requirements? How can one protocol be allowed to dictate to a multi=
-protocol process? Why is this always one step forward and two back on AODVv=
2 confirming to the WG agreed structure?

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 11 Sep 2014, at 21:57, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
>=20
> Hello Henning,
>=20
>> On 9/10/2014 10:24 PM, Henning Rogge wrote:
>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>> <charles.perkins@earthlink.net> wrote:
>>> Hello Chris,
>>>=20
>>> That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255?
>> On protocol level? Put it into the right document (e.g. the "rfc5444
>> security practices" or whatever).
>=20
> Seriously?  How would such a document be written so that sometimes
> RFC 5444 would know to use this security practice (i.e., in the case of AO=
DVv2)
> and sometimes it would know not to do so?  Do we need to create a new
> registry of [manet] protocols and have the security requirements of each
> one tabulated for the benefit of RFC 5444?  This would be a new
> feature potentially making earlier implementations noncompliant.
>=20
> How about, in the meantime, if we create a new section in the AODVv2
> document entitled "Recommended RFC 5444 security practices"?
>=20
>=20
>>=20
>> On implementation level? Just as you do now, just a line of code in
>> the right place.
>=20
> No problem, but presumably the implementation depends on the specification=
.
>=20
>>=20
>> Would be the "use IP-TTL 255 as an additional security measurement"
>> part of the AODVv2 protocol? No, because the protocol should only deal
>> with the messages so its easy to mix with the other protocols using
>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>> of symmetric links). But of course it would be part of some (maybe not
>> all) AODVv2 implementations (some might implement other security
>> measurements).
>=20
> Some routing protocols might not need such a thing, or may
> specify other mechanisms that effectively provide a security
> superset.  However, I find the following to be confusing:
>=20
> - routing protocol A needs security protections 'A', as specified
>   by other IETF documents
> - routing protocol B needs other security protections, not exactly
>   the same as needed by A
>=20
> Then, if one tries to live within the RFC 5444 constraints as
> recently characterized,  I don't see how RFC 5444 can resolve
> this without some instruction from the routing protocol.  This
> would require new features.
>=20
> Alternatively, we could say that RFC 5444 requires a whole new
> set of security features tailored to the particular requirements
> of message bundling and topology management.  Well, I guess
> that would be great for some purposes, but I really think it is
> the wrong approach.
>=20
>=20
> Regards,
> Charlie P.
>=20
> PS.  There has been so much email on this topic that I might
>        have overlooked something -- please send me a reminder
>        in that case!
>=20
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 11 14:07:47 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0FC91A0266 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 14:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQXYeHJaMxJq for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 14:07:44 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47A6E1A01E7 for <manet@ietf.org>; Thu, 11 Sep 2014 14:07:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 25A7F240081; Thu, 11 Sep 2014 14:07:44 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 88D08240927; Thu, 11 Sep 2014 14:07:43 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (12A365)
In-Reply-To: <54120CBB.80803@earthlink.net>
Date: Thu, 11 Sep 2014 23:07:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC57B140-7302-4A29-A30E-B9004F25C0D6@thomasclausen.org>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <54120CBB.80803@earthlink.net>
To: Charlie Perkins <charles.perkins@earthlink.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/-Klwe4ZxdSKMrf-Vs4ArWUVIi4I
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 21:07:45 -0000

Again...having developed, implemented, and deployed reactive and proactive r=
outing protocols that are trivially compliant with RFC5444, I do sincerely n=
ot understand what it is that causes the current authors of this particular p=
rotocol so much suffering.=20

This email pulls out hypothetical arguments such as:

  "routing protocol A needs security protections 'A'.... routing protocol
     B needs other security protections, not exactly the same as needed by A=
"

Which, honestly, seems really like the current authors trying really hard to=
 create a problem where none exists, to simply discredit past WG consensus.

Thomas

Sent from my iPad

> On 11 Sep 2014, at 22:57, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
>=20
> Hello Henning,
>=20
>> On 9/10/2014 10:24 PM, Henning Rogge wrote:
>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>> <charles.perkins@earthlink.net> wrote:
>>> Hello Chris,
>>>=20
>>> That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255?
>> On protocol level? Put it into the right document (e.g. the "rfc5444
>> security practices" or whatever).
>=20
> Seriously?  How would such a document be written so that sometimes
> RFC 5444 would know to use this security practice (i.e., in the case of AO=
DVv2)
> and sometimes it would know not to do so?  Do we need to create a new
> registry of [manet] protocols and have the security requirements of each
> one tabulated for the benefit of RFC 5444?  This would be a new
> feature potentially making earlier implementations noncompliant.
>=20
> How about, in the meantime, if we create a new section in the AODVv2
> document entitled "Recommended RFC 5444 security practices"?
>=20
>=20
>>=20
>> On implementation level? Just as you do now, just a line of code in
>> the right place.
>=20
> No problem, but presumably the implementation depends on the specification=
.
>=20
>>=20
>> Would be the "use IP-TTL 255 as an additional security measurement"
>> part of the AODVv2 protocol? No, because the protocol should only deal
>> with the messages so its easy to mix with the other protocols using
>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>> of symmetric links). But of course it would be part of some (maybe not
>> all) AODVv2 implementations (some might implement other security
>> measurements).
>=20
> Some routing protocols might not need such a thing, or may
> specify other mechanisms that effectively provide a security
> superset.  However, I find the following to be confusing:
>=20
> - routing protocol A needs security protections 'A', as specified
>   by other IETF documents
> - routing protocol B needs other security protections, not exactly
>   the same as needed by A
>=20
> Then, if one tries to live within the RFC 5444 constraints as
> recently characterized,  I don't see how RFC 5444 can resolve
> this without some instruction from the routing protocol.  This
> would require new features.
>=20
> Alternatively, we could say that RFC 5444 requires a whole new
> set of security features tailored to the particular requirements
> of message bundling and topology management.  Well, I guess
> that would be great for some purposes, but I really think it is
> the wrong approach.
>=20
>=20
> Regards,
> Charlie P.
>=20
> PS.  There has been so much email on this topic that I might
>        have overlooked something -- please send me a reminder
>        in that case!
>=20
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 11 14:15:46 2014
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B19D91A0290 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 14:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R9iBGUH1KGzi for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 14:15:39 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 75BDC1A01EE for <manet@ietf.org>; Thu, 11 Sep 2014 14:15:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=f6m8m9vJa4pij+GjbsiQzXkDawBQhzNpAN5heDNGcT873yq7YJLq8clIL4xvv7q8; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.255.215]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1XSBiL-0001Jw-NE; Thu, 11 Sep 2014 17:15:37 -0400
Message-ID: <541210F7.3050106@earthlink.net>
Date: Thu, 11 Sep 2014 14:15:35 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christopher Dearlove <christopher.dearlove@gmail.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <54120CBB.80803@earthlink.net> <E56B34BC-5CB1-480B-B380-97888AA1EE2E@gmail.com>
In-Reply-To: <E56B34BC-5CB1-480B-B380-97888AA1EE2E@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac79872900631df53f18da6a864611e3763350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ZfQgq6LXzgYoGV0EgCnJCSSX_68
Cc: draft-ietf-manet-aodvv2@tools.ietf.org, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 21:15:41 -0000

Hello Chris,

I really think you are putting this in the wrong context.

To wit, it's not just AODVv2.  It's *all future protocols*.

Plus, I think I could easily make the argument that NHDP
*should* specify TTL=255.  But that is *not* my problem,
and I am not expecting to argue about it.

Furthermore, as noted previously, there is no place that
I noticed in RFC 5444 prohibiting routing protocols from
specifying TTL=255, and it remains mysterious to me why
a message bundling protocol would be specified in such
a way to have that effect.

But, and this is important, I am *not* trying to avoid
conformance to RFC 5444.  It's just that there have been
several times when behavior not explicitly specified within
the RFC 5444 document turns out to not conform to other
unstated assumptions that were made by the authors of
RFC 5444.

So I think your characterization:
                "always one step forward and two back on AODVv2"
is simply wrong, and not constructive.  If anything, I think
the discussion has been useful in terms of how well RFC 5444
serves the needs of protocol designers who are not faced with
the burden of compressing dozens or hundreds of addresses.

Regards,
Charlie P.


On 9/11/2014 2:06 PM, Christopher Dearlove wrote:
> Once again, this is not specific to AODVv2. Why is it in any way different to NHDP's requirements? How can one protocol be allowed to dictate to a multi-protocol process? Why is this always one step forward and two back on AODVv2 confirming to the WG agreed structure?
>
> --
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>
>> On 11 Sep 2014, at 21:57, Charlie Perkins <charles.perkins@earthlink.net> wrote:
>>
>>
>> Hello Henning,
>>
>>> On 9/10/2014 10:24 PM, Henning Rogge wrote:
>>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>>> <charles.perkins@earthlink.net> wrote:
>>>> Hello Chris,
>>>>
>>>> That's fine with me.  How do I instruct RFC 5444 to set TTL==255?
>>> On protocol level? Put it into the right document (e.g. the "rfc5444
>>> security practices" or whatever).
>> Seriously?  How would such a document be written so that sometimes
>> RFC 5444 would know to use this security practice (i.e., in the case of AODVv2)
>> and sometimes it would know not to do so?  Do we need to create a new
>> registry of [manet] protocols and have the security requirements of each
>> one tabulated for the benefit of RFC 5444?  This would be a new
>> feature potentially making earlier implementations noncompliant.
>>
>> How about, in the meantime, if we create a new section in the AODVv2
>> document entitled "Recommended RFC 5444 security practices"?
>>
>>
>>> On implementation level? Just as you do now, just a line of code in
>>> the right place.
>> No problem, but presumably the implementation depends on the specification.
>>
>>> Would be the "use IP-TTL 255 as an additional security measurement"
>>> part of the AODVv2 protocol? No, because the protocol should only deal
>>> with the messages so its easy to mix with the other protocols using
>>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>>> of symmetric links). But of course it would be part of some (maybe not
>>> all) AODVv2 implementations (some might implement other security
>>> measurements).
>> Some routing protocols might not need such a thing, or may
>> specify other mechanisms that effectively provide a security
>> superset.  However, I find the following to be confusing:
>>
>> - routing protocol A needs security protections 'A', as specified
>>    by other IETF documents
>> - routing protocol B needs other security protections, not exactly
>>    the same as needed by A
>>
>> Then, if one tries to live within the RFC 5444 constraints as
>> recently characterized,  I don't see how RFC 5444 can resolve
>> this without some instruction from the routing protocol.  This
>> would require new features.
>>
>> Alternatively, we could say that RFC 5444 requires a whole new
>> set of security features tailored to the particular requirements
>> of message bundling and topology management.  Well, I guess
>> that would be great for some purposes, but I really think it is
>> the wrong approach.
>>
>>
>> Regards,
>> Charlie P.
>>
>> PS.  There has been so much email on this topic that I might
>>         have overlooked something -- please send me a reminder
>>         in that case!
>>
>>
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 11 15:08:15 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 027F81A0174 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 15:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Riaag7kU3X4z for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 15:07:55 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 983121A015F for <manet@ietf.org>; Thu, 11 Sep 2014 15:07:54 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id y10so6272635wgg.27 for <manet@ietf.org>; Thu, 11 Sep 2014 15:07:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:content-transfer-encoding:subject:references:from :mime-version:in-reply-to:message-id:date:cc:to; bh=DhrOueHWUmlRgt5EtNe5yACnz0HE+XO1DElo0o3Jgyg=; b=uMYJ2ZwA5gOi6Yxazyasscczq3jhMgdupibDHmSxNf2jTlN4YgMIujrVqLvzZusJ9e wRhFDhbdM9bB3NQ62OnmQC1tIx6R9d1m96rc4OyyPdUh8g4TDqor0djAFn1tvbCyJl9k YjSEMQ2z7MGAodIR1uMmUdonemzDLKYB8gjAW2PemP7WzD5iWhkmjbjo1O1nBjRRzkei v+2/rNRz+XfRzUNtX6PUZ9kor8aEAfPXhCzchrMPwl1dVLXCUOZqBfJC2Zwjb2gcljH9 beJqptfk17DPzo9dPPxubqummllHxvT4BOWywL9kXxd+WBfGuu1ebMhAA3rr71vfR1ad auLA==
X-Received: by 10.180.228.106 with SMTP id sh10mr10709535wic.65.1410473273246;  Thu, 11 Sep 2014 15:07:53 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id z5sm2827043wib.20.2014.09.11.15.07.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 15:07:51 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <54120CBB.80803@earthlink.net> <E56B34BC-5CB1-480B-B380-97888AA1EE2E@gmail.com> <541210F7.3050106@earthlink.net>
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <541210F7.3050106@earthlink.net>
Message-Id: <0A0D571C-9512-4DD3-B829-DF8C9BA07FC8@gmail.com>
Date: Thu, 11 Sep 2014 22:52:13 +0100
To: Charlie Perkins <charles.perkins@earthlink.net>
X-Mailer: iPhone Mail (11D257)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/xM0RzPFisZPmOhZgU3GG1_4JoEM
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 22:08:01 -0000

I could write something longer, but I'm just tired of making the same points=
 (also independently made by at least two other people) especially when I'm s=
upposed to be on holiday. Suffice to say, nothing you have just said either r=
ecognises the issues or changes the position.

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 11 Sep 2014, at 22:15, Charlie Perkins <charles.perkins@earthlink.net> w=
rote:
>=20
>=20
> Hello Chris,
>=20
> I really think you are putting this in the wrong context.
>=20
> To wit, it's not just AODVv2.  It's *all future protocols*.
>=20
> Plus, I think I could easily make the argument that NHDP
> *should* specify TTL=3D255.  But that is *not* my problem,
> and I am not expecting to argue about it.
>=20
> Furthermore, as noted previously, there is no place that
> I noticed in RFC 5444 prohibiting routing protocols from
> specifying TTL=3D255, and it remains mysterious to me why
> a message bundling protocol would be specified in such
> a way to have that effect.
>=20
> But, and this is important, I am *not* trying to avoid
> conformance to RFC 5444.  It's just that there have been
> several times when behavior not explicitly specified within
> the RFC 5444 document turns out to not conform to other
> unstated assumptions that were made by the authors of
> RFC 5444.
>=20
> So I think your characterization:
>               "always one step forward and two back on AODVv2"
> is simply wrong, and not constructive.  If anything, I think
> the discussion has been useful in terms of how well RFC 5444
> serves the needs of protocol designers who are not faced with
> the burden of compressing dozens or hundreds of addresses.
>=20
> Regards,
> Charlie P.
>=20
>=20
>> On 9/11/2014 2:06 PM, Christopher Dearlove wrote:
>> Once again, this is not specific to AODVv2. Why is it in any way differen=
t to NHDP's requirements? How can one protocol be allowed to dictate to a mu=
lti-protocol process? Why is this always one step forward and two back on AO=
DVv2 confirming to the WG agreed structure?
>>=20
>> --
>> Christopher Dearlove
>> christopher.dearlove@gmail.com (iPhone)
>> chris@mnemosyne.demon.co.uk (home)
>>=20
>>> On 11 Sep 2014, at 21:57, Charlie Perkins <charles.perkins@earthlink.net=
> wrote:
>>>=20
>>>=20
>>> Hello Henning,
>>>=20
>>>> On 9/10/2014 10:24 PM, Henning Rogge wrote:
>>>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>>>> <charles.perkins@earthlink.net> wrote:
>>>>> Hello Chris,
>>>>>=20
>>>>> That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255?
>>>> On protocol level? Put it into the right document (e.g. the "rfc5444
>>>> security practices" or whatever).
>>> Seriously?  How would such a document be written so that sometimes
>>> RFC 5444 would know to use this security practice (i.e., in the case of A=
ODVv2)
>>> and sometimes it would know not to do so?  Do we need to create a new
>>> registry of [manet] protocols and have the security requirements of each=

>>> one tabulated for the benefit of RFC 5444?  This would be a new
>>> feature potentially making earlier implementations noncompliant.
>>>=20
>>> How about, in the meantime, if we create a new section in the AODVv2
>>> document entitled "Recommended RFC 5444 security practices"?
>>>=20
>>>=20
>>>> On implementation level? Just as you do now, just a line of code in
>>>> the right place.
>>> No problem, but presumably the implementation depends on the specificati=
on.
>>>=20
>>>> Would be the "use IP-TTL 255 as an additional security measurement"
>>>> part of the AODVv2 protocol? No, because the protocol should only deal
>>>> with the messages so its easy to mix with the other protocols using
>>>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>>>> of symmetric links). But of course it would be part of some (maybe not
>>>> all) AODVv2 implementations (some might implement other security
>>>> measurements).
>>> Some routing protocols might not need such a thing, or may
>>> specify other mechanisms that effectively provide a security
>>> superset.  However, I find the following to be confusing:
>>>=20
>>> - routing protocol A needs security protections 'A', as specified
>>>   by other IETF documents
>>> - routing protocol B needs other security protections, not exactly
>>>   the same as needed by A
>>>=20
>>> Then, if one tries to live within the RFC 5444 constraints as
>>> recently characterized,  I don't see how RFC 5444 can resolve
>>> this without some instruction from the routing protocol.  This
>>> would require new features.
>>>=20
>>> Alternatively, we could say that RFC 5444 requires a whole new
>>> set of security features tailored to the particular requirements
>>> of message bundling and topology management.  Well, I guess
>>> that would be great for some purposes, but I really think it is
>>> the wrong approach.
>>>=20
>>>=20
>>> Regards,
>>> Charlie P.
>>>=20
>>> PS.  There has been so much email on this topic that I might
>>>        have overlooked something -- please send me a reminder
>>>        in that case!
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>=20


From nobody Thu Sep 11 15:44:03 2014
Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFC561A019C for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 15:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.153
X-Spam-Level: 
X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E62BXZQ_yTNp for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 15:44:00 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDBC41A0184 for <manet@ietf.org>; Thu, 11 Sep 2014 15:43:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4500; q=dns/txt; s=iport; t=1410475441; x=1411685041; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ombWgazbCoV0L5cHb6cJxtcAimnECcmu6x7iIR7KAvI=; b=UKXlu9kzQo+ikO8uZaP/JH0hVrzHtkl2PCAZ0C1Gt/jk8i0m0OkXjHvV RQHRTXecANdK6sUoWm3pnzozn86fhlR3LgbAnso+BMDwjVbF2T5MiTAwI pMavx6LL4piich/E3Vo6RExNj35MgxCHXG3jzqR5pA7g4ftLDygHUo42F g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUFAOQkElStJV2Q/2dsb2JhbABfgw1TVwSyPJYFCodNAYERFniEAwEBAQMBAQEBNzQFBgULAgEIGB4QJwslAgQOBYguAwkIDb10ARMEjB6BAoFLEQEdMweDL4EdBZFLizaVO4IbgUZsgQ85gQcBAQE
X-IronPort-AV: E=Sophos;i="5.04,508,1406592000"; d="scan'208";a="354572375"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-8.cisco.com with ESMTP; 11 Sep 2014 22:43:58 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s8BMhv10010356 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 11 Sep 2014 22:43:57 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Thu, 11 Sep 2014 17:43:57 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Thomas Clausen <thomas@thomasclausen.org>
Thread-Topic: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
Thread-Index: AQHPy2tywP0/a380PEiOH6CIFTnCIJv3r2aAgAAj8gCAAAOjgIAAArOAgAAEJACAAAH4gIAACsSAgAAXcACAAAo7gIAABb4AgALx8JOAAWtWfoAAVpaAgAAa5AA=
Date: Thu, 11 Sep 2014 22:43:56 +0000
Message-ID: <C5963EFD-86FE-43FB-8485-C6A322D5F40B@cisco.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <54120CBB.80803@earthlink.net> <CC57B140-7302-4A29-A30E-B9004F25C0D6@thomasclausen.org>
In-Reply-To: <CC57B140-7302-4A29-A30E-B9004F25C0D6@thomasclausen.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.179.210]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <66CED7B65554C344B340AEFB4B45ECA9@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/675vE5UO-MKgryYpvONo1TocBX8
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 22:44:02 -0000

On Sep 11, 2014, at 5:07 PM, Thomas Clausen <thomas@thomasclausen.org> wrot=
e:

> Again...having developed, implemented, and deployed reactive and proactiv=
e routing protocols that are trivially compliant with RFC5444, I do sincere=
ly not understand what it is that causes the current authors of this partic=
ular protocol so much suffering.=20
>=20
> This email pulls out hypothetical arguments such as:
>=20
>  "routing protocol A needs security protections 'A'.... routing protocol
>     B needs other security protections, not exactly the same as needed by=
 A"
>=20
> Which, honestly, seems really like the current authors trying really hard=
 to create a problem where none exists, to simply discredit past WG consens=
us.

I respectfully disagree, and I take exception to the above characterization=
.=20

>From my perspective, there was a question asked: "How would (or could) an R=
FC5444-compliant protocol take advantage of things like setting TTL=3D255 o=
n a packet?"=20
It would appear from this thread that the answer is "You don't." Or rather,=
 "You can't."=20

Got it.=20

I now ask all involved - let's bring the temperature down a few notches, pl=
ease.=20

Stan



>=20
> Thomas
>=20
> Sent from my iPad
>=20
>> On 11 Sep 2014, at 22:57, Charlie Perkins <charles.perkins@earthlink.net=
> wrote:
>>=20
>>=20
>> Hello Henning,
>>=20
>>> On 9/10/2014 10:24 PM, Henning Rogge wrote:
>>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>>> <charles.perkins@earthlink.net> wrote:
>>>> Hello Chris,
>>>>=20
>>>> That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255?
>>> On protocol level? Put it into the right document (e.g. the "rfc5444
>>> security practices" or whatever).
>>=20
>> Seriously?  How would such a document be written so that sometimes
>> RFC 5444 would know to use this security practice (i.e., in the case of =
AODVv2)
>> and sometimes it would know not to do so?  Do we need to create a new
>> registry of [manet] protocols and have the security requirements of each
>> one tabulated for the benefit of RFC 5444?  This would be a new
>> feature potentially making earlier implementations noncompliant.
>>=20
>> How about, in the meantime, if we create a new section in the AODVv2
>> document entitled "Recommended RFC 5444 security practices"?
>>=20
>>=20
>>>=20
>>> On implementation level? Just as you do now, just a line of code in
>>> the right place.
>>=20
>> No problem, but presumably the implementation depends on the specificati=
on.
>>=20
>>>=20
>>> Would be the "use IP-TTL 255 as an additional security measurement"
>>> part of the AODVv2 protocol? No, because the protocol should only deal
>>> with the messages so its easy to mix with the other protocols using
>>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>>> of symmetric links). But of course it would be part of some (maybe not
>>> all) AODVv2 implementations (some might implement other security
>>> measurements).
>>=20
>> Some routing protocols might not need such a thing, or may
>> specify other mechanisms that effectively provide a security
>> superset.  However, I find the following to be confusing:
>>=20
>> - routing protocol A needs security protections 'A', as specified
>>  by other IETF documents
>> - routing protocol B needs other security protections, not exactly
>>  the same as needed by A
>>=20
>> Then, if one tries to live within the RFC 5444 constraints as
>> recently characterized,  I don't see how RFC 5444 can resolve
>> this without some instruction from the routing protocol.  This
>> would require new features.
>>=20
>> Alternatively, we could say that RFC 5444 requires a whole new
>> set of security features tailored to the particular requirements
>> of message bundling and topology management.  Well, I guess
>> that would be great for some purposes, but I really think it is
>> the wrong approach.
>>=20
>>=20
>> Regards,
>> Charlie P.
>>=20
>> PS.  There has been so much email on this topic that I might
>>       have overlooked something -- please send me a reminder
>>       in that case!
>>=20
>>=20
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 11 16:02:48 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EFDB1A0233 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 16:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26JEBojT99Nu for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 16:02:33 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F2931A0208 for <manet@ietf.org>; Thu, 11 Sep 2014 16:02:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 1CD29241054; Thu, 11 Sep 2014 16:02:33 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 7D30224104E; Thu, 11 Sep 2014 16:02:32 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (12A365)
In-Reply-To: <C5963EFD-86FE-43FB-8485-C6A322D5F40B@cisco.com>
Date: Fri, 12 Sep 2014 01:02:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE5B2FA2-328D-49F8-80A6-2BA75E70986A@thomasclausen.org>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <54120CBB.80803@earthlink.net> <CC57B140-7302-4A29-A3 0E-B9004F25C0D6@thomasclausen.org> <C5963EFD-86FE-43FB-8485-C6A322D5F40B@cisco.com>
To: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/qVaDzybGtKPn8pLcU5dofRidURY
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 23:02:43 -0000

> On 12 Sep 2014, at 00:43, Stan Ratliff (sratliff) <sratliff@cisco.com> wro=
te:
>=20
>=20
>> On Sep 11, 2014, at 5:07 PM, Thomas Clausen <thomas@thomasclausen.org> wr=
ote:
>>=20
>> Again...having developed, implemented, and deployed reactive and proactiv=
e routing protocols that are trivially compliant with RFC5444, I do sincerel=
y not understand what it is that causes the current authors of this particul=
ar protocol so much suffering.=20
>>=20
>> This email pulls out hypothetical arguments such as:
>>=20
>> "routing protocol A needs security protections 'A'.... routing protocol
>>    B needs other security protections, not exactly the same as needed by A=
"
>>=20
>> Which, honestly, seems really like the current authors trying really hard=
 to create a problem where none exists, to simply discredit past WG consensu=
s.
>=20
> I respectfully disagree, and I take exception to the above characterizatio=
n.=20

Fair enough - I was responding to mr. Perkins and I wouldn't know if you or m=
r. Dowdell share his  perspective and opinion. I should not have painted all=
 the current authors with the same brush. Please accept my apologies, to you=
 and mr Dowdell.

That said, I maintain that the messages from mr. Perkins read as if "discred=
it past WG consensus" is the express intent since - as I indicated, I have e=
xperience designing, implementing, and deploying, both proactive and reactiv=
e rfc5444-compliant protocols without encountering grief and suffering such a=
s is being expressed.

>> =46rom my perspective, there was a question asked: "How would (or could) a=
n RFC5444-compliant protocol take advantage of things like setting TTL=3D255=
 on a packet?"
> It would appear from this thread that the answer is "You don't." Or rather=
, "You can't."=20
>=20
> Got it.=20
>=20
> I now ask all involved - let's bring the temperature down a few notches, p=
lease.=20
>=20
I *think* you are quoting in a way such that it appears that you are replyin=
g to me in the above.. I think that I did  not write what you are quoting an=
d responding to.

Respectfully,

Thomas




> Stan
>=20
>=20
>=20
>>=20
>> Thomas
>>=20
>> Sent from my iPad
>>=20
>>> On 11 Sep 2014, at 22:57, Charlie Perkins <charles.perkins@earthlink.net=
> wrote:
>>>=20
>>>=20
>>> Hello Henning,
>>>=20
>>>> On 9/10/2014 10:24 PM, Henning Rogge wrote:
>>>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>>>> <charles.perkins@earthlink.net> wrote:
>>>>> Hello Chris,
>>>>>=20
>>>>> That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255?
>>>> On protocol level? Put it into the right document (e.g. the "rfc5444
>>>> security practices" or whatever).
>>>=20
>>> Seriously?  How would such a document be written so that sometimes
>>> RFC 5444 would know to use this security practice (i.e., in the case of A=
ODVv2)
>>> and sometimes it would know not to do so?  Do we need to create a new
>>> registry of [manet] protocols and have the security requirements of each=

>>> one tabulated for the benefit of RFC 5444?  This would be a new
>>> feature potentially making earlier implementations noncompliant.
>>>=20
>>> How about, in the meantime, if we create a new section in the AODVv2
>>> document entitled "Recommended RFC 5444 security practices"?
>>>=20
>>>=20
>>>>=20
>>>> On implementation level? Just as you do now, just a line of code in
>>>> the right place.
>>>=20
>>> No problem, but presumably the implementation depends on the specificati=
on.
>>>=20
>>>>=20
>>>> Would be the "use IP-TTL 255 as an additional security measurement"
>>>> part of the AODVv2 protocol? No, because the protocol should only deal
>>>> with the messages so its easy to mix with the other protocols using
>>>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>>>> of symmetric links). But of course it would be part of some (maybe not
>>>> all) AODVv2 implementations (some might implement other security
>>>> measurements).
>>>=20
>>> Some routing protocols might not need such a thing, or may
>>> specify other mechanisms that effectively provide a security
>>> superset.  However, I find the following to be confusing:
>>>=20
>>> - routing protocol A needs security protections 'A', as specified
>>> by other IETF documents
>>> - routing protocol B needs other security protections, not exactly
>>> the same as needed by A
>>>=20
>>> Then, if one tries to live within the RFC 5444 constraints as
>>> recently characterized,  I don't see how RFC 5444 can resolve
>>> this without some instruction from the routing protocol.  This
>>> would require new features.
>>>=20
>>> Alternatively, we could say that RFC 5444 requires a whole new
>>> set of security features tailored to the particular requirements
>>> of message bundling and topology management.  Well, I guess
>>> that would be great for some purposes, but I really think it is
>>> the wrong approach.
>>>=20
>>>=20
>>> Regards,
>>> Charlie P.
>>>=20
>>> PS.  There has been so much email on this topic that I might
>>>      have overlooked something -- please send me a reminder
>>>      in that case!
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 11 16:10:04 2014
Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30EE61A0263 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 16:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.153
X-Spam-Level: 
X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPQSlRON-9Hp for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 16:09:59 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E499D1A0262 for <manet@ietf.org>; Thu, 11 Sep 2014 16:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6285; q=dns/txt; s=iport; t=1410476998; x=1411686598; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=4ECipQenHoUWGHDuS8o3fXIk5qtbjHp942J0yj4Papg=; b=UVm7A0SwPnqdoXDJe7UFxPYYD5LnC1bdT0bGipGB0j7kWkOTrFWG+ycJ IEwJ+Ef5EppgtTvUOi7P2d3/cIQ49Aq5qDSobjQLiPPMYUQf/11XwvVmL guIB4F8iJbkw2tLH8xa3g7uJaR462SsRohTUGasSiOtFFfwiT/6rSpQTQ Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUFAHMrElStJA2B/2dsb2JhbABfgw1TVwSyPZYFCodNAYESFniEAwEBAQMBAQEBNzQFBhACAQgYHhAnCyUCBA4FiC4DCQgNvhUBEwSMHoECgUsRAR0zB4MvgR0FkUuGcIRGlTuCG4FGbIEPOYEHAQEB
X-IronPort-AV: E=Sophos;i="5.04,508,1406592000"; d="scan'208";a="77178351"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-3.cisco.com with ESMTP; 11 Sep 2014 23:09:58 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s8BN9vZi024444 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 11 Sep 2014 23:09:57 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0195.001; Thu, 11 Sep 2014 18:09:57 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Thomas Clausen <thomas@thomasclausen.org>
Thread-Topic: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
Thread-Index: AQHPy2tywP0/a380PEiOH6CIFTnCIJv3r2aAgAAj8gCAAAOjgIAAArOAgAAEJACAAAH4gIAACsSAgAAXcACAAAo7gIAABb4AgALx8JOAAWtWfoAAVpaAgAAa5ACAAAUvgIAAAhUA
Date: Thu, 11 Sep 2014 23:09:57 +0000
Message-ID: <358E4132-C24C-4CA0-8F07-D2BD07AFE332@cisco.com>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <54120CBB.80803@earthlink.net> <CC57B140-7302-4A29-A3 0E-B9004F25C0D6@thomasclausen.org> <C5963EFD-86FE-43FB-8485-C6A322D5F40B@cisco.com> <EE5B2FA2-328D-49F8-80A6-2BA75E70986A@thomasclausen.org>
In-Reply-To: <EE5B2FA2-328D-49F8-80A6-2BA75E70986A@thomasclausen.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.179.210]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <94064D9A129A384D95DB8E4CEDFAFA80@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/B0HTSasgeSz0CmKNnr-RubcA_NY
Cc: Charlie Perkins <charles.perkins@earthlink.net>, "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Sep 2014 23:10:01 -0000

On Sep 11, 2014, at 7:02 PM, Thomas Clausen <thomas@thomasclausen.org> wrot=
e:

>=20
>=20
>> On 12 Sep 2014, at 00:43, Stan Ratliff (sratliff) <sratliff@cisco.com> w=
rote:
>>=20
>>=20
>>> On Sep 11, 2014, at 5:07 PM, Thomas Clausen <thomas@thomasclausen.org> =
wrote:
>>>=20
>>> Again...having developed, implemented, and deployed reactive and proact=
ive routing protocols that are trivially compliant with RFC5444, I do since=
rely not understand what it is that causes the current authors of this part=
icular protocol so much suffering.=20
>>>=20
>>> This email pulls out hypothetical arguments such as:
>>>=20
>>> "routing protocol A needs security protections 'A'.... routing protocol
>>>   B needs other security protections, not exactly the same as needed by=
 A"
>>>=20
>>> Which, honestly, seems really like the current authors trying really ha=
rd to create a problem where none exists, to simply discredit past WG conse=
nsus.
>>=20
>> I respectfully disagree, and I take exception to the above characterizat=
ion.=20
>=20
> Fair enough - I was responding to mr. Perkins and I wouldn't know if you =
or mr. Dowdell share his  perspective and opinion. I should not have painte=
d all the current authors with the same brush. Please accept my apologies, =
to you and mr Dowdell.
>=20
> That said, I maintain that the messages from mr. Perkins read as if "disc=
redit past WG consensus" is the express intent since - as I indicated, I ha=
ve experience designing, implementing, and deploying, both proactive and re=
active rfc5444-compliant protocols without encountering grief and suffering=
 such as is being expressed.
>=20
>>> From my perspective, there was a question asked: "How would (or could) =
an RFC5444-compliant protocol take advantage of things like setting TTL=3D2=
55 on a packet?"
>> It would appear from this thread that the answer is "You don't." Or rath=
er, "You can't."=20
>>=20
>> Got it.=20
>>=20
>> I now ask all involved - let's bring the temperature down a few notches,=
 please.=20
>>=20
> I *think* you are quoting in a way such that it appears that you are repl=
ying to me in the above.. I think that I did  not write what you are quotin=
g and responding to.

Then my apologies are in order for what a colleague refers to as "communica=
ting sloppily". In my last posting, the quotations were meant as my distill=
ation of the email thread. I did not intend for it to be taken as quoting a=
 specific person's response, and I apologize that I did not clarify that.=20

Regards,
Stan


>=20
> Respectfully,
>=20
> Thomas
>=20
>=20
>=20
>=20
>> Stan
>>=20
>>=20
>>=20
>>>=20
>>> Thomas
>>>=20
>>> Sent from my iPad
>>>=20
>>>> On 11 Sep 2014, at 22:57, Charlie Perkins <charles.perkins@earthlink.n=
et> wrote:
>>>>=20
>>>>=20
>>>> Hello Henning,
>>>>=20
>>>>> On 9/10/2014 10:24 PM, Henning Rogge wrote:
>>>>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>>>>> <charles.perkins@earthlink.net> wrote:
>>>>>> Hello Chris,
>>>>>>=20
>>>>>> That's fine with me.  How do I instruct RFC 5444 to set TTL=3D=3D255=
?
>>>>> On protocol level? Put it into the right document (e.g. the "rfc5444
>>>>> security practices" or whatever).
>>>>=20
>>>> Seriously?  How would such a document be written so that sometimes
>>>> RFC 5444 would know to use this security practice (i.e., in the case o=
f AODVv2)
>>>> and sometimes it would know not to do so?  Do we need to create a new
>>>> registry of [manet] protocols and have the security requirements of ea=
ch
>>>> one tabulated for the benefit of RFC 5444?  This would be a new
>>>> feature potentially making earlier implementations noncompliant.
>>>>=20
>>>> How about, in the meantime, if we create a new section in the AODVv2
>>>> document entitled "Recommended RFC 5444 security practices"?
>>>>=20
>>>>=20
>>>>>=20
>>>>> On implementation level? Just as you do now, just a line of code in
>>>>> the right place.
>>>>=20
>>>> No problem, but presumably the implementation depends on the specifica=
tion.
>>>>=20
>>>>>=20
>>>>> Would be the "use IP-TTL 255 as an additional security measurement"
>>>>> part of the AODVv2 protocol? No, because the protocol should only dea=
l
>>>>> with the messages so its easy to mix with the other protocols using
>>>>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>>>>> of symmetric links). But of course it would be part of some (maybe no=
t
>>>>> all) AODVv2 implementations (some might implement other security
>>>>> measurements).
>>>>=20
>>>> Some routing protocols might not need such a thing, or may
>>>> specify other mechanisms that effectively provide a security
>>>> superset.  However, I find the following to be confusing:
>>>>=20
>>>> - routing protocol A needs security protections 'A', as specified
>>>> by other IETF documents
>>>> - routing protocol B needs other security protections, not exactly
>>>> the same as needed by A
>>>>=20
>>>> Then, if one tries to live within the RFC 5444 constraints as
>>>> recently characterized,  I don't see how RFC 5444 can resolve
>>>> this without some instruction from the routing protocol.  This
>>>> would require new features.
>>>>=20
>>>> Alternatively, we could say that RFC 5444 requires a whole new
>>>> set of security features tailored to the particular requirements
>>>> of message bundling and topology management.  Well, I guess
>>>> that would be great for some purposes, but I really think it is
>>>> the wrong approach.
>>>>=20
>>>>=20
>>>> Regards,
>>>> Charlie P.
>>>>=20
>>>> PS.  There has been so much email on this topic that I might
>>>>     have overlooked something -- please send me a reminder
>>>>     in that case!
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> manet mailing list
>>>> manet@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/manet
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 11 17:33:23 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822C11A02A6 for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 17:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zcl5By3jvVVt for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 17:33:19 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DAC21A020B for <manet@ietf.org>; Thu, 11 Sep 2014 17:33:19 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id a41so12497276yho.40 for <manet@ietf.org>; Thu, 11 Sep 2014 17:33:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ipa600rP/uyjxtjMP0MNnKo9lfv6c5vUaUceTrhEk/o=; b=FCA4ILz+7I9fPU/eUjVJgRsANcmPbiqzT5W93ksu34GEtve4mK+jAqhlLQjPx1X2x5 Dd51Z42xn/16VSB7Au0lVKyczm+jaFSOijJUtf4B0CXizodLBqNRxazsVgG9wwMFMIGV dq9n+BDR721bjb4S8JVc3VP7yDs1M797HyTCUJXq0Xdj0uHV/MYbN9kQyP0xuqD+ijbI XEBfVa9tZYwxbNFkUYhn/fLEVhu7m5c4ESAlqSnXhd+gSxdvxfitYV7UmezkHRJa1RXB HACPAyL98AkGi3pHr8c55kloLo7COUwd9nwUplur2DOeQi89Qe1RPvKZNm96xQkFftFq xWag==
MIME-Version: 1.0
X-Received: by 10.236.74.226 with SMTP id x62mr174268yhd.169.1410481998906; Thu, 11 Sep 2014 17:33:18 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Thu, 11 Sep 2014 17:33:18 -0700 (PDT)
In-Reply-To: <54120CBB.80803@earthlink.net>
References: <061.5b91f4f9f74fe26d1eb24cfd1ed89d43@trac.tools.ietf.org> <CADnDZ88M+4iNTn1vuuFhs2M4LaCVkpYnbdsUPA=pchxURmekqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEEC7B@GLKXM0002V.GREENLNK.net> <CADnDZ8_XkWGFmprByZB050yGFjiZaD_4mupMmRzv87ST6Y7pXQ@mail.gmail.com> <44A42EE0-D82E-47D6-B871-B72F3A01F035@mnemosyne.demon.co.uk> <540DE8B6.504@earthlink.net> <57F01541-8BFA-40C2-8522-3B612D19AD2C@gmail.com> <540DEE07.1000405@earthlink.net> <76864242-2E4A-4768-95B9-7A1543B95B30@gmail.com> <540DF327.70901@earthlink.net> <DAD3BF93-6D2A-472A-969C-3AC9CE7BD299@gmail.com> <540E0FD8.2060402@earthlink.net> <CCB4654D-AEEF-4D24-87D7-B3D9B0166505@gmail.com> <540E1D3E.9050703@earthlink.net> <CAGnRvuqqW_q4uA9K4eXS54Gn6c68dgLMqKaJyV0JQ3ycZwQ_sg@mail.gmail.com> <540E9302.5060506@earthlink.net> <B3515A23-A8BE-4062-9F68-882015AD5D40@gmail.com> <5410DBF7.2080405@earthlink.net> <CAGnRvupzjHnFCTC_8KsjNRtU6sRMDzFB4yAg9DpjuQEiUCJgrw@mail.gmail.com> <54120CBB.80803@earthlink.net>
Date: Fri, 12 Sep 2014 02:33:18 +0200
Message-ID: <CADnDZ8-kkCZm3d4HjpUPM4JZswj9zmqpaDsMQ=wBmCONsFy4hw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Charlie Perkins <charles.perkins@earthlink.net>
Content-Type: multipart/alternative; boundary=90e6ba1ef13281ce250502d36e11
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/HkdseARSoVTVuPaP_63ZQLCpReg
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, MANET IETF <manet@ietf.org>
Subject: Re: [manet] #45 (aodvv2): RFC 5498 non-compliance (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 00:33:21 -0000

--90e6ba1ef13281ce250502d36e11
Content-Type: text/plain; charset=UTF-8

I agree with Charlie,

AB

On Thursday, September 11, 2014, Charlie Perkins wrote:

>
> Hello Henning,
>
> On 9/10/2014 10:24 PM, Henning Rogge wrote:
>
>> On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins
>> <charles.perkins@earthlink.net> wrote:
>>
>>> Hello Chris,
>>>
>>> That's fine with me.  How do I instruct RFC 5444 to set TTL==255?
>>>
>> On protocol level? Put it into the right document (e.g. the "rfc5444
>> security practices" or whatever).
>>
>
> Seriously?  How would such a document be written so that sometimes
> RFC 5444 would know to use this security practice (i.e., in the case of
> AODVv2)
> and sometimes it would know not to do so?  Do we need to create a new
> registry of [manet] protocols and have the security requirements of each
> one tabulated for the benefit of RFC 5444?  This would be a new
> feature potentially making earlier implementations noncompliant.
>
> How about, in the meantime, if we create a new section in the AODVv2
> document entitled "Recommended RFC 5444 security practices"?
>
>
>
>> On implementation level? Just as you do now, just a line of code in
>> the right place.
>>
>
> No problem, but presumably the implementation depends on the specification.
>
>
>> Would be the "use IP-TTL 255 as an additional security measurement"
>> part of the AODVv2 protocol? No, because the protocol should only deal
>> with the messages so its easy to mix with the other protocols using
>> RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection
>> of symmetric links). But of course it would be part of some (maybe not
>> all) AODVv2 implementations (some might implement other security
>> measurements).
>>
>
> Some routing protocols might not need such a thing, or may
> specify other mechanisms that effectively provide a security
> superset.  However, I find the following to be confusing:
>
> - routing protocol A needs security protections 'A', as specified
>    by other IETF documents
> - routing protocol B needs other security protections, not exactly
>    the same as needed by A
>
> Then, if one tries to live within the RFC 5444 constraints as
> recently characterized,  I don't see how RFC 5444 can resolve
> this without some instruction from the routing protocol.  This
> would require new features.
>
> Alternatively, we could say that RFC 5444 requires a whole new
> set of security features tailored to the particular requirements
> of message bundling and topology management.  Well, I guess
> that would be great for some purposes, but I really think it is
> the wrong approach.
>
>
> Regards,
> Charlie P.
>
> PS.  There has been so much email on this topic that I might
>         have overlooked something -- please send me a reminder
>         in that case!
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--90e6ba1ef13281ce250502d36e11
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I agree with Charlie,<div><br></div><div>AB<br><br>On Thursday, September 1=
1, 2014, Charlie Perkins  wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hello Henning,<br>
<br>
On 9/10/2014 10:24 PM, Henning Rogge wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Thu, Sep 11, 2014 at 1:17 AM, Charlie Perkins<br>
&lt;<a>charles.perkins@earthlink.net</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello Chris,<br>
<br>
That&#39;s fine with me.=C2=A0 How do I instruct RFC 5444 to set TTL=3D=3D2=
55?<br>
</blockquote>
On protocol level? Put it into the right document (e.g. the &quot;rfc5444<b=
r>
security practices&quot; or whatever).<br>
</blockquote>
<br>
Seriously?=C2=A0 How would such a document be written so that sometimes<br>
RFC 5444 would know to use this security practice (i.e., in the case of AOD=
Vv2)<br>
and sometimes it would know not to do so?=C2=A0 Do we need to create a new<=
br>
registry of [manet] protocols and have the security requirements of each<br=
>
one tabulated for the benefit of RFC 5444?=C2=A0 This would be a new<br>
feature potentially making earlier implementations noncompliant.<br>
<br>
How about, in the meantime, if we create a new section in the AODVv2<br>
document entitled &quot;Recommended RFC 5444 security practices&quot;?<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
On implementation level? Just as you do now, just a line of code in<br>
the right place.<br>
</blockquote>
<br>
No problem, but presumably the implementation depends on the specification.=
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Would be the &quot;use IP-TTL 255 as an additional security measurement&quo=
t;<br>
part of the AODVv2 protocol? No, because the protocol should only deal<br>
with the messages so its easy to mix with the other protocols using<br>
RFC5444 (e.g. NHDP for proactive neighborhood discovery and detection<br>
of symmetric links). But of course it would be part of some (maybe not<br>
all) AODVv2 implementations (some might implement other security<br>
measurements).<br>
</blockquote>
<br>
Some routing protocols might not need such a thing, or may<br>
specify other mechanisms that effectively provide a security<br>
superset.=C2=A0 However, I find the following to be confusing:<br>
<br>
- routing protocol A needs security protections &#39;A&#39;, as specified<b=
r>
=C2=A0 =C2=A0by other IETF documents<br>
- routing protocol B needs other security protections, not exactly<br>
=C2=A0 =C2=A0the same as needed by A<br>
<br>
Then, if one tries to live within the RFC 5444 constraints as<br>
recently characterized,=C2=A0 I don&#39;t see how RFC 5444 can resolve<br>
this without some instruction from the routing protocol.=C2=A0 This<br>
would require new features.<br>
<br>
Alternatively, we could say that RFC 5444 requires a whole new<br>
set of security features tailored to the particular requirements<br>
of message bundling and topology management.=C2=A0 Well, I guess<br>
that would be great for some purposes, but I really think it is<br>
the wrong approach.<br>
<br>
<br>
Regards,<br>
Charlie P.<br>
<br>
PS.=C2=A0 There has been so much email on this topic that I might<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 have overlooked something -- please send me a r=
eminder<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 in that case!<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
manet mailing list<br>
<a>manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/manet</a><br>
</blockquote></div>

--90e6ba1ef13281ce250502d36e11--


From nobody Thu Sep 11 19:34:17 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6471A01AC for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 19:34:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FzV6sencm2At for <manet@ietfa.amsl.com>; Thu, 11 Sep 2014 19:34:14 -0700 (PDT)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF44D1A0190 for <manet@ietf.org>; Thu, 11 Sep 2014 19:34:13 -0700 (PDT)
Received: by mail-yk0-f180.google.com with SMTP id q9so51930ykb.39 for <manet@ietf.org>; Thu, 11 Sep 2014 19:34:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=2y5DRYFZG5Nc8UpKIzNA8oSewhZVcchyRZwg8pk5S44=; b=EqZp/+wennoYupSCi0uXtaDX7OSkhNCmQtHnN5SG0II1+ZbA4CeP7RDAR7wsNTmMvg xSJDT0R+Ybktypr/nfCDQrZF8Dyed6MGA2uNx0GCEZRbjzMBU+SDVX+13JR/y+Kuls1o W56IF94hqi89UmZzv1r7nFfiDkxOCwG4frPLCxJMfWuKDhTIFb5XFft1SjgsG/09c31o TA8wtla7Qf9od8qOLy/1ETYFMWX2z+u/ggWBgDRpzX+L+UPj6nAgQXfy/69VSAthkSpX /dLjjoovkYqDuBp0SEcfv4uxh0zUpaXulaayHCsyzDbR6nBDOM0jokpKGgdx4xjotU81 XQRg==
MIME-Version: 1.0
X-Received: by 10.236.17.194 with SMTP id j42mr5955035yhj.156.1410489253171; Thu, 11 Sep 2014 19:34:13 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Thu, 11 Sep 2014 19:34:13 -0700 (PDT)
Date: Fri, 12 Sep 2014 04:34:13 +0200
Message-ID: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c1e2a8e5188c0502d51ede
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/QTb0ZE6YvEqcyXIY5YTNmH1Kf38
Cc: "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 02:34:16 -0000

--001a11c1e2a8e5188c0502d51ede
Content-Type: text/plain; charset=UTF-8

In another discussion the WG may want RFC5444 packets not mentioned in our
protocols because it belongs only for multiplexer. However, This draft
mentions packets and many protocol considerations for RFC5444 packets. The
draft avoid even mentioning the multiplexer, even though it is very
important for the use case.

Therefore, either take out all describing packets in draft (put it in one
place as the management consideration section), which I don't think is
correct because it's an MT protocol, or specify a protocol for multiplexer
in another draft, or do specify multiplexing in this draft. There is an
assumption in the draft which I don't think can be accepted to avoid
multiplexing while considering packets and MT.

IMHO the draft needs to specify how the multiplexer packs its
MT messages so that each packet go through the right topology. Specifying
parser/multiplexer function is because this draft is mentioning packets and
messages for MT without mentioning multiplexer. We should ensure that each
packet routes in one topology and messages are packed correctly. For
example I don't find the function maintaining that messages of one topology
are not mixed with messages of other topologies.

AB

--001a11c1e2a8e5188c0502d51ede
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

In another discussion the WG may=C2=A0want RFC5444=C2=A0packets not mention=
ed in our protocols because it belongs=C2=A0only for multiplexer. However,=
=C2=A0This draft mentions packets and=C2=A0many protocol=C2=A0consideration=
s for RFC5444=C2=A0packets. The draft avoid even mentioning the multiplexer=
, even though it is very important for the=C2=A0use case.=C2=A0<div><br></d=
iv><div>Therefore, either take out all describing packets in draft=C2=A0(pu=
t it in one place as the management consideration section),=C2=A0which I do=
n&#39;t think is correct because it&#39;s an=C2=A0MT protocol, or specify a=
 protocol for multiplexer in another draft, or do specify multiplexing in t=
his draft. There is an assumption in the draft which I don&#39;t think can =
be accepted to avoid multiplexing while considering packets and MT.=C2=A0</=
div><div><br></div><div>IMHO the=C2=A0draft needs to specify how the multip=
lexer packs its MT=C2=A0messages=C2=A0so that each packet go through the ri=
ght topology. Specifying parser/multiplexer function=C2=A0is because this d=
raft is mentioning packets and messages for MT=C2=A0without mentioning mult=
iplexer. We should=C2=A0ensure that each packet=C2=A0routes in one topology=
 and messages are packed correctly.=C2=A0For example I don&#39;t find the f=
unction maintaining that=C2=A0messages of one topology are not mixed with m=
essages of other topologies.=C2=A0<div><br></div><div>AB</div></div>

--001a11c1e2a8e5188c0502d51ede--


From nobody Fri Sep 12 00:53:05 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1640D1A0659 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 00:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tRVJr6JUxg9L for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 00:53:02 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DB481A059F for <manet@ietf.org>; Fri, 12 Sep 2014 00:53:02 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id bs8so106585wib.4 for <manet@ietf.org>; Fri, 12 Sep 2014 00:53:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:mime-version:content-type:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2LcW4lmr2pFp/4+YV8TVjAEEQ1gMJ3btbkUlDf7/kuQ=; b=0ys3f1dgsGlD2T76bRYk0RPN3McF9wMqV9dbPWutUM2CtW+mpW/k6yvojmx9UqT1BD DGfJq6GtNN47MMQZzFBreL0HeNVjMp9FL0zO6Go9SWcKwz0TkVRiXcbFPws0rsg5qwx1 fl2jZ2jud6hCLHmtN1AfhszGZp2mk4zeEJ50nZOU35irlA0sYAaYqhAhwuYwgR5jkKQZ a99M4MdoKo/b3KM4qDcVoOFRO2xQPzWBgHzdWECHPlRyF4y8LOW3TV2aEwUzO0NQ7Ju6 Luk9IScMqd+Cysypzkn2Vn6yd0xTBu43wIKNCPEE5J6xTwPebs2vzabRqnOijBgxM9Vo YI9g==
X-Received: by 10.180.198.228 with SMTP id jf4mr183177wic.26.1410508380850; Fri, 12 Sep 2014 00:53:00 -0700 (PDT)
Received: from [192.168.254.1] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id qd1sm896334wic.8.2014.09.12.00.52.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Sep 2014 00:52:59 -0700 (PDT)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
X-Google-Original-From: Christopher Dearlove <chris@mnemosyne.demon.co.uk>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com>
Date: Fri, 12 Sep 2014 08:52:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk>
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/3bINfUsd4D8_5H-cM3pxWNnum_c
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 07:53:04 -0000

Every use of the word packet in the draft refers to a data packet being =
routed, not a 5444 packet. I just checked.

This makes this posting of yours even more of a waste of time than =
usual. Will you please actually read and understand things before =
commenting. (Putting aside the timescale issue.)

(The protocol thus does exactly what it needs to do with regard to the =
5444 multiplexer. Nothing.)


On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:

> In another discussion the WG may want RFC5444 packets not mentioned in =
our protocols because it belongs only for multiplexer. However, This =
draft mentions packets and many protocol considerations for RFC5444 =
packets. The draft avoid even mentioning the multiplexer, even though it =
is very important for the use case.=20
>=20
> Therefore, either take out all describing packets in draft (put it in =
one place as the management consideration section), which I don't think =
is correct because it's an MT protocol, or specify a protocol for =
multiplexer in another draft, or do specify multiplexing in this draft. =
There is an assumption in the draft which I don't think can be accepted =
to avoid multiplexing while considering packets and MT.=20
>=20
> IMHO the draft needs to specify how the multiplexer packs its MT =
messages so that each packet go through the right topology. Specifying =
parser/multiplexer function is because this draft is mentioning packets =
and messages for MT without mentioning multiplexer. We should ensure =
that each packet routes in one topology and messages are packed =
correctly. For example I don't find the function maintaining that =
messages of one topology are not mixed with messages of other =
topologies.=20
>=20
> AB
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Fri Sep 12 01:13:04 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EEC21A0696 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 01:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eo9c3ByNHh5V for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 01:13:01 -0700 (PDT)
Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EA671A06AC for <manet@ietf.org>; Fri, 12 Sep 2014 01:12:10 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id i8so63345qcq.4 for <manet@ietf.org>; Fri, 12 Sep 2014 01:12:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=W/2qfxmZmuBUFrWRSN2r6Kiz2IF/qI/Yzdg1MOBx6PA=; b=BCSOJA05rABUfkJGWF9R3l2m+OZYcXCGCGRJBy9HYVP4A4wjGLed8lCzg4UJy6CkaM +L0DPj0iZAp8720wwHccXQX8t6D0FaSobkwmlW5TevBUmyNQAPIcP8dFs3afDLBa0RjD c1OtTXqvbBRjUVBhU1nuD3HJTF5OVRofqvQsIKz7cYKroAFhEBRsna1djCSHUue6LZp0 b1xuu7ZWDltn/VqzFocJBaLP0yRyoiN+iLw5zuXK79yTTJmf7gw6KaY3cxFmCnmS7je9 OVAdMWBNWR/Fjt6NFiWDBN+LZQlsoRG+QdLY4pr8gfl/rwM58WWK/aYd1IoYLgBjIKjC 3Ygg==
X-Received: by 10.224.76.72 with SMTP id b8mr9663041qak.38.1410509530295; Fri, 12 Sep 2014 01:12:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Fri, 12 Sep 2014 01:11:50 -0700 (PDT)
In-Reply-To: <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk>
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 12 Sep 2014 10:11:50 +0200
Message-ID: <CAGnRvuq1bq-L_-wzUJ3pr7-TGBmndah5QDYNGHg2ou4=CJns=A@mail.gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/0Mwvd0T1gjQVlnfTS19Fm2K9zYE
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 08:13:03 -0000

On Fri, Sep 12, 2014 at 9:52 AM, Christopher Dearlove
<christopher.dearlove@gmail.com> wrote:
> Every use of the word packet in the draft refers to a data packet being routed, not a 5444 packet. I just checked.
>
> This makes this posting of yours even more of a waste of time than usual. Will you please actually read and understand things before commenting. (Putting aside the timescale issue.)
>
> (The protocol thus does exactly what it needs to do with regard to the 5444 multiplexer. Nothing.)

Again a case of "writing emails before reading the document"? This is
really getting annoying.

Henning Rogge


From nobody Fri Sep 12 03:15:48 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 893B81A03C5 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zWzGLm5WQ8kk for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:15:40 -0700 (PDT)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 101D41A0145 for <manet@ietf.org>; Fri, 12 Sep 2014 03:15:16 -0700 (PDT)
Received: by mail-yk0-f180.google.com with SMTP id q9so278571ykb.11 for <manet@ietf.org>; Fri, 12 Sep 2014 03:15:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VjVPiIrgyIFKols4H2HmYk7H14CsTi6onYo7M5cO0Yw=; b=OL/ljt+ZCFWw7RKEARjOgvq4ic5Ew+Ot9o2Am6oP4Xu4DufQ//lzoC91snqbwKc5hg qxAjn+fGJO+b3DXfgjpDJdHJb29w210cUpDy38xuVIHNbYfIEeY3Wxt8jf4X4uPKJIl0 +xfEeIO9oErdOjPDI5fRuSzdsQKcV7kfSFQUtfZKo6kRcyjm13qXcT7/vJCJ3cMCsCjV ywo5KJ06G2RxgduthVLlrk19Li/IU/69F8uMujK5etclclgFI2TV5/UJEqfnCWdpMq8x raWL8/f2dnw5AGs0tIeoPn8ECzioVuN41izz5RX2yxCrvWwPkIOEHqIuXZltwnAfRhBc pn9A==
MIME-Version: 1.0
X-Received: by 10.236.1.167 with SMTP id 27mr8822182yhd.21.1410516916365; Fri, 12 Sep 2014 03:15:16 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 12 Sep 2014 03:15:16 -0700 (PDT)
In-Reply-To: <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk>
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk>
Date: Fri, 12 Sep 2014 12:15:16 +0200
Message-ID: <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: multipart/alternative; boundary=089e011825d0bff1730502db8f56
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ThzLx5DE0uZQS3ncKK1QXQzOr88
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 10:15:42 -0000

--089e011825d0bff1730502db8f56
Content-Type: text/plain; charset=UTF-8

Any input from any participant is not wast of time. I will leave all my
other comments for IESG call then.  You could not even remember this week
why was logic hop (and many ip hop possibility for packets) put in RFC5444,
which may mean that RFC can wast readers time. The WG draft under my
investigation and time, uses the terminology of RFC5444, see the
terminology section, therefore if you want to say data packet just say it
as you did in your below email.

However, still you need to ensure that packets are having not mixed
topology messages. I hope editors respect WG participants even if they
think one input is stupid or wasting time.

AB

On Friday, September 12, 2014, Christopher Dearlove wrote:

> Every use of the word packet in the draft refers to a data packet being
> routed, not a 5444 packet. I just checked.
>
> This makes this posting of yours even more of a waste of time than usual.
> Will you please actually read and understand things before commenting.
> (Putting aside the timescale issue.)
>
> (The protocol thus does exactly what it needs to do with regard to the
> 5444 multiplexer. Nothing.)
>
>
> On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:
>
> > In another discussion the WG may want RFC5444 packets not mentioned in
> our protocols because it belongs only for multiplexer. However, This draft
> mentions packets and many protocol considerations for RFC5444 packets. The
> draft avoid even mentioning the multiplexer, even though it is very
> important for the use case.
> >
> > Therefore, either take out all describing packets in draft (put it in
> one place as the management consideration section), which I don't think is
> correct because it's an MT protocol, or specify a protocol for multiplexer
> in another draft, or do specify multiplexing in this draft. There is an
> assumption in the draft which I don't think can be accepted to avoid
> multiplexing while considering packets and MT.
> >
> > IMHO the draft needs to specify how the multiplexer packs its MT
> messages so that each packet go through the right topology. Specifying
> parser/multiplexer function is because this draft is mentioning packets and
> messages for MT without mentioning multiplexer. We should ensure that each
> packet routes in one topology and messages are packed correctly. For
> example I don't find the function maintaining that messages of one topology
> are not mixed with messages of other topologies.
> >
> > AB
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org <javascript:;>
> > https://www.ietf.org/mailman/listinfo/manet
>
>

--089e011825d0bff1730502db8f56
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br>Any input from any participant is not wast of time. I will leave all my=
 other comments for IESG call then.=C2=A0=C2=A0You could not even remember =
this week why was logic hop (and many ip hop possibility for packets)=C2=A0=
put in RFC5444, which may mean that RFC can wast readers time.=C2=A0The WG=
=C2=A0draft under my investigation and time,=C2=A0uses the terminology of R=
FC5444, see the terminology section,=C2=A0therefore if you want to say data=
 packet just say it as you did in your below email.=C2=A0<div><br></div><di=
v>However, still you need to ensure that packets are having not mixed topol=
ogy messages. I hope editors respect WG participants even if they think one=
 input is stupid or wasting time.=C2=A0</div><div><br></div><div>AB</div><d=
iv><br>On Friday, September 12, 2014, Christopher Dearlove  wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">Every use of the word packet in the draft refers =
to a data packet being routed, not a 5444 packet. I just checked.<br>
<br>
This makes this posting of yours even more of a waste of time than usual. W=
ill you please actually read and understand things before commenting. (Putt=
ing aside the timescale issue.)<br>
<br>
(The protocol thus does exactly what it needs to do with regard to the 5444=
 multiplexer. Nothing.)<br>
<br>
<br>
On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:<br>
<br>
&gt; In another discussion the WG may want RFC5444 packets not mentioned in=
 our protocols because it belongs only for multiplexer. However, This draft=
 mentions packets and many protocol considerations for RFC5444 packets. The=
 draft avoid even mentioning the multiplexer, even though it is very import=
ant for the use case.<br>
&gt;<br>
&gt; Therefore, either take out all describing packets in draft (put it in =
one place as the management consideration section), which I don&#39;t think=
 is correct because it&#39;s an MT protocol, or specify a protocol for mult=
iplexer in another draft, or do specify multiplexing in this draft. There i=
s an assumption in the draft which I don&#39;t think can be accepted to avo=
id multiplexing while considering packets and MT.<br>
&gt;<br>
&gt; IMHO the draft needs to specify how the multiplexer packs its MT messa=
ges so that each packet go through the right topology. Specifying parser/mu=
ltiplexer function is because this draft is mentioning packets and messages=
 for MT without mentioning multiplexer. We should ensure that each packet r=
outes in one topology and messages are packed correctly. For example I don&=
#39;t find the function maintaining that messages of one topology are not m=
ixed with messages of other topologies.<br>
&gt;<br>
&gt; AB<br>
&gt; _______________________________________________<br>
&gt; manet mailing list<br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;man=
et@ietf.org&#39;)">manet@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br>
</blockquote></div>

--089e011825d0bff1730502db8f56--


From nobody Fri Sep 12 03:24:55 2014
Return-Path: <drdanhe@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C72321A03C5 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GEld_WHGFfeK for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:24:52 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1CDC1A0145 for <manet@ietf.org>; Fri, 12 Sep 2014 03:24:51 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id y10so485909wgg.15 for <manet@ietf.org>; Fri, 12 Sep 2014 03:24:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MrkrDa7pDaUZJ1dI2kR1S2TkHD94acjziyl+3EL9RsI=; b=B4Pbj2JxtRQQJM7jUYYDgjdN8hO8ToXNnn8NR1IVibfFzHDkqoQGuu/P1xw8Uvwis+ HomIDgfGamCfIZTzw7spQLAj4ypVjIrESz9FbfK6mk62j9Os91pr2JfBG2kbizoM6+8n n8QXu+/X13qtk6GzBIqILkkx4SdBgPSJ4Jfhib/yiuH9gNQic8zFD8p3/A9vZOMmfbDM GC6R3Qq93n4uO2r/aUu17/IAvA3R/BQFQeO3QH5VIBuzp/ZGMc81LYArRhPcvy7yYqA0 H74V7Xawbgi7h/bp9JEdFvf1ygGuNp/jJgaX1+YSygw/yLDTp3jn+qtjr+1zeiPXxk/j HHQw==
MIME-Version: 1.0
X-Received: by 10.180.86.33 with SMTP id m1mr1030472wiz.11.1410517485775; Fri, 12 Sep 2014 03:24:45 -0700 (PDT)
Received: by 10.216.194.3 with HTTP; Fri, 12 Sep 2014 03:24:45 -0700 (PDT)
In-Reply-To: <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com>
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk> <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com>
Date: Fri, 12 Sep 2014 11:24:45 +0100
Message-ID: <CAMDg9bPEYTTESu1Sk3ST+yb5sz=NSzAicQRSNakh+uE7jgP09Q@mail.gmail.com>
From: Dan He <drdanhe@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04428deab0736c0502dbb10d
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/gVYaCI4UTeSnOD1EQmOHq5R19fQ
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 10:24:53 -0000

--f46d04428deab0736c0502dbb10d
Content-Type: text/plain; charset=UTF-8

I think "they think one input is stupid or wasting time" ! there are always
having good inputs or non-sense inputs if you agree


> AB
>
> On Friday, September 12, 2014, Christopher Dearlove wrote:
>
>> Every use of the word packet in the draft refers to a data packet being
>> routed, not a 5444 packet. I just checked.
>>
>> This makes this posting of yours even more of a waste of time than usual.
>> Will you please actually read and understand things before commenting.
>> (Putting aside the timescale issue.)
>>
>> (The protocol thus does exactly what it needs to do with regard to the
>> 5444 multiplexer. Nothing.)
>>
>>
>> On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:
>>
>> > In another discussion the WG may want RFC5444 packets not mentioned in
>> our protocols because it belongs only for multiplexer. However, This draft
>> mentions packets and many protocol considerations for RFC5444 packets. The
>> draft avoid even mentioning the multiplexer, even though it is very
>> important for the use case.
>> >
>> > Therefore, either take out all describing packets in draft (put it in
>> one place as the management consideration section), which I don't think is
>> correct because it's an MT protocol, or specify a protocol for multiplexer
>> in another draft, or do specify multiplexing in this draft. There is an
>> assumption in the draft which I don't think can be accepted to avoid
>> multiplexing while considering packets and MT.
>> >
>> > IMHO the draft needs to specify how the multiplexer packs its MT
>> messages so that each packet go through the right topology. Specifying
>> parser/multiplexer function is because this draft is mentioning packets and
>> messages for MT without mentioning multiplexer. We should ensure that each
>> packet routes in one topology and messages are packed correctly. For
>> example I don't find the function maintaining that messages of one topology
>> are not mixed with messages of other topologies.
>> >
>> > AB
>> > _______________________________________________
>> > manet mailing list
>> > manet@ietf.org
>> > https://www.ietf.org/mailman/listinfo/manet
>>
>>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--f46d04428deab0736c0502dbb10d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>I think &quot;they think one input is stupid or =
wasting time&quot; ! there are always<br></div>having good inputs or non-se=
nse inputs if you agree<br><br></div><div><div><div class=3D"gmail_extra"><=
div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><di=
v>AB</div><div><br>On Friday, September 12, 2014, Christopher Dearlove  wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">Every use of the word packet in the d=
raft refers to a data packet being routed, not a 5444 packet. I just checke=
d.<br>
<br>
This makes this posting of yours even more of a waste of time than usual. W=
ill you please actually read and understand things before commenting. (Putt=
ing aside the timescale issue.)<br>
<br>
(The protocol thus does exactly what it needs to do with regard to the 5444=
 multiplexer. Nothing.)<br>
<br>
<br>
On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:<br>
<br>
&gt; In another discussion the WG may want RFC5444 packets not mentioned in=
 our protocols because it belongs only for multiplexer. However, This draft=
 mentions packets and many protocol considerations for RFC5444 packets. The=
 draft avoid even mentioning the multiplexer, even though it is very import=
ant for the use case.<br>
&gt;<br>
&gt; Therefore, either take out all describing packets in draft (put it in =
one place as the management consideration section), which I don&#39;t think=
 is correct because it&#39;s an MT protocol, or specify a protocol for mult=
iplexer in another draft, or do specify multiplexing in this draft. There i=
s an assumption in the draft which I don&#39;t think can be accepted to avo=
id multiplexing while considering packets and MT.<br>
&gt;<br>
&gt; IMHO the draft needs to specify how the multiplexer packs its MT messa=
ges so that each packet go through the right topology. Specifying parser/mu=
ltiplexer function is because this draft is mentioning packets and messages=
 for MT without mentioning multiplexer. We should ensure that each packet r=
outes in one topology and messages are packed correctly. For example I don&=
#39;t find the function maintaining that messages of one topology are not m=
ixed with messages of other topologies.<br>
&gt;<br>
&gt; AB<br>
&gt; _______________________________________________<br>
&gt; manet mailing list<br>
&gt; <a>manet@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br>
</blockquote></div>
<br>_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div></div></div></div>

--f46d04428deab0736c0502dbb10d--


From nobody Fri Sep 12 03:26:42 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6805E1A06A7 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QLGs3np6529W for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:26:39 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 517711A06A0 for <manet@ietf.org>; Fri, 12 Sep 2014 03:26:39 -0700 (PDT)
Received: by mail-qg0-f44.google.com with SMTP id f51so471689qge.3 for <manet@ietf.org>; Fri, 12 Sep 2014 03:26:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+/b7nlYGOJRb14FzH8gZ5d99wuwX42QYFt2+gyII+QE=; b=x54F1YElNzibGm8DZR6imYaqYXL1XhhVqyUV5GPEjEWoojxoteT9okh8CRq+JPH+Fs 6U+aScsp3STmAKciSnH7IMEJhh7GUruR+dwjr/uOEnIaYFMAZFi3DJljmRxk9YZ1adak JHcqgpfkTcRe1K59BRP5InHzjSovgngOEbt4fBxmkQIAPlQWWjvgLpJhqgMysyx8DuGq PGtNbPke/AABG8qDAjxbhKp1FCEZGLcZLX44bBBQaYPoKVJrG+vRlkP0tJEgfZWZhgFn MKFmArBYZvqGVo1nrc2b9LSvkZm+8Q2iHuExNdd+jU27995s2W2zNbkrvPgz6deJTxF7 NpfQ==
X-Received: by 10.229.40.3 with SMTP id i3mr4767062qce.30.1410517598491; Fri, 12 Sep 2014 03:26:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Fri, 12 Sep 2014 03:26:18 -0700 (PDT)
In-Reply-To: <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com>
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk> <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 12 Sep 2014 12:26:18 +0200
Message-ID: <CAGnRvurmNrZ49Kt813UiDGD+VhBi+8Rwj+XCF5=fd0uAA8HJzg@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/mUIGpE7hrGcQvI6M4P3OTqp4Xx4
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 10:26:41 -0000

On Fri, Sep 12, 2014 at 12:15 PM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:

> You could not even remember this week
> why was logic hop (and many ip hop possibility for packets) put in RFC5444,
("You" refers to Christopher Dearlove)



> Any input from any participant is not wast of time.
Normally yes...

but the last two of your post in this thread were a waste of time.

> I will leave all my other comments for IESG call then.

> You could not even remember this week
> why was logic hop (and many ip hop possibility for packets) put in RFC5444,

I would like to see the relevant quote from Christopher from you.

(and I would like to know what you mean with "logic hop")

Henning Rogge

> which may mean that RFC can wast readers time. The WG draft under my
> investigation and time, uses the terminology of RFC5444, see the terminology
> section, therefore if you want to say data packet just say it as you did in
> your below email.
>
> However, still you need to ensure that packets are having not mixed topology
> messages. I hope editors respect WG participants even if they think one
> input is stupid or wasting time.
>
> AB
>
> On Friday, September 12, 2014, Christopher Dearlove wrote:
>>
>> Every use of the word packet in the draft refers to a data packet being
>> routed, not a 5444 packet. I just checked.
>>
>> This makes this posting of yours even more of a waste of time than usual.
>> Will you please actually read and understand things before commenting.
>> (Putting aside the timescale issue.)
>>
>> (The protocol thus does exactly what it needs to do with regard to the
>> 5444 multiplexer. Nothing.)
>>
>>
>> On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:
>>
>> > In another discussion the WG may want RFC5444 packets not mentioned in
>> > our protocols because it belongs only for multiplexer. However, This draft
>> > mentions packets and many protocol considerations for RFC5444 packets. The
>> > draft avoid even mentioning the multiplexer, even though it is very
>> > important for the use case.
>> >
>> > Therefore, either take out all describing packets in draft (put it in
>> > one place as the management consideration section), which I don't think is
>> > correct because it's an MT protocol, or specify a protocol for multiplexer
>> > in another draft, or do specify multiplexing in this draft. There is an
>> > assumption in the draft which I don't think can be accepted to avoid
>> > multiplexing while considering packets and MT.
>> >
>> > IMHO the draft needs to specify how the multiplexer packs its MT
>> > messages so that each packet go through the right topology. Specifying
>> > parser/multiplexer function is because this draft is mentioning packets and
>> > messages for MT without mentioning multiplexer. We should ensure that each
>> > packet routes in one topology and messages are packed correctly. For example
>> > I don't find the function maintaining that messages of one topology are not
>> > mixed with messages of other topologies.
>> >
>> > AB
>> > _______________________________________________
>> > manet mailing list
>> > manet@ietf.org
>> > https://www.ietf.org/mailman/listinfo/manet
>>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>


From nobody Fri Sep 12 03:29:35 2014
Return-Path: <john.dowdell.ietf@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B58A1A06AD for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.888
X-Spam-Level: 
X-Spam-Status: No, score=-0.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GaL-icW55Zv6 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:29:32 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3793F1A03C5 for <manet@ietf.org>; Fri, 12 Sep 2014 03:29:32 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id u56so512973wes.32 for <manet@ietf.org>; Fri, 12 Sep 2014 03:29:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=5eyJvuepL4kO/Hgfl96hKsW+pbQNpCajLOkBRGGZCKo=; b=XloChyWUnC03yJBmpI8u4NBUywnmgsWGbmujOOi1nCC3xHPRZGCe0VkIFp+LDI5Wpw mnl5pDIVZSQpxBQdDVQAxVrd5CNTUGM1sUic5USDHUAExG3OBc+u97n2fXnNIvPpMaeY KGgWAs3pOX2X67YoouB5hVYXcD/rqSm8W7rHwPEFWY3sRYOP57kQXZn4z1vvciaGJhh+ rnxrtvR7lxTw+5QUJ0g0a0IP6qam5qAEnRcd0Gs29uZc6F92XRlp8IYuf3woy/IjT64R tAmbaP+Z97UsPYyUR84qeJ1LunYxfqZCrcd7kOBIf02mlsRfQGTODn0+mb9Hok5QrBLq Qd2g==
X-Received: by 10.180.93.130 with SMTP id cu2mr1093029wib.15.1410517770874; Fri, 12 Sep 2014 03:29:30 -0700 (PDT)
Received: from [10.0.4.178] ([217.158.48.187]) by mx.google.com with ESMTPSA id em1sm1309468wib.17.2014.09.12.03.29.30 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Sep 2014 03:29:30 -0700 (PDT)
Message-ID: <5412CB09.6020000@gmail.com>
Date: Fri, 12 Sep 2014 11:29:29 +0100
From: John Dowdell <john.dowdell.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
References: <061.7e05e09a5a981863ce7bf1d07b303583@trac.tools.ietf.org>	<53CC9339.50103@computer.org>	<B31EEDDDB8ED7E4A93FDF12A4EECD30D40CEECC2@GLKXM0002V.GREENLNK.net>	<CADnDZ88OMOTUc7Btbf9TP57NT58R4Z4rM8t58mX-6=k21GPrDg@mail.gmail.com>	<5411750F.9050303@gmail.com> <CADnDZ8_6+5Zeq8o2EueFHOo7rbYRi+qqzBbLVMOUfFOTCM=2CA@mail.gmail.com>
In-Reply-To: <CADnDZ8_6+5Zeq8o2EueFHOo7rbYRi+qqzBbLVMOUfFOTCM=2CA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010906080005000601090405"
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/HQv0Whrmv7G4Efx0z_Q6rEgKU1E
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] #43 (aodvv2): Reliance on bidirectional paths (submitted for Chris Dearlove)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 10:29:34 -0000

This is a multi-part message in MIME format.
--------------010906080005000601090405
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Abdussalam

Actually this is a topic that is still under discussion in the author 
team. The problem can be looked at from a number of different 
viewpoints. I proposed something similar to your edit and then something 
I had not thought of was pointed out to me by one of the other authors. 
I do not believe it is appropriate to share the raw work in progress 
with the WG if the authors do not yet have a common understanding.

On a similar note, as I posted yesterday, the document is large and I am 
having a hard time working through it all. I will defend your right to 
make suggestions and propose edits, since that is after all what the 
IETF is about, but given that there are some bigger topics I want to get 
straight in my own head, please excuse me for not including this topic 
at the moment. I will come back to it, but there are bigger issues right 
now.

John

On 11/09/14 14:01, Abdussalam Baryun wrote:
> Hi John,
>
> I believe its WG work not author team work. My edit below was 
> documented in IETF for WG and is before WG editors action, because 
> authors done their discussion outside IETF. I will continue help the 
> WG in this draft as it's our work together and to making action per 
> ticket for progress. So I understand that authors agree with my edits 
> action.
>
> AB
>
> On Thursday, September 11, 2014, John Dowdell wrote:
>
>     Abdussalam
>
>     I have already spotted that one in my review and it has been
>     discussed within the author team. But thanks anyway.
>
>     John
>
>     On 10/09/14 21:50, Abdussalam Baryun wrote:
>>
>>
>>     On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:
>>
>>         The key thing is that two independent implementations need to
>>         interoperate and not use unidirectional links. At the moment
>>         that wouldn't happen.
>>
>>
>>     In draft's applicability statement:
>>
>>     ---- OLD EDIT-----
>>     AODVv2 only supports bidirectional links.  In the case of possible unidirectional links, either blacklists (seeSection 5.2) or other means (e.g. adjacency establishment with only neighboring routers that have bidirectional communication as indicated by NHDP [RFC6130]) of assuring and monitoring bidirectionality are recommended. Otherwise, persistent packet loss or persistent protocol failures could occur.  The cost of bidirectional link L (denoted Cost(L)) may depend upon the direction across the link for which the cost is measured.  If received over a link that is
>>       u
>>     nidirectional, metric information from incoming AODVv2 messages SHOULD NOT be used for route table updates.
>>
>>     ---- NEW EDIT -----
>>     AODVv2 only supports bidirectional links.  In the case of possible unidirectional links, the protocol MUST use blacklists (see Section 5.2), otherwise may use means (e.g. adjacency establishment with only neighboring routers that have bidirectional communication as indicated by NHDP [RFC6130]) of assuring and monitoring bidirectionality are recommended. Otherwise, persistent packet loss or persistent protocol failures could occur.
>>     -------------
>>     Move the below text to another suitable section which I recommend section 5.2.
>>     {{{
>>     The cost of bidirectional link L (denoted Cost(L)) may depend upon the direction across the link for which the cost is measured.  If received over a link that is unidirectional, metric information from incoming AODVv2 messages SHOULD NOT be used for route table updates.
>>     }}}
>>
>>     AB
>>
>>
>>
>>     _______________________________________________
>>     manet mailing list
>>     manet@ietf.org  <javascript:_e(%7B%7D,'cvml','manet@ietf.org');>
>>     https://www.ietf.org/mailman/listinfo/manet
>


--------------010906080005000601090405
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Abdussalam<br>
    <br>
    Actually this is a topic that is still under discussion in the
    author team. The problem can be looked at from a number of different
    viewpoints. I proposed something similar to your edit and then
    something I had not thought of was pointed out to me by one of the
    other authors. I do not believe it is appropriate to share the raw
    work in progress with the WG if the authors do not yet have a common
    understanding.<br>
    <br>
    On a similar note, as I posted yesterday, the document is large and
    I am having a hard time working through it all. I will defend your
    right to make suggestions and propose edits, since that is after all
    what the IETF is about, but given that there are some bigger topics
    I want to get straight in my own head, please excuse me for not
    including this topic at the moment. I will come back to it, but
    there are bigger issues right now.<br>
    <br>
    John<br>
    <br>
    <div class="moz-cite-prefix">On 11/09/14 14:01, Abdussalam Baryun
      wrote:<br>
    </div>
    <blockquote
cite="mid:CADnDZ8_6+5Zeq8o2EueFHOo7rbYRi+qqzBbLVMOUfFOTCM=2CA@mail.gmail.com"
      type="cite">
      <div>Hi John,</div>
      <div><br>
      </div>
      <div>I believe its WG work not author team work.Â My edit below was
        documented in IETF for WG and isÂ before WG editors action,
        because authors done their discussion outside IETF. I will
        continue help the WG in this draft as it's our work togetherÂ and
        toÂ making action per ticket for progress. So I understand that
        authors agree with my edits action.Â </div>
      <div><br>
      </div>
      <div>AB<br>
        <br>
        On Thursday, September 11, 2014, John Dowdell wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div text="#000000" bgcolor="#FFFFFF"> Abdussalam<br>
            <br>
            I have already spotted that one in my review and it has been
            discussed within the author team. But thanks anyway.<br>
            <br>
            John<br>
            <br>
            <div>On 10/09/14 21:50, Abdussalam Baryun wrote:<br>
            </div>
            <blockquote type="cite"><br>
              <br>
              On Tuesday, July 22, 2014, Dearlove, Christopher (UK)
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">The
                key thing is that two independent implementations need
                to interoperate and not use unidirectional links. At the
                moment that wouldn't happen.<br>
                <br>
              </blockquote>
              <div><br>
              </div>
              <div>In draft'sÂ applicability statement:Â </div>
              <div><br>
              </div>
              <div>---- OLD EDIT-----</div>
              <div>
                <div title="Page 9">
                  <div>
                    <div>
                      <div>
                        <pre><span style="font-size:10.000000pt;font-family:'Courier'">AODVv2 only supports bidirectional links.  In the case of possible unidirectional links, either blacklists (see </span><span style="font-size:10.000000pt;font-family:'Courier';color:rgb(0.000000%,0.000000%,100.000000%)">Section 5.2</span><span style="font-size:10.000000pt;font-family:'Courier'">) or other means (e.g. adjacency establishment with only neighboring routers that have bidirectional communication as indicated by NHDP [</span><span style="font-size:10.000000pt;font-family:'Courier';color:rgb(0.000000%,0.000000%,100.000000%)">RFC6130</span><span style="font-size:10.000000pt;font-family:'Courier'">]) of assuring and monitoring bidirectionality are recommended. Otherwise, persistent packet loss or persistent protocol failures could occur.  The cost of bidirectional link L (denoted Cost(L)) may depend upon the direction across the link for which the cost is measured.  If received over a link 
 t
hat is 
 u
nidirectional, metric information from incoming AODVv2 messages SHOULD NOT be used for route table updates.</span></pre>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
              <div><br>
              </div>
              <div>---- NEW EDIT -----Â </div>
              <div>
                <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">AODVv2 only supports bidirectional links.  In the case of possible unidirectional links, the protocol MUSTÂ useÂ blacklists (see Section 5.2), otherwiseÂ mayÂ useÂ means (e.g. adjacency establishment with only neighboring routers that have bidirectional communication as indicated by NHDP [RFC6130]) of assuring and monitoring bidirectionality are recommended. Otherwise, persistent packet loss or persistent protocol failures could occur.Â  </span></font></pre>
                <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">-------------</span></font></pre>
                <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">Move the below text to another suitable section which I recommend section 5.2.Â </span></font></pre>
                <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">{{{</span></font></pre>
                <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">The cost of bidirectional link L (denoted Cost(L)) may depend upon the direction across the link for which the cost is measured.  If received over a link that is unidirectional, metric information from incoming AODVv2 messages SHOULD NOT be used for route table updates.</span></font></pre>
                <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">}}}</span></font></pre>
                <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">
</span></font></pre>
                <pre><font face="Helvetica Neue, Helvetica, Arial, sans-serif" size="3"><span style="white-space:normal;background-color:rgba(255,255,255,0)">AB</span></font></pre>
              </div>
              <div><br>
              </div>
              <br>
              <fieldset></fieldset>
              <br>
              <pre>_______________________________________________
manet mailing list
<a moz-do-not-send="true" href="javascript:_e(%7B%7D,'cvml','manet@ietf.org');" target="_blank">manet@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/manet" target="_blank">https://www.ietf.org/mailman/listinfo/manet</a>
</pre>
            </blockquote>
            <br>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------010906080005000601090405--


From nobody Fri Sep 12 03:51:54 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E81241A06E6 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEKTAZ8q4i95 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:51:51 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B14431A06E7 for <manet@ietf.org>; Fri, 12 Sep 2014 03:51:31 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id q58so544007wes.37 for <manet@ietf.org>; Fri, 12 Sep 2014 03:51:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=fS3iBXx/FPAntl60qTzsddbkorK7vxzzLQVA3I4F3wI=; b=YKNH+9vnjiLHE86dAW5UvokFJUm14zIN9skI4R7a5lmtLOyeJLujBjMmWtJAEyXZLv waN16AlVYKU/WiV8mVcif7l35fElbK2uOlk1qT2zxA/UVKcZOkk0j2jtSnuMeYEpL3k/ HKmxiOnr75VUeMOui4jgXmkbnkLVaAmIxR/NplNv/FLgFvi5tgsXw/T9f7InBDqojpxB Kd8NkeY3kCxSYDeCR5+d8bLMhep7Ypd236oF80EF9kWbWGJGkUIHLdVO1vx7nSXyO7/q FoklJpdltmyzgbjgD0BXSeYdEyFPMKM4Zr+BxgHu9+brPOGnFdYzTAcVkF6Bug0JSv40 iZ6A==
X-Received: by 10.194.92.71 with SMTP id ck7mr9688870wjb.11.1410519090320; Fri, 12 Sep 2014 03:51:30 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id n3sm1373866wiy.10.2014.09.12.03.51.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Sep 2014 03:51:28 -0700 (PDT)
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk> <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com> <CAGnRvurmNrZ49Kt813UiDGD+VhBi+8Rwj+XCF5=fd0uAA8HJzg@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAGnRvurmNrZ49Kt813UiDGD+VhBi+8Rwj+XCF5=fd0uAA8HJzg@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AF5EAFE-1C39-4090-B3D6-B7F70135ED50@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Fri, 12 Sep 2014 11:51:25 +0100
To: Henning Rogge <hrogge@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/jF5ZLnFjEo5NJ2lee3Ul_RdoLaw
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 10:51:53 -0000

It's true I don't recall why it (for at least one value of it) was put in. B=
ut why something was put in (who had the idea, was it WG consensus or IESG r=
equirement - not the only options) is only relevant to a discussion why we a=
re where we are (as I was making). It has no relevance to where we are, incl=
uding no difference to anyone implementing.

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 12 Sep 2014, at 11:26, Henning Rogge <hrogge@gmail.com> wrote:
>=20
> On Fri, Sep 12, 2014 at 12:15 PM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>=20
>> You could not even remember this week
>> why was logic hop (and many ip hop possibility for packets) put in RFC544=
4,
> ("You" refers to Christopher Dearlove)
>=20
>=20
>=20
>> Any input from any participant is not wast of time.
> Normally yes...
>=20
> but the last two of your post in this thread were a waste of time.
>=20
>> I will leave all my other comments for IESG call then.
>=20
>> You could not even remember this week
>> why was logic hop (and many ip hop possibility for packets) put in RFC544=
4,
>=20
> I would like to see the relevant quote from Christopher from you.
>=20
> (and I would like to know what you mean with "logic hop")
>=20
> Henning Rogge
>=20
>> which may mean that RFC can wast readers time. The WG draft under my
>> investigation and time, uses the terminology of RFC5444, see the terminol=
ogy
>> section, therefore if you want to say data packet just say it as you did i=
n
>> your below email.
>>=20
>> However, still you need to ensure that packets are having not mixed topol=
ogy
>> messages. I hope editors respect WG participants even if they think one
>> input is stupid or wasting time.
>>=20
>> AB
>>=20
>>> On Friday, September 12, 2014, Christopher Dearlove wrote:
>>>=20
>>> Every use of the word packet in the draft refers to a data packet being
>>> routed, not a 5444 packet. I just checked.
>>>=20
>>> This makes this posting of yours even more of a waste of time than usual=
.
>>> Will you please actually read and understand things before commenting.
>>> (Putting aside the timescale issue.)
>>>=20
>>> (The protocol thus does exactly what it needs to do with regard to the
>>> 5444 multiplexer. Nothing.)
>>>=20
>>>=20
>>>> On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:
>>>>=20
>>>> In another discussion the WG may want RFC5444 packets not mentioned in
>>>> our protocols because it belongs only for multiplexer. However, This dr=
aft
>>>> mentions packets and many protocol considerations for RFC5444 packets. T=
he
>>>> draft avoid even mentioning the multiplexer, even though it is very
>>>> important for the use case.
>>>>=20
>>>> Therefore, either take out all describing packets in draft (put it in
>>>> one place as the management consideration section), which I don't think=
 is
>>>> correct because it's an MT protocol, or specify a protocol for multiple=
xer
>>>> in another draft, or do specify multiplexing in this draft. There is an=

>>>> assumption in the draft which I don't think can be accepted to avoid
>>>> multiplexing while considering packets and MT.
>>>>=20
>>>> IMHO the draft needs to specify how the multiplexer packs its MT
>>>> messages so that each packet go through the right topology. Specifying
>>>> parser/multiplexer function is because this draft is mentioning packets=
 and
>>>> messages for MT without mentioning multiplexer. We should ensure that e=
ach
>>>> packet routes in one topology and messages are packed correctly. For ex=
ample
>>>> I don't find the function maintaining that messages of one topology are=
 not
>>>> mixed with messages of other topologies.
>>>>=20
>>>> AB
>>>> _______________________________________________
>>>> manet mailing list
>>>> manet@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/manet
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>=20


From nobody Fri Sep 12 03:55:20 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 003071A069C for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2-Dxr97NJ15u for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 03:55:17 -0700 (PDT)
Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ACC61A064E for <manet@ietf.org>; Fri, 12 Sep 2014 03:55:17 -0700 (PDT)
Received: by mail-qg0-f41.google.com with SMTP id a108so504140qge.14 for <manet@ietf.org>; Fri, 12 Sep 2014 03:55:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=QCtxdXMwrOI4lEIjCleeSf8Qag9QwhS8Yzxep6Ckee0=; b=HYnN6kI5UJhNgzukdj0p+QfkGKsdJb7ri9ph7XfPOhESndxGWgYQer2UBQfDCFS/jn VzIskn7ku0uYT0gG+KoW7rVwZc4o3UyvQ10rgqG51HYmF/kmlgE4CMhceAFnN6ALrTBa fYboklJN0KksfOY/Cfco7d5RSD/Ya5kbpe2HjjoJPDSk0E5MrzZc0iY4TWEIpTwFW8Rj zccmthQC/n2Qzgsw1pAITdY6cYqvFbZ+r/6mZrCQVGvVAoUZV5VvlM8UhYqdBdk83DEZ yRQn22ISJDS7Rw2HXyOaagMQiAArQOCxM544EVO1JQCBIJd7lYPol2on8HcItjJv7cX0 lJvA==
X-Received: by 10.140.92.97 with SMTP id a88mr10651113qge.85.1410519315720; Fri, 12 Sep 2014 03:55:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Fri, 12 Sep 2014 03:54:55 -0700 (PDT)
In-Reply-To: <6AF5EAFE-1C39-4090-B3D6-B7F70135ED50@gmail.com>
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk> <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com> <CAGnRvurmNrZ49Kt813UiDGD+VhBi+8Rwj+XCF5=fd0uAA8HJzg@mail.gmail.com> <6AF5EAFE-1C39-4090-B3D6-B7F70135ED50@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 12 Sep 2014 12:54:55 +0200
Message-ID: <CAGnRvuopk-7QbrtN8JnMhfuT7LUWDnOHOayPnNN1KsOb5Xd8YA@mail.gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/zXK42HKpT_HQHwoAcKm1bDHnVXY
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 10:55:19 -0000

Okay,

are we talking about the "Hop Count" or the "Hop Limit" field in the
RFC5444 message header? Or something else?

Henning Rogge

On Fri, Sep 12, 2014 at 12:51 PM, Christopher Dearlove
<christopher.dearlove@gmail.com> wrote:
> It's true I don't recall why it (for at least one value of it) was put in=
. But why something was put in (who had the idea, was it WG consensus or IE=
SG requirement - not the only options) is only relevant to a discussion why=
 we are where we are (as I was making). It has no relevance to where we are=
, including no difference to anyone implementing.
>
> --
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>
>> On 12 Sep 2014, at 11:26, Henning Rogge <hrogge@gmail.com> wrote:
>>
>> On Fri, Sep 12, 2014 at 12:15 PM, Abdussalam Baryun
>> <abdussalambaryun@gmail.com> wrote:
>>
>>> You could not even remember this week
>>> why was logic hop (and many ip hop possibility for packets) put in RFC5=
444,
>> ("You" refers to Christopher Dearlove)
>>
>>
>>
>>> Any input from any participant is not wast of time.
>> Normally yes...
>>
>> but the last two of your post in this thread were a waste of time.
>>
>>> I will leave all my other comments for IESG call then.
>>
>>> You could not even remember this week
>>> why was logic hop (and many ip hop possibility for packets) put in RFC5=
444,
>>
>> I would like to see the relevant quote from Christopher from you.
>>
>> (and I would like to know what you mean with "logic hop")
>>
>> Henning Rogge
>>
>>> which may mean that RFC can wast readers time. The WG draft under my
>>> investigation and time, uses the terminology of RFC5444, see the termin=
ology
>>> section, therefore if you want to say data packet just say it as you di=
d in
>>> your below email.
>>>
>>> However, still you need to ensure that packets are having not mixed top=
ology
>>> messages. I hope editors respect WG participants even if they think one
>>> input is stupid or wasting time.
>>>
>>> AB
>>>
>>>> On Friday, September 12, 2014, Christopher Dearlove wrote:
>>>>
>>>> Every use of the word packet in the draft refers to a data packet bein=
g
>>>> routed, not a 5444 packet. I just checked.
>>>>
>>>> This makes this posting of yours even more of a waste of time than usu=
al.
>>>> Will you please actually read and understand things before commenting.
>>>> (Putting aside the timescale issue.)
>>>>
>>>> (The protocol thus does exactly what it needs to do with regard to the
>>>> 5444 multiplexer. Nothing.)
>>>>
>>>>
>>>>> On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:
>>>>>
>>>>> In another discussion the WG may want RFC5444 packets not mentioned i=
n
>>>>> our protocols because it belongs only for multiplexer. However, This =
draft
>>>>> mentions packets and many protocol considerations for RFC5444 packets=
. The
>>>>> draft avoid even mentioning the multiplexer, even though it is very
>>>>> important for the use case.
>>>>>
>>>>> Therefore, either take out all describing packets in draft (put it in
>>>>> one place as the management consideration section), which I don't thi=
nk is
>>>>> correct because it's an MT protocol, or specify a protocol for multip=
lexer
>>>>> in another draft, or do specify multiplexing in this draft. There is =
an
>>>>> assumption in the draft which I don't think can be accepted to avoid
>>>>> multiplexing while considering packets and MT.
>>>>>
>>>>> IMHO the draft needs to specify how the multiplexer packs its MT
>>>>> messages so that each packet go through the right topology. Specifyin=
g
>>>>> parser/multiplexer function is because this draft is mentioning packe=
ts and
>>>>> messages for MT without mentioning multiplexer. We should ensure that=
 each
>>>>> packet routes in one topology and messages are packed correctly. For =
example
>>>>> I don't find the function maintaining that messages of one topology a=
re not
>>>>> mixed with messages of other topologies.
>>>>>
>>>>> AB
>>>>> _______________________________________________
>>>>> manet mailing list
>>>>> manet@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/manet
>>>
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>


From nobody Fri Sep 12 04:07:08 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6399F1A06E7 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 04:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JGG4fuPYkfwE for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 04:07:02 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 959A91A06E3 for <manet@ietf.org>; Fri, 12 Sep 2014 04:07:00 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id x12so537859wgg.26 for <manet@ietf.org>; Fri, 12 Sep 2014 04:06:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=gj5PQUndoqCeliUKuvdph4D1MNGaCZn0Af/IGFJRoKs=; b=gnZ6MbgU0N0xLcD+P6pGjseuZMqGYi2sikDsllhDf2MDdYLu1+KV1TrmzcSwbUYVjo Zk3ve9k1nT48D3XlqbRv7LV2BSVL3anhgmjV+uT4w2DJPhgiMe1+7ZTSuqnBpAl3BwHq ZRK+RNl9tZxRot4pbruS7uURm/+i7dRvj1x5x74UPrVebwzlP9bWlfsMWwOnJ7KQjBqq 8AuU06CP3lD+/vM/i/2M6aLcHR1rF/EeifWYYzOWVkYgjlCxdpyNq5kDCQtZ9UDbPEBZ mvLuM90Fh1FKTatOpzHs/27EsS9mSp89nJdysQGZf7HNskUZgQvhflH7FwbK9/qVt8u8 UWrQ==
X-Received: by 10.180.189.226 with SMTP id gl2mr1529266wic.12.1410520017600; Fri, 12 Sep 2014 04:06:57 -0700 (PDT)
Received: from [192.168.254.2] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id o10sm1843819wia.0.2014.09.12.04.06.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Sep 2014 04:06:56 -0700 (PDT)
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk> <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com> <CAGnRvurmNrZ49Kt813UiDGD+VhBi+8Rwj+XCF5=fd0uAA8HJzg@mail.gmail.com> <6AF5EAFE-1C39-4090-B3D6-B7F70135ED50@gmail.com> <CAGnRvuopk-7QbrtN8JnMhfuT7LUWDnOHOayPnNN1KsOb5Xd8YA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAGnRvuopk-7QbrtN8JnMhfuT7LUWDnOHOayPnNN1KsOb5Xd8YA@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1C842D2-C6D0-411A-AD6E-5695A78D0929@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Fri, 12 Sep 2014 12:06:51 +0100
To: Henning Rogge <hrogge@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/eSldFBm0lW2urSxlfgvw6ZnRVHY
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 11:07:05 -0000

The point I think was about the qualifying word logical in stating that 5444=
 packets only travel one hop. At the IP level that is, nothing to do with 54=
44's fields.

But the point is, I don't recall who wanted that word in. But it's irrelevan=
t except as a historical point. What it means is all that matters. And what i=
t basically means is "looks like one hop, and can be used as if one hop, eve=
n if physically it uses more than one link. For example we could have a dumb=
 relay in the system. Or use tunnelling.

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 12 Sep 2014, at 11:54, Henning Rogge <hrogge@gmail.com> wrote:
>=20
> Okay,
>=20
> are we talking about the "Hop Count" or the "Hop Limit" field in the
> RFC5444 message header? Or something else?
>=20
> Henning Rogge
>=20
> On Fri, Sep 12, 2014 at 12:51 PM, Christopher Dearlove
> <christopher.dearlove@gmail.com> wrote:
>> It's true I don't recall why it (for at least one value of it) was put in=
. But why something was put in (who had the idea, was it WG consensus or IES=
G requirement - not the only options) is only relevant to a discussion why w=
e are where we are (as I was making). It has no relevance to where we are, i=
ncluding no difference to anyone implementing.
>>=20
>> --
>> Christopher Dearlove
>> christopher.dearlove@gmail.com (iPhone)
>> chris@mnemosyne.demon.co.uk (home)
>>=20
>>> On 12 Sep 2014, at 11:26, Henning Rogge <hrogge@gmail.com> wrote:
>>>=20
>>> On Fri, Sep 12, 2014 at 12:15 PM, Abdussalam Baryun
>>> <abdussalambaryun@gmail.com> wrote:
>>>=20
>>>> You could not even remember this week
>>>> why was logic hop (and many ip hop possibility for packets) put in RFC5=
444,
>>> ("You" refers to Christopher Dearlove)
>>>=20
>>>=20
>>>=20
>>>> Any input from any participant is not wast of time.
>>> Normally yes...
>>>=20
>>> but the last two of your post in this thread were a waste of time.
>>>=20
>>>> I will leave all my other comments for IESG call then.
>>>=20
>>>> You could not even remember this week
>>>> why was logic hop (and many ip hop possibility for packets) put in RFC5=
444,
>>>=20
>>> I would like to see the relevant quote from Christopher from you.
>>>=20
>>> (and I would like to know what you mean with "logic hop")
>>>=20
>>> Henning Rogge
>>>=20
>>>> which may mean that RFC can wast readers time. The WG draft under my
>>>> investigation and time, uses the terminology of RFC5444, see the termin=
ology
>>>> section, therefore if you want to say data packet just say it as you di=
d in
>>>> your below email.
>>>>=20
>>>> However, still you need to ensure that packets are having not mixed top=
ology
>>>> messages. I hope editors respect WG participants even if they think one=

>>>> input is stupid or wasting time.
>>>>=20
>>>> AB
>>>>=20
>>>>> On Friday, September 12, 2014, Christopher Dearlove wrote:
>>>>>=20
>>>>> Every use of the word packet in the draft refers to a data packet bein=
g
>>>>> routed, not a 5444 packet. I just checked.
>>>>>=20
>>>>> This makes this posting of yours even more of a waste of time than usu=
al.
>>>>> Will you please actually read and understand things before commenting.=

>>>>> (Putting aside the timescale issue.)
>>>>>=20
>>>>> (The protocol thus does exactly what it needs to do with regard to the=

>>>>> 5444 multiplexer. Nothing.)
>>>>>=20
>>>>>=20
>>>>>> On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:
>>>>>>=20
>>>>>> In another discussion the WG may want RFC5444 packets not mentioned i=
n
>>>>>> our protocols because it belongs only for multiplexer. However, This d=
raft
>>>>>> mentions packets and many protocol considerations for RFC5444 packets=
. The
>>>>>> draft avoid even mentioning the multiplexer, even though it is very
>>>>>> important for the use case.
>>>>>>=20
>>>>>> Therefore, either take out all describing packets in draft (put it in=

>>>>>> one place as the management consideration section), which I don't thi=
nk is
>>>>>> correct because it's an MT protocol, or specify a protocol for multip=
lexer
>>>>>> in another draft, or do specify multiplexing in this draft. There is a=
n
>>>>>> assumption in the draft which I don't think can be accepted to avoid
>>>>>> multiplexing while considering packets and MT.
>>>>>>=20
>>>>>> IMHO the draft needs to specify how the multiplexer packs its MT
>>>>>> messages so that each packet go through the right topology. Specifyin=
g
>>>>>> parser/multiplexer function is because this draft is mentioning packe=
ts and
>>>>>> messages for MT without mentioning multiplexer. We should ensure that=
 each
>>>>>> packet routes in one topology and messages are packed correctly. For e=
xample
>>>>>> I don't find the function maintaining that messages of one topology a=
re not
>>>>>> mixed with messages of other topologies.
>>>>>>=20
>>>>>> AB
>>>>>> _______________________________________________
>>>>>> manet mailing list
>>>>>> manet@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/manet
>>>>=20
>>>> _______________________________________________
>>>> manet mailing list
>>>> manet@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/manet
>>>>=20


From nobody Fri Sep 12 04:10:02 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34A431A06ED for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 04:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOrTusDcsxgY for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 04:09:41 -0700 (PDT)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 349451A06EC for <manet@ietf.org>; Fri, 12 Sep 2014 04:09:31 -0700 (PDT)
Received: by mail-qa0-f53.google.com with SMTP id n8so506000qaq.12 for <manet@ietf.org>; Fri, 12 Sep 2014 04:09:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=zf0HQ48MfWQIJYrsHXgUVFWJqkl1GeNb/VA4hmqOlMw=; b=ZKDOn02h66ktx4XMZhokbwlrkLsHNscm0Ifv7MWEnuotKpRTtILW7XyyRvDt70qUh9 GO2XFdLABw9P1lEC2Pv3bC+Fskeyy3OWCTEK1mgdYp3Bim59cs0U/jZWOT2aBLTXUp0T sW5UFDOhYICl1X8jIhjfzoUD/tuTskOcN5OzjbhkP+ovU5Mnvk0DyK4jbfCl3I3Tc6p4 C/qWPZNzv6HGSEMlpRNHCTxEsxHFAel/7LlsRWOKiPDlRmQUZkNPljSLUCUSfK1pcY8J Nf8cJb4Ah/i/yr9TfQ4+XP0DPnq5dE4vagZbDhlTuNFggHlPbyfV9tgVWL0cn6Z/K+yK vwcg==
X-Received: by 10.140.92.97 with SMTP id a88mr10766661qge.85.1410520168280; Fri, 12 Sep 2014 04:09:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.133 with HTTP; Fri, 12 Sep 2014 04:09:08 -0700 (PDT)
In-Reply-To: <B1C842D2-C6D0-411A-AD6E-5695A78D0929@gmail.com>
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk> <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com> <CAGnRvurmNrZ49Kt813UiDGD+VhBi+8Rwj+XCF5=fd0uAA8HJzg@mail.gmail.com> <6AF5EAFE-1C39-4090-B3D6-B7F70135ED50@gmail.com> <CAGnRvuopk-7QbrtN8JnMhfuT7LUWDnOHOayPnNN1KsOb5Xd8YA@mail.gmail.com> <B1C842D2-C6D0-411A-AD6E-5695A78D0929@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 12 Sep 2014 13:09:08 +0200
Message-ID: <CAGnRvureuqiVqg6GaWtPMQo5iS+0CDC4KMBifFa-yLeGbMgJAg@mail.gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ahyVg9NEkkPzTu4jcuWR-6-3J-k
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 11:09:48 -0000

On Fri, Sep 12, 2014 at 1:06 PM, Christopher Dearlove
<christopher.dearlove@gmail.com> wrote:
> The point I think was about the qualifying word logical in stating that 5=
444 packets only travel one hop. At the IP level that is, nothing to do wit=
h 5444's fields.

Only RFC5444 Packets with a broadcast/multicast destination can only
travel a single IP hop.

> But the point is, I don't recall who wanted that word in. But it's irrele=
vant except as a historical point. What it means is all that matters. And w=
hat it basically means is "looks like one hop, and can be used as if one ho=
p, even if physically it uses more than one link. For example we could have=
 a dumb relay in the system. Or use tunnelling.

Or unicast.

Henning


From nobody Fri Sep 12 04:19:30 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB671A06E8 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 04:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hoIWl6Vo8Ne6 for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 04:19:24 -0700 (PDT)
Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 835121A06E7 for <manet@ietf.org>; Fri, 12 Sep 2014 04:19:24 -0700 (PDT)
Received: by mail-yk0-f169.google.com with SMTP id 20so319646yks.0 for <manet@ietf.org>; Fri, 12 Sep 2014 04:19:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=2vbXmvxmvaQFGgPCh45YpiQL3L++SawcfBw2+XntfUA=; b=uGOb9f2veU1moGoqo9RoRxnZzEn9kJd3+WQATwCycaADFkl1D9UvQrqwIi8kKfxdfL knw6CJk8ZPuiDTgQV1TP/KB3oy4rjWNNidsOmDkGdE0Y9eVi9IColFGUEtP9WjmQ8ofh J1FWFcf7Am4c1Qf8qvgAUgTl3pqk/yq6bs1v5FfpWtnjL6OUghpcFV7loajdai6WpxbD u67r7RSQD/gRe1fS1DLLG9s+FPylG5rfpA42zHoRtCuHg2StUuS7tRnUHAvWFMdI7M1q +6QDpCH9uAhCeN4gpYu56pV7xeUst69XJAI/a+fVEcQUCRE39E7xjs68uadXaecEgXER OQ6w==
MIME-Version: 1.0
X-Received: by 10.236.26.196 with SMTP id c44mr9233253yha.15.1410520763654; Fri, 12 Sep 2014 04:19:23 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 12 Sep 2014 04:19:23 -0700 (PDT)
Date: Fri, 12 Sep 2014 13:19:23 +0200
Message-ID: <CADnDZ896orO6ZDr3k_TFvVNEtGYmXMeJjrWQxF15=hi7oJ79Eg@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: manet <manet@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b5d61e610e8510502dc759e
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/c0LjTK0uc3qsOvqmIwniNtDMdAU
Subject: [manet] What logical hop of RFC5444 packets mean? What did WG agree on?
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 11:19:26 -0000

--047d7b5d61e610e8510502dc759e
Content-Type: text/plain; charset=UTF-8

Just to remind the WG of an important issue or question that may wast the
readers time. I think WG needs to fix that.

If the WG have consensus on something then we should write it down in RFC
or update our RFC. The logical hop and possible many IP hop in one logical
hop is not following the WG thoughts about RFC5444 packet with TTL=1.
Furthermore if the WG has in mind a protocol/architecture/system for
multiplexing the why the WG does not write it in an RFC.  Read below texts.

On Monday, September 8, 2014, Christopher Dearlove wrote:

> This is no different to NHDP's requirements (which may use the IP packet
> source address). It is, as I have said, a 5444 multiplexing issue.
>
> It does, I agree open up the question as to what one logical hop means
> precisely. Right now I forget why that distinction was put in 5444, I think
> was a requirement from outside the authors.


The RFC5444 is not owned by authors, it's the WG work and the WG cannot be
outside the authors. So TTL can be any number as the WG consensus.


>
>
> > On 8 Sep 2014, at 22:18, Charlie Perkins <charles.perkins@earthlink.net
> <javascript:;>> wrote:
> >
> > Hello Chris,
> >
> > AODVv2 needs the functionality because it relies on
> > reverse path forwarding.
> >
> > AODVv2 should be able to control the dissemination of
> > AODVv2 messages, and since AODVv2 messages are contained
> > in packets, then it seems that AODVv2 ought to be able to
> > specify how packets containing AODVv2 messages are to
> > be disseminated.
> >
> > In RFC 5444, one finds the following:
> >
> >>    Messages are designed to be able to be forwarded over one or more
> >>    logical hops, in a new packet for each logical hop.  Each logical hop
> >>    may consist of one or more IP hops.
> >
> > I admit that this passage may be interpreted in various different ways.
> > But to me it meant that AODVv2 needs to make sure that there would
> > just be one hop.  The term "logical hop" isn't defined in the document,
> > and I'm sure we could both write down multiple reasonable definitions
> > for the term.  Overlay networks come to mind, or multi-link Ethernet
> > media, or ...
> >


Logical hop SHOULD have been defined by the WG. I suggest we put it into
errata or future update to RFC5444.

AB

--047d7b5d61e610e8510502dc759e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Just to remind the WG of an important issue or question that may wast the r=
eaders time. I think WG needs to fix that.=C2=A0<div><br></div><div>If=C2=
=A0the WG have consensus on something then we should write it down in RFC o=
r update our RFC. The logical hop and possible many IP hop in one logical h=
op is not following the WG thoughts about RFC5444 packet with TTL=3D1. Furt=
hermore if the WG has in mind a protocol/architecture/system for multiplexi=
ng the why the WG does not write it in an RFC.=C2=A0=C2=A0Read below texts.=
=C2=A0<br><br>On Monday, September 8, 2014, Christopher Dearlove  wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">This is no different to NHDP&#39;s requirem=
ents (which may use the IP packet source address). It is, as I have said, a=
 5444 multiplexing issue.<br>
<br>
It does, I agree open up the question as to what one logical hop means prec=
isely. Right now I forget why that distinction was put in 5444, I think was=
 a requirement from outside the authors.</blockquote><div><br></div><div>Th=
e RFC5444 is not owned by authors, it&#39;s the WG work and the WG cannot b=
e outside the authors. So TTL can be any number as the WG consensus.=C2=A0<=
/div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
&gt; On 8 Sep 2014, at 22:18, Charlie Perkins &lt;<a href=3D"javascript:;" =
onclick=3D"_e(event, &#39;cvml&#39;, &#39;charles.perkins@earthlink.net&#39=
;)">charles.perkins@earthlink.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Hello Chris,<br>
&gt;<br>
&gt; AODVv2 needs the functionality because it relies on<br>
&gt; reverse path forwarding.<br>
&gt;<br>
&gt; AODVv2 should be able to control the dissemination of<br>
&gt; AODVv2 messages, and since AODVv2 messages are contained<br>
&gt; in packets, then it seems that AODVv2 ought to be able to<br>
&gt; specify how packets containing AODVv2 messages are to<br>
&gt; be disseminated.<br>
&gt;<br>
&gt; In RFC 5444, one finds the following:<br>
&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 Messages are designed to be able to be forwarded over=
 one or more<br>
&gt;&gt;=C2=A0 =C2=A0 logical hops, in a new packet for each logical hop.=
=C2=A0 Each logical hop<br>
&gt;&gt;=C2=A0 =C2=A0 may consist of one or more IP hops.<br>
&gt;<br>
&gt; I admit that this passage may be interpreted in various different ways=
.<br>
&gt; But to me it meant that AODVv2 needs to make sure that there would<br>
&gt; just be one hop.=C2=A0 The term &quot;logical hop&quot; isn&#39;t defi=
ned in the document,<br>
&gt; and I&#39;m sure we could both write down multiple reasonable definiti=
ons<br>
&gt; for the term.=C2=A0 Overlay networks come to mind, or multi-link Ether=
net<br>
&gt; media, or ...<br>
&gt;</blockquote><div><br></div><div>Logical hop SHOULD have been defined b=
y the WG. I suggest we put it into errata or future update to RFC5444.</div=
><div><br></div><div>AB</div></div>

--047d7b5d61e610e8510502dc759e--


From nobody Fri Sep 12 07:09:37 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 779841A000B for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 07:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KTvuohicbu-U for <manet@ietfa.amsl.com>; Fri, 12 Sep 2014 07:09:33 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C3B21A06B3 for <manet@ietf.org>; Fri, 12 Sep 2014 07:09:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id F10A41BC2951; Fri, 12 Sep 2014 07:09:32 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [129.104.75.100] (unknown [129.104.75.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 60C4D1BC2943; Fri, 12 Sep 2014 07:09:32 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (12A365)
In-Reply-To: <B1C842D2-C6D0-411A-AD6E-5695A78D0929@gmail.com>
Date: Fri, 12 Sep 2014 16:09:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4EB971F1-87C9-427A-A45A-2B435ADE0DC6@thomasclausen.org>
References: <CADnDZ88ebDZYjh_gTJ4RbLLD6eH9krdT5xHN24vLWdyNUUjAAg@mail.gmail.com> <B366DB1F-1C00-4E5A-AA72-383B86A7CB4F@mnemosyne.demon.co.uk> <CADnDZ8-HJ0kiQQg4a_umtye8kLJk=3Fk4FPey9+ogbp9sX3UDQ@mail.gmail.com> <CAGnRvurmNrZ49Kt813UiDGD+VhBi+8Rwj+XCF5=fd0uAA8HJzg@mail.gmail.com> <6AF5EAFE-1C39-4090-B3D6-B7F70135ED50@gmail.com> <CAGnRvuopk-7QbrtN8JnMhfuT7LUWDnOHOayPnNN1KsOb5Xd8YA@mail.gmail.com> <B1C842D2-C6D0-411A-AD6E-5695A78D0929@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/9UleX2nodWBk8QKbCAxDfAruxvE
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#1 (olsrv2-multitopology): Multiplexing RFC5444 Packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 14:09:35 -0000

My understanding:

Single logical IP hop =3D=3D "ttl not decremented", in IPv4 terms.=20

(An IP-in-IP tunnel may thus appear as one logical IP hop, even though the t=
unnel spans multiple)

Sent from my iPad

> On 12 Sep 2014, at 13:06, Christopher Dearlove <christopher.dearlove@gmail=
.com> wrote:
>=20
> The point I think was about the qualifying word logical in stating that 54=
44 packets only travel one hop. At the IP level that is, nothing to do with 5=
444's fields.
>=20
> But the point is, I don't recall who wanted that word in. But it's irrelev=
ant except as a historical point. What it means is all that matters. And wha=
t it basically means is "looks like one hop, and can be used as if one hop, e=
ven if physically it uses more than one link. For example we could have a du=
mb relay in the system. Or use tunnelling.
>=20
> --=20
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>=20
>> On 12 Sep 2014, at 11:54, Henning Rogge <hrogge@gmail.com> wrote:
>>=20
>> Okay,
>>=20
>> are we talking about the "Hop Count" or the "Hop Limit" field in the
>> RFC5444 message header? Or something else?
>>=20
>> Henning Rogge
>>=20
>> On Fri, Sep 12, 2014 at 12:51 PM, Christopher Dearlove
>> <christopher.dearlove@gmail.com> wrote:
>>> It's true I don't recall why it (for at least one value of it) was put i=
n. But why something was put in (who had the idea, was it WG consensus or IE=
SG requirement - not the only options) is only relevant to a discussion why w=
e are where we are (as I was making). It has no relevance to where we are, i=
ncluding no difference to anyone implementing.
>>>=20
>>> --
>>> Christopher Dearlove
>>> christopher.dearlove@gmail.com (iPhone)
>>> chris@mnemosyne.demon.co.uk (home)
>>>=20
>>>> On 12 Sep 2014, at 11:26, Henning Rogge <hrogge@gmail.com> wrote:
>>>>=20
>>>> On Fri, Sep 12, 2014 at 12:15 PM, Abdussalam Baryun
>>>> <abdussalambaryun@gmail.com> wrote:
>>>>=20
>>>>> You could not even remember this week
>>>>> why was logic hop (and many ip hop possibility for packets) put in RFC=
5444,
>>>> ("You" refers to Christopher Dearlove)
>>>>=20
>>>>=20
>>>>=20
>>>>> Any input from any participant is not wast of time.
>>>> Normally yes...
>>>>=20
>>>> but the last two of your post in this thread were a waste of time.
>>>>=20
>>>>> I will leave all my other comments for IESG call then.
>>>>=20
>>>>> You could not even remember this week
>>>>> why was logic hop (and many ip hop possibility for packets) put in RFC=
5444,
>>>>=20
>>>> I would like to see the relevant quote from Christopher from you.
>>>>=20
>>>> (and I would like to know what you mean with "logic hop")
>>>>=20
>>>> Henning Rogge
>>>>=20
>>>>> which may mean that RFC can wast readers time. The WG draft under my
>>>>> investigation and time, uses the terminology of RFC5444, see the termi=
nology
>>>>> section, therefore if you want to say data packet just say it as you d=
id in
>>>>> your below email.
>>>>>=20
>>>>> However, still you need to ensure that packets are having not mixed to=
pology
>>>>> messages. I hope editors respect WG participants even if they think on=
e
>>>>> input is stupid or wasting time.
>>>>>=20
>>>>> AB
>>>>>=20
>>>>>> On Friday, September 12, 2014, Christopher Dearlove wrote:
>>>>>>=20
>>>>>> Every use of the word packet in the draft refers to a data packet bei=
ng
>>>>>> routed, not a 5444 packet. I just checked.
>>>>>>=20
>>>>>> This makes this posting of yours even more of a waste of time than us=
ual.
>>>>>> Will you please actually read and understand things before commenting=
.
>>>>>> (Putting aside the timescale issue.)
>>>>>>=20
>>>>>> (The protocol thus does exactly what it needs to do with regard to th=
e
>>>>>> 5444 multiplexer. Nothing.)
>>>>>>=20
>>>>>>=20
>>>>>>> On 12 Sep 2014, at 03:34, Abdussalam Baryun wrote:
>>>>>>>=20
>>>>>>> In another discussion the WG may want RFC5444 packets not mentioned i=
n
>>>>>>> our protocols because it belongs only for multiplexer. However, This=
 draft
>>>>>>> mentions packets and many protocol considerations for RFC5444 packet=
s. The
>>>>>>> draft avoid even mentioning the multiplexer, even though it is very
>>>>>>> important for the use case.
>>>>>>>=20
>>>>>>> Therefore, either take out all describing packets in draft (put it i=
n
>>>>>>> one place as the management consideration section), which I don't th=
ink is
>>>>>>> correct because it's an MT protocol, or specify a protocol for multi=
plexer
>>>>>>> in another draft, or do specify multiplexing in this draft. There is=
 an
>>>>>>> assumption in the draft which I don't think can be accepted to avoid=

>>>>>>> multiplexing while considering packets and MT.
>>>>>>>=20
>>>>>>> IMHO the draft needs to specify how the multiplexer packs its MT
>>>>>>> messages so that each packet go through the right topology. Specifyi=
ng
>>>>>>> parser/multiplexer function is because this draft is mentioning pack=
ets and
>>>>>>> messages for MT without mentioning multiplexer. We should ensure tha=
t each
>>>>>>> packet routes in one topology and messages are packed correctly. For=
 example
>>>>>>> I don't find the function maintaining that messages of one topology a=
re not
>>>>>>> mixed with messages of other topologies.
>>>>>>>=20
>>>>>>> AB
>>>>>>> _______________________________________________
>>>>>>> manet mailing list
>>>>>>> manet@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/manet
>>>>>=20
>>>>> _______________________________________________
>>>>> manet mailing list
>>>>> manet@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/manet
>>>>>=20


From nobody Sat Sep 13 05:33:31 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88131A8863 for <manet@ietfa.amsl.com>; Sat, 13 Sep 2014 05:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srP-B_FQsx2Z for <manet@ietfa.amsl.com>; Sat, 13 Sep 2014 05:33:28 -0700 (PDT)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8BDC1A0552 for <manet@ietf.org>; Sat, 13 Sep 2014 05:33:27 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id f73so1119870yha.11 for <manet@ietf.org>; Sat, 13 Sep 2014 05:33:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3vRBGVFrUKQPiwxkHuWI54oMJuI2PuJ28Y590B1qAus=; b=zoXh6d/3rDKsCInbrA9z68cqcynsissdnGA4L5inRYJN5ozgqcH5LUVf2OwoBfI9NX yRkaEWKhxPbovmLp06wtpgGB4rzcIImPJfpyIvixf6MpOECVunUM/nXpFkCWqYHBES8+ kwVtvQpNnPtdcLMpiUW59jY9zxUWejs2eP0xXT+YIrJKymdns/1zHTpDHYzAIgukqL92 ELsxFh/1HE0rCFjrbCMPOO91JJdhaRa+gs3cBv/UTVH5FisZTlUmx3rvtRQeJB/EifT0 6pE0Tkb92pklNhwyf7smn1KfrjDvu+2t4SC6uVXwjWamATUsapAIJFF5WD1D1XJgMClc lioQ==
MIME-Version: 1.0
X-Received: by 10.236.134.75 with SMTP id r51mr18342219yhi.57.1410611607103; Sat, 13 Sep 2014 05:33:27 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Sat, 13 Sep 2014 05:33:27 -0700 (PDT)
In-Reply-To: <1CD9CC1F-18BD-4592-BFEE-AFA5812785B5@thomasclausen.org>
References: <1CD9CC1F-18BD-4592-BFEE-AFA5812785B5@thomasclausen.org>
Date: Sat, 13 Sep 2014 14:33:27 +0200
Message-ID: <CADnDZ88GFwzZVvHoPQ7ZfQsH75=z0ac=eSCZPVi9K0kDEjTzsw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Clausen <thomas@thomasclausen.org>
Content-Type: multipart/alternative; boundary=485b397dcf15c1eebd0502f19b83
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/iylah-KngafddYywC-0fVzxL9ns
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>, manet <manet@ietf.org>
Subject: Re: [manet] Security question for draft-ietf-manet-aodvv2-04
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Sep 2014 12:33:30 -0000

--485b397dcf15c1eebd0502f19b83
Content-Type: text/plain; charset=UTF-8

My comment Subject draft: draft-ietf-manet-aodvv2-04 (last
version submitted in 20 July).

Dear Thomas,

Thanks for your questions, my delay to reply have some reasons. I
thought your question was for the WG chairs or AD or draft authors (the
message was multiplexed with some texts that I have no part in), but it can
be understood that it addresses all WG. As I am taking a position of
answering and editing on the list to help in this draft's progress, I will
answer your review-questions regarding the new submission
version-draft, because any part of WG still did not reply.

On Tuesday, July 22, 2014, Thomas Clausen wrote:
>
> Given that  we were told that a way forward for security had been
identified, but we were not allowed to know what that way forward was,
 I'll  ask some specific questions that I hope can be answered.


It is strange that you as a participant in the WG to be not allowed to know
about our/your work way (IMHO the WG chairs are responsible for such
issue). I will do my best in discussing and participation with you for
the draft progress.

>
>
> Page numbers refer to the document in <subject>
>
> --- Page 4 ---
>
> Draft text:
> > When a data packet is received to  be forwarded but there is no valid
route for the destination,
> > then  the AODVv2 router of the source of the packet is notified via a
Route  Error (RERR)
> > message.


I think that The route state is not valid or break as it was active, so it
needs to send error message. Error messages are for sources to stop sending
data, to reduce losses.

>
>
>
> Comment:


>
> This, then, essentially, means that for every non-routable packet, the
protocol must be informed -- as for with routing table "hits" for marking a
route as active, this is uncommon, and somewhat intrusive, as has been
discussed elsewhere.


Yes the route is informed to stop sending data from nodes of the reverse
forwarding path.

>
>
> Question:
> With that being said, as a router must send a message for each
non-delivered message, this also does sound like a formidable attack vector
against a router: pump it data packets to a set of non-existing address,
and watch it exhaust itself generating RERRs.
> How is that being guarded against?


No, the routers don't react only to its routes if there is no route entry
the packet is dropped. That is normal to any router. If the data packet was
for existing entries which are not valid then error is send back.

>
>
> Draft text:
> > Each upstream router that receives the RERR  marks the route as broken.
>
> Comment:
> So, essentially this implies that it is possible to do a
denial-of-service attack, by injecting RERRs and cause other devices to do
a RREQ flooding on the network -- draining battery, causing channel
congestion, etc.
>

This gets us out of context of draft, that text is in first section as
overview (not full details), so you need to read RERR handling. RERRs are
not listened only from neighbours.  See section 8.4 of handling RERR which
examines messages and secures that example you refer to. However, do you
want to suggest some edit to this overview section to make it refer to
other sections?

>
> Question:
> How is this protected against?
>
> Bigger Question:
> It is possible to attack a router, and the network *both* by sending
control signals and by sending data packets.


If any MANET router does not know its neighbours then yes attacks are
possible. Our protocols know their neighbours and active routes.

>
>
> One might device an "admission policy" based in ICVs on control signals,
that could be used to exclude (as in the above) a rogue RERR.
>
> How to protect against attacks-by-data-packets? Requiring ICVs on all
data packets seems unfeasible, what's the "way forward" for this?


When Routes are active then each router only forwards its neighbour.


Best Regards,

AB

--485b397dcf15c1eebd0502f19b83
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>My comment=C2=A0Subject draft: draft-ietf-manet-aodvv2-04 (last versio=
n=C2=A0submitted in 20 July).=C2=A0</div><div><br></div>Dear=C2=A0Thomas,<d=
iv><br></div><div>Thanks for your questions, my delay to reply have some re=
asons.=C2=A0I thought=C2=A0your question was for the WG chairs or AD or dra=
ft authors (the message was multiplexed with some texts=C2=A0that I have no=
 part in),=C2=A0but it can be understood that it addresses all=C2=A0WG.=C2=
=A0As I am taking a position of answering and editing on the list to help i=
n this draft&#39;s progress, I will answer your review-questions regarding =
the new submission version-draft,=C2=A0because any part of WG=C2=A0still di=
d not reply.=C2=A0<br>
<br>
On Tuesday, July 22, 2014, Thomas Clausen wrote:<br>
&gt;<br>
&gt; Given that =C2=A0we were told that a way forward for security had been=
 identified, but we were not allowed to know what that way forward was, =C2=
=A0I&#39;ll =C2=A0ask some specific questions that I hope can be answered.<=
br>
<br>
<br>
It is strange that you as a participant in the WG to be not allowed to know=
 about our/your work way (IMHO=C2=A0the WG chairs are responsible for such =
issue). I will=C2=A0do my best in discussing and=C2=A0participation with yo=
u=C2=A0for the=C2=A0draft progress.=C2=A0<br>
=C2=A0<br>
&gt;<br>
&gt;<br>
&gt; Page numbers refer to the document in &lt;subject&gt;<br>
&gt;<br>
&gt; --- Page 4 ---<br>
&gt;<br>
&gt; Draft text:<br>
&gt; &gt;=C2=A0When a data packet is received to=C2=A0 be forwarded but the=
re is no valid route for the destination,=C2=A0<br>
&gt; &gt; then=C2=A0 the AODVv2 router of the source of the packet is notif=
ied via a Route=C2=A0 Error (RERR)=C2=A0<br>
&gt; &gt; message.<br>
<br>
<br>I think that=C2=A0The route state is not valid or break=C2=A0as it was =
active, so it needs to send error message. Error messages are for sources t=
o stop sending data, to reduce losses.=C2=A0<br>
=C2=A0<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Comment:<br>
<br>
=C2=A0<br>
&gt;<br>
&gt; This, then, essentially, means that for every non-routable packet, the=
 protocol must be informed -- as for with routing table &quot;hits&quot; fo=
r marking a route as active, this is uncommon, and somewhat intrusive, as h=
as been discussed elsewhere.=C2=A0<br>
<br>
<br>
Yes the route is=C2=A0informed to stop sending data from nodes of=C2=A0the =
reverse forwarding path.=C2=A0</div><div><span></span><br>
&gt;<br>
&gt;<br>
&gt; Question:<br>
&gt; With that being said,=C2=A0as a router must send a message for each no=
n-delivered message, this also does sound like a formidable attack vector a=
gainst a router: pump it data packets to a set of non-existing address, and=
 watch it exhaust itself generating RERRs.<br>
&gt; How is that being guarded against?<br>
<br>
<br>
No, the routers don&#39;t react only to its routes if there is no route ent=
ry the packet is dropped. That is normal to any router. If the data packet =
was for existing entries which are not valid then error is send back.=C2=A0=
=C2=A0=C2=A0<br>
<br>
&gt;<br>
&gt;<br>
&gt; Draft text:<br>
&gt; &gt; Each upstream router that receives the RERR=C2=A0 marks the route=
 as broken.<br>
&gt;<br>
&gt; Comment:<br>
&gt; So, essentially this implies that it is possible to do a denial-of-ser=
vice attack, by injecting RERRs and cause other devices to do a RREQ floodi=
ng on the network -- draining battery, causing channel congestion, etc.<br>
&gt;<br>
<br>
This gets us out of context of draft, that text is in first section as over=
view (not full=C2=A0details),=C2=A0so you need to read RERR handling.=C2=A0=
RERRs are not listened only from neighbours. =C2=A0See section 8.4 of handl=
ing RERR which examines messages and secures that example=C2=A0you refer to=
. However, do you want to=C2=A0suggest some edit to this overview section t=
o make it refer to other sections?<br>
=C2=A0<br>
&gt;<br>
&gt; Question:<br>
&gt; How is this protected against?<br>
&gt;<br>
&gt; Bigger Question:<br>
&gt; It is possible to attack a router, and the network *both* by sending c=
ontrol signals and by sending data packets.=C2=A0<br>
<br>
<br>
If any MANET router does not know its neighbours then yes attacks are possi=
ble. Our protocols know their neighbours and active routes.=C2=A0<br>
=C2=A0<br>
&gt;<br>
&gt;<br>
&gt; One might device an &quot;admission policy&quot; based in ICVs on cont=
rol signals, that could be used to exclude (as in the above) a rogue RERR.<=
br>
&gt;<br>
&gt; How to protect against attacks-by-data-packets? Requiring ICVs on all =
data packets seems unfeasible, what&#39;s the &quot;way forward&quot; for t=
his?<br>
<br>
<br>
When=C2=A0Routes are active=C2=A0then each router only forwards its=C2=A0ne=
ighbour.<div><br></div><div><br>Best Regards,</div><div><br></div><div>AB</=
div></div>

--485b397dcf15c1eebd0502f19b83--


From nobody Sun Sep 14 05:29:56 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 556C91A0347 for <manet@ietfa.amsl.com>; Sun, 14 Sep 2014 05:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_SUMOF=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sx4IyJ6GVbRm for <manet@ietfa.amsl.com>; Sun, 14 Sep 2014 05:29:53 -0700 (PDT)
Received: from mail-yh0-x236.google.com (mail-yh0-x236.google.com [IPv6:2607:f8b0:4002:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E128A1A0346 for <manet@ietf.org>; Sun, 14 Sep 2014 05:29:52 -0700 (PDT)
Received: by mail-yh0-f54.google.com with SMTP id z6so1409180yhz.41 for <manet@ietf.org>; Sun, 14 Sep 2014 05:29:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=/y34ZGHUo9Dl734+B2OWEKRaMc3XO9ZH1SKBukrFaB4=; b=ujSeP+bQMndy7sZYWAG2HqNScox7nZL19MjYhEv5n35/svR/g63GbsNP5q+4BldzDM 2HDSN5Qo+keHP+yfoo5soHLrIfBKPHW2klytcRfw5ar1q+RcbHaz2gslU239rq7EcRYn cXPlr2czImiq5+uT57grT1GEVHTxF4g7RXmrQ4/D091ju4TD6HpNv1SBpmJ1y7FBjfoE oaTQjkkDwMr9u5ux4mCtcYK1BBO6zleDfS/tKlAF+GoWm27zdr0T0xPN5alIaDV69KrB uIoJ+wNxz42/zGMHNnuCNuVUkrrNFOojLrF6a7KifGBjzKdNJH1vi/MQoMH6eBtut9hu 6spg==
MIME-Version: 1.0
X-Received: by 10.236.172.161 with SMTP id t21mr1753056yhl.65.1410697792052; Sun, 14 Sep 2014 05:29:52 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Sun, 14 Sep 2014 05:29:51 -0700 (PDT)
Date: Sun, 14 Sep 2014 14:29:51 +0200
Message-ID: <CADnDZ8_1M2SUFGNoJ2vio_LemdgUoDWsHR92s5aiJTD9hfv73w@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Henning Rogge <hrogge@googlemail.com>, Emmanuel.Baccelli@inria.fr
Content-Type: multipart/alternative; boundary=20cf304273e0c7e41c050305ac22
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/trspJTDN2BgrHXU2-xR6__Y_ZfE
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-dat-metric@tools.ietf.org" <draft-ietf-manet-olsrv2-dat-metric@tools.ietf.org>
Subject: [manet] AB#1 Review for draft-ietf-manet-olsrv2-dat-metric (DAT metric for RFC7181)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Sep 2014 12:29:55 -0000

--20cf304273e0c7e41c050305ac22
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Reviewed draft name: draft-ietf-manet-olsrv2-dat-metric-02.
Date: 14.09.2014.

Dear WG editors, and All WG participants,

I thank you very much for this interesting work. I read the draft and don't
think the draft is ready for WGLC as Thomas proposed previously in July [1]
(no action/reply by WG yet for the proposal). Furthermore, I agree with the
comment of Thomas regarding IANA section, specially for
olsrv2 multitopology's consideration. However, IMHO the draft should be
clear who the RFC5444 packets belong to (from other discussions with WG,
they think it only belongs to the multiplexer), while measuring
link packets loss.

 The terminology section should clarify what are packets for this protocol,
is a packet: the link packet, control packet, data packet, IP packet, or
mixed, but because not clear about that it may taken more reading time. I
understand it is only link packets because this metric-protocol measures
only link packets. The WG draft in section 9 defines value for RFC5444
packet, but does not describe how it is implemented or does not mention the
unified multiplexer function. I suggest adding one section for multiplexing
considerations. I remember in one conversation [2], you suggested a code
line into right place. For this experimental protocol where will be the
right place to instruct RFC5444 to input value for packet sequence numbers.

[1]. http://www.ietf.org/mail-archive/web/manet/current/msg16741.html

[2]. http://www.ietf.org/mail-archive/web/manet/current/msg16987.html


AB> the draft needs to be clear what is the "packet loss". IMO it should
always say "link packet loss". Please amend.

In section 3:
Some links may have more than one routing protocol using it as RFC5498/5444
shares the number/port for all MANET protocols' control traffic.

--- OLD ---
If [RFC5444] control traffic is used to determine the link packet loss, the
administrator should take care that link layer multicast transmission do
not not have a higher reception probability than the slowest unicast
transmission.

--- NEW ---
If [RFC5444] control traffic is used to determine the average packet loss,
the administrator should take care the following: 1) that the control
traffic is owned by the routing protocol determining the metric, 2) that
link layer multicast transmission do not not have a higher reception
probability than the slowest unicast transmission.

In section 5:
The ratio is not average because it should be less than 1. The draft has to
determine that the ratio is per protocol not per multiplexer. IMHO The
draft is now calculating the ratio per multiplexer.

--- OLD ---
The average packet loss ratio is calculated as the sum of the =E2=80=99tota=
l
packets=E2=80=99 counters divided by the sum of the =E2=80=99packets receiv=
ed=E2=80=99 counters.
 This value is then divided through the current link-speed and then scaled
into the range of metrics allowed for OLSRv2.

--- NEW ---
The link packet loss value is calculated as the sum of the =E2=80=99total p=
ackets=E2=80=99
counters routing protocol links divided by the sum of the =E2=80=99packets
received=E2=80=99 counters for same links.  This average value is then divi=
ded
through the current link-speed and then scaled into the range of metrics
allowed for OLSRv2.

In section 6:

It says defines two constants that are defined but then refers to four
constants. I expect you mean the first two are MUST and the others are
mandatory per case. If that is case please clarify in the section.

In section 8.1:

Repeated packet sequence number initial ( please delete one).

--- OLD ---
L_DAT_lost_hello_messages :=3D 0 (no HELLO interval without packets).

--- NEW ---
L_DAT_lost_hello_messages :=3D 0 (no HELLO interval without a hello message=
).

In Section 9.3

---OLD---
While this metric was designed for measuring the packet loss based on the
[RFC5444] packet sequence number, some implementations might not be able to
add the packet sequence number to their output. Because of this the
following section contains multiple alternatives to calculate the packet
loss.

--- NEW ---
While this metric was designed for measuring the packet loss and link
speed based on the Link packet sequence number and the multiplexer
policy, some implementations might not be able to add the packet sequence
number to their output. Because of this the following section contains
multiple alternatives to calculate the packet loss.

In section 10:

You mention RFC5444 processing, what do you mean, I understand you
mean the unified multiplexing of RFC5444, is that what you mean?

Overall, looking into our WG drafts and RFCs, is the WG avoiding
mentioning the multiplexer function in its drafts for an unknown
reason? Is that an official editing procedure plan? Even the RFC5444
puts it in the appendix, which I think is the wrong place, if the WG
is considering interoperability.

Best Regards,

AB

This is the first review of AB for this WG draft.


On Friday, August 8, 2014, wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Mobile Ad-hoc Networks Working Group of
> the IETF.
>
>         Title           : Packet Sequence Number based directional airtim=
e
> metric for OLSRv2
>         Authors         : Henning Rogge
>                           Emmanuel Baccelli
>         Filename        : draft-ietf-manet-olsrv2-dat-metric-02.txt
>         Pages           : 17
>         Date            : 2014-08-08
>
> Abstract:
>    This document specifies an directional airtime link metric for usage
>    in OLSRv2.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-02
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2-dat-metric-02
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--20cf304273e0c7e41c050305ac22
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Reviewed draft=C2=A0name: draft-ietf-manet-olsrv2-dat-metric-02.=C2=A0=
</div><div>Date: 14.09.2014.=C2=A0</div><div><br></div>Dear WG editors,=C2=
=A0and All WG participants,<div><br></div><div>I thank you very much=C2=A0f=
or this interesting work.=C2=A0I read the draft and don&#39;t think the dra=
ft is ready for WGLC as Thomas proposed=C2=A0previously in July=C2=A0[1] (n=
o action/reply=C2=A0by WG yet for the proposal).=C2=A0Furthermore,=C2=A0I a=
gree with the comment of Thomas regarding IANA section,=C2=A0specially for =
olsrv2=C2=A0multitopology&#39;s consideration. However, IMHO=C2=A0the=C2=A0=
draft should be clear who the=C2=A0RFC5444=C2=A0packets belong to (from oth=
er discussions with WG, they think it only=C2=A0belongs to the=C2=A0multipl=
exer), while measuring link=C2=A0packets loss.=C2=A0</div><div><br></div><d=
iv>=C2=A0The terminology section should clarify what are=C2=A0packets for t=
his protocol, is a packet: the=C2=A0link packet, control packet, data packe=
t, IP packet, or mixed, but=C2=A0because not clear about that=C2=A0it may=
=C2=A0taken more reading time.=C2=A0I understand it is only=C2=A0link packe=
ts because this metric-protocol measures only=C2=A0link packets.=C2=A0The W=
G=C2=A0draft in section 9=C2=A0defines value for RFC5444 packet, but does n=
ot describe how it is implemented=C2=A0or does not=C2=A0mention the unified=
 multiplexer function. I suggest adding one section for multiplexing consid=
erations. I remember in one conversation [2],=C2=A0you suggested a code lin=
e into right place. For this experimental=C2=A0protocol where will be=C2=A0=
the right place to instruct RFC5444 to input value for=C2=A0packet=C2=A0seq=
uence numbers.=C2=A0</div><div><br></div><div>[1].=C2=A0<a href=3D"http://w=
ww.ietf.org/mail-archive/web/manet/current/msg16741.html">http://www.ietf.o=
rg/mail-archive/web/manet/current/msg16741.html</a><br></div><div><span></s=
pan></div><div><br></div><div>[2].=C2=A0<a href=3D"http://www.ietf.org/mail=
-archive/web/manet/current/msg16987.html" target=3D"_blank">http://www.ietf=
.org/mail-archive/web/manet/current/msg16987.html</a><br></div><div><br></d=
iv><div><br></div>AB&gt; the draft needs to be clear what is the &quot;pack=
et loss&quot;.=C2=A0IMO it should always say &quot;link packet loss&quot;. =
Please amend.=C2=A0<br><div><br></div><div>In section 3:</div><div>Some lin=
ks may have more than one routing protocol using it as RFC5498/5444 shares =
the number/port for all MANET protocols&#39;=C2=A0control traffic.=C2=A0</d=
iv><div><br></div><div>--- OLD ---</div><div>If [RFC5444] control traffic i=
s used to determine the link packet loss, the administrator should take car=
e that link layer multicast transmission do not not have a higher reception=
 probability than the slowest unicast transmission.<br></div><div><br></div=
><div>--- NEW ---</div><div>If [RFC5444] control traffic is used to determi=
ne the average=C2=A0packet loss, the administrator should take care the fol=
lowing: 1) that the control traffic is owned by the routing protocol determ=
ining the metric, 2)=C2=A0that link layer multicast transmission do not not=
 have a higher reception probability than the slowest unicast transmission.=
=C2=A0<br></div><div><br></div><div>In section 5:</div>The ratio is not ave=
rage because=C2=A0it=C2=A0should be less than 1. The draft has to determine=
 that the ratio is per protocol not per multiplexer. IMHO=C2=A0The draft is=
 now calculating the ratio=C2=A0per multiplexer.=C2=A0<div><br></div><div>-=
-- OLD ---</div><div>The average packet loss ratio is calculated as the sum=
 of the =E2=80=99total packets=E2=80=99 counters divided by the sum of the =
=E2=80=99packets received=E2=80=99 counters. =C2=A0This value is then divid=
ed through the current link-speed and then scaled into the range of metrics=
 allowed for OLSRv2.</div><div><br></div><div>--- NEW ---</div><div>The lin=
k=C2=A0packet loss value=C2=A0is calculated as the sum of the =E2=80=99tota=
l packets=E2=80=99 counters=C2=A0routing=C2=A0protocol links=C2=A0divided b=
y the sum of the =E2=80=99packets received=E2=80=99 counters for same links=
. =C2=A0This average=C2=A0value is then divided through the current link-sp=
eed and then scaled into the range of metrics allowed for OLSRv2.<br><div><=
br></div><div>In section 6:</div><div><br></div><div>It says defines two co=
nstants that are defined but then refers to four constants. I expect you me=
an the first two are MUST and the others are mandatory per case. If that is=
 case please clarify in the section.=C2=A0</div><div><br></div><div>In sect=
ion 8.1:</div><div><br></div><div>Repeated packet sequence number initial (=
 please delete one).=C2=A0</div><div><br></div><div>--- OLD ---</div><div>L=
_DAT_lost_hello_messages :=3D 0 (no HELLO interval without packets).<br></d=
iv><div><br></div><div>--- NEW ---</div><div>L_DAT_lost_hello_messages :=3D=
 0 (no HELLO interval without a=C2=A0hello message).<br></div><div><br></di=
v><div>In=C2=A0Section 9.3</div><div><br></div><div>---OLD---</div><div><sp=
an style=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleBody;fo=
nt-size:17px;line-height:22px;text-decoration:-webkit-letterpress">While th=
is metric was designed for measuring the packet loss based on=C2=A0</span><=
span style=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleBody;=
font-size:17px;line-height:16.5pt;text-decoration:-webkit-letterpress">the =
[RFC5444] packet sequence number, some implementations might not=C2=A0</spa=
n><span style=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleBo=
dy;font-size:17px;line-height:16.5pt;text-decoration:-webkit-letterpress">b=
e able to add the packet sequence number to their output. Because=C2=A0</sp=
an><span style=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleB=
ody;font-size:17px;line-height:16.5pt;text-decoration:-webkit-letterpress">=
of this the following section contains multiple alternatives to=C2=A0</span=
><span style=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleBod=
y;font-size:17px;line-height:16.5pt;text-decoration:-webkit-letterpress">ca=
lculate the packet loss.</span><br></div><div><span style=3D"color:rgba(0,0=
,0,0.701961);font-family:UICTFontTextStyleBody;font-size:17px;line-height:1=
6.5pt;text-decoration:-webkit-letterpress"><br></span></div><div><span styl=
e=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleBody;font-size=
:17px;line-height:16.5pt;text-decoration:-webkit-letterpress">--- NEW ---</=
span></div><div><span style=3D"color:rgba(0,0,0,0.701961);font-family:UICTF=
ontTextStyleBody;font-size:17px;line-height:22px;text-decoration:-webkit-le=
tterpress">While this metric was designed for measuring the packet loss and=
 link speed=C2=A0based on=C2=A0</span><span style=3D"color:rgba(0,0,0,0.701=
961);font-family:UICTFontTextStyleBody;font-size:17px;line-height:16.5pt;te=
xt-decoration:-webkit-letterpress">the Link=C2=A0packet sequence number and=
 the multiplexer policy,=C2=A0some implementations might not=C2=A0</span><s=
pan style=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleBody;f=
ont-size:17px;line-height:16.5pt;text-decoration:-webkit-letterpress">be ab=
le to add the packet sequence number to their output. Because=C2=A0</span><=
span style=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleBody;=
font-size:17px;line-height:16.5pt;text-decoration:-webkit-letterpress">of t=
his the following section contains multiple alternatives to=C2=A0</span><sp=
an style=3D"color:rgba(0,0,0,0.701961);font-family:UICTFontTextStyleBody;fo=
nt-size:17px;line-height:16.5pt;text-decoration:-webkit-letterpress">calcul=
ate the packet loss.</span><span style=3D"color:rgba(0,0,0,0.701961);font-f=
amily:UICTFontTextStyleBody;font-size:17px;line-height:16.5pt;text-decorati=
on:-webkit-letterpress"><br></span></div><div>
	=09
=09
=09
		<div title=3D"Page 9">
			<div>
				<div>
					<div>
						<pre><span style=3D"font-family:&#39;Helvetica Neue&#39;,Helvetica,Ar=
ial,sans-serif">In section 10: </span><br></pre><pre><font face=3D"Helvetic=
a Neue, Helvetica, Arial, sans-serif">You mention RFC5444 processing, what =
do you mean, I understand you mean the unified multiplexing of RFC5444, is =
that what you mean?</font></pre><pre><span style=3D"font-family:&#39;Helvet=
ica Neue&#39;,Helvetica,Arial,sans-serif">Overall, looking into our WG draf=
ts and RFCs, is the WG avoiding mentioning the multiplexer function </span>=
<span style=3D"font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-se=
rif">in its drafts for an unknown reason? Is that an official editing proce=
dure plan? Even the RFC5444 puts it in the appendix, which I think is the w=
rong place, if the WG is considering interoperability. </span><br></pre><pr=
e><span style=3D"font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-=
serif">Best Regards,</span></pre></div></div></div></div>AB</div><div><br><=
/div><div>This is the first review of=C2=A0AB for=C2=A0this WG=C2=A0draft.=
=C2=A0</div><div><br></div><div><br>On Friday, August 8, 2014,   wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=C2=A0This draft is a work item of the Mobile Ad-hoc Networks Working Group=
 of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Packet Sequence Number based directional airtime metric for OLSRv2<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Henn=
ing Rogge<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Emmanuel Baccelli<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-manet-olsrv2-dat-metric-02.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 17<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2014-08-08<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document specifies an directional airtime link metric for=
 usage<br>
=C2=A0 =C2=A0in OLSRv2.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-met=
ric/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-manet-o=
lsrv2-dat-metric/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-02=
" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-=
metric-02</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2-dat-m=
etric-02" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-m=
anet-olsrv2-dat-metric-02</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a>manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div>
</div>

--20cf304273e0c7e41c050305ac22--


From nobody Sun Sep 14 09:32:39 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0811A00A8 for <manet@ietfa.amsl.com>; Sun, 14 Sep 2014 09:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5QIwYWqjpR0m for <manet@ietfa.amsl.com>; Sun, 14 Sep 2014 09:32:34 -0700 (PDT)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DF5F1A00BA for <manet@ietf.org>; Sun, 14 Sep 2014 09:32:32 -0700 (PDT)
Received: by mail-yk0-f171.google.com with SMTP id 79so1557069ykr.2 for <manet@ietf.org>; Sun, 14 Sep 2014 09:32:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wevspWfTv6fQg2pmq9LyNGNviCazJuvh5Wk+wvzz/hQ=; b=woSQsMbufXdHsuxPtwDSb1IxJeO5BHtNGFQo3xbCIHwewLc0BzucSn6P71hleSe4nM oTalB5rjyh3OZ7Y8vIU4bl0qTJ3XnVFrQ9gZPpWmHg/BTzYaGenMx5pe8BIRgtr9mmf8 dJELW82xEKtN15uk60zHEb8gnDFPJP9R7DogPg1W5EHN0Uy/FKNHcq258qLMbExYYhnc DD0rvWgJNXkLnYzVDsnWi/+mVoIM/6vd8M7ofn09n2pXxK0/OlU66rrpCJ6g2c9p2+Q7 zI96l1FX0YlNXULPxVI++3PQIfHLkcNzeq/+sseDO1ipS6Usx56q2Dgw2QOpaOhUaHR4 GHeg==
MIME-Version: 1.0
X-Received: by 10.236.140.11 with SMTP id d11mr26738784yhj.16.1410712352370; Sun, 14 Sep 2014 09:32:32 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Sun, 14 Sep 2014 09:32:32 -0700 (PDT)
In-Reply-To: <CADnDZ89CbBO8zxCRP0kMw8gHFvvXaUR57PnS5hAzhEB-XuGyFA@mail.gmail.com>
References: <CADnDZ8-ArnYio0V+EWY0u3nadx+rOuD=k4YVBRyKtbD0TcH+ew@mail.gmail.com> <CADnDZ8_mbgKcE_gDSOc97tK=VcLAKSpv+4ZAcWjvmFKi4NSX5g@mail.gmail.com> <CADnDZ89CbBO8zxCRP0kMw8gHFvvXaUR57PnS5hAzhEB-XuGyFA@mail.gmail.com>
Date: Sun, 14 Sep 2014 18:32:32 +0200
Message-ID: <CADnDZ89s34PNzceVFOTLg6U+Eiwsf2E=bLRCwYTS0D-921o8Og@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: manet <manet@ietf.org>
Content-Type: multipart/alternative; boundary=20cf303ea3e4a4ce940503091083
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/9qU4aLvoMzPSke5r9zk7r9vNY94
Cc: "manet-chairs@tools.ietf.org" <manet-chairs@tools.ietf.org>
Subject: [manet] Request to update MANET-WG-Milestones
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Sep 2014 16:32:36 -0000

--20cf303ea3e4a4ce940503091083
Content-Type: text/plain; charset=UTF-8

Please update the WG milestone for WG drafts listed below, with
reasonable dates. Most of them need to be added because the WG adopted them
(I may forgotten some because of the volume). For AODVv2 and DLEP the date
past.

draft-ietf-manet-aodvv2
draft-ietf-manet-dlep
draft-ietf-manet-report-mib

draft-ietf-manet-olsrv2-multitopology
draft-ietf-manet-nhdp-optimization
draft-ietf-manet-olsrv2-dat-metric
draft-ietf-manet-olsrv2-management-snapshot
draft-ietf-manet-olsrv2-multipath

draft-ietf-manet-rfc6779bis
draft-ietf-manet-smf-sec-threats

It is important for me to see the milestones so I can progress. Please note
that my reviews/participation depend on WG milestones not on WG calls (IMHO
the WG calls should consider milestones to help guid participation).
Thanking you.


AB

--20cf303ea3e4a4ce940503091083
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br>Please update the WG=C2=A0milestone for WG drafts listed below, with re=
asonable=C2=A0dates.=C2=A0Most of them need to be added because the WG adop=
ted them (I may forgotten some because of the volume). For AODVv2 and DLEP=
=C2=A0the date past.=C2=A0<br><div><br></div><div><div>draft-ietf-manet-aod=
vv2</div><div>draft-ietf-manet-dlep</div><div>draft-ietf-manet-report-mib</=
div><div><br></div>draft-ietf-manet-olsrv2-multitopology<br><div>draft-ietf=
-manet-nhdp-optimization<span style=3D"white-space:pre-wrap">	</span></div>=
<div>draft-ietf-manet-olsrv2-dat-metric</div><div>draft-ietf-manet-olsrv2-m=
anagement-snapshot</div><div>draft-ietf-manet-olsrv2-multipath</div><div><b=
r></div><div>draft-ietf-manet-rfc6779bis</div><div>draft-ietf-manet-smf-sec=
-threats</div></div><div><br></div><div>It is important for me to see the m=
ilestones so I can progress. Please note that my reviews/participation depe=
nd on WG=C2=A0milestones not on WG=C2=A0calls (IMHO the WG calls should con=
sider milestones to help guid participation). Thanking you.=C2=A0<br></div>=
<div><br></div><br><div>AB</div>

--20cf303ea3e4a4ce940503091083--


From nobody Sun Sep 14 22:28:44 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 567BB1A064D; Sun, 14 Sep 2014 22:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3m2mMjT8dOyW; Sun, 14 Sep 2014 22:28:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 466E01A065B; Sun, 14 Sep 2014 22:28:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140915052837.6967.42757.idtracker@ietfa.amsl.com>
Date: Sun, 14 Sep 2014 22:28:37 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/qK8G-L2n6BpOJ-5f-d2tN-CRBDU
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-smf-sec-threats-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 05:28:40 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

        Title           : Security Threats for Simplified Multicast Forwarding (SMF)
        Authors         : Jiazi Yi
                          Thomas Heide Clausen
                          Ulrich Herberg
	Filename        : draft-ietf-manet-smf-sec-threats-01.txt
	Pages           : 14
	Date            : 2014-09-14

Abstract:
   This document analyzes security threats of the Simplified Multicast
   Forwarding (SMF), including the vulnerabilities of duplicate packet
   detection and relay set selection mechanisms.  This document is not
   intended to propose solutions to the threats described.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-smf-sec-threats/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-manet-smf-sec-threats-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-smf-sec-threats-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Sep 14 22:42:03 2014
Return-Path: <yi.jiazi@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 312DC1A0663 for <manet@ietfa.amsl.com>; Sun, 14 Sep 2014 22:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DN0OHiZNqNzL for <manet@ietfa.amsl.com>; Sun, 14 Sep 2014 22:41:53 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C81B1A064D for <manet@ietf.org>; Sun, 14 Sep 2014 22:41:53 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id u57so3394048wes.29 for <manet@ietf.org>; Sun, 14 Sep 2014 22:41:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=Q/zZ1nwZ0innM863tH4LluNZcbyTR2OdETI7wiPbs/k=; b=v1r0Nxmrf08e+XXerOSji+tCA9A81tcBN7cdv9CLfF2leki678A9UDlTu0cbSu+4U7 vDwcq9cBhswoRZ43+pSSxbEuf8QitfAQROFE0qxDo+io9K0j6HAJxUynaY8YRQQrDIjp WbteMhulREXGPraKK0l00FatmUknBP/PtcIu9osJh2Rkwwnix+kNA37VGlzpaoNEBld2 zkYE+/EjjSaDkUbjnMsxQz05cdR1EI9I8N8nsYurs1fsEmUK5XREZGhIx+gHAzXAn1hd /gLE1Pjer7GcVD+A5/TN44F9Et6w8kqmynf2E6a6eoWEajZv0HwvMQlexZdNuS6m4R95 dL8g==
MIME-Version: 1.0
X-Received: by 10.194.78.243 with SMTP id e19mr419071wjx.119.1410759711907; Sun, 14 Sep 2014 22:41:51 -0700 (PDT)
Sender: yi.jiazi@gmail.com
Received: by 10.194.86.169 with HTTP; Sun, 14 Sep 2014 22:41:51 -0700 (PDT)
In-Reply-To: <20140915052837.6967.21309.idtracker@ietfa.amsl.com>
References: <20140915052837.6967.21309.idtracker@ietfa.amsl.com>
Date: Mon, 15 Sep 2014 13:41:51 +0800
X-Google-Sender-Auth: iwtTe_u5F38FymRpEIMwtTR4raU
Message-ID: <CAN1bDFy8_rW8dO3dU_cGB0SX1gJXpBOTVXTfXofnnJrNhqJW8w@mail.gmail.com>
From: Jiazi YI <jiazi@jiaziyi.com>
To: manet <manet@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bfcf01c7de35605031417c1
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/1NrdHrycDR8DA-spePeE-QbBwxI
Subject: [manet] Fwd: New Version Notification for draft-ietf-manet-smf-sec-threats-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 05:41:55 -0000

--047d7bfcf01c7de35605031417c1
Content-Type: text/plain; charset=UTF-8

Dear all,

A new revision of the smf-sec-threats has been submitted.
Compared to the previous revision, some figures are added to explain the
attacks, and a new section "Future work" is added to discuss possibilities
to secure the protocol in the future, as the AD suggested for RFC7186.

Your comments are appreciated.

regards

Jiazi

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Mon, Sep 15, 2014 at 1:28 PM
Subject: New Version Notification for
draft-ietf-manet-smf-sec-threats-01.txt
To: Ulrich Herberg <ulrich@herberg.name>, "Thomas H. Clausen" <
T.Clausen@computer.org>, Jiazi Yi <jiazi@jiaziyi.com>, Thomas Heide Clausen
<t.clausen@computer.org>



A new version of I-D, draft-ietf-manet-smf-sec-threats-01.txt
has been successfully submitted by Jiazi Yi and posted to the
IETF repository.

Name:           draft-ietf-manet-smf-sec-threats
Revision:       01
Title:          Security Threats for Simplified Multicast Forwarding (SMF)
Document date:  2014-09-14
Group:          manet
Pages:          14
URL:
http://www.ietf.org/internet-drafts/draft-ietf-manet-smf-sec-threats-01.txt
Status:
https://datatracker.ietf.org/doc/draft-ietf-manet-smf-sec-threats/
Htmlized:
http://tools.ietf.org/html/draft-ietf-manet-smf-sec-threats-01
Diff:
http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-smf-sec-threats-01

Abstract:
   This document analyzes security threats of the Simplified Multicast
   Forwarding (SMF), including the vulnerabilities of duplicate packet
   detection and relay set selection mechanisms.  This document is not
   intended to propose solutions to the threats described.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--047d7bfcf01c7de35605031417c1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear all,=C2=A0</div><div><br></div><div>A new revisi=
on of the smf-sec-threats has been submitted.=C2=A0</div><div>Compared to t=
he previous revision, some figures are added to explain the attacks, and a =
new section &quot;Future work&quot; is added to discuss possibilities to se=
cure the protocol in the future, as the AD suggested for RFC7186.=C2=A0</di=
v><div><br></div><div>Your comments are appreciated.=C2=A0</div><div><br></=
div><div>regards</div><div><br></div><div>Jiazi</div><br><div class=3D"gmai=
l_quote">---------- Forwarded message ----------<br>From: <b class=3D"gmail=
_sendername"></b> <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@i=
etf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;</span><br>Date:=
 Mon, Sep 15, 2014 at 1:28 PM<br>Subject: New Version Notification for draf=
t-ietf-manet-smf-sec-threats-01.txt<br>To: Ulrich Herberg &lt;<a href=3D"ma=
ilto:ulrich@herberg.name" target=3D"_blank">ulrich@herberg.name</a>&gt;, &q=
uot;Thomas H. Clausen&quot; &lt;<a href=3D"mailto:T.Clausen@computer.org" t=
arget=3D"_blank">T.Clausen@computer.org</a>&gt;, Jiazi Yi &lt;<a href=3D"ma=
ilto:jiazi@jiaziyi.com" target=3D"_blank">jiazi@jiaziyi.com</a>&gt;, Thomas=
 Heide Clausen &lt;<a href=3D"mailto:t.clausen@computer.org" target=3D"_bla=
nk">t.clausen@computer.org</a>&gt;<br><br><br><br>
A new version of I-D, draft-ietf-manet-smf-sec-threats-01.txt<br>
has been successfully submitted by Jiazi Yi and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-manet-smf-sec-thre=
ats<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A001<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Security Threats for Simplified Mu=
lticast Forwarding (SMF)<br>
Document date:=C2=A0 2014-09-14<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 manet<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 14<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://www.ietf.or=
g/internet-drafts/draft-ietf-manet-smf-sec-threats-01.txt" target=3D"_blank=
">http://www.ietf.org/internet-drafts/draft-ietf-manet-smf-sec-threats-01.t=
xt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-ietf-manet-smf-sec-threats/" target=3D"_blank">https://data=
tracker.ietf.org/doc/draft-ietf-manet-smf-sec-threats/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://tools.ietf.org/html/d=
raft-ietf-manet-smf-sec-threats-01" target=3D"_blank">http://tools.ietf.org=
/html/draft-ietf-manet-smf-sec-threats-01</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.ietf.or=
g/rfcdiff?url2=3Ddraft-ietf-manet-smf-sec-threats-01" target=3D"_blank">htt=
p://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-manet-smf-sec-threats-01</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document analyzes security threats of the Simplified Mult=
icast<br>
=C2=A0 =C2=A0Forwarding (SMF), including the vulnerabilities of duplicate p=
acket<br>
=C2=A0 =C2=A0detection and relay set selection mechanisms.=C2=A0 This docum=
ent is not<br>
=C2=A0 =C2=A0intended to propose solutions to the threats described.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div>

--047d7bfcf01c7de35605031417c1--


From nobody Mon Sep 15 11:49:07 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7D31A6F45; Mon, 15 Sep 2014 11:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ty15jmYvZSM7; Mon, 15 Sep 2014 11:48:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E26A1A86ED; Mon, 15 Sep 2014 11:31:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140915183153.8242.48801.idtracker@ietfa.amsl.com>
Date: Mon, 15 Sep 2014 11:31:53 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/vCf6nhgwWuuC6vRJ6W9SD6Zs1MY
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-management-snapshot-03.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 18:49:03 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

        Title           : Snapshot of OLSRv2-Routed MANET Management
        Authors         : Thomas Clausen
                          Ulrich Herberg
	Filename        : draft-ietf-manet-olsrv2-management-snapshot-03.txt
	Pages           : 14
	Date            : 2014-09-15

Abstract:
   This document describes how Mobile Ad Hoc Networks (MANETs) are
   typically managed, in terms of pre-deployment management, as well as
   rationale and means of monitoring and management of MANET routers
   running the Optimized Link State Routing protocol version 2 (OLSRv2)
   and its constituent MANET Neighborhood Discovery Protocol (NHDP).
   Apart from pre-deployment management for setting up IP addresses and
   security related credentials, OLSRv2 only needs routers to agree one
   single configuration parameter (called "C").  Other parameters for
   tweaking network performance may be determined during operation of
   the network, and need not be the same in all routers.  This, using
   MIB modules and related management protocols such as SNMP (or
   possibly other, less "chatty", protocols).  In addition, for
   debugging purposes, monitoring data and performance related counters,
   as well as notifications ("traps") can be sent to the Network
   Management System (NMS) via standardized management protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-management-snapshot/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-manet-olsrv2-management-snapshot-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-management-snapshot-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Sep 15 12:06:00 2014
Return-Path: <ulrich@herberg.name>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B161A6F3E for <manet@ietfa.amsl.com>; Mon, 15 Sep 2014 12:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yXZf4xlwyaMU for <manet@ietfa.amsl.com>; Mon, 15 Sep 2014 12:05:54 -0700 (PDT)
Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3446D1A7020 for <manet@ietf.org>; Mon, 15 Sep 2014 11:57:26 -0700 (PDT)
Received: by mail-vc0-f176.google.com with SMTP id la4so3797519vcb.7 for <manet@ietf.org>; Mon, 15 Sep 2014 11:57:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=sNmotHc4CiL7fDgSGXNKLaoIKeTwTs/XYqGcRUW7xzw=; b=t4RcAb0qfi9MCawyoa+a539pcK7fM2uCTNf8AdN9TA6MJBAlBsdKQ1hYGWQpyMh1S+ 9+S0DCAEQKMdyBugNhnXVK8LvrVsAwjHcCGNVUqUmn+jrNP2ZfevibOsw3Vmu0j4yH2H /mtpgVHgjtRYcGAbJHjxxSnSyH9QqYJ5pYXOo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=sNmotHc4CiL7fDgSGXNKLaoIKeTwTs/XYqGcRUW7xzw=; b=P2xt3XxJKAuXPhZByFt6m9A1aZpO34/Y8XFmhdCe+6GnIBaMM3PFCWiFM6MSCgVJaI bEJGXQcD0BAo3EQWbauKkGgtnWQ6gg35pddws6rRUyBFiqD41/sO6FTsA8jfNQXHJSe9 zKxQopVWmCoH09ZxL8X9+3yooC89vS9Iy97focg0QAlcH5hO1Ze+VT76YJwlnnsdgGNA LsM6LlcwFuLUK0kvRxXu22Lm1EgEbniSwcQfIMEBWdvOcF6+8tnfDiPn2N5xq5cosCqw 0X45fom+jwOeX1R4tk9Fw6rTV/0fvi3aPsw+eI46avx+iBDz02u0x4XGKmid9EFmuWc4 1/tg==
X-Gm-Message-State: ALoCoQmuCOgRADLzaLdetX3mmLzYbtvRy4kzbo7wgRiCyqnMUEdlcPxkh7wuvB3Ws2YfTMGVPkDl
MIME-Version: 1.0
X-Received: by 10.220.97.5 with SMTP id j5mr25138395vcn.16.1410807445237; Mon, 15 Sep 2014 11:57:25 -0700 (PDT)
Received: by 10.220.85.211 with HTTP; Mon, 15 Sep 2014 11:57:25 -0700 (PDT)
In-Reply-To: <20140915183153.8242.48801.idtracker@ietfa.amsl.com>
References: <20140915183153.8242.48801.idtracker@ietfa.amsl.com>
Date: Mon, 15 Sep 2014 11:57:25 -0700
Message-ID: <CAK=bVC-chZ=n4vjdRXwTPyZywXGDrp3CcCYC1tdSj1gQrayUtQ@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: manet@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/e0qCXEwneQSgJbgfgMRNmqxkqkg
Subject: Re: [manet] I-D Action: draft-ietf-manet-olsrv2-management-snapshot-03.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 19:05:55 -0000

We submitted a new revision of
draft-ietf-manet-olsrv2-management-snapshot, addressing multiple
comments we received from the shepherd review. The changes are
editorial plus some clarifications.

Best regards
Ulrich

On Mon, Sep 15, 2014 at 11:31 AM,  <internet-drafts@ietf.org> wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.
>
>         Title           : Snapshot of OLSRv2-Routed MANET Management
>         Authors         : Thomas Clausen
>                           Ulrich Herberg
>         Filename        : draft-ietf-manet-olsrv2-management-snapshot-03.txt
>         Pages           : 14
>         Date            : 2014-09-15
>
> Abstract:
>    This document describes how Mobile Ad Hoc Networks (MANETs) are
>    typically managed, in terms of pre-deployment management, as well as
>    rationale and means of monitoring and management of MANET routers
>    running the Optimized Link State Routing protocol version 2 (OLSRv2)
>    and its constituent MANET Neighborhood Discovery Protocol (NHDP).
>    Apart from pre-deployment management for setting up IP addresses and
>    security related credentials, OLSRv2 only needs routers to agree one
>    single configuration parameter (called "C").  Other parameters for
>    tweaking network performance may be determined during operation of
>    the network, and need not be the same in all routers.  This, using
>    MIB modules and related management protocols such as SNMP (or
>    possibly other, less "chatty", protocols).  In addition, for
>    debugging purposes, monitoring data and performance related counters,
>    as well as notifications ("traps") can be sent to the Network
>    Management System (NMS) via standardized management protocols.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-management-snapshot/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-manet-olsrv2-management-snapshot-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-management-snapshot-03
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Mon Sep 15 14:50:59 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C9681A87BE; Mon, 15 Sep 2014 14:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gFOQ3coKNyhD; Mon, 15 Sep 2014 14:50:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7381A87C4; Mon, 15 Sep 2014 14:50:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140915215053.30430.38357.idtracker@ietfa.amsl.com>
Date: Mon, 15 Sep 2014 14:50:53 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/hRVGsZWLFW3lBG8s3awT3hhP6T0
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-multipath-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 21:50:56 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

        Title           : Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)
        Authors         : Jiazi Yi
                          Benoit Parrein
	Filename        : draft-ietf-manet-olsrv2-multipath-01.txt
	Pages           : 18
	Date            : 2014-09-15

Abstract:
   This document specifies a multi-path extension to the Optimized Link
   State Routing Protocol version 2 (OLSRv2) to discover multiple
   disjoint paths, so as to improve reliability of the OLSRv2 protocol.
   The interoperability with OLSRv2 is retained.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-manet-olsrv2-multipath-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-multipath-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Sep 15 14:55:25 2014
Return-Path: <yi.jiazi@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 095E71A879A for <manet@ietfa.amsl.com>; Mon, 15 Sep 2014 14:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oV3JkNBF-4h for <manet@ietfa.amsl.com>; Mon, 15 Sep 2014 14:55:23 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 866281A02BA for <manet@ietf.org>; Mon, 15 Sep 2014 14:55:23 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id w61so4700036wes.28 for <manet@ietf.org>; Mon, 15 Sep 2014 14:55:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=KR2GNjZwdEFyEd/Ovfr6kzXbDAvV9XkuExr5nd0GPzY=; b=o1PyAZEjjSEtYnIrhQw7INUitk1+Vtao4vUZWeXYuCDrALa2fKOrj8VJK/A92zhb7I pJxjku+Bi0MU2gQg0j6TPaKjV5zlEUGB/1ltGx4FpG2dNld8h04sCUHe1WXMkkCt4Btk hBA938wYMHZzOIx8ekLtegg+PgiVXVJUYYmjj5pfDohptjIDAqiYF99IKPaM+ganF7vR xC9Lpe/LpJ/nLqSNutFoY/kf80afdpNYCJlV+dYdQMQt9LCFdZVVhAwBhOhrzdwRbU5g d8g3T8V14dxCGOwTJnJA0+OZaEueriMNc3AmwHJXZAtLN8YVYYoDfjsPkAq7fmIy9GIF rK+Q==
MIME-Version: 1.0
X-Received: by 10.180.149.169 with SMTP id ub9mr27363217wib.32.1410818122141;  Mon, 15 Sep 2014 14:55:22 -0700 (PDT)
Sender: yi.jiazi@gmail.com
Received: by 10.194.176.226 with HTTP; Mon, 15 Sep 2014 14:55:22 -0700 (PDT)
In-Reply-To: <20140915215053.30430.98654.idtracker@ietfa.amsl.com>
References: <20140915215053.30430.98654.idtracker@ietfa.amsl.com>
Date: Tue, 16 Sep 2014 05:55:22 +0800
X-Google-Sender-Auth: riIJXjg-d2WkVr1Y-dn-i8PkIcM
Message-ID: <CAN1bDFwQknD=0YmPFDwGDRtJ=VSRrjGXXVNeVM6SAu_SYa0GRg@mail.gmail.com>
From: Jiazi YI <ietf@jiaziyi.com>
To: manet <manet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c38aea03541e050321b109
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/D5cBexeaBpM1VxR5qHLERQoBmns
Subject: [manet] Fwd: New Version Notification for draft-ietf-manet-olsrv2-multipath-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 21:55:25 -0000

--001a11c38aea03541e050321b109
Content-Type: text/plain; charset=UTF-8

Dear all,

A new revision of the draft-ietf-manet-olsrv2-multipath has been submitted.

Based on the comments received, we improved the forwarding process, and
added the security consideration section.

Your comments are welcome and appreciated.

regards

Jiazi

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Tue, Sep 16, 2014 at 5:50 AM
Subject: New Version Notification for
draft-ietf-manet-olsrv2-multipath-01.txt
To: Jiazi Yi <jiazi@jiaziyi.com>, Benoit Parrein <
benoit.parrein@polytech.univ-nantes.fr>, Benoit Parrein <
Benoit.Parrein@polytech.univ-nantes.fr>



A new version of I-D, draft-ietf-manet-olsrv2-multipath-01.txt
has been successfully submitted by Jiazi Yi and posted to the
IETF repository.

Name:           draft-ietf-manet-olsrv2-multipath
Revision:       01
Title:          Multi-path Extension for the Optimized Link State Routing
Protocol version 2 (OLSRv2)
Document date:  2014-09-15
Group:          manet
Pages:          18
URL:
http://www.ietf.org/internet-drafts/draft-ietf-manet-olsrv2-multipath-01.txt
Status:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/
Htmlized:
http://tools.ietf.org/html/draft-ietf-manet-olsrv2-multipath-01
Diff:
http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-multipath-01

Abstract:
   This document specifies a multi-path extension to the Optimized Link
   State Routing Protocol version 2 (OLSRv2) to discover multiple
   disjoint paths, so as to improve reliability of the OLSRv2 protocol.
   The interoperability with OLSRv2 is retained.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--001a11c38aea03541e050321b109
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear all,=C2=A0</div><div><br></div><div>A new revisi=
on of the draft-ietf-manet-olsrv2-multipath has been submitted.=C2=A0</div>=
<div><br></div><div>Based on the comments received, we improved the forward=
ing process, and added the security consideration section.=C2=A0</div><div>=
<br></div><div>Your comments are welcome and appreciated.=C2=A0</div><div><=
br></div><div>regards</div><div><br></div><div>Jiazi</div><br><div class=3D=
"gmail_quote">---------- Forwarded message ----------<br>From: <b class=3D"=
gmail_sendername"></b> <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-dra=
fts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;</span><br>=
Date: Tue, Sep 16, 2014 at 5:50 AM<br>Subject: New Version Notification for=
 draft-ietf-manet-olsrv2-multipath-01.txt<br>To: Jiazi Yi &lt;<a href=3D"ma=
ilto:jiazi@jiaziyi.com" target=3D"_blank">jiazi@jiaziyi.com</a>&gt;, Benoit=
 Parrein &lt;<a href=3D"mailto:benoit.parrein@polytech.univ-nantes.fr" targ=
et=3D"_blank">benoit.parrein@polytech.univ-nantes.fr</a>&gt;, Benoit Parrei=
n &lt;<a href=3D"mailto:Benoit.Parrein@polytech.univ-nantes.fr" target=3D"_=
blank">Benoit.Parrein@polytech.univ-nantes.fr</a>&gt;<br><br><br><br>
A new version of I-D, draft-ietf-manet-olsrv2-multipath-01.txt<br>
has been successfully submitted by Jiazi Yi and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-manet-olsrv2-multi=
path<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A001<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Multi-path Extension for the Optim=
ized Link State Routing Protocol version 2 (OLSRv2)<br>
Document date:=C2=A0 2014-09-15<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 manet<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 18<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://www.ietf.or=
g/internet-drafts/draft-ietf-manet-olsrv2-multipath-01.txt" target=3D"_blan=
k">http://www.ietf.org/internet-drafts/draft-ietf-manet-olsrv2-multipath-01=
.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-ietf-manet-olsrv2-multipath/" target=3D"_blank">https://dat=
atracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://tools.ietf.org/html/d=
raft-ietf-manet-olsrv2-multipath-01" target=3D"_blank">http://tools.ietf.or=
g/html/draft-ietf-manet-olsrv2-multipath-01</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.ietf.or=
g/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2-multipath-01" target=3D"_blank">ht=
tp://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2-multipath-01</a><b=
r>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document specifies a multi-path extension to the Optimize=
d Link<br>
=C2=A0 =C2=A0State Routing Protocol version 2 (OLSRv2) to discover multiple=
<br>
=C2=A0 =C2=A0disjoint paths, so as to improve reliability of the OLSRv2 pro=
tocol.<br>
=C2=A0 =C2=A0The interoperability with OLSRv2 is retained.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div>

--001a11c38aea03541e050321b109--


From nobody Mon Sep 15 15:27:19 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C8161A87C3 for <manet@ietfa.amsl.com>; Mon, 15 Sep 2014 15:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNQU242W1O20 for <manet@ietfa.amsl.com>; Mon, 15 Sep 2014 15:27:16 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DD451A879A for <manet@ietf.org>; Mon, 15 Sep 2014 15:27:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 39FB92412F3; Mon, 15 Sep 2014 15:27:16 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.142] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 3FD25240E7C; Mon, 15 Sep 2014 15:27:15 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-D17F3868-115F-4859-9784-F7BC06B1FAC1
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <thomas@thomasclausen.org>
X-Mailer: iPad Mail (12A365)
In-Reply-To: <CAN1bDFwQknD=0YmPFDwGDRtJ=VSRrjGXXVNeVM6SAu_SYa0GRg@mail.gmail.com>
Date: Tue, 16 Sep 2014 00:27:11 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <DA6C1C3E-6417-47B7-A4C2-845DABCBBAAE@thomasclausen.org>
References: <20140915215053.30430.98654.idtracker@ietfa.amsl.com> <CAN1bDFwQknD=0YmPFDwGDRtJ=VSRrjGXXVNeVM6SAu_SYa0GRg@mail.gmail.com>
To: Jiazi YI <ietf@jiaziyi.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/eOMfQScmKJ7bGPZCN836-l_ZiDk
Cc: manet <manet@ietf.org>
Subject: Re: [manet] Fwd: New Version Notification for draft-ietf-manet-olsrv2-multipath-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 22:27:18 -0000

--Apple-Mail-D17F3868-115F-4859-9784-F7BC06B1FAC1
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Jiazi,

Thanks. I've not read this revision yet, but to guide my doing, a question: a=
ny outstanding issues in the document, i.e., thing that you know needs work,=
 or are you pretty much satisfied that it's "good to go"?

Best,

Thomas

Sent from my iPad

> On 15 Sep 2014, at 23:55, Jiazi YI <ietf@jiaziyi.com> wrote:
>=20
> Dear all,=20
>=20
> A new revision of the draft-ietf-manet-olsrv2-multipath has been submitted=
.=20
>=20
> Based on the comments received, we improved the forwarding process, and ad=
ded the security consideration section.=20
>=20
> Your comments are welcome and appreciated.=20
>=20
> regards
>=20
> Jiazi
>=20
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Tue, Sep 16, 2014 at 5:50 AM
> Subject: New Version Notification for draft-ietf-manet-olsrv2-multipath-01=
.txt
> To: Jiazi Yi <jiazi@jiaziyi.com>, Benoit Parrein <benoit.parrein@polytech.=
univ-nantes.fr>, Benoit Parrein <Benoit.Parrein@polytech.univ-nantes.fr>
>=20
>=20
>=20
> A new version of I-D, draft-ietf-manet-olsrv2-multipath-01.txt
> has been successfully submitted by Jiazi Yi and posted to the
> IETF repository.
>=20
> Name:           draft-ietf-manet-olsrv2-multipath
> Revision:       01
> Title:          Multi-path Extension for the Optimized Link State Routing P=
rotocol version 2 (OLSRv2)
> Document date:  2014-09-15
> Group:          manet
> Pages:          18
> URL:            http://www.ietf.org/internet-drafts/draft-ietf-manet-olsrv=
2-multipath-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-m=
ultipath/
> Htmlized:       http://tools.ietf.org/html/draft-ietf-manet-olsrv2-multipa=
th-01
> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2=
-multipath-01
>=20
> Abstract:
>    This document specifies a multi-path extension to the Optimized Link
>    State Routing Protocol version 2 (OLSRv2) to discover multiple
>    disjoint paths, so as to improve reliability of the OLSRv2 protocol.
>    The interoperability with OLSRv2 is retained.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of submissi=
on
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-D17F3868-115F-4859-9784-F7BC06B1FAC1
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Jiazi,</div><div><br></div><div>Thanks=
. I've not read this revision yet, but to guide my doing, a question: any ou=
tstanding issues in the document, i.e., thing that you know needs work, or a=
re you pretty much satisfied that it's "good to go"?</div><div><br></div><di=
v>Best,</div><div><br></div><div>Thomas</div><div><br></div><div>Sent from m=
y iPad</div><div><br>On 15 Sep 2014, at 23:55, Jiazi YI &lt;<a href=3D"mailt=
o:ietf@jiaziyi.com">ietf@jiaziyi.com</a>&gt; wrote:<br><br></div><blockquote=
 type=3D"cite"><div><div dir=3D"ltr"><div>Dear all,&nbsp;</div><div><br></di=
v><div>A new revision of the draft-ietf-manet-olsrv2-multipath has been subm=
itted.&nbsp;</div><div><br></div><div>Based on the comments received, we imp=
roved the forwarding process, and added the security consideration section.&=
nbsp;</div><div><br></div><div>Your comments are welcome and appreciated.&nb=
sp;</div><div><br></div><div>regards</div><div><br></div><div>Jiazi</div><br=
><div class=3D"gmail_quote">---------- Forwarded message ----------<br>From:=
 <b class=3D"gmail_sendername"></b> <span dir=3D"ltr">&lt;<a href=3D"mailto:=
internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;=
</span><br>Date: Tue, Sep 16, 2014 at 5:50 AM<br>Subject: New Version Notifi=
cation for draft-ietf-manet-olsrv2-multipath-01.txt<br>To: Jiazi Yi &lt;<a h=
ref=3D"mailto:jiazi@jiaziyi.com" target=3D"_blank">jiazi@jiaziyi.com</a>&gt;=
, Benoit Parrein &lt;<a href=3D"mailto:benoit.parrein@polytech.univ-nantes.f=
r" target=3D"_blank">benoit.parrein@polytech.univ-nantes.fr</a>&gt;, Benoit P=
arrein &lt;<a href=3D"mailto:Benoit.Parrein@polytech.univ-nantes.fr" target=3D=
"_blank">Benoit.Parrein@polytech.univ-nantes.fr</a>&gt;<br><br><br><br>
A new version of I-D, draft-ietf-manet-olsrv2-multipath-01.txt<br>
has been successfully submitted by Jiazi Yi and posted to the<br>
IETF repository.<br>
<br>
Name:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;draft-ietf-manet-olsrv2-multip=
ath<br>
Revision:&nbsp; &nbsp; &nbsp; &nbsp;01<br>
Title:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Multi-path Extension for the Optimi=
zed Link State Routing Protocol version 2 (OLSRv2)<br>
Document date:&nbsp; 2014-09-15<br>
Group:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; manet<br>
Pages:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 18<br>
URL:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href=3D"http://www.ietf.org=
/internet-drafts/draft-ietf-manet-olsrv2-multipath-01.txt" target=3D"_blank"=
>http://www.ietf.org/internet-drafts/draft-ietf-manet-olsrv2-multipath-01.tx=
t</a><br>
Status:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"https://datatracker.ietf=
.org/doc/draft-ietf-manet-olsrv2-multipath/" target=3D"_blank">https://datat=
racker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/</a><br>
Htmlized:&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"http://tools.ietf.org/html/dr=
aft-ietf-manet-olsrv2-multipath-01" target=3D"_blank">http://tools.ietf.org/=
html/draft-ietf-manet-olsrv2-multipath-01</a><br>
Diff:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"http://www.ietf.org=
/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2-multipath-01" target=3D"_blank">http=
://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2-multipath-01</a><br>
<br>
Abstract:<br>
&nbsp; &nbsp;This document specifies a multi-path extension to the Optimized=
 Link<br>
&nbsp; &nbsp;State Routing Protocol version 2 (OLSRv2) to discover multiple<=
br>
&nbsp; &nbsp;disjoint paths, so as to improve reliability of the OLSRv2 prot=
ocol.<br>
&nbsp; &nbsp;The interoperability with OLSRv2 is retained.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submission=
<br>
until the htmlized version and diff are available at <a href=3D"http://tools=
.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>manet mailing list</span><br><sp=
an><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mai=
lman/listinfo/manet</a></span><br></div></blockquote></body></html>=

--Apple-Mail-D17F3868-115F-4859-9784-F7BC06B1FAC1--


From nobody Mon Sep 15 22:58:57 2014
Return-Path: <yi.jiazi@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15A2B1A02E4 for <manet@ietfa.amsl.com>; Mon, 15 Sep 2014 22:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DGi0uZp9a3KD for <manet@ietfa.amsl.com>; Mon, 15 Sep 2014 22:58:54 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 192F81A02D1 for <manet@ietf.org>; Mon, 15 Sep 2014 22:58:53 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id n12so4974041wgh.5 for <manet@ietf.org>; Mon, 15 Sep 2014 22:58:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=VTmeEnBqlNAOi6ZIar3i8ph36UJ74AXgamCFCKT/6hw=; b=x5SknZINqtckxcv7ZP+6yLCPDDaiQaglTMyqdfv2XivOjlwda/dUB3hNPBgC7SSVFo BnnZS5YfMFmA1FfBAEywflK/r+V6gsv8VfzsWz5U7xxMWQVwHagZCAVefEmbEN7S4sRq Pw40RApeMf7YK5XaQq9ulM4j/E2+NAIOsdvASjgtfLu70X5JaIAJ7h8aYZJPjAnAx6pb IdS6z0sOljc0bSoUPHTRLImegEBFXXXuy8bx6VybA1ekJx+n1Mtcrpmu/iMoLySFUk4d Kgq70mtv4O5fL5i4HbdaCjl+2AeJNQstpkZuV+2QRRJjOuwmfbSQxpsO4Vk159mv/0uq cmpQ==
MIME-Version: 1.0
X-Received: by 10.194.200.137 with SMTP id js9mr17163152wjc.90.1410847132541;  Mon, 15 Sep 2014 22:58:52 -0700 (PDT)
Sender: yi.jiazi@gmail.com
Received: by 10.194.176.226 with HTTP; Mon, 15 Sep 2014 22:58:52 -0700 (PDT)
In-Reply-To: <DA6C1C3E-6417-47B7-A4C2-845DABCBBAAE@thomasclausen.org>
References: <20140915215053.30430.98654.idtracker@ietfa.amsl.com> <CAN1bDFwQknD=0YmPFDwGDRtJ=VSRrjGXXVNeVM6SAu_SYa0GRg@mail.gmail.com> <DA6C1C3E-6417-47B7-A4C2-845DABCBBAAE@thomasclausen.org>
Date: Tue, 16 Sep 2014 13:58:52 +0800
X-Google-Sender-Auth: LkNpTzzMV31Y-pio7mKnh0Mj5y0
Message-ID: <CAN1bDFzaPreMJk7ii-N3z1Fvm8h18zvEyOgk9fidg6YF3jfc7g@mail.gmail.com>
From: Jiazi YI <ietf@jiaziyi.com>
To: Thomas Clausen <thomas@thomasclausen.org>
Content-Type: multipart/alternative; boundary=047d7bb70c742aea250503287266
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/LQ1Ocuj2C8VtVO4QhtS7TkzGFus
Cc: manet <manet@ietf.org>
Subject: Re: [manet] Fwd: New Version Notification for draft-ietf-manet-olsrv2-multipath-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 05:58:56 -0000

--047d7bb70c742aea250503287266
Content-Type: text/plain; charset=UTF-8

Hi,

It would be good to have careful review of the interoperability with OLSRv2
and the new security consideration section.

best

Jiazi

On Tue, Sep 16, 2014 at 6:27 AM, Thomas Clausen <thomas@thomasclausen.org>
wrote:

> Jiazi,
>
> Thanks. I've not read this revision yet, but to guide my doing, a
> question: any outstanding issues in the document, i.e., thing that you know
> needs work, or are you pretty much satisfied that it's "good to go"?
>
> Best,
>
> Thomas
>
> Sent from my iPad
>
> On 15 Sep 2014, at 23:55, Jiazi YI <ietf@jiaziyi.com> wrote:
>
> Dear all,
>
> A new revision of the draft-ietf-manet-olsrv2-multipath has been
> submitted.
>
> Based on the comments received, we improved the forwarding process, and
> added the security consideration section.
>
> Your comments are welcome and appreciated.
>
> regards
>
> Jiazi
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Tue, Sep 16, 2014 at 5:50 AM
> Subject: New Version Notification for
> draft-ietf-manet-olsrv2-multipath-01.txt
> To: Jiazi Yi <jiazi@jiaziyi.com>, Benoit Parrein <
> benoit.parrein@polytech.univ-nantes.fr>, Benoit Parrein <
> Benoit.Parrein@polytech.univ-nantes.fr>
>
>
>
> A new version of I-D, draft-ietf-manet-olsrv2-multipath-01.txt
> has been successfully submitted by Jiazi Yi and posted to the
> IETF repository.
>
> Name:           draft-ietf-manet-olsrv2-multipath
> Revision:       01
> Title:          Multi-path Extension for the Optimized Link State Routing
> Protocol version 2 (OLSRv2)
> Document date:  2014-09-15
> Group:          manet
> Pages:          18
> URL:
> http://www.ietf.org/internet-drafts/draft-ietf-manet-olsrv2-multipath-01.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/
> Htmlized:
> http://tools.ietf.org/html/draft-ietf-manet-olsrv2-multipath-01
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-multipath-01
>
> Abstract:
>    This document specifies a multi-path extension to the Optimized Link
>    State Routing Protocol version 2 (OLSRv2) to discover multiple
>    disjoint paths, so as to improve reliability of the OLSRv2 protocol.
>    The interoperability with OLSRv2 is retained.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--047d7bb70c742aea250503287266
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>It would be good to have careful re=
view of the interoperability with OLSRv2 and the new security consideration=
 section.=C2=A0</div><div><br></div><div>best</div><div><br></div><div>Jiaz=
i</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On T=
ue, Sep 16, 2014 at 6:27 AM, Thomas Clausen <span dir=3D"ltr">&lt;<a href=
=3D"mailto:thomas@thomasclausen.org" target=3D"_blank">thomas@thomasclausen=
.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"au=
to"><div>Jiazi,</div><div><br></div><div>Thanks. I&#39;ve not read this rev=
ision yet, but to guide my doing, a question: any outstanding issues in the=
 document, i.e., thing that you know needs work, or are you pretty much sat=
isfied that it&#39;s &quot;good to go&quot;?</div><div><br></div><div>Best,=
</div><div><br></div><div>Thomas</div><div><br></div><div>Sent from my iPad=
</div><div><div class=3D"h5"><div><br>On 15 Sep 2014, at 23:55, Jiazi YI &l=
t;<a href=3D"mailto:ietf@jiaziyi.com" target=3D"_blank">ietf@jiaziyi.com</a=
>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"ltr"><=
div>Dear all,=C2=A0</div><div><br></div><div>A new revision of the draft-ie=
tf-manet-olsrv2-multipath has been submitted.=C2=A0</div><div><br></div><di=
v>Based on the comments received, we improved the forwarding process, and a=
dded the security consideration section.=C2=A0</div><div><br></div><div>You=
r comments are welcome and appreciated.=C2=A0</div><div><br></div><div>rega=
rds</div><div><br></div><div>Jiazi</div><br><div class=3D"gmail_quote">----=
------ Forwarded message ----------<br>From: <b class=3D"gmail_sendername">=
</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" targ=
et=3D"_blank">internet-drafts@ietf.org</a>&gt;</span><br>Date: Tue, Sep 16,=
 2014 at 5:50 AM<br>Subject: New Version Notification for draft-ietf-manet-=
olsrv2-multipath-01.txt<br>To: Jiazi Yi &lt;<a href=3D"mailto:jiazi@jiaziyi=
.com" target=3D"_blank">jiazi@jiaziyi.com</a>&gt;, Benoit Parrein &lt;<a hr=
ef=3D"mailto:benoit.parrein@polytech.univ-nantes.fr" target=3D"_blank">beno=
it.parrein@polytech.univ-nantes.fr</a>&gt;, Benoit Parrein &lt;<a href=3D"m=
ailto:Benoit.Parrein@polytech.univ-nantes.fr" target=3D"_blank">Benoit.Parr=
ein@polytech.univ-nantes.fr</a>&gt;<br><br><br><br>
A new version of I-D, draft-ietf-manet-olsrv2-multipath-01.txt<br>
has been successfully submitted by Jiazi Yi and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-manet-olsrv2-multi=
path<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A001<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Multi-path Extension for the Optim=
ized Link State Routing Protocol version 2 (OLSRv2)<br>
Document date:=C2=A0 2014-09-15<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 manet<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 18<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://www.ietf.or=
g/internet-drafts/draft-ietf-manet-olsrv2-multipath-01.txt" target=3D"_blan=
k">http://www.ietf.org/internet-drafts/draft-ietf-manet-olsrv2-multipath-01=
.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-ietf-manet-olsrv2-multipath/" target=3D"_blank">https://dat=
atracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://tools.ietf.org/html/d=
raft-ietf-manet-olsrv2-multipath-01" target=3D"_blank">http://tools.ietf.or=
g/html/draft-ietf-manet-olsrv2-multipath-01</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.ietf.or=
g/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2-multipath-01" target=3D"_blank">ht=
tp://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-manet-olsrv2-multipath-01</a><b=
r>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document specifies a multi-path extension to the Optimize=
d Link<br>
=C2=A0 =C2=A0State Routing Protocol version 2 (OLSRv2) to discover multiple=
<br>
=C2=A0 =C2=A0disjoint paths, so as to improve reliability of the OLSRv2 pro=
tocol.<br>
=C2=A0 =C2=A0The interoperability with OLSRv2 is retained.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div>
</div></blockquote></div></div><blockquote type=3D"cite"><div><span>_______=
________________________________________</span><br><span>manet mailing list=
</span><br><span><a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@=
ietf.org</a></span><br><span><a href=3D"https://www.ietf.org/mailman/listin=
fo/manet" target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a>=
</span><br></div></blockquote></div></blockquote></div><br></div>

--047d7bb70c742aea250503287266--


From nobody Tue Sep 16 01:22:05 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 995F21A00AB for <manet@ietfa.amsl.com>; Tue, 16 Sep 2014 01:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_SUMOF=1, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5wrqnttRezjR for <manet@ietfa.amsl.com>; Tue, 16 Sep 2014 01:22:02 -0700 (PDT)
Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0DB01A00B9 for <manet@ietf.org>; Tue, 16 Sep 2014 01:22:01 -0700 (PDT)
Received: by mail-qc0-f171.google.com with SMTP id x13so3277744qcv.30 for <manet@ietf.org>; Tue, 16 Sep 2014 01:22:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=61RxH9U7P1vSJMGnDv+4mMdLmeEUx6myLqkmQ6LDmHM=; b=QVUmbjIm/DGWhvxh2PeWyoslnzfLuuXegjyYCxI+t2tYMXteA0QKHNQ16TwczPu13Y 5hoY/A0ymssDvpzs2uMqzQOnu08DjwWcII94LfcVU1ErxVqxsPYWJ++mWsjmP21Qq0Ge Af5ONRfHr2EH8vtxsMKEvIHzGVzt3GJtBmiHoqgQlZeMDyazw3oWwSjXaRWOEHMzGC7O zyte7UkpLzVte4pWBboPkssFWScOQeEShlNSabjm0vfoFjwAyHuZtWSSyiC1M9L6cTIA wolFOYjdFeJsCEwSDFSxUJZetqiIAcMBg9euGkr0aXmTPDlf3rgGGKntB6Ke0OiTVBPs sk9g==
X-Received: by 10.224.162.196 with SMTP id w4mr43233500qax.60.1410855721073; Tue, 16 Sep 2014 01:22:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.184.9 with HTTP; Tue, 16 Sep 2014 01:21:40 -0700 (PDT)
In-Reply-To: <CADnDZ8_1M2SUFGNoJ2vio_LemdgUoDWsHR92s5aiJTD9hfv73w@mail.gmail.com>
References: <CADnDZ8_1M2SUFGNoJ2vio_LemdgUoDWsHR92s5aiJTD9hfv73w@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 16 Sep 2014 10:21:40 +0200
Message-ID: <CAGnRvuo3urLBHo1iVkyn-aXPU9piU-80y4Au65+Kg9HeQ0YiEA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/Yzc8_XUFvyyEjNrUE_g_sHur7j4
Cc: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-dat-metric@tools.ietf.org" <draft-ietf-manet-olsrv2-dat-metric@tools.ietf.org>
Subject: Re: [manet] AB#1 Review for draft-ietf-manet-olsrv2-dat-metric (DAT metric for RFC7181)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 08:22:03 -0000

On Sun, Sep 14, 2014 at 2:29 PM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> Reviewed draft name: draft-ietf-manet-olsrv2-dat-metric-02.
> Date: 14.09.2014.
>
> Dear WG editors, and All WG participants,
>
> I thank you very much for this interesting work. I read the draft and don=
't
> think the draft is ready for WGLC as Thomas proposed previously in July [=
1]
> (no action/reply by WG yet for the proposal). Furthermore, I agree with t=
he
> comment of Thomas regarding IANA section, specially for olsrv2
> multitopology's consideration.
If you read the IANA section of the olsrv2 multitopology draft, you
will notice the extended 'administrative action' part.

So the question about if this draft (which does not extend the
definition of outgoing RFC5444 packets/messages on its own) needs a
Type Extension registration is still open.

> However, IMHO the draft should be clear who
> the RFC5444 packets belong to (from other discussions with WG, they think=
 it
> only belongs to the multiplexer), while measuring link packets loss.

This draft does not define any extension of the RFC5444 packets, it
just uses what has been suggested in RFC5444 (and its errata).

>  The terminology section should clarify what are packets for this protoco=
l,
> is a packet: the link packet, control packet, data packet, IP packet, or
> mixed, but because not clear about that it may taken more reading time. I
> understand it is only link packets because this metric-protocol measures
> only link packets.

As you can (and should) read in the draft it defines several ways to
measure the link packet loss. Depending on your choice you measure
something different.

In addition to this the term "link packets" doesn't make much sense...
link packet loss describes the packet loss on a link... not the loss
of a special kind of packet. I hope you are aware what a "link" is.

> The WG draft in section 9 defines value for RFC5444
> packet, but does not describe how it is implemented or does not mention t=
he
> unified multiplexer function. I suggest adding one section for multiplexi=
ng
> considerations.

Again, this draft does not define new RFC5444 messages, nor does it
add new TLVs. It only mandates the presence of the packet sequence
number as it has been described in RFC5444 (and errata).

> I remember in one conversation [2], you suggested a code
> line into right place. For this experimental protocol where will be the
> right place to instruct RFC5444 to input value for packet sequence number=
s.
>
> [1]. http://www.ietf.org/mail-archive/web/manet/current/msg16741.html
>
> [2]. http://www.ietf.org/mail-archive/web/manet/current/msg16987.html

As you can read in my mail you linked in [2], the comment was about an
implementation. Implementation specific details should not be part of
this draft.

> AB> the draft needs to be clear what is the "packet loss". IMO it should
> always say "link packet loss". Please amend.
>
> In section 3:
> Some links may have more than one routing protocol using it as RFC5498/54=
44
> shares the number/port for all MANET protocols' control traffic.

Please re-read the section about packet-sequence number based link
loss measurements. The advantage (and challenge) of this is that you
can use the RFC5444 protocol traffic of ALL protocols using the MANET
port defined in RFC5498. As long as its a RFC5444 packet going the the
multicast address defined in RFC5498, you can use it without even
looking into the protocol specific messages. The more RFC5444 packets
you get, the more exact will be the estimated link loss.

> --- OLD ---
> If [RFC5444] control traffic is used to determine the link packet loss, t=
he
> administrator should take care that link layer multicast transmission do =
not
> not have a higher reception probability than the slowest unicast
> transmission.
>
> --- NEW ---
> If [RFC5444] control traffic is used to determine the average packet loss=
,
> the administrator should take care the following: 1) that the control
> traffic is owned by the routing protocol determining the metric, 2) that
> link layer multicast transmission do not not have a higher reception
> probability than the slowest unicast transmission.

Two paragraphs above you suggest using "link packet loss" everywhere
and now you suggest replacing it by "average packet loss"?

> In section 5:
> The ratio is not average because it should be less than 1.

Yes, it is an average... no, it is not below 1.

As you can read in RFC7181 we have to deal with link COSTS, which
means "low is good, high is bad". So the ratio this draft talks about
is total packets divided by received packets. This is equivalent to
the link costs described in the ETX and ETT papers referenced by this
draft.

> The draft has to
> determine that the ratio is per protocol not per multiplexer. IMHO The dr=
aft
> is now calculating the ratio per multiplexer.

Ratio per multiplexer? I am not sure what you are talking about.

> --- OLD ---
> The average packet loss ratio is calculated as the sum of the =E2=80=99to=
tal
> packets=E2=80=99 counters divided by the sum of the =E2=80=99packets rece=
ived=E2=80=99 counters.
> This value is then divided through the current link-speed and then scaled
> into the range of metrics allowed for OLSRv2.
>
> --- NEW ---
> The link packet loss value is calculated as the sum of the =E2=80=99total=
 packets=E2=80=99
> counters routing protocol links divided by the sum of the =E2=80=99packet=
s received=E2=80=99
> counters for same links.  This average value is then divided through the
> current link-speed and then scaled into the range of metrics allowed for
> OLSRv2.

I don't think this text change makes any sense.

> In section 6:
>
> It says defines two constants that are defined but then refers to four
> constants.

Yes, this is definitely a bug, thank you for finding it.

> I expect you mean the first two are MUST and the others are
> mandatory per case. If that is case please clarify in the section.

All of the constants are similar important.

But replacing "two constants" by "multiple constants" should fix the proble=
m.

> In section 8.1:
>
> Repeated packet sequence number initial ( please delete one).
>
> --- OLD ---
> L_DAT_lost_hello_messages :=3D 0 (no HELLO interval without packets).
>
> --- NEW ---
> L_DAT_lost_hello_messages :=3D 0 (no HELLO interval without a hello messa=
ge).

No, that is wrong. The draft does only need to "estimate" any loss if
it doesn't get any RFC5444 packet over a link. As soon as it receives
a single RFC5444 packet, it can calculate the earlier packet losses
based on the packet sequence number so the L_DAT_lost_hello_messages
is really the number of HELLO intervals without any received RFC5444
packets.

> In Section 9.3
>
> ---OLD---
> While this metric was designed for measuring the packet loss based on the
> [RFC5444] packet sequence number, some implementations might not be able =
to
> add the packet sequence number to their output. Because of this the
> following section contains multiple alternatives to calculate the packet
> loss.
>
> --- NEW ---
> While this metric was designed for measuring the packet loss and link spe=
ed
> based on the Link packet sequence number and the multiplexer policy, some
> implementations might not be able to add the packet sequence number to th=
eir
> output. Because of this the following section contains multiple alternati=
ves
> to calculate the packet loss.

No, this is wrong. The link speed is NOT based on the packet sequence numbe=
rs.

Not sure what you want to say with the multiplexer policy.

> In section 10:
>
> You mention RFC5444 processing, what do you mean, I understand you mean t=
he
> unified multiplexing of RFC5444, is that what you mean?

It means section 9, which describes the parsing of data incoming
through RFC5444 packets and messages.

> Overall, looking into our WG drafts and RFCs, is the WG avoiding mentioni=
ng
> the multiplexer function in its drafts for an unknown reason? Is that an
> official editing procedure plan? Even the RFC5444 puts it in the appendix=
,
> which I think is the wrong place, if the WG is considering interoperabili=
ty.

Its not the job of this draft to describe the multiplexer part for
RFC5444. It just reads existing incoming information, including the
packet sequence number content described in RFC5444.

Henning Rogge


From nobody Wed Sep 17 05:06:56 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB321A0202 for <manet@ietfa.amsl.com>; Wed, 17 Sep 2014 05:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PDaoAG2jp73Q for <manet@ietfa.amsl.com>; Wed, 17 Sep 2014 05:06:53 -0700 (PDT)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C2961A0203 for <manet@ietf.org>; Wed, 17 Sep 2014 05:06:53 -0700 (PDT)
Received: by mail-qc0-f176.google.com with SMTP id x3so451790qcv.7 for <manet@ietf.org>; Wed, 17 Sep 2014 05:06:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=gBxNEmtjmpxylnKoMNeAx4IGB8m2qpfnzq+VL1yLgow=; b=ZsxFxt3RxYTpmsXZA8/mwa8xREh5z31Vscgo2lRkYRzX0AQpH4H8jKPqpAj/dgLXP+ ZvfufQJB4Ffbnhfa3hkH26HufWMVk8blpY4g+Hpz66rZ9aUGjvYvNu2b8XrEulAKtC2p pEU5kFlURlnGQYSYiTUmHseiUcHtvo38o+wV5Qhj80i5J9Y/P4OJYs1Ho2Vkiy8AvDtM N5SI+/PFQ9CGU0JQLit6jA/0mKXAVLhvVlmbdNx4Z80yA6ank8g+I63VgOmk/hfok0qZ rWALtnVVWZHr7k9nIQMvRGOnla6BIpORCjeLr8G/MsBGruXaLgBfQ2t/mITymkNzJqjH WyBA==
MIME-Version: 1.0
X-Received: by 10.236.155.234 with SMTP id j70mr20132799yhk.74.1410955612414;  Wed, 17 Sep 2014 05:06:52 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Wed, 17 Sep 2014 05:06:52 -0700 (PDT)
Date: Wed, 17 Sep 2014 14:06:52 +0200
Message-ID: <CADnDZ8-qFnwt1bYdCL9kXR-V3VdW_r9r6qTzBDoy_TYCkrcMWA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Henning Rogge <hrogge@googlemail.com>,  "Emmanuel.Baccelli@inria.fr" <Emmanuel.Baccelli@inria.fr>
Content-Type: multipart/alternative; boundary=20cf302d4986126883050341b447
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/klLlvCnljHPlDw0C9o-idg2uc7s
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-dat-metric@tools.ietf.org" <draft-ietf-manet-olsrv2-dat-metric@tools.ietf.org>
Subject: [manet] AB#2 Review for draft-ietf-manet-olsrv2-dat-metric (DAT metric for RFC7181)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 12:06:55 -0000

--20cf302d4986126883050341b447
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Regarding the review of [1] to the draft-01 it was not reflected totally
regarding to section 10. The editors mention in [2] that it done the update
related to that review, but I see that the editing of section 10 is still
not clear to show the two modes as was clear from Thomas's edit/review.


In [1] it was more clear for the protocol processing modes as:
{{
10. Processing Directives
10.1 Processing Directives for =E2=80=9CMode A=E2=80=9D
10.2 Additional Processing Directives for when using =E2=80=9CMode B=E2=80=
=9D

I note that section 10 in the above would have a ton of subsections,
essentially capturing the current 9.3.1 to 11
}}

The metric has two modes, but not clearly presented in draft-02. Therefore,
I suggest amending the section title of 10 and its subsection as it is more
clear in [1] than in the draft-02.

[1]. http://www.ietf.org/mail-archive/web/manet/current/msg16741.html
[2]. http://www.ietf.org/mail-archive/web/manet/current/msg16808.html

AB

--20cf302d4986126883050341b447
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Regarding the review of [1] to the draft-01 it was not reflected total=
ly regarding to section 10. The editors mention in [2] that it done the upd=
ate related to that review,=C2=A0but I see that the editing of section 10 i=
s still not clear to show the two modes as was clear from Thomas&#39;s edit=
/review.=C2=A0</div><div><br></div><div><br></div><div>In [1] it was more c=
lear for the protocol processing=C2=A0modes=C2=A0as:</div><div>{{</div><div=
><font><span style=3D"background-color:rgba(255,255,255,0)">10. Processing =
Directives</span></font></div><div><font><span style=3D"background-color:rg=
ba(255,255,255,0)"></span></font><span style=3D"background-color:rgba(255,2=
55,255,0);font-size:small">10.1 Processing Directives for =E2=80=9CMode A=
=E2=80=9D</span></div><div><font><span style=3D"background-color:rgba(255,2=
55,255,0)"></span></font><span style=3D"background-color:rgba(255,255,255,0=
);font-size:small">10.2 Additional Processing Directives for when using =E2=
=80=9CMode B=E2=80=9D</span></div><div><font><span style=3D"background-colo=
r:rgba(255,255,255,0)"><br></span></font></div><div><font><span style=3D"ba=
ckground-color:rgba(255,255,255,0)"></span></font><font><span style=3D"back=
ground-color:rgba(255,255,255,0)">I note that section 10 in the above would=
 have a ton of subsections, essentially=C2=A0</span></font><span style=3D"b=
ackground-color:rgba(255,255,255,0);font-size:small">capturing the current =
9.3.1 to 11</span></div><div><span style=3D"background-color:rgba(255,255,2=
55,0);font-size:small">}}</span></div><div><span style=3D"background-color:=
rgba(255,255,255,0);font-size:small"><br></span></div><div><span style=3D"b=
ackground-color:rgba(255,255,255,0);font-size:small">The metric has two mod=
es, but not clearly presented in draft-02.=C2=A0Therefore, I suggest amendi=
ng the section title of 10=C2=A0and its=C2=A0subsection=C2=A0as it is more =
clear in [1] than in the draft-02.</span></div><div><span style=3D"backgrou=
nd-color:rgba(255,255,255,0);font-size:small"><br></span></div><div><div><f=
ont><span style=3D"background-color:rgba(255,255,255,0)">[1].=C2=A0<a href=
=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16741.html" targe=
t=3D"_blank">http://www.ietf.org/mail-archive/web/manet/current/msg16741.ht=
ml</a><br></span></font></div><div><font>[2].=C2=A0<a href=3D"http://www.ie=
tf.org/mail-archive/web/manet/current/msg16808.html">http://www.ietf.org/ma=
il-archive/web/manet/current/msg16808.html</a></font></div></div><div><font=
><br></font></div><div><font>AB</font></div><div>=C2=A0</div>

--20cf302d4986126883050341b447--


From nobody Wed Sep 17 23:01:33 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC81B1A7010 for <manet@ietfa.amsl.com>; Wed, 17 Sep 2014 23:01:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_64=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VlWG9wMIviC5 for <manet@ietfa.amsl.com>; Wed, 17 Sep 2014 23:01:29 -0700 (PDT)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64D6E1A700F for <manet@ietf.org>; Wed, 17 Sep 2014 23:01:29 -0700 (PDT)
Received: by mail-lb0-f175.google.com with SMTP id n15so447992lbi.20 for <manet@ietf.org>; Wed, 17 Sep 2014 23:01:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=817vOTFkfIwMOYZUHNokmkq2T+fbuCDJtFLQO0NI8sg=; b=J/2oFDdA7uFFuV23pAUaPd7WmJ8Cp+ns4r7IffiH5jZm4SCZKKkBlaWMD+HON93y1k 25stK+u+9XSauUJVRhg4Ce32f0skvpWAIMBofbPU9wKELKQhNtnYS6bFlojeU91BsW+4 UebHC++LlhLYDRNKZqdvG+sE5btNYtZuqKNF+9NLlr5Wwn6JwgUp0iAKg9hyOCLBFqO1 eILZ3b49wG9MFhwLGZWAl5cnhdaZoz8IYcLdkSCWcMtBuiaz1lrccW2pdRqWgtqZOk2v Qmxip32PnYxHJpGM8t6ccruRt5YYuyW+Iq+0af10VKPgXADK3gs+9LI299lza0r2xwtv gfUA==
X-Received: by 10.152.4.194 with SMTP id m2mr2250292lam.63.1411020087427; Wed, 17 Sep 2014 23:01:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.176.37 with HTTP; Wed, 17 Sep 2014 23:01:07 -0700 (PDT)
In-Reply-To: <CADnDZ8-qFnwt1bYdCL9kXR-V3VdW_r9r6qTzBDoy_TYCkrcMWA@mail.gmail.com>
References: <CADnDZ8-qFnwt1bYdCL9kXR-V3VdW_r9r6qTzBDoy_TYCkrcMWA@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 18 Sep 2014 08:01:07 +0200
Message-ID: <CAGnRvuppG3ZBjw2CwfVLw5edDe3wUBs8kf083ZnQqMGtepkSKQ@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/42jC3l-tDKJBCioQtHO9yfqTXbY
Cc: "Emmanuel.Baccelli@inria.fr" <Emmanuel.Baccelli@inria.fr>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-dat-metric@tools.ietf.org" <draft-ietf-manet-olsrv2-dat-metric@tools.ietf.org>
Subject: Re: [manet] AB#2 Review for draft-ietf-manet-olsrv2-dat-metric (DAT metric for RFC7181)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 06:01:31 -0000

On Wed, Sep 17, 2014 at 2:06 PM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> Regarding the review of [1] to the draft-01 it was not reflected totally
> regarding to section 10. The editors mention in [2] that it done the upda=
te
> related to that review, but I see that the editing of section 10 is still
> not clear to show the two modes as was clear from Thomas's edit/review.
>
> In [1] it was more clear for the protocol processing modes as:
> {{
> 10. Processing Directives
> 10.1 Processing Directives for =E2=80=9CMode A=E2=80=9D
> 10.2 Additional Processing Directives for when using =E2=80=9CMode B=E2=
=80=9D
>
> I note that section 10 in the above would have a ton of subsections,
> essentially capturing the current 9.3.1 to 11
> }}
>
> The metric has two modes, but not clearly presented in draft-02. Therefor=
e,
> I suggest amending the section title of 10 and its subsection as it is mo=
re
> clear in [1] than in the draft-02.

Its not really two modes for the whole metric,just a small part (the
gathering of the current link loss, which is then put into the queue
for further processing) has multiple alternatives.

That is the reason I did not follow this suggestion of the new format
(but most of the other suggestions) when creating draft -02.

But I will have another look at the review of Thomas Clausen.

Henning Rogge


From nobody Wed Sep 17 23:49:45 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 017471A700C for <manet@ietfa.amsl.com>; Wed, 17 Sep 2014 23:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQ2O5dzNmLTK for <manet@ietfa.amsl.com>; Wed, 17 Sep 2014 23:49:41 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE84F1A6F68 for <manet@ietf.org>; Wed, 17 Sep 2014 23:49:38 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id u10so517799lbd.27 for <manet@ietf.org>; Wed, 17 Sep 2014 23:49:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:cc:content-type;  bh=n3qMGh9UIHXiHxwgF6keHlQoHcSk7ieI/jCR2i/PhMY=; b=L2IcT0YJj2vXx7APXc6iUj7ApciF6n10zNDhQKvj7aoCPrwYuUPdWm3JTclkHGnAQ7 V933J55fEzxvu8JGxJUaRy/4HgeOzlIXOdEFWR7gKzghStXT2vUmUDlX2UnQJOo6zoXq ZJ+BdxH2KoM42FNnT1FglcgmVyBFRA0ZIRwTyTvZrQgRJ6oaClem8hdPHhTZePmwIfwH hPk/rXrJvptal6X6hWNZY+O3uSf8ELtdKcUL45Mvfj62pMR2hk1/qjndS26FuGvsAJBx 71/C+pLBqdN2Pj6+UYXAJWbbqS6bbVqcwRMHFjNNpNSkr2HDOoOX/8QSYzi3ScZwiAu9 Kh+g==
X-Received: by 10.152.5.9 with SMTP id o9mr1181274lao.95.1411022976887; Wed, 17 Sep 2014 23:49:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.176.37 with HTTP; Wed, 17 Sep 2014 23:49:16 -0700 (PDT)
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 18 Sep 2014 08:49:16 +0200
Message-ID: <CAGnRvuqChLDDnEQ6XAxjy8jH2Vku5GW=u5cuYg30xxyhtWZF0A@mail.gmail.com>
To: MANET IETF <manet@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/5Aoo9L08LxzNdIUzcoGEQ5ljVbY
Cc: Thomas Heide Clausen <thomas@thomasclausen.org>
Subject: [manet] Combining the two packet-lass gathering strategies of the DAT metric draft
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 06:49:43 -0000

Hi,

after working through Thomas Clausen's review and reading my own draft
again, I think it might be possible to combine both packet-lass
gathering strategies of the draft.

The "packet sequence number based" part already needs to process both
Hello Messages and timeouts, so its not that difficult to integrate
the processing with the "Hello timeout based" strategy.

I see two advantages of combining both strategies:

1.) get rid of the artificial split in chapter 9.3
2.) compatibility between nodes that can send/receive packet sequence
numbers and nodes that can not

Might be worth a respin for a -03 draft, what do you think?

Henning Rogge


From nobody Thu Sep 18 02:59:23 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9A71A005E for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 02:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8VktfgV3mCng for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 02:59:20 -0700 (PDT)
Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E75D1A70E1 for <manet@ietf.org>; Thu, 18 Sep 2014 02:59:20 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id x13so885572qcv.3 for <manet@ietf.org>; Thu, 18 Sep 2014 02:59:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5EYj1WwFKCcCEQb+oDj2SzzOQ2oD0XuyUu5FrFcvHUQ=; b=UMzBi2HrVHMzeeoTUOPp8QZK0cEvhFfeYzSFMq0qDK882StdXftXpeclVEFAxnVffp Z+hY6PQUOURqc4YycYue6EztqwmdBidX+HbbQuO+tXMfrdgr7s+fdCIADpU/p1ymhoD2 PSIuCRC0QmymWEETWssuBcYu/AyOJFwvf0OeDHSQFf/iEWGxevD8oNMjVOXxbpT6073G tV+yba3qd1W9VDKnSHgCV4ZXTMSTbduE9c8m4Wn/Hp38pERdAs2fLy78fDwTvFd1PIBU lCDtl2kkyieTzzO5IuKk4zuzzIBMkt9v6FLeTw9mq7+8nNRsRrTME+aXLyLtivynHnvl xSEg==
MIME-Version: 1.0
X-Received: by 10.236.90.84 with SMTP id d60mr156190yhf.182.1411034359571; Thu, 18 Sep 2014 02:59:19 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Thu, 18 Sep 2014 02:59:19 -0700 (PDT)
In-Reply-To: <CAGnRvuqChLDDnEQ6XAxjy8jH2Vku5GW=u5cuYg30xxyhtWZF0A@mail.gmail.com>
References: <CAGnRvuqChLDDnEQ6XAxjy8jH2Vku5GW=u5cuYg30xxyhtWZF0A@mail.gmail.com>
Date: Thu, 18 Sep 2014 11:59:19 +0200
Message-ID: <CADnDZ8-MUvHbztaL+8tP=Z8bgqWaCiK+7zXy+L=2cj+w6qnGTA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Content-Type: multipart/alternative; boundary=20cf301af78dc4ae15050354097b
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/2vCZf5hJ_ZQiY_r0mfFTxQ59zjk
Cc: MANET IETF <manet@ietf.org>, Thomas Heide Clausen <thomas@thomasclausen.org>
Subject: Re: [manet] Combining the two packet-lass gathering strategies of the DAT metric draft
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 09:59:22 -0000

--20cf301af78dc4ae15050354097b
Content-Type: text/plain; charset=UTF-8

I agree with this. Thanks,

AB

On Thursday, September 18, 2014, Henning Rogge wrote:

> Hi,
>
> after working through Thomas Clausen's review and reading my own draft
> again, I think it might be possible to combine both packet-lass
> gathering strategies of the draft.
>
> The "packet sequence number based" part already needs to process both
> Hello Messages and timeouts, so its not that difficult to integrate
> the processing with the "Hello timeout based" strategy.
>
> I see two advantages of combining both strategies:
>
> 1.) get rid of the artificial split in chapter 9.3
> 2.) compatibility between nodes that can send/receive packet sequence
> numbers and nodes that can not
>
> Might be worth a respin for a -03 draft, what do you think?
>
> Henning Rogge
>
> _______________________________________________
> manet mailing list
> manet@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/manet
>

--20cf301af78dc4ae15050354097b
Content-Type: text/html; charset=UTF-8

I agree with this. Thanks,<div><br></div><div>AB<br><br>On Thursday, September 18, 2014, Henning Rogge  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
after working through Thomas Clausen&#39;s review and reading my own draft<br>
again, I think it might be possible to combine both packet-lass<br>
gathering strategies of the draft.<br>
<br>
The &quot;packet sequence number based&quot; part already needs to process both<br>
Hello Messages and timeouts, so its not that difficult to integrate<br>
the processing with the &quot;Hello timeout based&quot; strategy.<br>
<br>
I see two advantages of combining both strategies:<br>
<br>
1.) get rid of the artificial split in chapter 9.3<br>
2.) compatibility between nodes that can send/receive packet sequence<br>
numbers and nodes that can not<br>
<br>
Might be worth a respin for a -03 draft, what do you think?<br>
<br>
Henning Rogge<br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;manet@ietf.org&#39;)">manet@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/manet" target="_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div>

--20cf301af78dc4ae15050354097b--


From nobody Thu Sep 18 04:22:31 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738781A017C for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 04:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0pPeKK9_4wK6 for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 04:22:28 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A6FA1A01E1 for <manet@ietf.org>; Thu, 18 Sep 2014 04:22:28 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id i8so317312qcq.27 for <manet@ietf.org>; Thu, 18 Sep 2014 04:22:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZMsJLd++9UV2jNpezZLad0wpU4v3DWvOvj96l/XHaVg=; b=eeK44g7bU+Z+phLQ/SB+QLuDYacnruG9Bx5o6k33gkkQzDYxqfcIivhUrTZBTBjCBW hJv4eougd9pRqo4TLuEP6nXZkC/Pr+QBJ4n35QWnwjkgTe4Ve8Z6fyPaOPeOpk748jlk N+SSFsKpRtlthJbHjsx3K3rzBClUSNHeHDJ60vKUs7RLkYMX/Kel0xqrd165d0Zu6vwy wrqK6jlXa9hUZrG5JberK2Lm/w4cNfowTHSdgEpJFvmWwBeak325IXEfqJeOX3ESagPY Oa5M12ghCRFg+IqWhAkbt11MkJBxe8ab8Ev3E4puYCrw5XwDKvexsh8KjMfPR3lQwbZK NC7Q==
MIME-Version: 1.0
X-Received: by 10.236.90.84 with SMTP id d60mr653100yhf.182.1411039347397; Thu, 18 Sep 2014 04:22:27 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Thu, 18 Sep 2014 04:22:27 -0700 (PDT)
In-Reply-To: <061.235f8637e3c7cb9456d361d8404ef4c1@trac.tools.ietf.org>
References: <061.235f8637e3c7cb9456d361d8404ef4c1@trac.tools.ietf.org>
Date: Thu, 18 Sep 2014 13:22:27 +0200
Message-ID: <CADnDZ8_xSfJdhS+EBirLxm5GHLqyzc14YMfXrqNbCpu0r1JG2A@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary=20cf301af78d11064305035533ed
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/qIMPw5ZqeSY1xkmAL-ifUptyRuw
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>
Subject: Re: [manet] #29 (aodvv2): Choice of IP address
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 11:22:30 -0000

--20cf301af78d11064305035533ed
Content-Type: text/plain; charset=UTF-8

On Thursday, April 3, 2014, manet issue tracker wrote:

> #29: Choice of IP address
>
>  (Thomas Clausen) In a great many places, it is stated "IP address of the
>  (node, Adjacent Node, Adjacent Router) sending the message".  If a router
>  has multiple interfaces, and/or if these interfaces have multiple
>  addresses, which of these (any? one matching the interface over which the
>  message is sent?) should be used or assumed here? The relationship
>  node/interface/address is, at best, unclear.


The protocol has defined the routing relations in addresses for
messages. The relationship is clear in the route table entry see  its
structure in section 5. Multiple interface is suitable as each interface
has one routable address (this condition mentioned in draft).


> It seems to me that this
>  specification is written with the assumption that each router has
>  *exactly* one interface participating in the routing protocol, with
>  *exactly* one IP address - and that that router *never* use anything but
>  that IP Address for anything.


The protocol is for Multiple interfaces and each interface with only one
routable address. Why does it seem to you that, please point to the draft
where that was understood?

I think this ticket had not pointed in the draft-03 (submitted in Feb
2014) of the problem, Which makes this ticket issue difficult to
understand.

AB

--20cf301af78d11064305035533ed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Thursday, April 3, 2014, manet issue tracker  wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">#29: Choice of IP address<br>
<br>
=C2=A0(Thomas Clausen) In a great many places, it is stated &quot;IP addres=
s of the<br>
=C2=A0(node, Adjacent Node, Adjacent Router) sending the message&quot;.=C2=
=A0 If a router<br>
=C2=A0has multiple interfaces, and/or if these interfaces have multiple<br>
=C2=A0addresses, which of these (any? one matching the interface over which=
 the<br>
=C2=A0message is sent?) should be used or assumed here? The relationship<br=
>
=C2=A0node/interface/address is, at best, unclear.=C2=A0=C2=A0</blockquote>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"></blockquote><div><br></div><div>The protoco=
l has defined the routing=C2=A0relations in addresses=C2=A0for messages.=C2=
=A0The relationship=C2=A0is clear=C2=A0in the route table entry=C2=A0see =
=C2=A0its structure in=C2=A0section 5. Multiple interface is suitable as ea=
ch interface has one routable address (this condition mentioned in draft).=
=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It seems to me =
that this<br>
=C2=A0specification is written with the assumption that each router has<br>
=C2=A0*exactly* one interface participating in the routing protocol, with<b=
r>
=C2=A0*exactly* one IP address - and that that router *never* use anything =
but<br>
=C2=A0that IP Address for anything.</blockquote><div><br></div><div>The pro=
tocol is for=C2=A0Multiple interfaces and each interface with only one rout=
able address. Why does it seem to you that, please point to the draft where=
 that was understood?</div><div>=C2=A0</div><div>I think this ticket had no=
t=C2=A0pointed in the draft-03 (submitted in Feb 2014)=C2=A0of the problem,=
=C2=A0Which makes this ticket issue=C2=A0difficult to understand.=C2=A0=C2=
=A0</div><div><br></div><div>AB</div>

--20cf301af78d11064305035533ed--


From nobody Thu Sep 18 06:36:53 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B141A87D0 for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 06:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6oPCZlF5Zb_X for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 06:36:49 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1D7E1A87CB for <manet@ietf.org>; Thu, 18 Sep 2014 06:36:49 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id wo20so639354obc.26 for <manet@ietf.org>; Thu, 18 Sep 2014 06:36:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=mp84J7REq4XCwJSWEFLvPFn2+MBdL39tXK5POcOJ9/U=; b=ErD1Jy7LQZbipchsYchl3oibJiQHj/7ikFk9tNwTsZp4QywJZ++Hgxhw6helWYozap l/E1EAFLVZ3NudTgAtbYGgnaHs7+dFGvh3WpBs8nF7pu/NO+igB2k9wIiY2PaOPkzggd ASQBxTTqwcBJfeEi9UKUm2RfZIpQKyZ1wcvLw4UGvB+J9TLOTrlwJc5BsuQj9outGKnh s9nLzDB1BmA4YUUb4p3FQh1YM50hnseXgocZx8oYjNknYVytqx0fsTEIvVuPgP+4qRvS J+KQ7mzysKml0TLnBGwsWk3ZT9DdSvVpoPYJK64iQHLmyl40QCTpIhN9nxCb4EjRzzlM +W5Q==
MIME-Version: 1.0
X-Received: by 10.182.32.5 with SMTP id e5mr4253185obi.73.1411047408162; Thu, 18 Sep 2014 06:36:48 -0700 (PDT)
Received: by 10.76.11.196 with HTTP; Thu, 18 Sep 2014 06:36:48 -0700 (PDT)
Date: Thu, 18 Sep 2014 15:36:48 +0200
Message-ID: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary=089e0122a2208709c40503571330
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/pZO4SBUKAOKuWycgGXJry5uXw6g
Cc: "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 13:36:51 -0000

--089e0122a2208709c40503571330
Content-Type: text/plain; charset=UTF-8

The draft depends on RFC7181, however, the draft does not define/restrict
RFC7181 packets clearly. In RFC7181 section 13.2, it specifies what are the
protocol packets. The protocol packets are having freedom to include all
RFC5444 messages even for other protocols. In 7181 it mentions in section
13.2:

{{{

Messages with different originating routers MAY be combined for
transmission within the same packet.  Messages from other protocols defined
using [RFC5444], including but not limited to NHDP [RFC6130], MAY be
combined for transmission within the same packet.

}}}

AB> For this protocol MT OLSRv2, it is reasonable to follow the edition way
of RFC7181 and to having a subsection of packet and to describing the
conditions for MT protocol in one clear section as did 7181 for non-MT
protocol. So I suggest to add one section/subsection of packets for MT
OLSRv2 and that describes restrictions/conditions of multitopology messages
to be combined among topologies.

AB

--- past review input related below ---

1. http://www.ietf.org/mail-archive/web/manet/current/msg16890.html
2. http://www.ietf.org/mail-archive/web/manet/current/msg16892.html
3. http://www.ietf.org/mail-archive/web/manet/current/msg16895.html
4. http://www.ietf.org/mail-archive/web/manet/current/msg17009.html

--089e0122a2208709c40503571330
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br>The draft depends on RFC7181,=C2=A0however, the draft=C2=A0does not def=
ine/restrict RFC7181 packets clearly.=C2=A0In RFC7181 section 13.2, it spec=
ifies what are the protocol packets. The=C2=A0protocol packets are having f=
reedom to include all RFC5444 messages even for other protocols. In 7181 it=
 mentions in section 13.2:<div><br></div><div>{{{</div><div><br></div><div>=
Messages with different originating routers MAY be combined for transmissio=
n within the same packet. =C2=A0Messages from other protocols defined using=
 [RFC5444], including but not limited to NHDP [RFC6130], MAY be combined fo=
r transmission within the same packet.<br></div><div><br></div><div>}}}</di=
v><div><br><div><div>AB&gt;=C2=A0For this protocol MT OLSRv2, it is reasona=
ble to follow the edition=C2=A0way of RFC7181 and to=C2=A0having a=C2=A0sub=
section of packet and to=C2=A0describing the conditions for MT protocol=C2=
=A0in one clear section=C2=A0as did 7181 for non-MT protocol.=C2=A0So I sug=
gest to add one section/subsection=C2=A0of packets for MT OLSRv2=C2=A0and t=
hat=C2=A0describes=C2=A0restrictions/conditions of=C2=A0multitopology messa=
ges to be combined among topologies.=C2=A0<div><br></div><div>AB</div></div=
><div><br></div><div>--- past review=C2=A0input related below ---</div><div=
><br></div><div>1.=C2=A0<a href=3D"http://www.ietf.org/mail-archive/web/man=
et/current/msg16890.html">http://www.ietf.org/mail-archive/web/manet/curren=
t/msg16890.html</a></div><div>2.=C2=A0<a href=3D"http://www.ietf.org/mail-a=
rchive/web/manet/current/msg16892.html">http://www.ietf.org/mail-archive/we=
b/manet/current/msg16892.html</a></div><div>3.=C2=A0<a href=3D"http://www.i=
etf.org/mail-archive/web/manet/current/msg16895.html">http://www.ietf.org/m=
ail-archive/web/manet/current/msg16895.html</a></div><div>4.=C2=A0<a href=
=3D"http://www.ietf.org/mail-archive/web/manet/current/msg17009.html">http:=
//www.ietf.org/mail-archive/web/manet/current/msg17009.html</a></div><div><=
br></div>
</div></div>

--089e0122a2208709c40503571330--


From nobody Thu Sep 18 09:25:21 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB34B1A886A for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 09:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWk0TReZoD77 for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 09:25:18 -0700 (PDT)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DDFE1A8868 for <manet@ietf.org>; Thu, 18 Sep 2014 09:25:18 -0700 (PDT)
Received: by mail-la0-f46.google.com with SMTP id q1so932596lam.33 for <manet@ietf.org>; Thu, 18 Sep 2014 09:25:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=HJm6S4HAX7T80z9Y49EtfY8IkcBhl6p0f2/mphkjmFk=; b=eDlocIk7SjFr1TVQ2U6Vw7uMnCauMAGqNdj7dUTinbyCQfUmeqFBQrQcEnznvQWNqZ lzlMocNuuaYr/qvaozRIRjy38qu9RTkGOWXJuisLWnsyTFqOr2iwpbJDYkroaEsYQQ1s u9kSyuRcdlJLFqq52qEP1Dq2psfVoH9YphnLLJ2xBGPsjFzLvE7OEVMxBEhU10wm+nRC Kk38UEA7+cCZlkpTZzD7czk+V5NgBZMqWcpONJnl/Sca5tNe97q6uaE9DZdEkK5/Viwp Qcvu+0S6sgEAc7JXbDZJeoCavypRQIaTVYpE4INXlGCucKiSkMMr6v9uXwIt1jeOha24 gHeA==
X-Received: by 10.112.159.169 with SMTP id xd9mr650990lbb.71.1411057516555; Thu, 18 Sep 2014 09:25:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.176.37 with HTTP; Thu, 18 Sep 2014 09:24:56 -0700 (PDT)
In-Reply-To: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com>
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 18 Sep 2014 18:24:56 +0200
Message-ID: <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ewtuPzhpgyY7ZbSKW9iBOuZBFuA
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 16:25:19 -0000

On Thu, Sep 18, 2014 at 3:36 PM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
>
> The draft depends on RFC7181, however, the draft does not define/restrict
> RFC7181 packets clearly. In RFC7181 section 13.2, it specifies what are the
> protocol packets. The protocol packets are having freedom to include all
> RFC5444 messages even for other protocols. In 7181 it mentions in section
> 13.2:
>
> {{{
>
> Messages with different originating routers MAY be combined for transmission
> within the same packet.  Messages from other protocols defined using
> [RFC5444], including but not limited to NHDP [RFC6130], MAY be combined for
> transmission within the same packet.
>
> }}}
>
> AB> For this protocol MT OLSRv2, it is reasonable to follow the edition way
> of RFC7181 and to having a subsection of packet and to describing the
> conditions for MT protocol in one clear section as did 7181 for non-MT
> protocol. So I suggest to add one section/subsection of packets for MT
> OLSRv2 and that describes restrictions/conditions of multitopology messages
> to be combined among topologies.

I don't think the MT-OLSRv2 draft restricts the mechanism described in
section 13.2 of RFC 7181 in any way. It only defines extensions of the
existing TC messages. It does not even change any part of the flooding
process, including the flooding MPR set.

Could you maybe specify where you see the need of additional
restrictions/conditions and what kind of messages you want to combine
among different topologies?

Henning Rogge


From nobody Thu Sep 18 09:58:45 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 255321A04A1 for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 09:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHFK8u3rCEpQ for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 09:58:42 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A596E1A0437 for <manet@ietf.org>; Thu, 18 Sep 2014 09:58:41 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id b13so1201622wgh.15 for <manet@ietf.org>; Thu, 18 Sep 2014 09:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=BkJ1uBZtOkFsIjk9/E0Rh9Vomj2AfLi27Q87ny2jkSQ=; b=dbGZhznga8eFxBr16u4y1uwcb01Mk2J62fk8vyxxi93gO4BGsCAOa/CTTXe5DGXAK/ SVg6I8KAJ2PtNuZx3djajism0OkAC8CrXUxubld4z46N78W8mlQWcpNlO2adsca6U9ce EIUqOJVHZpnNAgm7nctdLapN6fLi1yKuPHKCER25/dDDJ+A/asifJ/+7m87ge3R0r2nM UrrFomQShYN2kzHkz/mvp4xSNpemnpoISFvV0FoUlwhVIuwE8acSMWoA1mYAcTZmtPJX n0S5yEX8g5vytAw4vUrRB2oDUO079hoJbNZYyfbGJnEnw7knDJD7UMAxwxDgboK7+s4r kK1g==
X-Received: by 10.180.90.207 with SMTP id by15mr49868207wib.76.1411059520266;  Thu, 18 Sep 2014 09:58:40 -0700 (PDT)
Received: from [10.6.196.79] (dab-hlw1-h-25-3.dab.02.net. [82.132.233.79]) by mx.google.com with ESMTPSA id mv14sm3628210wic.20.2014.09.18.09.58.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Sep 2014 09:58:38 -0700 (PDT)
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com> <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DE1EB55-66BC-464D-8445-08CF8240FCB6@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Thu, 18 Sep 2014 17:58:33 +0100
To: Henning Rogge <hrogge@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/AMOheJBheK1GzhNfLrTl9wY4OoQ
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 16:58:44 -0000

As Henning says, the original comment is wrong. It even uses the phrase RFC 7=
181 packets. There are no such things. (There are RFC 5444 packets, which ma=
y have some or all messages used by OLSRv2, or may not.)

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 18 Sep 2014, at 17:24, Henning Rogge <hrogge@gmail.com> wrote:
>=20
> On Thu, Sep 18, 2014 at 3:36 PM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>>=20
>> The draft depends on RFC7181, however, the draft does not define/restrict=

>> RFC7181 packets clearly. In RFC7181 section 13.2, it specifies what are t=
he
>> protocol packets. The protocol packets are having freedom to include all
>> RFC5444 messages even for other protocols. In 7181 it mentions in section=

>> 13.2:
>>=20
>> {{{
>>=20
>> Messages with different originating routers MAY be combined for transmiss=
ion
>> within the same packet.  Messages from other protocols defined using
>> [RFC5444], including but not limited to NHDP [RFC6130], MAY be combined f=
or
>> transmission within the same packet.
>>=20
>> }}}
>>=20
>> AB> For this protocol MT OLSRv2, it is reasonable to follow the edition w=
ay
>> of RFC7181 and to having a subsection of packet and to describing the
>> conditions for MT protocol in one clear section as did 7181 for non-MT
>> protocol. So I suggest to add one section/subsection of packets for MT
>> OLSRv2 and that describes restrictions/conditions of multitopology messag=
es
>> to be combined among topologies.
>=20
> I don't think the MT-OLSRv2 draft restricts the mechanism described in
> section 13.2 of RFC 7181 in any way. It only defines extensions of the
> existing TC messages. It does not even change any part of the flooding
> process, including the flooding MPR set.
>=20
> Could you maybe specify where you see the need of additional
> restrictions/conditions and what kind of messages you want to combine
> among different topologies?
>=20
> Henning Rogge
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Sep 18 10:38:18 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F1741A04C5 for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 10:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Npi9H7hTyiHo for <manet@ietfa.amsl.com>; Thu, 18 Sep 2014 10:38:09 -0700 (PDT)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD1971A8889 for <manet@ietf.org>; Thu, 18 Sep 2014 10:37:36 -0700 (PDT)
Received: by mail-yk0-f173.google.com with SMTP id 19so198404ykq.32 for <manet@ietf.org>; Thu, 18 Sep 2014 10:37:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=lwqq1ElyYBgZD85FtWvSwX+WHpYFhKmxPZSvQ6w4cm0=; b=R5LUYEbyRbO2Crqbvyr4prt4Vo/zHyciwmPTQVjn6zvGnitde6Funh5pbYp0VlKMOA a2rvvgQ3kr2luSWHpK45NWmhxGv0gC3b4SpptkAQ8KHVgXeVbTxNrAM3VysnKAjl1whR 4PHUXHqKwPuzYNQaJ4hoF/JCSRI3CWabxeUx7Snl6TGheyOgcIZxY7wjduJtnVLJZiYe 3NDT8EAkIc9Zh696hs5NbchL0537KEA55DTGwusnhD5w5kvNh6YTjfv5ZOCASw5UvQrk Ez2QAjesXSHU5fh9zoqCdLmfPO2sR+gvNjFd877w5N1PmrrmSHgFENC/K0Mm9ogOpILq uCeQ==
MIME-Version: 1.0
X-Received: by 10.236.45.65 with SMTP id o41mr4847133yhb.118.1411061855925; Thu, 18 Sep 2014 10:37:35 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Thu, 18 Sep 2014 10:37:35 -0700 (PDT)
Date: Thu, 18 Sep 2014 19:37:35 +0200
Message-ID: <CADnDZ89rTFc+VuR7eurh5n-YXg39SqEF4jwOe5uhrmNuwx0FXw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary=089e0115ef7aadbdb505035a70ab
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/z-fsx5WgLK568tw5V5sELpQuZMg
Cc: "draft-ietf-manet-aodvv2@tools.ietf.org" <draft-ietf-manet-aodvv2@tools.ietf.org>
Subject: [manet] AB#1 Review (aodvv2): Draft Content Organisation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2014 17:38:14 -0000

--089e0115ef7aadbdb505035a70ab
Content-Type: text/plain; charset=UTF-8

Following similar way of RFC3561 as having section of messages and then
its operation. The AODVv2 draft-04 section 5 mixes the specification of
having some operation with the data structure specification.

I suggest for AODVv2 to organised to have data-structures and then
there operation in separate sections, so section 5 to represent all data
structure including one subsection for the packet/message. Section 7.2
should be transferred to be into the current subsection 5.4. Furthermore,
this section 5 should focus on structure and leave operation of such
subsection to the operation section.

--- OLD ---
5. Data Structures.
5.1.  Route Table Entry .
5.2.  Bidirectional Connectivity and Blacklists.
5.3.  Router Clients and Clients Network.
5.4.  AODVv2 Message Header Fields and Information Elements.
5.5.  Sequence Numbers.
5.6.  Enabling Alternate Metrics.
5.7.  RREQ Table: Received RREQ Messages.

--- NEW ---

5. Data Structures.
5.1.  Route Table Entry .
5.2.  RREQ Table Entry (Received RREQ Messages).
5.3.  Blacklists and Bidirectional Connectivity.
5.4.  Packet/Messages and information elements.
5.5.  Enabling Alternate Metrics.
5.6   Sequence Numbers.
5.7.  Router Clients and Clients Network.

AB> The above section 5 can be reordered, because I was not sure about
which is better to be before which but I tried to start with all tables and
consider most used data structure.

Finally, In operation section as 6 to include all operation related to the
above data structure of new section 5.

--- OLD ---
6. AODVv2 Operation of routing table entries

--- NEW ---
6. AODVv2 Operation
...
6.1 routing table entries operation.

Any operation description in section 5 to be transferred to section 6. The
following sections to 6 if it is operation then it should be under this
section 6 as a subsection. For example section 7 must be 6.2.

Best Regards


AB

--089e0115ef7aadbdb505035a70ab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Following similar way of RFC3561 as having section of=C2=A0messages=C2=A0an=
d then its=C2=A0operation. The AODVv2 draft-04 section 5=C2=A0mixes the=C2=
=A0specification of having=C2=A0some operation with the=C2=A0data structure=
 specification.=C2=A0<div><br></div><div>I suggest for AODVv2=C2=A0to organ=
ised to have data-structures=C2=A0and then there=C2=A0operation in separate=
 sections, so=C2=A0section 5 to represent all data structure including one =
subsection for the=C2=A0packet/message. Section 7.2 should be transferred t=
o be into the=C2=A0current=C2=A0subsection 5.4. Furthermore, this section 5=
 should focus on structure and leave operation of such subsection to the op=
eration section.=C2=A0<div><br></div><div>--- OLD ---</div><div><div>5. Dat=
a Structures.=C2=A0</div><div>5.1. =C2=A0Route Table Entry .</div><div>5.2.=
 =C2=A0Bidirectional Connectivity and Blacklists.=C2=A0</div><div>5.3. =C2=
=A0Router Clients and Clients Network.=C2=A0</div><div>5.4. =C2=A0AODVv2 Me=
ssage Header Fields and=C2=A0Information Elements.=C2=A0</div><div>5.5. =C2=
=A0Sequence Numbers.=C2=A0</div><div>5.6. =C2=A0Enabling Alternate Metrics.=
=C2=A0</div><div>5.7. =C2=A0RREQ Table: Received RREQ Messages.=C2=A0</div>=
</div><div><br></div><div>--- NEW ---<span></span></div><div><br></div><div=
><div>5. Data Structures.=C2=A0</div><div>5.1.=C2=A0 Route Table Entry .</d=
iv><div>5.2. =C2=A0RREQ Table Entry (Received RREQ Messages).=C2=A0<br></di=
v><div>5.3. =C2=A0Blacklists and=C2=A0Bidirectional Connectivity.=C2=A0</di=
v><div>5.4.=C2=A0=C2=A0Packet/Messages and information elements.=C2=A0<br><=
/div><div>5.5.=C2=A0 Enabling Alternate Metrics.=C2=A0</div><div>5.6=C2=A0 =
=C2=A0Sequence Numbers.=C2=A0<br></div><div><div>5.7.=C2=A0 Router Clients =
and Clients Network.=C2=A0</div><div><br></div><div>AB&gt;=C2=A0The above s=
ection 5 can be reordered, because I was not sure about which is better to =
be before which but I tried to start with all tables and consider=C2=A0most=
 used=C2=A0data structure.=C2=A0</div><div><br></div></div><div>Finally,=C2=
=A0In operation section as 6 to include all operation related to the above =
data structure of new section 5.=C2=A0</div><div><br></div><div>--- OLD ---=
</div><div>6. AODVv2=C2=A0Operation of routing table entries</div><div><br>=
</div><div>--- NEW ---</div><div>6. AODVv2 Operation</div><div>...</div><di=
v>6.1=C2=A0routing table entries operation.=C2=A0<br></div><div><br></div><=
div>Any operation description in section 5 to be transferred to section 6.=
=C2=A0The following sections to 6 if it is operation then it should be unde=
r this section 6 as a=C2=A0subsection. For example section 7 must be=C2=A06=
.2.=C2=A0</div><div><br></div><div>Best=C2=A0Regards</div><div><br></div><d=
iv><br></div><div>AB=C2=A0</div></div><div><br></div>
</div>

--089e0115ef7aadbdb505035a70ab--


From nobody Fri Sep 19 02:44:21 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA7F01A006A for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 02:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.552
X-Spam-Level: 
X-Spam-Status: No, score=-8.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OeLxsWrJDrqU for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 02:44:18 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B11931A0063 for <manet@ietf.org>; Fri, 19 Sep 2014 02:44:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.04,554,1406588400"; d="scan'208";a="404428488"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 19 Sep 2014 10:44:17 +0100
X-IronPort-AV: E=Sophos;i="5.04,554,1406588400"; d="scan'208";a="73556536"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasodc005.greenlnk.net with ESMTP; 19 Sep 2014 10:44:15 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.186]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.03.0174.001; Fri, 19 Sep 2014 10:44:15 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>, Henning Rogge <hrogge@gmail.com>
Thread-Topic: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
Thread-Index: AQHP00WrJwzRfF1YEUKHN8NYQwgwopwHAtsAgAAJZYCAASfi0A==
Date: Fri, 19 Sep 2014 09:44:14 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D37E42@GLKXM0002V.GREENLNK.net>
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com> <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com> <0DE1EB55-66BC-464D-8445-08CF8240FCB6@gmail.com>
In-Reply-To: <0DE1EB55-66BC-464D-8445-08CF8240FCB6@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/io28lTqTUDt7cnjg1bSuZ_AHuJE
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 09:44:20 -0000

OK, I will agree I/we might have worded that slightly differently today. Ra=
ther than saying messages may be combined in packets, I would say messages =
(of different originators etc.)  can be sent to the multiplexer together fo=
r recommended inclusion in the same packet. But essentially this is a null =
comment, it says "The 5444 multiplexer may do what it is allowed to do."

-- =

Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: Christopher Dearlove [mailto:christopher.dearlove@gmail.com] =

Sent: 18 September 2014 17:59
To: Henning Rogge
Cc: Abdussalam Baryun; manet@ietf.org; draft-ietf-manet-olsrv2-multitopolog=
y@tools.ietf.org
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

As Henning says, the original comment is wrong. It even uses the phrase RFC=
 7181 packets. There are no such things. (There are RFC 5444 packets, which=
 may have some or all messages used by OLSRv2, or may not.)

--
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 18 Sep 2014, at 17:24, Henning Rogge <hrogge@gmail.com> wrote:
> =

> On Thu, Sep 18, 2014 at 3:36 PM, Abdussalam Baryun =

> <abdussalambaryun@gmail.com> wrote:
>> =

>> The draft depends on RFC7181, however, the draft does not =

>> define/restrict
>> RFC7181 packets clearly. In RFC7181 section 13.2, it specifies what =

>> are the protocol packets. The protocol packets are having freedom to =

>> include all
>> RFC5444 messages even for other protocols. In 7181 it mentions in =

>> section
>> 13.2:
>> =

>> {{{
>> =

>> Messages with different originating routers MAY be combined for =

>> transmission within the same packet.  Messages from other protocols =

>> defined using [RFC5444], including but not limited to NHDP [RFC6130], =

>> MAY be combined for transmission within the same packet.
>> =

>> }}}
>> =

>> AB> For this protocol MT OLSRv2, it is reasonable to follow the =

>> AB> edition way
>> of RFC7181 and to having a subsection of packet and to describing the =

>> conditions for MT protocol in one clear section as did 7181 for =

>> non-MT protocol. So I suggest to add one section/subsection of =

>> packets for MT
>> OLSRv2 and that describes restrictions/conditions of multitopology =

>> messages to be combined among topologies.
> =

> I don't think the MT-OLSRv2 draft restricts the mechanism described in =

> section 13.2 of RFC 7181 in any way. It only defines extensions of the =

> existing TC messages. It does not even change any part of the flooding =

> process, including the flooding MPR set.
> =

> Could you maybe specify where you see the need of additional =

> restrictions/conditions and what kind of messages you want to combine =

> among different topologies?
> =

> Henning Rogge
> =

> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

********************************************************************
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.
********************************************************************


From nobody Fri Sep 19 05:57:18 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5886E1A010E for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 05:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9u3_Nc07Pum for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 05:57:15 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 395491A0127 for <manet@ietf.org>; Fri, 19 Sep 2014 05:57:15 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id f73so523359yha.26 for <manet@ietf.org>; Fri, 19 Sep 2014 05:57:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dXVsQ8XBtHufI6hIS1FFngTIB13QvwhDIZAykZX6afU=; b=FgJFKgk+88pJpfuDYp5TinSlgrn7rM7PsxlgH8IEKNpTSx8qfC8FYviaSJSALwJkUs xk7RbGvczY+7UH/7Qr71CbkX1EviCBIKm8qIvIk57TdFh/ECwWPx5PguWzlOfrdgabZp 35/RzGLIiKNE0Vlg26BXW40E+0H8c5fMdMcDk5yYXGpCzFVoJ8nvjwa/ECb1xZLg2FcH 9xCLCKWPo1r5JfSzBClwB4gobU/rocqgEpPbIgNrHxhbwRmMzP6fyaZLvzP2U2qEe0hw ALbJw0zvMKwmBLhIlQ+c33WV0tNlj1T8B1H4bnI4f/IJ5xGuH/oSRYsHWbX4EYFfn9+C DTIg==
MIME-Version: 1.0
X-Received: by 10.236.90.84 with SMTP id d60mr206503yhf.182.1411131434400; Fri, 19 Sep 2014 05:57:14 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 19 Sep 2014 05:57:14 -0700 (PDT)
In-Reply-To: <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com>
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com> <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com>
Date: Fri, 19 Sep 2014 14:57:14 +0200
Message-ID: <CADnDZ8_WKV6V-1rcgDjWw=U_+5LksfTk8pSvOnOZbGJ4qN17pw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Content-Type: multipart/alternative; boundary=20cf301af78de0ff7a05036aa3ca
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/RSDEw2DNwVkCBQtR7pPMR7d8BIQ
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 12:57:17 -0000

--20cf301af78de0ff7a05036aa3ca
Content-Type: text/plain; charset=UTF-8

Hi Henning,

On Thursday, September 18, 2014, Henning Rogge wrote:

>
> >
>
>
> I don't think the MT-OLSRv2 draft restricts the mechanism described in
> section 13.2 of RFC 7181 in any way. It only defines extensions of the
> existing TC messages. It does not even change any part of the flooding
> process, including the flooding MPR set.


I think it should do, to ensure (with its conditions) that any packet
have combine messages of only same topology. RFC7181 section 13.2 does not
ensure that because it is not MT protocol. So it will be good to refer to
that in one section in this draft of MT.


> Could you maybe specify where you see the need of additional
> restrictions/conditions and what kind of messages you want to combine
> among different topologies?


IMO Conditions for MT are related to: metrics, route maintenance, and
packets. The draft tries to use assumptions but that can not be enough for
me without having analysis presented in IETF. IMHO, the dynamic topologies
can not have its control-messages mixed in one same packet. The draft
restricts that each topology has one-metric-type, but does not restrict
its control-packets, that is why we need a section about packets to
fix that. I will review the related drafts again to write down the full
conditions for this draft.

Regards,

AB

--20cf301af78de0ff7a05036aa3ca
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Henning,<br><br>On Thursday, September 18, 2014, Henning Rogge  wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><br>
&gt;<br><br>
<br>
I don&#39;t think the MT-OLSRv2 draft restricts the mechanism described in<=
br>
section 13.2 of RFC 7181 in any way. It only defines extensions of the<br>
existing TC messages. It does not even change any part of the flooding<br>
process, including the flooding MPR set.</blockquote><div><br></div><div>I =
think it should do, to=C2=A0ensure (with its=C2=A0conditions)=C2=A0that=C2=
=A0any packet have=C2=A0combine messages of only=C2=A0same topology. RFC718=
1 section 13.2 does not ensure that because it is not MT protocol. So it wi=
ll be good to refer to that in one section in this draft of MT.=C2=A0</div>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<br>
Could you maybe specify where you see the need of additional<br>
restrictions/conditions and what kind of messages you want to combine<br>
among different topologies?</blockquote><div><br></div><div>IMO=C2=A0Condit=
ions for MT=C2=A0are related to:=C2=A0metrics, route maintenance,=C2=A0and =
packets. The draft tries to use assumptions but that can not be enough for =
me without having analysis presented in IETF. IMHO, the dynamic=C2=A0topolo=
gies can not have its control-messages mixed in one same packet. The draft =
restricts that each topology has one-metric-type,=C2=A0but does not restric=
t its=C2=A0control-packets, that is why we need a section about packets to =
fix=C2=A0that.=C2=A0I will review the related drafts again to write down th=
e full conditions for this draft.=C2=A0</div><div><br></div><div>Regards,</=
div><div><br></div><div>AB</div>

--20cf301af78de0ff7a05036aa3ca--


From nobody Fri Sep 19 06:46:32 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFE811A017E for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 06:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EyhlVuNes6p3 for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 06:46:28 -0700 (PDT)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C869F1A0173 for <manet@ietf.org>; Fri, 19 Sep 2014 06:46:28 -0700 (PDT)
Received: by mail-yh0-f43.google.com with SMTP id v1so557864yhn.16 for <manet@ietf.org>; Fri, 19 Sep 2014 06:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=LOvpfAooonK7G3QCbmRSl4JwiFw6iXrwThZzax3YIFs=; b=oKfdiscFfw4JcqAAe2PUBY7Y6BHbxrH6IuAbwLa60jTOlDhNjNg4b4AqB1fpmrf1am UHWvqELF8yTo7e/WE54XDoDXWZNXWr96AI+b8jahC1RnUl9UKvFphFkND4wx40maYoKm 6Cl45Le4uxlz/JG6t/0MHuY3dTErqd5dzW3aDnN800o2i/9uhiwbKRmwCP4m+TAhNfOk zs+ZaKGlxPpMaPIcLfyv+6XdogU8HODy3MdUxpgBDJymbujOv+gs1Ff7YaviBvNJ16+R BmMBn9JFQ2VHsSlAIH9QFft0tLOQX8xyhe3OR3MIUzmW+KFFIcYjHzxhrWhR/Kfg8KW6 5e+g==
MIME-Version: 1.0
X-Received: by 10.236.65.38 with SMTP id e26mr592440yhd.164.1411134387944; Fri, 19 Sep 2014 06:46:27 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 19 Sep 2014 06:46:27 -0700 (PDT)
Date: Fri, 19 Sep 2014 15:46:27 +0200
Message-ID: <CADnDZ89TQ3orYdLV-1KvhAAW=C5pz1fLn7e8EUdi1UTt2Gg80w@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec50dc1baec810e05036b531f
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/heE9EbXVBav0DNWeS5AVtOkDwhE
Cc: "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: [manet] AB#3 (olsrv2-multitopology): Adding section for Metric Type
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 13:46:30 -0000

--bcaec50dc1baec810e05036b531f
Content-Type: text/plain; charset=UTF-8

The draft depends on RFC7181 and is interoperable with RFC7181 routing.
Draft is different than RFC7181 as 7181 has only one metric type to route
data packets, but this draft can route data packets with more than one
metric type, as each packet routed in one topology. I recommend adding one
section for the metric type, and focus the content related of
metrics in draft into one section to show this specification restriction
for metric types clearly.

The RFC7181 metric types are link metric types that MUST be additive (this
can be one restriction but not mentioned in draft). In page 4, the draft
specifies a Boolean for metric type, but Boolean is not additive. How can
you add these true and false?

If this MT protocol allows other metric types than the additive, then state
that clearly in one section for metric. Otherwise delete it because it does
not follow additive types (if WG think I am wrong then I think you need to
explain it clearly in a separate section for metric and not in page
4, because the draft confuses this important element that is related/usedto
MT).

Regards,
AB


On Thursday, September 18, 2014, Abdussalam Baryun wrote:

>
> The draft depends on RFC7181, however, the draft does not define/restrict
> RFC7181 packets clearly. In RFC7181 section 13.2, it specifies what are the
> protocol packets. The protocol packets are having freedom to include all
> RFC5444 messages even for other protocols. In 7181 it mentions in section
> 13.2:
>
> {{{
>
> Messages with different originating routers MAY be combined for
> transmission within the same packet.  Messages from other protocols defined
> using [RFC5444], including but not limited to NHDP [RFC6130], MAY be
> combined for transmission within the same packet.
>
> }}}
>
> AB> For this protocol MT OLSRv2, it is reasonable to follow the
> edition way of RFC7181 and to having a subsection of packet and
> to describing the conditions for MT protocol in one clear section as did
> 7181 for non-MT protocol. So I suggest to add one section/subsection of
> packets for MT OLSRv2 and that describes restrictions/conditions
> of multitopology messages to be combined among topologies.
>
> AB
>
> --- past review input related below ---
>
> 1. http://www.ietf.org/mail-archive/web/manet/current/msg16890.html
> 2. http://www.ietf.org/mail-archive/web/manet/current/msg16892.html
> 3. http://www.ietf.org/mail-archive/web/manet/current/msg16895.html
> 4. http://www.ietf.org/mail-archive/web/manet/current/msg17009.html
>
>

--bcaec50dc1baec810e05036b531f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The draft depends on RFC7181 and is interoperable with RFC7181 routing. Dra=
ft=C2=A0is different than RFC7181 as 7181 has only one metric type to route=
 data=C2=A0packets, but this draft can=C2=A0route=C2=A0data packets with mo=
re than one metric type, as each packet routed=C2=A0in one topology.=C2=A0I=
 recommend adding one section for the metric type, and focus the content re=
lated of metrics=C2=A0in=C2=A0draft into one section=C2=A0to show this spec=
ification restriction for metric types clearly.=C2=A0<div><div><br></div><d=
iv>The RFC7181 metric types are=C2=A0link=C2=A0metric types that=C2=A0MUST =
be additive (this can be one=C2=A0restriction but not mentioned in draft).=
=C2=A0In page 4, the draft specifies a Boolean for metric type, but Boolean=
 is not additive. How can you add these true and false?=C2=A0</div><div><br=
></div><div>If this MT protocol allows other metric types than the=C2=A0add=
itive,=C2=A0then state that clearly in one section for metric. Otherwise=C2=
=A0delete it because it does not follow additive types (if WG=C2=A0think I =
am wrong then I think=C2=A0you need to explain it clearly=C2=A0in a separat=
e section for metric and not in page 4,=C2=A0because the draft confuses thi=
s important element that is related/used<span></span>to MT).=C2=A0</div><di=
v><br></div><div>Regards,</div><div>AB</div><div><br></div><div><font><span=
 style=3D"background-color:rgba(255,255,255,0)">=C2=A0</span></font><br>On =
Thursday, September 18, 2014, Abdussalam Baryun  wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><br>The draft depends on RFC7181,=C2=A0however, the draft=C2=
=A0does not define/restrict RFC7181 packets clearly.=C2=A0In RFC7181 sectio=
n 13.2, it specifies what are the protocol packets. The=C2=A0protocol packe=
ts are having freedom to include all RFC5444 messages even for other protoc=
ols. In 7181 it mentions in section 13.2:<div><br></div><div>{{{</div><div>=
<br></div><div>Messages with different originating routers MAY be combined =
for transmission within the same packet. =C2=A0Messages from other protocol=
s defined using [RFC5444], including but not limited to NHDP [RFC6130], MAY=
 be combined for transmission within the same packet.<br></div><div><br></d=
iv><div>}}}</div><div><br><div><div>AB&gt;=C2=A0For this protocol MT OLSRv2=
, it is reasonable to follow the edition=C2=A0way of RFC7181 and to=C2=A0ha=
ving a=C2=A0subsection of packet and to=C2=A0describing the conditions for =
MT protocol=C2=A0in one clear section=C2=A0as did 7181 for non-MT protocol.=
=C2=A0So I suggest to add one section/subsection=C2=A0of packets for MT OLS=
Rv2=C2=A0and that=C2=A0describes=C2=A0restrictions/conditions of=C2=A0multi=
topology messages to be combined among topologies.=C2=A0<div><br></div><div=
>AB</div></div><div><br></div><div>--- past review=C2=A0input related below=
 ---</div><div><br></div><div>1.=C2=A0<a href=3D"http://www.ietf.org/mail-a=
rchive/web/manet/current/msg16890.html" target=3D"_blank">http://www.ietf.o=
rg/mail-archive/web/manet/current/msg16890.html</a></div><div>2.=C2=A0<a hr=
ef=3D"http://www.ietf.org/mail-archive/web/manet/current/msg16892.html" tar=
get=3D"_blank">http://www.ietf.org/mail-archive/web/manet/current/msg16892.=
html</a></div><div>3.=C2=A0<a href=3D"http://www.ietf.org/mail-archive/web/=
manet/current/msg16895.html" target=3D"_blank">http://www.ietf.org/mail-arc=
hive/web/manet/current/msg16895.html</a></div><div>4.=C2=A0<a href=3D"http:=
//www.ietf.org/mail-archive/web/manet/current/msg17009.html" target=3D"_bla=
nk">http://www.ietf.org/mail-archive/web/manet/current/msg17009.html</a></d=
iv><div><br></div>
</div></div>
</blockquote></div></div>

--bcaec50dc1baec810e05036b531f--


From nobody Fri Sep 19 07:21:35 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 516011A019C for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 07:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4GXEnKSNBdi for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 07:21:29 -0700 (PDT)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF3921A0199 for <manet@ietf.org>; Fri, 19 Sep 2014 07:21:28 -0700 (PDT)
Received: by mail-la0-f46.google.com with SMTP id q1so2633781lam.5 for <manet@ietf.org>; Fri, 19 Sep 2014 07:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qM0vU8IbxGR09eo6i1CFrpsqf00D9K4SFnRBBiFVaSA=; b=AN1WuCoAXrrzanfu4FbHXE+asrBSix5DoorALEVJQ7MGnCMeqPCijeVZyVMaGynAbB K4eYdvHh43rAGDpRkagzZJs4qmcV49HZxsYv5Us6VQG+MrElXWUxsUh+pT/jQeiss+t1 nnKScYwxjiaX5tQAkKITAnWIJTGoo9ulei1Z9mgQdgHF+0shdR2p22SIHuzl7JKEE9/z P1DFQEj442B/uYLpPwZdsVeybeE/ZMx5ateL7xO6DEiQsRJyZrYeW6Hxx7fXqsHmKDkI +xKDfNKVle5doEEjiWDJ1WBVhMigGtdoaLuOzhoJCtnOY2aFZyxYojKIBJfm0vZ41wPr pLwQ==
X-Received: by 10.112.54.135 with SMTP id j7mr6596138lbp.51.1411136486940; Fri, 19 Sep 2014 07:21:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.176.37 with HTTP; Fri, 19 Sep 2014 07:21:06 -0700 (PDT)
In-Reply-To: <CADnDZ89TQ3orYdLV-1KvhAAW=C5pz1fLn7e8EUdi1UTt2Gg80w@mail.gmail.com>
References: <CADnDZ89TQ3orYdLV-1KvhAAW=C5pz1fLn7e8EUdi1UTt2Gg80w@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 19 Sep 2014 16:21:06 +0200
Message-ID: <CAGnRvurOuKwfoE7=hwo_mqPrte9BRAvNrU4iQw7aSWOz5cNLqA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/wSWkpadoS6u55fJQPNgk6nTJgTc
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#3 (olsrv2-multitopology): Adding section for Metric Type
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 14:21:31 -0000

On Fri, Sep 19, 2014 at 3:46 PM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> The draft depends on RFC7181 and is interoperable with RFC7181 routing.
> Draft is different than RFC7181 as 7181 has only one metric type to route
> data packets, but this draft can route data packets with more than one
> metric type, as each packet routed in one topology. I recommend adding one
> section for the metric type, and focus the content related of metrics in
> draft into one section to show this specification restriction for metric
> types clearly.
>
> The RFC7181 metric types are link metric types that MUST be additive (this
> can be one restriction but not mentioned in draft). In page 4, the draft
> specifies a Boolean for metric type, but Boolean is not additive. How can
> you add these true and false?

I have just read section 4 of the current olsrv2 multitopology draft
and I cannot find anything that defines a boolean metric.

I would suggest you become more specific to the text you are referring to.

Henning Rogge


From nobody Fri Sep 19 08:36:19 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6949F1A005E for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 08:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.103
X-Spam-Level: 
X-Spam-Status: No, score=-4.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bN-F9KfGCCFe for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 08:36:15 -0700 (PDT)
Received: from ukmta1.baesystems.com (unknown [20.133.0.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BFAC1A0053 for <manet@ietf.org>; Fri, 19 Sep 2014 08:36:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.04,555,1406588400"; d="scan'208";a="478758206"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 19 Sep 2014 16:36:13 +0100
X-IronPort-AV: E=Sophos;i="5.04,555,1406588400"; d="scan'208";a="65795285"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 19 Sep 2014 16:36:09 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.186]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0174.001; Fri, 19 Sep 2014 16:36:08 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Henning Rogge <hrogge@gmail.com>, Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: [manet] AB#3 (olsrv2-multitopology): Adding section for Metric Type
Thread-Index: AQHP1BAypJzZbinMIUqNq05IX8aocpwIcQIAgAAlNxA=
Date: Fri, 19 Sep 2014 15:36:07 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D37F04@GLKXM0002V.GREENLNK.net>
References: <CADnDZ89TQ3orYdLV-1KvhAAW=C5pz1fLn7e8EUdi1UTt2Gg80w@mail.gmail.com> <CAGnRvurOuKwfoE7=hwo_mqPrte9BRAvNrU4iQw7aSWOz5cNLqA@mail.gmail.com>
In-Reply-To: <CAGnRvurOuKwfoE7=hwo_mqPrte9BRAvNrU4iQw7aSWOz5cNLqA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/EN3tR9JZv-fLyNu1yQNwYArgPKw
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#3 (olsrv2-multitopology): Adding section for Metric Type
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 15:36:17 -0000

There is a reference to  a boolean type, not metric type, on page 4. Correc=
tly.

I would have to waste less time if I didn't have to respond to comments due=
 to not reading what the document says.

-- =

Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Henning Rogge
Sent: 19 September 2014 15:21
To: Abdussalam Baryun
Cc: manet@ietf.org; draft-ietf-manet-olsrv2-multitopology@tools.ietf.org
Subject: Re: [manet] AB#3 (olsrv2-multitopology): Adding section for Metric=
 Type

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

On Fri, Sep 19, 2014 at 3:46 PM, Abdussalam Baryun <abdussalambaryun@gmail.=
com> wrote:
> The draft depends on RFC7181 and is interoperable with RFC7181 routing.
> Draft is different than RFC7181 as 7181 has only one metric type to =

> route data packets, but this draft can route data packets with more =

> than one metric type, as each packet routed in one topology. I =

> recommend adding one section for the metric type, and focus the =

> content related of metrics in draft into one section to show this =

> specification restriction for metric types clearly.
>
> The RFC7181 metric types are link metric types that MUST be additive =

> (this can be one restriction but not mentioned in draft). In page 4, =

> the draft specifies a Boolean for metric type, but Boolean is not =

> additive. How can you add these true and false?

I have just read section 4 of the current olsrv2 multitopology draft and I =
cannot find anything that defines a boolean metric.

I would suggest you become more specific to the text you are referring to.

Henning Rogge

_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet

********************************************************************
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.
********************************************************************


From nobody Fri Sep 19 10:21:24 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08CB01A03BF for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 10:21:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g-S_S59brY-W for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 10:21:19 -0700 (PDT)
Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F67D1A03AD for <manet@ietf.org>; Fri, 19 Sep 2014 10:21:19 -0700 (PDT)
Received: by mail-yk0-f177.google.com with SMTP id 9so112583ykp.8 for <manet@ietf.org>; Fri, 19 Sep 2014 10:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0xZqhHRon05sOlWzIZyfM7Gxvx3h+pvnOLbaZ2C8rck=; b=Q94riPnt2T1XrAiuwFYRWEbUrk2G5h5GW3o+H7VNGpG0ZODlSsPm2Ep5brJMkOoGk7 7vJ2BZbYtAgvd2ObXyZtcv0Io+8utVel5ukFrNxRB7fFI2OWbZtV59ajBaPpYCc4JTNl uapXQ5ziGijHu2Ax6svNGCwfZ7WM1sFzX3z/r1rrjVMRPGBfeTHJ93YQ/PDGmmZ/uIhi essKwJ+Dn/pn3ZLNazO2d//Cy6qcAOitAaZ2m/RY1i11QAZr9blN+ZwaiQRn+fR2OXYn bSMRw6IuT95dc8+grcCaOWZ+G48aBfJfKiauTqmoMqs76nQf6gWKJ+Z6aS/IyJn3xK5m F0jA==
MIME-Version: 1.0
X-Received: by 10.236.121.228 with SMTP id r64mr1478999yhh.31.1411147278244; Fri, 19 Sep 2014 10:21:18 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 19 Sep 2014 10:21:18 -0700 (PDT)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D37F04@GLKXM0002V.GREENLNK.net>
References: <CADnDZ89TQ3orYdLV-1KvhAAW=C5pz1fLn7e8EUdi1UTt2Gg80w@mail.gmail.com> <CAGnRvurOuKwfoE7=hwo_mqPrte9BRAvNrU4iQw7aSWOz5cNLqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D37F04@GLKXM0002V.GREENLNK.net>
Date: Fri, 19 Sep 2014 19:21:18 +0200
Message-ID: <CADnDZ89q523oOr1Ht8xPF-6Bfv=XU9m3PS_SkAssQwY+VX=YWA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=20cf3010e68d3ee0a005036e54ad
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/RIRHENzCNLhuuQVYzj3goZjrlFc
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#3 (olsrv2-multitopology): Adding section for Metric Type
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 17:21:21 -0000

--20cf3010e68d3ee0a005036e54ad
Content-Type: text/plain; charset=UTF-8

Ok, sorry it was not metric but a mapping to Boolean. The map function is
related to the metric type, so doing the section for metric type is
important. The main point of this thread is adding a section to avoid
confusion.

On Friday, September 19, 2014, Dearlove, Christopher (UK) wrote:

> There is a reference to  a boolean type, not metric type, on page 4.
> Correctly.
>
> I would have to waste less time if I didn't have to respond to comments
> due to not reading what the document says.


Each metric type needs to define the map, so that is a restriction for this
MT toward metrics.


AB

--20cf3010e68d3ee0a005036e54ad
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Ok, sorry=C2=A0it was not metric but a mapping to Boolean.=C2=A0The map fun=
ction is related to the metric type, so=C2=A0doing=C2=A0the section for met=
ric type is important. The main point of this thread is adding a section to=
 avoid confusion.=C2=A0<br><br>On Friday, September 19, 2014, Dearlove, Chr=
istopher (UK)  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There is a referenc=
e to=C2=A0 a boolean type, not metric type, on page 4. Correctly.<br>
<br>
I would have to waste less time if I didn&#39;t have to respond to comments=
 due to not reading what the document says.</blockquote><div><br></div><div=
>Each metric type needs to define the map, so that is a restriction for thi=
s MT toward metrics.=C2=A0</div><div><br></div><div><br></div><div>AB</div>=
<div><br></div><div><br></div><br>

--20cf3010e68d3ee0a005036e54ad--


From nobody Fri Sep 19 10:46:08 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4447C1A04B9 for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 10:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lYBln8Ldt1oF for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 10:46:05 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C4F91A0418 for <manet@ietf.org>; Fri, 19 Sep 2014 10:46:05 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id l18so71203wgh.4 for <manet@ietf.org>; Fri, 19 Sep 2014 10:46:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=xjK/TL1BMvdGWyfi3WKSUJcDSd0jrYwuOqkQMOTGYHA=; b=SN9xAKQaXbKPs8SZeWnrTw8hKEAfsP71/KWaXycCyd4T62gf17Fytk2QardHkf0ejX ciICQdK3sDJLDFSq4VVU7sP1UZsDas/8UhJ7wugYXfvL9DeTtXD4HZGVPVB6qrxLh7Ol NlsAhm1RvHn+lp3Jwkq4b8kI9Izil/TlTOUMM+kROEzPFO126/knWN2RZBFHKnahBoyW /ltKM6Hjks3pKPt2u9uHZKaViD76lOu43n2SbVSpyPkMUVGOAdnQrJ9zFP6jd44ru/Ll FtQGBxkiHxmpWwJNW9pNCZZ+K2LDLXWkjJqmORrOIbd4UHl53FUMjnMOgBqSyzrTfAk3 w8UA==
X-Received: by 10.194.220.7 with SMTP id ps7mr2775816wjc.28.1411148764002; Fri, 19 Sep 2014 10:46:04 -0700 (PDT)
Received: from [192.168.254.4] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id s1sm2827494wiw.6.2014.09.19.10.46.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Sep 2014 10:46:03 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A7644368-A6D6-4BB9-9156-D394B27680FD"
From: Christopher Dearlove <christopher.dearlove@gmail.com>
In-Reply-To: <CADnDZ89q523oOr1Ht8xPF-6Bfv=XU9m3PS_SkAssQwY+VX=YWA@mail.gmail.com>
Date: Fri, 19 Sep 2014 18:46:02 +0100
Message-Id: <743F1727-64A0-4830-9DDD-62F7C0A2C335@gmail.com>
References: <CADnDZ89TQ3orYdLV-1KvhAAW=C5pz1fLn7e8EUdi1UTt2Gg80w@mail.gmail.com> <CAGnRvurOuKwfoE7=hwo_mqPrte9BRAvNrU4iQw7aSWOz5cNLqA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40D37F04@GLKXM0002V.GREENLNK.net> <CADnDZ89q523oOr1Ht8xPF-6Bfv=XU9m3PS_SkAssQwY+VX=YWA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/VQJgF0MQkzEgX2Fq2kUd4LbN2WM
Cc: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#3 (olsrv2-multitopology): Adding section for Metric Type
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 17:46:07 -0000

--Apple-Mail=_A7644368-A6D6-4BB9-9156-D394B27680FD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

No. Still wrong. MT-OLSRv2, like OLSRv2, doesn't need metric specific =
information. It needs to be told which metrics to use (and can ignore =
the rest) and needs to be given actual metric values. But those are =
inputs to it. There is no metric type map definition or anything like =
it.

Please, read and understand. However long that takes, please stop =
posting things that are wrong in the meanwhile. If you have a question, =
ask a question instead. Of course there could be errors, nobody's =
perfect, but so far  just yours.


On 19 Sep 2014, at 18:21, Abdussalam Baryun wrote:

> Ok, sorry it was not metric but a mapping to Boolean. The map function =
is related to the metric type, so doing the section for metric type is =
important. The main point of this thread is adding a section to avoid =
confusion.=20
>=20
> On Friday, September 19, 2014, Dearlove, Christopher (UK) wrote:
> There is a reference to  a boolean type, not metric type, on page 4. =
Correctly.
>=20
> I would have to waste less time if I didn't have to respond to =
comments due to not reading what the document says.
>=20
> Each metric type needs to define the map, so that is a restriction for =
this MT toward metrics.=20
>=20
>=20
> AB
>=20
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


--Apple-Mail=_A7644368-A6D6-4BB9-9156-D394B27680FD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>No. Still wrong. MT-OLSRv2, like OLSRv2, doesn't need metric =
specific information. It needs to be told which metrics to use (and can =
ignore the rest) and needs to be given actual metric values. But those =
are inputs to it. There is no metric type map definition or anything =
like it.</div><div><br></div><div>Please, read and understand. However =
long that takes, please stop posting things that are wrong in the =
meanwhile. If you have a question, ask a question instead. Of course =
there could be errors, nobody's perfect,&nbsp;but so far &nbsp;just =
yours.</div><div><br></div><br><div><div>On 19 Sep 2014, at 18:21, =
Abdussalam Baryun wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">Ok, =
sorry&nbsp;it was not metric but a mapping to Boolean.&nbsp;The map =
function is related to the metric type, so&nbsp;doing&nbsp;the section =
for metric type is important. The main point of this thread is adding a =
section to avoid confusion.&nbsp;<br><br>On Friday, September 19, 2014, =
Dearlove, Christopher (UK)  wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">There is a reference to&nbsp; a boolean type, =
not metric type, on page 4. Correctly.<br>
<br>
I would have to waste less time if I didn't have to respond to comments =
due to not reading what the document =
says.</blockquote><div><br></div><div>Each metric type needs to define =
the map, so that is a restriction for this MT toward =
metrics.&nbsp;</div><div><br></div><div><br></div><div>AB</div><div><br></=
div><div><br></div><br>
_______________________________________________<br>manet mailing =
list<br><a =
href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/manet<br></blockquote></div><br></body></html>=

--Apple-Mail=_A7644368-A6D6-4BB9-9156-D394B27680FD--


From nobody Fri Sep 19 10:51:24 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCFCE1A0691 for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 10:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LeO020YTQZrf for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 10:51:21 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C272A1A0643 for <manet@ietf.org>; Fri, 19 Sep 2014 10:51:20 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id x48so151139wes.35 for <manet@ietf.org>; Fri, 19 Sep 2014 10:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:mime-version:content-type:in-reply-to:date:cc :message-id:references:to; bh=tRFRxXwLuRcllJ/AV5ju4VmU+wGFRws3ZL1BKmjDs3M=; b=KR7WqjAqIGcy4/pmrLu84OrY0ZwYZufismVFtMamXISpOQfkpFNeaC4+rfzEmtuZJg tDDMS3WDtFTHuTgX5gYljl2LQQ7gmuxkfr9VVLbSa9OIDGR6AvAk/fwH39HIgwq5hs+A /EkbIX6QPRH0U8cnp5zSm7F9y74ED77UemJSRNkla2y1qnKTbZGY4cF6d1IxwCdIiZVB zntskuvsfc6Jev9doMxi7D41o5AKA54HTdqual7fyQBupn58ySbu4hLFRuK/ReGQGxFW m10ZJUU3fHWYUQ6ASR2JQgFX0sXGDH+zLYm8SILwzx6zYN4shh1mZiCZVZ3LkceUb/1A kSyw==
X-Received: by 10.180.183.133 with SMTP id em5mr56900188wic.72.1411149079460;  Fri, 19 Sep 2014 10:51:19 -0700 (PDT)
Received: from [192.168.254.4] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id u5sm2822046wia.17.2014.09.19.10.51.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Sep 2014 10:51:18 -0700 (PDT)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
X-Google-Original-From: Christopher Dearlove <chris@mnemosyne.demon.co.uk>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1E1DEE9D-EB79-4FC8-8CBE-6BCB19E01612"
In-Reply-To: <CADnDZ8_WKV6V-1rcgDjWw=U_+5LksfTk8pSvOnOZbGJ4qN17pw@mail.gmail.com>
Date: Fri, 19 Sep 2014 18:51:17 +0100
Message-Id: <1309678A-A21B-4992-92AE-68FE05F26C64@mnemosyne.demon.co.uk>
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com> <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com> <CADnDZ8_WKV6V-1rcgDjWw=U_+5LksfTk8pSvOnOZbGJ4qN17pw@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/5Pm8LxYAUjdfjKrx2eFBbS4risY
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 17:51:22 -0000

--Apple-Mail=_1E1DEE9D-EB79-4FC8-8CBE-6BCB19E01612
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Wrong, wrong and wrong again. This is getting tiresome.


On 19 Sep 2014, at 13:57, Abdussalam Baryun wrote:

> Hi Henning,
>=20
> On Thursday, September 18, 2014, Henning Rogge wrote:
>=20
> >
>=20
>=20
> I don't think the MT-OLSRv2 draft restricts the mechanism described in
> section 13.2 of RFC 7181 in any way. It only defines extensions of the
> existing TC messages. It does not even change any part of the flooding
> process, including the flooding MPR set.
>=20
> I think it should do, to ensure (with its conditions) that any packet =
have combine messages of only same topology. RFC7181 section 13.2 does =
not ensure that because it is not MT protocol. So it will be good to =
refer to that in one section in this draft of MT.=20
>=20
>=20
> Could you maybe specify where you see the need of additional
> restrictions/conditions and what kind of messages you want to combine
> among different topologies?
>=20
> IMO Conditions for MT are related to: metrics, route maintenance, and =
packets. The draft tries to use assumptions but that can not be enough =
for me without having analysis presented in IETF. IMHO, the dynamic =
topologies can not have its control-messages mixed in one same packet. =
The draft restricts that each topology has one-metric-type, but does not =
restrict its control-packets, that is why we need a section about =
packets to fix that. I will review the related drafts again to write =
down the full conditions for this draft.=20
>=20
> Regards,
>=20
> AB
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


--Apple-Mail=_1E1DEE9D-EB79-4FC8-8CBE-6BCB19E01612
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Wrong, wrong and wrong again. This is getting tiresome.</div><div><br></div><br><div><div>On 19 Sep 2014, at 13:57, Abdussalam Baryun wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html; charset=utf-8">Hi Henning,<br><br>On Thursday, September 18, 2014, Henning Rogge  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
&gt;<br><br>
<br>
I don't think the MT-OLSRv2 draft restricts the mechanism described in<br>
section 13.2 of RFC 7181 in any way. It only defines extensions of the<br>
existing TC messages. It does not even change any part of the flooding<br>
process, including the flooding MPR set.</blockquote><div><br></div><div>I think it should do, to&nbsp;ensure (with its&nbsp;conditions)&nbsp;that&nbsp;any packet have&nbsp;combine messages of only&nbsp;same topology. RFC7181 section 13.2 does not ensure that because it is not MT protocol. So it will be good to refer to that in one section in this draft of MT.&nbsp;</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Could you maybe specify where you see the need of additional<br>
restrictions/conditions and what kind of messages you want to combine<br>
among different topologies?</blockquote><div><br></div><div>IMO&nbsp;Conditions for MT&nbsp;are related to:&nbsp;metrics, route maintenance,&nbsp;and packets. The draft tries to use assumptions but that can not be enough for me without having analysis presented in IETF. IMHO, the dynamic&nbsp;topologies can not have its control-messages mixed in one same packet. The draft restricts that each topology has one-metric-type,&nbsp;but does not restrict its&nbsp;control-packets, that is why we need a section about packets to fix&nbsp;that.&nbsp;I will review the related drafts again to write down the full conditions for this draft.&nbsp;</div><div><br></div><div>Regards,</div><div><br></div><div>AB</div>
_______________________________________________<br>manet mailing list<br><a href="mailto:manet@ietf.org">manet@ietf.org</a><br><a href="https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet</a><br></blockquote></div><br></body></html>
--Apple-Mail=_1E1DEE9D-EB79-4FC8-8CBE-6BCB19E01612--


From nobody Fri Sep 19 12:40:46 2014
Return-Path: <yi.jiazi@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7DD51A86ED for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 12:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D0F0rYwZUPTp for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 12:40:44 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88CA51A0697 for <manet@ietf.org>; Fri, 19 Sep 2014 12:40:44 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id z2so130411wiv.5 for <manet@ietf.org>; Fri, 19 Sep 2014 12:40:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=NTSAj9vY+01YOKDC1H8U/FdhhJbiYSIeDPlK9606sVQ=; b=dWA6XmGuy3YnHPon1M2bPy013dyF8oHSkEmTW3iTKTAd0KGWfst4pj2HCHrV/t0Ldp kezxkTiZq+00QYSfEWkhxZPuVW+1RhfmrvYOXVjzBHrzdZ6rcgg8maDIYVJZY7xbntx+ 7i55aX1S2miyB5NciqSRqsV33WlJ07DQScbDvV4oFEA51s2druXwcrZ7qMsjA0EFR0Mi ZMIrZY0/Go28YM7CDZH2HsfV2wFOmQ7TcRdBjZ7nBKsPIR9PkXEpSG4UOYu4TVhPZO74 ALn1ZbuRSEdHCQGhbprCOPk4pm2y7slGYNuhiczp8x+tt0i/0+JDPcTeWvAGwFDlwVPe 1XhQ==
MIME-Version: 1.0
X-Received: by 10.194.78.136 with SMTP id b8mr3137771wjx.106.1411155643170; Fri, 19 Sep 2014 12:40:43 -0700 (PDT)
Sender: yi.jiazi@gmail.com
Received: by 10.194.176.226 with HTTP; Fri, 19 Sep 2014 12:40:43 -0700 (PDT)
In-Reply-To: <CADnDZ8_WKV6V-1rcgDjWw=U_+5LksfTk8pSvOnOZbGJ4qN17pw@mail.gmail.com>
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com> <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com> <CADnDZ8_WKV6V-1rcgDjWw=U_+5LksfTk8pSvOnOZbGJ4qN17pw@mail.gmail.com>
Date: Fri, 19 Sep 2014 21:40:43 +0200
X-Google-Sender-Auth: zS19LRxFu8jN5TZTgAtCMD9Ucy8
Message-ID: <CAN1bDFycdDUW9oPEOc6yGQKk3uPXLbaHc7Fye_hSOY3ZMjxYfA@mail.gmail.com>
From: Jiazi YI <ietf@jiaziyi.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd91a8cd585a9050370469f
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ZHRsGfAUer7qixuEsyjzSkRXGio
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 19:40:46 -0000

--047d7bd91a8cd585a9050370469f
Content-Type: text/plain; charset=UTF-8

On Fri, Sep 19, 2014 at 2:57 PM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> Hi Henning,
>
> On Thursday, September 18, 2014, Henning Rogge wrote:
>
>>
>> >
>>
>>
>> I don't think the MT-OLSRv2 draft restricts the mechanism described in
>> section 13.2 of RFC 7181 in any way. It only defines extensions of the
>> existing TC messages. It does not even change any part of the flooding
>> process, including the flooding MPR set.
>
>
> I think it should do, to ensure (with its conditions) that any packet
> have combine messages of only same topology. RFC7181 section 13.2 does not
> ensure that because it is not MT protocol. So it will be good to refer to
> that in one section in this draft of MT.
>

No. There is nothing special regarding this point that needs to be added.

best

Jiazi

--047d7bd91a8cd585a9050370469f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Sep 19, 2014 at 2:57 PM, Abdussalam Baryun <span dir=3D"ltr">&l=
t;<a href=3D"mailto:abdussalambaryun@gmail.com" target=3D"_blank">abdussala=
mbaryun@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">H=
i Henning,<span class=3D""><br><br>On Thursday, September 18, 2014, Henning=
 Rogge  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
&gt;<br><br>
<br>
I don&#39;t think the MT-OLSRv2 draft restricts the mechanism described in<=
br>
section 13.2 of RFC 7181 in any way. It only defines extensions of the<br>
existing TC messages. It does not even change any part of the flooding<br>
process, including the flooding MPR set.</blockquote><div><br></div></span>=
<div>I think it should do, to=C2=A0ensure (with its=C2=A0conditions)=C2=A0t=
hat=C2=A0any packet have=C2=A0combine messages of only=C2=A0same topology. =
RFC7181 section 13.2 does not ensure that because it is not MT protocol. So=
 it will be good to refer to that in one section in this draft of MT.=C2=A0=
</div></blockquote><div><br></div><div>No. There is nothing special regardi=
ng this point that needs to be added. =C2=A0</div><div><br></div><div>best<=
/div><div><br></div><div>Jiazi</div></div></div></div>

--047d7bd91a8cd585a9050370469f--


From nobody Fri Sep 19 15:15:33 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A9F1A88DA for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 15:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2afCzexBaNz for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 15:15:30 -0700 (PDT)
Received: from mail-yh0-x233.google.com (mail-yh0-x233.google.com [IPv6:2607:f8b0:4002:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B63B1A88D2 for <manet@ietf.org>; Fri, 19 Sep 2014 15:15:30 -0700 (PDT)
Received: by mail-yh0-f51.google.com with SMTP id c41so420812yho.24 for <manet@ietf.org>; Fri, 19 Sep 2014 15:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4rsj4J9vm3jgTxel7ASX6ycR1LV2usKEnHyYXz1hwVM=; b=LhlSOfsNK2BfrUwCpixxGf01tt2Jhuj3hWOQDbecB4QEmXdt2coQg3ttOlKei5xgTE CKTB4BddSH+PDUmEtqt0rMznPGjednq1j0d/v9sj42WESl/h31gPFSlE1lxw/uRIRYJu k/lXycBqKMUHAOFwM42V5JxQS5sdwTHf/rk+sxSAFR46dYHsvJZXRao6jUek7DyXDLmS T6Tp72l0sx5PzDqQZBbKbsTYg4lSF77BDekLuMp+Pm9S05Cba0rVzXTByAowDIZorff6 ShRRDfiMMSd4vsoWG8Jz1WKLAuPtda4Y0mN0rWzDqbzSZcMmE+q29IabIQzX2uCx5nvn 7ezg==
MIME-Version: 1.0
X-Received: by 10.236.159.131 with SMTP id s3mr3860920yhk.69.1411164929911; Fri, 19 Sep 2014 15:15:29 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 19 Sep 2014 15:15:29 -0700 (PDT)
In-Reply-To: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com>
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com>
Date: Sat, 20 Sep 2014 00:15:29 +0200
Message-ID: <CADnDZ8_6CHqvPUSJq=YyKrT-3stMa8JAptU2sX=n2ExD67E+3w@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: multipart/alternative; boundary=20cf30426d705df11805037270da
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/2KwxYVyEvZ3eoemaPF-0tahKuO8
Cc: manet <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: [manet]  AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 22:15:32 -0000

--20cf30426d705df11805037270da
Content-Type: text/plain; charset=UTF-8

Hi Chris,

We can look into use cases of MT, which helps know what we need (that was
my first question when the draft was proposed). However, we want to use
this work in best way we can/want.

On Thursday, September 18, 2014, Abdussalam Baryun wrote:

>
> The draft depends on RFC7181, however, the draft does not define/restrict
> RFC7181 packets clearly. In RFC7181 section 13.2, it specifies what are the
> protocol packets. The protocol packets are having freedom to include all
> RFC5444 messages even for other protocols. In 7181 it mentions in section
> 13.2:
>
> {{{
>
> Messages with different originating routers MAY be combined for
> transmission within the same packet.  Messages from other protocols defined
> using [RFC5444], including but not limited to NHDP [RFC6130], MAY be
> combined for transmission within the same packet.
>
> }}}
>

Could we have  5444 packet tlv for MT OLSRv2 that may help to simplify the
MT administrative work? IMHO this will help identify packets per topology
or per use case. The current draft just looks into metric types for
topologies.
>
>
AB

--20cf30426d705df11805037270da
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Chris,<div><br></div><div>We can look into use cases of MT, which helps =
know what we need (that was my first question when the draft was proposed).=
=C2=A0However, we want to use this work in best way we can/want.=C2=A0<br><=
br>On Thursday, September 18, 2014, Abdussalam Baryun  wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><br>The draft depends on RFC7181,=C2=A0however, the dr=
aft=C2=A0does not define/restrict RFC7181 packets clearly.=C2=A0In RFC7181 =
section 13.2, it specifies what are the protocol packets. The=C2=A0protocol=
 packets are having freedom to include all RFC5444 messages even for other =
protocols. In 7181 it mentions in section 13.2:<div><br></div><div>{{{</div=
><div><br></div><div>Messages with different originating routers MAY be com=
bined for transmission within the same packet. =C2=A0Messages from other pr=
otocols defined using [RFC5444], including but not limited to NHDP [RFC6130=
], MAY be combined for transmission within the same packet.<br></div><div><=
br></div><div>}}}</div></blockquote><div><br></div>Could we have =C2=A05444=
<span></span>=C2=A0packet tlv for MT OLSRv2 that may help to simplify the M=
T=C2=A0administrative work? IMHO this will help identify packets per topolo=
gy or per use case. The current draft just looks into metric types for topo=
logies.=C2=A0<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div><div><div></div>
</div></div>
</blockquote><div><br></div><div>AB</div>
</div>

--20cf30426d705df11805037270da--


From nobody Fri Sep 19 15:38:55 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CACEB1A88E6 for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 15:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fa4Ef0aoN6fX for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 15:38:52 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 462EE1A88E1 for <manet@ietf.org>; Fri, 19 Sep 2014 15:38:52 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id fb4so296511wid.3 for <manet@ietf.org>; Fri, 19 Sep 2014 15:38:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=IiaD8gWSXIjeu8hnlGnEHCdJFnbtKYTGoS3WEMP8Ncw=; b=maAY0ItDPhojX7g6yheIINg0laSQ0qT+tcMZajs7IfRENu/0SKiFreOodBXoHY6YHt Ux4n8m9HsDnQSBqfPqFGFkErW7NHBxp2L4NpR3Vo/tsPVCHNJFMrZOTSl+Slfw5ECMHj pOZr4lKepd8i+sKX+n8cDrgJkaaIrNkLk6UsqZ+6I8rLaZheO6RLnVfnLZIC/VpZH82l OY85QHtKcYe19KRlx/Hx8VfNOoa75eAysVlk3wAEZYNWr96FRW3CipR1jYMwMcgmwnPz 8Wq0p3OJZYiFkcGZKhKqI1vny/q6xisz5kEO9ScqNJ7rB1WLTJiXbN//0M/PgxQcbvPo vhbg==
X-Received: by 10.180.86.133 with SMTP id p5mr1154761wiz.40.1411166330924; Fri, 19 Sep 2014 15:38:50 -0700 (PDT)
Received: from [192.168.254.3] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id eg8sm3468482wib.15.2014.09.19.15.38.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Sep 2014 15:38:49 -0700 (PDT)
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com> <CADnDZ8_6CHqvPUSJq=YyKrT-3stMa8JAptU2sX=n2ExD67E+3w@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ8_6CHqvPUSJq=YyKrT-3stMa8JAptU2sX=n2ExD67E+3w@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-D799DD4D-AD12-45BB-B22A-956B3B01DE16
Content-Transfer-Encoding: 7bit
Message-Id: <7804E128-6CB7-4A04-A614-157C266456C0@gmail.com>
X-Mailer: iPhone Mail (11D257)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Fri, 19 Sep 2014 23:38:47 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/sNhpEKjzhovtjZM3dHZqcK-r5xU
Cc: manet <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 22:38:54 -0000

--Apple-Mail-D799DD4D-AD12-45BB-B22A-956B3B01DE16
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

First, we don't need a packet TLV. We don't need to recognise "packets per t=
opology". For not the first time of saying, references to packets in MT-OLSR=
v2 at to data packets. I'm not sure why you keep wanting to pull in 5444 pac=
kets, but unless anyone needs to, you shouldn't. Which means packet usage (p=
acket TLVs) are for when someone has a concrete suggestion, not just a vague=
 non-idea.

And beyond that, you are again trying to reopen closed questions already dec=
ided. Without showing understanding of them. The WG (which has done WGLC) ag=
reed that in this experimental RFC that topology =3D metric (which is common=
ly used in other protocols) was a sensible approach, given that no one could=
 see a clean more general solution that interworked with non-MT-OLSRv2. Desp=
ite trying.

--=20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 19 Sep 2014, at 23:15, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
>=20
> Hi Chris,
>=20
> We can look into use cases of MT, which helps know what we need (that was m=
y first question when the draft was proposed). However, we want to use this w=
ork in best way we can/want.=20
>=20
>> On Thursday, September 18, 2014, Abdussalam Baryun wrote:
>>=20
>> The draft depends on RFC7181, however, the draft does not define/restrict=
 RFC7181 packets clearly. In RFC7181 section 13.2, it specifies what are the=
 protocol packets. The protocol packets are having freedom to include all RFC=
5444 messages even for other protocols. In 7181 it mentions in section 13.2:=

>>=20
>> {{{
>>=20
>> Messages with different originating routers MAY be combined for transmiss=
ion within the same packet.  Messages from other protocols defined using [RFC=
5444], including but not limited to NHDP [RFC6130], MAY be combined for tran=
smission within the same packet.
>>=20
>> }}}
>=20
> Could we have  5444 packet tlv for MT OLSRv2 that may help to simplify the=
 MT administrative work? IMHO this will help identify packets per topology o=
r per use case. The current draft just looks into metric types for topologie=
s.=20
>=20
> AB

--Apple-Mail-D799DD4D-AD12-45BB-B22A-956B3B01DE16
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>First, we don't need a packet TLV. We d=
on't need to recognise "packets per topology". For not the first time of say=
ing, references to packets in MT-OLSRv2 at to data packets. I'm not sure why=
 you keep wanting to pull in 5444 packets, but unless anyone needs to, you s=
houldn't. Which means packet usage (packet TLVs) are for when someone has a c=
oncrete suggestion, not just a vague non-idea.</div><div><br></div><div>And b=
eyond that, you are again trying to reopen closed questions already decided.=
 Without showing understanding of them. The WG (which has done WGLC) agreed t=
hat in this experimental RFC that topology =3D metric (which is commonly use=
d in other protocols) was a sensible approach, given that no one could see a=
 clean more general solution that interworked with non-MT-OLSRv2. Despite tr=
ying.<br><br>--&nbsp;<div>Christopher Dearlove</div><div><a href=3D"mailto:c=
hristopher.dearlove@gmail.com">christopher.dearlove@gmail.com</a> (iPhone)</=
div><div><a href=3D"mailto:chris@mnemosyne.demon.co.uk">chris@mnemosyne.demo=
n.co.uk</a> (home)</div></div><div><br>On 19 Sep 2014, at 23:15, Abdussalam B=
aryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">abdussalambaryun@gma=
il.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>Hi Chris,<=
div><br></div><div>We can look into use cases of MT, which helps know what w=
e need (that was my first question when the draft was proposed).&nbsp;Howeve=
r, we want to use this work in best way we can/want.&nbsp;<br><br>On Thursda=
y, September 18, 2014, Abdussalam Baryun  wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><br>The draft depends on RFC7181,&nbsp;however, the draft&nbsp;does no=
t define/restrict RFC7181 packets clearly.&nbsp;In RFC7181 section 13.2, it s=
pecifies what are the protocol packets. The&nbsp;protocol packets are having=
 freedom to include all RFC5444 messages even for other protocols. In 7181 i=
t mentions in section 13.2:<div><br></div><div>{{{</div><div><br></div><div>=
Messages with different originating routers MAY be combined for transmission=
 within the same packet. &nbsp;Messages from other protocols defined using [=
RFC5444], including but not limited to NHDP [RFC6130], MAY be combined for t=
ransmission within the same packet.<br></div><div><br></div><div>}}}</div></=
blockquote><div><br></div>Could we have &nbsp;5444<span></span>&nbsp;packet t=
lv for MT OLSRv2 that may help to simplify the MT&nbsp;administrative work? I=
MHO this will help identify packets per topology or per use case. The curren=
t draft just looks into metric types for topologies.&nbsp;<blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div><div><div></div>
</div></div>
</blockquote><div><br></div><div>AB</div>
</div>
</div></blockquote></body></html>=

--Apple-Mail-D799DD4D-AD12-45BB-B22A-956B3B01DE16--


From nobody Sun Sep 21 04:53:56 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2CF91A00AE for <manet@ietfa.amsl.com>; Sun, 21 Sep 2014 04:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xg_ouimG5nj3 for <manet@ietfa.amsl.com>; Sun, 21 Sep 2014 04:53:52 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A32B1A00AD for <manet@ietf.org>; Sun, 21 Sep 2014 04:53:51 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id f73so1466668yha.12 for <manet@ietf.org>; Sun, 21 Sep 2014 04:53:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ILbKsnNsoqFSvMa+DpQDuxE/ChG2uSxUCsd5mQ/uRPQ=; b=Yq9sVW8iyY7c9Vc6dwKiaVswZomG71Jej8y/31IZ2xxgq/s5v6MZ+SYz2dbC2NYWxP c4X7g73udZZeZCh3q4eTN3GI5Ajrgggj0dYT6Ih9e5xuuAtRk4/jetP2g9Xky5vEqr8P GfmUm/g+VosclQwUfioMCE9TAtXfZJnS2Qi4eQqnYpXyzCCRQweJk4+LSl1dk9ppobn9 1PoGo+ldof5IrW6rKBqaDqEynJiWfRwHoKrDFCPwXq3o0fZLHD9sg5wt15MmLFl/8GuP a3/5DLMj/b+mV+KiX9YDdiJpxI2JactIQQX4oTAi93uVOmtyUEvDGZc5ETgE0DSyZB41 azvQ==
MIME-Version: 1.0
X-Received: by 10.236.53.69 with SMTP id f45mr18268437yhc.53.1411300431227; Sun, 21 Sep 2014 04:53:51 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Sun, 21 Sep 2014 04:53:50 -0700 (PDT)
In-Reply-To: <C83A8919-4D6A-4B64-9695-8A60CFA45908@gmail.com>
References: <066.3e1906b2a4af830a63b2dc76aad57fbe@trac.tools.ietf.org> <C83A8919-4D6A-4B64-9695-8A60CFA45908@gmail.com>
Date: Sun, 21 Sep 2014 13:53:50 +0200
Message-ID: <CADnDZ88rmtEHyLheZKrUNXaoBt42A2Ty1RQ6TeShqGg98qPDzw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: multipart/alternative; boundary=089e0122971cdff109050391fc11
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/DJLt3X6X79X8nlqj_9Kojx5sviw
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] #55 (olsrv2-multitopology): Maintaining Multiple Routing Sets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Sep 2014 11:53:54 -0000

--089e0122971cdff109050391fc11
Content-Type: text/plain; charset=UTF-8

Section 11 and subsection 6.8 need more specification details for routing
maintenance.

On Saturday, August 23, 2014, Christopher Dearlove wrote:

> ....
>
> Yes, the draft does describe creating multiple routing sets. See Section
> 11. If familiar with OLSRv2, that's all you need - because OLSRv2 describes
> how a Routing Set is calculated and when it needs to change.


Already seen section 11 when reviewed but is not enough. Regarding RFC7181
(which section refers to) it is only for single topology, so for MT we need
a fresh maintenance paragraph at least. In subsection 6.8 it does not
describe how is the separation. In section 11 it does not describe how the
calculation separates routing sets. The is a need to add an element in
routing set for metric type. All maps are done with metric type
reference, but in the routing sets there is no element for metric type or
reference.

How do we go from changes occurring to updating the routing sets? In non-MT
is easy because all update is single topology.  MT has replaced in 7181 all
sets' elements are replaced with maps but for Routing Set the draft
says only routing set is separated by metric type (subsection 6.8), which
is only in draft-words not in specification of the routing sets.


> How are things separated? By metric type, as is clearly said more than
> once. Metric types are defined in OLSRv2.


Only one type is defined in OLSRv2 which is in LINK_METRIC_TYPE. This MT
draft replaced/adds other parameters which is not much linked to separate
Routing Sets. I will give suggestions.

AB

--089e0122971cdff109050391fc11
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Section 11 and subsection=C2=A06.8 need more specification=C2=A0details for=
 routing maintenance.=C2=A0<br><br>On Saturday, August 23, 2014, Christophe=
r Dearlove  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">....<br>
<br>
Yes, the draft does describe creating multiple routing sets. See Section 11=
. If familiar with OLSRv2, that&#39;s all you need - because OLSRv2 describ=
es how a Routing Set is calculated and when it needs to change.</blockquote=
><div><br></div><div>Already seen section 11 when reviewed but is not enoug=
h. Regarding RFC7181 (which section refers=C2=A0to)=C2=A0it is only=C2=A0fo=
r single topology, so for MT we need a fresh maintenance paragraph at least=
. In subsection 6.8 it does not describe how is the=C2=A0separation.=C2=A0I=
n section 11 it does not describe how the calculation separates routing set=
s. The is a need to add an element in routing set for metric type. All maps=
 are=C2=A0done with metric type reference,=C2=A0but in the routing sets the=
re is no element for metric type or reference.=C2=A0</div><div><br></div><d=
iv>How do we go from changes occurring=C2=A0to updating=C2=A0the routing se=
ts? In non-MT is easy because all update is single topology.=C2=A0=C2=A0MT =
has replaced=C2=A0in 7181 all sets&#39; elements=C2=A0are replaced=C2=A0wit=
h maps=C2=A0but for Routing Set the=C2=A0draft says=C2=A0only routing set i=
s separated by metric type (subsection 6.8),=C2=A0which is only in draft-wo=
rds=C2=A0not in specification of the routing sets.=C2=A0<span></span></div>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<br>
How are things separated? By metric type, as is clearly said more than once=
. Metric types are defined in OLSRv2.=C2=A0</blockquote><div><br></div><div=
>Only one type is defined in OLSRv2 which is in LINK_METRIC_TYPE. This MT d=
raft replaced/adds=C2=A0other parameters which is not much linked to separa=
te Routing Sets. I will give suggestions.=C2=A0</div><div><br></div><div>AB=
=C2=A0</div>

--089e0122971cdff109050391fc11--


From nobody Sun Sep 21 05:09:29 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC03C1A00AB for <manet@ietfa.amsl.com>; Sun, 21 Sep 2014 05:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qw8X74NRrl_6 for <manet@ietfa.amsl.com>; Sun, 21 Sep 2014 05:09:24 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DA561A008F for <manet@ietf.org>; Sun, 21 Sep 2014 05:09:24 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id z2so1549010wiv.5 for <manet@ietf.org>; Sun, 21 Sep 2014 05:09:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:from:subject:date:to; bh=E/T0rdzyhJnfFoEkLHx6GaFIZIzqAG5p42+joC+VqRc=; b=LrCkLz+QNC5bqD4JKSkK2IYEG+Gp5IVUftNbHwEwr5PROipTAV044fxe6FhPgum0OP 2WLntVnEBtDT2+ifPe7O5ib/+hFfN3H+YJhCmn/u6JyCeEh5JkTjecuBf8a2TnmCmiZb 5J1cvaidxbV3ACxe3i25cfRA8XNQzKjhoeP8pNtbqEWhR4HItgXuA33JAAV4LdoranNL 7BfR1u7sAuzB3WrwMzWYGMbHfhXZzWd+qZskGfATcZIvrb7xC9jfVWQnyCd/boPjOyII yInwWKYsLa6DpZ+NDlHMUhob6bR6N0Uz/0ullEABOaoSADzoLzkIkwK0rCLIZPlfMjDr vJPw==
X-Received: by 10.194.5.234 with SMTP id v10mr13408400wjv.45.1411301363013; Sun, 21 Sep 2014 05:09:23 -0700 (PDT)
Received: from [192.168.254.3] (mnemosyne.demon.co.uk. [62.49.16.209]) by mx.google.com with ESMTPSA id ks10sm8675944wjb.38.2014.09.21.05.09.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 21 Sep 2014 05:09:21 -0700 (PDT)
References: <066.3e1906b2a4af830a63b2dc76aad57fbe@trac.tools.ietf.org> <C83A8919-4D6A-4B64-9695-8A60CFA45908@gmail.com> <CADnDZ88rmtEHyLheZKrUNXaoBt42A2Ty1RQ6TeShqGg98qPDzw@mail.gmail.com>
In-Reply-To: <CADnDZ88rmtEHyLheZKrUNXaoBt42A2Ty1RQ6TeShqGg98qPDzw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-2B9FE9D8-CEB2-4F2F-B24D-44E4D93B4467
Message-Id: <3E9FA613-CC56-4B9A-A135-DAAC9323CC52@gmail.com>
X-Mailer: iPhone Mail (12A365)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Sun, 21 Sep 2014 13:09:20 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/aEuo2W8-Xo5R7lGZlEmxvO-qyi0
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] #55 (olsrv2-multitopology): Maintaining Multiple Routing Sets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Sep 2014 12:09:27 -0000

--Apple-Mail-2B9FE9D8-CEB2-4F2F-B24D-44E4D93B4467
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

This is a proactive routing protocol. There's nothing special about routing m=
aintenance.

If you think something specific is wanted, you should say so, instead of vag=
ue comments. If you don't understand, ask. Not make assertions without any p=
resented foundation.

It seems everyone else understand. But if there's something specific not sai=
d that everyone has assumed, say what it is.

I would also refer you to the first paragraph of Section 4 and the third bul=
let point in Section 12. Note that this protocol's job is to create and main=
tain the Routing Sets. What to do with them is a task outside this protocol (=
though strongly suggested by this protocol, with a big warning about mixing s=
ets in that bullet point).

--=20
-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)
chris@mnemosyne.demon.co.uk (home)

> On 21 Sep 2014, at 12:53, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
>=20
> Section 11 and subsection 6.8 need more specification details for routing m=
aintenance.=20
>=20
>> On Saturday, August 23, 2014, Christopher Dearlove wrote:
>> ....
>>=20
>> Yes, the draft does describe creating multiple routing sets. See Section 1=
1. If familiar with OLSRv2, that's all you need - because OLSRv2 describes h=
ow a Routing Set is calculated and when it needs to change.
>=20
> Already seen section 11 when reviewed but is not enough. Regarding RFC7181=
 (which section refers to) it is only for single topology, so for MT we need=
 a fresh maintenance paragraph at least. In subsection 6.8 it does not descr=
ibe how is the separation. In section 11 it does not describe how the calcul=
ation separates routing sets. The is a need to add an element in routing set=
 for metric type. All maps are done with metric type reference, but in the r=
outing sets there is no element for metric type or reference.=20
>=20
> How do we go from changes occurring to updating the routing sets? In non-M=
T is easy because all update is single topology.  MT has replaced in 7181 al=
l sets' elements are replaced with maps but for Routing Set the draft says o=
nly routing set is separated by metric type (subsection 6.8), which is only i=
n draft-words not in specification of the routing sets.=20
>=20
>>=20
>> How are things separated? By metric type, as is clearly said more than on=
ce. Metric types are defined in OLSRv2.=20
>=20
> Only one type is defined in OLSRv2 which is in LINK_METRIC_TYPE. This MT d=
raft replaced/adds other parameters which is not much linked to separate Rou=
ting Sets. I will give suggestions.=20
>=20
> AB=20

--Apple-Mail-2B9FE9D8-CEB2-4F2F-B24D-44E4D93B4467
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><span></span></div><div><meta http-equ=
iv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><div>This is a pr=
oactive routing protocol. There's nothing special about routing maintenance.=
</div><div><br></div><div>If you think something specific is wanted, you sho=
uld say so, instead of vague comments. If you don't understand, ask. Not mak=
e assertions without any presented foundation.</div><div><br></div><div>It s=
eems everyone else understand. But if there's something specific not said th=
at everyone has assumed, say what it is.</div><div><br></div><div>I would al=
so refer you to the first paragraph of Section 4 and the third bullet point i=
n Section 12. Note that this protocol's job is to create and maintain the Ro=
uting Sets. What to do with them is a task outside this protocol (though str=
ongly suggested by this protocol, with a big warning about mixing sets in th=
at bullet point).<br><br>--&nbsp;<div>-- &nbsp;<div>Christopher Dearlove</di=
v><div><a href=3D"mailto:christopher.dearlove@gmail.com">christopher.dearlov=
e@gmail.com</a> (iPhone)</div><div><a href=3D"mailto:chris@mnemosyne.demon.c=
o.uk">chris@mnemosyne.demon.co.uk</a> (home)</div><div><a href=3D"mailto:chr=
is@mnemosyne.demon.co.uk">chris@mnemosyne.demon.co.uk</a> (home)</div></div>=
<div><br>On 21 Sep 2014, at 12:53, Abdussalam Baryun &lt;<a href=3D"mailto:a=
bdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:<br><br>=
</div><blockquote type=3D"cite"><div><meta http-equiv=3D"Content-Type" conte=
nt=3D"text/html; charset=3Dutf-8">Section 11 and subsection&nbsp;6.8 need mo=
re specification&nbsp;details for routing maintenance.&nbsp;<br><br>On Satur=
day, August 23, 2014, Christopher Dearlove  wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">....<br>
<br>
Yes, the draft does describe creating multiple routing sets. See Section 11.=
 If familiar with OLSRv2, that's all you need - because OLSRv2 describes how=
 a Routing Set is calculated and when it needs to change.</blockquote><div><=
br></div><div>Already seen section 11 when reviewed but is not enough. Regar=
ding RFC7181 (which section refers&nbsp;to)&nbsp;it is only&nbsp;for single t=
opology, so for MT we need a fresh maintenance paragraph at least. In subsec=
tion 6.8 it does not describe how is the&nbsp;separation.&nbsp;In section 11=
 it does not describe how the calculation separates routing sets. The is a n=
eed to add an element in routing set for metric type. All maps are&nbsp;done=
 with metric type reference,&nbsp;but in the routing sets there is no elemen=
t for metric type or reference.&nbsp;</div><div><br></div><div>How do we go f=
rom changes occurring&nbsp;to updating&nbsp;the routing sets? In non-MT is e=
asy because all update is single topology.&nbsp;&nbsp;MT has replaced&nbsp;i=
n 7181 all sets' elements&nbsp;are replaced&nbsp;with maps&nbsp;but for Rout=
ing Set the&nbsp;draft says&nbsp;only routing set is separated by metric typ=
e (subsection 6.8),&nbsp;which is only in draft-words&nbsp;not in specificat=
ion of the routing sets.&nbsp;<span></span></div><div><br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
<br>
How are things separated? By metric type, as is clearly said more than once.=
 Metric types are defined in OLSRv2.&nbsp;</blockquote><div><br></div><div>O=
nly one type is defined in OLSRv2 which is in LINK_METRIC_TYPE. This MT draf=
t replaced/adds&nbsp;other parameters which is not much linked to separate R=
outing Sets. I will give suggestions.&nbsp;</div><div><br></div><div>AB&nbsp=
;</div>
</div></blockquote></div></div></body></html>=

--Apple-Mail-2B9FE9D8-CEB2-4F2F-B24D-44E4D93B4467--


From nobody Sun Sep 21 10:12:28 2014
Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0984E1A014C for <manet@ietfa.amsl.com>; Sun, 21 Sep 2014 10:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.386
X-Spam-Level: 
X-Spam-Status: No, score=-13.386 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSzdWJ_wZqTB for <manet@ietfa.amsl.com>; Sun, 21 Sep 2014 10:12:24 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F84A1A0135 for <manet@ietf.org>; Sun, 21 Sep 2014 10:12:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8725; q=dns/txt; s=iport; t=1411319544; x=1412529144; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=CvcSSiyy3LwE6ndDSe7txC9AfQP8n8ZlEB84e7DzZ28=; b=YlpxhQa61eDQVxp1afh23AuUWo5bgSF0ZU5zOniVmlGn4USF2Q5ZpNAd tQEmUI62nF7s3sSCHLJK66rzWMJF3PqyMRb2K6wTKZl73vCrkZ6VnsJki ymzSFCHUf6HUJWEatzHHrn9vhOo06E1EnapICYW1OrV/iLliqbDO1E934 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FADMGH1StJA2G/2dsb2JhbABggw5TVwTJVwEJh00BfhYBeYQEAQEEAQEBawYFEAIBCD8HIQYLFBECBA4FiCoDEQ27YQ2HLwETBI1XgU0RAVAHgy6BHQWRV4Z1gjqCEI8NhkWDYWyBDzmBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,566,1406592000";  d="scan'208,217";a="357062843"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-4.cisco.com with ESMTP; 21 Sep 2014 17:12:23 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s8LHCNEf019324 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 21 Sep 2014 17:12:23 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.21]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0195.001; Sun, 21 Sep 2014 12:12:23 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: [manet] #55 (olsrv2-multitopology): Maintaining Multiple Routing Sets
Thread-Index: AQHP1ZK/jjRLq2LHDkKjzobcoq0Nf5wMJxSA
Date: Sun, 21 Sep 2014 17:12:22 +0000
Message-ID: <A34255DF-DA0F-47B9-B602-C2BF749B2B2F@cisco.com>
References: <066.3e1906b2a4af830a63b2dc76aad57fbe@trac.tools.ietf.org> <C83A8919-4D6A-4B64-9695-8A60CFA45908@gmail.com> <CADnDZ88rmtEHyLheZKrUNXaoBt42A2Ty1RQ6TeShqGg98qPDzw@mail.gmail.com>
In-Reply-To: <CADnDZ88rmtEHyLheZKrUNXaoBt42A2Ty1RQ6TeShqGg98qPDzw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.179.211]
Content-Type: multipart/alternative; boundary="_000_A34255DFDA0F47B9B602C2BF749B2B2Fciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/ieR9GhMGP7XCW3Fyt0qMp3vd4SI
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] #55 (olsrv2-multitopology): Maintaining Multiple Routing Sets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Sep 2014 17:12:27 -0000

--_000_A34255DFDA0F47B9B602C2BF749B2B2Fciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Abdussalam,

On Sep 21, 2014, at 7:53 AM, Abdussalam Baryun <abdussalambaryun@gmail.com<=
mailto:abdussalambaryun@gmail.com>> wrote:

Section 11 and subsection 6.8 need more specification details for routing m=
aintenance.

On Saturday, August 23, 2014, Christopher Dearlove wrote:
....

Yes, the draft does describe creating multiple routing sets. See Section 11=
. If familiar with OLSRv2, that's all you need - because OLSRv2 describes h=
ow a Routing Set is calculated and when it needs to change.

Already seen section 11 when reviewed but is not enough. Regarding RFC7181 =
(which section refers to) it is only for single topology, so for MT we need=
 a fresh maintenance paragraph at least. In subsection 6.8 it does not desc=
ribe how is the separation. In section 11 it does not describe how the calc=
ulation separates routing sets. The is a need to add an element in routing =
set for metric type. All maps are done with metric type reference, but in t=
he routing sets there is no element for metric type or reference.

I want to reinforce what Chris Dearlove said in another email. The text abo=
ve implies (at least to me) that you have a specific deployment scenario in=
 mind, and that when looking at the text of the draft, you conclude that yo=
ur scenario won't work. If that is the case, describe the scenario - I'm no=
t able to follow your concerns, above some vague notion that "this won't wo=
rk". Without the necessary detail, I can only conclude that consensus exist=
s to progress the draft, and you are "in the rough".

It should go without saying, but I'll say it anyway - everyone on this list=
 is interested in producing the highest-quality draft possible. There have =
been multiple reviews, by people who are intimately familiar with the techn=
ology. To my thinking, the multiple reviews make it highly unlikely (but no=
t impossible) that some technical detail has been missed. At this stage of =
the process with this document, the WG needs a fully-documented failing cas=
e in order to understand, and correct, any deficiency in the draft. Therefo=
re, please refrain from general "that is not enough" or "that won't work" d=
escriptions, and provide sufficient detail for us to recognize the issue yo=
u believe you have encountered. For example, some description that starts o=
ut "Assume the following physical topology, with the following multiple rou=
ting sets. When Router 1 does XYZ, Router 2 (or Router 3 or whatever system=
 in the topology) is incapable of distinguishing the action between the mul=
tiple routing sets because of <whatever the perceived error is>". The more =
detail, the better.

Regards,
Stan


How do we go from changes occurring to updating the routing sets? In non-MT=
 is easy because all update is single topology.  MT has replaced in 7181 al=
l sets' elements are replaced with maps but for Routing Set the draft says =
only routing set is separated by metric type (subsection 6.8), which is onl=
y in draft-words not in specification of the routing sets.


How are things separated? By metric type, as is clearly said more than once=
. Metric types are defined in OLSRv2.

Only one type is defined in OLSRv2 which is in LINK_METRIC_TYPE. This MT dr=
aft replaced/adds other parameters which is not much linked to separate Rou=
ting Sets. I will give suggestions.

AB
_______________________________________________
manet mailing list
manet@ietf.org<mailto:manet@ietf.org>
https://www.ietf.org/mailman/listinfo/manet


--_000_A34255DFDA0F47B9B602C2BF749B2B2Fciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <F379F251701526459E2FC3F3CB1AA0BC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Abdussalam,
<div><br>
<div>
<div>On Sep 21, 2014, at 7:53 AM, Abdussalam Baryun &lt;<a href=3D"mailto:a=
bdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">Section 11 and subsection&nbsp;6.8 need more spec=
ification&nbsp;details for routing maintenance.&nbsp;<br>
<br>
On Saturday, August 23, 2014, Christopher Dearlove wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
....<br>
<br>
Yes, the draft does describe creating multiple routing sets. See Section 11=
. If familiar with OLSRv2, that's all you need - because OLSRv2 describes h=
ow a Routing Set is calculated and when it needs to change.</blockquote>
<div><br>
</div>
<div>Already seen section 11 when reviewed but is not enough. Regarding RFC=
7181 (which section refers&nbsp;to)&nbsp;it is only&nbsp;for single topolog=
y, so for MT we need a fresh maintenance paragraph at least. In subsection =
6.8 it does not describe how is the&nbsp;separation.&nbsp;In
 section 11 it does not describe how the calculation separates routing sets=
. The is a need to add an element in routing set for metric type. All maps =
are&nbsp;done with metric type reference,&nbsp;but in the routing sets ther=
e is no element for metric type or reference.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>I want to reinforce what Chris Dearlove said in another email. The tex=
t above implies (at least to me) that you have a specific deployment scenar=
io in mind, and that when looking at the text of the draft, you conclude th=
at your scenario won't work. If
 that is the case, describe the scenario - I'm not able to follow your conc=
erns, above some vague notion that &quot;this won't work&quot;. Without the=
 necessary detail, I can only conclude that consensus exists to progress th=
e draft, and you are &quot;in the rough&quot;.&nbsp;</div>
<div><br>
</div>
<div>It should go without saying, but I'll say it anyway - everyone on this=
 list is interested in producing the highest-quality draft possible. There =
have been multiple reviews, by people who are intimately familiar with the =
technology. To my thinking, the
 multiple reviews make it highly unlikely (but not impossible) that some te=
chnical detail has been missed. At this stage of the process with this docu=
ment, the WG needs a fully-documented failing case in order to understand, =
and correct, any deficiency in the
 draft. Therefore, please refrain from general &quot;that is not enough&quo=
t; or &quot;that won't work&quot; descriptions, and provide sufficient deta=
il for us to recognize the issue you believe you have encountered. For exam=
ple, some description that starts out &quot;Assume the following
 physical topology, with the following multiple routing sets. When Router 1=
 does XYZ, Router 2 (or Router 3 or whatever system in the topology) is inc=
apable of distinguishing the action between the multiple routing sets becau=
se of &lt;whatever the perceived error
 is&gt;&quot;. The more detail, the better.&nbsp;</div>
<div><br>
</div>
<div>Regards,</div>
<div>Stan</div>
<br>
<blockquote type=3D"cite">
<div><br>
</div>
<div>How do we go from changes occurring&nbsp;to updating&nbsp;the routing =
sets? In non-MT is easy because all update is single topology.&nbsp;&nbsp;M=
T has replaced&nbsp;in 7181 all sets' elements&nbsp;are replaced&nbsp;with =
maps&nbsp;but for Routing Set the&nbsp;draft says&nbsp;only routing set is =
separated
 by metric type (subsection 6.8),&nbsp;which is only in draft-words&nbsp;no=
t in specification of the routing sets.&nbsp;<span></span></div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
How are things separated? By metric type, as is clearly said more than once=
. Metric types are defined in OLSRv2.&nbsp;</blockquote>
<div><br>
</div>
<div>Only one type is defined in OLSRv2 which is in LINK_METRIC_TYPE. This =
MT draft replaced/adds&nbsp;other parameters which is not much linked to se=
parate Routing Sets. I will give suggestions.&nbsp;</div>
<div><br>
</div>
<div>AB&nbsp;</div>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/manet<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_A34255DFDA0F47B9B602C2BF749B2B2Fciscocom_--


From donb@mitre.org  Tue Sep 23 11:11:58 2014
Return-Path: <donb@mitre.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0DFE1A1B7F for <manet@ietfa.amsl.com>; Tue, 23 Sep 2014 11:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level: 
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1UzDNO3PO7gU for <manet@ietfa.amsl.com>; Tue, 23 Sep 2014 11:11:57 -0700 (PDT)
Received: from smtptsrv1.mitre.org (smtptsrv1.mitre.org [192.52.194.77]) by ietfa.amsl.com (Postfix) with ESMTP id 127301A1B23 for <manet@ietf.org>; Tue, 23 Sep 2014 11:11:56 -0700 (PDT)
Received: from smtptsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 868F9C50F2D; Tue, 23 Sep 2014 14:11:56 -0400 (EDT)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtptsrv1.mitre.org (Postfix) with ESMTP id 51535C50786; Tue, 23 Sep 2014 14:11:56 -0400 (EDT)
Received: from IMCMBX02.MITRE.ORG ([169.254.2.137]) by IMCCAS03.MITRE.ORG ([129.83.29.80]) with mapi id 14.03.0174.001; Tue, 23 Sep 2014 14:11:55 -0400
From: "Broderick, Don" <donb@mitre.org>
To: "manet@ietf.org" <manet@ietf.org>, "macker@itd.nrl.navy.mil" <macker@itd.nrl.navy.mil>, "sratliff@cisco.com" <sratliff@cisco.com>
Thread-Topic: Common Layer 3 Informational RFC
Thread-Index: Ac/XWKz9RMERcst0TEiKBeesO40xKw==
Date: Tue, 23 Sep 2014 18:11:55 +0000
Message-ID: <CBF66114B0594B44B27A96829523E3C32E9430F4@IMCMBX02.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.140.19.249]
Content-Type: multipart/alternative; boundary="_000_CBF66114B0594B44B27A96829523E3C32E9430F4IMCMBX02MITREOR_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/RT2wkTnPDHqkuker3q5CgQCkPeQ
X-Mailman-Approved-At: Tue, 23 Sep 2014 12:20:39 -0700
Cc: "Jack Shaio \(jshaio@comcast.net\)" <jshaio@comcast.net>, "Caleb Lo \(flashbuzzer@gmail.com\)" <flashbuzzer@gmail.com>
Subject: [manet] Common Layer 3 Informational RFC
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 18:15:34 -0000

--_000_CBF66114B0594B44B27A96829523E3C32E9430F4IMCMBX02MITREOR_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

http://datatracker.ietf.org/doc/draft-shaio-manet-common-l3-interface/

We have just submitted version 01 of our draft "A Common Layer 3 Interface =
for MANET" and would like to request WG comments or issues regarding moving=
 this draft to be an Informational RFC. This draft summarizes our tests usi=
ng an interface between a MANET and L3 routing (OSPFv2 in our case although=
 other routing protocols could have been used).
Thank You,
Don, Jack, Caleb


--_000_CBF66114B0594B44B27A96829523E3C32E9430F4IMCMBX02MITREOR_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><a href=3D"http://datatracker.ietf.org/doc/draft-sha=
io-manet-common-l3-interface/"><span style=3D"color:#0563C1">http://datatra=
cker.ietf.org/doc/draft-shaio-manet-common-l3-interface/</span></a><o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">We have just submitte=
d version 01 of our draft &quot;A Common Layer 3 Interface for MANET&quot; =
and would like to request WG comments or issues regarding moving this draft=
 to be an Informational RFC. This draft summarizes
 our tests using an interface between a MANET and L3 routing (OSPFv2 in our=
 case although other routing protocols could have been used).
<o:p></o:p></p>
<p class=3D"MsoNormal">Thank You, <br>
Don, Jack, Caleb<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_CBF66114B0594B44B27A96829523E3C32E9430F4IMCMBX02MITREOR_--


From nobody Wed Sep 24 06:15:55 2014
Return-Path: <jshaio@yahoo.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D803A1A00D6 for <manet@ietfa.amsl.com>; Wed, 24 Sep 2014 06:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.786
X-Spam-Level: 
X-Spam-Status: No, score=-2.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RkN3ge7nbGue for <manet@ietfa.amsl.com>; Wed, 24 Sep 2014 06:15:47 -0700 (PDT)
Received: from nm31-vm6.bullet.mail.bf1.yahoo.com (nm31-vm6.bullet.mail.bf1.yahoo.com [72.30.239.14]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D55C1A00C0 for <manet@ietf.org>; Wed, 24 Sep 2014 06:15:47 -0700 (PDT)
Received: from [66.196.81.171] by nm31.bullet.mail.bf1.yahoo.com with NNFMP; 24 Sep 2014 13:15:45 -0000
Received: from [98.139.212.211] by tm17.bullet.mail.bf1.yahoo.com with NNFMP;  24 Sep 2014 13:15:45 -0000
Received: from [127.0.0.1] by omp1020.mail.bf1.yahoo.com with NNFMP; 24 Sep 2014 13:15:45 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 627093.23322.bm@omp1020.mail.bf1.yahoo.com
Received: (qmail 74157 invoked by uid 60001); 24 Sep 2014 13:15:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1411564545; bh=SRYjm6rfzUrvdqSXr1yCDJsWUhStwzwrhY+vPtd1bCo=; h=References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=n1SG+bj/36nYPhsy/sN9krSF3570tVc4y6xxfPWiA8DgxPpdIK/9+taDt7AJ05UK0vZebF5ipsOBEQHdUTeWcBCT1mhTuds5f9QjeL9pfH/azhJ1krdcP2ivQXixFG6B/xEA3bQSRyXu5c7nqGLL9JtKe8CD5WTrb0VwSc1VXx0=
X-YMail-OSG: 8tYLO48VM1m50_Fo21FEiEJJen8j0rR7VplBJPeDTfM.2u1 j3hFsZfKUVFU8T.zNezp0zb5qSlwwDH_uwMff86wUi2XlK0k3Hdu4KYk9fE7 KLvQ_Hx0Qr0fspf0oCDe7x_MVafwiYRDzUkCp5yTdOUjBMxlb0xjF7veEDU5 VlxlytdBX_GIU8sNbr6c1rpH.waLDhBMBV3D8Rddy80Py5LxkYkquBxJr.2u ZicHCFROTPM184_G9eB5a3DfN7cXjUZ9roNVW_in3K6gPVcPHAc7xVOLPBm_ JmwbI_pDlneoabikzJjktrx1D_PVZx1vL8siJVsMSem4cjv_ClTvUUtV_cMl oisGfuuNNkbf1qrod.05escZHX28GIsRgRg6xEW_aqm8n6YyagBRsnBzkt3E 4cEe6.hmV_imolGLuv9vWTqWn4HeUk8rTxF.kJyJvLQLVMakCbWsUjNc1bvJ RTr0Pm8rbeJ_uXsbZciZrweGVdVQWACximvJXE8eCv_qJ6Yk6oJnWNyYN5v3 hGHqQSYPivaukcKIcwdWiaMJLzbt2PpELWwDz07xlgXL8FWY-
Received: from [174.62.202.123] by web140105.mail.bf1.yahoo.com via HTTP; Wed, 24 Sep 2014 06:15:45 PDT
X-Rocket-MIMEInfo: 002.001, V2UgaGF2ZSBqdXN0IHN1Ym1pdHRlZCB2ZXJzaW9uIG9mIDAxIG9mIG91ciBkcmFmdCAiQSBDb21tb24gTGF5ZXIgMyBJbnRlcmZhY2UgZm9yIE1BTkVUIgphbmQgd291bGQgbGlrZSB0byByZXF1ZXN0IFdHIGNvbW1lbnRzIG9yIGlzc3VlcyByZWdhcmRpbmcgbW92aW5nIHRoaXMgZHJhZnQgdG8gYmUgYW4KCkluZm9ybWF0aW9uYWwgUkZDLgoKClRoaXMgZHJhZnQgc3VtbWFyaXplcyBvdXIgdGVzdHMgdXNpbmcgYW4gaW50ZXJmYWNlIGJldHdlZW4gYSBNQU5FVCBhbmQgTDMgcm91dGluZyAoT1NQRnYyCgppbiABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.203.696
References: <20140923174834.12736.4791.idtracker@ietfa.amsl.com>
Message-ID: <1411564545.60710.YahooMailNeo@web140105.mail.bf1.yahoo.com>
Date: Wed, 24 Sep 2014 06:15:45 -0700
From: JS <jshaio@yahoo.com>
To: "manet@ietf.org" <manet@ietf.org>, "macker@itd.nrl.navy.mil" <macker@itd.nrl.navy.mil>, "sratliff@cisco.com" <sratliff@cisco.com>
In-Reply-To: <20140923174834.12736.4791.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/1UhlwFYLaz9pwJNEXHV9Q6tZ6u0
Subject: Re: [manet] New Version for draft-shaio-manet-common-l3-interface-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: JS <jshaio@yahoo.com>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2014 13:15:52 -0000

We have just submitted version of 01 of our draft "A Common Layer 3 Interface for MANET"
and would like to request WG comments or issues regarding moving this draft to be an

Informational RFC.


This draft summarizes our tests using an interface between a MANET and L3 routing (OSPFv2

in our tests but could have been another routing protocol instead).

 
thanks, 
     Jack, Don, Caleb


----- Forwarded Message -----
From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
To: Jack Shaio <jshaio@yahoo.com>; Caleb Lo <clo03@alumni.caltech.edu>; Caleb Lo <clo03@alumni.caltech.edu>; Jack Shaio <jshaio@yahoo.com>; "donb@mitre.org" <donb@mitre.org>; Don Broderick <donb@mitre.org>
Cc: 
Sent: Tuesday, September 23, 2014 1:48 PM
Subject: New Version Notification for draft-shaio-manet-common-l3-interface-01.txt


A new version of I-D, draft-shaio-manet-common-l3-interface-01.txt
has been successfully submitted by Don Broderick and posted to the
IETF repository.

Name:        draft-shaio-manet-common-l3-interface
Revision:    01
Title:        A Common Layer 3 Interface for MANET
Document date:    2014-09-23
Group:        Individual Submission
Pages:        16
URL:            http://www.ietf.org/internet-drafts/draft-shaio-manet-common-l3-interface-01.txt
Status:        https://datatracker.ietf.org/doc/draft-shaio-manet-common-l3-interface/
Htmlized:      http://tools.ietf.org/html/draft-shaio-manet-common-l3-interface-01
Diff:          http://www.ietf.org/rfcdiff?url2=draft-shaio-manet-common-l3-interface-01

Abstract:
   This paper presents an approach that allows an algorithm to choose IP
   routing peers intelligently among the nodes in a MANET but does not
   involve any modifications to existing IP routing protocols. In
   addition, our approach works as a pure interface between (any) MANET
   radio terminal and any IP router, so nodes using our interface
   interoperate with nodes that do not use this interface or with nodes
   using different algorithms to select routing peers. This interface
   was prototyped and this paper includes test results for two different
   mobility patterns on a mobile network using OLSR for MANET routing
   and OSPFv2 for IP routing.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


From nobody Fri Sep 26 06:55:46 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADA7C1A87E1 for <manet@ietfa.amsl.com>; Fri, 26 Sep 2014 06:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9jTzMn0jTr0s for <manet@ietfa.amsl.com>; Fri, 26 Sep 2014 06:55:43 -0700 (PDT)
Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEDFF1A87B8 for <manet@ietf.org>; Fri, 26 Sep 2014 06:55:42 -0700 (PDT)
Received: by mail-yk0-f174.google.com with SMTP id q9so3444190ykb.19 for <manet@ietf.org>; Fri, 26 Sep 2014 06:55:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Cv8hFYRMzuxLtLjWyADyiVY6tAPuXLuS3E/zKWbpR7A=; b=gc5ji06bMYkisOnza63HRubHtlMRk1xznUDDVBH45HHfTj89Dyc7UEtjb0YKJFU+Cz wJqY6AjUYOQQ77hjjSZPx3sXwNEtJWrLfjyJ5HMM8pUjZ/b4PLORRNM7tiDLbaTHy0QG etHXO/jFMaG9jkQ7Tx+yI5CHmt9JcqqZum4kSVaVe0pbESLvEHWHkIEBaLVvs2P+CHRD WLgsV5dfD/7bHMprKBZY7wTzqLacO99JHii3s/M4r6y/hn5sU8tp6h3p+FyuDMZkuNe9 Yj1TwSnS9mFtW1KtQiY7sBCsn6LVv+MtKUw5HEi3/fyoubR+Um/UzLQW/24R4EFx1jN7 NKPA==
MIME-Version: 1.0
X-Received: by 10.236.90.78 with SMTP id d54mr1034580yhf.182.1411739742017; Fri, 26 Sep 2014 06:55:42 -0700 (PDT)
Received: by 10.170.150.194 with HTTP; Fri, 26 Sep 2014 06:55:41 -0700 (PDT)
In-Reply-To: <A34255DF-DA0F-47B9-B602-C2BF749B2B2F@cisco.com>
References: <066.3e1906b2a4af830a63b2dc76aad57fbe@trac.tools.ietf.org> <C83A8919-4D6A-4B64-9695-8A60CFA45908@gmail.com> <CADnDZ88rmtEHyLheZKrUNXaoBt42A2Ty1RQ6TeShqGg98qPDzw@mail.gmail.com> <A34255DF-DA0F-47B9-B602-C2BF749B2B2F@cisco.com>
Date: Fri, 26 Sep 2014 15:55:41 +0200
Message-ID: <CADnDZ8-KZRu8NBED+RG9dMQWGA=8NcLrWhaqnju5OGk7W-bDUA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
Content-Type: multipart/alternative; boundary=20cf300e5531d69fad0503f84590
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/_X00syy6iR90MisQcFAYwwp34vA
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] #55 (olsrv2-multitopology): Maintaining Multiple Routing Sets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2014 13:55:44 -0000

--20cf300e5531d69fad0503f84590
Content-Type: text/plain; charset=UTF-8

Hi

On Sunday, September 21, 2014, Stan Ratliff (sratliff) wrote:

>  Abdussalam,
>
>  On Sep 21, 2014, at 7:53 AM, Abdussalam Baryun <
> abdussalambaryun@gmail.com> wrote:
>
> Section 11 and subsection 6.8 need more specification details for routing
> maintenance.
>
> On Saturday, August 23, 2014, Christopher Dearlove wrote:
>
>> ....
>>
>> Yes, the draft does describe creating multiple routing sets. See Section
>> 11. If familiar with OLSRv2, that's all you need - because OLSRv2 describes
>> how a Routing Set is calculated and when it needs to change.
>
>
>  Already seen section 11 when reviewed but is not enough. Regarding
> RFC7181 (which section refers to) it is only for single topology, so for MT
> we need a fresh maintenance paragraph at least. In subsection 6.8 it does
> not describe how is the separation. In section 11 it does not describe how
> the calculation separates routing sets. The is a need to add an element in
> routing set for metric type. All maps are done with metric type
> reference, but in the routing sets there is no element for metric type or
> reference.
>
>
>  I want to reinforce what Chris Dearlove said in another email. The text
> above implies (at least to me) that you have a specific deployment scenario
> in mind, and that when looking at the text of the draft, you conclude that
> your scenario won't work. If that is the case, describe the scenario
>


That is not the case, the scenarios are general purpose of MANET or as
RFC7181. The case is the draft reader did not understand and is discussing
to clarify the issues. The reader is referring to texts in the draft
related to updating routing sets. Generally, the case is that some of my
questions are not getting clear answers. It is good that reader reviewing
and commenting on draft and sharing his/her understanding
or misunderstanding. I want to implement the work then will think about
scenarios.



> - I'm not able to follow your concerns, above some vague notion that "this
> won't work". Without the necessary detail, I can only conclude that
> consensus exists to progress the draft, and you are "in the rough".
>

 I never said it does not work. I want the draft to be clear to readers how
protocol works. Does your message mean stop discussing because your in
the rough? Or stop because you have no scenario detail (usually my scenario
is the draft scenario). The WG is small in size so maybe 10% participants
don't understand the work. The IETF is not about only consensus, but about
publishing readable work that full community can understand and implement.

AB

--20cf300e5531d69fad0503f84590
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi<br><br>On Sunday, September 21, 2014, Stan Ratliff (sratliff)  wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Abdussalam,
<div><br>
<div>
<div>On Sep 21, 2014, at 7:53 AM, Abdussalam Baryun &lt;<a>abdussalambaryun=
@gmail.com</a>&gt; wrote:</div>
<br>
<blockquote type=3D"cite">Section 11 and subsection=C2=A06.8 need more spec=
ification=C2=A0details for routing maintenance.=C2=A0<br>
<br>
On Saturday, August 23, 2014, Christopher Dearlove wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
....<br>
<br>
Yes, the draft does describe creating multiple routing sets. See Section 11=
. If familiar with OLSRv2, that&#39;s all you need - because OLSRv2 describ=
es how a Routing Set is calculated and when it needs to change.</blockquote=
>
<div><br>
</div>
<div>Already seen section 11 when reviewed but is not enough. Regarding RFC=
7181 (which section refers=C2=A0to)=C2=A0it is only=C2=A0for single topolog=
y, so for MT we need a fresh maintenance paragraph at least. In subsection =
6.8 it does not describe how is the=C2=A0separation.=C2=A0In
 section 11 it does not describe how the calculation separates routing sets=
. The is a need to add an element in routing set for metric type. All maps =
are=C2=A0done with metric type reference,=C2=A0but in the routing sets ther=
e is no element for metric type or reference.=C2=A0</div>
</blockquote>
<div><br>
</div>
<div>I want to reinforce what Chris Dearlove said in another email. The tex=
t above implies (at least to me) that you have a specific deployment scenar=
io in mind, and that when looking at the text of the draft, you conclude th=
at your scenario won&#39;t work. If
 that is the case, describe the scenario=C2=A0</div><div></div></div></div>=
</div></blockquote><div><br></div><div><br></div><div>That is not the case,=
 the scenarios are general purpose of MANET=C2=A0or as RFC7181.=C2=A0The ca=
se is the draft=C2=A0reader did not understand and is discussing to clarify=
 the issues. The reader is referring to=C2=A0texts in=C2=A0the draft relate=
d to updating routing sets. Generally, the case is=C2=A0that some of=C2=A0m=
y questions are not getting clear=C2=A0answers. It is good=C2=A0that reader=
=C2=A0reviewing and commenting on draft=C2=A0and sharing his/her=C2=A0under=
standing or=C2=A0misunderstanding. I want to implement the work then will t=
hink about scenarios.=C2=A0</div><div><br></div><div>=C2=A0=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><div><d=
iv>- I&#39;m not able to follow your concerns, above some vague notion that=
 &quot;this won&#39;t work&quot;. Without the necessary detail, I can only =
conclude that consensus exists to progress the draft, and you are &quot;in =
the rough&quot;.=C2=A0</div></div></div></div></blockquote><div><br></div><=
div>=C2=A0I=C2=A0never said it does not work. I want the draft to be clear =
to readers=C2=A0how protocol works. Does your message mean stop discussing =
because your in the=C2=A0rough?=C2=A0Or stop because you have no scenario d=
etail (usually my scenario is the draft scenario). The WG is small in size =
so maybe 10% participants don&#39;t understand the work.=C2=A0The=C2=A0IETF=
 is not about only consensus, but about publishing readable work that full=
=C2=A0community can understand and implement.=C2=A0<span></span></div><div>=
<br></div><div>AB</div><div>=C2=A0</div>

--20cf300e5531d69fad0503f84590--


From nobody Fri Sep 26 10:07:24 2014
Return-Path: <christopher.dearlove@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ACC41A016F for <manet@ietfa.amsl.com>; Fri, 26 Sep 2014 10:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjFd6w0W0T5h for <manet@ietfa.amsl.com>; Fri, 26 Sep 2014 10:07:17 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D96D1A0130 for <manet@ietf.org>; Fri, 26 Sep 2014 10:07:16 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id r20so11380105wiv.14 for <manet@ietf.org>; Fri, 26 Sep 2014 10:07:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=itqqGFJGxE6uqQcZdY5wVna9S8VZJh5OaJgk7V3A7NE=; b=ojDMEeVqPvW8IrQOamCaTpVRCuqKiDaigvsIBw+JTqkZTb/sVs32mxzO0WIJagxaAI Swig2gmJVlJsUqVsJ67lfa6Tc+RDaprGRRu1KUCb1iLXddYO7ccjpZ/1rMOaqEha/7nC N37pDT2gz8cxFB0urS2x59JAcEah4IQmalcg0BNmD7qOsSAFyAYsZiIR/9mY+ALgDva7 fv1uow4epp39yrRd4iMXwwevZmTDHwN8T5P2om/KMIK+MccIL2vyecWks7vnkZ0mO7XK g+2XGcTr446VNN3fu8hSsXQI9m4OeJZJNmjcnIOGa32LBadslESw3hJQsMrO6tHn9lZU sz8A==
X-Received: by 10.194.78.4 with SMTP id x4mr25592793wjw.44.1411751235754; Fri, 26 Sep 2014 10:07:15 -0700 (PDT)
Received: from [10.5.18.96] (dab-glb1-h-10-1.dab.02.net. [82.132.216.142]) by mx.google.com with ESMTPSA id dc9sm2875133wib.5.2014.09.26.10.07.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Sep 2014 10:07:14 -0700 (PDT)
References: <066.3e1906b2a4af830a63b2dc76aad57fbe@trac.tools.ietf.org> <C83A8919-4D6A-4B64-9695-8A60CFA45908@gmail.com> <CADnDZ88rmtEHyLheZKrUNXaoBt42A2Ty1RQ6TeShqGg98qPDzw@mail.gmail.com> <A34255DF-DA0F-47B9-B602-C2BF749B2B2F@cisco.com> <CADnDZ8-KZRu8NBED+RG9dMQWGA=8NcLrWhaqnju5OGk7W-bDUA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ8-KZRu8NBED+RG9dMQWGA=8NcLrWhaqnju5OGk7W-bDUA@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-C5522421-9520-47F6-82C3-4EDE5BE7B449
Content-Transfer-Encoding: 7bit
Message-Id: <63AF3FF4-9F0B-4717-958B-BBD0610DE6E3@gmail.com>
X-Mailer: iPhone Mail (12A365)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Fri, 26 Sep 2014 18:07:09 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/nqWdlSF_PStPXjeyYSg61dT3rkk
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>, "Stan Ratliff \(sratliff\)" <sratliff@cisco.com>
Subject: Re: [manet] #55 (olsrv2-multitopology): Maintaining Multiple Routing Sets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2014 17:07:20 -0000

--Apple-Mail-C5522421-9520-47F6-82C3-4EDE5BE7B449
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

The chair has pointed out this discussion should stop. And strictly I'm viol=
ating that. But find another person, one who understands OLSRv2 but not MT-O=
LSRv2, then there may be something to say.

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 26 Sep 2014, at 14:55, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
>=20
> Hi
>=20
>> On Sunday, September 21, 2014, Stan Ratliff (sratliff) wrote:
>> Abdussalam,
>>=20
>>> On Sep 21, 2014, at 7:53 AM, Abdussalam Baryun <abdussalambaryun@gmail.c=
om> wrote:
>>>=20
>>> Section 11 and subsection 6.8 need more specification details for routin=
g maintenance.=20
>>>=20
>>>> On Saturday, August 23, 2014, Christopher Dearlove wrote:
>>>> ....
>>>>=20
>>>> Yes, the draft does describe creating multiple routing sets. See Sectio=
n 11. If familiar with OLSRv2, that's all you need - because OLSRv2 describe=
s how a Routing Set is calculated and when it needs to change.
>>>=20
>>> Already seen section 11 when reviewed but is not enough. Regarding RFC71=
81 (which section refers to) it is only for single topology, so for MT we ne=
ed a fresh maintenance paragraph at least. In subsection 6.8 it does not des=
cribe how is the separation. In section 11 it does not describe how the calc=
ulation separates routing sets. The is a need to add an element in routing s=
et for metric type. All maps are done with metric type reference, but in the=
 routing sets there is no element for metric type or reference.=20
>>=20
>> I want to reinforce what Chris Dearlove said in another email. The text a=
bove implies (at least to me) that you have a specific deployment scenario i=
n mind, and that when looking at the text of the draft, you conclude that yo=
ur scenario won't work. If that is the case, describe the scenario=20
>=20
>=20
> That is not the case, the scenarios are general purpose of MANET or as RFC=
7181. The case is the draft reader did not understand and is discussing to c=
larify the issues. The reader is referring to texts in the draft related to u=
pdating routing sets. Generally, the case is that some of my questions are n=
ot getting clear answers. It is good that reader reviewing and commenting on=
 draft and sharing his/her understanding or misunderstanding. I want to impl=
ement the work then will think about scenarios.=20
>=20
>  =20
>> - I'm not able to follow your concerns, above some vague notion that "thi=
s won't work". Without the necessary detail, I can only conclude that consen=
sus exists to progress the draft, and you are "in the rough".=20
>=20
>  I never said it does not work. I want the draft to be clear to readers ho=
w protocol works. Does your message mean stop discussing because your in the=
 rough? Or stop because you have no scenario detail (usually my scenario is t=
he draft scenario). The WG is small in size so maybe 10% participants don't u=
nderstand the work. The IETF is not about only consensus, but about publishi=
ng readable work that full community can understand and implement.=20
>=20
> AB
> =20

--Apple-Mail-C5522421-9520-47F6-82C3-4EDE5BE7B449
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>The chair has pointed out this discuss=
ion should stop. And strictly I'm violating that. But find another person, o=
ne who understands OLSRv2 but not MT-OLSRv2, then there may be something to s=
ay.</div><div><br>-- &nbsp;<div>Christopher Dearlove</div><div><a href=3D"ma=
ilto:christopher.dearlove@gmail.com">christopher.dearlove@gmail.com</a> (iPh=
one)</div><div><a href=3D"mailto:chris@mnemosyne.demon.co.uk">chris@mnemosyn=
e.demon.co.uk</a> (home)</div></div><div><br>On 26 Sep 2014, at 14:55, Abdus=
salam Baryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">abdussalambar=
yun@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>Hi<=
br><br>On Sunday, September 21, 2014, Stan Ratliff (sratliff)  wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Abdussalam,
<div><br>
<div>
<div>On Sep 21, 2014, at 7:53 AM, Abdussalam Baryun &lt;<a>abdussalambaryun@=
gmail.com</a>&gt; wrote:</div>
<br>
<blockquote type=3D"cite">Section 11 and subsection&nbsp;6.8 need more speci=
fication&nbsp;details for routing maintenance.&nbsp;<br>
<br>
On Saturday, August 23, 2014, Christopher Dearlove wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
....<br>
<br>
Yes, the draft does describe creating multiple routing sets. See Section 11.=
 If familiar with OLSRv2, that's all you need - because OLSRv2 describes how=
 a Routing Set is calculated and when it needs to change.</blockquote>
<div><br>
</div>
<div>Already seen section 11 when reviewed but is not enough. Regarding RFC7=
181 (which section refers&nbsp;to)&nbsp;it is only&nbsp;for single topology,=
 so for MT we need a fresh maintenance paragraph at least. In subsection 6.8=
 it does not describe how is the&nbsp;separation.&nbsp;In
 section 11 it does not describe how the calculation separates routing sets.=
 The is a need to add an element in routing set for metric type. All maps ar=
e&nbsp;done with metric type reference,&nbsp;but in the routing sets there i=
s no element for metric type or reference.&nbsp;</div>
</blockquote>
<div><br>
</div>
<div>I want to reinforce what Chris Dearlove said in another email. The text=
 above implies (at least to me) that you have a specific deployment scenario=
 in mind, and that when looking at the text of the draft, you conclude that y=
our scenario won't work. If
 that is the case, describe the scenario&nbsp;</div><div></div></div></div><=
/div></blockquote><div><br></div><div><br></div><div>That is not the case, t=
he scenarios are general purpose of MANET&nbsp;or as RFC7181.&nbsp;The case i=
s the draft&nbsp;reader did not understand and is discussing to clarify the i=
ssues. The reader is referring to&nbsp;texts in&nbsp;the draft related to up=
dating routing sets. Generally, the case is&nbsp;that some of&nbsp;my questi=
ons are not getting clear&nbsp;answers. It is good&nbsp;that reader&nbsp;rev=
iewing and commenting on draft&nbsp;and sharing his/her&nbsp;understanding o=
r&nbsp;misunderstanding. I want to implement the work then will think about s=
cenarios.&nbsp;</div><div><br></div><div>&nbsp;&nbsp;</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;paddi=
ng-left:1ex"><div style=3D"word-wrap:break-word"><div><div><div>- I'm not ab=
le to follow your concerns, above some vague notion that "this won't work". W=
ithout the necessary detail, I can only conclude that consensus exists to pr=
ogress the draft, and you are "in the rough".&nbsp;</div></div></div></div><=
/blockquote><div><br></div><div>&nbsp;I&nbsp;never said it does not work. I w=
ant the draft to be clear to readers&nbsp;how protocol works. Does your mess=
age mean stop discussing because your in the&nbsp;rough?&nbsp;Or stop becaus=
e you have no scenario detail (usually my scenario is the draft scenario). T=
he WG is small in size so maybe 10% participants don't understand the work.&=
nbsp;The&nbsp;IETF is not about only consensus, but about publishing readabl=
e work that full&nbsp;community can understand and implement.&nbsp;<span></s=
pan></div><div><br></div><div>AB</div><div>&nbsp;</div>
</div></blockquote></body></html>=

--Apple-Mail-C5522421-9520-47F6-82C3-4EDE5BE7B449--

