
From nobody Mon Nov  2 05:37:01 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 734431B368E; Mon,  2 Nov 2015 05:36:58 -0800 (PST)
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: 6.7.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151102133658.9081.1395.idtracker@ietfa.amsl.com>
Date: Mon, 02 Nov 2015 05:36:58 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/UaU8rjjqDdIdLDZc322fqpQu-g4>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-07.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: <https://mailarchive.ietf.org/arch/browse/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, 02 Nov 2015 13:36:58 -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           : Packet Sequence Number based directional airtime metric for OLSRv2
        Authors         : Henning Rogge
                          Emmanuel Baccelli
	Filename        : draft-ietf-manet-olsrv2-dat-metric-07.txt
	Pages           : 19
	Date            : 2015-11-02

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:
https://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-dat-metric-07


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 Nov  2 05:45:11 2015
Return-Path: <henning.rogge@fkie.fraunhofer.de>
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 AE1F61B36A7 for <manet@ietfa.amsl.com>; Mon,  2 Nov 2015 05:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 GM10gFzOL9v4 for <manet@ietfa.amsl.com>; Mon,  2 Nov 2015 05:45:08 -0800 (PST)
Received: from a.mx.fkie.fraunhofer.de (a.mx.fkie.fraunhofer.de [IPv6:2001:638:401:102:1aa9:5ff:fe5f:7f22]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 819691B36A5 for <manet@ietf.org>; Mon,  2 Nov 2015 05:45:08 -0800 (PST)
Received: from rufsun5.fkie.fraunhofer.de ([128.7.2.5] helo=mailhost.fkie.fraunhofer.de) by a.mx.fkie.fraunhofer.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henning.rogge@fkie.fraunhofer.de>) id 1ZtFQ1-0004Ou-Ua; Mon, 02 Nov 2015 14:45:05 +0100
Received: from mailserv2acas.fkie.fraunhofer.de ([128.7.96.54] helo=mailserv2.fkie.fraunhofer.de) by mailhost.fkie.fraunhofer.de with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <henning.rogge@fkie.fraunhofer.de>) id 1ZtFQ1-00019F-Qo; Mon, 02 Nov 2015 14:45:05 +0100
Received: from [128.7.5.36] (128.7.5.36) by MAILSERV2ACAS.lorien.fkie.fgan.de (128.7.96.58) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 2 Nov 2015 14:45:05 +0100
To: <manet@ietf.org>
References: <20151102133658.9081.1395.idtracker@ietfa.amsl.com>
From: Henning Rogge <henning.rogge@fkie.fraunhofer.de>
Message-ID: <563768DD.7010507@fkie.fraunhofer.de>
Date: Mon, 2 Nov 2015 14:45:01 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151102133658.9081.1395.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms010907060003090004040402"
X-Originating-IP: [128.7.5.36]
X-Virus-Scanned: yes (ClamAV 0.98.1/21032/Sun Nov 1 15:56:21 2015) by a.mx.fkie.fraunhofer.de
X-Scan-Signature: ff5b53f4d81aecd7a6b2d230e03a1f9e
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Vg_PS-sGVqCtkeRS5qsmDaxDPOs>
Subject: Re: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-07.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: <https://mailarchive.ietf.org/arch/browse/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, 02 Nov 2015 13:45:10 -0000

--------------ms010907060003090004040402
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable

On 11/02/2015 02:36 PM, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
>   This draft is a work item of the Mobile Ad-hoc Networks Working Group=
 of the IETF.
>
>          Title           : Packet Sequence Number based directional air=
time metric for OLSRv2
>          Authors         : Henning Rogge
>                            Emmanuel Baccelli
> 	Filename        : draft-ietf-manet-olsrv2-dat-metric-07.txt
> 	Pages           : 19
> 	Date            : 2015-11-02

Hi,

this is the (long delayed) new revision of the DAT metric draft, created =

as a response to the long review of Alvaro Retana.

I fixed a few issues with the draft and tried to clarify other regions=20
which could be hard to understand. I also added a new appendix that=20
describes the coming work in regards to metrics.

Henning Rogge


--=20
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut f=FCr
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Fraunhofer Stra=DFe 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961,   Fax +49 228 9435 685
mailto:henning.rogge@fkie.fraunhofer.de http://www.fkie.fraunhofer.de


--------------ms010907060003090004040402
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
FGAwggQuMIIDFqADAgECAgIBDDANBgkqhkiG9w0BAQUFADBxMQswCQYDVQQGEwJERTEcMBoG
A1UEChMTRGV1dHNjaGUgVGVsZWtvbSBBRzEfMB0GA1UECxMWVC1UZWxlU2VjIFRydXN0IENl
bnRlcjEjMCEGA1UEAxMaRGV1dHNjaGUgVGVsZWtvbSBSb290IENBIDIwHhcNMDcxMjA1MTUx
ODU4WhcNMTkwNjMwMjM1OTU5WjBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2Zl
cjEhMB8GA1UECxMYRnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhv
ZmVyIFJvb3QgQ0EgMjAwNzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMM9Hsll
jVuIN/c+wSG2VN6wOlcbGhzumAh0AVpvtd82VytERc7zRhNldpWYVMeohRVuEqQX6AvhIacx
PSnd/6PWT9K0if1jStqrU+9ZBbRP4jsqkZnAy2VXgaMwk5AOyb39FTIyCKRIfFYF8rs2ieJI
wm9LkgwlRb6tPtTHAe2xyBK0MAhup29/eiCnu7TlNYBULBmP2UvAHatD+GEUlPuwHV23kexi
wJHRXt2nC7MtH2Y5GDyuBBTl0n022bLNpxOwzEWdVgRRcTM2XC9dUROeT0iQDpdaS3DbuXnZ
odaUyJLQpftgvy2tnnEAF4bA/UhmnRRMBU5M0XFEC9B6D7ECAwEAAaOB2TCB1jAfBgNVHSME
GDAWgBQxw3kbuvVT1xfgiXotF2wKsyudMzAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFC9F
Qh4xBYDVcNj4HVfLW3rVPZz3MBIGA1UdEwEB/wQIMAYBAf8CAQEwcAYDVR0fBGkwZzBloGOg
YYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9Eb3dubG9hZEFS
TC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwDQYJKoZIhvcN
AQEFBQADggEBABq3THo85d3CY7LehiVORWJM9PKPX13X5Y3ODtf1lOGLkzE2p5oj52fhUsFa
GNaZ4YBkOA9KNTNdZnoo3Dh/N3LNUnVuEI5sfYz3Ket3wrkZBdS3PWG66AUS1FBiU+8iVGL8
TQHDXtQNg3RpUdU8nqzbpCt8bYSW03FNz9UtcaOSxD9Vz5s9I3cHV+nIzh2XtjP7kZdglg/3
9t5vJZASqxlH1UQjrsGSNSi/KkNeD+oHXdJE0IWC4xK8R+osrfjwQVJ9Nroin3qgMu9LvPk6
B7Ypxn04XzVVfjjyP3yz7i1uIXhfuRPP795lgMgl9WYtVEqtztkuDjDPgDOnixly6kEwggTG
MIIDrqADAgECAgphHTMZAAAAAAADMA0GCSqGSIb3DQEBBQUAMGcxCzAJBgNVBAYTAkRFMRMw
EQYDVQQKEwpGcmF1bmhvZmVyMSEwHwYDVQQLExhGcmF1bmhvZmVyIENvcnBvcmF0ZSBQS0kx
IDAeBgNVBAMTF0ZyYXVuaG9mZXIgUm9vdCBDQSAyMDA3MB4XDTA3MTIxMjE0NDkzNVoXDTE5
MDYzMDIzNTk1OVowZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNV
BAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2Vy
IENBIDIwMDcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDCdBBRy3XRgfErNZ1a
gjqvkq7NAvyuyPsgdw7/aBIVkEmnZ3xoJF/6DiYaZT5KngkK04dPMxGKa1WiS02lT1Yb48d4
efijC95VRmSH2owPPU6JYS8JPppdvVW6leZy4Ta0sHWctee2+nQruSX38b6TucFwp/eWf0y8
i3XrsYFR7PzJ4XM75gWwUUvjsPVKCp/j2b8mJlBHTh4PHAOTxhWkT/avPKu9+FZ5SPluPsuw
aDecLbqla6lm26TkNrB2KPa4r92/seVnbDK1YnihgKUP3Tb4Aeb7rgHIUZ7ADWR4KQIjwsz+
/0BWGKpNrp3XMRF8D4KO9qInwd7kGd8Rzlf3AgMBAAGjggFyMIIBbjASBgNVHRMBAf8ECDAG
AQH/AgEAMB0GA1UdDgQWBBRPHa+Iym24qhwJ+cXREe1ZtJP6CzAOBgNVHQ8BAf8EBAMCAQYw
HwYDVR0jBBgwFoAUL0VCHjEFgNVw2PgdV8tbetU9nPcwdQYDVR0fBG4wbDBqoGigZoYxaHR0
cDovL2NybC5wa2kuZnJhdW5ob2Zlci5kZS9maGctcm9vdC1jYS0yMDA3LmNybIYxaHR0cDov
L2NybC5mcmF1bmhvZmVyLXBraS5kZS9maGctcm9vdC1jYS0yMDA3LmNybDCBkAYIKwYBBQUH
AQEEgYMwgYAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2Zo
Zy1yb290LWNhLTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVy
LXBraS5kZS9maGctcm9vdC1jYS0yMDA3LmNlcjANBgkqhkiG9w0BAQUFAAOCAQEAAHdsjDP5
7lcEJcrLiDnmTkykzsKWSxmGTbhEV8KVqRA37DBVMV/1nrW7tWtaoXfseksl2OFdQs3BQzhh
d8AO28iFf+ncgudyPZbmU48vc41LIy2bnA+I3jY2t0BLt/bELGLLhNzE3xRSYK/zXgBTB1ZJ
Bxsd5VV2/hdyd/vcXlx5P8Af8iCnf0SIjDE0+Pmvq2tjEwrGAHuJICdL89k12BjfLbo4woLF
FG8HyQvcKzogiTDSTNYu7FFalSiKLMFu4eUKVlDbtROEQLAxM+3XqVwmGgCMD6axCJK9HROt
86h4ZjOHoEu4hpgXzUKIVDuoyTljXCfXSManNHP+FlB4PDCCBagwggSQoAMCAQICCjQb63gA
AAAAuucwDQYJKoZIhvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9m
ZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5o
b2ZlciBVc2VyIENBIDIwMDcwHhcNMTAwMjAxMTE0MDM0WhcNMTYwMTMxMTE0MDM0WjBaMQsw
CQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjENMAsGA1UECxMERktJRTEPMA0GA1UE
CxMGUGVvcGxlMRYwFAYDVQQDEw1IZW5uaW5nIFJvZ2dlMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAxsgT9VRlhiEraBMqzI0g5nkPrSTp7j5TS/GTjKhiwmyr4hZ6VuurgDhT
Mulz7JRLZJMXJqEwjEBqPiHoGTEkgHl166P/lx2Or+j9XiHPYPxJjDOvRkWsrw+SWuiyacbr
oSTaDwz7nA38R27jXUSEKyi0SmhXYiBUIhh1/sEf/uDmi9oBhfj6gOjzM/vLM7NJqi70CE6U
Ma0Ph8R7H+rwYXhQlVWZzUnKvt6OJFJ4HLJvm6xHreiOrU97kPlwi3YQZUxC439gYPY0wmFE
mddNHOQ2fjtkoQYR9IgGWfP3vbQ8nXxUTIlOhS5x9sSaSU/pTYBJv7xYyjPrS9SIGl5bqQID
AQABo4ICYTCCAl0wDgYDVR0PAQH/BAQDAgbAMCsGA1UdEQQkMCKBIGhlbm5pbmcucm9nZ2VA
ZmtpZS5mcmF1bmhvZmVyLmRlMB0GA1UdDgQWBBQBfgSrsBkuX2mKj92DUbzW0i0r8zAfBgNV
HSMEGDAWgBRPHa+Iym24qhwJ+cXREe1ZtJP6CzB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8v
Y3JsLnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JshjFodHRwOi8vY3Js
LmZyYXVuaG9mZXItcGtpLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JsMIIBCgYIKwYBBQUHAQEE
gf0wgfowPgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11
c2VyLWNhLTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVyLXBr
aS5kZS9maGctdXNlci1jYS0yMDA3LmNlcjA7BggrBgEFBQcwAYYvaHR0cDovL2ZoZy11c2Vy
LWNhLTIwMDcub2NzcC5wa2kuZnJhdW5ob2Zlci5kZS8wOwYIKwYBBQUHMAGGL2h0dHA6Ly9m
aGctdXNlci1jYS0yMDA3Lm9jc3AuZnJhdW5ob2Zlci1wa2kuZGUvMBMGA1UdJQQMMAoGCCsG
AQUFBwMEMEQGA1UdIAQ9MDswOQYLKwYBBAGGClADAQEwKjAoBggrBgEFBQcCARYcaHR0cDov
L3BraS5mcmF1bmhvZmVyLmRlL2NwLzANBgkqhkiG9w0BAQUFAAOCAQEAOayOZLk0fQfhQ7I0
Qzn6KzuD4ixrzteSXITHu1RJ9/3xebplEm6YI/jwMLNFnfglXq+9I+rGjE/PxSOW6qK8CA31
DIo8qXhsxvvfF3yrFzHLzgyCcWdoxer2YvfKpJJfx0BKPGMvuAeTJp5L+PuWcGkvmDb/wRwA
JOfjNSokNdc27k3T+HTtXNsMrQzGWeIZFnK+pSQm/gWoDX7dNZE592/Dq8Rp83jedwl5CDBK
d0B6PDCM7vsEA9P+9L9/142H/1u6gYVNlR7GhsjCjUtsvpDZrMPNAd2wVAPoqiJ0WrfG/IEu
A5SySue+aeflbvMxDT1cWFnighiatWYbxwNmPDCCBbQwggScoAMCAQICCjQb6OgAAAAAuuYw
DQYJKoZIhvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAf
BgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBV
c2VyIENBIDIwMDcwHhcNMTAwMjAxMTE0MDM0WhcNMTYwMTMxMTE0MDM0WjBaMQswCQYDVQQG
EwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjENMAsGA1UECxMERktJRTEPMA0GA1UECxMGUGVv
cGxlMRYwFAYDVQQDEw1IZW5uaW5nIFJvZ2dlMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAosulW1xdX1xuHoX36m/A69SfDwvfsXmrYgI0qhSDgovRnWxT64dxCK2+vU+LskPn
o1m0RJTRbKgVo6O8j1/oU/OBVpi82DM97mWMUxYEpweKLdq+ROTZPUwFY8Qfz8EJ/cZjyrEB
Ys8NxAfRPFRWGd+BrkKNIvB9mr77PQa/rA+qEuNTmKY0Nbl4VAgwmGV37RFA2CLz38wc44ul
oJJKyYIA7CbIMae3kjUKy9YY55kyjgCY3c21/YV4ruOEwBu9yfEBmxx0E1P0/fB7G3+7d6kB
L+avP/QhwYmdJjFsarYSmUpXp9P1+c8HFTw5TYGULtj8f/FWQlmRjWDzSct4eQIDAQABo4IC
bTCCAmkwDgYDVR0PAQH/BAQDAgQwMCsGA1UdEQQkMCKBIGhlbm5pbmcucm9nZ2VAZmtpZS5m
cmF1bmhvZmVyLmRlMB0GA1UdDgQWBBRir/+EBYAUW6PBp6sYHmuGX1+fsjAfBgNVHSMEGDAW
gBRPHa+Iym24qhwJ+cXREe1ZtJP6CzB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8vY3JsLnBr
aS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JshjFodHRwOi8vY3JsLmZyYXVu
aG9mZXItcGtpLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JsMIIBCgYIKwYBBQUHAQEEgf0wgfow
PgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNh
LTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVyLXBraS5kZS9m
aGctdXNlci1jYS0yMDA3LmNlcjA7BggrBgEFBQcwAYYvaHR0cDovL2ZoZy11c2VyLWNhLTIw
MDcub2NzcC5wa2kuZnJhdW5ob2Zlci5kZS8wOwYIKwYBBQUHMAGGL2h0dHA6Ly9maGctdXNl
ci1jYS0yMDA3Lm9jc3AuZnJhdW5ob2Zlci1wa2kuZGUvMB8GA1UdJQQYMBYGCisGAQQBgjcK
AwQGCCsGAQUFBwMEMEQGA1UdIAQ9MDswOQYLKwYBBAGGClADAQEwKjAoBggrBgEFBQcCARYc
aHR0cDovL3BraS5mcmF1bmhvZmVyLmRlL2NwLzANBgkqhkiG9w0BAQUFAAOCAQEABPYI1Hbq
ips/0o+2m6Guww7ys/5F++qSYPq6w4CtlyuPupLZdKzEVuZ2n1fopZuEndTyCTq8DUJwZXKP
EIYKQGhkbFNy3IDaHB5VHaX0JsqV4DsgD6Xa2jnEBQpiy8RxMKP5mY5NRS4jO6J+bFjrMiKb
jDlzvJJxy6kqy8efjxH6RdMjGxQRcMS4EUTs7DRu38A81XEGaqqtjcwN3n3EvJUVcBzXn63B
mb4bgv1U6DYXFMSMcksssapmsdL0EPXKAWBRcswouetjRBXIFfu1xKFINtwyax6RCZycAEXd
dFC6j/3BVvi6iNFSE1VVQx+HQz1EhGBcp80W3qnIvoO1UjGCA4swggOHAgEBMHUwZzELMAkG
A1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29y
cG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2VyIENBIDIwMDcCCjQb63gAAAAA
uucwDQYJYIZIAWUDBAIBBQCgggHnMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTE1MTEwMjEzNDUwNFowLwYJKoZIhvcNAQkEMSIEIMCSRt9R+uIpKPBrj7Y1
5vWpKuxdhQOiChFelG4gp9veMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCG
SAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYF
Kw4DAgcwDQYIKoZIhvcNAwICASgwgYQGCSsGAQQBgjcQBDF3MHUwZzELMAkGA1UEBhMCREUx
EzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBL
STEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2VyIENBIDIwMDcCCjQb6OgAAAAAuuYwgYYGCyqG
SIb3DQEJEAILMXegdTBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEhMB8G
A1UECxMYRnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVyIFVz
ZXIgQ0EgMjAwNwIKNBvo6AAAAAC65jANBgkqhkiG9w0BAQEFAASCAQAuMbcHUc/rZQEBcfWo
DtWfCLaz5I5BvvAQlbFCFUKMr0WDUyHKWcsSPP1vJv1b4hOpL9jLbKhQa0ZtHTyX/IDivEmP
QWFE9qgvh10pQShNY6PSGHClfBtNwTggIB2KF0qAXCQ3iW8JmJpzyz5XbA82LfFQfUjlQFSL
Adbw5kzhNN/ttFY+3iPA2eJXJV3MHz38SzM3ROWMa6puoH//8rfh2vXp3e83Sb+aiiQZcB1y
XQMir2QoemKX+l0XtPD2jy1nip28RqQYgc4iP/4yu5USlCydL1jbvW0hVuUrDd2EmyugYjSK
f8dmQHII9++OJe/D5Sj+EME/UvqihH3zU/4iAAAAAAAA
--------------ms010907060003090004040402--


From nobody Mon Nov  2 17:47:40 2015
Return-Path: <aretana@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 C77171B2B7D for <manet@ietfa.amsl.com>; Mon,  2 Nov 2015 17:47:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 sYMsRVEb-k2X for <manet@ietfa.amsl.com>; Mon,  2 Nov 2015 17:47:35 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD63D1B2B73 for <manet@ietf.org>; Mon,  2 Nov 2015 17:47:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=766; q=dns/txt; s=iport; t=1446515252; x=1447724852; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=N7O23uS7nD/xuro3FW9yq5IQX7qItURAjK4CHDZrMNU=; b=PzTonET6GMTedV5BN7OHP5fZoTxSbvZwBvW03T4LlGTiI6sUlv6NhyDZ LtRxI/sqX3xxhVOVnUpePFbQ77Jd1uocpXtgHY4Bp1HQMc0ltYPky2BUX aE9z2m8EG5eIBXZiU6ahUe1jihOplXyoPDLSyoxm0WsNaXWq5ILMD2M4T c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AbAgD8EDhW/4cNJK1egzuBQga/RAENgVqGGQKBNzgUAQEBAQEBAYEKhDYBAQQ6TwIBCDYQMiUCBAESiDDBfQEBAQEBAQEDAQEBAQEBARyGdwGEfYlAAQSSZoNdAY0kgVmSD4hSAR8BAUKEBHIBhHaBBwEBAQ
X-IronPort-AV: E=Sophos;i="5.20,236,1444694400"; d="scan'208";a="203102405"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-2.cisco.com with ESMTP; 03 Nov 2015 01:47:32 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id tA31lWVu023730 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 3 Nov 2015 01:47:32 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 2 Nov 2015 19:47:31 -0600
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1104.000; Mon, 2 Nov 2015 19:47:31 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Henning Rogge <henning.rogge@fkie.fraunhofer.de>, "manet@ietf.org" <manet@ietf.org>
Thread-Topic: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-07.txt
Thread-Index: AQHRFXOWOOWfxXiMZ0CU9ZrV0VhvxZ6JIwWAgAFguIA=
Date: Tue, 3 Nov 2015 01:47:31 +0000
Message-ID: <D25E3A7D.E791E%aretana@cisco.com>
References: <20151102133658.9081.1395.idtracker@ietfa.amsl.com> <563768DD.7010507@fkie.fraunhofer.de>
In-Reply-To: <563768DD.7010507@fkie.fraunhofer.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.70.230.167]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <77F4AD1A5CF4BA41908D2EAA7C1C9AD8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/XBa5SrapC-eX6DBln-PwHPjOD1A>
Subject: Re: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-07.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: <https://mailarchive.ietf.org/arch/browse/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, 03 Nov 2015 01:47:40 -0000

On 11/2/15, 10:45 PM, "Henning Rogge" <henning.rogge@fkie.fraunhofer.de>
wrote:

Henning:

Hi!

>this is the (long delayed) new revision of the DAT metric draft, created
>as a response to the long review of Alvaro Retana.

Thanks for the update.

I just have a couple of nits:
1. 9.2 s/make this metric ignoring all packets/make this metric ignore all
packets
2. App B.  s/400 routerscovering/400 routers covering

There's no rush in fixing these, but I'm putting the document on the
Dec/3rd IESG Telechat, so an update before Nov/27 would be nice.

I am also going ahead and starting the IETF Last Call.  I'm extending it
for an extra week just because of the fact that we're starting it in the
middle of the IETF week.

Thanks!

Alvaro.


From nobody Mon Nov  2 17:57:46 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB5B1A0137; Mon,  2 Nov 2015 17:57:45 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.7.2
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20151103015745.2752.58097.idtracker@ietfa.amsl.com>
Date: Mon, 02 Nov 2015 17:57:45 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/W3zFAwW2jZao66VLKxZkFHDALZM>
Cc: manet-chairs@ietf.org, manet@ietf.org, draft-ietf-manet-olsrv2-dat-metric@ietf.org
Subject: [manet] Last Call: <draft-ietf-manet-olsrv2-dat-metric-07.txt> (Packet Sequence Number based directional airtime metric for OLSRv2) to Experimental RFC
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Nov 2015 01:57:45 -0000

The IESG has received a request from the Mobile Ad-hoc Networks WG
(manet) to consider the following document:
- 'Packet Sequence Number based directional airtime metric for OLSRv2'
  <draft-ietf-manet-olsrv2-dat-metric-07.txt> as Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-11-23. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document specifies an directional airtime link metric for usage
   in OLSRv2.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/ballot/


No IPR declarations have been submitted directly on this I-D.



From nobody Wed Nov  4 06:44:48 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9549C1B30D0; Wed,  4 Nov 2015 06:44:45 -0800 (PST)
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: 6.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151104144445.16812.82197.idtracker@ietfa.amsl.com>
Date: Wed, 04 Nov 2015 06:44:45 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/qDyvMqsdMHSEdn4rfOZrQCJmGI8>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-08.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: <https://mailarchive.ietf.org/arch/browse/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, 04 Nov 2015 14:44:45 -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           : Packet Sequence Number based directional airtime metric for OLSRv2
        Authors         : Henning Rogge
                          Emmanuel Baccelli
	Filename        : draft-ietf-manet-olsrv2-dat-metric-08.txt
	Pages           : 19
	Date            : 2015-11-04

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:
https://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-dat-metric-08


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 Nov  5 16:06:47 2015
Return-Path: <demadie.workshop@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 0FB721A1EED for <manet@ietfa.amsl.com>; Thu,  5 Nov 2015 16:06:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_51=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 tHKmyHZH1QYE for <manet@ietfa.amsl.com>; Thu,  5 Nov 2015 16:06:44 -0800 (PST)
Received: from mail-yk0-x242.google.com (mail-yk0-x242.google.com [IPv6:2607:f8b0:4002:c07::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED8641A1BFA for <manet@ietf.org>; Thu,  5 Nov 2015 16:06:43 -0800 (PST)
Received: by ykek133 with SMTP id k133so14745053yke.2 for <manet@ietf.org>; Thu, 05 Nov 2015 16:06:43 -0800 (PST)
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=qEYB5fErRzM2flTfXBGayDA83Gsfork+TN48hVrQrK0=; b=oQCdj43/aVdYOyCuVYheK7+vxgugU6Wjx2Z0hFX9iec+kwRhcLirOMSuukjRYjTjPf f4kJ4G5GemIMKU1U2K59nqvYutOluSWQKmPKnyI0DFgNFoMbzy8LunERIVYmJPhuonxd vBcXehrZ0b45+eyomlmqoRODzqCsXlts9l2IqWaNttNOKgBv4Paiosy8MVsP7G21R+1z mNxtmpMKfPkEnakL+S6nBElOxVFdFzP/u+JY0RIuJwcjKkb9lKR4254VohsCoDj+pmFD OMX3/ZZOSU8uyi+UKrqKGbUvVih4xA4b8m+gDWyef3Rkd0OzN05umdh+hxmyi8EUWIcW kTpg==
MIME-Version: 1.0
X-Received: by 10.129.146.81 with SMTP id j78mr9016373ywg.217.1446768403308; Thu, 05 Nov 2015 16:06:43 -0800 (PST)
Received: by 10.37.124.131 with HTTP; Thu, 5 Nov 2015 16:06:43 -0800 (PST)
Date: Fri, 6 Nov 2015 00:06:43 +0000
Message-ID: <CAAwPRrQqfuktupYFcF9ChmSmEnaQ8xkcBsfLRMn0XpuYEBBLxw@mail.gmail.com>
From: DeMaDIE Workshop <demadie.workshop@gmail.com>
To: manet@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c0916fac067490523d404e7
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/kMBp_q0DARvVA9zZohaYjur3D4M>
Subject: [manet] DeMaDIE workshop PAAMS'16: Call for Papers
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: <https://mailarchive.ietf.org/arch/browse/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, 06 Nov 2015 00:06:46 -0000

--94eb2c0916fac067490523d404e7
Content-Type: text/plain; charset=UTF-8

Please consider to contribute to and/or forward to the appropriate groups
the following opportunity to submit and publish original scientific results
to the:

*Decision Making in Dynamic Information Environments (DeMADIE) Workshop*
http://www.paams.net/workshops/demadie

at the

*14th International Conference on Practical Applications of Agents and
Multiagent Systems (PAAMS'16)*
University of Sevilla (Spain)
1st-3rd June, 2016
www.paams.net

*Scope*
In multi-agent systems, an agent which is dependent on the arrival of
information from other agents may have to suspend processes if
communication fails or if the information is simply not available. In most
cases, communication is not guaranteed, and even if it were, there may be
other factors affecting information transfer (such as the impossibility of
or delays in acquiring the information at the source). Furthermore, if
there is no knowledge about the state of the world, getting the appropriate
response to an event becomes impossible. Moreover, in situations which
demand a negotiated outcome, negotiation is impaired by missing information
or uncertainty. Thus, reaching an outcome in such situations requires the
development of decision frameworks that account for missing, contradictory
or uncertain information.

*Topics*
The topics for this workshop include, but are not limited to:


   - Distributed decision making frameworks
   - Coordination mechanisms for rational agents
   - Problem solving with incomplete information
   - Default reasoning
   - Belief revision in multi-agent systems
   - Argumentation
   - Semantic models and ontologies for dynamic environments
   - Models of trust and reputation for agent populations
   - Decision theory in multi-agent systems
   - Speculation and generation of scenarios
   - Communication efficiency in multi-agent systems
   - Utility measures in problem solving
   - Optimization of information exchange
   - Reasoning under uncertainty
   - Fault tolerant architectures
   - Applications (reasoning techniques in dynamic environments such as a
   medical setting, dispute resolution, task scheduling, etc)


*Submission Details*

*Submitting paper*s
Papers must be formatted according to the Springer LNCS Template, with a
maximum length of 12 pages, including figures and references. All proposed
papers must be submitted in electronic form (PDF format) using the Paper
Submission Page. The submission instructions are the same as the general
instructions for PAAMS'16. Templates and more details may be found at
http://www.paams.net/submission
.

*Publication*
Accepted papers will be included in the workshop proceedings after a
careful review process. At least one of the authors will be required to
register and attend the symposium to present the paper in order to include
the paper in the workshop proceedings. All accepted papers will be
published in the CCIS series of Springer Verlag.

*Important Dates*
Submission date:  18th January, 2016
Notification date:  22nd February, 2016
Camera-ready deadline: 07th March, 2016
Conference dates:  1st-3rd June, 2016

*Organizing Committee*
Tiago Oliveira, University of Minho, Portugal
Jose Carlos Montoya, Universidad Carlos III de Madrid, Spain
Paulo Novais, University of Minho, Portugal
Ken Satoh, National Institute of Informatics, Japan


For any questions please contact us at demadie.workshop@gmail.com or Tiago
Oliveira directly at toliveira@di.uminho.pt .

Best regards,

*The Organizing Committee*
Tiago Oliveira
Jose Carlos Montoya
Paulo Novais
Ken Satoh

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

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Please consider to =
contribute to and/or forward to the appropriate groups the following opport=
unity to submit and publish original scientific results to the:</div><div><=
br></div><div><b><font size=3D"4">Decision Making in Dynamic Information En=
vironments (DeMADIE) Workshop</font></b></div><div><a href=3D"http://www.pa=
ams.net/workshops/demadie" target=3D"_blank">http://www.paams.net/workshops=
/demadie</a></div><div><br></div><div>at the</div><div><br></div><div><b>14=
th International Conference on Practical Applications of Agents and Multiag=
ent Systems (PAAMS&#39;16)</b></div><div>University of Sevilla (Spain)</div=
><div>1st-3rd June, 2016</div><div><a href=3D"http://www.paams.net" target=
=3D"_blank">www.paams.net</a></div><div><br></div><div><b>Scope</b></div><d=
iv>In multi-agent systems, an agent which is dependent on the arrival of in=
formation from other agents may have to suspend processes if communication =
fails or if the information is simply not available. In most cases, communi=
cation is not guaranteed, and even if it were, there may be other factors a=
ffecting information transfer (such as the impossibility of or delays in ac=
quiring the information at the source). Furthermore, if there is no knowled=
ge about the state of the world, getting the appropriate response to an eve=
nt becomes impossible. Moreover, in situations which demand a negotiated ou=
tcome, negotiation is impaired by missing information or uncertainty. Thus,=
 reaching an outcome in such situations requires the development of decisio=
n frameworks that account for missing, contradictory or uncertain informati=
on.</div><div><br></div><div><b>Topics</b></div><div>The topics for this wo=
rkshop include, but are not limited to:</div><div><br></div><div><ul><li>Di=
stributed decision making frameworks<br></li><li>Coordination mechanisms fo=
r rational agents<br></li><li>Problem solving with incomplete information<b=
r></li><li>Default reasoning<br></li><li>Belief revision in multi-agent sys=
tems<br></li><li>Argumentation<br></li><li>Semantic models and ontologies f=
or dynamic environments<br></li><li>Models of trust and reputation for agen=
t populations<br></li><li>Decision theory in multi-agent systems<br></li><l=
i>Speculation and generation of scenarios<br></li><li>Communication efficie=
ncy in multi-agent systems<br></li><li>Utility measures in problem solving<=
br></li><li>Optimization of information exchange<br></li><li>Reasoning unde=
r uncertainty<br></li><li>Fault tolerant architectures<br></li><li>Applicat=
ions (reasoning techniques in dynamic environments such as a medical settin=
g, dispute resolution, task scheduling, etc)<br></li></ul></div><div><br></=
div><div><b>Submission Details</b></div><div><br></div><div><i>Submitting p=
aper</i>s</div><div>Papers must be formatted according to the Springer LNCS=
 Template, with a maximum length of 12 pages, including figures and referen=
ces. All proposed papers must be submitted in electronic form (PDF format) =
using the Paper Submission Page. The submission instructions are the same a=
s the general instructions for PAAMS&#39;16. Templates and more details may=
 be found at <a href=3D"http://www.paams.net/submission" target=3D"_blank">=
http://www.paams.net/submission </a>.</div><div><br></div><div><i>Publicati=
on</i></div><div>Accepted papers will be included in the workshop proceedin=
gs after a careful review process. At least one of the authors will be requ=
ired to register and attend the symposium to present the paper in order to =
include the paper in the workshop proceedings. All accepted papers will be =
published in the CCIS series of Springer Verlag.</div><div><br></div><div><=
i>Important Dates</i></div><div>Submission date: =C2=A018th January, 2016</=
div><div>Notification date: =C2=A022nd February, 2016</div><div>Camera-read=
y deadline: 07th March, 2016</div><div>Conference dates: =C2=A01st-3rd June=
, 2016</div><div><br></div><div><b>Organizing Committee</b></div><div>Tiago=
 Oliveira, University of Minho, Portugal=C2=A0</div><div>Jose Carlos Montoy=
a, Universidad Carlos III de Madrid, Spain=C2=A0</div><div>Paulo Novais, Un=
iversity of Minho, Portugal=C2=A0</div><div>Ken Satoh, National Institute o=
f Informatics, Japan</div><div><br></div><div><br></div><div>For any questi=
ons please contact us at <a href=3D"mailto:demadie.workshop@gmail.com" targ=
et=3D"_blank">demadie.workshop@gmail.com</a> or Tiago Oliveira directly at =
<a href=3D"mailto:toliveira@di.uminho.pt" target=3D"_blank">toliveira@di.um=
inho.pt</a> .=C2=A0</div><div><br></div><div>Best regards,</div><div><br></=
div><div><b>The Organizing Committee</b></div><div>Tiago Oliveira</div><div=
>Jose Carlos Montoya</div><div>Paulo Novais</div><div>Ken Satoh</div></div>
<br></div>
<br></div>

--94eb2c0916fac067490523d404e7--


From nobody Fri Nov  6 06:01:31 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DBA991A9044; Fri,  6 Nov 2015 06:01:21 -0800 (PST)
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: 6.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151106140121.14504.14193.idtracker@ietfa.amsl.com>
Date: Fri, 06 Nov 2015 06:01:21 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/6X1vGub2Con7Dw8TX1Z5NpwljUE>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-smf-sec-threats-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: <https://mailarchive.ietf.org/arch/browse/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, 06 Nov 2015 14:01:22 -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-03.txt
	Pages           : 15
	Date            : 2015-11-06

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:
https://tools.ietf.org/html/draft-ietf-manet-smf-sec-threats-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-smf-sec-threats-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 Nov  6 06:10:34 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F6A41A908D; Fri,  6 Nov 2015 06:10:32 -0800 (PST)
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: 6.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151106141032.20708.77172.idtracker@ietfa.amsl.com>
Date: Fri, 06 Nov 2015 06:10:32 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Aj_gpjgwjhBEoFgoobKNP6CL1lQ>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-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: <https://mailarchive.ietf.org/arch/browse/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, 06 Nov 2015 14:10:32 -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 the Optimized Link State Routing Protocol version 2 (OLSRv2)
        Authors         : Thomas Clausen
                          Ulrich Herberg
                          Jiazi Yi
	Filename        : draft-ietf-manet-olsrv2-sec-threats-01.txt
	Pages           : 23
	Date            : 2015-11-06

Abstract:
   This document analyzes common security threats of the Optimized Link
   State Routing Protocol version 2 (OLSRv2) and describes their
   potential impacts on Mobile Ad Hoc Network (MANET) operations.  It
   then analyzes which of these security vulnerabilities can be
   mitigated when using the mandatory-to-implement security mechanisms
   for OLSRv2, and how the vulnerabilities are mitigated.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-manet-olsrv2-sec-threats-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-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 Nov  8 02:00:00 2015
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 0D4241A00F0 for <manet@ietfa.amsl.com>; Sun,  8 Nov 2015 01:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.951
X-Spam-Level: 
X-Spam-Status: No, score=-0.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 C-ySt1bVzaKZ for <manet@ietfa.amsl.com>; Sun,  8 Nov 2015 01:59:58 -0800 (PST)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A10631A00E5 for <manet@ietf.org>; Sun,  8 Nov 2015 01:59:57 -0800 (PST)
Received: by wimw2 with SMTP id w2so53989808wim.1 for <manet@ietf.org>; Sun, 08 Nov 2015 01:59:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=6gULiSQL/+AjmRj4ocEIm5AVbS5/UC3Y89yNH2ufdI8=; b=guau4nz0WbK03gW32zdDB+EWX8+rHHZY6U4Mcq7P5Cs9UIcw5AbbvrwuljiF2lCTU2 VHuMt7ZEae4PaI72D+TzIUaLPp5iff3NXOk4yqlDqedGzSo8AmDtI+0Z6z3X5B6kWBEX TRJ6tsIKPKCaXr/u8nJgT7kcDsE6gADmhjKKETQqaELH447Gjso8j5Ih4EPWzkcmFWv2 u+++MPwxNLUjaW9DJyWGJCmDUUxFiRTa+vHZHaRUfZuBcbyzWpR+7jyp6CKYqZkFV4th Po3p+smbG7hCii2z11yP+il/lBPHrEEahQp93dv5rGqsh/FRIfc7bK7VkgALzIbZj9dI PhrA==
X-Received: by 10.194.7.97 with SMTP id i1mr27421141wja.87.1446976796218; Sun, 08 Nov 2015 01:59:56 -0800 (PST)
Received: from johns-mbp.home (host217-43-35-94.range217-43.btcentralplus.com. [217.43.35.94]) by smtp.gmail.com with ESMTPSA id l186sm8092543wmg.19.2015.11.08.01.59.54 for <manet@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Nov 2015 01:59:55 -0800 (PST)
From: John Dowdell <john.dowdell.ietf@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <25B4C462-C7F2-48F5-A62B-126111C3C1C2@gmail.com>
Date: Sat, 7 Nov 2015 10:58:12 +0000
To: manet@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/YBMcHXSkLO19lBXjRYxUWmdGUxA>
Subject: [manet] Review of draft-ietf-manet-credit-window-00
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Nov 2015 09:59:59 -0000

Stan

Thanks for splitting this out as a separate draft. I believe this will =
set the template for other extension drafts to follow.

On the whole, it=E2=80=99s a good read, however I have some observations =
that could help an implementor, especially one that may be new to DLEP.

1. Clarification

I would like to see a little more expansion of the exchanges during the =
Session Initialisation exchanges for a new destination. Presumably if =
the modem (say) supports Credit Windowing but the router does not, the =
modem would issue the code for =E2=80=98Credit Windowing supported=E2=80=99=
 in the Extensions Supported data item, and the router would then =
respond with its Session Initialisation Response but minus that code in =
its Extensions Supported data item. Is it fair to say that if either end =
supported no extensions, then the Extensions Supported data item would =
not even be sent?

2. Worked example

Just to help things along, I=E2=80=99d like to see a worked example. If =
the Credit Grant is for 1000 octets, then is the value of the Credit =
Increment in the Credit Grant and Credit Window Status data items 1000?

3. Feature Architecture

Is it the case that Credit Windowing (I=E2=80=99ll call this Feature X =
as it=E2=80=99s a generic discussion) would have to be supported =
end-to-end, i.e. if one modem-router pair both supported Feature X then =
for the feature to work properly, the destination modem-router pair =
would also have to support Feature X? It might be worth a few words (in =
a section that can be populated by future extension draft authors too) =
to say how the feature is envisaged to work architecturally; is it a =
purely local modem-router feature, or should (must?) all modem-router =
pairs in a network implement the feature?

So what then if two modem-router pairs happily support Feature X, but a =
newcomer modem-router pair does not? We already know that how the modems =
negotiate with each other is not part of the DLEP specification, so if =
Feature X is required to be implemented end-to-end then the modems would =
have to signal to each other by =E2=80=98radio magic=E2=80=99 that this =
feature is not to be used in this session. The modem =E2=80=98radio =
magic=E2=80=99 negotiation would have to take place before the Session =
Initialisation/Response exchanges. This then places a mandatory =
dependency on the modems to negotiate for DLEP Supported Extensions =
before talking to their respective routers. Should that be something =
that is added to core DLEP?

Best regards
John=


From nobody Sun Nov  8 09:08:07 2015
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 CD02E1A8A76 for <manet@ietfa.amsl.com>; Sun,  8 Nov 2015 09:08:04 -0800 (PST)
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 LUPrXyH28egj for <manet@ietfa.amsl.com>; Sun,  8 Nov 2015 09:08:02 -0800 (PST)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 914701A8A74 for <manet@ietf.org>; Sun,  8 Nov 2015 09:08:02 -0800 (PST)
Received: by wiby19 with SMTP id y19so5595362wib.0 for <manet@ietf.org>; Sun, 08 Nov 2015 09:08:01 -0800 (PST)
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=jkpu9xParf0TtMBH0k4nt0QuW/wkntlTokVuttugX1U=; b=XJXvyly0oBe/+GzRtZ3fWybff6c3vtPo9AasrVl8l2SbayEkKIyEKtmmw06SZjw1qs fvzwwV6WgCmB7i5LANvxwC6zSeIYa4U/vFvcN7bbAjx058Z2e1HKqfvUUoE0wo9FR73T QJlPpqCXw5MFLmr7rr/jxxnrQJ99H5Z7yomd+FjWqXl+cQHkBOLmOwQBD1p55Idv3ZjR LWwlg3B6sY5NmSA0MMP2HERTac12bkYD1xP2C6f20j18z3UWky1iIFqdXOaJkpnkGjf/ 75Xm/PIY87igLBHHOdfjSMyarEZ5jGHK0JbeB1oX3sdMN5kUGktIVBXkQMR11QAfaDpO cJ/Q==
X-Received: by 10.194.173.100 with SMTP id bj4mr24569189wjc.95.1447002481225;  Sun, 08 Nov 2015 09:08:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.191.212 with HTTP; Sun, 8 Nov 2015 09:07:31 -0800 (PST)
In-Reply-To: <CAJVE_fVDCg21bE5hT3UymcSpqD77ujH3q4vsGi-XQoFFiy9FAQ@mail.gmail.com>
References: <CAJVE_fVDCg21bE5hT3UymcSpqD77ujH3q4vsGi-XQoFFiy9FAQ@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Sun, 8 Nov 2015 18:07:31 +0100
Message-ID: <CAGnRvuoWQvFsnmMdzBKGbpiyttem=OXWRhv-FX=6r6A+aJFZMQ@mail.gmail.com>
To: Ahmad Haghighi <haghighi.ahmad@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/88A7dlUYZoOrpMemkcZaairN6zs>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Find Sender of Route Reply
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Nov 2015 17:08:05 -0000

Hi,

a malicious node could easily pretend to be a different node... or try
to "frame" a different node further away.

Without a source-specific signature, how do you want to be sure that a
data field is reliable?

Henning Rogge

On Fri, Oct 16, 2015 at 11:28 AM, Ahmad Haghighi
<haghighi.ahmad@gmail.com> wrote:
> Hello
> I'm working on MANET security and Blackhole/Grayhole detection.
> I have a question, so please help me, or  If you have little time and so
> can't answer me, please refer me to some people or book for finding my
> answer. my question is:
> In MANET (with DSR or AODV) when a Route Reply (RREP) packet received by the
> source node, the source node can not be sure who is the sender of RREP, (it
> is a assumption in all papers) so source node (the node which initiated
> Route Discovery) should do some operations for detecting exact address of
> Malicious node (sender of malicious RREP).
> But e.g. in DSR Header we have a "Source Address" field which carries
> address of sender. or also in IP header of ADOV RREP.
> I don't understand why source node is *not sure* about identity of sender of
> RREP?
> I don't know the reason of above assumption.
>
> Let me explain my question more oblivious.
> Source node, receive a malicious RREP, the source node use it's path for
> sending packets. As expected Malicious node drops all packets.
> Ok.
> Now we want to find malicious node (sender of RREP), If value of "Source
> Address" Was reliable, we be able to easily find malicious node (sender of
> RREP).
> But in all papers, authors employs some mechanisms for detecting malicious
> node (sender of RREP). so we can conclude value of "Source address" field is
> not reliable.
> My question is, why? why source node can not use this field for detecting
> and removing malicious node?
> One answer is because of IP Spoofing i.e malicious node can use another
> address as source address
> but this not the only reason, I need to find another reason for that
>
> I hardly need the answer.
> So please guide me
> Thanks
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>


From nobody Sun Nov  8 17:22:41 2015
Return-Path: <ratliffstan@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 17DAA1B44A9 for <manet@ietfa.amsl.com>; Sun,  8 Nov 2015 17:22:40 -0800 (PST)
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 c1Vn3X17RP9T for <manet@ietfa.amsl.com>; Sun,  8 Nov 2015 17:22:36 -0800 (PST)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51EC71B4476 for <manet@ietf.org>; Sun,  8 Nov 2015 17:22:36 -0800 (PST)
Received: by lbbkw15 with SMTP id kw15so82693103lbb.0 for <manet@ietf.org>; Sun, 08 Nov 2015 17:22:34 -0800 (PST)
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=8kJMIzlMTnnFofTvijftgNOr5aKBCItWOxqIGJYtaLs=; b=tJb/tBiPAsiCJ7p66xUi+bO5mCXeT7xTKFYokOiBSTNTLWyhx1iVrzHLU44MHEOS/h a8pn0YPbqWsmxJ6gSn/C471kWQOqjbn/J14sF9otgTlj+ALkqYy86f7ZHb5xFroNpDc6 d85AZetPe23+6w5T1sKUlQxWb9ZtYtDRINepTVzGHaE4eM5L+4/uy95a7+0F3w8fPr1z L91CkzNIF42f2pabZEmk8p+qYKyjUtY+Zyg/nWwys7JDqI8z2Sfme8GGiYHof83XJ3eA GhELPqbW20ZXNvAfF4kBT2H411X5VU/QrW23SOWuV9aZfNDIxhaUPuEYCjqA1g/HN5qS ZpFw==
MIME-Version: 1.0
X-Received: by 10.112.199.4 with SMTP id jg4mr12884349lbc.59.1447032154430; Sun, 08 Nov 2015 17:22:34 -0800 (PST)
Received: by 10.25.155.134 with HTTP; Sun, 8 Nov 2015 17:22:34 -0800 (PST)
In-Reply-To: <25B4C462-C7F2-48F5-A62B-126111C3C1C2@gmail.com>
References: <25B4C462-C7F2-48F5-A62B-126111C3C1C2@gmail.com>
Date: Sun, 8 Nov 2015 20:22:34 -0500
Message-ID: <CALtoyonWhUMVAi8_uO4k9U-Kn-LCr+NiB2yYT8NEu6pZtQB0FQ@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: John Dowdell <john.dowdell.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c324b08b284e0524116d57
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/5ZmzfMlrAayCk_2C_25r_xumXkw>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Review of draft-ietf-manet-credit-window-00
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Nov 2015 01:22:40 -0000

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

John,

Thanks for the review! Responses inline.


On Sat, Nov 7, 2015 at 5:58 AM, John Dowdell <john.dowdell.ietf@gmail.com>
wrote:

> Stan
>
> Thanks for splitting this out as a separate draft. I believe this will se=
t
> the template for other extension drafts to follow.
>
> On the whole, it=E2=80=99s a good read, however I have some observations =
that
> could help an implementor, especially one that may be new to DLEP.
>
> 1. Clarification
>
> I would like to see a little more expansion of the exchanges during the
> Session Initialisation exchanges for a new destination. Presumably if the
> modem (say) supports Credit Windowing but the router does not, the modem
> would issue the code for =E2=80=98Credit Windowing supported=E2=80=99 in =
the Extensions
> Supported data item, and the router would then respond with its Session
> Initialisation Response but minus that code in its Extensions Supported
> data item. Is it fair to say that if either end supported no extensions,
> then the Extensions Supported data item would not even be sent?
>

Going on your example where the modem supports the extension, but the
router does not - The Peer Init from the router would *not* contain an
entry for it in the "Extensions Supported" data item (Section 10.6 of the
base DLEP draft). Therefore, it would be an error for the mode to use *any*
of the credit windowing extension data items.


>
> 2. Worked example
>
> Just to help things along, I=E2=80=99d like to see a worked example. If t=
he Credit
> Grant is for 1000 octets, then is the value of the Credit Increment in th=
e
> Credit Grant and Credit Window Status data items 1000?
>

I'll try. In your example, the value of the Credit Grant would be 1000, the
value of the Credit Window Status would be the absolute value of the window
(e.g. whatever the 'old' credit count was, plus the new grant of 1000).


>
> 3. Feature Architecture
>
> Is it the case that Credit Windowing (I=E2=80=99ll call this Feature X as=
 it=E2=80=99s a
> generic discussion) would have to be supported end-to-end, i.e. if one
> modem-router pair both supported Feature X then for the feature to work
> properly, the destination modem-router pair would also have to support
> Feature X? It might be worth a few words (in a section that can be
> populated by future extension draft authors too) to say how the feature i=
s
> envisaged to work architecturally; is it a purely local modem-router
> feature, or should (must?) all modem-router pairs in a network implement
> the feature?
>
> So what then if two modem-router pairs happily support Feature X, but a
> newcomer modem-router pair does not? We already know that how the modems
> negotiate with each other is not part of the DLEP specification, so if
> Feature X is required to be implemented end-to-end then the modems would
> have to signal to each other by =E2=80=98radio magic=E2=80=99 that this f=
eature is not to
> be used in this session. The modem =E2=80=98radio magic=E2=80=99 negotiat=
ion would have to
> take place before the Session Initialisation/Response exchanges. This the=
n
> places a mandatory dependency on the modems to negotiate for DLEP Support=
ed
> Extensions before talking to their respective routers. Should that be
> something that is added to core DLEP?
>


Actually, there's nothing about credit-windowing that forces it to be used
by all router-modem pairs as you've outlined - theoretically, I could
deploy one router/modem pair that uses the extension, and another that
doesn't. The windowing isn't 'end-to-end'. Rather, it's just 'local
router-to-local modem' and 'local modem-to-local router'.

Regards,
Stan



>
> Best regards
> John
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

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

<div dir=3D"ltr"><div>John, <br><br></div>Thanks for the review! Responses =
inline.<br><br><div><div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Sat, Nov 7, 2015 at 5:58 AM, John Dowdell <span dir=3D"ltr">&lt;=
<a href=3D"mailto:john.dowdell.ietf@gmail.com" target=3D"_blank">john.dowde=
ll.ietf@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">S=
tan<br>
<br>
Thanks for splitting this out as a separate draft. I believe this will set =
the template for other extension drafts to follow.<br>
<br>
On the whole, it=E2=80=99s a good read, however I have some observations th=
at could help an implementor, especially one that may be new to DLEP.<br>
<br>
1. Clarification<br>
<br>
I would like to see a little more expansion of the exchanges during the Ses=
sion Initialisation exchanges for a new destination. Presumably if the mode=
m (say) supports Credit Windowing but the router does not, the modem would =
issue the code for =E2=80=98Credit Windowing supported=E2=80=99 in the Exte=
nsions Supported data item, and the router would then respond with its Sess=
ion Initialisation Response but minus that code in its Extensions Supported=
 data item. Is it fair to say that if either end supported no extensions, t=
hen the Extensions Supported data item would not even be sent?<br></blockqu=
ote><div><br></div><div>Going on your example where the modem supports the =
extension, but the router does not - The Peer Init from the router would *n=
ot* contain an entry for it in the &quot;Extensions Supported&quot; data it=
em (Section 10.6 of the base DLEP draft). Therefore, it would be an error f=
or the mode to use *any* of the credit windowing extension data items. <br>=
</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>
2. Worked example<br>
<br>
Just to help things along, I=E2=80=99d like to see a worked example. If the=
 Credit Grant is for 1000 octets, then is the value of the Credit Increment=
 in the Credit Grant and Credit Window Status data items 1000?<br></blockqu=
ote><div><br></div><div>I&#39;ll try. In your example, the value of the Cre=
dit Grant would be 1000, the value of the Credit Window Status would be the=
 absolute value of the window (e.g. whatever the &#39;old&#39; credit count=
 was, plus the new grant of 1000). <br></div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
<br>
3. Feature Architecture<br>
<br>
Is it the case that Credit Windowing (I=E2=80=99ll call this Feature X as i=
t=E2=80=99s a generic discussion) would have to be supported end-to-end, i.=
e. if one modem-router pair both supported Feature X then for the feature t=
o work properly, the destination modem-router pair would also have to suppo=
rt Feature X? It might be worth a few words (in a section that can be popul=
ated by future extension draft authors too) to say how the feature is envis=
aged to work architecturally; is it a purely local modem-router feature, or=
 should (must?) all modem-router pairs in a network implement the feature?<=
br>
<br>
So what then if two modem-router pairs happily support Feature X, but a new=
comer modem-router pair does not? We already know that how the modems negot=
iate with each other is not part of the DLEP specification, so if Feature X=
 is required to be implemented end-to-end then the modems would have to sig=
nal to each other by =E2=80=98radio magic=E2=80=99 that this feature is not=
 to be used in this session. The modem =E2=80=98radio magic=E2=80=99 negoti=
ation would have to take place before the Session Initialisation/Response e=
xchanges. This then places a mandatory dependency on the modems to negotiat=
e for DLEP Supported Extensions before talking to their respective routers.=
 Should that be something that is added to core DLEP?<br></blockquote><div>=
<br><br></div><div>Actually, there&#39;s nothing about credit-windowing tha=
t forces it to be used by all router-modem pairs as you&#39;ve outlined - t=
heoretically, I could deploy one router/modem pair that uses the extension,=
 and another that doesn&#39;t. The windowing isn&#39;t &#39;end-to-end&#39;=
. Rather, it&#39;s just &#39;local router-to-local modem&#39; and &#39;loca=
l modem-to-local router&#39;. <br><br></div><div>Regards,<br></div><div>Sta=
n <br></div><div><br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best regards<br>
John<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" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div></div></div></div>

--001a11c324b08b284e0524116d57--


From nobody Mon Nov  9 09:10:23 2015
Return-Path: <sratliff@idirect.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 C42411B7FC6 for <manet@ietfa.amsl.com>; Mon,  9 Nov 2015 09:10:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 oJ1mu7_w9uRZ for <manet@ietfa.amsl.com>; Mon,  9 Nov 2015 09:10:20 -0800 (PST)
Received: from smtp1.idirect.net (smtp1.idirect.net [198.180.159.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DB691B7FC5 for <manet@ietf.org>; Mon,  9 Nov 2015 09:10:20 -0800 (PST)
IronPort-PHdr: 9a23:R3l+xB1MdrGtVVORsmDT+DRfVm0co7zxezQtwd8ZsegTIvad9pjvdHbS+e9qxAeQG96LtrQY0KGH7ujJYi8p39WoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6kO74TNaIBjjLw09fr2zQd6PyZjsnLHvs7ToICx2xxOFKYtoKxu3qQiD/uI3uqBFbpgL9x3Sv3FTcP5Xz247bXianhL7+9vitMU7q3cY6Lod8JsKVKz8crgQTLFEAnIhKW9/rJnuvB/OUSOO62cSFGIMnUwbLRLC6USwZJ7ttir0uK414zWTO8n7XPp8DS+45rtvSRHmoCYLNiQ0+32RjMFs2vEI6Cm9rgByltaHKLqeM+BzK/vQ
X-IronPort-AV: E=Sophos;i="5.20,266,1444708800"; d="scan'208,217";a="438434"
X-IPAS-Result: A2DLAQBI0kBW/8v6+gpeGQEDDwEBAoI+gSB1vjgBDYFhEod5FAEBAQEBAQEBfguCLoIOLV4BDHQmAQQbiCvBJAELIYZWjjUFlkgBjR+BYoRAliofAQGERoVRgQcBAQE
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
Thread-Index: AdEbEMFYH/6T6vHbR1e9WXWwAcrURw==
Date: Mon, 9 Nov 2015 17:10:17 +0000
Message-ID: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: multipart/alternative; boundary="_000_241ccb422cb941bda2617d7be275c649VAUSDITCHM2idirectnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/gsEFpHRXXJFfJ0-C5FuQAHM3XMw>
Subject: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Nov 2015 17:10:23 -0000

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

Hello WG participants -

The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (=
DLEP). The co-authors and the chairs ask that you please take some time to =
review and comment on the new submissions.

Regards,
Stan



_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________

--_000_241ccb422cb941bda2617d7be275c649VAUSDITCHM2idirectnet_
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 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">Hello WG participants &#8211; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">The above referenc=
ed drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (DLEP). The co-auth=
ors and the chairs ask that you please take some
 time to review and comment on the new submissions. <o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Regards,<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Stan<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p><=
/span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br><span style=3D"font-size: 8pt; font-family: Arial, sans-serif; color: #=
003366;">_____________________________________________________<br>This elec=
tronic message and any files transmitted with it contains<br>information fr=
om iDirect, which may be privileged, proprietary<br>and/or confidential. It=
 is intended solely for the use of the individual<br>or entity to whom they=
 are addressed. If you are not the original<br>recipient or the person resp=
onsible for delivering the email to the<br>intended recipient, be advised t=
hat you have received this email<br>in error, and that any use, disseminati=
on, forwarding, printing, or<br>copying of this email is strictly prohibite=
d. If you received this email<br>in error, please delete it and immediately=
 notify the sender.<br>____________________________________________________=
_</span></body>
</html>

--_000_241ccb422cb941bda2617d7be275c649VAUSDITCHM2idirectnet_--


From nobody Wed Nov 11 03:05:24 2015
Return-Path: <haghighi.ahmad@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 8B98F1A008E for <manet@ietfa.amsl.com>; Wed, 11 Nov 2015 03:05:23 -0800 (PST)
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 GRI2_NWLIXsw for <manet@ietfa.amsl.com>; Wed, 11 Nov 2015 03:05:21 -0800 (PST)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 122661A0041 for <manet@ietf.org>; Wed, 11 Nov 2015 03:05:21 -0800 (PST)
Received: by lbblt2 with SMTP id lt2so14812335lbb.3 for <manet@ietf.org>; Wed, 11 Nov 2015 03:05:19 -0800 (PST)
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=yZCWjZYlUkgtHCWIb8mIvSLWXli39Y/3MNTh+o6m2QI=; b=e/fqV6dctw9D+ZFyrAZJzDWAhmO97yseMpBFcLw36Mptc+U4MuN87XcvQ5wOmn8dhb 36wGGi0VVSSwoeDGNvUciNybIqShQhyJkXRLGc/SPEbGNYb435nGgd+s0NNvgup5G0Tl GiDP+N8Cwjb4a8pet//gPGYAsCnEUOJgSsWV9YlW6aH9BhO1bdECAkPULKXbFZdkPmO/ Fj/wOYz2iSn154030t6DObiKICEefEGd+VDwwxAw9cXzKGieaSXDGZf7F7w7SQYTkuxi /G/AdPMNbdkY7xDYmZtsK3+DuzObSY8dqDaEMKdZUi9AWyONKbR5vDz9Z8w/uDw02hQd M31Q==
MIME-Version: 1.0
X-Received: by 10.112.135.65 with SMTP id pq1mr4267203lbb.11.1447239919084; Wed, 11 Nov 2015 03:05:19 -0800 (PST)
Received: by 10.112.139.100 with HTTP; Wed, 11 Nov 2015 03:05:19 -0800 (PST)
Date: Wed, 11 Nov 2015 14:35:19 +0330
Message-ID: <CAJVE_fUFEAY1nWGOW_7G=pBraTj+HeLBNuxK9B1PwEzeBb11+w@mail.gmail.com>
From: Ahmad Haghighi <haghighi.ahmad@gmail.com>
To: manet@ietf.org
Content-Type: multipart/alternative; boundary=089e01182846482e5e052441cd3f
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/rP2ReBI_B8T9oYoEGJd5LIhy4qU>
Subject: Re: [manet] Find Sender of Route Reply
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Nov 2015 11:05:23 -0000

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

Thanks. I think so
But my supervisor wants another reason for that!!!

On Wed, Nov 11, 2015 at 10:50 AM, Ahmad Haghighi <haghighi.ahmad@gmail.com>
wrote:

> Thanks. I think so
> But my supervisor wants another reason for that!!!
>
> On Sun, Nov 8, 2015 at 8:37 PM, Henning Rogge <hrogge@gmail.com> wrote:
>
>> Hi,
>>
>> a malicious node could easily pretend to be a different node... or try
>> to "frame" a different node further away.
>>
>> Without a source-specific signature, how do you want to be sure that a
>> data field is reliable?
>>
>> Henning Rogge
>>
>> On Fri, Oct 16, 2015 at 11:28 AM, Ahmad Haghighi
>> <haghighi.ahmad@gmail.com> wrote:
>> > Hello
>> > I'm working on MANET security and Blackhole/Grayhole detection.
>> > I have a question, so please help me, or  If you have little time and =
so
>> > can't answer me, please refer me to some people or book for finding my
>> > answer. my question is:
>> > In MANET (with DSR or AODV) when a Route Reply (RREP) packet received
>> by the
>> > source node, the source node can not be sure who is the sender of RREP=
,
>> (it
>> > is a assumption in all papers) so source node (the node which initiate=
d
>> > Route Discovery) should do some operations for detecting exact address
>> of
>> > Malicious node (sender of malicious RREP).
>> > But e.g. in DSR Header we have a "Source Address" field which carries
>> > address of sender. or also in IP header of ADOV RREP.
>> > I don't understand why source node is *not sure* about identity of
>> sender of
>> > RREP?
>> > I don't know the reason of above assumption.
>> >
>> > Let me explain my question more oblivious.
>> > Source node, receive a malicious RREP, the source node use it's path f=
or
>> > sending packets. As expected Malicious node drops all packets.
>> > Ok.
>> > Now we want to find malicious node (sender of RREP), If value of "Sour=
ce
>> > Address" Was reliable, we be able to easily find malicious node (sende=
r
>> of
>> > RREP).
>> > But in all papers, authors employs some mechanisms for detecting
>> malicious
>> > node (sender of RREP). so we can conclude value of "Source address"
>> field is
>> > not reliable.
>> > My question is, why? why source node can not use this field for
>> detecting
>> > and removing malicious node?
>> > One answer is because of IP Spoofing i.e malicious node can use anothe=
r
>> > address as source address
>> > but this not the only reason, I need to find another reason for that
>> >
>> > I hardly need the answer.
>> > So please guide me
>> > Thanks
>> >
>> >
>> >
>> > _______________________________________________
>> > manet mailing list
>> > manet@ietf.org
>> > https://www.ietf.org/mailman/listinfo/manet
>> >
>>
>
>
>
> --
> *Ahmad Haghighi.*
> *=E2=80=8B*
> *=E2=80=8BSecure Communications* MSc
>  Student.
> Department of Electrical & Computer Engineering.
> *Yazd University*.
> Islamic Republic of Iran.
>



--=20
*Ahmad Haghighi.*
*=E2=80=8B*
*=E2=80=8BSecure Communications* MSc
 Student.
Department of Electrical & Computer Engineering.
*Yazd University*.
Islamic Republic of Iran.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif"><div class=3D"gmail_default" style=3D"font-size:12.8px">Thanks. =
I think so</div><div class=3D"gmail_default" style=3D"font-size:12.8px">But=
 my supervisor wants another reason for that!!!=C2=A0</div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Nov 11, 2015 at 10:=
50 AM, Ahmad Haghighi <span dir=3D"ltr">&lt;<a href=3D"mailto:haghighi.ahma=
d@gmail.com" target=3D"_blank">haghighi.ahmad@gmail.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:s=
olid;padding-left:1ex"><div dir=3D"ltr"><div style=3D"font-family:tahoma,sa=
ns-serif">Thanks. I think so</div><div style=3D"font-family:tahoma,sans-ser=
if">But my supervisor wants another reason for that!!!=C2=A0</div><div clas=
s=3D"gmail_extra"><div><div class=3D"h5"><br><div class=3D"gmail_quote">On =
Sun, Nov 8, 2015 at 8:37 PM, Henning Rogge <span dir=3D"ltr">&lt;<a href=3D=
"mailto:hrogge@gmail.com" target=3D"_blank">hrogge@gmail.com</a>&gt;</span>=
 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-st=
yle:solid;padding-left:1ex">Hi,<br>
<br>
a malicious node could easily pretend to be a different node... or try<br>
to &quot;frame&quot; a different node further away.<br>
<br>
Without a source-specific signature, how do you want to be sure that a<br>
data field is reliable?<br>
<br>
Henning Rogge<br>
<div><div><br>
On Fri, Oct 16, 2015 at 11:28 AM, Ahmad Haghighi<br>
&lt;<a href=3D"mailto:haghighi.ahmad@gmail.com" target=3D"_blank">haghighi.=
ahmad@gmail.com</a>&gt; wrote:<br>
&gt; Hello<br>
&gt; I&#39;m working on MANET security and Blackhole/Grayhole detection.<br=
>
&gt; I have a question, so please help me, or=C2=A0 If you have little time=
 and so<br>
&gt; can&#39;t answer me, please refer me to some people or book for findin=
g my<br>
&gt; answer. my question is:<br>
&gt; In MANET (with DSR or AODV) when a Route Reply (RREP) packet received =
by the<br>
&gt; source node, the source node can not be sure who is the sender of RREP=
, (it<br>
&gt; is a assumption in all papers) so source node (the node which initiate=
d<br>
&gt; Route Discovery) should do some operations for detecting exact address=
 of<br>
&gt; Malicious node (sender of malicious RREP).<br>
&gt; But e.g. in DSR Header we have a &quot;Source Address&quot; field whic=
h carries<br>
&gt; address of sender. or also in IP header of ADOV RREP.<br>
&gt; I don&#39;t understand why source node is *not sure* about identity of=
 sender of<br>
&gt; RREP?<br>
&gt; I don&#39;t know the reason of above assumption.<br>
&gt;<br>
&gt; Let me explain my question more oblivious.<br>
&gt; Source node, receive a malicious RREP, the source node use it&#39;s pa=
th for<br>
&gt; sending packets. As expected Malicious node drops all packets.<br>
&gt; Ok.<br>
&gt; Now we want to find malicious node (sender of RREP), If value of &quot=
;Source<br>
&gt; Address&quot; Was reliable, we be able to easily find malicious node (=
sender of<br>
&gt; RREP).<br>
&gt; But in all papers, authors employs some mechanisms for detecting malic=
ious<br>
&gt; node (sender of RREP). so we can conclude value of &quot;Source addres=
s&quot; field is<br>
&gt; not reliable.<br>
&gt; My question is, why? why source node can not use this field for detect=
ing<br>
&gt; and removing malicious node?<br>
&gt; One answer is because of IP Spoofing i.e malicious node can use anothe=
r<br>
&gt; address as source address<br>
&gt; but this not the only reason, I need to find another reason for that<b=
r>
&gt;<br>
&gt; I hardly need the answer.<br>
&gt; So please guide me<br>
&gt; Thanks<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div>&gt; _______________________________________________<br>
&gt; manet mailing list<br>
&gt; <a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
&gt;<br>
</blockquote></div><br><br clear=3D"all"><div><br></div></div></div><span c=
lass=3D""><font color=3D"#888888">-- <br><div><div dir=3D"ltr"><font face=
=3D"tahoma, sans-serif" style=3D"color:rgb(69,69,69);font-size:12px"><b>Ahm=
ad Haghighi.</b></font><div><font face=3D"tahoma, sans-serif" style=3D"colo=
r:rgb(69,69,69);font-family:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-s=
erif;font-size:12px"><div style=3D"display:inline"><u>=E2=80=8B</u></div></=
font><div style=3D"color:rgb(136,136,136);font-family:tahoma,sans-serif;fon=
t-size:13px;display:inline"><u>=E2=80=8BSecure Communications</u> MSc</div>=
<span style=3D"color:rgb(136,136,136);font-family:tahoma,sans-serif;font-si=
ze:13px">=C2=A0Student.</span><br style=3D"color:rgb(136,136,136);font-fami=
ly:tahoma,sans-serif;font-size:13px"><font color=3D"#888888" face=3D"tahoma=
, sans-serif">Department of=C2=A0Electrical=C2=A0&amp; Computer Engineering=
.</font><br style=3D"color:rgb(136,136,136);font-family:tahoma,sans-serif;f=
ont-size:13px"><u style=3D"color:rgb(136,136,136);font-family:tahoma,sans-s=
erif;font-size:13px">Yazd University</u><span style=3D"color:rgb(136,136,13=
6);font-family:tahoma,sans-serif;font-size:13px">.=C2=A0</span><br style=3D=
"color:rgb(136,136,136);font-family:tahoma,sans-serif;font-size:13px"><span=
 style=3D"color:rgb(136,136,136);font-family:tahoma,sans-serif;font-size:13=
px">Islamic Republic of Iran.</span></div></div></div>
</font></span></div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature"><div dir=3D"ltr"><font face=3D"tahoma, sans-serif" sty=
le=3D"color:rgb(69,69,69);font-size:12px"><b>Ahmad Haghighi.</b></font><div=
><font face=3D"tahoma, sans-serif" style=3D"color:rgb(69,69,69);font-family=
:&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:12px"><div s=
tyle=3D"display:inline"><u>=E2=80=8B</u></div></font><div style=3D"color:rg=
b(136,136,136);font-family:tahoma,sans-serif;font-size:13px;display:inline"=
><u>=E2=80=8BSecure Communications</u> MSc</div><span style=3D"color:rgb(13=
6,136,136);font-family:tahoma,sans-serif;font-size:13px">=C2=A0Student.</sp=
an><br style=3D"color:rgb(136,136,136);font-family:tahoma,sans-serif;font-s=
ize:13px"><font color=3D"#888888" face=3D"tahoma, sans-serif">Department of=
=C2=A0Electrical=C2=A0&amp; Computer Engineering.</font><br style=3D"color:=
rgb(136,136,136);font-family:tahoma,sans-serif;font-size:13px"><u style=3D"=
color:rgb(136,136,136);font-family:tahoma,sans-serif;font-size:13px">Yazd U=
niversity</u><span style=3D"color:rgb(136,136,136);font-family:tahoma,sans-=
serif;font-size:13px">.=C2=A0</span><br style=3D"color:rgb(136,136,136);fon=
t-family:tahoma,sans-serif;font-size:13px"><span style=3D"color:rgb(136,136=
,136);font-family:tahoma,sans-serif;font-size:13px">Islamic Republic of Ira=
n.</span></div></div></div>
</div></div>

--089e01182846482e5e052441cd3f--


From nobody Wed Nov 11 05:32:02 2015
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 979621ACD87 for <manet@ietfa.amsl.com>; Wed, 11 Nov 2015 05:32:01 -0800 (PST)
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 4neaDSdCE2iH for <manet@ietfa.amsl.com>; Wed, 11 Nov 2015 05:31:59 -0800 (PST)
Received: from ukmta2.baesystems.com (unknown [20.133.0.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CED381ACD8D for <manet@ietf.org>; Wed, 11 Nov 2015 05:31:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.20,275,1444690800"; d="scan'208";a="18304499"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta2.baesystems.com with ESMTP; 11 Nov 2015 13:31:39 +0000
X-IronPort-AV: E=Sophos;i="5.20,275,1444690800"; d="scan'208";a="119887926"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasmds017.greenlnk.net with ESMTP; 11 Nov 2015 13:31:39 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.152]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.03.0248.002; Wed, 11 Nov 2015 13:31:39 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Ahmad Haghighi <haghighi.ahmad@gmail.com>, "manet@ietf.org" <manet@ietf.org>
Thread-Topic: [manet] Find Sender of Route Reply
Thread-Index: AQHRHHDayekepuqihEiTNryky7X6IJ6Wzo1w
Date: Wed, 11 Nov 2015 13:31:38 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D6BAC1D7C@GLKXM0002V.GREENLNK.net>
References: <CAJVE_fUFEAY1nWGOW_7G=pBraTj+HeLBNuxK9B1PwEzeBb11+w@mail.gmail.com>
In-Reply-To: <CAJVE_fUFEAY1nWGOW_7G=pBraTj+HeLBNuxK9B1PwEzeBb11+w@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="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/qZYUXPCge3xFPVgICie7U4QQ07E>
Subject: Re: [manet] Find Sender of Route Reply
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Nov 2015 13:32:01 -0000

VGhlcmUgYXJlIHR3byBwb3RlbnRpYWwgY2hvaWNlczoNCg0KLSBSUkVRIGhhcyBhbiBpbnRlZ3Jp
dHkgY2hlY2sgdmFsdWUgdG8gaW5kaWNhdGUgdGhhdCBzb21lb25lIHRydXN0ZWQgY3JlYXRlZCBp
dCwgaWYgbm90IG5lY2Vzc2FyaWx5IHRoZSBkZXN0aW5hdGlvbi4gVGhhdCBzb21lb25lIG1pZ2h0
IGJlIGlkZW50aWZpYWJsZSBvciBub3QuDQotIFJSRVEgaGFzIGEgc2lnbmF0dXJlIHRoYXQgaW5k
aWNhdGVzIHRoYXQgdGhlIGRlc3RpbmF0aW9uIGNyZWF0ZWQgaXQuDQoNClVuZm9ydHVuYXRlbHks
IGFuIFJSRVEgdGhhdCBjaGFuZ2VzIGFzIGl0IGlzIGZvcndhcmRlZCAoYWdncmVnYXRpbmcgZGF0
YSBvZiBhbnkgc29ydCkgbWFrZXMgdGhlIHNlY29uZCBvcHRpb24gdHJpY2t5LCB1bmxlc3MgdGhl
cmXigJlzIHNvbWUgc29ydCBvZiBhZ2dyZWdhdGluZyBzaWduYXR1cmUgYXMgaXQgaXMgZm9yd2Fy
ZGVkLiBCdXQgSeKAmW0gbm90IGFuIGV4cGVydCBvbiB0aGUgbGF0dGVyLg0KDQpUaGUgbW9zdCB0
cml2aWFsIGNhc2Ugb2YgdGhlIGZvcm1lciBpcyBzaW1wbHkgdGhhdCBldmVyeW9uZSB0cnVzdGVk
IGhhcyBhIHNpbmdsZSBzaGFyZWQga2V5LiBUaGF0IGhhcyBvYnZpb3VzIGlzc3VlcyDigJMgYWx0
aG91Z2ggaXQgd2FzIGdvb2QgZW5vdWdoIHRoYXQgZW1ib2RpZWQgYXMgUkZDIDcxODMgd2UgY291
bGQgZ2V0IDcxODEgdGhyb3VnaCB0aGUgc3lzdGVtIChhcyBhIOKAnG11c3QgaW1wbGVtZW50LCBk
byBub3QgbmVlZCB0byB1c2XigJ0gbWluaW1hbCBjYXNlKS4gQWx0ZXJuYXRpdmVseSBzb21ldGhp
bmcgaWRlbnRpdHktYmFzZWQgKGUuZy4gZHJhZnQtaWV0Zi1tYW5ldC1pYnMpIGNvdWxkIGJlIHVz
ZWQsIHNvIHlvdSBrbm93IHdobyBjcmVhdGVkIHRoZSBtZXNzYWdlIHlvdSByZWNlaXZlZCwgYnV0
IHlvdSBhcmUgcmVseWluZyBvbiBhIGNoYWluIG9mIHRydXN0LCBob3AgYnkgaG9wLiBBdCB3aGlj
aCBwb2ludCB5b3UgbWlnaHQgYXMgd2VsbCBqdXN0IHNpZ24gcGFja2V0cyAoc2VlIFJGQyA3MTgy
KS4NCg0KQnV0IGluIGV2ZW4gdGhlIHdlYWtlc3QgY2FzZSAodGhlIHNpbmdsZSBzaGFyZWQga2V5
IHVzZWQgaG9wIGJ5IGhvcCkgdGhlcmUgaGFzIHRvIGJlIGEgZmFpbHVyZSBmb3IgdGhpbmdzIHRv
IGdvIHdyb25nIC0gZWl0aGVyIGxvc3Mgb2Yga2V5IChpbiB3aGljaCBjYXNlIGFsbCBiZXRzIGFy
ZSBvZmYpIG9yIHN1Ym9ybmluZyBvbmUgcm91dGVyICh3aG8gY2FuIGRvIHF1aXRlIGEgbG90IG9m
IGRhbWFnZSkuDQoNCkkgaGF2ZW4ndCByZWFkIHRoZSBsYXRlc3QgQU9EVnYyIGRyYWZ0IHlldCwg
YnV0IHRoaXMgc29ydCBvZiB0aGluZyBzaG91bGQgYmUgZGVzY3JpYmVkIGluIGl0cyBzZWN1cml0
eSBjb25zaWRlcmF0aW9ucyAtIHRoZSBwcmV2aW91cyBkcmFmdCB0aG91Z2ggZGlkbid0IGRpc2N1
c3MgdGhpcyBhcyBmYXIgYXMgSSByZWNhbGwuDQoNCi0tIA0KQ2hyaXN0b3BoZXIgRGVhcmxvdmUN
ClNlbmlvciBQcmluY2lwYWwgRW5naW5lZXINCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdl
bmNlDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KDQpUOiDCoCs0NCAoMCkxMjQ1IDI0MjE5NCDCoHwgwqBF
OiBjaHJpcy5kZWFybG92ZUBiYWVzeXN0ZW1zLmNvbQ0KDQpCQUUgU3lzdGVtcyBBcHBsaWVkIElu
dGVsbGlnZW5jZSwgQ2hlbG1zZm9yZCBUZWNobm9sb2d5IFBhcmssIEdyZWF0IEJhZGRvdywgQ2hl
bG1zZm9yZCwgRXNzZXggQ00yIDhITi4NCnd3dy5iYWVzeXN0ZW1zLmNvbS9haQ0KQkFFIFN5c3Rl
bXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UgTGltaXRlZA0KUmVnaXN0ZXJlZCBpbiBFbmdsYW5kICYg
V2FsZXMgTm86IDAxMzM3NDUxDQpSZWdpc3RlcmVkIE9mZmljZTogU3VycmV5IFJlc2VhcmNoIFBh
cmssIEd1aWxkZm9yZCwgU3VycmV5LCBHVTIgN1lQDQoNCg0KRnJvbTogbWFuZXQgW21haWx0bzpt
YW5ldC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQWhtYWQgSGFnaGlnaGkNClNlbnQ6
IDExIE5vdmVtYmVyIDIwMTUgMTE6MDUNClRvOiBtYW5ldEBpZXRmLm9yZw0KU3ViamVjdDogUmU6
IFttYW5ldF0gRmluZCBTZW5kZXIgb2YgUm91dGUgUmVwbHkNCg0KDQoqKiogV0FSTklORyAqKioN
ClRoaXMgbWVzc2FnZSBvcmlnaW5hdGVzIGZyb20gb3V0c2lkZSBvdXIgb3JnYW5pc2F0aW9uLCBl
aXRoZXIgZnJvbSBhbiBleHRlcm5hbCBwYXJ0bmVyIG9yIHRoZSBpbnRlcm5ldC4NCkNvbnNpZGVy
IGNhcmVmdWxseSB3aGV0aGVyIHlvdSBzaG91bGQgY2xpY2sgb24gYW55IGxpbmtzLCBvcGVuIGFu
eSBhdHRhY2htZW50cyBvciByZXBseS4NCkZvciBpbmZvcm1hdGlvbiByZWdhcmRpbmcgUmVkIEZs
YWdzIHRoYXQgeW91IGNhbiBsb29rIG91dCBmb3IgaW4gZW1haWxzIHlvdSByZWNlaXZlLCBjbGlj
ayBoZXJlLg0KSWYgeW91IGZlZWwgdGhlIGVtYWlsIGlzIHN1c3BpY2lvdXMsIHBsZWFzZSBmb2xs
b3cgdGhpcyBwcm9jZXNzLg0KKioqIFdBUk5JTkcgKioqDQpFWFRFUk5BTCBFTUFJTCAtLSBUaGlz
IG1lc3NhZ2Ugb3JpZ2luYXRlcyBmcm9tIG91dHNpZGUgb3VyIG9yZ2FuaXphdGlvbi4NCg0KVGhh
bmtzLiBJIHRoaW5rIHNvDQpCdXQgbXkgc3VwZXJ2aXNvciB3YW50cyBhbm90aGVyIHJlYXNvbiBm
b3IgdGhhdCEhIcKgDQoNCk9uIFdlZCwgTm92IDExLCAyMDE1IGF0IDEwOjUwIEFNLCBBaG1hZCBI
YWdoaWdoaSA8aGFnaGlnaGkuYWhtYWRAZ21haWwuY29tPiB3cm90ZToNClRoYW5rcy4gSSB0aGlu
ayBzbw0KQnV0IG15IHN1cGVydmlzb3Igd2FudHMgYW5vdGhlciByZWFzb24gZm9yIHRoYXQhISHC
oA0KDQpPbiBTdW4sIE5vdiA4LCAyMDE1IGF0IDg6MzcgUE0sIEhlbm5pbmcgUm9nZ2UgPGhyb2dn
ZUBnbWFpbC5jb20+IHdyb3RlOg0KSGksDQoNCmEgbWFsaWNpb3VzIG5vZGUgY291bGQgZWFzaWx5
IHByZXRlbmQgdG8gYmUgYSBkaWZmZXJlbnQgbm9kZS4uLiBvciB0cnkNCnRvICJmcmFtZSIgYSBk
aWZmZXJlbnQgbm9kZSBmdXJ0aGVyIGF3YXkuDQoNCldpdGhvdXQgYSBzb3VyY2Utc3BlY2lmaWMg
c2lnbmF0dXJlLCBob3cgZG8geW91IHdhbnQgdG8gYmUgc3VyZSB0aGF0IGENCmRhdGEgZmllbGQg
aXMgcmVsaWFibGU/DQoNCkhlbm5pbmcgUm9nZ2UNCg0KT24gRnJpLCBPY3QgMTYsIDIwMTUgYXQg
MTE6MjggQU0sIEFobWFkIEhhZ2hpZ2hpDQo8aGFnaGlnaGkuYWhtYWRAZ21haWwuY29tPiB3cm90
ZToNCj4gSGVsbG8NCj4gSSdtIHdvcmtpbmcgb24gTUFORVQgc2VjdXJpdHkgYW5kIEJsYWNraG9s
ZS9HcmF5aG9sZSBkZXRlY3Rpb24uDQo+IEkgaGF2ZSBhIHF1ZXN0aW9uLCBzbyBwbGVhc2UgaGVs
cCBtZSwgb3LCoCBJZiB5b3UgaGF2ZSBsaXR0bGUgdGltZSBhbmQgc28NCj4gY2FuJ3QgYW5zd2Vy
IG1lLCBwbGVhc2UgcmVmZXIgbWUgdG8gc29tZSBwZW9wbGUgb3IgYm9vayBmb3IgZmluZGluZyBt
eQ0KPiBhbnN3ZXIuIG15IHF1ZXN0aW9uIGlzOg0KPiBJbiBNQU5FVCAod2l0aCBEU1Igb3IgQU9E
Vikgd2hlbiBhIFJvdXRlIFJlcGx5IChSUkVQKSBwYWNrZXQgcmVjZWl2ZWQgYnkgdGhlDQo+IHNv
dXJjZSBub2RlLCB0aGUgc291cmNlIG5vZGUgY2FuIG5vdCBiZSBzdXJlIHdobyBpcyB0aGUgc2Vu
ZGVyIG9mIFJSRVAsIChpdA0KPiBpcyBhIGFzc3VtcHRpb24gaW4gYWxsIHBhcGVycykgc28gc291
cmNlIG5vZGUgKHRoZSBub2RlIHdoaWNoIGluaXRpYXRlZA0KPiBSb3V0ZSBEaXNjb3ZlcnkpIHNo
b3VsZCBkbyBzb21lIG9wZXJhdGlvbnMgZm9yIGRldGVjdGluZyBleGFjdCBhZGRyZXNzIG9mDQo+
IE1hbGljaW91cyBub2RlIChzZW5kZXIgb2YgbWFsaWNpb3VzIFJSRVApLg0KPiBCdXQgZS5nLiBp
biBEU1IgSGVhZGVyIHdlIGhhdmUgYSAiU291cmNlIEFkZHJlc3MiIGZpZWxkIHdoaWNoIGNhcnJp
ZXMNCj4gYWRkcmVzcyBvZiBzZW5kZXIuIG9yIGFsc28gaW4gSVAgaGVhZGVyIG9mIEFET1YgUlJF
UC4NCj4gSSBkb24ndCB1bmRlcnN0YW5kIHdoeSBzb3VyY2Ugbm9kZSBpcyAqbm90IHN1cmUqIGFi
b3V0IGlkZW50aXR5IG9mIHNlbmRlciBvZg0KPiBSUkVQPw0KPiBJIGRvbid0IGtub3cgdGhlIHJl
YXNvbiBvZiBhYm92ZSBhc3N1bXB0aW9uLg0KPg0KPiBMZXQgbWUgZXhwbGFpbiBteSBxdWVzdGlv
biBtb3JlIG9ibGl2aW91cy4NCj4gU291cmNlIG5vZGUsIHJlY2VpdmUgYSBtYWxpY2lvdXMgUlJF
UCwgdGhlIHNvdXJjZSBub2RlIHVzZSBpdCdzIHBhdGggZm9yDQo+IHNlbmRpbmcgcGFja2V0cy4g
QXMgZXhwZWN0ZWQgTWFsaWNpb3VzIG5vZGUgZHJvcHMgYWxsIHBhY2tldHMuDQo+IE9rLg0KPiBO
b3cgd2Ugd2FudCB0byBmaW5kIG1hbGljaW91cyBub2RlIChzZW5kZXIgb2YgUlJFUCksIElmIHZh
bHVlIG9mICJTb3VyY2UNCj4gQWRkcmVzcyIgV2FzIHJlbGlhYmxlLCB3ZSBiZSBhYmxlIHRvIGVh
c2lseSBmaW5kIG1hbGljaW91cyBub2RlIChzZW5kZXIgb2YNCj4gUlJFUCkuDQo+IEJ1dCBpbiBh
bGwgcGFwZXJzLCBhdXRob3JzIGVtcGxveXMgc29tZSBtZWNoYW5pc21zIGZvciBkZXRlY3Rpbmcg
bWFsaWNpb3VzDQo+IG5vZGUgKHNlbmRlciBvZiBSUkVQKS4gc28gd2UgY2FuIGNvbmNsdWRlIHZh
bHVlIG9mICJTb3VyY2UgYWRkcmVzcyIgZmllbGQgaXMNCj4gbm90IHJlbGlhYmxlLg0KPiBNeSBx
dWVzdGlvbiBpcywgd2h5PyB3aHkgc291cmNlIG5vZGUgY2FuIG5vdCB1c2UgdGhpcyBmaWVsZCBm
b3IgZGV0ZWN0aW5nDQo+IGFuZCByZW1vdmluZyBtYWxpY2lvdXMgbm9kZT8NCj4gT25lIGFuc3dl
ciBpcyBiZWNhdXNlIG9mIElQIFNwb29maW5nIGkuZSBtYWxpY2lvdXMgbm9kZSBjYW4gdXNlIGFu
b3RoZXINCj4gYWRkcmVzcyBhcyBzb3VyY2UgYWRkcmVzcw0KPiBidXQgdGhpcyBub3QgdGhlIG9u
bHkgcmVhc29uLCBJIG5lZWQgdG8gZmluZCBhbm90aGVyIHJlYXNvbiBmb3IgdGhhdA0KPg0KPiBJ
IGhhcmRseSBuZWVkIHRoZSBhbnN3ZXIuDQo+IFNvIHBsZWFzZSBndWlkZSBtZQ0KPiBUaGFua3MN
Cj4NCj4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gbWFuZXQgbWFpbGluZyBsaXN0DQo+IG1hbmV0QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQNCj4NCg0KDQoNCg0KLS0gDQpBaG1hZCBI
YWdoaWdoaS4NCuKAiw0K4oCLU2VjdXJlIENvbW11bmljYXRpb25zIE1TYw0KwqBTdHVkZW50Lg0K
RGVwYXJ0bWVudCBvZsKgRWxlY3RyaWNhbMKgJiBDb21wdXRlciBFbmdpbmVlcmluZy4NCllhemQg
VW5pdmVyc2l0eS7CoA0KSXNsYW1pYyBSZXB1YmxpYyBvZiBJcmFuLg0KDQoNCg0KDQotLSANCkFo
bWFkIEhhZ2hpZ2hpLg0K4oCLDQrigItTZWN1cmUgQ29tbXVuaWNhdGlvbnMgTVNjDQrCoFN0dWRl
bnQuDQpEZXBhcnRtZW50IG9mwqBFbGVjdHJpY2FswqAmIENvbXB1dGVyIEVuZ2luZWVyaW5nLg0K
WWF6ZCBVbml2ZXJzaXR5LsKgDQpJc2xhbWljIFJlcHVibGljIG9mIElyYW4uDQoqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KgpUaGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgYXJlIGNvbmZpZGVudGlhbCB0byB0aGUg
aW50ZW5kZWQKcmVjaXBpZW50IGFuZCBtYXkgYWxzbyBiZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJl
IG5vdCB0aGUgaW50ZW5kZWQKcmVjaXBpZW50IHBsZWFzZSBkZWxldGUgaXQgZnJvbSB5b3VyIHN5
c3RlbSBhbmQgbm90aWZ5IHRoZSBzZW5kZXIuCllvdSBzaG91bGQgbm90IGNvcHkgaXQgb3IgdXNl
IGl0IGZvciBhbnkgcHVycG9zZSBub3IgZGlzY2xvc2Ugb3IKZGlzdHJpYnV0ZSBpdHMgY29udGVu
dHMgdG8gYW55IG90aGVyIHBlcnNvbi4KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioK


From nobody Fri Nov 13 06:05:10 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 78B5F1A88A4; Fri, 13 Nov 2015 06:05:08 -0800 (PST)
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: 6.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151113140508.22543.80104.idtracker@ietfa.amsl.com>
Date: Fri, 13 Nov 2015 06:05:08 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/qCu-AoVnpmvZSY6qDRRva_rshgc>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-09.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: <https://mailarchive.ietf.org/arch/browse/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, 13 Nov 2015 14:05:08 -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           : Packet Sequence Number based directional airtime metric for OLSRv2
        Authors         : Henning Rogge
                          Emmanuel Baccelli
	Filename        : draft-ietf-manet-olsrv2-dat-metric-09.txt
	Pages           : 19
	Date            : 2015-11-13

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:
https://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-dat-metric-09


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 Nov 13 06:07:07 2015
Return-Path: <henning.rogge@fkie.fraunhofer.de>
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 EAFD51A88B2 for <manet@ietfa.amsl.com>; Fri, 13 Nov 2015 06:07:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.161
X-Spam-Level: 
X-Spam-Status: No, score=-0.161 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 TIfxBI1OOc13 for <manet@ietfa.amsl.com>; Fri, 13 Nov 2015 06:07:04 -0800 (PST)
Received: from a.mx.fkie.fraunhofer.de (mailguard.fkie.fraunhofer.de [IPv6:2001:638:401:102:1aa9:5ff:fe5f:7f22]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2DB51A88BD for <manet@ietf.org>; Fri, 13 Nov 2015 06:07:03 -0800 (PST)
Received: from rufsun5.fkie.fraunhofer.de ([128.7.2.5] helo=mailhost.fkie.fraunhofer.de) by a.mx.fkie.fraunhofer.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henning.rogge@fkie.fraunhofer.de>) id 1ZxF0I-0004FS-3Q for manet@ietf.org; Fri, 13 Nov 2015 15:07:02 +0100
Received: from mailserv2bcas.fkie.fraunhofer.de ([128.7.96.56] helo=mailserv2.fkie.fraunhofer.de) by mailhost.fkie.fraunhofer.de with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <henning.rogge@fkie.fraunhofer.de>) id 1ZxF0H-0004Wn-Vx for manet@ietf.org; Fri, 13 Nov 2015 15:07:01 +0100
Received: from [128.7.5.36] (128.7.5.36) by MAILSERV2BCAS.lorien.fkie.fgan.de (128.7.96.58) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 13 Nov 2015 15:07:01 +0100
To: <manet@ietf.org>
References: <20151113140508.22543.80104.idtracker@ietfa.amsl.com>
From: Henning Rogge <henning.rogge@fkie.fraunhofer.de>
Message-ID: <5645EE80.3040306@fkie.fraunhofer.de>
Date: Fri, 13 Nov 2015 15:06:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151113140508.22543.80104.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms050409080400000000020502"
X-Originating-IP: [128.7.5.36]
X-Virus-Scanned: yes (ClamAV 0.98.1/21060/Thu Nov 12 18:35:33 2015) by a.mx.fkie.fraunhofer.de
X-Scan-Signature: 2373b5e69b5e37e3efcc60d711afffcb
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/F6kpEdjoY5oiZSp5ch7uKPxdTJ4>
Subject: Re: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-09.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: <https://mailarchive.ietf.org/arch/browse/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, 13 Nov 2015 14:07:06 -0000

--------------ms050409080400000000020502
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi,

I updated the draft according to a comment from IANA...

the update just removes the IANA section (which is empty anyways).

Henning Rogge

--=20
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut f=FCr
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Fraunhofer Stra=DFe 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961,   Fax +49 228 9435 685
mailto:henning.rogge@fkie.fraunhofer.de http://www.fkie.fraunhofer.de


--------------ms050409080400000000020502
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
FGAwggQuMIIDFqADAgECAgIBDDANBgkqhkiG9w0BAQUFADBxMQswCQYDVQQGEwJERTEcMBoG
A1UEChMTRGV1dHNjaGUgVGVsZWtvbSBBRzEfMB0GA1UECxMWVC1UZWxlU2VjIFRydXN0IENl
bnRlcjEjMCEGA1UEAxMaRGV1dHNjaGUgVGVsZWtvbSBSb290IENBIDIwHhcNMDcxMjA1MTUx
ODU4WhcNMTkwNjMwMjM1OTU5WjBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2Zl
cjEhMB8GA1UECxMYRnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhv
ZmVyIFJvb3QgQ0EgMjAwNzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMM9Hsll
jVuIN/c+wSG2VN6wOlcbGhzumAh0AVpvtd82VytERc7zRhNldpWYVMeohRVuEqQX6AvhIacx
PSnd/6PWT9K0if1jStqrU+9ZBbRP4jsqkZnAy2VXgaMwk5AOyb39FTIyCKRIfFYF8rs2ieJI
wm9LkgwlRb6tPtTHAe2xyBK0MAhup29/eiCnu7TlNYBULBmP2UvAHatD+GEUlPuwHV23kexi
wJHRXt2nC7MtH2Y5GDyuBBTl0n022bLNpxOwzEWdVgRRcTM2XC9dUROeT0iQDpdaS3DbuXnZ
odaUyJLQpftgvy2tnnEAF4bA/UhmnRRMBU5M0XFEC9B6D7ECAwEAAaOB2TCB1jAfBgNVHSME
GDAWgBQxw3kbuvVT1xfgiXotF2wKsyudMzAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFC9F
Qh4xBYDVcNj4HVfLW3rVPZz3MBIGA1UdEwEB/wQIMAYBAf8CAQEwcAYDVR0fBGkwZzBloGOg
YYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9Eb3dubG9hZEFS
TC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwDQYJKoZIhvcN
AQEFBQADggEBABq3THo85d3CY7LehiVORWJM9PKPX13X5Y3ODtf1lOGLkzE2p5oj52fhUsFa
GNaZ4YBkOA9KNTNdZnoo3Dh/N3LNUnVuEI5sfYz3Ket3wrkZBdS3PWG66AUS1FBiU+8iVGL8
TQHDXtQNg3RpUdU8nqzbpCt8bYSW03FNz9UtcaOSxD9Vz5s9I3cHV+nIzh2XtjP7kZdglg/3
9t5vJZASqxlH1UQjrsGSNSi/KkNeD+oHXdJE0IWC4xK8R+osrfjwQVJ9Nroin3qgMu9LvPk6
B7Ypxn04XzVVfjjyP3yz7i1uIXhfuRPP795lgMgl9WYtVEqtztkuDjDPgDOnixly6kEwggTG
MIIDrqADAgECAgphHTMZAAAAAAADMA0GCSqGSIb3DQEBBQUAMGcxCzAJBgNVBAYTAkRFMRMw
EQYDVQQKEwpGcmF1bmhvZmVyMSEwHwYDVQQLExhGcmF1bmhvZmVyIENvcnBvcmF0ZSBQS0kx
IDAeBgNVBAMTF0ZyYXVuaG9mZXIgUm9vdCBDQSAyMDA3MB4XDTA3MTIxMjE0NDkzNVoXDTE5
MDYzMDIzNTk1OVowZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNV
BAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2Vy
IENBIDIwMDcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDCdBBRy3XRgfErNZ1a
gjqvkq7NAvyuyPsgdw7/aBIVkEmnZ3xoJF/6DiYaZT5KngkK04dPMxGKa1WiS02lT1Yb48d4
efijC95VRmSH2owPPU6JYS8JPppdvVW6leZy4Ta0sHWctee2+nQruSX38b6TucFwp/eWf0y8
i3XrsYFR7PzJ4XM75gWwUUvjsPVKCp/j2b8mJlBHTh4PHAOTxhWkT/avPKu9+FZ5SPluPsuw
aDecLbqla6lm26TkNrB2KPa4r92/seVnbDK1YnihgKUP3Tb4Aeb7rgHIUZ7ADWR4KQIjwsz+
/0BWGKpNrp3XMRF8D4KO9qInwd7kGd8Rzlf3AgMBAAGjggFyMIIBbjASBgNVHRMBAf8ECDAG
AQH/AgEAMB0GA1UdDgQWBBRPHa+Iym24qhwJ+cXREe1ZtJP6CzAOBgNVHQ8BAf8EBAMCAQYw
HwYDVR0jBBgwFoAUL0VCHjEFgNVw2PgdV8tbetU9nPcwdQYDVR0fBG4wbDBqoGigZoYxaHR0
cDovL2NybC5wa2kuZnJhdW5ob2Zlci5kZS9maGctcm9vdC1jYS0yMDA3LmNybIYxaHR0cDov
L2NybC5mcmF1bmhvZmVyLXBraS5kZS9maGctcm9vdC1jYS0yMDA3LmNybDCBkAYIKwYBBQUH
AQEEgYMwgYAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2Zo
Zy1yb290LWNhLTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVy
LXBraS5kZS9maGctcm9vdC1jYS0yMDA3LmNlcjANBgkqhkiG9w0BAQUFAAOCAQEAAHdsjDP5
7lcEJcrLiDnmTkykzsKWSxmGTbhEV8KVqRA37DBVMV/1nrW7tWtaoXfseksl2OFdQs3BQzhh
d8AO28iFf+ncgudyPZbmU48vc41LIy2bnA+I3jY2t0BLt/bELGLLhNzE3xRSYK/zXgBTB1ZJ
Bxsd5VV2/hdyd/vcXlx5P8Af8iCnf0SIjDE0+Pmvq2tjEwrGAHuJICdL89k12BjfLbo4woLF
FG8HyQvcKzogiTDSTNYu7FFalSiKLMFu4eUKVlDbtROEQLAxM+3XqVwmGgCMD6axCJK9HROt
86h4ZjOHoEu4hpgXzUKIVDuoyTljXCfXSManNHP+FlB4PDCCBagwggSQoAMCAQICCjQb63gA
AAAAuucwDQYJKoZIhvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9m
ZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5o
b2ZlciBVc2VyIENBIDIwMDcwHhcNMTAwMjAxMTE0MDM0WhcNMTYwMTMxMTE0MDM0WjBaMQsw
CQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjENMAsGA1UECxMERktJRTEPMA0GA1UE
CxMGUGVvcGxlMRYwFAYDVQQDEw1IZW5uaW5nIFJvZ2dlMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAxsgT9VRlhiEraBMqzI0g5nkPrSTp7j5TS/GTjKhiwmyr4hZ6VuurgDhT
Mulz7JRLZJMXJqEwjEBqPiHoGTEkgHl166P/lx2Or+j9XiHPYPxJjDOvRkWsrw+SWuiyacbr
oSTaDwz7nA38R27jXUSEKyi0SmhXYiBUIhh1/sEf/uDmi9oBhfj6gOjzM/vLM7NJqi70CE6U
Ma0Ph8R7H+rwYXhQlVWZzUnKvt6OJFJ4HLJvm6xHreiOrU97kPlwi3YQZUxC439gYPY0wmFE
mddNHOQ2fjtkoQYR9IgGWfP3vbQ8nXxUTIlOhS5x9sSaSU/pTYBJv7xYyjPrS9SIGl5bqQID
AQABo4ICYTCCAl0wDgYDVR0PAQH/BAQDAgbAMCsGA1UdEQQkMCKBIGhlbm5pbmcucm9nZ2VA
ZmtpZS5mcmF1bmhvZmVyLmRlMB0GA1UdDgQWBBQBfgSrsBkuX2mKj92DUbzW0i0r8zAfBgNV
HSMEGDAWgBRPHa+Iym24qhwJ+cXREe1ZtJP6CzB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8v
Y3JsLnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JshjFodHRwOi8vY3Js
LmZyYXVuaG9mZXItcGtpLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JsMIIBCgYIKwYBBQUHAQEE
gf0wgfowPgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11
c2VyLWNhLTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVyLXBr
aS5kZS9maGctdXNlci1jYS0yMDA3LmNlcjA7BggrBgEFBQcwAYYvaHR0cDovL2ZoZy11c2Vy
LWNhLTIwMDcub2NzcC5wa2kuZnJhdW5ob2Zlci5kZS8wOwYIKwYBBQUHMAGGL2h0dHA6Ly9m
aGctdXNlci1jYS0yMDA3Lm9jc3AuZnJhdW5ob2Zlci1wa2kuZGUvMBMGA1UdJQQMMAoGCCsG
AQUFBwMEMEQGA1UdIAQ9MDswOQYLKwYBBAGGClADAQEwKjAoBggrBgEFBQcCARYcaHR0cDov
L3BraS5mcmF1bmhvZmVyLmRlL2NwLzANBgkqhkiG9w0BAQUFAAOCAQEAOayOZLk0fQfhQ7I0
Qzn6KzuD4ixrzteSXITHu1RJ9/3xebplEm6YI/jwMLNFnfglXq+9I+rGjE/PxSOW6qK8CA31
DIo8qXhsxvvfF3yrFzHLzgyCcWdoxer2YvfKpJJfx0BKPGMvuAeTJp5L+PuWcGkvmDb/wRwA
JOfjNSokNdc27k3T+HTtXNsMrQzGWeIZFnK+pSQm/gWoDX7dNZE592/Dq8Rp83jedwl5CDBK
d0B6PDCM7vsEA9P+9L9/142H/1u6gYVNlR7GhsjCjUtsvpDZrMPNAd2wVAPoqiJ0WrfG/IEu
A5SySue+aeflbvMxDT1cWFnighiatWYbxwNmPDCCBbQwggScoAMCAQICCjQb6OgAAAAAuuYw
DQYJKoZIhvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAf
BgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBV
c2VyIENBIDIwMDcwHhcNMTAwMjAxMTE0MDM0WhcNMTYwMTMxMTE0MDM0WjBaMQswCQYDVQQG
EwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjENMAsGA1UECxMERktJRTEPMA0GA1UECxMGUGVv
cGxlMRYwFAYDVQQDEw1IZW5uaW5nIFJvZ2dlMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAosulW1xdX1xuHoX36m/A69SfDwvfsXmrYgI0qhSDgovRnWxT64dxCK2+vU+LskPn
o1m0RJTRbKgVo6O8j1/oU/OBVpi82DM97mWMUxYEpweKLdq+ROTZPUwFY8Qfz8EJ/cZjyrEB
Ys8NxAfRPFRWGd+BrkKNIvB9mr77PQa/rA+qEuNTmKY0Nbl4VAgwmGV37RFA2CLz38wc44ul
oJJKyYIA7CbIMae3kjUKy9YY55kyjgCY3c21/YV4ruOEwBu9yfEBmxx0E1P0/fB7G3+7d6kB
L+avP/QhwYmdJjFsarYSmUpXp9P1+c8HFTw5TYGULtj8f/FWQlmRjWDzSct4eQIDAQABo4IC
bTCCAmkwDgYDVR0PAQH/BAQDAgQwMCsGA1UdEQQkMCKBIGhlbm5pbmcucm9nZ2VAZmtpZS5m
cmF1bmhvZmVyLmRlMB0GA1UdDgQWBBRir/+EBYAUW6PBp6sYHmuGX1+fsjAfBgNVHSMEGDAW
gBRPHa+Iym24qhwJ+cXREe1ZtJP6CzB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8vY3JsLnBr
aS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JshjFodHRwOi8vY3JsLmZyYXVu
aG9mZXItcGtpLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JsMIIBCgYIKwYBBQUHAQEEgf0wgfow
PgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNh
LTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVyLXBraS5kZS9m
aGctdXNlci1jYS0yMDA3LmNlcjA7BggrBgEFBQcwAYYvaHR0cDovL2ZoZy11c2VyLWNhLTIw
MDcub2NzcC5wa2kuZnJhdW5ob2Zlci5kZS8wOwYIKwYBBQUHMAGGL2h0dHA6Ly9maGctdXNl
ci1jYS0yMDA3Lm9jc3AuZnJhdW5ob2Zlci1wa2kuZGUvMB8GA1UdJQQYMBYGCisGAQQBgjcK
AwQGCCsGAQUFBwMEMEQGA1UdIAQ9MDswOQYLKwYBBAGGClADAQEwKjAoBggrBgEFBQcCARYc
aHR0cDovL3BraS5mcmF1bmhvZmVyLmRlL2NwLzANBgkqhkiG9w0BAQUFAAOCAQEABPYI1Hbq
ips/0o+2m6Guww7ys/5F++qSYPq6w4CtlyuPupLZdKzEVuZ2n1fopZuEndTyCTq8DUJwZXKP
EIYKQGhkbFNy3IDaHB5VHaX0JsqV4DsgD6Xa2jnEBQpiy8RxMKP5mY5NRS4jO6J+bFjrMiKb
jDlzvJJxy6kqy8efjxH6RdMjGxQRcMS4EUTs7DRu38A81XEGaqqtjcwN3n3EvJUVcBzXn63B
mb4bgv1U6DYXFMSMcksssapmsdL0EPXKAWBRcswouetjRBXIFfu1xKFINtwyax6RCZycAEXd
dFC6j/3BVvi6iNFSE1VVQx+HQz1EhGBcp80W3qnIvoO1UjGCA4swggOHAgEBMHUwZzELMAkG
A1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29y
cG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2VyIENBIDIwMDcCCjQb63gAAAAA
uucwDQYJYIZIAWUDBAIBBQCgggHnMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTE1MTExMzE0MDcwMFowLwYJKoZIhvcNAQkEMSIEIFobySWyGJ9I2xQp0Y6s
dUhkbgLt39RQ6S0udUYoPc/1MGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCG
SAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYF
Kw4DAgcwDQYIKoZIhvcNAwICASgwgYQGCSsGAQQBgjcQBDF3MHUwZzELMAkGA1UEBhMCREUx
EzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBL
STEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2VyIENBIDIwMDcCCjQb6OgAAAAAuuYwgYYGCyqG
SIb3DQEJEAILMXegdTBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEhMB8G
A1UECxMYRnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVyIFVz
ZXIgQ0EgMjAwNwIKNBvo6AAAAAC65jANBgkqhkiG9w0BAQEFAASCAQC9GbjkyRhmsIL63UoM
Tt2Ds9PcdciIS+uHpJoWeEpNNc/f6oaxUIbSbIc9Mn3HsPpeAvhbEeANDTaY7eB9sNmr/5K4
zckjaKTkUviwzXYJe/HuAxrt0haUXA72Aa8cNuccDHoEHalc+KeyRMuY3csgVJMtHTDDv3xv
ciBYAkVtu/ILF7TYAdgNGWDeUhjBmzyC9iIHzn7mbWvdeiL9sPbkMhTLhT6T2nSHZswAqKU/
WEqFx45YaBCvbMiUzTfoL3sNIHj/J/n5vsItZG9l+ckWWa+Re+7mqSCbx5+yvnHuLWiGMjcH
/p2P3zFx0Ja+x1v5uLl67hf3lwTbMKdyM6RgAAAAAAAA
--------------ms050409080400000000020502--


From nobody Mon Nov 16 10:49:59 2015
Return-Path: <ratliffstan@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 9B8711A8745 for <manet@ietfa.amsl.com>; Mon, 16 Nov 2015 10:49:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 DD3wVT4M3fOS for <manet@ietfa.amsl.com>; Mon, 16 Nov 2015 10:49:57 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC4071A8741 for <manet@ietf.org>; Mon, 16 Nov 2015 10:49:56 -0800 (PST)
Received: by lbblt2 with SMTP id lt2so94612983lbb.3 for <manet@ietf.org>; Mon, 16 Nov 2015 10:49:54 -0800 (PST)
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=3vX6O6p2Ai3oINkkSmL6FYkO+jdnTgP9Np0hJsAGrNg=; b=EfFwbSGmfoPcLbCryv+5zEF9aq0rq56TxW5Mlc8x2fdnCHfCaJSP/+Q8fHuXRVg9Bv zlNtjRKGY4znndRUYVeTcWZui5GxqpqJGpfPUrAwfNON4b40PaQZD+KyPmN9xnBvpGgr Wh7w6/1izYOteNXNSaKiAtB2N1Q+V7eeitzpM1qNhJhzzTrL6P1KxvJ/IqvciTYcBeCK Q+GgtrvSBIvE1eJj7TONHW12wJGp/ZFoaowfgoibEQ+sppbJqOtGhSz9YauJn/I2v2h2 BAQZgz7UCK+ReMqtW50qntpf2L6OBRAerQWhLs4vv9SCplasWUBpmGWbephpULn64KZP bnPA==
MIME-Version: 1.0
X-Received: by 10.112.199.4 with SMTP id jg4mr18288172lbc.59.1447699794837; Mon, 16 Nov 2015 10:49:54 -0800 (PST)
Received: by 10.25.155.134 with HTTP; Mon, 16 Nov 2015 10:49:54 -0800 (PST)
Date: Mon, 16 Nov 2015 13:49:54 -0500
Message-ID: <CALtoyomz+M6AsrPbExOBiNW0F0T8DvHmtAL1qpaRRWvyqmNBZw@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: MANET IETF <manet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c324b00349cf0524ace0a6
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/M6W3tyq3Y6HO-5MvrkFg6OPd0aI>
Subject: [manet] Request for WGLC on DLEP-17
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Nov 2015 18:49:58 -0000

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

Hello Working Group,

DLEP-17 has been posted for a while now, without any discussion. Therefore,
the authors respectfully ask the group & chair for a WGLC on this document.

Regards,
Stan

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

<div dir=3D"ltr">Hello Working Group,=C2=A0<div><br></div><div>DLEP-17 has =
been posted for a while now, without any discussion. Therefore, the authors=
 respectfully ask the group &amp; chair for a WGLC on this document.=C2=A0<=
/div><div><br></div><div>Regards,<br>Stan</div><div><br></div></div>

--001a11c324b00349cf0524ace0a6--


From nobody Tue Nov 17 17:35:06 2015
Return-Path: <ietf@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 550B61B3707 for <manet@ietfa.amsl.com>; Tue, 17 Nov 2015 17:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 RQz8JOBXfDWW for <manet@ietfa.amsl.com>; Tue, 17 Nov 2015 17:35:01 -0800 (PST)
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 980691B3706 for <manet@ietf.org>; Tue, 17 Nov 2015 17:35:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 7C0CB240426; Tue, 17 Nov 2015 17:35:01 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.201.100] (115x125x248x70.ap115.ftth.ucom.ne.jp [115.125.248.70]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id E7FFF240380; Tue, 17 Nov 2015 17:35:00 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-D30D7446-9E5D-4E1E-B0C7-DB2441EB301D
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <ietf@thomasclausen.org>
X-Mailer: iPad Mail (13B143)
In-Reply-To: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net>
Date: Wed, 18 Nov 2015 10:35:00 +0900
Content-Transfer-Encoding: 7bit
Message-Id: <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net>
To: "Ratliff, Stanley" <sratliff@idirect.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/fE2rL2JR-liAUqtywfWTG1rZx4Y>
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Nov 2015 01:35:04 -0000

--Apple-Mail-D30D7446-9E5D-4E1E-B0C7-DB2441EB301D
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Dear all,

I have started looking through the recently updated draft-ietf-manet-aodvv2-=
12. A lot has changed, and I regret not to have had a blow-by-bow comeback t=
o the previous review comments  - would have made it a somewhat easier task t=
o check if all have been addressed or not.

But, I will work through it and produce a detailed review - but from my firs=
t quick read-through there're a couple of issue that jumped at me as worth b=
ringing forward on a more global level already.

The first relates to  how RREQs are forwarded -- or, more generally, are not=
.

The protocol currently talks about "message is regenerated" rather than "for=
warded". I have understood that this means that a RREQ is actually not an "e=
nd to end" entity, but is a "hop by hop" entity.=20

First, that is a curious design choice, is there any reason why this is so c=
onsidered?

Second, if a RREQ message is hop-by-hop only, then I do not think that the u=
se of the RFC5444 hop-limit/hop-count fields is appropriate.

Third, the statement in section 6.5 on the use of RFC6621 is incorrect in tw=
o ways: RFC6621 does specify how messages are *forwarded* (but, as discussed=
 above, you are not forwarding messages).

More seriously, this paragraph is incorrect:

> "Implementations MAY choose to employ techniques to reduce the number of m=
ulticast messages sent. Use of [RFC6621] in deployments is recommended. Empl=
oying [RFC6621] in a subset of the operational AODVv2 routers in a network, o=
r configuring different algorithms on different routers, will not cause inte=
roperability issues, but will reduce the effectiveness of the multicast redu=
ction scheme."


Different routers using different relay selection algorithms in the same net=
work will not *just* cause loss of efficiency, but *will* cause interoperabi=
lity issues.

For example if "router A" decides to suppress its message relaying because i=
t estimates that "router B" provides sufficient coverage - and conversely "r=
outer B" suppresses relaying for the same reason: neither A nor B would rela=
y, and so any routers reachable only via A and B would not be covered.

This is not a far-sought example: it can be as simple as A and B simply usin=
g self-selecting relay algorithms with different tie-breakers.

In short: I think that the whole message flooding/regeneration part requires=
 serious work.

The second issue is that I also suspect that there is some issue with buffer=
ing, or rather with how it is specified; starting in section 6.6, I am not s=
ure that leaving that as "a matter of policy at each router" is entirely rig=
ht.=20

Also on buffering, I am wondering if the "start delivering buffered packets"=
 conditions (penultimate paragraph in 6.6, and of course through the process=
ing sections) is sufficient; I suspect that the condition "When a valid rout=
e is installed" is not sufficient - that there are situations where a routin=
g table entry is installed, but the complete route is not available or is no=
t bidirectional?This obviously is related to RREP_Ack being hop-by-hop and n=
ot end-to-end....

Either way, the parts of the specification that relate to buffering contain a=
 mixture of normative and non-normative verbiage (a lot of "can" but also a l=
ot of MUST/SHOULD) which I think could do with a tightening up.=20

But....is buffering even something that should be specified by this document=
? It does not impact interoperability and it interferes substantially with t=
ransport and congestion control, and I am not sure that we understand the co=
nsequences (I am not convinced that the claims in the document on benefits t=
o TCP are substantiated or even true).

As I indicated, a complete review will follow, but I thought that these was a=
 global enough topics to call out and get engineered right.

Thomas

PS: I remain convinced that the security considerations section is insuffici=
ent ; I will try to articulate my thoughts on why that is, but for starters l=
ooking at the recently raised (by somebody else, the Chris replied) AODV sec=
urity questions would probably be helpful

> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote:
>=20
> Hello WG participants =E2=80=93
> =20
> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (=
DLEP). The co-authors and the chairs ask that you please take some time to r=
eview and comment on the new submissions.
> =20
> Regards,
> Stan
> =20
> =20
>=20
> _____________________________________________________
> This electronic message and any files transmitted with it contains
> information from iDirect, which may be privileged, proprietary
> and/or confidential. It is intended solely for the use of the individual
> or entity to whom they are addressed. If you are not the original
> recipient or the person responsible for delivering the email to the
> intended recipient, be advised that you have received this email
> in error, and that any use, dissemination, forwarding, printing, or
> copying of this email is strictly prohibited. If you received this email
> in error, please delete it and immediately notify the sender.
> _____________________________________________________
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-D30D7446-9E5D-4E1E-B0C7-DB2441EB301D
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>Dear all,</div><div><br></div><div>I h=
ave started looking through the recently updated&nbsp;draft-ietf-manet-aodvv=
2-12. A lot has changed, and I regret not to have had a blow-by-bow comeback=
 to the previous review comments &nbsp;- would have made it a somewhat easie=
r task to check if all have been addressed or not.</div><div><br></div><div>=
But, I will work through it and produce a detailed review - but from my firs=
t quick read-through there're a couple of issue that jumped at me as worth b=
ringing forward on a more global level already.</div><div><br></div><div>The=
 first relates to &nbsp;how RREQs are forwarded -- or, more generally, are n=
ot.</div><div><br></div><div>The protocol currently talks about "message is r=
egenerated" rather than "forwarded". I have understood that this means that a=
 RREQ is actually not an "end to end" entity, but is a "hop by hop" entity.&=
nbsp;</div><div><br></div><div>First, that is a curious design choice, is th=
ere any reason why this is so considered?</div><div><br></div><div>Second, i=
f a RREQ message is hop-by-hop only, then I do not think that the use of the=
 RFC5444 hop-limit/hop-count fields is appropriate.</div><div><br></div><div=
>Third, the statement in section 6.5 on the use of RFC6621 is incorrect in t=
wo ways: RFC6621 does specify how messages are *forwarded* (but, as discusse=
d above, you are not forwarding messages).</div><div><br></div><div>More ser=
iously, this paragraph <span style=3D"background-color: rgba(255, 255, 255, 0=
);">is incorrect</span>:</div><div><pre class=3D"newpage" style=3D"margin-to=
p: 0px; margin-bottom: 0px; page-break-before: always;"><font face=3D"UICTFo=
ntTextStyleTallBody"><span style=3D"white-space: normal; background-color: r=
gba(255, 255, 255, 0);"><br></span></font></pre><pre class=3D"newpage" style=
=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: always;"><blockq=
uote type=3D"cite"><font face=3D"UICTFontTextStyleTallBody"><span style=3D"w=
hite-space: normal; background-color: rgba(255, 255, 255, 0);">"Implementati=
ons MAY choose to employ techniques to reduce the number
   of multicast messages sent.  Use of [<a href=3D"https://tools.ietf.org/ht=
ml/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;">RFC6621</a=
>] in deployments is
   recommended.  Employing [<a href=3D"https://tools.ietf.org/html/rfc6621" t=
itle=3D"&quot;Simplified Multicast Forwarding&quot;">RFC6621</a>] in a subse=
t of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction scheme."</span></font=
><span style=3D"font-size: 19px; -webkit-text-size-adjust: auto;">
</span></blockquote></pre></div><div><br></div><div>Different routers using d=
ifferent relay selection algorithms in the same network will not *just* caus=
e loss of efficiency, but *will* cause interoperability issues.</div><div><b=
r></div><div>For example if "router A" decides to suppress its message relay=
ing because it estimates that "router B" provides sufficient coverage - and c=
onversely "router B" suppresses relaying for the same reason: neither A nor B=
 would relay, and so any routers reachable only via A and B would not be cov=
ered.</div><div><br></div><div>This is not a far-sought example: it can be a=
s simple as A and B simply using self-selecting relay algorithms with differ=
ent tie-breakers.</div><div><br></div><div>In short: I think that the whole m=
essage flooding/regeneration part requires serious work.</div><div><br></div=
><div><div><span style=3D"background-color: rgba(255, 255, 255, 0);">The sec=
ond issue is that I also suspect that there is some issue with buffering, or=
 rather with how it is specified; starting in section 6.6, I am not sure tha=
t leaving that as "a matter of policy at each router" is entirely right.&nbs=
p;</span></div><div><span style=3D"background-color: rgba(255, 255, 255, 0);=
"><br></span></div><div><span style=3D"background-color: rgba(255, 255, 255,=
 0);">Also on buffering, I am wondering if the "start delivering buffered pa=
ckets" conditions (penultimate paragraph in 6.6, and of course through the p=
rocessing sections) is sufficient; I suspect that the condition "When a vali=
d route is installed" is not sufficient - that there are situations where a r=
outing table entry is installed, but the complete route is not available or i=
s not bidirectional?This obviously is related to RREP_Ack being hop-by-hop a=
nd not end-to-end....</span></div><div><span style=3D"background-color: rgba=
(255, 255, 255, 0);"><br></span></div><div><span style=3D"background-color: r=
gba(255, 255, 255, 0);">Either way, the parts of the specification that rela=
te to buffering contain a mixture of normative and non-normative verbiage (a=
 lot of "can" but also a lot of MUST/SHOULD) which I think could do with a t=
ightening up.&nbsp;</span></div><div><span style=3D"background-color: rgba(2=
55, 255, 255, 0);"><br></span></div><div><span style=3D"background-color: rg=
ba(255, 255, 255, 0);">But....is buffering even something that should be spe=
cified by this document? It does not impact interoperability and it interfer=
es substantially with transport and congestion control, and I am not sure th=
at we understand the consequences (I am not convinced that the claims in the=
 document on benefits to TCP are substantiated or even true).</span></div><d=
iv><span style=3D"background-color: rgba(255, 255, 255, 0);"><br></span><div=
>As I indicated, a complete review will follow, but I thought that these was=
 a global enough topics to call out and get engineered right.</div></div></d=
iv><div><br></div><div>Thomas</div><div><br></div><div>PS: I remain convince=
d that the security considerations section is insufficient ; I will try to a=
rticulate my thoughts on why that is, but for starters looking at the recent=
ly raised (by somebody else, the Chris replied) AODV security questions woul=
d probably be helpful</div><div><div id=3D"AppleMailSignature"></div></div><=
div><br>On 10 Nov 2015, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sra=
tliff@idirect.net">sratliff@idirect.net</a>&gt; wrote:<br><br></div><blockqu=
ote type=3D"cite"><div>

<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]-->


<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello WG participants =E2=80=93 <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">The above referenced=
 drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (DLEP). The co-authors=
 and the chairs ask that you please take some
 time to review and comment on the new submissions. <o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p></s=
pan></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Regards,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Stan<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p></s=
pan></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br><span style=3D"font-size: 8pt; font-family: Arial, sans-serif; color: #0=
03366;">_____________________________________________________<br>This electr=
onic message and any files transmitted with it contains<br>information from i=
Direct, which may be privileged, proprietary<br>and/or confidential. It is i=
ntended solely for the use of the individual<br>or entity to whom they are a=
ddressed. If you are not the original<br>recipient or the person responsible=
 for delivering the email to the<br>intended recipient, be advised that you h=
ave received this email<br>in error, and that any use, dissemination, forwar=
ding, printing, or<br>copying of this email is strictly prohibited. If you r=
eceived this email<br>in error, please delete it and immediately notify the s=
ender.<br>_____________________________________________________</span>

</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-D30D7446-9E5D-4E1E-B0C7-DB2441EB301D--


From nobody Wed Nov 18 00:50:05 2015
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 BD6F71B2A36 for <manet@ietfa.amsl.com>; Wed, 18 Nov 2015 00:49:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 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, J_CHICKENPOX_52=0.6, MIME_QP_LONG_LINE=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 o-TclIF2hk_e for <manet@ietfa.amsl.com>; Wed, 18 Nov 2015 00:49:56 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F6DF1B2A50 for <manet@ietf.org>; Wed, 18 Nov 2015 00:49:55 -0800 (PST)
Received: by wmec201 with SMTP id c201so62504616wme.1 for <manet@ietf.org>; Wed, 18 Nov 2015 00:49:53 -0800 (PST)
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=L+7hhav+siwXXPxeFKvUxG11lxq4C1Jw7uyRXA67qWk=; b=G7o8PXPISZxCgVs46V/BIydM0hMuM+OhgKDEgUqBN93hc1lTs71QOuf2jSuz4b05n/ iM6xwW4uSKRQF7tWJm8XIdZCUq1QDUu8LeNYH4L6RxFmXNWZxVXN8r0d+DrBX+dwUBI4 LourV27ZNeXdRUTROPSVPfg+mCFvWICLk6juob+Q3Fd7tXblYh24Os1rq71xZJD2oSFy YPiOKmyf3rLrNFHwUNm6oVDAN4YtRhdOvbg6txntYNw+oHnjnFc7Wsxax+HAkVYegw9U UBmrdPP0+gtWIQrWAdT+96gqFH0iio9UptwSqeJ6WlqtchBU8VFddQpLuT2ZG2uVIjZk TVfg==
X-Received: by 10.194.185.173 with SMTP id fd13mr499237wjc.54.1447836593802; Wed, 18 Nov 2015 00:49:53 -0800 (PST)
Received: from [192.168.1.112] (static-84-9-19-92.vodafonexdsl.co.uk. [84.9.19.92]) by smtp.gmail.com with ESMTPSA id gl4sm1696466wjd.17.2015.11.18.00.49.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Nov 2015 00:49:52 -0800 (PST)
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org>
Content-Type: multipart/alternative; boundary=Apple-Mail-DEC2A24A-5215-44A9-9328-EA4593ECBC8A
Content-Transfer-Encoding: 7bit
Message-Id: <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com>
X-Mailer: iPhone Mail (13B143)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Wed, 18 Nov 2015 08:49:50 +0000
To: Thomas Clausen <ietf@thomasclausen.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/dbZU6tW6QjvG5AVow9M3KG-ycCE>
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Nov 2015 08:49:59 -0000

--Apple-Mail-DEC2A24A-5215-44A9-9328-EA4593ECBC8A
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

I've not had time to look at either yet, though I hope to review DLEP very s=
oon.

But this has made me think about the RFC 6621 reference in AODVv2. It's alwa=
ys been clear this has been rather a throwaway comment that needed thought, b=
ut until now I hadn't really given it any.

And it doesn't work. RFC 6621 is fundamentally unusable here. Let's consider=
 each on turn.=20

AODVv2 is in the RFC 5444 structure. As has been noted on many occasions, AO=
VDVv2 gets to use messages, but packets are not in its competence.

RFC 6621 is about packets. But not even RFC 5444 packets but IP packets. It'=
s about whether or not to forward them. But RFC 5444 packets aren't just not=
 forwarded in unchanged IP packets, they aren't even forwarded at all. They a=
re each a single hop construct, and if a message is forwarded (which is by t=
he routing protocol, as far as RFC 5444 is concerned, it's a new message) it=
 will be in a new packet, with possibly new companions.

If AODVv2 wants to use a more efficient flooding process, it needs one at th=
e message level. Now an example of that exists - the mechanism on RFC 7181. U=
nfortunately we didn't break that out as a separate draft (we would have lik=
ed to, but there were reasons we didn't).

And even if (by reference or other means) it were used - or some related mec=
hanism such as a CDS - that processing/forwarding mechanism assumes you have=
 defined MPRs (or similarly, that you have defined a CDS). And that needs a l=
ocal exchange of information, such as NHDP's HELLO messages (and the rest of=
 NHDP) augmented with RFC 7181's MPR TLV (though only the flooding bit is ne=
eded).

In other words, taking some real work to define. And also raising a question=
 for the WG - why do we want a reactive protocol? The main attraction as I s=
ee it is the "if you're not doing anything, you're not transmitting" propert=
y. Which adding this voids. Of course maybe the WG doesn't value that. Or it=
 is acceptable as an option. But if so it needs to be an option that all rou=
ters use, or none. And if all, compatibly. (MPR flooding allows different MP=
R selection algorithms - but only as long as they satisfy the fundamental MP=
R algorithm properties.)

In short, RFC 6621 must go. The alternative is nothing, or significant work.=


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

> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote:
>=20
> Dear all,
>=20
> I have started looking through the recently updated draft-ietf-manet-aodvv=
2-12. A lot has changed, and I regret not to have had a blow-by-bow comeback=
 to the previous review comments  - would have made it a somewhat easier tas=
k to check if all have been addressed or not.
>=20
> But, I will work through it and produce a detailed review - but from my fi=
rst quick read-through there're a couple of issue that jumped at me as worth=
 bringing forward on a more global level already.
>=20
> The first relates to  how RREQs are forwarded -- or, more generally, are n=
ot.
>=20
> The protocol currently talks about "message is regenerated" rather than "f=
orwarded". I have understood that this means that a RREQ is actually not an "=
end to end" entity, but is a "hop by hop" entity.=20
>=20
> First, that is a curious design choice, is there any reason why this is so=
 considered?
>=20
> Second, if a RREQ message is hop-by-hop only, then I do not think that the=
 use of the RFC5444 hop-limit/hop-count fields is appropriate.
>=20
> Third, the statement in section 6.5 on the use of RFC6621 is incorrect in t=
wo ways: RFC6621 does specify how messages are *forwarded* (but, as discusse=
d above, you are not forwarding messages).
>=20
> More seriously, this paragraph is incorrect:
>=20
>> "Implementations MAY choose to employ techniques to reduce the number of m=
ulticast messages sent. Use of [RFC6621] in deployments is recommended. Empl=
oying [RFC6621] in a subset of the operational AODVv2 routers in a network, o=
r configuring different algorithms on different routers, will not cause inte=
roperability issues, but will reduce the effectiveness of the multicast redu=
ction scheme."
>=20
>=20
> Different routers using different relay selection algorithms in the same n=
etwork will not *just* cause loss of efficiency, but *will* cause interopera=
bility issues.
>=20
> For example if "router A" decides to suppress its message relaying because=
 it estimates that "router B" provides sufficient coverage - and conversely "=
router B" suppresses relaying for the same reason: neither A nor B would rel=
ay, and so any routers reachable only via A and B would not be covered.
>=20
> This is not a far-sought example: it can be as simple as A and B simply us=
ing self-selecting relay algorithms with different tie-breakers.
>=20
> In short: I think that the whole message flooding/regeneration part requir=
es serious work.
>=20
> The second issue is that I also suspect that there is some issue with buff=
ering, or rather with how it is specified; starting in section 6.6, I am not=
 sure that leaving that as "a matter of policy at each router" is entirely r=
ight.=20
>=20
> Also on buffering, I am wondering if the "start delivering buffered packet=
s" conditions (penultimate paragraph in 6.6, and of course through the proce=
ssing sections) is sufficient; I suspect that the condition "When a valid ro=
ute is installed" is not sufficient - that there are situations where a rout=
ing table entry is installed, but the complete route is not available or is n=
ot bidirectional?This obviously is related to RREP_Ack being hop-by-hop and n=
ot end-to-end....
>=20
> Either way, the parts of the specification that relate to buffering contai=
n a mixture of normative and non-normative verbiage (a lot of "can" but also=
 a lot of MUST/SHOULD) which I think could do with a tightening up.=20
>=20
> But....is buffering even something that should be specified by this docume=
nt? It does not impact interoperability and it interferes substantially with=
 transport and congestion control, and I am not sure that we understand the c=
onsequences (I am not convinced that the claims in the document on benefits t=
o TCP are substantiated or even true).
>=20
> As I indicated, a complete review will follow, but I thought that these wa=
s a global enough topics to call out and get engineered right.
>=20
> Thomas
>=20
> PS: I remain convinced that the security considerations section is insuffi=
cient ; I will try to articulate my thoughts on why that is, but for starter=
s looking at the recently raised (by somebody else, the Chris replied) AODV s=
ecurity questions would probably be helpful
>=20
>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote:
>>=20
>> Hello WG participants =E2=80=93
>> =20
>> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16=
 (DLEP). The co-authors and the chairs ask that you please take some time to=
 review and comment on the new submissions.
>> =20
>> Regards,
>> Stan
>> =20
>> =20
>>=20
>> _____________________________________________________
>> This electronic message and any files transmitted with it contains
>> information from iDirect, which may be privileged, proprietary
>> and/or confidential. It is intended solely for the use of the individual
>> or entity to whom they are addressed. If you are not the original
>> recipient or the person responsible for delivering the email to the
>> intended recipient, be advised that you have received this email
>> in error, and that any use, dissemination, forwarding, printing, or
>> copying of this email is strictly prohibited. If you received this email
>> in error, please delete it and immediately notify the sender.
>> _____________________________________________________
>> _______________________________________________
>> 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-DEC2A24A-5215-44A9-9328-EA4593ECBC8A
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>I've not had time to look at either ye=
t, though I hope to review DLEP very soon.</div><div><br></div><div>But this=
 has made me think about the RFC 6621 reference in AODVv2. It's always been c=
lear this has been rather a throwaway comment that needed thought, but until=
 now I hadn't really given it any.</div><div><br></div><div>And it doesn't w=
ork. RFC 6621 is fundamentally unusable here. Let's consider each on turn.&n=
bsp;</div><div><br></div><div>AODVv2 is in the RFC 5444 structure. As has be=
en noted on many occasions, AOVDVv2 gets to use messages, but packets are no=
t in its competence.</div><div><br></div><div>RFC 6621 is about packets. But=
 not even RFC 5444 packets but IP packets. It's about whether or not to forw=
ard them. But RFC 5444 packets aren't just not forwarded in unchanged IP pac=
kets, they aren't even forwarded at all. They are each a single hop construc=
t, and if a message is forwarded (which is by the routing protocol, as far a=
s RFC 5444 is concerned, it's a new message) it will be in a new packet, wit=
h possibly new companions.</div><div><br></div><div>If AODVv2 wants to use a=
 more efficient flooding process, it needs one at the message level. Now an e=
xample of that exists - the mechanism on RFC 7181. Unfortunately we didn't b=
reak that out as a separate draft (we would have liked to, but there were re=
asons we didn't).</div><div><br></div><div>And even if (by reference or othe=
r means) it were used - or some related mechanism such as a CDS - that proce=
ssing/forwarding mechanism assumes you have defined MPRs (or similarly, that=
 you have defined a CDS). And that needs a local exchange of information, su=
ch as NHDP's HELLO messages (and the rest of NHDP) augmented with RFC 7181's=
 MPR TLV (though only the flooding bit is needed).</div><div><br></div><div>=
In other words, taking some real work to define. And also raising a question=
 for the WG - why do we want a reactive protocol? The main attraction as I s=
ee it is the "if you're not doing anything, you're not transmitting" propert=
y. Which adding this voids. Of course maybe the WG doesn't value that. Or it=
 is acceptable as an option. But if so it needs to be an option that all rou=
ters use, or none. And if all, compatibly. (MPR flooding allows different MP=
R selection algorithms - but only as long as they satisfy the fundamental MP=
R algorithm properties.)</div><div><br></div><div>In short, RFC 6621 must go=
. The alternative is nothing, or significant work.<br><br><div>-- &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"mailt=
o:chris@mnemosyne.demon.co.uk">chris@mnemosyne.demon.co.uk</a> (home)</div><=
/div></div><div><br>On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a href=3D"=
mailto:ietf@thomasclausen.org">ietf@thomasclausen.org</a>&gt; wrote:<br><br>=
</div><blockquote type=3D"cite"><div>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"><di=
v>Dear all,</div><div><br></div><div>I have started looking through the rece=
ntly updated&nbsp;draft-ietf-manet-aodvv2-12. A lot has changed, and I regre=
t not to have had a blow-by-bow comeback to the previous review comments &nb=
sp;- would have made it a somewhat easier task to check if all have been add=
ressed or not.</div><div><br></div><div>But, I will work through it and prod=
uce a detailed review - but from my first quick read-through there're a coup=
le of issue that jumped at me as worth bringing forward on a more global lev=
el already.</div><div><br></div><div>The first relates to &nbsp;how RREQs ar=
e forwarded -- or, more generally, are not.</div><div><br></div><div>The pro=
tocol currently talks about "message is regenerated" rather than "forwarded"=
. I have understood that this means that a RREQ is actually not an "end to e=
nd" entity, but is a "hop by hop" entity.&nbsp;</div><div><br></div><div>Fir=
st, that is a curious design choice, is there any reason why this is so cons=
idered?</div><div><br></div><div>Second, if a RREQ message is hop-by-hop onl=
y, then I do not think that the use of the RFC5444 hop-limit/hop-count field=
s is appropriate.</div><div><br></div><div>Third, the statement in section 6=
.5 on the use of RFC6621 is incorrect in two ways: RFC6621 does specify how m=
essages are *forwarded* (but, as discussed above, you are not forwarding mes=
sages).</div><div><br></div><div>More seriously, this paragraph <span style=3D=
"background-color: rgba(255, 255, 255, 0);">is incorrect</span>:</div><div><=
pre class=3D"newpage" style=3D"margin-top: 0px; margin-bottom: 0px; page-bre=
ak-before: always;"><font face=3D"UICTFontTextStyleTallBody"><span style=3D"=
white-space: normal; background-color: rgba(255, 255, 255, 0);"><br></span><=
/font></pre><pre class=3D"newpage" style=3D"margin-top: 0px; margin-bottom: 0=
px; page-break-before: always;"><blockquote type=3D"cite"><font face=3D"UICT=
FontTextStyleTallBody"><span style=3D"white-space: normal; background-color:=
 rgba(255, 255, 255, 0);">"Implementations MAY choose to employ techniques t=
o reduce the number
   of multicast messages sent.  Use of [<a href=3D"https://tools.ietf.org/ht=
ml/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;">RFC6621</a=
>] in deployments is
   recommended.  Employing [<a href=3D"https://tools.ietf.org/html/rfc6621" t=
itle=3D"&quot;Simplified Multicast Forwarding&quot;">RFC6621</a>] in a subse=
t of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction scheme."</span></font=
><span style=3D"font-size: 19px; -webkit-text-size-adjust: auto;">
</span></blockquote></pre></div><div><br></div><div>Different routers using d=
ifferent relay selection algorithms in the same network will not *just* caus=
e loss of efficiency, but *will* cause interoperability issues.</div><div><b=
r></div><div>For example if "router A" decides to suppress its message relay=
ing because it estimates that "router B" provides sufficient coverage - and c=
onversely "router B" suppresses relaying for the same reason: neither A nor B=
 would relay, and so any routers reachable only via A and B would not be cov=
ered.</div><div><br></div><div>This is not a far-sought example: it can be a=
s simple as A and B simply using self-selecting relay algorithms with differ=
ent tie-breakers.</div><div><br></div><div>In short: I think that the whole m=
essage flooding/regeneration part requires serious work.</div><div><br></div=
><div><div><span style=3D"background-color: rgba(255, 255, 255, 0);">The sec=
ond issue is that I also suspect that there is some issue with buffering, or=
 rather with how it is specified; starting in section 6.6, I am not sure tha=
t leaving that as "a matter of policy at each router" is entirely right.&nbs=
p;</span></div><div><span style=3D"background-color: rgba(255, 255, 255, 0);=
"><br></span></div><div><span style=3D"background-color: rgba(255, 255, 255,=
 0);">Also on buffering, I am wondering if the "start delivering buffered pa=
ckets" conditions (penultimate paragraph in 6.6, and of course through the p=
rocessing sections) is sufficient; I suspect that the condition "When a vali=
d route is installed" is not sufficient - that there are situations where a r=
outing table entry is installed, but the complete route is not available or i=
s not bidirectional?This obviously is related to RREP_Ack being hop-by-hop a=
nd not end-to-end....</span></div><div><span style=3D"background-color: rgba=
(255, 255, 255, 0);"><br></span></div><div><span style=3D"background-color: r=
gba(255, 255, 255, 0);">Either way, the parts of the specification that rela=
te to buffering contain a mixture of normative and non-normative verbiage (a=
 lot of "can" but also a lot of MUST/SHOULD) which I think could do with a t=
ightening up.&nbsp;</span></div><div><span style=3D"background-color: rgba(2=
55, 255, 255, 0);"><br></span></div><div><span style=3D"background-color: rg=
ba(255, 255, 255, 0);">But....is buffering even something that should be spe=
cified by this document? It does not impact interoperability and it interfer=
es substantially with transport and congestion control, and I am not sure th=
at we understand the consequences (I am not convinced that the claims in the=
 document on benefits to TCP are substantiated or even true).</span></div><d=
iv><span style=3D"background-color: rgba(255, 255, 255, 0);"><br></span><div=
>As I indicated, a complete review will follow, but I thought that these was=
 a global enough topics to call out and get engineered right.</div></div></d=
iv><div><br></div><div>Thomas</div><div><br></div><div>PS: I remain convince=
d that the security considerations section is insufficient ; I will try to a=
rticulate my thoughts on why that is, but for starters looking at the recent=
ly raised (by somebody else, the Chris replied) AODV security questions woul=
d probably be helpful</div><div><div id=3D"AppleMailSignature"></div></div><=
div><br>On 10 Nov 2015, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sra=
tliff@idirect.net">sratliff@idirect.net</a>&gt; wrote:<br><br></div><blockqu=
ote type=3D"cite"><div>


<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]-->


<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello WG participants =E2=80=93 <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">The above referenced=
 drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (DLEP). The co-authors=
 and the chairs ask that you please take some
 time to review and comment on the new submissions. <o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p></s=
pan></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Regards,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Stan<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p></s=
pan></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br><span style=3D"font-size: 8pt; font-family: Arial, sans-serif; color: #0=
03366;">_____________________________________________________<br>This electr=
onic message and any files transmitted with it contains<br>information from i=
Direct, which may be privileged, proprietary<br>and/or confidential. It is i=
ntended solely for the use of the individual<br>or entity to whom they are a=
ddressed. If you are not the original<br>recipient or the person responsible=
 for delivering the email to the<br>intended recipient, be advised that you h=
ave received this email<br>in error, and that any use, dissemination, forwar=
ding, printing, or<br>copying of this email is strictly prohibited. If you r=
eceived this email<br>in error, please delete it and immediately notify the s=
ender.<br>_____________________________________________________</span>

</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></blockquote><blo=
ckquote type=3D"cite"><div><span>___________________________________________=
____</span><br><span>manet mailing list</span><br><span><a href=3D"mailto:ma=
net@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></body></html>=

--Apple-Mail-DEC2A24A-5215-44A9-9328-EA4593ECBC8A--


From nobody Thu Nov 19 05:09:50 2015
Return-Path: <rja.lists@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 220D61AD0B1 for <manet@ietfa.amsl.com>; Thu, 19 Nov 2015 05:08:07 -0800 (PST)
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 SLBkTHX7G-_1 for <manet@ietfa.amsl.com>; Thu, 19 Nov 2015 05:08:04 -0800 (PST)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 830EC1AD0AD for <manet@ietf.org>; Thu, 19 Nov 2015 05:08:04 -0800 (PST)
Received: by ykfs79 with SMTP id s79so107420786ykf.1 for <manet@ietf.org>; Thu, 19 Nov 2015 05:08:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=hUFrBnVQLUFIblqQj0aOHMi0pRVzRrMukKbf+OIEw60=; b=yJcFE6pDyfNjiBNM0K1QumHab6vr8ktulypAeAe+xMlUgQzpIWMtl6vNv2c6ePrOj5 RYbaob+3Mub0ZM23CACgbXvISIJUMJjLTrqZrFmrQMqegrrt/KngLqehTLMGeBbdZcRF C1+9ACrHOmob6/wmCEQTTP3yx2GO0k511oC9ZXRM6GqcNIkFD69lblHpalxFhxl+guAM iB5SMr0fUN9DXL05h/s8oXnwPoMSowPaYpAXi6rkNJccke3fF1wpBc5yJIqyVRFoPAUw mKZ+phFO3Q8lyzqtdLETracXEAF8XONVtzbBa7kbndhi9NQLvAGW+3IKtyaVtQ7UgRbp OkYg==
X-Received: by 10.129.156.79 with SMTP id t76mr7218148ywg.71.1447938483679; Thu, 19 Nov 2015 05:08:03 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id c67sm7502754ywe.31.2015.11.19.05.08.03 for <manet@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Nov 2015 05:08:03 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <047F7B99-7220-4E19-8E31-02ED64470986@gmail.com>
Date: Thu, 19 Nov 2015 08:08:04 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/vq57ng9Zyhy89q6LZz9OCCRHiSg>
Subject: [manet] DLEP-17
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Nov 2015 13:08:07 -0000

Stan,

I regret that circumstances beyond my control have delayed 
my looking at this revision. I hope to be able to review 
this document this weekend and post any comments before
(US) Thanksgiving.


Yours,

Ran Atkinson




From nobody Thu Nov 19 07:03:31 2015
Return-Path: <rick@tropicalstormsoftware.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 E124D1B2B1B for <manet@ietfa.amsl.com>; Thu, 19 Nov 2015 07:03:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 DjPL--aXVx9D for <manet@ietfa.amsl.com>; Thu, 19 Nov 2015 07:03:23 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFC921B2AFC for <manet@ietf.org>; Thu, 19 Nov 2015 07:03:22 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Thu, 19 Nov 2015 15:02:57 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: manet IETF <manet@ietf.org>
Thread-Topic: New individual draft
Thread-Index: AdEi21+JPQ5qlf7ETd+idX8apPnwrQ==
Date: Thu, 19 Nov 2015 15:02:56 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8AF5D1E@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/9ynQpybyNr7sH5_KqRb01B92rS8>
Subject: [manet] New individual 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: <https://mailarchive.ietf.org/arch/browse/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, 19 Nov 2015 15:03:29 -0000

Hi All,=0A=
=0A=
I have just submitted a new individual draft: DLEP Destination Service =0A=
Announcement (https://www.ietf.org/id/draft-taylor-manet-dlep-dsa-00.txt)=
=0A=
=0A=
This is an extension to DLEP, and so should probably wait for DLEP to =0A=
progress, but I am asking for working group adoption.=0A=
=0A=
I understand that the WG is not taking on any further tasks before the =0A=
current outstanding tasks complete, so can I request everyone interested =
=0A=
please review DLEP-17?=0A=
=0A=
Many thanks=0A=
=0A=
Rick Taylor=0A=


From nobody Thu Nov 19 08:09:11 2015
Return-Path: <vmercieca0@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 CC41B1B2C1E for <manet@ietfa.amsl.com>; Thu, 19 Nov 2015 08:09:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.149
X-Spam-Level: 
X-Spam-Status: No, score=-0.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, J_CHICKENPOX_52=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 Ru5zmZJDBvXe for <manet@ietfa.amsl.com>; Thu, 19 Nov 2015 08:09:05 -0800 (PST)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97B491B2BF9 for <manet@ietf.org>; Thu, 19 Nov 2015 08:09:04 -0800 (PST)
Received: by lbblt2 with SMTP id lt2so46547808lbb.3 for <manet@ietf.org>; Thu, 19 Nov 2015 08:09:02 -0800 (PST)
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 :content-type; bh=AHpNWs3RB4XpXDEELRL/tsXP3sllW0Urqc4Rflp1BMs=; b=JalsqoxIe2BVcdyNPQrAUnKVgWY/+1XBe+eHJ3/Jn34ji/idIeB4UOuW+xaQKgwriO yoJQ0MOOrDNUKDXJ/mmnab50i9oV2sd8yLnyN9Ghy44vk2DZFrA26aS6d7KNWtlbfhDq wBEwU0/TwI08Gvgba45PeClyZrvrMbtu1DckFX9vic04tyQc1tBQzQ5JnPXkUlXzeppq 6k78sGRS7aHaRWrw4K+uLsAwo4PMn8wM0pOMoCHqBBQEOXdv/nb5jrLnzi0fjKUgI3YB OfkC//f6VUF5nvpd8Fvva5h2M/9qx1bZjMzmQ6+Yw3bd5lSduosXHJ7ZXuMajG4b2aId vNLw==
MIME-Version: 1.0
X-Received: by 10.112.12.73 with SMTP id w9mr3762221lbb.36.1447949342674; Thu, 19 Nov 2015 08:09:02 -0800 (PST)
Received: by 10.112.85.234 with HTTP; Thu, 19 Nov 2015 08:09:02 -0800 (PST)
In-Reply-To: <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com>
Date: Thu, 19 Nov 2015 16:09:02 +0000
Message-ID: <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com>
From: Victoria Mercieca <vmercieca0@gmail.com>
To: manet <manet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c39b663918b20524e6fa77
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/PzkcKPQVeeTw-7Bmq46HPMjy88o>
Subject: [manet] Fwd: draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Nov 2015 16:09:10 -0000

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

Hi Thomas and Christopher,

Thank you for your comments.  If I may address just one point for starters
- regeneration vs forwarding. We use the term regeneration since forwarding
seems inappropriate when the message content changes at each hop.

The changes we make to the message content are:

1) We change the metric so that each router along the path learns a route
from the message, with the metric associated with the path up to that point
2) AckReq only applies between hops, so needs to be removed at each hop,
and a new AckReq element may need to be added for the next hop.
3) ValidityTime could potentially be added by any intermediate router that
wishes to limit the time it will forward packets on the route.
4) Stripping out Unreachable Addresses from RERR which did not affect our
route set.

Can we really use the term "forwarding" if we are changing the metric
value, adding a validity time, adding/removing AckReq or removing addresses
and their associated TLVs?

Further, in reply to the comment about use of the msg-hop-count and
msg-hop-limit fields, I think it does not matter that a message only
travels one hop in that particular form, with that exact set of information
enclosed. Hop limit and hop count are part of the message and used by the
routing protocol, and so they refer to the multi-hop path that the AODVv2
message will follow, indicating when not to regenerate any further. So
AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit the
number of hops across which it will regenerate a packet so as to "prevent
messages from endlessly circulating in a MANET".

Kind regards,
Victoria.

On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <
christopher.dearlove@gmail.com> wrote:

> I've not had time to look at either yet, though I hope to review DLEP ver=
y
> soon.
>
> But this has made me think about the RFC 6621 reference in AODVv2. It's
> always been clear this has been rather a throwaway comment that needed
> thought, but until now I hadn't really given it any.
>
> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's
> consider each on turn.
>
> AODVv2 is in the RFC 5444 structure. As has been noted on many occasions,
> AOVDVv2 gets to use messages, but packets are not in its competence.
>
> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.
> It's about whether or not to forward them. But RFC 5444 packets aren't ju=
st
> not forwarded in unchanged IP packets, they aren't even forwarded at all.
> They are each a single hop construct, and if a message is forwarded (whic=
h
> is by the routing protocol, as far as RFC 5444 is concerned, it's a new
> message) it will be in a new packet, with possibly new companions.
>
> If AODVv2 wants to use a more efficient flooding process, it needs one at
> the message level. Now an example of that exists - the mechanism on RFC
> 7181. Unfortunately we didn't break that out as a separate draft (we woul=
d
> have liked to, but there were reasons we didn't).
>
> And even if (by reference or other means) it were used - or some related
> mechanism such as a CDS - that processing/forwarding mechanism assumes yo=
u
> have defined MPRs (or similarly, that you have defined a CDS). And that
> needs a local exchange of information, such as NHDP's HELLO messages (and
> the rest of NHDP) augmented with RFC 7181's MPR TLV (though only the
> flooding bit is needed).
>
> In other words, taking some real work to define. And also raising a
> question for the WG - why do we want a reactive protocol? The main
> attraction as I see it is the "if you're not doing anything, you're not
> transmitting" property. Which adding this voids. Of course maybe the WG
> doesn't value that. Or it is acceptable as an option. But if so it needs =
to
> be an option that all routers use, or none. And if all, compatibly. (MPR
> flooding allows different MPR selection algorithms - but only as long as
> they satisfy the fundamental MPR algorithm properties.)
>
> In short, RFC 6621 must go. The alternative is nothing, or significant
> work.
>
> --
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>
> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote:
>
> Dear all,
>
> I have started looking through the recently
> updated draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not t=
o
> have had a blow-by-bow comeback to the previous review comments  - would
> have made it a somewhat easier task to check if all have been addressed o=
r
> not.
>
> But, I will work through it and produce a detailed review - but from my
> first quick read-through there're a couple of issue that jumped at me as
> worth bringing forward on a more global level already.
>
> The first relates to  how RREQs are forwarded -- or, more generally, are
> not.
>
> The protocol currently talks about "message is regenerated" rather than
> "forwarded". I have understood that this means that a RREQ is actually no=
t
> an "end to end" entity, but is a "hop by hop" entity.
>
> First, that is a curious design choice, is there any reason why this is s=
o
> considered?
>
> Second, if a RREQ message is hop-by-hop only, then I do not think that th=
e
> use of the RFC5444 hop-limit/hop-count fields is appropriate.
>
> Third, the statement in section 6.5 on the use of RFC6621 is incorrect in
> two ways: RFC6621 does specify how messages are *forwarded* (but, as
> discussed above, you are not forwarding messages).
>
> More seriously, this paragraph is incorrect:
>
>
> "Implementations MAY choose to employ techniques to reduce the number
>    of multicast messages sent.  Use of [RFC6621 <https://tools.ietf.org/h=
tml/rfc6621>] in deployments is
>    recommended.  Employing [RFC6621 <https://tools.ietf.org/html/rfc6621>=
] in a subset of the operational
>    AODVv2 routers in a network, or configuring different algorithms on
>    different routers, will not cause interoperability issues, but will
>    reduce the effectiveness of the multicast reduction scheme."
>
>
> Different routers using different relay selection algorithms in the same
> network will not *just* cause loss of efficiency, but *will* cause
> interoperability issues.
>
> For example if "router A" decides to suppress its message relaying becaus=
e
> it estimates that "router B" provides sufficient coverage - and conversel=
y
> "router B" suppresses relaying for the same reason: neither A nor B would
> relay, and so any routers reachable only via A and B would not be covered=
.
>
> This is not a far-sought example: it can be as simple as A and B simply
> using self-selecting relay algorithms with different tie-breakers.
>
> In short: I think that the whole message flooding/regeneration part
> requires serious work.
>
> The second issue is that I also suspect that there is some issue with
> buffering, or rather with how it is specified; starting in section 6.6, I
> am not sure that leaving that as "a matter of policy at each router" is
> entirely right.
>
> Also on buffering, I am wondering if the "start delivering buffered
> packets" conditions (penultimate paragraph in 6.6, and of course through
> the processing sections) is sufficient; I suspect that the condition "Whe=
n
> a valid route is installed" is not sufficient - that there are situations
> where a routing table entry is installed, but the complete route is not
> available or is not bidirectional?This obviously is related to RREP_Ack
> being hop-by-hop and not end-to-end....
>
> Either way, the parts of the specification that relate to buffering
> contain a mixture of normative and non-normative verbiage (a lot of "can"
> but also a lot of MUST/SHOULD) which I think could do with a tightening u=
p.
>
> But....is buffering even something that should be specified by this
> document? It does not impact interoperability and it interferes
> substantially with transport and congestion control, and I am not sure th=
at
> we understand the consequences (I am not convinced that the claims in the
> document on benefits to TCP are substantiated or even true).
>
> As I indicated, a complete review will follow, but I thought that these
> was a global enough topics to call out and get engineered right.
>
> Thomas
>
> PS: I remain convinced that the security considerations section is
> insufficient ; I will try to articulate my thoughts on why that is, but f=
or
> starters looking at the recently raised (by somebody else, the Chris
> replied) AODV security questions would probably be helpful
>
> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote:
>
> Hello WG participants =E2=80=93
>
>
>
> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16
> (DLEP). The co-authors and the chairs ask that you please take some time =
to
> review and comment on the new submissions.
>
>
>
> Regards,
>
> Stan
>
>
>
>
>
> _____________________________________________________
> This electronic message and any files transmitted with it contains
> information from iDirect, which may be privileged, proprietary
> and/or confidential. It is intended solely for the use of the individual
> or entity to whom they are addressed. If you are not the original
> recipient or the person responsible for delivering the email to the
> intended recipient, be advised that you have received this email
> in error, and that any use, dissemination, forwarding, printing, or
> copying of this email is strictly prohibited. If you received this email
> in error, please delete it and immediately notify the sender.
> _____________________________________________________
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_quote"><div dir=3D"ltr"><p dir=3D"=
ltr">Hi Thomas and Christopher,</p>
<p dir=3D"ltr">Thank you for your comments.=C2=A0 If I may address just one=
=20
point for starters - regeneration vs forwarding. We use the term=20
regeneration since forwarding seems inappropriate when the message=20
content changes at each hop.</p>
<p dir=3D"ltr">The changes we make to the message content are:</p>
<p dir=3D"ltr">1) We change the metric so that each router along the path=
=20
learns a route from the message, with the metric associated with the=20
path up to that point<br>
2) AckReq only applies between hops, so needs to be removed at each hop,
 and a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router=20
that wishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our r=
oute set.</p>
<p dir=3D"ltr">Can we really use the term &quot;forwarding&quot; if we are =
changing=20
the metric value, adding a validity time, adding/removing AckReq or=20
removing addresses and their associated TLVs?</p>
<p dir=3D"ltr">Further, in reply to the comment about use of the=20
msg-hop-count and msg-hop-limit fields, I think it does not matter that a
=20
message only travels one hop in that particular form, with that exact=20
set of information enclosed. Hop limit and hop count are part of the=20
message=20
and used by the routing protocol, and so they=20
refer to the multi-hop path that the AODVv2 message will follow,=20
indicating when not to regenerate any further. So=20
AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit=20
the number of hops across which it will regenerate a packet so as to=20
&quot;prevent messages from endlessly circulating in a MANET&quot;. </p>
<p dir=3D"ltr">Kind regards,<br>
Victoria.</p></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Wed, Nov 18, 2015 at 8:49 AM, =
Christopher Dearlove <span dir=3D"ltr">&lt;<a href=3D"mailto:christopher.de=
arlove@gmail.com" target=3D"_blank">christopher.dearlove@gmail.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><div>I&#3=
9;ve not had time to look at either yet, though I hope to review DLEP very =
soon.</div><div><br></div><div>But this has made me think about the RFC 662=
1 reference in AODVv2. It&#39;s always been clear this has been rather a th=
rowaway comment that needed thought, but until now I hadn&#39;t really give=
n it any.</div><div><br></div><div>And it doesn&#39;t work. RFC 6621 is fun=
damentally unusable here. Let&#39;s consider each on turn.=C2=A0</div><div>=
<br></div><div>AODVv2 is in the RFC 5444 structure. As has been noted on ma=
ny occasions, AOVDVv2 gets to use messages, but packets are not in its comp=
etence.</div><div><br></div><div>RFC 6621 is about packets. But not even RF=
C 5444 packets but IP packets. It&#39;s about whether or not to forward the=
m. But RFC 5444 packets aren&#39;t just not forwarded in unchanged IP packe=
ts, they aren&#39;t even forwarded at all. They are each a single hop const=
ruct, and if a message is forwarded (which is by the routing protocol, as f=
ar as RFC 5444 is concerned, it&#39;s a new message) it will be in a new pa=
cket, with possibly new companions.</div><div><br></div><div>If AODVv2 want=
s to use a more efficient flooding process, it needs one at the message lev=
el. Now an example of that exists - the mechanism on RFC 7181. Unfortunatel=
y we didn&#39;t break that out as a separate draft (we would have liked to,=
 but there were reasons we didn&#39;t).</div><div><br></div><div>And even i=
f (by reference or other means) it were used - or some related mechanism su=
ch as a CDS - that processing/forwarding mechanism assumes you have defined=
 MPRs (or similarly, that you have defined a CDS). And that needs a local e=
xchange of information, such as NHDP&#39;s HELLO messages (and the rest of =
NHDP) augmented with RFC 7181&#39;s MPR TLV (though only the flooding bit i=
s needed).</div><div><br></div><div>In other words, taking some real work t=
o define. And also raising a question for the WG - why do we want a reactiv=
e protocol? The main attraction as I see it is the &quot;if you&#39;re not =
doing anything, you&#39;re not transmitting&quot; property. Which adding th=
is voids. Of course maybe the WG doesn&#39;t value that. Or it is acceptabl=
e as an option. But if so it needs to be an option that all routers use, or=
 none. And if all, compatibly. (MPR flooding allows different MPR selection=
 algorithms - but only as long as they satisfy the fundamental MPR algorith=
m properties.)</div><div><br></div><div>In short, RFC 6621 must go. The alt=
ernative is nothing, or significant work.<br><br><div>-- =C2=A0<span><font =
color=3D"#888888"><div>Christopher Dearlove</div><div><a href=3D"mailto:chr=
istopher.dearlove@gmail.com" target=3D"_blank">christopher.dearlove@gmail.c=
om</a> (iPhone)</div><div><a href=3D"mailto:chris@mnemosyne.demon.co.uk" ta=
rget=3D"_blank">chris@mnemosyne.demon.co.uk</a> (home)</div></font></span><=
/div></div><div><div><div><br>On 18 Nov 2015, at 01:35, Thomas Clausen &lt;=
<a href=3D"mailto:ietf@thomasclausen.org" target=3D"_blank">ietf@thomasclau=
sen.org</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>
<div>Dear all,</div><div><br></div><div>I have started looking through the =
recently updated=C2=A0draft-ietf-manet-aodvv2-12. A lot has changed, and I =
regret not to have had a blow-by-bow comeback to the previous review commen=
ts =C2=A0- would have made it a somewhat easier task to check if all have b=
een addressed or not.</div><div><br></div><div>But, I will work through it =
and produce a detailed review - but from my first quick read-through there&=
#39;re a couple of issue that jumped at me as worth bringing forward on a m=
ore global level already.</div><div><br></div><div>The first relates to =C2=
=A0how RREQs are forwarded -- or, more generally, are not.</div><div><br></=
div><div>The protocol currently talks about &quot;message is regenerated&qu=
ot; rather than &quot;forwarded&quot;. I have understood that this means th=
at a RREQ is actually not an &quot;end to end&quot; entity, but is a &quot;=
hop by hop&quot; entity.=C2=A0</div><div><br></div><div>First, that is a cu=
rious design choice, is there any reason why this is so considered?</div><d=
iv><br></div><div>Second, if a RREQ message is hop-by-hop only, then I do n=
ot think that the use of the RFC5444 hop-limit/hop-count fields is appropri=
ate.</div><div><br></div><div>Third, the statement in section 6.5 on the us=
e of RFC6621 is incorrect in two ways: RFC6621 does specify how messages ar=
e *forwarded* (but, as discussed above, you are not forwarding messages).</=
div><div><br></div><div>More seriously, this paragraph <span style=3D"backg=
round-color:rgba(255,255,255,0)">is incorrect</span>:</div><div><pre style=
=3D"margin-top:0px;margin-bottom:0px"><font face=3D"UICTFontTextStyleTallBo=
dy"><span style=3D"white-space:normal;background-color:rgba(255,255,255,0)"=
><br></span></font></pre><pre style=3D"margin-top:0px;margin-bottom:0px"><b=
lockquote type=3D"cite"><font face=3D"UICTFontTextStyleTallBody"><span styl=
e=3D"white-space:normal;background-color:rgba(255,255,255,0)">&quot;Impleme=
ntations MAY choose to employ techniques to reduce the number
   of multicast messages sent.  Use of [<a href=3D"https://tools.ietf.org/h=
tml/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;" target=
=3D"_blank">RFC6621</a>] in deployments is
   recommended.  Employing [<a href=3D"https://tools.ietf.org/html/rfc6621"=
 title=3D"&quot;Simplified Multicast Forwarding&quot;" target=3D"_blank">RF=
C6621</a>] in a subset of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction scheme.&quot;</span>=
</font><span style=3D"font-size:19px">
</span></blockquote></pre></div><div><br></div><div>Different routers using=
 different relay selection algorithms in the same network will not *just* c=
ause loss of efficiency, but *will* cause interoperability issues.</div><di=
v><br></div><div>For example if &quot;router A&quot; decides to suppress it=
s message relaying because it estimates that &quot;router B&quot; provides =
sufficient coverage - and conversely &quot;router B&quot; suppresses relayi=
ng for the same reason: neither A nor B would relay, and so any routers rea=
chable only via A and B would not be covered.</div><div><br></div><div>This=
 is not a far-sought example: it can be as simple as A and B simply using s=
elf-selecting relay algorithms with different tie-breakers.</div><div><br><=
/div><div>In short: I think that the whole message flooding/regeneration pa=
rt requires serious work.</div><div><br></div><div><div><span style=3D"back=
ground-color:rgba(255,255,255,0)">The second issue is that I also suspect t=
hat there is some issue with buffering, or rather with how it is specified;=
 starting in section 6.6, I am not sure that leaving that as &quot;a matter=
 of policy at each router&quot; is entirely right.=C2=A0</span></div><div><=
span style=3D"background-color:rgba(255,255,255,0)"><br></span></div><div><=
span style=3D"background-color:rgba(255,255,255,0)">Also on buffering, I am=
 wondering if the &quot;start delivering buffered packets&quot; conditions =
(penultimate paragraph in 6.6, and of course through the processing section=
s) is sufficient; I suspect that the condition &quot;When a valid route is =
installed&quot; is not sufficient - that there are situations where a routi=
ng table entry is installed, but the complete route is not available or is =
not bidirectional?This obviously is related to RREP_Ack being hop-by-hop an=
d not end-to-end....</span></div><div><span style=3D"background-color:rgba(=
255,255,255,0)"><br></span></div><div><span style=3D"background-color:rgba(=
255,255,255,0)">Either way, the parts of the specification that relate to b=
uffering contain a mixture of normative and non-normative verbiage (a lot o=
f &quot;can&quot; but also a lot of MUST/SHOULD) which I think could do wit=
h a tightening up.=C2=A0</span></div><div><span style=3D"background-color:r=
gba(255,255,255,0)"><br></span></div><div><span style=3D"background-color:r=
gba(255,255,255,0)">But....is buffering even something that should be speci=
fied by this document? It does not impact interoperability and it interfere=
s substantially with transport and congestion control, and I am not sure th=
at we understand the consequences (I am not convinced that the claims in th=
e document on benefits to TCP are substantiated or even true).</span></div>=
<div><span style=3D"background-color:rgba(255,255,255,0)"><br></span><div>A=
s I indicated, a complete review will follow, but I thought that these was =
a global enough topics to call out and get engineered right.</div></div></d=
iv><div><br></div><div>Thomas</div><div><br></div><div>PS: I remain convinc=
ed that the security considerations section is insufficient ; I will try to=
 articulate my thoughts on why that is, but for starters looking at the rec=
ently raised (by somebody else, the Chris replied) AODV security questions =
would probably be helpful</div><div><div></div></div><div><br>On 10 Nov 201=
5, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sratliff@idirect.net" t=
arget=3D"_blank">sratliff@idirect.net</a>&gt; wrote:<br><br></div><blockquo=
te type=3D"cite"><div>






<div>
<p class=3D"MsoNormal">Hello WG participants =E2=80=93 <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">The above referenc=
ed drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (DLEP). The co-auth=
ors and the chairs ask that you please take some
 time to review and comment on the new submissions. <u></u><u></u></span></=
p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>=C2=A0<u></=
u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Regards,<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Stan<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>=C2=A0<u></=
u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<br><span style=3D"font-size:8pt;font-family:Arial,sans-serif;color:#003366=
">_____________________________________________________<br>This electronic =
message and any files transmitted with it contains<br>information from iDir=
ect, which may be privileged, proprietary<br>and/or confidential. It is int=
ended solely for the use of the individual<br>or entity to whom they are ad=
dressed. If you are not the original<br>recipient or the person responsible=
 for delivering the email to the<br>intended recipient, be advised that you=
 have received this email<br>in error, and that any use, dissemination, for=
warding, printing, or<br>copying of this email is strictly prohibited. If y=
ou received this email<br>in error, please delete it and immediately notify=
 the sender.<br>_____________________________________________________</span=
>

</div></blockquote><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/listinfo/manet" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a></span><br><=
/div></blockquote></div></blockquote><blockquote type=3D"cite"><div><span>_=
______________________________________________</span><br><span>manet mailin=
g 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/=
listinfo/manet" target=3D"_blank">https://www.ietf.org/mailman/listinfo/man=
et</a></span><br></div></blockquote></div></div></div><br>_________________=
______________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>
</div></div></div><br></div>

--001a11c39b663918b20524e6fa77--


From nobody Thu Nov 19 14:36:44 2015
Return-Path: <prvs=876563002b=david.wiggins@ll.mit.edu>
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 BA0371B369C for <manet@ietfa.amsl.com>; Thu, 19 Nov 2015 14:36:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.784
X-Spam-Level: 
X-Spam-Status: No, score=-4.784 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, UNPARSEABLE_RELAY=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 8WLRicfK5B-K for <manet@ietfa.amsl.com>; Thu, 19 Nov 2015 14:36:41 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0D49A1B369A for <manet@ietf.org>; Thu, 19 Nov 2015 14:36:40 -0800 (PST)
Received: from LLE2K10-HUB01.mitll.ad.local (LLE2K10-HUB01.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tAJMadoQ004033; Thu, 19 Nov 2015 17:36:39 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: Rick Taylor <rick@tropicalstormsoftware.com>, manet IETF <manet@ietf.org>
Thread-Topic: [manet] New individual draft
Thread-Index: AQHRIxrAYeQh97DhUk+/5j0T0bl5vA==
Date: Thu, 19 Nov 2015 22:36:38 +0000
Message-ID: <D273B8B7.129C%David.Wiggins@ll.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.59.174]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3530799397_53899409"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-11-19_15:2015-11-19,2015-11-19,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1508030000 definitions=main-1511190370
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/846Cz3nhy_e4aFqAbkFbzHM0O5s>
Subject: Re: [manet] New individual 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: <https://mailarchive.ietf.org/arch/browse/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, 19 Nov 2015 22:36:42 -0000

--B_3530799397_53899409
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

I made a pass through DLEP-17 when it came out, and nothing jumped out at
me.  I'll take another look and send any comments by Monday.

David

On 11/19/15, 10:02 AM, "manet on behalf of Rick Taylor"
<manet-bounces@ietf.org on behalf of rick@tropicalstormsoftware.com> wrote:

>Hi All,
>
>I have just submitted a new individual draft: DLEP Destination Service
>Announcement (https://www.ietf.org/id/draft-taylor-manet-dlep-dsa-00.txt)
>
>This is an extension to DLEP, and so should probably wait for DLEP to
>progress, but I am asking for working group adoption.
>
>I understand that the WG is not taking on any further tasks before the
>current outstanding tasks complete, so can I request everyone interested
>please review DLEP-17?
>
>Many thanks
>
>Rick Taylor
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www.ietf.org/mailman/listinfo/manet

--B_3530799397_53899409
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIMEgYJKoZIhvcNAQcCoIIMAzCCC/8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CfUwggT1MIID3aADAgECAgpar+vgAAAAADYOMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAMTCk1JVExMIENBLTMwHhcNMTUwNDA2MTE1OTM4WhcNMTYwNDA1MTE1OTM4WjBiMQsw
CQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMG
UGVvcGxlMSEwHwYDVQQDExhXaWdnaW5zLkRhdmlkLlAuNTAwMTUyMDcwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDdVA0BrVjbk6NP8JFi7Lks3SHtN8CxSBqFLPNRVWGjTgLG
W9pDcqqOrij0IHmGpAP404gR4dP9mUEb9KfOhKuDdFQFyZnVICDSRbyT4tGOxiTH7MIsV49d
UwrWhj2P/ms6wf1E5L2QwJqjOTMPZj3IClWAkcZsAix5jHkLvNXI5OilCe2u2TDihM1x2kfB
zgQpRy9tuXpxYtFZpoEb0XbqLIzS9FLkTbqlocSm4jwhPXTFQtFwbd6l4zzD4RVPgnpFxg/8
KpuV35lGkp5lbPvpkskz4+n3P9LoCvpoh1pgj3fS0CvCVRzWRAX+oNR/D7RmP1ug+7Ix+JCg
iAB3vLdFAgMBAAGjggG8MIIBuDAdBgNVHQ4EFgQUofYOKn4e6iCZO59iu2f0FxOad4MwDgYD
VR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUH
AQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcE
MDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAiBgNV
HSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMCMGA1UdEQQcMBqBGERhdmlkLldpZ2dpbnNAbGwubWl0LmVkdTAnBgkrBgEEAYI3FAIE
Gh4YAEwATABVAHMAZQByAFMAaQBnAC0AUwBXMA0GCSqGSIb3DQEBCwUAA4IBAQCgEybvvRIJ
tAlKEfYZyf5DIlcT+LfePOiebFcPxZatSTQW/hJHv4RX/TN8N3bQrx4Jkxe17eQfsKvJXhOi
R6as3vemCxYEMOFIKSsm5LEIC4D4GcXBRZ1CAJIHCY5ezXfKQUxBSdZAq82/fAoNEEP4KPEv
Y07m7OVwXMWpu7kz3CeBVOqL7xlL53pPvkyxtijQRtZrZ5coE9Qh9tHzATi7DW8UWoUv3Yhj
Qz9SnBn3T30ho0GtlTvMXso7UjGZFWLQI2JyR2QW5FYq8GGEq/5PRz/xslsKA5EoHxmSSeRh
eei3gpFbnUrRS+5JSS6kgA/HVoM7CRFo/O8KYXU5z/ihMIIE+DCCA+CgAwIBAgIKWrCpkwAA
AAA2DzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNv
bG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1
MDQwNjEyMDAyNloXDTE2MDQwNTEyMDAyNlowYjELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBlb3BsZTEhMB8GA1UEAxMYV2lnZ2lu
cy5EYXZpZC5QLjUwMDE1MjA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlEWD
uIm5kuHghfe7O+eMLVena6sNfAZtHLp2mwXLrNshaHM6wVKmml8zhxeSmJJXTF3Owyn7imKs
vHMWcIJD9EoFQyJoeBaFV5Ll75/fE2WKswtGn9ZSSejplI/Iy99SI/9Lna5B7/BDmPozGn66
jdzgl+JVFptqEUGx5NZlRUEEtVtXYUy+PllIq6SpR/242wFiYVslFqSoHu789mexaDDAl7p7
z3W9cYidPtZUoysjW0omzwZIoYMsIhTbUMnv+TkBuhJErBmaNvAXPf8Y3pNf3pYz8pnR4MyI
ibFv2CS/2KLGxJRE9xt1nrgHT8Wx+E6Ro6IYkYLPSdE6YgYAgwIDAQABo4IBvzCCAbswHQYD
VR0OBBYEFGww5LYEZSoVOkuJ7ZVJS+35ChrUMA4GA1UdDwEB/wQEAwIFIDAfBgNVHSMEGDAW
gBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0
cDovL2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2Nz
cC5sbC5taXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aG
rYcVg+rwRYW2oR8dhevQcIPr7SACAWQCAQQwJQYDVR0lBB4wHAYEVR0lAAYIKwYBBQUHAwQG
CisGAQQBgjcKAwQwGAYDVR0gBBEwDzANBgsqhkiG9xICAQMBCDAjBgNVHREEHDAagRhEYXZp
ZC5XaWdnaW5zQGxsLm1pdC5lZHUwJwYJKwYBBAGCNxQCBBoeGABMAEwAVQBzAGUAcgBFAG4A
YwAtAFMAVzANBgkqhkiG9w0BAQsFAAOCAQEATCsJT66TKeYNh9hrcC1wxRH08CricKt9JktB
I1WWl48F4CqcYDZlLMpvHuSe6GezZzTUH4oq1y2q3um9Txh1NjLPT7j0k5SSwdr2V7d8upDN
WOrXvCi59Cyz5RvuhleCPIE+6wPyDrQwfBRhte/cv8PVOrsG4tio4VOHi/nXcS+HLgC5qNxk
1/w1UBf8QkkNP8kIgum/uItm4QwVdVAJMuwe3te8dYjtp3M5nC2exfqQfk+Mmw/8fdZFpch0
rSYbpchMMOueBuy2UnWaYBF84uXldBH9fkONRX8AL8EQ3sQEOyzxqpwKQ/d0itjAGaPCCJCI
VgnSYSWYoFiN9idyaTGCAeUwggHhAgEBMF8wUTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTETMBEGA1UEAxMKTUlUTEwgQ0Et
MwIKWq/r4AAAAAA2DjAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFJQVT3oFgeiQR9AU
1BbMOAxWoHcPMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MTExOTIyMzYzN1owDQYJKoZIhvcNAQEBBQAEggEAbwD7aNOneqPokLekQFjnm3EZQBN4+qwQ
CILp5LlKljkdosZQ0Eg77UlNUA7bjeJld5o8wAYBUvuYHCWooK7/+7Jeqr1E4MxMDkJQ5zuO
G4z64Sx138IHZpHYQPTCNSws1PcuZPBqAgSJWc7wSoewGFZs1LSm5uV/X3Pe2rv77v8SdmEC
ctlGQA4QPJFJktZnyM//0lI4ezWdtV6Fo3oTPEPFpqQrX4gT5nkgqgQ/Vxhr/YzPuR8kjiEN
oZ5EJ84yxxDokKDxxVgD7nRA4APCWR6bijoQpmt/qUbY0Z5MJJWm3/mvTPUo4cw8mTlvmn+q
dL+BGiOiiyYJ9t8Hy74xkg==

--B_3530799397_53899409--


From nobody Mon Nov 23 07:40:35 2015
Return-Path: <prvs=8769e8d09e=david.wiggins@ll.mit.edu>
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 26B231A88AC for <manet@ietfa.amsl.com>; Mon, 23 Nov 2015 07:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.885
X-Spam-Level: 
X-Spam-Status: No, score=-2.885 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, UNPARSEABLE_RELAY=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 V3H70jS4VvXm for <manet@ietfa.amsl.com>; Mon, 23 Nov 2015 07:40:30 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id 10E051A88A7 for <manet@ietf.org>; Mon, 23 Nov 2015 07:40:29 -0800 (PST)
Received: from LLE2K10-HUB01.mitll.ad.local (LLE2K10-HUB01.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tANFeScA021577; Mon, 23 Nov 2015 10:40:28 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: manet IETF <manet@ietf.org>, "Ratliff, Stanley" <sratliff@idirect.net>
Thread-Topic: DLEP-17 comments
Thread-Index: AQHRJgVGI+oO8ZSuh0OtSSuxn9Cu4Q==
Date: Mon, 23 Nov 2015 15:40:27 +0000
Message-ID: <D2789D9A.12B7%David.Wiggins@ll.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.59.174]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3531120026_73159765"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-11-23_07:2015-11-23,2015-11-23,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1508030000 definitions=main-1511230266
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/aqJ4k_uiQQ2KAdWGjRulkocx1sM>
Subject: [manet] DLEP-17 comments
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Nov 2015 15:40:33 -0000

--B_3531120026_73159765
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Here are a few minor comments on DLEP-17.  It is much improved over the
drafts I saw at the beginning of this year.

-- The IPv4/6 Attached Subnet data item can appear in Destination Up, but
not in Destination Update.  At first I thought this was an omission, but
then I found this in section 10.11:

   As in the case of the IPv4 attached Subnet
   data item above, once an IPv6 attached subnet has been declared, it
   SHALL NOT be withdrawn without withdrawing the destination (via the
   Destination Down message (Section 9.11) and re-issuing the
   Destination Up message.

Why have this restriction?  It seems odd for this data item to have
different behavior than all of the other similar ones.

If the restriction is kept, then the definition of the data item may need
adjusting.  The flags field indicates "whether this is a new or existing
subnet address (1), or a withdrawal of a subnet address (0)," but the
above paragraph rules out the possibility of withdrawal.  So this is an
option that can never be exercised, which is confusing.  Perhaps you can
keep the flags field for future extensibility, but just not define any
flags for now.

-- When the session initialization handshake completes, it seems like a
good idea for the protocol to require each peer to send all of its
currently-up destinations to the other peer.  If they don't, the protocol
can get into an endless cycle of terminating and re-establishing the
session (we have seen this):

Peer A and B start a session
Peer A sends Destination Up X to B
something happens to terminate the session (some other error, for example)
Peer A and B restart the session
Peer A sends Destination UpDATE X to B
Peer B terminates the session because it's never heard of destination X

Peer A and B restart the session...

Peer A made a mistake by sending an Update before an Up.  Requiring a
database dump of all existing destinations to your new peer avoids this
mistake.  You could instead track which destinations you've send to each
peer, and make sure that any Update is preceded by Up, but that
complicates the implementation.  Anyway, your peer probably needs to know
the state of your world up front.  If you're not telling a peer about a
known destination, it seems likely that routing is not going to work as
you expect.


--Remove the normative reference to the credit windowing extension if this
really gates progress on DLEP.

Hope this helps.

David

--B_3531120026_73159765
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIMEgYJKoZIhvcNAQcCoIIMAzCCC/8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CfUwggT1MIID3aADAgECAgpar+vgAAAAADYOMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAMTCk1JVExMIENBLTMwHhcNMTUwNDA2MTE1OTM4WhcNMTYwNDA1MTE1OTM4WjBiMQsw
CQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMG
UGVvcGxlMSEwHwYDVQQDExhXaWdnaW5zLkRhdmlkLlAuNTAwMTUyMDcwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDdVA0BrVjbk6NP8JFi7Lks3SHtN8CxSBqFLPNRVWGjTgLG
W9pDcqqOrij0IHmGpAP404gR4dP9mUEb9KfOhKuDdFQFyZnVICDSRbyT4tGOxiTH7MIsV49d
UwrWhj2P/ms6wf1E5L2QwJqjOTMPZj3IClWAkcZsAix5jHkLvNXI5OilCe2u2TDihM1x2kfB
zgQpRy9tuXpxYtFZpoEb0XbqLIzS9FLkTbqlocSm4jwhPXTFQtFwbd6l4zzD4RVPgnpFxg/8
KpuV35lGkp5lbPvpkskz4+n3P9LoCvpoh1pgj3fS0CvCVRzWRAX+oNR/D7RmP1ug+7Ix+JCg
iAB3vLdFAgMBAAGjggG8MIIBuDAdBgNVHQ4EFgQUofYOKn4e6iCZO59iu2f0FxOad4MwDgYD
VR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUH
AQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcE
MDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAiBgNV
HSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMCMGA1UdEQQcMBqBGERhdmlkLldpZ2dpbnNAbGwubWl0LmVkdTAnBgkrBgEEAYI3FAIE
Gh4YAEwATABVAHMAZQByAFMAaQBnAC0AUwBXMA0GCSqGSIb3DQEBCwUAA4IBAQCgEybvvRIJ
tAlKEfYZyf5DIlcT+LfePOiebFcPxZatSTQW/hJHv4RX/TN8N3bQrx4Jkxe17eQfsKvJXhOi
R6as3vemCxYEMOFIKSsm5LEIC4D4GcXBRZ1CAJIHCY5ezXfKQUxBSdZAq82/fAoNEEP4KPEv
Y07m7OVwXMWpu7kz3CeBVOqL7xlL53pPvkyxtijQRtZrZ5coE9Qh9tHzATi7DW8UWoUv3Yhj
Qz9SnBn3T30ho0GtlTvMXso7UjGZFWLQI2JyR2QW5FYq8GGEq/5PRz/xslsKA5EoHxmSSeRh
eei3gpFbnUrRS+5JSS6kgA/HVoM7CRFo/O8KYXU5z/ihMIIE+DCCA+CgAwIBAgIKWrCpkwAA
AAA2DzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNv
bG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1
MDQwNjEyMDAyNloXDTE2MDQwNTEyMDAyNlowYjELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBlb3BsZTEhMB8GA1UEAxMYV2lnZ2lu
cy5EYXZpZC5QLjUwMDE1MjA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlEWD
uIm5kuHghfe7O+eMLVena6sNfAZtHLp2mwXLrNshaHM6wVKmml8zhxeSmJJXTF3Owyn7imKs
vHMWcIJD9EoFQyJoeBaFV5Ll75/fE2WKswtGn9ZSSejplI/Iy99SI/9Lna5B7/BDmPozGn66
jdzgl+JVFptqEUGx5NZlRUEEtVtXYUy+PllIq6SpR/242wFiYVslFqSoHu789mexaDDAl7p7
z3W9cYidPtZUoysjW0omzwZIoYMsIhTbUMnv+TkBuhJErBmaNvAXPf8Y3pNf3pYz8pnR4MyI
ibFv2CS/2KLGxJRE9xt1nrgHT8Wx+E6Ro6IYkYLPSdE6YgYAgwIDAQABo4IBvzCCAbswHQYD
VR0OBBYEFGww5LYEZSoVOkuJ7ZVJS+35ChrUMA4GA1UdDwEB/wQEAwIFIDAfBgNVHSMEGDAW
gBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0
cDovL2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2Nz
cC5sbC5taXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aG
rYcVg+rwRYW2oR8dhevQcIPr7SACAWQCAQQwJQYDVR0lBB4wHAYEVR0lAAYIKwYBBQUHAwQG
CisGAQQBgjcKAwQwGAYDVR0gBBEwDzANBgsqhkiG9xICAQMBCDAjBgNVHREEHDAagRhEYXZp
ZC5XaWdnaW5zQGxsLm1pdC5lZHUwJwYJKwYBBAGCNxQCBBoeGABMAEwAVQBzAGUAcgBFAG4A
YwAtAFMAVzANBgkqhkiG9w0BAQsFAAOCAQEATCsJT66TKeYNh9hrcC1wxRH08CricKt9JktB
I1WWl48F4CqcYDZlLMpvHuSe6GezZzTUH4oq1y2q3um9Txh1NjLPT7j0k5SSwdr2V7d8upDN
WOrXvCi59Cyz5RvuhleCPIE+6wPyDrQwfBRhte/cv8PVOrsG4tio4VOHi/nXcS+HLgC5qNxk
1/w1UBf8QkkNP8kIgum/uItm4QwVdVAJMuwe3te8dYjtp3M5nC2exfqQfk+Mmw/8fdZFpch0
rSYbpchMMOueBuy2UnWaYBF84uXldBH9fkONRX8AL8EQ3sQEOyzxqpwKQ/d0itjAGaPCCJCI
VgnSYSWYoFiN9idyaTGCAeUwggHhAgEBMF8wUTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTETMBEGA1UEAxMKTUlUTEwgQ0Et
MwIKWq/r4AAAAAA2DjAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFP5N5OtwxtcYkHiK
7laepcNEUlJNMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MTEyMzE1NDAyNlowDQYJKoZIhvcNAQEBBQAEggEAm2qp8aM6cdr1DrwvEV+/N+YFDXgR0dU5
J2dw8Q7U9EHdRQEwflnhqduEBMeizfeGOHNT6UoaGRQEW2NX7OjHC5LRDwNt6nr/RMiHEbrv
cq2NjBgMcLXZUbOb2bJPYAoZdsEW6vqz1Dw1yUxuNLIe0RmkQu5L3D3Ukm+Z0hSaWQ96KRFm
Ckl6KnwJVG0ZXNP/mad+ThhqOi1afCjbXc9ry1qF99fGV3olclDcFCqXGspRdYwlHerzDVpX
HEewDzoecW5M86PmC3mr1FwyMDZko1RM+FcEN/zCWCGgNLFcScNZZDfW+39An8G6Y1lpWl33
9ltErw0hxWs/XQ3a/gh6zQ==

--B_3531120026_73159765--


From nobody Mon Nov 23 08:06:15 2015
Return-Path: <rick@tropicalstormsoftware.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 536C91A8968 for <manet@ietfa.amsl.com>; Mon, 23 Nov 2015 08:06:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 EecGVIBMVBzR for <manet@ietfa.amsl.com>; Mon, 23 Nov 2015 08:06:12 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31C1F1A8966 for <manet@ietf.org>; Mon, 23 Nov 2015 08:06:12 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Mon, 23 Nov 2015 16:05:47 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>, manet IETF <manet@ietf.org>, "Ratliff, Stanley" <sratliff@idirect.net>
Thread-Topic: [manet] DLEP-17 comments
Thread-Index: AQHRJgjPecjBNJYs7kSmaWLbMNQN5g==
Date: Mon, 23 Nov 2015 16:05:46 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8AFFA22@tss-server1.home.tropicalstormsoftware.com>
References: <D2789D9A.12B7%David.Wiggins@ll.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/SekDTqe8F2MQSkeg0HsEB6SPnIw>
Subject: Re: [manet] DLEP-17 comments
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Nov 2015 16:06:14 -0000

Thank you very much for the review David,=0A=
=0A=
Some comments inline...=0A=
=0A=
On 23/11/15 15:40, Wiggins, David - 0665 - MITLL wrote:=0A=
> Here are a few minor comments on DLEP-17.  It is much improved over the=
=0A=
> drafts I saw at the beginning of this year.=0A=
>=0A=
> -- The IPv4/6 Attached Subnet data item can appear in Destination Up, but=
=0A=
> not in Destination Update.  At first I thought this was an omission, but=
=0A=
> then I found this in section 10.11:=0A=
>=0A=
>     As in the case of the IPv4 attached Subnet=0A=
>     data item above, once an IPv6 attached subnet has been declared, it=
=0A=
>     SHALL NOT be withdrawn without withdrawing the destination (via the=
=0A=
>     Destination Down message (Section 9.11) and re-issuing the=0A=
>     Destination Up message.=0A=
>=0A=
> Why have this restriction?  It seems odd for this data item to have=0A=
> different behavior than all of the other similar ones.=0A=
>=0A=
> If the restriction is kept, then the definition of the data item may need=
=0A=
> adjusting.  The flags field indicates "whether this is a new or existing=
=0A=
> subnet address (1), or a withdrawal of a subnet address (0)," but the=0A=
> above paragraph rules out the possibility of withdrawal.  So this is an=
=0A=
> option that can never be exercised, which is confusing.  Perhaps you can=
=0A=
> keep the flags field for future extensibility, but just not define any=0A=
> flags for now.=0A=
=0A=
I believe you have found some legacy text.  The restriction is not =0A=
supposed to be there any more, hence the Add/Drop indicator.  I will =0A=
correct the text.=0A=
=0A=
=0A=
>=0A=
> -- When the session initialization handshake completes, it seems like a=
=0A=
> good idea for the protocol to require each peer to send all of its=0A=
> currently-up destinations to the other peer.  If they don't, the protocol=
=0A=
> can get into an endless cycle of terminating and re-establishing the=0A=
> session (we have seen this):=0A=
>=0A=
> Peer A and B start a session=0A=
> Peer A sends Destination Up X to B=0A=
> something happens to terminate the session (some other error, for example=
)=0A=
> Peer A and B restart the session=0A=
> Peer A sends Destination UpDATE X to B=0A=
> Peer B terminates the session because it's never heard of destination X=
=0A=
>=0A=
> Peer A and B restart the session...=0A=
>=0A=
> Peer A made a mistake by sending an Update before an Up.  Requiring a=0A=
> database dump of all existing destinations to your new peer avoids this=
=0A=
> mistake.  You could instead track which destinations you've send to each=
=0A=
> peer, and make sure that any Update is preceded by Up, but that=0A=
> complicates the implementation.  Anyway, your peer probably needs to know=
=0A=
> the state of your world up front.  If you're not telling a peer about a=
=0A=
> known destination, it seems likely that routing is not going to work as=
=0A=
> you expect.=0A=
=0A=
This is a very good point.  I have always assumed that an implementation =
=0A=
dumps its destination state after session initialization, as the rules =0A=
specify that one cannot have an Update without a prior Up on a session. =0A=
  I will double check the text to see if there is a good place to =0A=
clarify this.=0A=
=0A=
>=0A=
>=0A=
> --Remove the normative reference to the credit windowing extension if thi=
s=0A=
> really gates progress on DLEP.=0A=
=0A=
We would like both drafts to progress in lock-step unless the WG really =0A=
doesn't want to.=0A=
=0A=
>=0A=
> Hope this helps.=0A=
=0A=
Yes it does!=0A=
=0A=
Rick=0A=


From nobody Mon Nov 23 08:59:52 2015
Return-Path: <vmercieca0@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 70DF01A90B4 for <manet@ietfa.amsl.com>; Mon, 23 Nov 2015 08:59:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.251
X-Spam-Level: *
X-Spam-Status: No, score=1.251 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, J_CHICKENPOX_52=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 cbsfL-IR9IRK for <manet@ietfa.amsl.com>; Mon, 23 Nov 2015 08:59:47 -0800 (PST)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AE091A90B7 for <manet@ietf.org>; Mon, 23 Nov 2015 08:59:46 -0800 (PST)
Received: by lfs39 with SMTP id 39so111919685lfs.3 for <manet@ietf.org>; Mon, 23 Nov 2015 08:59:44 -0800 (PST)
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 :content-type; bh=DKHYPDvvxBU7oLv1z8cLdVHJdzk4dEyXQQYUHlsIGKI=; b=t63z+xfxHy/mMKKEtLEgfB4QxGs4YlabyC4d40seb82NVfFMeGHzZTak3MDYxHuwkB NEEsZ/kGzd/2fdkuP0+aIspxAkF+xnQ28fI0/i0lv4NZmRMYBCczIj7He6lDYJFmNNHp woXQEFoMN3J25NYQWqcT5bpfhs9WUBJ90pbvNJRjXWwR3jHgzGAzKL/XL7STs4a8TwkN xl97Mw2hxBiWDYOYblcJZco/pOoUePND/+VwIWidQ7tSW3yKE33EoU3AOBNLov1cdjk0 /YWXE3nHs1k6R5SZeSGJzOjE9qR0P5vybK7n1Xix2/43QYnNVm6ZE6PYRg9TT2fhhQN9 R6Ow==
MIME-Version: 1.0
X-Received: by 10.25.79.17 with SMTP id d17mr11574964lfb.40.1448297984694; Mon, 23 Nov 2015 08:59:44 -0800 (PST)
Received: by 10.112.126.136 with HTTP; Mon, 23 Nov 2015 08:59:44 -0800 (PST)
In-Reply-To: <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com>
Date: Mon, 23 Nov 2015 16:59:44 +0000
Message-ID: <CAAePS4BVMBHyETCoo1NzHVaGSkdqgTfOciZ_6vwRNxDDTRiFZQ@mail.gmail.com>
From: Victoria Mercieca <vmercieca0@gmail.com>
To: manet <manet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11406b50e8374f05253826b9
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/eKSlEkWDcliXRV_qGL6GC1VMnYM>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Nov 2015 16:59:51 -0000

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

Hi again,

Regarding the comments on bidirectionality and acks, from Thomas Clausen's
email...specifically:
* "Also on buffering, I am wondering if the "start delivering buffered
packets" conditions (penultimate paragraph in 6.6, and of course through
the processing sections) is sufficient; I suspect that the condition "When
a valid route is installed" is not sufficient - that there are situations
where a routing table entry is installed, but the complete route is not
available or is not bidirectional?This obviously is related to RREP_Ack
being hop-by-hop and not end-to-end....*"


Thomas is right about hop-by-hop RREP_Ack. For intermediate nodes who
install a route to OrigAddr based on a one-hop RREP_Ack from their next hop
toward OrigAddr, it's not guaranteed that the complete route to OrigAddr is
available. Since the route is valid, the router may start forwarding data
packets to OrigAddr. An issue occurs if data packets are forwarded to
intermediate routers before the intermediate router installs a valid route.
If this happened, those data packets would be dropped and RERRs generated
(and regenerated toward the source of the data packets by any router using
it), and the route to OrigAddr would be removed at some but maybe not all
of the routers that installed it. A new RREQ would then have to go out on
behalf of the source of the traffic. So this problem would eventually fix
itself....but not without some dropped packets, RERRs, and a new RREQ/RREP
cycle. But there was a suggestion that this issue might be seen so
infrequently in practise that the overhead required to avoid this issue is
not worth it (i.e. the extra control traffic of acknowledging every link in
every route ever requested, even when some links are already known to be
bidirectional).

If you disagree, then we need to make RREP_Ack end-to-end and accept the
fact that this will result in many more RREP_Ack messages being generated
than in the current version.

Kind regards,
Victoria.

On Thu, Nov 19, 2015 at 4:09 PM, Victoria Mercieca <vmercieca0@gmail.com>
wrote:

>
> Hi Thomas and Christopher,
>
> Thank you for your comments.  If I may address just one point for starter=
s
> - regeneration vs forwarding. We use the term regeneration since forwardi=
ng
> seems inappropriate when the message content changes at each hop.
>
> The changes we make to the message content are:
>
> 1) We change the metric so that each router along the path learns a route
> from the message, with the metric associated with the path up to that poi=
nt
> 2) AckReq only applies between hops, so needs to be removed at each hop,
> and a new AckReq element may need to be added for the next hop.
> 3) ValidityTime could potentially be added by any intermediate router tha=
t
> wishes to limit the time it will forward packets on the route.
> 4) Stripping out Unreachable Addresses from RERR which did not affect our
> route set.
>
> Can we really use the term "forwarding" if we are changing the metric
> value, adding a validity time, adding/removing AckReq or removing address=
es
> and their associated TLVs?
>
> Further, in reply to the comment about use of the msg-hop-count and
> msg-hop-limit fields, I think it does not matter that a message only
> travels one hop in that particular form, with that exact set of informati=
on
> enclosed. Hop limit and hop count are part of the message and used by the
> routing protocol, and so they refer to the multi-hop path that the AODVv2
> message will follow, indicating when not to regenerate any further. So
> AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit the
> number of hops across which it will regenerate a packet so as to "prevent
> messages from endlessly circulating in a MANET".
>
> Kind regards,
> Victoria.
>
> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <
> christopher.dearlove@gmail.com> wrote:
>
>> I've not had time to look at either yet, though I hope to review DLEP
>> very soon.
>>
>> But this has made me think about the RFC 6621 reference in AODVv2. It's
>> always been clear this has been rather a throwaway comment that needed
>> thought, but until now I hadn't really given it any.
>>
>> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's
>> consider each on turn.
>>
>> AODVv2 is in the RFC 5444 structure. As has been noted on many occasions=
,
>> AOVDVv2 gets to use messages, but packets are not in its competence.
>>
>> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.
>> It's about whether or not to forward them. But RFC 5444 packets aren't j=
ust
>> not forwarded in unchanged IP packets, they aren't even forwarded at all=
.
>> They are each a single hop construct, and if a message is forwarded (whi=
ch
>> is by the routing protocol, as far as RFC 5444 is concerned, it's a new
>> message) it will be in a new packet, with possibly new companions.
>>
>> If AODVv2 wants to use a more efficient flooding process, it needs one a=
t
>> the message level. Now an example of that exists - the mechanism on RFC
>> 7181. Unfortunately we didn't break that out as a separate draft (we wou=
ld
>> have liked to, but there were reasons we didn't).
>>
>> And even if (by reference or other means) it were used - or some related
>> mechanism such as a CDS - that processing/forwarding mechanism assumes y=
ou
>> have defined MPRs (or similarly, that you have defined a CDS). And that
>> needs a local exchange of information, such as NHDP's HELLO messages (an=
d
>> the rest of NHDP) augmented with RFC 7181's MPR TLV (though only the
>> flooding bit is needed).
>>
>> In other words, taking some real work to define. And also raising a
>> question for the WG - why do we want a reactive protocol? The main
>> attraction as I see it is the "if you're not doing anything, you're not
>> transmitting" property. Which adding this voids. Of course maybe the WG
>> doesn't value that. Or it is acceptable as an option. But if so it needs=
 to
>> be an option that all routers use, or none. And if all, compatibly. (MPR
>> flooding allows different MPR selection algorithms - but only as long as
>> they satisfy the fundamental MPR algorithm properties.)
>>
>> In short, RFC 6621 must go. The alternative is nothing, or significant
>> work.
>>
>> --
>> Christopher Dearlove
>> christopher.dearlove@gmail.com (iPhone)
>> chris@mnemosyne.demon.co.uk (home)
>>
>> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote:
>>
>> Dear all,
>>
>> I have started looking through the recently
>> updated draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not =
to
>> have had a blow-by-bow comeback to the previous review comments  - would
>> have made it a somewhat easier task to check if all have been addressed =
or
>> not.
>>
>> But, I will work through it and produce a detailed review - but from my
>> first quick read-through there're a couple of issue that jumped at me as
>> worth bringing forward on a more global level already.
>>
>> The first relates to  how RREQs are forwarded -- or, more generally, are
>> not.
>>
>> The protocol currently talks about "message is regenerated" rather than
>> "forwarded". I have understood that this means that a RREQ is actually n=
ot
>> an "end to end" entity, but is a "hop by hop" entity.
>>
>> First, that is a curious design choice, is there any reason why this is
>> so considered?
>>
>> Second, if a RREQ message is hop-by-hop only, then I do not think that
>> the use of the RFC5444 hop-limit/hop-count fields is appropriate.
>>
>> Third, the statement in section 6.5 on the use of RFC6621 is incorrect i=
n
>> two ways: RFC6621 does specify how messages are *forwarded* (but, as
>> discussed above, you are not forwarding messages).
>>
>> More seriously, this paragraph is incorrect:
>>
>>
>> "Implementations MAY choose to employ techniques to reduce the number
>>    of multicast messages sent.  Use of [RFC6621 <https://tools.ietf.org/=
html/rfc6621>] in deployments is
>>    recommended.  Employing [RFC6621 <https://tools.ietf.org/html/rfc6621=
>] in a subset of the operational
>>    AODVv2 routers in a network, or configuring different algorithms on
>>    different routers, will not cause interoperability issues, but will
>>    reduce the effectiveness of the multicast reduction scheme."
>>
>>
>> Different routers using different relay selection algorithms in the same
>> network will not *just* cause loss of efficiency, but *will* cause
>> interoperability issues.
>>
>> For example if "router A" decides to suppress its message relaying
>> because it estimates that "router B" provides sufficient coverage - and
>> conversely "router B" suppresses relaying for the same reason: neither A
>> nor B would relay, and so any routers reachable only via A and B would n=
ot
>> be covered.
>>
>> This is not a far-sought example: it can be as simple as A and B simply
>> using self-selecting relay algorithms with different tie-breakers.
>>
>> In short: I think that the whole message flooding/regeneration part
>> requires serious work.
>>
>> The second issue is that I also suspect that there is some issue with
>> buffering, or rather with how it is specified; starting in section 6.6, =
I
>> am not sure that leaving that as "a matter of policy at each router" is
>> entirely right.
>>
>> Also on buffering, I am wondering if the "start delivering buffered
>> packets" conditions (penultimate paragraph in 6.6, and of course through
>> the processing sections) is sufficient; I suspect that the condition "Wh=
en
>> a valid route is installed" is not sufficient - that there are situation=
s
>> where a routing table entry is installed, but the complete route is not
>> available or is not bidirectional?This obviously is related to RREP_Ack
>> being hop-by-hop and not end-to-end....
>>
>> Either way, the parts of the specification that relate to buffering
>> contain a mixture of normative and non-normative verbiage (a lot of "can=
"
>> but also a lot of MUST/SHOULD) which I think could do with a tightening =
up.
>>
>> But....is buffering even something that should be specified by this
>> document? It does not impact interoperability and it interferes
>> substantially with transport and congestion control, and I am not sure t=
hat
>> we understand the consequences (I am not convinced that the claims in th=
e
>> document on benefits to TCP are substantiated or even true).
>>
>> As I indicated, a complete review will follow, but I thought that these
>> was a global enough topics to call out and get engineered right.
>>
>> Thomas
>>
>> PS: I remain convinced that the security considerations section is
>> insufficient ; I will try to articulate my thoughts on why that is, but =
for
>> starters looking at the recently raised (by somebody else, the Chris
>> replied) AODV security questions would probably be helpful
>>
>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote:
>>
>> Hello WG participants =E2=80=93
>>
>>
>>
>> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 1=
6
>> (DLEP). The co-authors and the chairs ask that you please take some time=
 to
>> review and comment on the new submissions.
>>
>>
>>
>> Regards,
>>
>> Stan
>>
>>
>>
>>
>>
>> _____________________________________________________
>> This electronic message and any files transmitted with it contains
>> information from iDirect, which may be privileged, proprietary
>> and/or confidential. It is intended solely for the use of the individual
>> or entity to whom they are addressed. If you are not the original
>> recipient or the person responsible for delivering the email to the
>> intended recipient, be advised that you have received this email
>> in error, and that any use, dissemination, forwarding, printing, or
>> copying of this email is strictly prohibited. If you received this email
>> in error, please delete it and immediately notify the sender.
>> _____________________________________________________
>>
>> _______________________________________________
>> 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
>>
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>
>>
>
>

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

<div dir=3D"ltr">Hi again,<br><br>Regarding the comments on bidirectionalit=
y and acks, from Thomas Clausen&#39;s
        email...specifically:<i><br>
          &quot;<span>Also on buffering, I am wondering if the &quot;start
            delivering buffered packets&quot; conditions (penultimate
            paragraph in 6.6, and of course through the processing
            sections) is sufficient; I suspect that the condition &quot;Whe=
n
            a valid route is installed&quot; is not sufficient - that there
            are situations where a routing table entry is installed, but
            the complete route is not available or is not
            bidirectional?This obviously is related to RREP_Ack being
            hop-by-hop and not end-to-end....</span></i>&quot;<br><div><i>
              <br></i></div><div><br>Thomas is right about hop-by-hop RREP_=
Ack. For intermediate nodes who install a route to OrigAddr based on a one-=
hop RREP_Ack from their next hop toward OrigAddr, it&#39;s not guaranteed t=
hat the complete route to OrigAddr is available. Since the route is valid, =
the router may start forwarding data packets to OrigAddr. An issue occurs i=
f data packets
            are forwarded to intermediate routers before the
            intermediate router installs a valid route. If this happened, t=
hose data packets would be dropped and RERRs generated (and regenerated tow=
ard the source of the data packets by any router using it), and the route t=
o OrigAddr would be removed at some but maybe not all of the routers that i=
nstalled it. A new RREQ would then
            have to go out on behalf of the source of the traffic. So
            this problem would eventually fix itself....but not without
some dropped packets, RERRs, and a new RREQ/RREP cycle. But there was a sug=
gestion that this
            issue might be seen so infrequently in practise that the
overhead required to avoid this issue is not worth it (i.e. the extra contr=
ol traffic of acknowledging every link in every route ever requested, even =
when some links are already known to be bidirectional).<br><br></div><div>I=
f you disagree, then we need to make RREP_Ack end-to-end and accept the fac=
t that this will result in many more RREP_Ack messages being generated than=
 in the current version.<br></div><div><br></div><div>Kind regards,<br></di=
v><div>Victoria.<br></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Nov 19, 2015 at 4:09 PM, Victoria Mercieca <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:vmercieca0@gmail.com" target=3D"_blank">vm=
ercieca0@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div class=3D"HOEnZb"><div class=3D"h5"><div dir=3D"ltr"><br><div class=3D"=
gmail_quote"><div dir=3D"ltr"><p dir=3D"ltr">Hi Thomas and Christopher,</p>
<p dir=3D"ltr">Thank you for your comments.=C2=A0 If I may address just one=
=20
point for starters - regeneration vs forwarding. We use the term=20
regeneration since forwarding seems inappropriate when the message=20
content changes at each hop.</p>
<p dir=3D"ltr">The changes we make to the message content are:</p>
<p dir=3D"ltr">1) We change the metric so that each router along the path=
=20
learns a route from the message, with the metric associated with the=20
path up to that point<br>
2) AckReq only applies between hops, so needs to be removed at each hop,
 and a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router=20
that wishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our r=
oute set.</p>
<p dir=3D"ltr">Can we really use the term &quot;forwarding&quot; if we are =
changing=20
the metric value, adding a validity time, adding/removing AckReq or=20
removing addresses and their associated TLVs?</p>
<p dir=3D"ltr">Further, in reply to the comment about use of the=20
msg-hop-count and msg-hop-limit fields, I think it does not matter that a
=20
message only travels one hop in that particular form, with that exact=20
set of information enclosed. Hop limit and hop count are part of the=20
message=20
and used by the routing protocol, and so they=20
refer to the multi-hop path that the AODVv2 message will follow,=20
indicating when not to regenerate any further. So=20
AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit=20
the number of hops across which it will regenerate a packet so as to=20
&quot;prevent messages from endlessly circulating in a MANET&quot;. </p>
<p dir=3D"ltr">Kind regards,<br>
Victoria.</p></div><div><div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <span dir=
=3D"ltr">&lt;<a href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_b=
lank">christopher.dearlove@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div dir=3D"auto"><div>I&#39;ve not had time to look at e=
ither yet, though I hope to review DLEP very soon.</div><div><br></div><div=
>But this has made me think about the RFC 6621 reference in AODVv2. It&#39;=
s always been clear this has been rather a throwaway comment that needed th=
ought, but until now I hadn&#39;t really given it any.</div><div><br></div>=
<div>And it doesn&#39;t work. RFC 6621 is fundamentally unusable here. Let&=
#39;s consider each on turn.=C2=A0</div><div><br></div><div>AODVv2 is in th=
e RFC 5444 structure. As has been noted on many occasions, AOVDVv2 gets to =
use messages, but packets are not in its competence.</div><div><br></div><d=
iv>RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.=
 It&#39;s about whether or not to forward them. But RFC 5444 packets aren&#=
39;t just not forwarded in unchanged IP packets, they aren&#39;t even forwa=
rded at all. They are each a single hop construct, and if a message is forw=
arded (which is by the routing protocol, as far as RFC 5444 is concerned, i=
t&#39;s a new message) it will be in a new packet, with possibly new compan=
ions.</div><div><br></div><div>If AODVv2 wants to use a more efficient floo=
ding process, it needs one at the message level. Now an example of that exi=
sts - the mechanism on RFC 7181. Unfortunately we didn&#39;t break that out=
 as a separate draft (we would have liked to, but there were reasons we did=
n&#39;t).</div><div><br></div><div>And even if (by reference or other means=
) it were used - or some related mechanism such as a CDS - that processing/=
forwarding mechanism assumes you have defined MPRs (or similarly, that you =
have defined a CDS). And that needs a local exchange of information, such a=
s NHDP&#39;s HELLO messages (and the rest of NHDP) augmented with RFC 7181&=
#39;s MPR TLV (though only the flooding bit is needed).</div><div><br></div=
><div>In other words, taking some real work to define. And also raising a q=
uestion for the WG - why do we want a reactive protocol? The main attractio=
n as I see it is the &quot;if you&#39;re not doing anything, you&#39;re not=
 transmitting&quot; property. Which adding this voids. Of course maybe the =
WG doesn&#39;t value that. Or it is acceptable as an option. But if so it n=
eeds to be an option that all routers use, or none. And if all, compatibly.=
 (MPR flooding allows different MPR selection algorithms - but only as long=
 as they satisfy the fundamental MPR algorithm properties.)</div><div><br><=
/div><div>In short, RFC 6621 must go. The alternative is nothing, or signif=
icant work.<br><br><div>-- =C2=A0<span><font color=3D"#888888"><div>Christo=
pher Dearlove</div><div><a href=3D"mailto:christopher.dearlove@gmail.com" t=
arget=3D"_blank">christopher.dearlove@gmail.com</a> (iPhone)</div><div><a h=
ref=3D"mailto:chris@mnemosyne.demon.co.uk" target=3D"_blank">chris@mnemosyn=
e.demon.co.uk</a> (home)</div></font></span></div></div><div><div><div><br>=
On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a href=3D"mailto:ietf@thomasc=
lausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt; wrote:<br><br>=
</div><blockquote type=3D"cite"><div>
<div>Dear all,</div><div><br></div><div>I have started looking through the =
recently updated=C2=A0draft-ietf-manet-aodvv2-12. A lot has changed, and I =
regret not to have had a blow-by-bow comeback to the previous review commen=
ts =C2=A0- would have made it a somewhat easier task to check if all have b=
een addressed or not.</div><div><br></div><div>But, I will work through it =
and produce a detailed review - but from my first quick read-through there&=
#39;re a couple of issue that jumped at me as worth bringing forward on a m=
ore global level already.</div><div><br></div><div>The first relates to =C2=
=A0how RREQs are forwarded -- or, more generally, are not.</div><div><br></=
div><div>The protocol currently talks about &quot;message is regenerated&qu=
ot; rather than &quot;forwarded&quot;. I have understood that this means th=
at a RREQ is actually not an &quot;end to end&quot; entity, but is a &quot;=
hop by hop&quot; entity.=C2=A0</div><div><br></div><div>First, that is a cu=
rious design choice, is there any reason why this is so considered?</div><d=
iv><br></div><div>Second, if a RREQ message is hop-by-hop only, then I do n=
ot think that the use of the RFC5444 hop-limit/hop-count fields is appropri=
ate.</div><div><br></div><div>Third, the statement in section 6.5 on the us=
e of RFC6621 is incorrect in two ways: RFC6621 does specify how messages ar=
e *forwarded* (but, as discussed above, you are not forwarding messages).</=
div><div><br></div><div>More seriously, this paragraph <span style=3D"backg=
round-color:rgba(255,255,255,0)">is incorrect</span>:</div><div><pre style=
=3D"margin-top:0px;margin-bottom:0px"><font face=3D"UICTFontTextStyleTallBo=
dy"><span style=3D"white-space:normal;background-color:rgba(255,255,255,0)"=
><br></span></font></pre><pre style=3D"margin-top:0px;margin-bottom:0px"><b=
lockquote type=3D"cite"><font face=3D"UICTFontTextStyleTallBody"><span styl=
e=3D"white-space:normal;background-color:rgba(255,255,255,0)">&quot;Impleme=
ntations MAY choose to employ techniques to reduce the number
   of multicast messages sent.  Use of [<a href=3D"https://tools.ietf.org/h=
tml/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;" target=
=3D"_blank">RFC6621</a>] in deployments is
   recommended.  Employing [<a href=3D"https://tools.ietf.org/html/rfc6621"=
 title=3D"&quot;Simplified Multicast Forwarding&quot;" target=3D"_blank">RF=
C6621</a>] in a subset of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction scheme.&quot;</span>=
</font><span style=3D"font-size:19px">
</span></blockquote></pre></div><div><br></div><div>Different routers using=
 different relay selection algorithms in the same network will not *just* c=
ause loss of efficiency, but *will* cause interoperability issues.</div><di=
v><br></div><div>For example if &quot;router A&quot; decides to suppress it=
s message relaying because it estimates that &quot;router B&quot; provides =
sufficient coverage - and conversely &quot;router B&quot; suppresses relayi=
ng for the same reason: neither A nor B would relay, and so any routers rea=
chable only via A and B would not be covered.</div><div><br></div><div>This=
 is not a far-sought example: it can be as simple as A and B simply using s=
elf-selecting relay algorithms with different tie-breakers.</div><div><br><=
/div><div>In short: I think that the whole message flooding/regeneration pa=
rt requires serious work.</div><div><br></div><div><div><span style=3D"back=
ground-color:rgba(255,255,255,0)">The second issue is that I also suspect t=
hat there is some issue with buffering, or rather with how it is specified;=
 starting in section 6.6, I am not sure that leaving that as &quot;a matter=
 of policy at each router&quot; is entirely right.=C2=A0</span></div><div><=
span style=3D"background-color:rgba(255,255,255,0)"><br></span></div><div><=
span style=3D"background-color:rgba(255,255,255,0)">Also on buffering, I am=
 wondering if the &quot;start delivering buffered packets&quot; conditions =
(penultimate paragraph in 6.6, and of course through the processing section=
s) is sufficient; I suspect that the condition &quot;When a valid route is =
installed&quot; is not sufficient - that there are situations where a routi=
ng table entry is installed, but the complete route is not available or is =
not bidirectional?This obviously is related to RREP_Ack being hop-by-hop an=
d not end-to-end....</span></div><div><span style=3D"background-color:rgba(=
255,255,255,0)"><br></span></div><div><span style=3D"background-color:rgba(=
255,255,255,0)">Either way, the parts of the specification that relate to b=
uffering contain a mixture of normative and non-normative verbiage (a lot o=
f &quot;can&quot; but also a lot of MUST/SHOULD) which I think could do wit=
h a tightening up.=C2=A0</span></div><div><span style=3D"background-color:r=
gba(255,255,255,0)"><br></span></div><div><span style=3D"background-color:r=
gba(255,255,255,0)">But....is buffering even something that should be speci=
fied by this document? It does not impact interoperability and it interfere=
s substantially with transport and congestion control, and I am not sure th=
at we understand the consequences (I am not convinced that the claims in th=
e document on benefits to TCP are substantiated or even true).</span></div>=
<div><span style=3D"background-color:rgba(255,255,255,0)"><br></span><div>A=
s I indicated, a complete review will follow, but I thought that these was =
a global enough topics to call out and get engineered right.</div></div></d=
iv><div><br></div><div>Thomas</div><div><br></div><div>PS: I remain convinc=
ed that the security considerations section is insufficient ; I will try to=
 articulate my thoughts on why that is, but for starters looking at the rec=
ently raised (by somebody else, the Chris replied) AODV security questions =
would probably be helpful</div><div><div></div></div><div><br>On 10 Nov 201=
5, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sratliff@idirect.net" t=
arget=3D"_blank">sratliff@idirect.net</a>&gt; wrote:<br><br></div><blockquo=
te type=3D"cite"><div>






<div>
<p class=3D"MsoNormal">Hello WG participants =E2=80=93 <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">The above referenc=
ed drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (DLEP). The co-auth=
ors and the chairs ask that you please take some
 time to review and comment on the new submissions. <u></u><u></u></span></=
p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>=C2=A0<u></=
u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Regards,<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Stan<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>=C2=A0<u></=
u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<br><span style=3D"font-size:8pt;font-family:Arial,sans-serif;color:#003366=
">_____________________________________________________<br>This electronic =
message and any files transmitted with it contains<br>information from iDir=
ect, which may be privileged, proprietary<br>and/or confidential. It is int=
ended solely for the use of the individual<br>or entity to whom they are ad=
dressed. If you are not the original<br>recipient or the person responsible=
 for delivering the email to the<br>intended recipient, be advised that you=
 have received this email<br>in error, and that any use, dissemination, for=
warding, printing, or<br>copying of this email is strictly prohibited. If y=
ou received this email<br>in error, please delete it and immediately notify=
 the sender.<br>_____________________________________________________</span=
>

</div></blockquote><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/listinfo/manet" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a></span><br><=
/div></blockquote></div></blockquote><blockquote type=3D"cite"><div><span>_=
______________________________________________</span><br><span>manet mailin=
g 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/=
listinfo/manet" target=3D"_blank">https://www.ietf.org/mailman/listinfo/man=
et</a></span><br></div></blockquote></div></div></div><br>_________________=
______________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>
</div></div></div><br></div>
</div></div></blockquote></div><br></div>

--001a11406b50e8374f05253826b9--


From nobody Tue Nov 24 06:11:37 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ACDD1A6FD0; Tue, 24 Nov 2015 06:11:36 -0800 (PST)
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: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151124141136.31172.3032.idtracker@ietfa.amsl.com>
Date: Tue, 24 Nov 2015 06:11:36 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/w5x9mCwnA34AyKEXNAx0wk3LMtk>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-10.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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 14:11:36 -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           : Packet Sequence Number based directional airtime metric for OLSRv2
        Authors         : Henning Rogge
                          Emmanuel Baccelli
	Filename        : draft-ietf-manet-olsrv2-dat-metric-10.txt
	Pages           : 19
	Date            : 2015-11-24

Abstract:
   This document specifies an Directional Airtime (DAT) 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:
https://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-dat-metric-10


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 Tue Nov 24 06:21:58 2015
Return-Path: <rja.lists@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 A85D51A7003 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 06:21:56 -0800 (PST)
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 EBOxahLOzOM2 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 06:21:55 -0800 (PST)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 969141A6FF8 for <manet@ietf.org>; Tue, 24 Nov 2015 06:21:55 -0800 (PST)
Received: by qgea14 with SMTP id a14so11185141qge.0 for <manet@ietf.org>; Tue, 24 Nov 2015 06:21:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=rE5bAxu0kosR01tSule6UvwBfUfWCN0wqM3ADAslICA=; b=vzL0xvFsR3rHacNrapcq1svUG8NHw+8qLQKAPsA3vgwHZ6H3OYDtBqAfUCSSjNB6vS Y8vdSbRkRCPMT+rjXTU+j6rVmCGOFr73DsFfhnU1igwHwpOfO8/x89Lc7pnMWNNIUGTo GhT/TvNgz7BVkY7YR9oHlOlJIed3Pyj1/9rCbybMUC4HxQcf2TZv4bZVkxz+UgtHA+DF SvyD37a+S0yi/aGV6R7Y84SpTEnGCDATQI5uouIzu7c0Ez2P5GPN/ICnL+AOt+x4Xgjs PZEn5QglIocz/xT262v0kdoayCgfYyItRPpevp85jQd9lU2hiGfJLp1UIbrHzWaRJDJr nEGQ==
X-Received: by 10.140.32.200 with SMTP id h66mr32921964qgh.16.1448374914795; Tue, 24 Nov 2015 06:21:54 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id y95sm4265502qgd.27.2015.11.24.06.21.54 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 06:21:54 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <6D5E138A-CA49-4516-84B1-9A2DEFE6E014@gmail.com>
Date: Tue, 24 Nov 2015 09:21:53 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/xlh_ke7SJoy7S8dH6E61eG3NSK4>
Subject: [manet] DLEP-17: Threaded feedback follows
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 14:21:56 -0000

I will be sending separately threaded feedback on
DLEP-17 starting in a moment.

I generally like the document, and think it is much
improved.  However, there still are several areas where 
the draft either lacks clarity or is not written in 
an IETF-consistent/compliant way.

Yours,

Ran


From nobody Tue Nov 24 06:57:04 2015
Return-Path: <rja.lists@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 A7B011A86FD for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 06:57:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 Srs0YKsU2uWA for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 06:57:01 -0800 (PST)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0624A1A854C for <manet@ietf.org>; Tue, 24 Nov 2015 06:57:01 -0800 (PST)
Received: by qgeb1 with SMTP id b1so12018289qge.1 for <manet@ietf.org>; Tue, 24 Nov 2015 06:56:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=8PgXgGDpf/sG1tqybBsXxiTlKz+eZ4PTyLQQE4m8ONo=; b=prL4iOBc7YG6S7U2IPAkp8fA/BDV4Vsd+0ybLMXNGDht/bMSRO2rxxGg7sEy9VlkKp B/OcBTDWWshEeTuSrpdUL1HfE4R8wa2Fxg035tn5ERbMfK09H2ex4KVxeuJdUemY1J8Z 5/i1E9Oon/L9Ng19Gs0AWvKEC9qZlrPYNL3Z0h8HqFXdiNV/eqySrPI/UbcHK/hoyEdb 2Za2WrBeD4zB6arnQvdbZYbSl+LI+TyhyB25uirQWOYhPz4p8IDTx8KU3f05sMRyJawA k6nRm0iTi9BiUbaS+XYXMTmy7eSHdwOb28vNTswnnMc/CHFcMzKT1GhAsChEqtYlmLdq xPVw==
X-Received: by 10.140.181.135 with SMTP id c129mr36002734qha.4.1448377010584;  Tue, 24 Nov 2015 06:56:50 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id z66sm4337385qka.13.2015.11.24.06.56.50 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 06:56:50 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com>
Date: Tue, 24 Nov 2015 09:56:49 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/YIBj3kDU9IyfKDM0Z54JUX8fDJE>
Subject: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 14:57:02 -0000

All,


The "Security Considerations=E2=80=9D text isn=E2=80=99t really =
adequate.

I suspect part of the problem is editorial.  I am supplying
candidate replacement text that I believe will be sufficient
for the draft to pass the IETF Security Area review.


Background:
  In the IETF, =E2=80=9Cimplement=E2=80=9D generally refers to code =
available
  to execute a feature in a product, while =E2=80=9Cuse=E2=80=9D or =
=E2=80=9Cdeploy=E2=80=9D=20
  refers to the operational decision of how to configure a product
  when installing it in an actual physical network. =20

  I realize that some people (incorrectly) use =E2=80=9Cimplement=E2=80=9D=
 to refer
  to deployment, but IETF protocol specifications generally try=20
  to avoid that confusion.

  Also, unlike some other standards bodies, the IETF doesn=E2=80=99t =
have a=20
  concept of =E2=80=9Cconformance testing=E2=80=9D.  Products that claim =
to implement=20
  an RFC are expected to implement it completely and properly,=20
  but there are no IETF =E2=80=9Cprotocol police=E2=80=9D checking a =
product to see=20
  whether each detail was done correctly. =20

  Last, in the IETF, the long-standing custom is that =
=E2=80=9Cimplementation=E2=80=9D
  of security is mandatory, while =E2=80=9Cdeployment/use=E2=80=9D of =
security is
  optional.  The reasoning is that an operator best knows their own
  security risks, but if the implementation does not include the=20
  specified security mechanism (e.g. TLS) then (a) the implementation=20
  won=E2=80=99t be interoperable and/or (b) the user won=E2=80=99t be =
ABLE to deploy/use=20
  the security when they deem it appropriate.


Proposed New Text for Section 11, sub-heading 1:

	1. An attacker might pretend to be a DLEP peer, either at=20
           DLEP session initialization or by injection of messages=20
           once a session has been established, and/or


Also, the several paragraphs that begin with =E2=80=9CIf the modem and =
router are=E2=80=9D
ought to be rewritten.  Proposed New Text is:

        All DLEP implementations must also implement support for=20
        IETF TLS [RFC5246], so that an operator always is able to choose=20=

        to deploy TLS with DLEP when the operator deems that =
appropriate.  =20

        Use of DLEP with TLS, however, might not be needed in some=20
        DLEP deployments.  Additional guidance on TLS use with DLEP =
follows.

	When the modem and router are NOT both on the same layer-2
        link (e.g. IP subnetwork, Ethernet VLAN) then session messages
        could be altered by an off-link attacker in order to subvert the
        behavior of either or both DLEP participants.  In short,
        a man-in-the-middle attack by an off-link attacker is possible.
        In these situations, deployment and use of TLS with DLEP is=20
        RECOMMENDED.

        In some deployments, for example deployments that include a
        =E2=80=9CLayer-2 VPN=E2=80=9D connecting different sites, there =
might be a=20
        non-trivial risk of an on-link attacker.  Operators should=20
        carefully consider the details of their deployment and their =
local
        operational risk model. In situations where local risks warrant,=20=

        then deployment and use of TLS with DLEP is RECOMMENDED.


Lastly, the final paragraph as written is not really acceptable in the=20=

modern IETF.  Here is Proposed New Text:

	Deployment of DLEP does not change the security risks for the
        data plane (i.e. the data packets between a router and a modem).
        In circumstances where there is non-trivial risk of an on-link
        attacker, then the use of appropriate link-layer security =
mechanisms=20
        (e.g. IEEE MAC-layer security [IEEE 802.10, IEEE 802.1AE] for =
data=20
        packets between a router and a modem is RECOMMENDED.

Informational References probably should add:

	[IEEE 802.1AE] IEEE, Standard for Local and Metropolitan Area =
Networks:=20
                       Media Access Control (MAC) Security, IEEE, NJ, =
USA. 2006

	[IEEE 802.10]  IEEE, Standard for Local and Metropolitan Area =
Networks:
                       Interoperable LAN/MAN Security (SILS), IEEE, NJ, =
USA. 1992.

Yours,

Ran



From nobody Tue Nov 24 07:10:55 2015
Return-Path: <rja.lists@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 D28A61A873A for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:10:54 -0800 (PST)
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 ei3ZBd0Oobnm for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:10:53 -0800 (PST)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A47611A8740 for <manet@ietf.org>; Tue, 24 Nov 2015 07:10:53 -0800 (PST)
Received: by qgea14 with SMTP id a14so12235683qge.0 for <manet@ietf.org>; Tue, 24 Nov 2015 07:10:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=2NyDuej/v5Xa23w9eOyi0t/d+iNZ+kUrX+msVsYRTuk=; b=VtBanlkq/V7mmf6ptJnWnrUAuxiWGPpH8Nm2wOHT+F3plt2yf071zEtCkVX7nHuJII O7zRuiULnYBNLui3dC74x00ixWT4jZyApc1QTW+Pfvd3vT8V8AbdAvnokw0qaSrMf++N HnAZZtA2Ox38/tAwxbSBWwH3AvuIrz1v5k/umT4UJAeyJuub4Z89J5vyH6JUAKqCxs3I HrrfXF1S7twIu/FzqTdqaxrfhfpbuYgNNcEjhHCowmUBMasgrz3LLTD/N/fme2hW/Koe w1TojeX5/dSI7PosyX1br9orFkwJ684KImqpqhrjp8bPumhoi9HfLcccVO/ruz90PIwL 6ZUw==
X-Received: by 10.140.217.138 with SMTP id n132mr35677393qhb.26.1448377852874;  Tue, 24 Nov 2015 07:10:52 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id j89sm4298600qgj.35.2015.11.24.07.10.52 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 07:10:52 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <0352FCAD-F1EA-4A5F-AFAD-CB200484627F@gmail.com>
Date: Tue, 24 Nov 2015 10:10:51 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/SK5eXspU_98Y7ALqlPYLaJ89Ksg>
Subject: [manet] DLEP-17: Extensions
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 15:10:55 -0000

Extensions are more clear to me now, but the document itself
is not crystal clear.  So I propose adding additional text
to make their existence/use/concept crystal clear to a naive
reader of the DLEP specification.


Concern:
  Neither Section 1.0 nor Section 1.1 mention that DLEP is
  extensible.  This begs the question in the mind of the
  first-time reader and leads to a surprise when the reader
  reads about Extensions (e.g. in Section 5) before their
  existence has been mentioned and they have been defined.

Proposed additional text at the end of Section 1.1:

  While the base DLEP specification defined here is believed to be
  sufficient, DLEP is extensible as described in Section 6 below.
  A DLEP extension can be used to define new behaviors, message types,
  data items, and/or status codes.


Concern:
  While on-list clarifications have been helpful, the actual
  specification is not crystal clear about how Extensions work.
  I have paraphrased previous on-list comments from others to
  create the new paragraph below.

Proposed additional paragraph for Section 6:

  A single extension might contain zero or more new behaviors, zero or 
  more new message types, zero or more data items, and/or zero or more 
  new status codes.  A single extension MUST contain at least one new
  behavior, new message type, new data item, or new status code.


Yours,

Ran


From nobody Tue Nov 24 07:20:32 2015
Return-Path: <rja.lists@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 5BA901A874F for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:20:30 -0800 (PST)
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 IaZd586Gk6a1 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:20:29 -0800 (PST)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75EC21A8756 for <manet@ietf.org>; Tue, 24 Nov 2015 07:20:28 -0800 (PST)
Received: by qkas77 with SMTP id s77so6232014qka.0 for <manet@ietf.org>; Tue, 24 Nov 2015 07:20:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=6O4wBR6PGGzk0aRq0/3VyQ2ReJ2vG8c6n7TXuz/jPO0=; b=Uo2HAk6L9W4SFNy16JMURKbXo94mpnIMIxfm53ENaP4VDc0pY0vlQ5Xlsw5DEYIKeA 4ziAeZQ/VF91g1KJ4xtFiGtVyvTNlRo9KFIVDWuUV12pFd4qavsrqL2ecEsnz9zyJfau 3v9FM6JoiVTmFrgPmyiIk/3wHlV8FwjSbi+aAFXKnwBgfTvPrkyRtXi/4u74hx2Mn+IN 6ickwPleQROFj4pINmSz9ihoKA2jyUfePeZdFnaVvwLsta4Wc+3etmMaY0qwILaKK/Wf Bo9hh1NrjOG6MfDu4AVRmcMUotF0utXImHR1eA7NWbh+lX8L/2qG+N7zEG0muVoACwHp 653Q==
X-Received: by 10.55.74.145 with SMTP id x139mr34781957qka.9.1448378427572; Tue, 24 Nov 2015 07:20:27 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id u143sm2612159qka.35.2015.11.24.07.20.27 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 07:20:27 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C8E8891-D798-49F8-8AF0-DD0A35BA476E@gmail.com>
Date: Tue, 24 Nov 2015 10:20:26 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/8FIKYh7MITrON6W9NFcXhJL7-9E>
Subject: [manet] DLEP-17:  "Use TLS" flag is not secure
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 15:20:30 -0000

Section 10.2, page 38 (top) defines a =E2=80=9CUse TLS=E2=80=9D flag.

This design creates a security problem.  The issue is commonly
known as a =E2=80=9Cdowngrade attack=E2=80=9D, because a =
man-in-the-middle
attacker (whether on-link or off-link) simply clears that bit
to (incorrectly) indicate that TLS is not required.

I don=E2=80=99t see any way to fix this, but I am open-minded=20
if someone has a creative idea.

The absolute bare minimum for IETF approval would be that this
(easily exploited) vulnerability be disclosed BOTH within=20
Section 10.2 AND also in the Security Considerations of Section 11.

My guess is that the Security Area reviewer will say that this
is unacceptable protocol design. =20

So I=E2=80=99d prefer (and recommend) that we drop this =E2=80=9CUse =
TLS=E2=80=9D flag.

Maybe an alternate approach would be to create an informative
status code or signal (whichever) that a peer could send to
a would-be peer to indicate that non-TLS DLEP sessions are not
allowed. =20

While that proposed message could be intercepted/dropped by
an adversary, it is purely a status message. A good DLEP
implementation would attempt a DLEP+TLS session with its=20
intended peer anytime a DLEP w/o TLS session failed, so
the loss of the proposed message doesn=E2=80=99t create a security
vulnerability.

Yours,

Ran


From nobody Tue Nov 24 07:26:40 2015
Return-Path: <rja.lists@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 994F31A8780 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:26:37 -0800 (PST)
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 TFiTUEwEz7Yt for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:26:36 -0800 (PST)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D175F1A8785 for <manet@ietf.org>; Tue, 24 Nov 2015 07:26:35 -0800 (PST)
Received: by qgcc31 with SMTP id c31so12513548qgc.3 for <manet@ietf.org>; Tue, 24 Nov 2015 07:26:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=uPc3h9w+uSueewnN5RjTQdAgaSmxN7HYxVohr4FkdoY=; b=RA5Gg1Za8W+xkwPrQemtFERRRhazNr2SEXMnrNtKSOmvhjl4OlkEo6+V4yHbNHV6b/ MTfhYuWXnHJ8V0FuJPFsiCo7R/tv7smxEXRFGcjCQEFNLtZH31UVg+Q1ZHCNFXLFT1Ry eV5Pv+JIxbQhpyTCr2rJuacOpGhM4wWovWqtF7sx5uGfKBeP+vXs/2VJQqTwlU32OmxM YQxVqS425kZXeP0hPLzzvb3VqiGdizwxkcWmCTuqV8rSS0HVBixKjN3BuY9aaE37cXH7 kl987rE8NZ3VvWZr0MgaKmvz1xKMJ3sCpFz2PEIuuSOcJaSPciyByJPIsJaaBVx1X8M/ 2aYg==
X-Received: by 10.140.147.67 with SMTP id 64mr35624182qht.12.1448378794996; Tue, 24 Nov 2015 07:26:34 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id s65sm4292876qhb.39.2015.11.24.07.26.34 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 07:26:34 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <7496DF74-0C45-4500-9AB9-0A412463FFEC@gmail.com>
Date: Tue, 24 Nov 2015 10:26:34 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/FPxK9jn_IzIkvtFuBopisX9uvS8>
Subject: [manet] DLEP-17: timers not clearly defined
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 15:26:37 -0000

The current specification seems to define (at least) two timers:
	- Peer Discovery Timer (Appendix A)
	- Heartbeat Timer (Section 5.3.1 & 10.5)

However, these are implicitly defined, rather than being explicitly
defined.  Further, the Peer Discovery Timer is defined in an
Appendix, not in the main body of the specification. =20


REQUEST:  Please add a new Section named =E2=80=9CTimers=E2=80=9D.

It can be short, but it ought to define each timer that an =
implementation
ought to have, the semantics of each timer, the units (seconds ?) of =
each
timer, and pointers to the parts of the draft that define when/where/how
to use the timer(s). =20

Thanks very much.

Yours,

Ran



From nobody Tue Nov 24 07:31:49 2015
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 ABBA01A87F0 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:31:47 -0800 (PST)
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 FPBXeomS9Pw0 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:31:46 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B65CB1A8848 for <manet@ietf.org>; Tue, 24 Nov 2015 07:31:45 -0800 (PST)
Received: by wmec201 with SMTP id c201so214661665wme.0 for <manet@ietf.org>; Tue, 24 Nov 2015 07:31:44 -0800 (PST)
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=AQmh+RvBLHKXkM5qGGsRC+T0Y4pBRpEj+swhmKDEspE=; b=pv1SglCcccxnoG3mQptZfDVq0ZdU586D5UpdjVbETiBG/6DUp9Z4RqR+3n/n4rf7Gd EONG1KLZiIr1jhR9fH/JEEdX3FwjyreIVkVw+oG3wPuTxM1gh6fhfTIoVum3Tk+KTa2+ qLM0CqK46OyOnJ70mzlg7z115A+L2Amdc7Fgf56kqmdOxR7ccg9NMNxhPJQmR1LRXzwh +9aWyub5Z3Y0lG9h5Y8H7LBttKBuOX2DxA2AJVVw4TMfAsnrs9ubkai3b/SjIwocT/bx Xr7sPpPrDdSApRWvGApISCPHycDGEdo9g3ZDfgFpAbjX+al/fHlzzFiIhwv0CTZ0P3tt Ofsw==
X-Received: by 10.194.104.5 with SMTP id ga5mr37945065wjb.155.1448379104278; Tue, 24 Nov 2015 07:31:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Tue, 24 Nov 2015 07:31:14 -0800 (PST)
In-Reply-To: <3C8E8891-D798-49F8-8AF0-DD0A35BA476E@gmail.com>
References: <3C8E8891-D798-49F8-8AF0-DD0A35BA476E@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 24 Nov 2015 16:31:14 +0100
Message-ID: <CAGnRvuoeW8WV78Vp92G9QBmDnDvSSXPgjOK2e18kwUYdKUUBAQ@mail.gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Jczc7fuzOmo0mZniNVB4Fu2vgCU>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: "Use TLS" flag is not secure
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 15:31:47 -0000

On Tue, Nov 24, 2015 at 4:20 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
>
> Section 10.2, page 38 (top) defines a =E2=80=9CUse TLS=E2=80=9D flag.
>
> This design creates a security problem.  The issue is commonly
> known as a =E2=80=9Cdowngrade attack=E2=80=9D, because a man-in-the-middl=
e
> attacker (whether on-link or off-link) simply clears that bit
> to (incorrectly) indicate that TLS is not required.

The TLS bit is (I think) not about "use TLS" or "don't use TLS", its
just the bit that tells you what to expect on the IP/port combination.

If you clear the bit, the other side would try to connect to the TLS
socket with a default TCP connection, which will fail.

> I don=E2=80=99t see any way to fix this, but I am open-minded
> if someone has a creative idea.
>
> The absolute bare minimum for IETF approval would be that this
> (easily exploited) vulnerability be disclosed BOTH within
> Section 10.2 AND also in the Security Considerations of Section 11.
>
> My guess is that the Security Area reviewer will say that this
> is unacceptable protocol design.
>
> So I=E2=80=99d prefer (and recommend) that we drop this =E2=80=9CUse TLS=
=E2=80=9D flag.
>
> Maybe an alternate approach would be to create an informative
> status code or signal (whichever) that a peer could send to
> a would-be peer to indicate that non-TLS DLEP sessions are not
> allowed.
>
> While that proposed message could be intercepted/dropped by
> an adversary, it is purely a status message. A good DLEP
> implementation would attempt a DLEP+TLS session with its
> intended peer anytime a DLEP w/o TLS session failed, so
> the loss of the proposed message doesn=E2=80=99t create a security
> vulnerability.

I don't think there is any way between two parties that don't know
each other to establish a secure connection if BOTH of them support
non-secure communication AND a Man in the Middle controls all traffic
between the two parties.

The MITM could just drop everything that is security-related from the
communication.

Henning Rogge


From nobody Tue Nov 24 07:33:08 2015
Return-Path: <rja.lists@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 AEADF1A886F for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:33:07 -0800 (PST)
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 qt0e2pwqip5Q for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:33:06 -0800 (PST)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D09E1A8853 for <manet@ietf.org>; Tue, 24 Nov 2015 07:33:06 -0800 (PST)
Received: by qgec40 with SMTP id c40so12703262qge.2 for <manet@ietf.org>; Tue, 24 Nov 2015 07:33:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=qcrFUAUByGciRQ+n0esptOLQR77qjbXl1uBTJLOWwpc=; b=c9/I9Vsjlhy2Z5b9YknumwgO/ZHz934l80/Q99VWAUfS8a63GIPtephKoMqY7+JMxp d0KJS2NcgRDCQNO5dxzIZV5QQK2eP/IBtDm7da4XrMUouG2pT+xsg0TDmmYCGAOh2Z5u 8naVFT6cElLwPqxD8ToCnDby80cPP818zsCBE1/qW8eNRMPL30lOL9L9YTs5s5bk59l1 E7sfjwjItkk4UycNVOLVCuBUG2VRE1JuV16o4yu5wN4QraomG4qhju8nOCqEejRFTFac A7sz2sStp9QI+8OKBKg8gAMGChDk9exZyj6PcUlrG85pSmZuTp2TcL0NubxBccovAbqW Kc0Q==
X-Received: by 10.140.84.40 with SMTP id k37mr33398112qgd.33.1448379185682; Tue, 24 Nov 2015 07:33:05 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id w134sm4314284qha.0.2015.11.24.07.33.05 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 07:33:05 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C2E2E59-68FB-45A8-A24F-4F8AC6E3D1EB@gmail.com>
Date: Tue, 24 Nov 2015 10:33:04 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/mPdJHtdD1pgR78PPKh8vbQUQzDI>
Subject: [manet] DLEP-17:  well-known IPv4 link-local multicast 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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 15:33:08 -0000

At present, IANA Considerations only requests an IPv6=20
link-local multicast address.

We will need one also to be defined for IPv4 for IPv4 deployments
of DLEP.  I have drafted precise IANA-compliant text below, so this
should be easy to insert into the DLEP draft.


Proposed New Text:

12.9  DLEP IPv4 Link-local Multicast Address

  Please allocate 1 multicast address to DLEP from the =E2=80=9CIPv4 =
Multicast=20
  Address, Local Network Control Block=E2=80=9D registry for "DLEP =
Discovery Signals".



Yours,

Ran


From nobody Tue Nov 24 07:54:34 2015
Return-Path: <rja.lists@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 87A611A8A6B for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:54:32 -0800 (PST)
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 V1MxW7r17CQ1 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 07:54:31 -0800 (PST)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6620C1A8A4E for <manet@ietf.org>; Tue, 24 Nov 2015 07:54:31 -0800 (PST)
Received: by qgeb1 with SMTP id b1so13301234qge.1 for <manet@ietf.org>; Tue, 24 Nov 2015 07:54:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=o1f6pVaqeITid0wwSGPhIkdxwdSI4jIddv7hB0P/o9E=; b=QqC8inhgy9T7EPADNnJfmHt47Hk8CiX1j/+DpHaboTZFC/VaaAFE+vmWnnou4t6ySx qta0UCcuOQgE4jsgNmpWYXUXyUksJYAx8TWXAYxKA2vCNA3zjCVJ0i6rMydaIwXvmwzH IYmSngh2NzUsh0PsxLYjpSJyp6bmCJWj62J94VJDMFUCRGzVQ2RAMuHM3mRdTVph4Vb7 UWlUiHoJhq+NNATlcuGUul5+cmggbFZ8Ky0XUptUHbfWo2FrBUsrb2Cav3BIovvfIY2z QXlUFpzbeZe7Telhw2T9wamxInjr6UsT5DmYoPv/sihmSf4gBRfifsBR7p2/jC6fGuvf /2pw==
X-Received: by 10.141.1.193 with SMTP id c184mr8867745qhd.9.1448380470569; Tue, 24 Nov 2015 07:54:30 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id j89sm4339603qgj.35.2015.11.24.07.54.30 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 07:54:30 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <447C1544-14DF-40C3-BA23-97F4F146A374@gmail.com>
Date: Tue, 24 Nov 2015 10:54:29 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/sxDmfoJ_bDgr-FARtEnOLFXMQ90>
Subject: [manet] DLEP-17: error handling during "In-Session" state
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 15:54:32 -0000

Section 5.3 seems to talk about all of the expected behaviors,
which is great.

But what is the intended response behavior if one side of the=20
active DLEP session receives a (presumably unexpected) TCP Reset ?

It seems to me that Section 5.3 ought to say something about:

(a) whether a DLEP peer is allowed to just reset the DLEP TCP session.
    (Maybe it isn=E2=80=99t allowed to, from a DLEP perspective, which
    might be important to note so implementers know this.)

(b) how the other DLEP peer, the one receiving the TCP RST,
    should respond to receiving that TCP RST=20
    (e.g. does it try to restart the DLEP session, does it wait=20
    for the other side to restart the DLEP session, or is some=20
    other behavior appropriate)

Thanks,

Ran


From nobody Tue Nov 24 08:05:41 2015
Return-Path: <rick@tropicalstormsoftware.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 C52C21A8ABD for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:05:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 HZAkWaWDnLMk for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:05:38 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79D141A8A57 for <manet@ietf.org>; Tue, 24 Nov 2015 08:05:37 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 16:05:00 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>, RJ Atkinson <rja.lists@gmail.com>
Thread-Topic: [manet] DLEP-17: "Use TLS" flag is not secure
Thread-Index: AQHRJs03eJAqOKKhL0O6fybRyrfwCA==
Date: Tue, 24 Nov 2015 16:04:58 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B04E7E@tss-server1.home.tropicalstormsoftware.com>
References: <3C8E8891-D798-49F8-8AF0-DD0A35BA476E@gmail.com> <CAGnRvuoeW8WV78Vp92G9QBmDnDvSSXPgjOK2e18kwUYdKUUBAQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/6yBC9t1mWKZSozjFI7JmOQKSOnA>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: "Use TLS" flag is not secure
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:05:39 -0000

Hi Ran,=0A=
=0A=
Thanks for the on-going reviews.  I'll quickly comment on this one.=0A=
=0A=
Henning is right, the 'Use-TLS' flag means "TLS is expected when using =0A=
this connection point (address:port)".  Perhaps 'Expect-TLS' would be a =0A=
better name for the flag?=0A=
=0A=
Cheers,=0A=
=0A=
Rick=0A=
=0A=
=0A=
On 24/11/15 15:31, Henning Rogge wrote:=0A=
> On Tue, Nov 24, 2015 at 4:20 PM, RJ Atkinson <rja.lists@gmail.com> wrote:=
=0A=
>>=0A=
>> Section 10.2, page 38 (top) defines a =93Use TLS=94 flag.=0A=
>>=0A=
>> This design creates a security problem.  The issue is commonly=0A=
>> known as a =93downgrade attack=94, because a man-in-the-middle=0A=
>> attacker (whether on-link or off-link) simply clears that bit=0A=
>> to (incorrectly) indicate that TLS is not required.=0A=
>=0A=
> The TLS bit is (I think) not about "use TLS" or "don't use TLS", its=0A=
> just the bit that tells you what to expect on the IP/port combination.=0A=
>=0A=
> If you clear the bit, the other side would try to connect to the TLS=0A=
> socket with a default TCP connection, which will fail.=0A=
>=0A=
>> I don=92t see any way to fix this, but I am open-minded=0A=
>> if someone has a creative idea.=0A=
>>=0A=
>> The absolute bare minimum for IETF approval would be that this=0A=
>> (easily exploited) vulnerability be disclosed BOTH within=0A=
>> Section 10.2 AND also in the Security Considerations of Section 11.=0A=
>>=0A=
>> My guess is that the Security Area reviewer will say that this=0A=
>> is unacceptable protocol design.=0A=
>>=0A=
>> So I=92d prefer (and recommend) that we drop this =93Use TLS=94 flag.=0A=
>>=0A=
>> Maybe an alternate approach would be to create an informative=0A=
>> status code or signal (whichever) that a peer could send to=0A=
>> a would-be peer to indicate that non-TLS DLEP sessions are not=0A=
>> allowed.=0A=
>>=0A=
>> While that proposed message could be intercepted/dropped by=0A=
>> an adversary, it is purely a status message. A good DLEP=0A=
>> implementation would attempt a DLEP+TLS session with its=0A=
>> intended peer anytime a DLEP w/o TLS session failed, so=0A=
>> the loss of the proposed message doesn=92t create a security=0A=
>> vulnerability.=0A=
>=0A=
> I don't think there is any way between two parties that don't know=0A=
> each other to establish a secure connection if BOTH of them support=0A=
> non-secure communication AND a Man in the Middle controls all traffic=0A=
> between the two parties.=0A=
>=0A=
> The MITM could just drop everything that is security-related from the=0A=
> communication.=0A=
>=0A=
> Henning Rogge=0A=
>=0A=
> _______________________________________________=0A=
> manet mailing list=0A=
> manet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/manet=0A=
>=0A=
=0A=


From nobody Tue Nov 24 08:08:36 2015
Return-Path: <rja.lists@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 1A0401A8AC4 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:08:36 -0800 (PST)
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 waa80eyEQ3e9 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:08:33 -0800 (PST)
Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE7DE1A8AC3 for <manet@ietf.org>; Tue, 24 Nov 2015 08:08:32 -0800 (PST)
Received: by qgcc31 with SMTP id c31so13444893qgc.3 for <manet@ietf.org>; Tue, 24 Nov 2015 08:08:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=DKu092M5rFrfVwmGlgIdtf6+j9F1VSq8s0I9rgaS5WE=; b=lYVMHKKuboUnbkQCRdoNmDeK1VCJH0ZCj6N27JGo/cJUOvvZgGXgpu54lQTaFTo/G2 IgT+mpUU13lzB19gkuORmB2XP7bpfuBOY3uKakBw11jj4sRHPJaWXjhJ1xK33B/7GFdT rom3GA3N4BZ16YvoHwQ9KmzfdzbmG0Lelm6bdH/tQyuPiYzMaklKGdeJPU/VLu+JFpzi Gp6ZeA1imB/WKa5RhQGDWibVAqaOh9AsFCM9X66C3hvVnMYcAuhD7sBGAZDWV79vn1q2 WgCzFp85vHMRAGjlAUKYFFGHjCAWu8TrpgLw/cxZluzj8oqvMQE9bRcRCyFydFCQmDDm mBQQ==
X-Received: by 10.140.202.132 with SMTP id x126mr35641892qha.1.1448381312157;  Tue, 24 Nov 2015 08:08:32 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id e28sm4405722qkj.19.2015.11.24.08.08.31 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 08:08:31 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <3489BD69-2F2B-46DB-AD89-7A9212E0D069@gmail.com>
Date: Tue, 24 Nov 2015 11:08:31 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/fK7GnFIH956DCH9mQLprtUIR9j0>
Subject: [manet] DLEP-17: IANA Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:08:36 -0000

The IANA Considerations in Section 12 is much better,
but still does not seem to be compliant with RFC-5226.

For example, RFC-5226 Section 4.1 language ought to be
used when describing the allocation policy (e.g.,
Hierarchical Allocation, First Come First Served,=20
Expert Review, Specification Required, RFC Required,
IETF Review, Standards Action, IESG Approval).

It is permitted to have more than 1 authorized allocation=20
policy allowed for a given registry created in an IETF RFC. =20
For example, it is common to have =E2=80=9CExpert Review, IETF
Review, Standards Action, or IESG Approval=E2=80=9D all be allowed
(concurrently) as ways for a new registry allocation to be=20
approved.  As an example, specifying =E2=80=9CExpert Review=E2=80=9D =
alone=20
would mean that the DLEP WG publishing an an IETF Standards Track=20
DLEP Extension would NOT be sufficient to allocate a code point=20
=E2=80=94 which would be both a very odd outcome and very odd registry
management approach.

Separately, the goal of this section should be that when
the IANA staff read the IANA Considerations section of
the draft (without reading the rest of the draft) immediately
know exactly what they need to do to create and document
any new registries =E2=80=94 and to update any existing registries
with new entries.  The current section 12.2 is not close=20
to being sufficient in this regard.

If folks want help getting this section into correct form,
I=E2=80=99m happy to help.

Yours,

Ran



From nobody Tue Nov 24 08:10:47 2015
Return-Path: <rick@tropicalstormsoftware.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 63B951A8A9D for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:10:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 1Ilppicl9VF4 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:10:45 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D3491A8A75 for <manet@ietf.org>; Tue, 24 Nov 2015 08:10:43 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 16:10:04 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: error handling during "In-Session" state
Thread-Index: AQHRJtBu2WxC5skuw0KB6S2DjRdVlA==
Date: Tue, 24 Nov 2015 16:10:03 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B04EE5@tss-server1.home.tropicalstormsoftware.com>
References: <447C1544-14DF-40C3-BA23-97F4F146A374@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/KHYwmuE-f91SFWu01lNeqvpHo_E>
Subject: Re: [manet] DLEP-17: error handling during "In-Session" state
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:10:46 -0000

Thanks Ran,=0A=
=0A=
My current thoughts are to add a blanket statement to Section 5, saying =0A=
something along the lines of "A TCP reset in any state causes an =0A=
immediate transition to the relevant initial state, clearing any session =
=0A=
information bases."=0A=
=0A=
I don't see the need for special handling for particular states, or any =0A=
kind of 'gentle' restarting.=0A=
=0A=
Cheers,=0A=
=0A=
Rick=0A=
=0A=
On 24/11/15 15:54, RJ Atkinson wrote:=0A=
>=0A=
> Section 5.3 seems to talk about all of the expected behaviors,=0A=
> which is great.=0A=
>=0A=
> But what is the intended response behavior if one side of the=0A=
> active DLEP session receives a (presumably unexpected) TCP Reset ?=0A=
>=0A=
> It seems to me that Section 5.3 ought to say something about:=0A=
>=0A=
> (a) whether a DLEP peer is allowed to just reset the DLEP TCP session.=0A=
>      (Maybe it isn=92t allowed to, from a DLEP perspective, which=0A=
>      might be important to note so implementers know this.)=0A=
>=0A=
> (b) how the other DLEP peer, the one receiving the TCP RST,=0A=
>      should respond to receiving that TCP RST=0A=
>      (e.g. does it try to restart the DLEP session, does it wait=0A=
>      for the other side to restart the DLEP session, or is some=0A=
>      other behavior appropriate)=0A=
>=0A=
> Thanks,=0A=
>=0A=
> Ran=0A=
>=0A=
> _______________________________________________=0A=
> manet mailing list=0A=
> manet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/manet=0A=
>=0A=
=0A=


From nobody Tue Nov 24 08:13:16 2015
Return-Path: <rick@tropicalstormsoftware.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 00FE01A8AE5 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 4d6R-JgctnmF for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:13:14 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 764561A8ADE for <manet@ietf.org>; Tue, 24 Nov 2015 08:13:14 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 16:12:35 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17:  well-known IPv4 link-local multicast address
Thread-Index: AQHRJs1t4NGRqeKuwESH7X34pLojhQ==
Date: Tue, 24 Nov 2015 16:12:34 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B04F12@tss-server1.home.tropicalstormsoftware.com>
References: <4C2E2E59-68FB-45A8-A24F-4F8AC6E3D1EB@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/BF_Ij4yksLnf4jnlQ8RDcRmxueg>
Subject: Re: [manet] DLEP-17:  well-known IPv4 link-local multicast 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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:13:16 -0000

Ran,=0A=
=0A=
We resisted the urge to request one of the few remaining IPv4 multicast =0A=
addresses, and went for the IPv4 broadcast address instead.  Discovery =0A=
is a single-hop process anyway.=0A=
=0A=
Cheers,=0A=
=0A=
Rick=0A=
=0A=
On 24/11/15 15:33, RJ Atkinson wrote:=0A=
>=0A=
> At present, IANA Considerations only requests an IPv6=0A=
> link-local multicast address.=0A=
>=0A=
> We will need one also to be defined for IPv4 for IPv4 deployments=0A=
> of DLEP.  I have drafted precise IANA-compliant text below, so this=0A=
> should be easy to insert into the DLEP draft.=0A=
>=0A=
>=0A=
> Proposed New Text:=0A=
>=0A=
> 12.9  DLEP IPv4 Link-local Multicast Address=0A=
>=0A=
>    Please allocate 1 multicast address to DLEP from the =93IPv4 Multicast=
=0A=
>    Address, Local Network Control Block=94 registry for "DLEP Discovery S=
ignals".=0A=
>=0A=
>=0A=
>=0A=
> Yours,=0A=
>=0A=
> Ran=0A=
>=0A=
> _______________________________________________=0A=
> manet mailing list=0A=
> manet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/manet=0A=
>=0A=
=0A=


From nobody Tue Nov 24 08:16:35 2015
Return-Path: <rja.lists@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 C61581A8BB3 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:16:33 -0800 (PST)
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 PqvUwMJZ7N75 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:16:32 -0800 (PST)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E98421A8AF8 for <manet@ietf.org>; Tue, 24 Nov 2015 08:16:31 -0800 (PST)
Received: by qgec40 with SMTP id c40so13681686qge.2 for <manet@ietf.org>; Tue, 24 Nov 2015 08:16:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=dgTtF1Ln5iLOBHAI8a35eowgzUboDVwiNDswzqaYaGk=; b=kx3hMmPiBBnkC2aDU1unoDcQgBlKcnf347zosanZINsUTlm1vJ7pl/10t7zqPlba/L ah/49pCi/NG11W9q5xkAkm+4m2Q3n81LK9aNDRYT4BHs4kCVWrKRUACopknAZZGLoUuo RxZWxAPN+Cpgg+Zll6Lr9C7nH3O/d+iA3E/yzK0lZsF4gzvTH0sHFjm2jO30vUP8NPsh 1m/57qDsbUQ/y/nYmnvl6SzmSqe+yc2jofEhQrVP0scZYWzU7zthVHTVycFXr1vzVuaY EN3A6+JmetP446rUx6fcRxS4WJi0t57JN5v/gDzIwbyEPJOL8kHs+o0Bbg8/TdJvxG4p 8wKg==
X-Received: by 10.140.92.163 with SMTP id b32mr34221507qge.85.1448381791087; Tue, 24 Nov 2015 08:16:31 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id q133sm4337240qhq.20.2015.11.24.08.16.30 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 08:16:30 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <57909BAD-55EB-4AE7-913F-745166306D4A@gmail.com>
Date: Tue, 24 Nov 2015 11:16:29 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Q0VSL2BaK-rJ2vAivYKyT0-bsag>
Subject: [manet] DLEP-17: Assumptions
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:16:33 -0000

I think it is NOT reasonable to assume that all DLEP
implementations will happen to support IPv6.  

Many deployed routers/modems either (a) do not support IPv6 (yet) 
or (b) have IPv6 disabled (e.g. in a network where IPv6 has not 
yet been deployed by the network operator).

Further, there are some existing deployed in-use IP/RF links 
that are both low data-rate and low-MTU.  In those links,
links likely to benefit from DLEP, it is not obvious how one 
can efficiently support IPv6, since IPv6 is specified to have 
a minimum MTU of 1280 bytes (and hence would require the
additional overhead of an adaptation layer).

For some multi-year transition period we also will need
to support UDP/IPv4 link-local multicast for DLEP Discovery.
(See my previous note about getting an IPv4 link-local 
multicast address for this purpose.)

I propose to edit this to either (a) remove the recommendation 
that only IPv6 link-local addresses be used or (b) scope
that recommendation to situations where IPv6 already is in use.

Yours,

Ran





From nobody Tue Nov 24 08:18:38 2015
Return-Path: <rja.lists@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 389E81A8F36 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:18:36 -0800 (PST)
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 62a472e7Jijx for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:18:34 -0800 (PST)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3001C1A8BB7 for <manet@ietf.org>; Tue, 24 Nov 2015 08:18:34 -0800 (PST)
Received: by qgec40 with SMTP id c40so13727456qge.2 for <manet@ietf.org>; Tue, 24 Nov 2015 08:18:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=HztU8EmPTcUojK/b0wKkT6w3UtBvQ9eeR2bdTNA7HOI=; b=xH06lx5+BBRNImcFAj474s0X4RHmbXvoSRylaL7/OEnaym5m0wOYZBLn+0C9XTefyU 52fibfC/URLDWDFV1ascdDJgdIDGKEp78Y6Cl38k3/fHAfAGZkJjgGu+jpH/xcJON7xb gO73DVQ15ZhK82a0BIrlWyBPMhIrXUDH+7UzmTCXj1AhYZYo+6JYCY1myFF6P5bGa61B 3dbjnmFVmLXKe1xifNrb2u8/ThqaZk+AVy6nQ+M2JSnNnCLQSAkd86XoY4ikdUFR0Oob 8E95rEAcBH9mIomVt7dR3Iv9Ahkv/twS2FjXU0wU5ccmm+EviukZfmvCT+a4ZfUCqngj c30Q==
X-Received: by 10.140.101.233 with SMTP id u96mr33698363qge.70.1448381913387;  Tue, 24 Nov 2015 08:18:33 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id j64sm1954693qhc.36.2015.11.24.08.18.32 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 08:18:33 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <DF2AB6DE-8F63-4125-9244-F2412E04F147@gmail.com>
Date: Tue, 24 Nov 2015 11:18:32 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/7IccuFEnAFo6FNMzQCjQXxUaLQ8>
Subject: [manet] DLEP-17: Section 3.1 editorial
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:18:36 -0000

For clarity, I propose to edit the text in Section 3.1
as follows.

OLD TEXT:
  However, a modem MUST include the following list of metrics
  in the Session Initialization Response message (Section 9.4):

NEW TEXT:
  However, a modem MUST include AT LEAST the following list of metrics
  in the Session Initialization Response message (Section 9.4):


Yours,

Ran


From nobody Tue Nov 24 08:24:17 2015
Return-Path: <rja.lists@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 5F89D1A8FD7 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:24:16 -0800 (PST)
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 5aQaD2wqOzS3 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:24:15 -0800 (PST)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 698C91A901C for <manet@ietf.org>; Tue, 24 Nov 2015 08:24:09 -0800 (PST)
Received: by qgeb1 with SMTP id b1so13984095qge.1 for <manet@ietf.org>; Tue, 24 Nov 2015 08:24:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=SqNg+wsAVgC62ZaSnb1FMs0CC0ObnEpe3k4x/KV/LSk=; b=qKY73U2HXeqMKO2PXrRw2DVv4k+5ZUjmedksZD5/x0A5z/pev1Mxy/i8nNp+ZHlk6x 0desOUOhiImU5VlTIzs5NZH0xmz7AW2JUuwYwsH4oHpghy7zXpnw2FXrBVhaBKrg5rcL VH0U+wvNiFYuG+HATFCNeKyHuS0NLiEgRIMnzC6+/f6sIg8Q0Td7ndXZFoSCEFO8z4OH cB9Qkr7BF2y+yAsUP9rNNv8to4cygYKSS4vYteuc7gKFHQcCFpv8+NyCjPSYwCWbH8Em d5WckGpmhkWlJtZdlzdSXI2jv9NrluiqnaMEhK7W/rTp8E3qb8QZoIFb4y5XfL49tDQN 8ESA==
X-Received: by 10.140.242.77 with SMTP id n74mr22803553qhc.37.1448382248653; Tue, 24 Nov 2015 08:24:08 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id a64sm4422156qka.47.2015.11.24.08.24.08 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 08:24:08 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <8C867205-4F66-4026-AEA7-471B66D00FC9@gmail.com>
Date: Tue, 24 Nov 2015 11:24:07 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/zbSpjYC5DFZjlbPHH7WFa8SNd28>
Subject: [manet] DLEP-17: Section 5.1, security concern
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:24:16 -0000

In Section 5.1, top of page 13, this sentence exists:
	The modem MUST accept a TCP connection on only one (1)
        address/port combination per session.

A quick reading of this yields confusion.  

On the surface, it appears to say that the modem can ONLY have 
1 peer at a time.  If correct, then an off-link attacker could 
deny service to a legitimate router by opening a DLEP session
with the modem (while pretending to be a legitimate router).

If the paragraph above is a correct description, then this
security vulnerability needs to be clearly disclosed in the
Security Considerations section of this I-D.  One imagines
that using TLS with both client-certificate and server-certificate
for endpoint identity authentication would be a RECOMMENDATION
for situations where the threat environment included either
off-link or on-link attackers.

Maybe the quoted text means something else ?
If that is the case, please rephrase it for clarity.

Thanks,

Ran





From nobody Tue Nov 24 08:26:48 2015
Return-Path: <ratliffstan@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 F22751A8FD2 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:26:46 -0800 (PST)
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 xMAmjGvcLn3h for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:26:45 -0800 (PST)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 956581A9046 for <manet@ietf.org>; Tue, 24 Nov 2015 08:26:43 -0800 (PST)
Received: by lffu14 with SMTP id u14so27777583lff.1 for <manet@ietf.org>; Tue, 24 Nov 2015 08:26:41 -0800 (PST)
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=P1OThPjUA+whUm2nH+4EQtmsFbUv9kuHTR7uS9cYeqc=; b=D2GHh+9YRtfxg5QDw3XdfUh2Wy+JJpGf5Z3Gl6IP7zgomq+qX3J7ZMwi9aWPzFoWlT KgPq3oz12zFkNPetmvnqXWar3EoINMqTKjsPybhmL0boK1cmi6jRcKgP4eK0FXWlErfw Ul/UTODB6Eu078RzifH7Ge7Kztx+BOuGtlGF/ISRf32HxSYnIFQt6su8mPK47IWIKruF sNJcoWbgZFrY0d1zFOXQqYnDOf3EBAkOX08LJTcGHe4MXEXSvB41UO9YElc3c71dTDDA ZEnHWfaVLJ9uxm8FDkVV1oLtabNrZIRBQo3XHi5VCJ02hYCtjOu7WmcwSnBdWndcNFSf KkcQ==
MIME-Version: 1.0
X-Received: by 10.25.146.79 with SMTP id u76mr13857704lfd.146.1448382401769; Tue, 24 Nov 2015 08:26:41 -0800 (PST)
Received: by 10.25.155.134 with HTTP; Tue, 24 Nov 2015 08:26:41 -0800 (PST)
In-Reply-To: <57909BAD-55EB-4AE7-913F-745166306D4A@gmail.com>
References: <57909BAD-55EB-4AE7-913F-745166306D4A@gmail.com>
Date: Tue, 24 Nov 2015 11:26:41 -0500
Message-ID: <CALtoyonJV6bim0Yz-dXp_v1ENkp27W=b1pLsywaT1a9PGodAsg@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
Content-Type: multipart/alternative; boundary=001a114013b68e771305254bce00
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/EaJaaFlhgHW8ioQHD8Hd9rdp6kI>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Assumptions
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:26:47 -0000

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

Ran,

Please note that this specification covers *only* the local connection
between a router and it's attached radio - the spec does not intend to
imply that the radio must support IPv6 OTA.

That said, I don't believe there's any hard-and-fast mandate to use IPv6,
just a recommendation that it be used. As Rick mentioned in an earlier
email, the IPv4 broadcast address can be used for discovery, and there is
no restriction that I'm aware of on the P2P session.

Regards,
Stan


On Tue, Nov 24, 2015 at 11:16 AM, RJ Atkinson <rja.lists@gmail.com> wrote:

>
> I think it is NOT reasonable to assume that all DLEP
> implementations will happen to support IPv6.
>
> Many deployed routers/modems either (a) do not support IPv6 (yet)
> or (b) have IPv6 disabled (e.g. in a network where IPv6 has not
> yet been deployed by the network operator).
>
> Further, there are some existing deployed in-use IP/RF links
> that are both low data-rate and low-MTU.  In those links,
> links likely to benefit from DLEP, it is not obvious how one
> can efficiently support IPv6, since IPv6 is specified to have
> a minimum MTU of 1280 bytes (and hence would require the
> additional overhead of an adaptation layer).
>
> For some multi-year transition period we also will need
> to support UDP/IPv4 link-local multicast for DLEP Discovery.
> (See my previous note about getting an IPv4 link-local
> multicast address for this purpose.)
>
> I propose to edit this to either (a) remove the recommendation
> that only IPv6 link-local addresses be used or (b) scope
> that recommendation to situations where IPv6 already is in use.
>
> Yours,
>
> Ran
>
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

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

<div dir=3D"ltr">Ran,=C2=A0<div><br></div><div>Please note that this specif=
ication covers *only* the local connection between a router and it&#39;s at=
tached radio - the spec does not intend to imply that the radio must suppor=
t IPv6 OTA.=C2=A0</div><div><br></div><div>That said, I don&#39;t believe t=
here&#39;s any hard-and-fast mandate to use IPv6, just a recommendation tha=
t it be used. As Rick mentioned in an earlier email, the IPv4 broadcast add=
ress can be used for discovery, and there is no restriction that I&#39;m aw=
are of on the P2P session.=C2=A0</div><div><br></div><div>Regards,</div><di=
v>Stan</div><div><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Nov 24, 2015 at 11:16 AM, RJ Atkinson <span dir=3D"ltr">&lt;<a =
href=3D"mailto:rja.lists@gmail.com" target=3D"_blank">rja.lists@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"><br>
I think it is NOT reasonable to assume that all DLEP<br>
implementations will happen to support IPv6.<br>
<br>
Many deployed routers/modems either (a) do not support IPv6 (yet)<br>
or (b) have IPv6 disabled (e.g. in a network where IPv6 has not<br>
yet been deployed by the network operator).<br>
<br>
Further, there are some existing deployed in-use IP/RF links<br>
that are both low data-rate and low-MTU.=C2=A0 In those links,<br>
links likely to benefit from DLEP, it is not obvious how one<br>
can efficiently support IPv6, since IPv6 is specified to have<br>
a minimum MTU of 1280 bytes (and hence would require the<br>
additional overhead of an adaptation layer).<br>
<br>
For some multi-year transition period we also will need<br>
to support UDP/IPv4 link-local multicast for DLEP Discovery.<br>
(See my previous note about getting an IPv4 link-local<br>
multicast address for this purpose.)<br>
<br>
I propose to edit this to either (a) remove the recommendation<br>
that only IPv6 link-local addresses be used or (b) scope<br>
that recommendation to situations where IPv6 already is in use.<br>
<br>
Yours,<br>
<br>
Ran<br>
<br>
<br>
<br>
<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" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div></div></div>

--001a114013b68e771305254bce00--


From nobody Tue Nov 24 08:28:44 2015
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 477C31A9082 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:28:28 -0800 (PST)
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 IQQelz4zl-Ek for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:28:27 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22D051A9042 for <manet@ietf.org>; Tue, 24 Nov 2015 08:28:19 -0800 (PST)
Received: by wmww144 with SMTP id w144so146068171wmw.1 for <manet@ietf.org>; Tue, 24 Nov 2015 08:28:17 -0800 (PST)
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=D7iKOcjVcszBDmqNir50fFbHlXyza0BTARFMHR+rG+I=; b=cAGCBVpTydXlOvHA4XokkSg2iM5XVHiGmyHdGWbPoUdg7JepdE0j3ipISRT4EQIi1D MidaxqMrqnSXs0ptF8rId6rt0SbdP3hjx0ZcNFyrHUCno69FyxWYKau93uzdJfNxZCE7 ymtMkDRfZ+nVfHJYDH0Nt85Q7hNOIoaebe+j2txDCqUz8ptp8O6qCbeg92OVW2fa6pUb JRQBWvmT5t/ma590S98+tXHfZGQVxo1wNJIrdda8yVzb0mBKI0ezPEPGQwkumE7LniR6 UlyGpAnXymoTJfm9tgoiL1YC6kNRx0QQuEVXW8wF6FbPC3FPenR2vrUdh/AbJsFFaJkw J43w==
X-Received: by 10.194.95.65 with SMTP id di1mr36451193wjb.134.1448382497754; Tue, 24 Nov 2015 08:28:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Tue, 24 Nov 2015 08:27:48 -0800 (PST)
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B04EE5@tss-server1.home.tropicalstormsoftware.com>
References: <447C1544-14DF-40C3-BA23-97F4F146A374@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04EE5@tss-server1.home.tropicalstormsoftware.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 24 Nov 2015 17:27:48 +0100
Message-ID: <CAGnRvurvHDFv=TFrRNZYf64Tt8BOXc0JFzJX2MPZguHB61=4CQ@mail.gmail.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/ZBDHi-uAYrB7P-yBYoTjmJ5TIDE>
Cc: MANET IETF <manet@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [manet] DLEP-17: error handling during "In-Session" state
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:28:28 -0000
X-List-Received-Date: Tue, 24 Nov 2015 16:28:28 -0000

On Tue, Nov 24, 2015 at 5:10 PM, Rick Taylor
<rick@tropicalstormsoftware.com> wrote:
> Thanks Ran,
>
> My current thoughts are to add a blanket statement to Section 5, saying
> something along the lines of "A TCP reset in any state causes an
> immediate transition to the relevant initial state, clearing any session
> information bases."
>
> I don't see the need for special handling for particular states, or any
> kind of 'gentle' restarting.

As far as I read the draft the "reset" is a termination both of the
TCP session and the protocol data associated with the session.

You tear everything down and start a completely new connection.

Henning Rogge


From nobody Tue Nov 24 08:28:45 2015
Return-Path: <rja.lists@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 CB5091A9042 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:28:32 -0800 (PST)
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 0-3UC1HwtxJt for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:28:28 -0800 (PST)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AADF81B2B03 for <manet@ietf.org>; Tue, 24 Nov 2015 08:28:24 -0800 (PST)
Received: by qgea14 with SMTP id a14so13958910qge.0 for <manet@ietf.org>; Tue, 24 Nov 2015 08:28:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=SxwPnshiv8EQ1sH90kvfsnIWCrG4rIYTbpvpgypMuEo=; b=O4lAnfdNhb3bureqneEe1+ZgMdqIkKiKTQwu6Ebf4ChxhJco8JAVnovVUIixh1k/4S Rmz17NRf2GboOzWPMyA0P3zvqMV+zLUhblLPi89LHB0Yu+hRzhGgpzelGKUXtED+Ew/O /86xwWPDj/N5MSGVMKHs0uyl0kc1n6w1fDmuzGdwXosGkuR9gjU6F+0YIxtDp9zAMDFC uQ0nmGTCOqSogK8qDLZD92PVy4axiq6DybpKjIT6LtV361tke3OZ+OvXydT8UueOJ/VR VuTa2aEbfj5fgfyzTPNDpDli6uHksF6iAqsXuTz++MLzw4vksrIhhCvzNkXj5cETY1pp od0A==
X-Received: by 10.140.92.16 with SMTP id a16mr34612404qge.54.1448382503807; Tue, 24 Nov 2015 08:28:23 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id a62sm4385578qga.8.2015.11.24.08.28.23 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 08:28:23 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0204F5F-22FB-4A79-852E-923DCBBC7C83@gmail.com>
Date: Tue, 24 Nov 2015 11:28:22 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/GolGkrI7TTMceKd8PMOab_G5u-w>
Subject: [manet] Section 5.2 - handling implementation errors
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:28:33 -0000

Section 5.2 is quite clear (which is good) that=20
=E2=80=9Can implementation MUST NOT emit any =E2=80=A6 not specified
in the received initialization message from its peer=E2=80=9D.

If a misbehaving implementation DID send a (message,
data item, signal, status code) that was NOT in the
received initialization message from the peer, how
ought the implementation react ?

My suggestion is that it ought to IGNORE the offending
(message, data item, signal, status code) and keep
going, but maybe the intended behavior is something
else (e.g. close the DLEP session and start over).

Either way, the correct behavior for the receiver of
invalid/unexpected stuff ought to be clearly specified.

(An old IETF motto is: =E2=80=9CBe conservative in what one sends,=20
and liberal in what one receives.=E2=80=9D)

Thanks,

Ran


From nobody Tue Nov 24 08:29:38 2015
Return-Path: <rick@tropicalstormsoftware.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 8C71F1A8F3D for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:29:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 Letku06_uMah for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:29:27 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2BEB1A8A29 for <manet@ietf.org>; Tue, 24 Nov 2015 08:29:04 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 16:28:40 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: Assumptions
Thread-Index: AQHRJtOAjDIAGYgxjUucJQUCqwsclA==
Date: Tue, 24 Nov 2015 16:28:38 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B0500C@tss-server1.home.tropicalstormsoftware.com>
References: <57909BAD-55EB-4AE7-913F-745166306D4A@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/eIdXZw2Trj8XEwFSEtjBDbkfr5g>
Subject: Re: [manet] DLEP-17: Assumptions
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:29:31 -0000

Ran,=0A=
=0A=
I was working under the assumption (and yes, I know it is an assumption) =
=0A=
that in 2015 the IETF would mandate IPv6, and not let us get away with =0A=
an either/or approach.=0A=
=0A=
I totally understand the difficulties of IPv6 and legacy equipment, but =0A=
DLEP must mandate 1 method of discovery, and I can't see the IESG =0A=
letting us mandate IPv4.=0A=
=0A=
If, however, someone has an approach that allows IPv4 only, and will get =
=0A=
through the IETF processes, then I would love to hear it.=0A=
=0A=
Cheers,=0A=
=0A=
Rick=0A=
=0A=
On 24/11/15 16:16, RJ Atkinson wrote:=0A=
>=0A=
> I think it is NOT reasonable to assume that all DLEP=0A=
> implementations will happen to support IPv6.=0A=
>=0A=
> Many deployed routers/modems either (a) do not support IPv6 (yet)=0A=
> or (b) have IPv6 disabled (e.g. in a network where IPv6 has not=0A=
> yet been deployed by the network operator).=0A=
>=0A=
> Further, there are some existing deployed in-use IP/RF links=0A=
> that are both low data-rate and low-MTU.  In those links,=0A=
> links likely to benefit from DLEP, it is not obvious how one=0A=
> can efficiently support IPv6, since IPv6 is specified to have=0A=
> a minimum MTU of 1280 bytes (and hence would require the=0A=
> additional overhead of an adaptation layer).=0A=
>=0A=
> For some multi-year transition period we also will need=0A=
> to support UDP/IPv4 link-local multicast for DLEP Discovery.=0A=
> (See my previous note about getting an IPv4 link-local=0A=
> multicast address for this purpose.)=0A=
>=0A=
> I propose to edit this to either (a) remove the recommendation=0A=
> that only IPv6 link-local addresses be used or (b) scope=0A=
> that recommendation to situations where IPv6 already is in use.=0A=
>=0A=
> Yours,=0A=
>=0A=
> Ran=0A=
>=0A=
>=0A=
>=0A=
>=0A=
> _______________________________________________=0A=
> manet mailing list=0A=
> manet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/manet=0A=
>=0A=
=0A=


From nobody Tue Nov 24 08:40:27 2015
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 EC3F21A9022 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:40:25 -0800 (PST)
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 6D3aQ3cy6vYZ for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:40:24 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45DD71A892F for <manet@ietf.org>; Tue, 24 Nov 2015 08:40:24 -0800 (PST)
Received: by wmec201 with SMTP id c201so34860505wme.1 for <manet@ietf.org>; Tue, 24 Nov 2015 08:40:22 -0800 (PST)
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=UOO225e3raUlxK/m7vEWLqcCrsnKeI7lZX0kE/fJcak=; b=UxRpskKvn4Use822jKOwiJj2Tk7Gq05tGN2aHQ9TjWA4Cpuj4NESOvzsSmYwqa8bPr dPd044mHrw5AEsBOvxs4wmKl646LIPX+l9yBOPoauEwa/80QUBHfe43MfDFHmUKdtTRx 2fsfCIrKMirSXLRkeYz+MVRS/0pvdrHeLlg8pt0G5YSZP7vD7ZXC/jTZB1LY+jmlu6d8 xAGw0D19k5pHEO6Xi56NuEWww2uOyj3FUj6A570Z5tLnlvLFwqPhxGovZa7dJRCgsRnV aBVaUx1AQnAlL8ukXn9E85ifrr86kLJysoh1tn9CoNeBUh6qvYdMezWqlSpwMAsVkGOi HyEA==
X-Received: by 10.194.2.193 with SMTP id 1mr32722237wjw.26.1448383222902; Tue, 24 Nov 2015 08:40:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Tue, 24 Nov 2015 08:39:53 -0800 (PST)
In-Reply-To: <8C867205-4F66-4026-AEA7-471B66D00FC9@gmail.com>
References: <8C867205-4F66-4026-AEA7-471B66D00FC9@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 24 Nov 2015 17:39:53 +0100
Message-ID: <CAGnRvuqAf8b+cmdpTnJWuWcJ_Xnft8WyjOB7-cN7rpgzXCCT=w@mail.gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/fuISnQ3gnglbtncHdo3mJkms4yE>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Section 5.1, security concern
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:40:26 -0000

On Tue, Nov 24, 2015 at 5:24 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
>
> In Section 5.1, top of page 13, this sentence exists:
>         The modem MUST accept a TCP connection on only one (1)
>         address/port combination per session.

"per session"...

so its more a matter if "multiple sessions on the same radio" makes
sense. If the radio only implements "pushing metrics to the router" it
could easily handle multiple sessions. If you want to do "request link
characteristics or even flow control", only a single session makes
sense.

> A quick reading of this yields confusion.
>
> On the surface, it appears to say that the modem can ONLY have
> 1 peer at a time.  If correct, then an off-link attacker could
> deny service to a legitimate router by opening a DLEP session
> with the modem (while pretending to be a legitimate router).

off-link would mean TLS... because linklocal IP traffic is not
forwarded between the off-link attacker and the DLEP instance.

> If the paragraph above is a correct description, then this
> security vulnerability needs to be clearly disclosed in the
> Security Considerations section of this I-D.  One imagines
> that using TLS with both client-certificate and server-certificate
> for endpoint identity authentication would be a RECOMMENDATION
> for situations where the threat environment included either
> off-link or on-link attackers.

If you have an on-link attacker you have lost anyways... because the
attacker already controls the data-plane.

Unless you use something like 802.1x, which would keep the link safe
(both data and control plane).

I still stand with my suggesting making linklocal IPs mandatory for
DLEP and drop all the TLS stuff... if someone wants to deploy a
layer-2 VPN, he/she can also deal with the necessary security for the
VPN.

Henning Rogge


From nobody Tue Nov 24 08:43:56 2015
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 3BE591A8F39 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:43:55 -0800 (PST)
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 vQeIz1TYSuxU for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:43:54 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A122A1A9025 for <manet@ietf.org>; Tue, 24 Nov 2015 08:43:53 -0800 (PST)
Received: by wmec201 with SMTP id c201so35005397wme.1 for <manet@ietf.org>; Tue, 24 Nov 2015 08:43:52 -0800 (PST)
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=mgGwYRnVnrPHdU4fgR498QJb6U8KlhAmDgO5LqVavnk=; b=J+LsLEM8XUWsm/HeNZiOpSLwJayPFHNyZPYCrYrCQoox9EccfhTYcIlteyyX/R8/i0 ejoO4R1AzK3DCKlYHe/onepSLFr5GKvSfCQFOUtvNHCkHmGa56PBvfe5S3gla1eZbvIL BehIzma94m9NCl+hVbD+irojwkTGPG3H0NGSadY06Gig963j5L8ryTxafu2bN0QUQgrY s7Hu9Q4D407OGmJyVPz5jrdlU+mobGfnkviR5jI4MLs4VilUvycXO6Nd0Zh+Vix2h+nl jothi3jKIaSACqE8P0MyxpkvP1gVzwgU6lBKoinb1grbfnArQQDY8omppBt8zqhytANU gZ/w==
X-Received: by 10.28.64.11 with SMTP id n11mr22898205wma.37.1448383432155; Tue, 24 Nov 2015 08:43:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Tue, 24 Nov 2015 08:43:22 -0800 (PST)
In-Reply-To: <D0204F5F-22FB-4A79-852E-923DCBBC7C83@gmail.com>
References: <D0204F5F-22FB-4A79-852E-923DCBBC7C83@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 24 Nov 2015 17:43:22 +0100
Message-ID: <CAGnRvuqOd+GaYnqhS0SJMShSggM7h0PHaZ4RzU8e__-eC0EBCA@mail.gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/2cXKn8zAgkYs2VEHSMaRjBbqrkk>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Section 5.2 - handling implementation errors
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:43:55 -0000

On Tue, Nov 24, 2015 at 5:28 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
>
> Section 5.2 is quite clear (which is good) that
> =E2=80=9Can implementation MUST NOT emit any =E2=80=A6 not specified
> in the received initialization message from its peer=E2=80=9D.
>
> If a misbehaving implementation DID send a (message,
> data item, signal, status code) that was NOT in the
> received initialization message from the peer, how
> ought the implementation react ?

I think the standard reaction should be to drop the session completely.

Henning Rogge


From nobody Tue Nov 24 08:44:43 2015
Return-Path: <ratliffstan@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 71FCB1A903E for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:44:42 -0800 (PST)
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 6eGB4VQ-a11J for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:44:40 -0800 (PST)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59F611B2B75 for <manet@ietf.org>; Tue, 24 Nov 2015 08:44:39 -0800 (PST)
Received: by lffu14 with SMTP id u14so28522835lff.1 for <manet@ietf.org>; Tue, 24 Nov 2015 08:44:37 -0800 (PST)
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=4BvzXg5KW4u70cvpbuk7ZcA5X6F3xZ6WARfxzduxyok=; b=EuJS50bVMDsLYHEWtPsiBrzXnR+tb3erv84VBHX2LwZcVowREpSDaK2TdyVUsLFane EpIRoY2u914TooGp7H331kZ9rADiwOBTuGWYqMogsFgwiTdeDnhg3gbQbGmL3UxFyNOX 6ejVSQN1DVeKn1ywjQ9bv+UxPiwt0NAubrC+3z6gpfIBdUQM9tXzagmAOGW6p9joxNnq 9u8SVCJ/4fcUddlWwFlogM0I0IpkUZqYmA5IepzTk6UdUTHpAzaINbrB3jnybEXX2OL/ Yixr9rD6uvPDWpaF9J6EP6fdBZT3jCUutMAWdkLEdhp582W9yrYHndPQhO9nXTiow1pJ FS+w==
MIME-Version: 1.0
X-Received: by 10.112.129.134 with SMTP id nw6mr13810353lbb.10.1448383477485;  Tue, 24 Nov 2015 08:44:37 -0800 (PST)
Received: by 10.25.155.134 with HTTP; Tue, 24 Nov 2015 08:44:37 -0800 (PST)
In-Reply-To: <CAGnRvuqAf8b+cmdpTnJWuWcJ_Xnft8WyjOB7-cN7rpgzXCCT=w@mail.gmail.com>
References: <8C867205-4F66-4026-AEA7-471B66D00FC9@gmail.com> <CAGnRvuqAf8b+cmdpTnJWuWcJ_Xnft8WyjOB7-cN7rpgzXCCT=w@mail.gmail.com>
Date: Tue, 24 Nov 2015 11:44:37 -0500
Message-ID: <CALtoyo=FsSPW--205pZ3SCm-t=2WwQQVcCiEZEUXd_damda0wg@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b343ee4ac999905254c0e19
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/OKEimTXVaILNQy0ZHWXJDq9XBa4>
Cc: MANET IETF <manet@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [manet] DLEP-17: Section 5.1, security concern
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:44:42 -0000

--047d7b343ee4ac999905254c0e19
Content-Type: text/plain; charset=UTF-8

On Tue, Nov 24, 2015 at 11:39 AM, Henning Rogge <hrogge@gmail.com> wrote:

> On Tue, Nov 24, 2015 at 5:24 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
> >
> > In Section 5.1, top of page 13, this sentence exists:
> >         The modem MUST accept a TCP connection on only one (1)
> >         address/port combination per session.
>
> "per session"...
>
> so its more a matter if "multiple sessions on the same radio" makes
> sense. If the radio only implements "pushing metrics to the router" it
> could easily handle multiple sessions. If you want to do "request link
> characteristics or even flow control", only a single session makes
> sense.
>

The intent of the text is to say "one session per radio, per interface." If
the radio wants to establish 3 sessions, each on a separate VLAN for
example, that's fine. But not multiple sessions on the same interface.

We'll make an attempt to clarify.

Regards,
Stan



>
> > A quick reading of this yields confusion.
> >
> > On the surface, it appears to say that the modem can ONLY have
> > 1 peer at a time.  If correct, then an off-link attacker could
> > deny service to a legitimate router by opening a DLEP session
> > with the modem (while pretending to be a legitimate router).
>
> off-link would mean TLS... because linklocal IP traffic is not
> forwarded between the off-link attacker and the DLEP instance.
>
> > If the paragraph above is a correct description, then this
> > security vulnerability needs to be clearly disclosed in the
> > Security Considerations section of this I-D.  One imagines
> > that using TLS with both client-certificate and server-certificate
> > for endpoint identity authentication would be a RECOMMENDATION
> > for situations where the threat environment included either
> > off-link or on-link attackers.
>
> If you have an on-link attacker you have lost anyways... because the
> attacker already controls the data-plane.
>
> Unless you use something like 802.1x, which would keep the link safe
> (both data and control plane).
>
> I still stand with my suggesting making linklocal IPs mandatory for
> DLEP and drop all the TLS stuff... if someone wants to deploy a
> layer-2 VPN, he/she can also deal with the necessary security for the
> VPN.
>
> Henning Rogge
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--047d7b343ee4ac999905254c0e19
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 Tue, Nov 24, 2015 at 11:39 AM, Henning Rogge <span dir=3D"ltr">&lt;<=
a href=3D"mailto:hrogge@gmail.com" target=3D"_blank">hrogge@gmail.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Nov 24, 2015 at =
5:24 PM, RJ Atkinson &lt;<a href=3D"mailto:rja.lists@gmail.com">rja.lists@g=
mail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; In Section 5.1, top of page 13, this sentence exists:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The modem MUST accept a TCP connectio=
n on only one (1)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0address/port combination per session.=
<br>
<br>
&quot;per session&quot;...<br>
<br>
so its more a matter if &quot;multiple sessions on the same radio&quot; mak=
es<br>
sense. If the radio only implements &quot;pushing metrics to the router&quo=
t; it<br>
could easily handle multiple sessions. If you want to do &quot;request link=
<br>
characteristics or even flow control&quot;, only a single session makes<br>
sense.<br></blockquote><div><br></div><div>The intent of the text is to say=
 &quot;one session per radio, per interface.&quot; If the radio wants to es=
tablish 3 sessions, each on a separate VLAN for example, that&#39;s fine. B=
ut not multiple sessions on the same interface.=C2=A0</div><div><br></div><=
div>We&#39;ll make an attempt to clarify.=C2=A0</div><div><br></div><div>Re=
gards,</div><div>Stan</div><div><br></div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<br>
&gt; A quick reading of this yields confusion.<br>
&gt;<br>
&gt; On the surface, it appears to say that the modem can ONLY have<br>
&gt; 1 peer at a time.=C2=A0 If correct, then an off-link attacker could<br=
>
&gt; deny service to a legitimate router by opening a DLEP session<br>
&gt; with the modem (while pretending to be a legitimate router).<br>
<br>
off-link would mean TLS... because linklocal IP traffic is not<br>
forwarded between the off-link attacker and the DLEP instance.<br>
<br>
&gt; If the paragraph above is a correct description, then this<br>
&gt; security vulnerability needs to be clearly disclosed in the<br>
&gt; Security Considerations section of this I-D.=C2=A0 One imagines<br>
&gt; that using TLS with both client-certificate and server-certificate<br>
&gt; for endpoint identity authentication would be a RECOMMENDATION<br>
&gt; for situations where the threat environment included either<br>
&gt; off-link or on-link attackers.<br>
<br>
If you have an on-link attacker you have lost anyways... because the<br>
attacker already controls the data-plane.<br>
<br>
Unless you use something like 802.1x, which would keep the link safe<br>
(both data and control plane).<br>
<br>
I still stand with my suggesting making linklocal IPs mandatory for<br>
DLEP and drop all the TLS stuff... if someone wants to deploy a<br>
layer-2 VPN, he/she can also deal with the necessary security for the<br>
VPN.<br>
<br>
Henning Rogge<br>
<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" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div></div>

--047d7b343ee4ac999905254c0e19--


From nobody Tue Nov 24 08:50:45 2015
Return-Path: <rick@tropicalstormsoftware.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 214711B2CB9 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:50:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 BQ__vx3abl6R for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 08:50:43 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7C141A8F4D for <manet@ietf.org>; Tue, 24 Nov 2015 08:50:42 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 16:50:06 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>, RJ Atkinson <rja.lists@gmail.com>
Thread-Topic: [manet] Section 5.2 - handling implementation errors
Thread-Index: AQHRJtVOJ2o9TviqhUS+Vy9v0lnYlw==
Date: Tue, 24 Nov 2015 16:50:04 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B051BF@tss-server1.home.tropicalstormsoftware.com>
References: <D0204F5F-22FB-4A79-852E-923DCBBC7C83@gmail.com> <CAGnRvuqOd+GaYnqhS0SJMShSggM7h0PHaZ4RzU8e__-eC0EBCA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/u9Vsaffe8_wMJE-UuEdHl687z7M>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Section 5.2 - handling implementation errors
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 16:50:44 -0000

On 24/11/15 16:43, Henning Rogge wrote:=0A=
> On Tue, Nov 24, 2015 at 5:28 PM, RJ Atkinson <rja.lists@gmail.com> wrote:=
=0A=
>>=0A=
>> Section 5.2 is quite clear (which is good) that=0A=
>> =93an implementation MUST NOT emit any =85 not specified=0A=
>> in the received initialization message from its peer=94.=0A=
>>=0A=
>> If a misbehaving implementation DID send a (message,=0A=
>> data item, signal, status code) that was NOT in the=0A=
>> received initialization message from the peer, how=0A=
>> ought the implementation react ?=0A=
>=0A=
> I think the standard reaction should be to drop the session completely.=
=0A=
=0A=
I think it is mentioned in Section 10.=0A=
=0A=
Also, there is text in the Status codes about how to react after sending =
=0A=
various codes, the mode for 'Invalid Data', 'Unexpected Message' are all =
=0A=
'Terminate'.=0A=
=0A=
Rick=0A=
=0A=


From nobody Tue Nov 24 09:19:05 2015
Return-Path: <rick@tropicalstormsoftware.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 C95651B2D0D for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 bpUaqc4kv5Fx for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:19:03 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 596011A904A for <manet@ietf.org>; Tue, 24 Nov 2015 09:19:02 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 17:18:36 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: Security Considerations
Thread-Index: AQHRJshlGZtS6M2f1UaEMBWkMA+6tA==
Date: Tue, 24 Nov 2015 17:18:35 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/r6k6v9hmsTq3FCfP9KY2Rcz-MFY>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:19:05 -0000

Ran,=0A=
=0A=
I really like your proposed changes to the Security Considerations, but =0A=
I do have a concern.  Many major radio manufacturers consider TLS a step =
=0A=
too far, and mandating it for environments where it is considered =0A=
unnecessary will prevent uptake of DLEP.=0A=
=0A=
I think we are all agreed that when there are multiple hops between =0A=
modem and router then TLS is a MUST.  But when there is a single piece =0A=
of wire between the devices, people will (possibly correctly) argue that =
=0A=
it is pointless.=0A=
=0A=
Do you have any advice on how we could add some text to your =0A=
recommendation along the lines of:=0A=
=0A=
"If you can prevent DLEP running over multiple hops in your =0A=
implementation, then you MAY choose not to implement TLS."=0A=
=0A=
How one prevents multi-hop is left as an exercise to the reader...=0A=
=0A=
This is an open question to the WG as well.=0A=
=0A=
Cheers,=0A=
=0A=
Rick=0A=
=0A=
=0A=
On 24/11/15 14:57, RJ Atkinson wrote:=0A=
> All,=0A=
>=0A=
>=0A=
> The "Security Considerations=94 text isn=92t really adequate.=0A=
>=0A=
> I suspect part of the problem is editorial.  I am supplying=0A=
> candidate replacement text that I believe will be sufficient=0A=
> for the draft to pass the IETF Security Area review.=0A=
>=0A=
>=0A=
> Background:=0A=
>    In the IETF, =93implement=94 generally refers to code available=0A=
>    to execute a feature in a product, while =93use=94 or =93deploy=94=0A=
>    refers to the operational decision of how to configure a product=0A=
>    when installing it in an actual physical network.=0A=
>=0A=
>    I realize that some people (incorrectly) use =93implement=94 to refer=
=0A=
>    to deployment, but IETF protocol specifications generally try=0A=
>    to avoid that confusion.=0A=
>=0A=
>    Also, unlike some other standards bodies, the IETF doesn=92t have a=0A=
>    concept of =93conformance testing=94.  Products that claim to implemen=
t=0A=
>    an RFC are expected to implement it completely and properly,=0A=
>    but there are no IETF =93protocol police=94 checking a product to see=
=0A=
>    whether each detail was done correctly.=0A=
>=0A=
>    Last, in the IETF, the long-standing custom is that =93implementation=
=94=0A=
>    of security is mandatory, while =93deployment/use=94 of security is=0A=
>    optional.  The reasoning is that an operator best knows their own=0A=
>    security risks, but if the implementation does not include the=0A=
>    specified security mechanism (e.g. TLS) then (a) the implementation=0A=
>    won=92t be interoperable and/or (b) the user won=92t be ABLE to deploy=
/use=0A=
>    the security when they deem it appropriate.=0A=
>=0A=
>=0A=
> Proposed New Text for Section 11, sub-heading 1:=0A=
>=0A=
> 	1. An attacker might pretend to be a DLEP peer, either at=0A=
>             DLEP session initialization or by injection of messages=0A=
>             once a session has been established, and/or=0A=
>=0A=
>=0A=
> Also, the several paragraphs that begin with =93If the modem and router a=
re=94=0A=
> ought to be rewritten.  Proposed New Text is:=0A=
>=0A=
>          All DLEP implementations must also implement support for=0A=
>          IETF TLS [RFC5246], so that an operator always is able to choose=
=0A=
>          to deploy TLS with DLEP when the operator deems that appropriate=
.=0A=
>=0A=
>          Use of DLEP with TLS, however, might not be needed in some=0A=
>          DLEP deployments.  Additional guidance on TLS use with DLEP foll=
ows.=0A=
>=0A=
> 	When the modem and router are NOT both on the same layer-2=0A=
>          link (e.g. IP subnetwork, Ethernet VLAN) then session messages=
=0A=
>          could be altered by an off-link attacker in order to subvert the=
=0A=
>          behavior of either or both DLEP participants.  In short,=0A=
>          a man-in-the-middle attack by an off-link attacker is possible.=
=0A=
>          In these situations, deployment and use of TLS with DLEP is=0A=
>          RECOMMENDED.=0A=
>=0A=
>          In some deployments, for example deployments that include a=0A=
>          =93Layer-2 VPN=94 connecting different sites, there might be a=
=0A=
>          non-trivial risk of an on-link attacker.  Operators should=0A=
>          carefully consider the details of their deployment and their loc=
al=0A=
>          operational risk model. In situations where local risks warrant,=
=0A=
>          then deployment and use of TLS with DLEP is RECOMMENDED.=0A=
>=0A=
>=0A=
> Lastly, the final paragraph as written is not really acceptable in the=0A=
> modern IETF.  Here is Proposed New Text:=0A=
>=0A=
> 	Deployment of DLEP does not change the security risks for the=0A=
>          data plane (i.e. the data packets between a router and a modem).=
=0A=
>          In circumstances where there is non-trivial risk of an on-link=
=0A=
>          attacker, then the use of appropriate link-layer security mechan=
isms=0A=
>          (e.g. IEEE MAC-layer security [IEEE 802.10, IEEE 802.1AE] for da=
ta=0A=
>          packets between a router and a modem is RECOMMENDED.=0A=
>=0A=
> Informational References probably should add:=0A=
>=0A=
> 	[IEEE 802.1AE] IEEE, Standard for Local and Metropolitan Area Networks:=
=0A=
>                         Media Access Control (MAC) Security, IEEE, NJ, US=
A. 2006=0A=
>=0A=
> 	[IEEE 802.10]  IEEE, Standard for Local and Metropolitan Area Networks:=
=0A=
>                         Interoperable LAN/MAN Security (SILS), IEEE, NJ, =
USA. 1992.=0A=
>=0A=
> Yours,=0A=
>=0A=
> Ran=0A=
>=0A=
>=0A=
> _______________________________________________=0A=
> manet mailing list=0A=
> manet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/manet=0A=
>=0A=
=0A=


From nobody Tue Nov 24 09:25:22 2015
Return-Path: <rja.lists@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 661911B2FC1 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:25:21 -0800 (PST)
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 KAIr7aJH17Vv for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:25:15 -0800 (PST)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CFE51A86F6 for <manet@ietf.org>; Tue, 24 Nov 2015 09:25:15 -0800 (PST)
Received: by qkao63 with SMTP id o63so7536384qka.2 for <manet@ietf.org>; Tue, 24 Nov 2015 09:25:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=UsQzsEqifBbuRCghtmLBYi1hx/mR4OewqbEKIpFZoWw=; b=pT4G82NDoCM0O/KeRTZ48nbQZWo+x+OyPjhoLCrYMUhTj5FwiGP9FI8goG+MrLUwzc RrGnI5seziP6XJpCYTAoYLHYepyOFzv4DyJl7v/WRmXBIRJiHeTxwMfDcd+luKuxv50m bHdjXhpq0+bdpoFtCfP/na4z03/wFycUPxkSv2jxheSDPa58OlbotbDwzQJxRVGc1s07 5nQPyUSeuD5XakB5JB+YjI98Jv5n/9wm9zi6Q5r4TklxnhbTM2PfkkDHJNeYgdglVCqA BwRxEEd8eivZkbHX1gjpXTUjARqkSgE1qxkjs5nY1P3UPPE+SpyeHz7oLRsUgwIisige RhuQ==
X-Received: by 10.55.76.73 with SMTP id z70mr34421444qka.38.1448385914513; Tue, 24 Nov 2015 09:25:14 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id s20sm4477686qki.31.2015.11.24.09.25.13 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 09:25:14 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <09672065-ED6B-40F1-B36F-81E6B721061B@gmail.com>
Date: Tue, 24 Nov 2015 12:25:12 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/aurci1dURixKBfF370en8wT2V5I>
Subject: [manet] DLEP-17: IANA Considerations - example
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:25:21 -0000

RFC 5246 (http://www.ietf.org/rfc/rfc5246.txt) has some
"IANA Considerations=E2=80=9D text that might be helpful as an
example to the authors in trying to write clearer text=20
for DLEP=E2=80=99s IANA Considerations.

The text for =E2=80=9CTLS SignatureAlgorithm Registry=E2=80=9D is useful
as an example of what text generally looks like for a
newly defined IANA registry.

For each new IANA Registry, one ought to define, and the=20
RFC-5246 text on page 66 generally does define:
  - NAME of the registry (e.g. TLS SignatureAlgorithm Registry)
  - INITIAL VALUES of the registry (e.g. reference to Table N)
  - ASSIGNMENT POLICIES for future values of the registry,
    including explicit reservation of =E2=80=9CPrivate Use=E2=80=9D =
values.
  - RFC REFERENCE (This should be a reference to the DLEP RFC
    for the case of DLEP registries created by the DLEP draft.)

If the DLEP-17 text for =E2=80=9CIANA Considerations=E2=80=9D were much =
more=20
consistent with the IANA Considerations text from RFC-5246,
that would be very helpful, and likely would get that section
to where it really ought to be.

The WG also might want to consider having multiple sections of=20
reserved numbers, each with its own allocation policy, as TLS does.
For example, for a given registry, some (lower) numbers might be=20
allocated only by =E2=80=9CStandards Action=E2=80=9D, while other =
(middle) numbers=20
might be allocated only by =E2=80=9CSpecification Required=E2=80=9D or =
=E2=80=9CExpert Review=E2=80=9D,=20
all while retaining a =E2=80=9CPrivate Use=E2=80=9D block in the (upper) =
numbers.

Yours,

Ran



From nobody Tue Nov 24 09:32:52 2015
Return-Path: <rick@tropicalstormsoftware.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 030D51B2E47 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:32:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 IwqOBgVFRxip for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:32:50 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75ED51B3013 for <manet@ietf.org>; Tue, 24 Nov 2015 09:32:49 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 17:32:25 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: Security Considerations
Thread-Index: AQHRJshlGZtS6M2f1UaEMBWkMA+6tA==
Date: Tue, 24 Nov 2015 17:32:23 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B0540F@tss-server1.home.tropicalstormsoftware.com>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/CXtFV7zRDq5v8qKulqBcCGnZYvM>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:32:51 -0000

On 24/11/15 17:19, Rick Taylor wrote:=0A=
=0A=
Ran,=0A=
=0A=
You suggest:=0A=
=0A=
>> When the modem and router are NOT both on the same layer-2=0A=
>> link (e.g. IP subnetwork, Ethernet VLAN) then session messages=0A=
>> could be altered by an off-link attacker in order to subvert the=0A=
>> behavior of either or both DLEP participants.  In short,=0A=
>> a man-in-the-middle attack by an off-link attacker is possible.=0A=
>> In these situations, deployment and use of TLS with DLEP is=0A=
>> RECOMMENDED.=0A=
=0A=
We assume layer-2 transparency for the data plane already with DLEP =0A=
(Section 2, para 2).  If we assume the same layer-2 connectivity for the =
=0A=
control plane, can't we remove the TLS requirement altogether?=0A=
=0A=
You go on to recommend Layer-2 VPNs requiring some kind of external =0A=
security, so I'm starting to wonder if TLS is a red herring.=0A=
=0A=
Rick=0A=


From nobody Tue Nov 24 09:37:17 2015
Return-Path: <rick@tropicalstormsoftware.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 457AC1B3022 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:37:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 xHGUIQv5Ydxi for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:37:14 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1802B1B2F37 for <manet@ietf.org>; Tue, 24 Nov 2015 09:37:13 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 17:36:49 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: IANA Considerations - example
Thread-Index: AQHRJt0b4wuql899a0Gu/k7IUQYQHg==
Date: Tue, 24 Nov 2015 17:36:48 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B05464@tss-server1.home.tropicalstormsoftware.com>
References: <09672065-ED6B-40F1-B36F-81E6B721061B@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/LMIUEfMBjH_lyGicAxJf2qSCJoM>
Subject: Re: [manet] DLEP-17: IANA Considerations - example
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:37:15 -0000

On 24/11/15 17:25, RJ Atkinson wrote:=0A=
>=0A=
> RFC 5246 (http://www.ietf.org/rfc/rfc5246.txt) has some=0A=
> "IANA Considerations=94 text that might be helpful as an=0A=
> example to the authors in trying to write clearer text=0A=
> for DLEP=92s IANA Considerations.=0A=
>=0A=
> The text for =93TLS SignatureAlgorithm Registry=94 is useful=0A=
> as an example of what text generally looks like for a=0A=
> newly defined IANA registry.=0A=
>=0A=
> For each new IANA Registry, one ought to define, and the=0A=
> RFC-5246 text on page 66 generally does define:=0A=
>    - NAME of the registry (e.g. TLS SignatureAlgorithm Registry)=0A=
>    - INITIAL VALUES of the registry (e.g. reference to Table N)=0A=
>    - ASSIGNMENT POLICIES for future values of the registry,=0A=
>      including explicit reservation of =93Private Use=94 values.=0A=
>    - RFC REFERENCE (This should be a reference to the DLEP RFC=0A=
>      for the case of DLEP registries created by the DLEP draft.)=0A=
>=0A=
> If the DLEP-17 text for =93IANA Considerations=94 were much more=0A=
> consistent with the IANA Considerations text from RFC-5246,=0A=
> that would be very helpful, and likely would get that section=0A=
> to where it really ought to be.=0A=
>=0A=
> The WG also might want to consider having multiple sections of=0A=
> reserved numbers, each with its own allocation policy, as TLS does.=0A=
> For example, for a given registry, some (lower) numbers might be=0A=
> allocated only by =93Standards Action=94, while other (middle) numbers=0A=
> might be allocated only by =93Specification Required=94 or =93Expert Revi=
ew=94,=0A=
> all while retaining a =93Private Use=94 block in the (upper) numbers.=0A=
=0A=
My gut feeling is that Messages should require Standards Action as they =0A=
alter the protocol, where-as new metrics might only need Specification =0A=
Required.=0A=
=0A=
We will certainly give it some thought.=0A=
=0A=
Cheers,=0A=
=0A=
Rick=0A=


From nobody Tue Nov 24 09:38:08 2015
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 C10441B302F for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 8-D4Snc9IllS for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:38:06 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25A851B302B for <manet@ietf.org>; Tue, 24 Nov 2015 09:38:06 -0800 (PST)
Received: by wmww144 with SMTP id w144so148827008wmw.1 for <manet@ietf.org>; Tue, 24 Nov 2015 09:38:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:content-type; bh=2wlcnS2uj8/cLViFW1RcBUHx4T7FxwW+nY57kzaFOIE=; b=zNR2NVuDetTVU/VLrPav7aHrrqqWQOM/nCRLdAccEPgxSoy2nkgLTPlL4YLKjOVYHW 7a9e7r+tUE5//HM0OtKncYbW72tsPxeZuPiSow61ytP9vmRxMomOr7dvDkFxFRisCygD thCJ+JGNcORBsDLIcehfQDvpduLKCzZ1ur/MBvnI+pEl5HBSNeJ8AcQBqFX4tFYIFdcU rqKvc6XxXx8MTIpn6hDifnQflXhKCiGZvAUn5oxvAx2qsmnsV88Ayee8mNNR0OsvD/3b 06y6CsfBZP8fhBDRl5jEptg1+oB8bAIS4h/5X7HwzLWO+U93icSrcNwEEXtwuHPSZ5ey 5Y7A==
X-Received: by 10.194.2.193 with SMTP id 1mr33034312wjw.26.1448386684727; Tue, 24 Nov 2015 09:38:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Tue, 24 Nov 2015 09:37:35 -0800 (PST)
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 24 Nov 2015 18:37:35 +0100
Message-ID: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@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/euoayYpaqHYBDAJFiiqBuNOTSm8>
Subject: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:38:07 -0000

Hi,

I talked with Rick about it and we agree to open a thread for this.

I am seeing a security feature creep coming, and there is not much we can do.

we already added the option for TLS. But even in Prague I said that
TLS would not help if we don't secure the UDP beacon (downgrade
attack!) and somehow connect both security sessions (otherwise the
attacker can fool a secure UDP beacon which says "please no TLS").

Now we are talking about in-link Man in the Middle attackers. And
about "semi-mandatory" client AND server certificate. And we are still
not done with a "good" security solution. We are talking about
securing a DLEP connection with multiple IP hops without even
considering how the hell the bridged user space traffic would get over
this distance.

We don't even know what a sane "attacker model" for DLEP would look like.

>From my point of view we are killing a really good part of DLEP, the
zero configuration autodiscovery. Plug your DSL-Modem/Radio into your
Router and it will work!

"Oh, plug your DSL-Modem into your router, copy your router
certificate to your USB, go to the website of the Modem and upload it,
grab the client certificate and download it, upload it to the
Router... oh, and validate the Hashes please!" doesn't sound nice.

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

So I would like to propose something different. Lets talk about
Linklocal-only DLEP.

Make sure (with both IP addresses AND TTL field) that we only
communicate a single hop with DLEP, both UDP and TCP.

And lets throw out ALL TLS out of the DLEP draft.


There is already a way to secure a link against an attacker, its
called 802.1x. If someone wants to establish a "multihop DLEP
connection", just setup a secure layer-2 VPN. We can put both into a
security consideration section.


Lets REDUCE the complexity of the draft and keep the good parts.

Henning Rogge


From nobody Tue Nov 24 09:40:20 2015
Return-Path: <steven.matty@airbus.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 B35081B3039 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:40:18 -0800 (PST)
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, 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 UrYTGwTzUyrp for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:40:11 -0800 (PST)
Received: from mirabel.astrium.eads.net (mirabel.astrium.eads.net [194.62.210.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02F9D1B3037 for <manet@ietf.org>; Tue, 24 Nov 2015 09:40:10 -0800 (PST)
Received: from rosout.astrium.eads.net ([10.222.0.6]) by mirabel.astrium.eads.net (8.14.4/8.14.4) with ESMTP id tAOHe7dX005278; Tue, 24 Nov 2015 17:40:07 GMT
Received: from rosout.astrium.eads.net (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3EFFD20817A; Tue, 24 Nov 2015 17:40:07 +0000 (GMT)
Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 24194208133; Tue, 24 Nov 2015 17:40:07 +0000 (GMT)
X-IMSS-HAND-OFF-DIRECTIVE: 127.0.0.1:10026
Received: from AUK52839.UKN.UKNROOT.ASTRIUM.CORP (unknown [10.221.1.32]) by rosout.astrium.eads.net (Postfix) with ESMTPS id 7CB01208133; Tue, 24 Nov 2015 17:40:00 +0000 (GMT)
Received: from AUK52982.UKN.UKNROOT.ASTRIUM.CORP ([fe80::543e:db1:48aa:1c6]) by AUK52839.UKN.UKNROOT.ASTRIUM.CORP ([fe80::cdf2:d214:a3a9:7510%15]) with mapi id 14.03.0123.003; Tue, 24 Nov 2015 17:39:59 +0000
From: "MATTY, Steven" <steven.matty@airbus.com>
To: "'Rick Taylor'" <rick@tropicalstormsoftware.com>, RJ Atkinson <rja.lists@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: Security Considerations
Thread-Index: AQHRJshlyN6GAd9txUq9x4R7m3okGJ6rb1nA
Date: Tue, 24 Nov 2015 17:39:58 +0000
Message-ID: <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58B6@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <17688_1448385550_56549C0E_17688_6973_1_38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com>
In-Reply-To: <17688_1448385550_56549C0E_17688_6973_1_38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.221.1.73]
X-TM-AS-Product-Ver: IMSVA-9.0.0.1383-8.0.0.1202-21962.001
X-TM-AS-Result: No--22.694-5.0-31-10
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
X-imss-scan-details: No--22.694-5.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1383-8.0.1202-21962.001
X-TMASE-Result: 10--22.693800-5.000000
X-TMASE-MatchedRID: yebcs53SkkBNlZ1zEcyAY5CYtcHXhxbaoprEeoZHCQIVGU3zNNLOPuO/ ytE9sHcwL14PG/qYSRZMphObkHxJ6sAQ0nRNv2K2kRs1fAcYNHE026H7nOZLr1zcTq9mcd2jwua niM9QXy1EWyqmHrvq4BcRpPm6GTDMT925Dbv5kLyZroPNdqiG88yZqgcnwGktV6KWY8jugmX8SF 1BLqnNuTooRrzDbQSNl1YHZ9wuMafubBIKSwNFkBKnJVt5wZxQXArLpqs9pJd3vUA6/Pi03EflX cv8ssQvL9xq0QbZ7u5bBg+tviG6VdGETJv1/WyO6Zzj+kMRBrb2v20RxLDyN8j0Eew4TN42qg7P 8SLGMMfzOOM5ZR4QTzABNQ0gfw8/lHVBLjBDrjmEJ5wBUYI5/RNtTUpgahCn4aROJEypr9wyoJR NWYUu4J2sYap/+nB5ssOVUaT3xRF4kJF7CcEyKGwjJ4TFeU1uE3NxsGztrMtX14Hy+eYp72fhhf E3VnR1yZ16q0j5nbZFbXBjYsNDK4CkWuQJNIQ/z5rIW0RbS5i0NJ9wxH7tk2ecrqZc3vab8myX5 RK7cEUhMcYfYbjfq7BxtImTC0vqQEdNChTTbLXDa1qWPNOExrghEq8e8JZyzAdJD7JeNMPA4131 gxGFr9w30/QipyLgeiHJ4NstS4KH02hS6VHWl1Re8joruKtphfFxxGG2IMVXPwnnY5XL5EBfLI/ qgIpC0LanOvpsZ3iyslnbO/W7LXWKviQww/XedAg4yd14qAR7Y2lJ1FJ3HcnaL1ri/ilX2zUIfO RoaiIRW3Fo+hK3sE0LTMaS+PdlZLL+6mlrdoyeAiCmPx4NwMidYBYDjITp+gD2vYtOFhgqtq5d3 cxkNQP90fJP9eHt
X-TMASE-SNAP-Result: 1.801202.0001-0-1-22:0,12:0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/x8rZI1uBJxzwEVJ--Ieh0cV4tZ0>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:40:18 -0000

Hi Rick et al

Is this a confusion between the terms "implement" and "use"/"deploy?".  I=
 think Ran is saying that
all DLEP solutions MUST implement TLS support but it is not mandatory to =
"use" TLS (this is something
best left to the end user to decide whether to enable TLS when deploying)

For a DLEP router or DLEP radio to claim conformance to the DLEP standard=
 it MUST provide an implementation
which allows the user to enable TLS. It just doesn't HAVE to be enabled.

Regards

Steve

>-----Original Message-----
>From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Rick Taylor
>Sent: Tuesday, November 24, 2015 5:19 PM
>To: RJ Atkinson; MANET IETF
>Subject: Re: [manet] DLEP-17: Security Considerations
>
>Ran,
>
>I really like your proposed changes to the Security Considerations, but
>I do have a concern.  Many major radio manufacturers consider TLS a step
>too far, and mandating it for environments where it is considered
>unnecessary will prevent uptake of DLEP.
>
>I think we are all agreed that when there are multiple hops between
>modem and router then TLS is a MUST.  But when there is a single piece
>of wire between the devices, people will (possibly correctly) argue that
>it is pointless.
>
>Do you have any advice on how we could add some text to your
>recommendation along the lines of:
>
>"If you can prevent DLEP running over multiple hops in your
>implementation, then you MAY choose not to implement TLS."
>
>How one prevents multi-hop is left as an exercise to the reader...
>
>This is an open question to the WG as well.
>
>Cheers,
>
>Rick
>
>
>On 24/11/15 14:57, RJ Atkinson wrote:
>> All,
>>
>>
>> The "Security Considerations" text isn't really adequate.
>>
>> I suspect part of the problem is editorial.  I am supplying
>> candidate replacement text that I believe will be sufficient
>> for the draft to pass the IETF Security Area review.
>>
>>
>> Background:
>>    In the IETF, "implement" generally refers to code available
>>    to execute a feature in a product, while "use" or "deploy"
>>    refers to the operational decision of how to configure a product
>>    when installing it in an actual physical network.
>>
>>    I realize that some people (incorrectly) use "implement" to refer
>>    to deployment, but IETF protocol specifications generally try
>>    to avoid that confusion.
>>
>>    Also, unlike some other standards bodies, the IETF doesn't have a
>>    concept of "conformance testing".  Products that claim to implement
>>    an RFC are expected to implement it completely and properly,
>>    but there are no IETF "protocol police" checking a product to see
>>    whether each detail was done correctly.
>>
>>    Last, in the IETF, the long-standing custom is that "implementation=
"
>>    of security is mandatory, while "deployment/use" of security is
>>    optional.  The reasoning is that an operator best knows their own
>>    security risks, but if the implementation does not include the
>>    specified security mechanism (e.g. TLS) then (a) the implementation
>>    won't be interoperable and/or (b) the user won't be ABLE to deploy/=
use
>>    the security when they deem it appropriate.
>>
>>
>> Proposed New Text for Section 11, sub-heading 1:
>>
>> =091. An attacker might pretend to be a DLEP peer, either at
>>             DLEP session initialization or by injection of messages
>>             once a session has been established, and/or
>>
>>
>> Also, the several paragraphs that begin with "If the modem and router =
are"
>> ought to be rewritten.  Proposed New Text is:
>>
>>          All DLEP implementations must also implement support for
>>          IETF TLS [RFC5246], so that an operator always is able to cho=
ose
>>          to deploy TLS with DLEP when the operator deems that appropri=
ate.
>>
>>          Use of DLEP with TLS, however, might not be needed in some
>>          DLEP deployments.  Additional guidance on TLS use with DLEP f=
ollows.
>>
>> =09When the modem and router are NOT both on the same layer-2
>>          link (e.g. IP subnetwork, Ethernet VLAN) then session message=
s
>>          could be altered by an off-link attacker in order to subvert =
the
>>          behavior of either or both DLEP participants.  In short,
>>          a man-in-the-middle attack by an off-link attacker is possibl=
e.
>>          In these situations, deployment and use of TLS with DLEP is
>>          RECOMMENDED.
>>
>>          In some deployments, for example deployments that include a
>>          "Layer-2 VPN" connecting different sites, there might be a
>>          non-trivial risk of an on-link attacker.  Operators should
>>          carefully consider the details of their deployment and their =
local
>>          operational risk model. In situations where local risks warra=
nt,
>>          then deployment and use of TLS with DLEP is RECOMMENDED.
>>
>>
>> Lastly, the final paragraph as written is not really acceptable in the
>> modern IETF.  Here is Proposed New Text:
>>
>> =09Deployment of DLEP does not change the security risks for the
>>          data plane (i.e. the data packets between a router and a mode=
m).
>>          In circumstances where there is non-trivial risk of an on-lin=
k
>>          attacker, then the use of appropriate link-layer security mec=
hanisms
>>          (e.g. IEEE MAC-layer security [IEEE 802.10, IEEE 802.1AE] for=
 data
>>          packets between a router and a modem is RECOMMENDED.
>>
>> Informational References probably should add:
>>
>> =09[IEEE 802.1AE] IEEE, Standard for Local and Metropolitan Area
>Networks:
>>                         Media Access Control (MAC) Security, IEEE, NJ,=
 USA. 2006
>>
>> =09[IEEE 802.10]  IEEE, Standard for Local and Metropolitan Area
>Networks:
>>                         Interoperable LAN/MAN Security (SILS), IEEE, N=
J, USA. 1992.
>>
>> Yours,
>>
>> Ran
>>
>>
>> _______________________________________________
>> 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
>
>This mail has originated outside your organization, either from an exter=
nal
>partner or the Global Internet.
>Keep this in mind if you answer this message.
>

This email (including any attachments) may contain confidential and/or pr=
ivileged information or information otherwise protected from disclosure. =
If you are not the intended recipient, please notify the sender immediate=
ly, do not copy this message or any attachments and do not use it for any=
 purpose or disclose its content to any person, but delete this message a=
nd any attachments from your system. Airbus Defence and Space Limited dis=
claims any and all liability if this email transmission was virus corrupt=
ed, altered or falsified.
-o-
Emails to Airbus Defence and Space Limited may be processed, recorded and=
 monitored outside the UK.
-o-
Airbus Defence and Space Limited, Registered in England and Wales No. 244=
9259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, =
England


From nobody Tue Nov 24 09:42:36 2015
Return-Path: <rick@tropicalstormsoftware.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 7E2951B3039 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:42:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 356gG4FCO2Ux for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:42:33 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92A461B3043 for <manet@ietf.org>; Tue, 24 Nov 2015 09:42:32 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 17:42:05 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "MATTY, Steven" <steven.matty@airbus.com>, RJ Atkinson <rja.lists@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: Security Considerations
Thread-Index: AQHRJshlGZtS6M2f1UaEMBWkMA+6tA==
Date: Tue, 24 Nov 2015 17:42:03 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B054B8@tss-server1.home.tropicalstormsoftware.com>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <17688_1448385550_56549C0E_17688_6973_1_38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com> <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58B6@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/mT5-JizuFZK43a_Ch5vmXYBFqMQ>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:42:35 -0000

Steve,=0A=
=0A=
You are right, I agree that is what Ran is saying.  However, I still =0A=
stand by my comment that some radio vendors are pushing back against =0A=
*implementing* TLS regardless of deployment.=0A=
=0A=
Rick=0A=
=0A=
On 24/11/15 17:40, MATTY, Steven wrote:=0A=
> Hi Rick et al=0A=
>=0A=
> Is this a confusion between the terms "implement" and "use"/"deploy?".  I=
 think Ran is saying that=0A=
> all DLEP solutions MUST implement TLS support but it is not mandatory to =
"use" TLS (this is something=0A=
> best left to the end user to decide whether to enable TLS when deploying)=
=0A=
>=0A=
> For a DLEP router or DLEP radio to claim conformance to the DLEP standard=
 it MUST provide an implementation=0A=
> which allows the user to enable TLS. It just doesn't HAVE to be enabled.=
=0A=
>=0A=
> Regards=0A=
>=0A=
> Steve=0A=
>=0A=
>> -----Original Message-----=0A=
>> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Rick Taylor=0A=
>> Sent: Tuesday, November 24, 2015 5:19 PM=0A=
>> To: RJ Atkinson; MANET IETF=0A=
>> Subject: Re: [manet] DLEP-17: Security Considerations=0A=
>>=0A=
>> Ran,=0A=
>>=0A=
>> I really like your proposed changes to the Security Considerations, but=
=0A=
>> I do have a concern.  Many major radio manufacturers consider TLS a step=
=0A=
>> too far, and mandating it for environments where it is considered=0A=
>> unnecessary will prevent uptake of DLEP.=0A=
>>=0A=
>> I think we are all agreed that when there are multiple hops between=0A=
>> modem and router then TLS is a MUST.  But when there is a single piece=
=0A=
>> of wire between the devices, people will (possibly correctly) argue that=
=0A=
>> it is pointless.=0A=
>>=0A=
>> Do you have any advice on how we could add some text to your=0A=
>> recommendation along the lines of:=0A=
>>=0A=
>> "If you can prevent DLEP running over multiple hops in your=0A=
>> implementation, then you MAY choose not to implement TLS."=0A=
>>=0A=
>> How one prevents multi-hop is left as an exercise to the reader...=0A=
>>=0A=
>> This is an open question to the WG as well.=0A=
>>=0A=
>> Cheers,=0A=
>>=0A=
>> Rick=0A=
>>=0A=
>>=0A=
>> On 24/11/15 14:57, RJ Atkinson wrote:=0A=
>>> All,=0A=
>>>=0A=
>>>=0A=
>>> The "Security Considerations" text isn't really adequate.=0A=
>>>=0A=
>>> I suspect part of the problem is editorial.  I am supplying=0A=
>>> candidate replacement text that I believe will be sufficient=0A=
>>> for the draft to pass the IETF Security Area review.=0A=
>>>=0A=
>>>=0A=
>>> Background:=0A=
>>>     In the IETF, "implement" generally refers to code available=0A=
>>>     to execute a feature in a product, while "use" or "deploy"=0A=
>>>     refers to the operational decision of how to configure a product=0A=
>>>     when installing it in an actual physical network.=0A=
>>>=0A=
>>>     I realize that some people (incorrectly) use "implement" to refer=
=0A=
>>>     to deployment, but IETF protocol specifications generally try=0A=
>>>     to avoid that confusion.=0A=
>>>=0A=
>>>     Also, unlike some other standards bodies, the IETF doesn't have a=
=0A=
>>>     concept of "conformance testing".  Products that claim to implement=
=0A=
>>>     an RFC are expected to implement it completely and properly,=0A=
>>>     but there are no IETF "protocol police" checking a product to see=
=0A=
>>>     whether each detail was done correctly.=0A=
>>>=0A=
>>>     Last, in the IETF, the long-standing custom is that "implementation=
"=0A=
>>>     of security is mandatory, while "deployment/use" of security is=0A=
>>>     optional.  The reasoning is that an operator best knows their own=
=0A=
>>>     security risks, but if the implementation does not include the=0A=
>>>     specified security mechanism (e.g. TLS) then (a) the implementation=
=0A=
>>>     won't be interoperable and/or (b) the user won't be ABLE to deploy/=
use=0A=
>>>     the security when they deem it appropriate.=0A=
>>>=0A=
>>>=0A=
>>> Proposed New Text for Section 11, sub-heading 1:=0A=
>>>=0A=
>>> 	1. An attacker might pretend to be a DLEP peer, either at=0A=
>>>              DLEP session initialization or by injection of messages=0A=
>>>              once a session has been established, and/or=0A=
>>>=0A=
>>>=0A=
>>> Also, the several paragraphs that begin with "If the modem and router a=
re"=0A=
>>> ought to be rewritten.  Proposed New Text is:=0A=
>>>=0A=
>>>           All DLEP implementations must also implement support for=0A=
>>>           IETF TLS [RFC5246], so that an operator always is able to cho=
ose=0A=
>>>           to deploy TLS with DLEP when the operator deems that appropri=
ate.=0A=
>>>=0A=
>>>           Use of DLEP with TLS, however, might not be needed in some=0A=
>>>           DLEP deployments.  Additional guidance on TLS use with DLEP f=
ollows.=0A=
>>>=0A=
>>> 	When the modem and router are NOT both on the same layer-2=0A=
>>>           link (e.g. IP subnetwork, Ethernet VLAN) then session message=
s=0A=
>>>           could be altered by an off-link attacker in order to subvert =
the=0A=
>>>           behavior of either or both DLEP participants.  In short,=0A=
>>>           a man-in-the-middle attack by an off-link attacker is possibl=
e.=0A=
>>>           In these situations, deployment and use of TLS with DLEP is=
=0A=
>>>           RECOMMENDED.=0A=
>>>=0A=
>>>           In some deployments, for example deployments that include a=
=0A=
>>>           "Layer-2 VPN" connecting different sites, there might be a=0A=
>>>           non-trivial risk of an on-link attacker.  Operators should=0A=
>>>           carefully consider the details of their deployment and their =
local=0A=
>>>           operational risk model. In situations where local risks warra=
nt,=0A=
>>>           then deployment and use of TLS with DLEP is RECOMMENDED.=0A=
>>>=0A=
>>>=0A=
>>> Lastly, the final paragraph as written is not really acceptable in the=
=0A=
>>> modern IETF.  Here is Proposed New Text:=0A=
>>>=0A=
>>> 	Deployment of DLEP does not change the security risks for the=0A=
>>>           data plane (i.e. the data packets between a router and a mode=
m).=0A=
>>>           In circumstances where there is non-trivial risk of an on-lin=
k=0A=
>>>           attacker, then the use of appropriate link-layer security mec=
hanisms=0A=
>>>           (e.g. IEEE MAC-layer security [IEEE 802.10, IEEE 802.1AE] for=
 data=0A=
>>>           packets between a router and a modem is RECOMMENDED.=0A=
>>>=0A=
>>> Informational References probably should add:=0A=
>>>=0A=
>>> 	[IEEE 802.1AE] IEEE, Standard for Local and Metropolitan Area=0A=
>> Networks:=0A=
>>>                          Media Access Control (MAC) Security, IEEE, NJ,=
 USA. 2006=0A=
>>>=0A=
>>> 	[IEEE 802.10]  IEEE, Standard for Local and Metropolitan Area=0A=
>> Networks:=0A=
>>>                          Interoperable LAN/MAN Security (SILS), IEEE, N=
J, USA. 1992.=0A=
>>>=0A=
>>> Yours,=0A=
>>>=0A=
>>> Ran=0A=
>>>=0A=
>>>=0A=
>>> _______________________________________________=0A=
>>> manet mailing list=0A=
>>> manet@ietf.org=0A=
>>> https://www.ietf.org/mailman/listinfo/manet=0A=
>>>=0A=
>>=0A=
>>=0A=
>> _______________________________________________=0A=
>> manet mailing list=0A=
>> manet@ietf.org=0A=
>> https://www.ietf.org/mailman/listinfo/manet=0A=
>>=0A=
>> This mail has originated outside your organization, either from an exter=
nal=0A=
>> partner or the Global Internet.=0A=
>> Keep this in mind if you answer this message.=0A=
>>=0A=
>=0A=
> This email (including any attachments) may contain confidential and/or pr=
ivileged information or information otherwise protected from disclosure. If=
 you are not the intended recipient, please notify the sender immediately, =
do not copy this message or any attachments and do not use it for any purpo=
se or disclose its content to any person, but delete this message and any a=
ttachments from your system. Airbus Defence and Space Limited disclaims any=
 and all liability if this email transmission was virus corrupted, altered =
or falsified.=0A=
> -o-=0A=
> Emails to Airbus Defence and Space Limited may be processed, recorded and=
 monitored outside the UK.=0A=
> -o-=0A=
> Airbus Defence and Space Limited, Registered in England and Wales No. 244=
9259=0A=
> Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, =
England=0A=
>=0A=
>=0A=
=0A=


From nobody Tue Nov 24 09:46:51 2015
Return-Path: <steven.matty@airbus.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 1F28D1B3025 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:46:50 -0800 (PST)
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, 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 CFEUd9zEJbw1 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:46:48 -0800 (PST)
Received: from mirabel.astrium.eads.net (mirabel.astrium.eads.net [194.62.210.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 516521B3026 for <manet@ietf.org>; Tue, 24 Nov 2015 09:46:46 -0800 (PST)
Received: from rosout.astrium.eads.net ([10.222.0.6]) by mirabel.astrium.eads.net (8.14.4/8.14.4) with ESMTP id tAOHkhQK005563; Tue, 24 Nov 2015 17:46:43 GMT
Received: from rosout.astrium.eads.net (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 47476208304; Tue, 24 Nov 2015 17:46:43 +0000 (GMT)
Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 372D4208133; Tue, 24 Nov 2015 17:46:43 +0000 (GMT)
X-IMSS-HAND-OFF-DIRECTIVE: 127.0.0.1:10026
Received: from AUK52839.UKN.UKNROOT.ASTRIUM.CORP (unknown [10.221.1.32]) by rosout.astrium.eads.net (Postfix) with ESMTPS id 99777208133; Tue, 24 Nov 2015 17:46:41 +0000 (GMT)
Received: from AUK52982.UKN.UKNROOT.ASTRIUM.CORP ([fe80::543e:db1:48aa:1c6]) by AUK52839.UKN.UKNROOT.ASTRIUM.CORP ([fe80::cdf2:d214:a3a9:7510%15]) with mapi id 14.03.0123.003; Tue, 24 Nov 2015 17:46:41 +0000
From: "MATTY, Steven" <steven.matty@airbus.com>
To: "'Rick Taylor'" <rick@tropicalstormsoftware.com>, "'RJ Atkinson'" <rja.lists@gmail.com>, "'MANET IETF'" <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: Security Considerations
Thread-Index: AQHRJshlyN6GAd9txUq9x4R7m3okGJ6rb1nAgAADAzA=
Date: Tue, 24 Nov 2015 17:46:40 +0000
Message-ID: <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58C7@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <17688_1448385550_56549C0E_17688_6973_1_38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com> <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58B6@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
In-Reply-To: <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58B6@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.221.1.73]
X-TM-AS-Product-Ver: IMSVA-9.0.0.1383-8.0.0.1202-21962.001
X-TM-AS-Result: No--21.070-5.0-31-10
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
X-imss-scan-details: No--21.070-5.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1383-8.0.1202-21962.001
X-TMASE-Result: 10--21.070200-5.000000
X-TMASE-MatchedRID: yebcs53SkkCQ4R94VvPFubxygpRxo469pwnFZnn+VHylvIixP/JrwaML o6XddXOYTWLw2jvbfpxcQYBu5oPw5Xz5lEEBuvac1yMJs9mBCcVQCOsAlaxN79+w/Z/BUog+EFM wn2lXrJeh1b/0SzIj8RleFt8BdZ33lh5qb5HiiQf3gsXe4cCmtKHXXqNw58ALWP9qYuzytBJQqb MfbYKhsvheRyvm5CI72oz+2qezHaT8aZXfXZG9JMhI95kTx6VemWGJLfJ2t7daW2Ktn+I8/tmk9 xmkVZss+DdBRY5GR53sl4gtJ3R3f0+3qIVpZwrEXP5rFAucBUHomPrNi98UBIhlq83HEbL+04aN lSoZaMTERF9kT2ceMKeAlEiFDc3d2X53LeVAc3EQuNZEyiTChb8+q17GFLKRRjHvrQ40Nxbl6AM 4Aa3gFgRP1FrIYU7Q2aDf8mMchGtmwT1tP6avkmgws6g0ewz2GW6TfocNCnudwU/qXYxHvMgPhC jBGUV+V1LKlmsKXRNrD4pJc/cu5xr7/qTof2dak3ewifG2MNMPRZDLPHU+341Oeo4wEgnhb2Kvi VER2l+pzZ9l9k2LiLs9OusH9JJyhd8nEZR/hIPzuBT1hmZLD9EHPXzvw9jkSSUXkvSVAdyAEapd 1DGem7AuD3QsPHdtD+Y7lG81O8fEPT0UZOWRrI+YSzwl92XTcW+VwHmrYOXf0XHmH2ZMPpHZY1M 4VObvwfO5L/qwS+nQXnWb4yS/ffK4UyeXB6c8+mHRL3uzOiIax3hQAS8V1eouc5Rcf1B0YbTRn9 kRP82vxGOtmo34h5Ylxuk1ogQA+zoAW8R15l+eAiCmPx4NwMidYBYDjITp+gD2vYtOFhgqtq5d3 cxkNQP90fJP9eHt
X-TMASE-SNAP-Result: 1.801202.0001-0-1-22:0,12:0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/1AW1WHA1E_Ddk-ltN_BsPlH8hto>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:46:50 -0000

Hi Rick

Please ignore my comment. I mis-read your comments...

Time to go home I think

Regards

Steve

>-----Original Message-----
>From: MATTY, Steven
>Sent: Tuesday, November 24, 2015 5:40 PM
>To: 'Rick Taylor'; RJ Atkinson; MANET IETF
>Subject: RE: [manet] DLEP-17: Security Considerations
>
>Hi Rick et al
>
>Is this a confusion between the terms "implement" and "use"/"deploy?".  =
I
>think Ran is saying that
>all DLEP solutions MUST implement TLS support but it is not mandatory to
>"use" TLS (this is something
>best left to the end user to decide whether to enable TLS when deploying=
)
>
>For a DLEP router or DLEP radio to claim conformance to the DLEP standar=
d it
>MUST provide an implementation
>which allows the user to enable TLS. It just doesn't HAVE to be enabled.
>
>Regards
>
>Steve
>
>>-----Original Message-----
>>From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Rick Taylor
>>Sent: Tuesday, November 24, 2015 5:19 PM
>>To: RJ Atkinson; MANET IETF
>>Subject: Re: [manet] DLEP-17: Security Considerations
>>
>>Ran,
>>
>>I really like your proposed changes to the Security Considerations, but
>>I do have a concern.  Many major radio manufacturers consider TLS a ste=
p
>>too far, and mandating it for environments where it is considered
>>unnecessary will prevent uptake of DLEP.
>>
>>I think we are all agreed that when there are multiple hops between
>>modem and router then TLS is a MUST.  But when there is a single piece
>>of wire between the devices, people will (possibly correctly) argue tha=
t
>>it is pointless.
>>
>>Do you have any advice on how we could add some text to your
>>recommendation along the lines of:
>>
>>"If you can prevent DLEP running over multiple hops in your
>>implementation, then you MAY choose not to implement TLS."
>>
>>How one prevents multi-hop is left as an exercise to the reader...
>>
>>This is an open question to the WG as well.
>>
>>Cheers,
>>
>>Rick
>>
>>
>>On 24/11/15 14:57, RJ Atkinson wrote:
>>> All,
>>>
>>>
>>> The "Security Considerations" text isn't really adequate.
>>>
>>> I suspect part of the problem is editorial.  I am supplying
>>> candidate replacement text that I believe will be sufficient
>>> for the draft to pass the IETF Security Area review.
>>>
>>>
>>> Background:
>>>    In the IETF, "implement" generally refers to code available
>>>    to execute a feature in a product, while "use" or "deploy"
>>>    refers to the operational decision of how to configure a product
>>>    when installing it in an actual physical network.
>>>
>>>    I realize that some people (incorrectly) use "implement" to refer
>>>    to deployment, but IETF protocol specifications generally try
>>>    to avoid that confusion.
>>>
>>>    Also, unlike some other standards bodies, the IETF doesn't have a
>>>    concept of "conformance testing".  Products that claim to implemen=
t
>>>    an RFC are expected to implement it completely and properly,
>>>    but there are no IETF "protocol police" checking a product to see
>>>    whether each detail was done correctly.
>>>
>>>    Last, in the IETF, the long-standing custom is that "implementatio=
n"
>>>    of security is mandatory, while "deployment/use" of security is
>>>    optional.  The reasoning is that an operator best knows their own
>>>    security risks, but if the implementation does not include the
>>>    specified security mechanism (e.g. TLS) then (a) the implementatio=
n
>>>    won't be interoperable and/or (b) the user won't be ABLE to deploy=
/use
>>>    the security when they deem it appropriate.
>>>
>>>
>>> Proposed New Text for Section 11, sub-heading 1:
>>>
>>> =091. An attacker might pretend to be a DLEP peer, either at
>>>             DLEP session initialization or by injection of messages
>>>             once a session has been established, and/or
>>>
>>>
>>> Also, the several paragraphs that begin with "If the modem and router=
 are"
>>> ought to be rewritten.  Proposed New Text is:
>>>
>>>          All DLEP implementations must also implement support for
>>>          IETF TLS [RFC5246], so that an operator always is able to ch=
oose
>>>          to deploy TLS with DLEP when the operator deems that appropr=
iate.
>>>
>>>          Use of DLEP with TLS, however, might not be needed in some
>>>          DLEP deployments.  Additional guidance on TLS use with DLEP =
follows.
>>>
>>> =09When the modem and router are NOT both on the same layer-2
>>>          link (e.g. IP subnetwork, Ethernet VLAN) then session messag=
es
>>>          could be altered by an off-link attacker in order to subvert=
 the
>>>          behavior of either or both DLEP participants.  In short,
>>>          a man-in-the-middle attack by an off-link attacker is possib=
le.
>>>          In these situations, deployment and use of TLS with DLEP is
>>>          RECOMMENDED.
>>>
>>>          In some deployments, for example deployments that include a
>>>          "Layer-2 VPN" connecting different sites, there might be a
>>>          non-trivial risk of an on-link attacker.  Operators should
>>>          carefully consider the details of their deployment and their=
 local
>>>          operational risk model. In situations where local risks warr=
ant,
>>>          then deployment and use of TLS with DLEP is RECOMMENDED.
>>>
>>>
>>> Lastly, the final paragraph as written is not really acceptable in th=
e
>>> modern IETF.  Here is Proposed New Text:
>>>
>>> =09Deployment of DLEP does not change the security risks for the
>>>          data plane (i.e. the data packets between a router and a mod=
em).
>>>          In circumstances where there is non-trivial risk of an on-li=
nk
>>>          attacker, then the use of appropriate link-layer security me=
chanisms
>>>          (e.g. IEEE MAC-layer security [IEEE 802.10, IEEE 802.1AE] fo=
r data
>>>          packets between a router and a modem is RECOMMENDED.
>>>
>>> Informational References probably should add:
>>>
>>> =09[IEEE 802.1AE] IEEE, Standard for Local and Metropolitan Area
>>Networks:
>>>                         Media Access Control (MAC) Security, IEEE, NJ=
, USA. 2006
>>>
>>> =09[IEEE 802.10]  IEEE, Standard for Local and Metropolitan Area
>>Networks:
>>>                         Interoperable LAN/MAN Security (SILS), IEEE, =
NJ, USA. 1992.
>>>
>>> Yours,
>>>
>>> Ran
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>This mail has originated outside your organization, either from an exte=
rnal
>>partner or the Global Internet.
>>Keep this in mind if you answer this message.
>>

This email (including any attachments) may contain confidential and/or pr=
ivileged information or information otherwise protected from disclosure. =
If you are not the intended recipient, please notify the sender immediate=
ly, do not copy this message or any attachments and do not use it for any=
 purpose or disclose its content to any person, but delete this message a=
nd any attachments from your system. Airbus Defence and Space Limited dis=
claims any and all liability if this email transmission was virus corrupt=
ed, altered or falsified.
-o-
Emails to Airbus Defence and Space Limited may be processed, recorded and=
 monitored outside the UK.
-o-
Airbus Defence and Space Limited, Registered in England and Wales No. 244=
9259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, =
England


From nobody Tue Nov 24 09:47:32 2015
Return-Path: <rja.lists@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 D0FE31B3026 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:47:31 -0800 (PST)
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 Jk6WTBOHT8q6 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:47:30 -0800 (PST)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7593A1B3018 for <manet@ietf.org>; Tue, 24 Nov 2015 09:47:30 -0800 (PST)
Received: by qkda6 with SMTP id a6so7809488qkd.3 for <manet@ietf.org>; Tue, 24 Nov 2015 09:47:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=fHVrC0yErCHNDdpbycuXHWyYZNk5iPWgO+EWiynxWyI=; b=J6d5RFepEdfahXxdjLqNF6xUtKyHiFueXjocF8aEsYRmOP82+nGQuhq8ChYTuUI6V6 AXVfwfkHQ7jR8HuZZA2y6t01QP4zmFfjKAVd6/uJvPIwKS4sYO6ZGruwlLUwGpmhgOu/ UBvZAhujrxpJXlQSFkVrSbWBAxsvp0+R6h3ggLrvbz86F9l4kjAhNeo2a7gWvoIfd6g4 TBhpfP8tPQp/EQsjEEVFDDm6R5MzRTmhfA5QIQJ/pHpOvvwbyvqZ2tyX21hiy+SpSZ7H uO75D20RFPxzdc8NqoO6SWl2jyE2zha+wqQbqMfYiFvAP1ySkSZHWr5vTc/TG1XYBii5 HyQg==
X-Received: by 10.55.23.170 with SMTP id 42mr33864002qkx.42.1448387249522; Tue, 24 Nov 2015 09:47:29 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id i124sm4418888qhi.29.2015.11.24.09.47.28 for <manet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 09:47:29 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <645B94E8-819A-4C4E-8477-089EA63C1303@gmail.com>
Date: Tue, 24 Nov 2015 12:47:27 -0500
To: MANET IETF <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/G3pFoK8BKznfkQL8a1euwVpynis>
Subject: [manet] DLEP-17:  initial assignment tables & nearby text
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:47:32 -0000

1. Signals/Messages
--------------------
Section 9.0, 3rd paragraph, says:
	=E2=80=9CThe core DLEP signals and messages are:=E2=80=9D

Table 1, which contains also items that I had not thought
were =E2=80=9Ccore DLEP signals and messages=E2=80=9D (e.g. Private Use
allocation), then follows.

My suggestion is to change the text above to read:
	=E2=80=9CThe core DLEP signals and messages have Type Code
         values from 1 to 16, inclusive.  The initial values
         for the DLEP Signals & Messages Registry are found
         in Table 1.=E2=80=9D


2. Data Items
--------------
Section 10.0, 2nd paragraph, says:
	=E2=80=9CThe core DLEP data items are:=E2=80=9D

Table 2, which contains also items that I had not thought
were =E2=80=9Ccore DLEP data items=E2=80=9D (e.g. Private Use =
allocation)
then follows.

My suggestion is to change the quoted text above to read:
	=E2=80=9CThe core DLEP data items have Type Code values=20
	from 1 to 20, inclusive.  The initial values for
        the DLEP Data Item Registry are found in Table 2.=E2=80=9D

3. Status Codes
---------------
(We don=E2=80=99t seem to have a defined set of =E2=80=9Ccore=E2=80=9D =
DLEP status codes,
which is OK with me, but unexpected after defining =E2=80=9Ccore=E2=80=9D =
values
earlier.)

I suggest inserting the following sentence just before
Table 3:
	=E2=80=9CThe initial values for the DLEP Status Codes Registry
	are found in Table 3.=E2=80=9D


4. Extension Types
------------------

(editorial)=20
Section 12.6 says in part:
	=E2=80=9CCurrent allocations are:=E2=80=9D

This ought instead to read:
	=E2=80=9CInitial allocations are:=E2=80=9D

because the reader=E2=80=99s definition of =E2=80=9Ccurrent=E2=80=9D is =
"when
they are reading the specification", rather than=20
"the date that the specification was written=E2=80=9D.

The =E2=80=9Ccurrent=E2=80=9D set is whatever the IANA Registry web page
says on the =E2=80=9Ccurrent day=E2=80=9D that one looks at that =
registry.


Thanks,

Ran





From nobody Tue Nov 24 09:47:54 2015
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 E1C481B2FFD for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:47:52 -0800 (PST)
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 EZkFnm9yK832 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:47:51 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC1871B3054 for <manet@ietf.org>; Tue, 24 Nov 2015 09:47:49 -0800 (PST)
Received: by wmec201 with SMTP id c201so37550349wme.1 for <manet@ietf.org>; Tue, 24 Nov 2015 09:47:48 -0800 (PST)
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=Avva3YoMlDYB/koweFAW6Xblixc31/7HHMN2x2r+eZ8=; b=aemTerHPkHdAQYriZHlD121zW5xJP8rY/0A05IM2ADpg3key83pDEZDe0uW1b1m8+A G+gAqr+Rps0YDmhRLLn4HTbKMYOz15LyKLEFhCFgxEtQjscoGOS3GkMSHmiJZX6ss4uz 6/vNd3gyDh6n1zwEqJqyne9Q5SZzQbb5vO3z5HN5vcx1Xwrl/6CDWmeAcxIiccfn5Diu 9hL3U3W9rDZzmtsCUxX8ZLnXeoWiWmQqX4fhagHGd2VnbS8idCdIMibldGqgbvG19NMl Yo+Lmf+l5TofvTgzoqUaqLoqUq9SxITs4H8SlDI+OgBEjYY/OVSw4aalI6cpBi8YpOXL KLmA==
X-Received: by 10.28.141.17 with SMTP id p17mr25889598wmd.35.1448387268368; Tue, 24 Nov 2015 09:47:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Tue, 24 Nov 2015 09:47:18 -0800 (PST)
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8AF5D1E@tss-server1.home.tropicalstormsoftware.com>
References: <38A5475DE83986499AEACD2CFAFC3F9801A8AF5D1E@tss-server1.home.tropicalstormsoftware.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 24 Nov 2015 18:47:18 +0100
Message-ID: <CAGnRvur9H3tQvPWX9BY8SPdssjJ-_gwiSu5ViQpRokypwPogig@mail.gmail.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/a5x3JHN60rkbA9hvk-ab2W7e9x8>
Cc: manet IETF <manet@ietf.org>
Subject: Re: [manet] New individual 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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:47:53 -0000

On Thu, Nov 19, 2015 at 4:02 PM, Rick Taylor
<rick@tropicalstormsoftware.com> wrote:
> Hi All,
>
> I have just submitted a new individual draft: DLEP Destination Service
> Announcement (https://www.ietf.org/id/draft-taylor-manet-dlep-dsa-00.txt)
>
> This is an extension to DLEP, and so should probably wait for DLEP to
> progress, but I am asking for working group adoption.

Just to be sure, this is similar to the transfer of IP addresses
between DLEP Radio and Router, right?

If you have some "Radio magic" that can propagate the information you
are fine... if not you don't use it.

Henning Rogge


From nobody Tue Nov 24 09:49:13 2015
Return-Path: <rick@tropicalstormsoftware.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 7C1111B3034 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:49:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 PzdM81CA8YDo for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:49:10 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40A011B3031 for <manet@ietf.org>; Tue, 24 Nov 2015 09:49:10 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 17:48:38 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] Linklocal DLEP
Thread-Index: AQHRJt7l9LrXpBvSJE2u010DeCngeA==
Date: Tue, 24 Nov 2015 17:48:37 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B0551F@tss-server1.home.tropicalstormsoftware.com>
References: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/0xys_eJqllJszLY4XXS2imAQaps>
Subject: Re: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:49:12 -0000

All,=0A=
=0A=
I'm a +1 on this one.=0A=
=0A=
We keep discussing this concept of multi-hop DLEP that we are trying to =0A=
secure, but given the layer-2 connectivity assumption in DLEP, I'm not =0A=
sure if it's actually possible to have multi-hop DLEP!=0A=
=0A=
If someone can describe how multi-hop DLEP works (I'm too tired to try =0A=
it now) then we can worry about TLS.=0A=
=0A=
Rick=0A=
=0A=
P.S. I love ASCII art, give me a network diagram or I'm going to ask =0A=
dumb questions.=0A=
=0A=
On 24/11/15 17:38, Henning Rogge wrote:=0A=
> Hi,=0A=
>=0A=
> I talked with Rick about it and we agree to open a thread for this.=0A=
>=0A=
> I am seeing a security feature creep coming, and there is not much we can=
 do.=0A=
>=0A=
> we already added the option for TLS. But even in Prague I said that=0A=
> TLS would not help if we don't secure the UDP beacon (downgrade=0A=
> attack!) and somehow connect both security sessions (otherwise the=0A=
> attacker can fool a secure UDP beacon which says "please no TLS").=0A=
>=0A=
> Now we are talking about in-link Man in the Middle attackers. And=0A=
> about "semi-mandatory" client AND server certificate. And we are still=0A=
> not done with a "good" security solution. We are talking about=0A=
> securing a DLEP connection with multiple IP hops without even=0A=
> considering how the hell the bridged user space traffic would get over=0A=
> this distance.=0A=
>=0A=
> We don't even know what a sane "attacker model" for DLEP would look like.=
=0A=
>=0A=
>>From my point of view we are killing a really good part of DLEP, the=0A=
> zero configuration autodiscovery. Plug your DSL-Modem/Radio into your=0A=
> Router and it will work!=0A=
>=0A=
> "Oh, plug your DSL-Modem into your router, copy your router=0A=
> certificate to your USB, go to the website of the Modem and upload it,=0A=
> grab the client certificate and download it, upload it to the=0A=
> Router... oh, and validate the Hashes please!" doesn't sound nice.=0A=
>=0A=
> -----------------------=0A=
>=0A=
> So I would like to propose something different. Lets talk about=0A=
> Linklocal-only DLEP.=0A=
>=0A=
> Make sure (with both IP addresses AND TTL field) that we only=0A=
> communicate a single hop with DLEP, both UDP and TCP.=0A=
>=0A=
> And lets throw out ALL TLS out of the DLEP draft.=0A=
>=0A=
>=0A=
> There is already a way to secure a link against an attacker, its=0A=
> called 802.1x. If someone wants to establish a "multihop DLEP=0A=
> connection", just setup a secure layer-2 VPN. We can put both into a=0A=
> security consideration section.=0A=
>=0A=
>=0A=
> Lets REDUCE the complexity of the draft and keep the good parts.=0A=
>=0A=
> Henning Rogge=0A=
>=0A=
> _______________________________________________=0A=
> manet mailing list=0A=
> manet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/manet=0A=
>=0A=
=0A=


From nobody Tue Nov 24 09:52:50 2015
Return-Path: <rick@tropicalstormsoftware.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 A8C781B3061 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:52:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 t2n64JvXoWp0 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:52:48 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA7441B3060 for <manet@ietf.org>; Tue, 24 Nov 2015 09:52:47 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Tue, 24 Nov 2015 17:52:13 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>
Thread-Topic: [manet] New individual draft
Thread-Index: AQHRJuA4G00PI57brUODW+SFsU1q5Q==
Date: Tue, 24 Nov 2015 17:52:12 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B0556F@tss-server1.home.tropicalstormsoftware.com>
References: <38A5475DE83986499AEACD2CFAFC3F9801A8AF5D1E@tss-server1.home.tropicalstormsoftware.com> <CAGnRvur9H3tQvPWX9BY8SPdssjJ-_gwiSu5ViQpRokypwPogig@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/QlBHAaNf5rEKPseTcc1nnqib_7w>
Cc: manet IETF <manet@ietf.org>
Subject: Re: [manet] New individual 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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:52:49 -0000

On 24/11/15 17:47, Henning Rogge wrote:=0A=
> On Thu, Nov 19, 2015 at 4:02 PM, Rick Taylor=0A=
> <rick@tropicalstormsoftware.com> wrote:=0A=
>> Hi All,=0A=
>>=0A=
>> I have just submitted a new individual draft: DLEP Destination Service=
=0A=
>> Announcement (https://www.ietf.org/id/draft-taylor-manet-dlep-dsa-00.txt=
)=0A=
>>=0A=
>> This is an extension to DLEP, and so should probably wait for DLEP to=0A=
>> progress, but I am asking for working group adoption.=0A=
>=0A=
> Just to be sure, this is similar to the transfer of IP addresses=0A=
> between DLEP Radio and Router, right?=0A=
>=0A=
> If you have some "Radio magic" that can propagate the information you=0A=
> are fine... if not you don't use it.=0A=
=0A=
Yes, that's exactly it.  If you have room in your radio magic for it, =0A=
you can choose to do it.  If not, it's an extension, don't announce it.=0A=
=0A=
Rick=0A=


From nobody Tue Nov 24 09:58:06 2015
Return-Path: <rja.lists@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 920B31B3068 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:58:03 -0800 (PST)
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 8FGpwNsAM9v9 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:58:01 -0800 (PST)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B71371B306A for <manet@ietf.org>; Tue, 24 Nov 2015 09:58:01 -0800 (PST)
Received: by qgeb1 with SMTP id b1so16039977qge.1 for <manet@ietf.org>; Tue, 24 Nov 2015 09:58:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1/C67E5l96TbPVbAAV8iKgZ3UtT8+aQBv0ilDRD8z/4=; b=D3JZwJrXNO37Ml0JYCss1CNgW60PLIIBP5WVfl8PZVa9qEmegRr7HPYTnacOiCn68n 9u8Q5eOoyec6fuyfb2GCWIK551/cB9rbGW74S4cn/p8fKQusjnjBqs627HOxiKas+fGy rBiqk0gXwBavgeW/kark/1ffX6bO8oolRKviQ/jUWqV9ujA/UlL8t20kmFTgMbCgn3eO 8QSzqaFrkSTmQS/Vt3vEtsjKRSI7RQFbRfpAX385S95FMkQwITeKAkY0WhnKxCp0vRNn l6vHKQLo+kiC9P+898rIZl4WYXyi/7lU8bUyfgjvBJLzt9niCdymtD1AB/iJdVaLoeFD eumw==
X-Received: by 10.140.109.247 with SMTP id l110mr34055621qgf.35.1448387880889;  Tue, 24 Nov 2015 09:58:00 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id c190sm4496118qkb.27.2015.11.24.09.58.00 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 09:58:00 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <CAGnRvuoeW8WV78Vp92G9QBmDnDvSSXPgjOK2e18kwUYdKUUBAQ@mail.gmail.com>
Date: Tue, 24 Nov 2015 12:57:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <02FEF0A4-B4F9-47DF-AE9C-8B33CC9136B7@gmail.com>
References: <3C8E8891-D798-49F8-8AF0-DD0A35BA476E@gmail.com> <CAGnRvuoeW8WV78Vp92G9QBmDnDvSSXPgjOK2e18kwUYdKUUBAQ@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/K7yFO2vi5AakO0nJ3fpJQig0DPY>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: "Use TLS" flag is not secure
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:58:03 -0000

> On 24  Nov 2015, at 10:31 , Henning Rogge <hrogge@gmail.com> wrote:
>=20
> On Tue, Nov 24, 2015 at 4:20 PM, RJ Atkinson <rja.lists@gmail.com> =
wrote:
>>=20
>> Section 10.2, page 38 (top) defines a =E2=80=9CUse TLS=E2=80=9D flag.
>>=20
>> This design creates a security problem.  The issue is commonly
>> known as a =E2=80=9Cdowngrade attack=E2=80=9D, because a =
man-in-the-middle
>> attacker (whether on-link or off-link) simply clears that bit
>> to (incorrectly) indicate that TLS is not required.
>=20
> The TLS bit is (I think) not about "use TLS" or "don't use TLS", its
> just the bit that tells you what to expect on the IP/port combination.
>=20
> If you clear the bit, the other side would try to connect to the TLS
> socket with a default TCP connection, which will fail.

Please edit the draft to say this =E2=80=94 possibly even use the words =
above.
That meaning is not clear right now.

>> I don=E2=80=99t see any way to fix this, but I am open-minded
>> if someone has a creative idea.
>>=20
>> The absolute bare minimum for IETF approval would be that this
>> (easily exploited) vulnerability be disclosed BOTH within
>> Section 10.2 AND also in the Security Considerations of Section 11.
>>=20
>> My guess is that the Security Area reviewer will say that this
>> is unacceptable protocol design.
>>=20
>> So I=E2=80=99d prefer (and recommend) that we drop this =E2=80=9CUse =
TLS=E2=80=9D flag.
>>=20
>> Maybe an alternate approach would be to create an informative
>> status code or signal (whichever) that a peer could send to
>> a would-be peer to indicate that non-TLS DLEP sessions are not
>> allowed.
>>=20
>> While that proposed message could be intercepted/dropped by
>> an adversary, it is purely a status message. A good DLEP
>> implementation would attempt a DLEP+TLS session with its
>> intended peer anytime a DLEP w/o TLS session failed, so
>> the loss of the proposed message doesn=E2=80=99t create a security
>> vulnerability.
>=20
> I don't think there is any way between two parties that don't know
> each other to establish a secure connection if BOTH of them support
> non-secure communication AND a Man in the Middle controls all traffic
> between the two parties.
>=20
> The MITM could just drop everything that is security-related from the
> communication.

That text seems to say the DLEP session would fail due to the described
DOS attack.  If that is the consensus answer, then please put the text=20=

above (or equivalent text discussing the TLS flag) into the DLEP
Security Considerations section. =20

Basically, the DLEP Security Considerations section ought to=20
at least document all known security vulnerabilities (not just off-link
vulnerabilities) and suggest remedies for the vulnerabilities.

Yours,

Ran


From nobody Tue Nov 24 09:59:15 2015
Return-Path: <rja.lists@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 6BD511B305D for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:59:14 -0800 (PST)
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 bceo3CUe1weH for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 09:59:13 -0800 (PST)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 178701B304F for <manet@ietf.org>; Tue, 24 Nov 2015 09:59:13 -0800 (PST)
Received: by qgec40 with SMTP id c40so15903469qge.2 for <manet@ietf.org>; Tue, 24 Nov 2015 09:59:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=EKPhVz/5kF48o9Ym8OzyQHTKw8DHUP5DFlgv1CSLsss=; b=L9gIcZzc7ENAXAFFngKAnW4A0am4Xk+TnOS3EdpAOUcfsdjOIPHmsfquphLi0KY5Zc LAe1JdbF1cwMz6t1J4Q/pHGRU5eammfrA+1HJK6R5EfxgbU3386HICqevPA+TAb9ENFy no6LdqijVkEO2npiwY35Ym0M1xgCrldpgDKG1OIzmX9rsgpDVMITGo8a9lxTgGKh9Q8n Ou8sl0thXRstlnny77623PEskJbNqWITxea3y+tRWquOZSUyuiFasjVMnCUpyKWRYeWw gBHbDF204gfvKFy7ye+SRr+2wu/5ifbA4cNFoK9B3FSIxzzmqFwlM2DgYnLEmcuAzmQE chtg==
X-Received: by 10.140.181.135 with SMTP id c129mr37141598qha.4.1448387952362;  Tue, 24 Nov 2015 09:59:12 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id 20sm4453896qhg.13.2015.11.24.09.59.11 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 09:59:12 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B04E7E@tss-server1.home.tropicalstormsoftware.com>
Date: Tue, 24 Nov 2015 12:59:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B99D05A-EFFB-49E9-B7C0-992B48C1E5E4@gmail.com>
References: <3C8E8891-D798-49F8-8AF0-DD0A35BA476E@gmail.com> <CAGnRvuoeW8WV78Vp92G9QBmDnDvSSXPgjOK2e18kwUYdKUUBAQ@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04E7E@tss-server1.home.tropicalstormsoftware.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/qTHAhkpuS9lYOfZ9VLStdAChUYA>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: "Use TLS" flag is not secure
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 17:59:14 -0000

> On 24  Nov 2015, at 11:04 , Rick Taylor =
<rick@tropicalstormsoftware.com> wrote:
>=20
> Hi Ran,
>=20
> Thanks for the on-going reviews.  I'll quickly comment on this one.
>=20
> Henning is right, the 'Use-TLS' flag means "TLS is expected when using=20=

> this connection point (address:port)".  Perhaps 'Expect-TLS' would be =
a=20
> better name for the flag?

It might be simpler and clearer to copy/paste Henning=92s text from his=20=

email (edit to taste) into the section that specifies that flag.

Ran


From nobody Tue Nov 24 10:03:37 2015
Return-Path: <rja.lists@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 04D7C1B3082 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:03:35 -0800 (PST)
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 c9H7SQ5qE3Ni for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:03:33 -0800 (PST)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79E301B307B for <manet@ietf.org>; Tue, 24 Nov 2015 10:03:33 -0800 (PST)
Received: by qgeb1 with SMTP id b1so16160984qge.1 for <manet@ietf.org>; Tue, 24 Nov 2015 10:03:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Qj4vXxMFGM+0+qmQFAcrwzxWyPIV4h7Trec0GW3ZmrI=; b=FEUOdGs6Gsprnd3rNnZDKD1haYwpqmAO62XIre4iLB37R1Fyo1OVUA9MOIl7jaVMk2 ZA5FVhmS5Jk6RS/EipKk3vsZ1MTCTpiEDzdmrMoN7mrFeV4H4dFL9wyDtfFCFtG6uI3D Lzc1syABN7PLchojzc6XRgtZKDa9pIH+h605UNN/kIYBbUmCnnuSr3TPMcDlPGGnPpHt rbEtmhEvJm3H7Rq5sI9/IOb092CYxSTq+2i4FsJf5xsaLYAtMdhngw//LdtTn5zOrkiO HTM8634dQWey6j4QVZB6Le3PHnOld2F3UaNOs7qKqfjfFAFwco71w27t8yAj5YKNcRBd EnGg==
X-Received: by 10.140.36.212 with SMTP id p78mr33794073qgp.13.1448388212681; Tue, 24 Nov 2015 10:03:32 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id m8sm4513864qki.3.2015.11.24.10.03.32 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:03:32 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B04EE5@tss-server1.home.tropicalstormsoftware.com>
Date: Tue, 24 Nov 2015 13:03:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <71ECF18E-E2A7-4308-8261-4A3E188270EB@gmail.com>
References: <447C1544-14DF-40C3-BA23-97F4F146A374@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04EE5@tss-server1.home.tropicalstormsoftware.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/bWKZy_VxkLB0prwR4_u26x-bJCY>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: error handling during "In-Session" state
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:03:35 -0000

> On 24  Nov 2015, at 11:10 , Rick Taylor =
<rick@tropicalstormsoftware.com> wrote:
>=20
> Thanks Ran,
>=20
> My current thoughts are to add a blanket statement to Section 5, =
saying=20
> something along the lines of "A TCP reset in any state causes an=20
> immediate transition to the relevant initial state, clearing any =
session=20
> information bases.=94

I am unclear what =93relevant initial state=94 above means.  Perhaps
say that when one receives a TCP Reset that (a) the current DLEP
session terminates and (b) the receiver should do X=20

[alternately: "(b) the receiver should listen on the DLEP port=20
as it would if the previous abruptly terminated DLEP session=20
had never existed=94]

I=92m not sure what you mean =93X" to be.  It could be do X or=20
to do nothing.  Please edit to make it clear somehow.

> I don't see the need for special handling for particular states, or =
any=20
> kind of 'gentle' restarting.

I=92m flexible about how to resolve this.

The key thing for me is to document the intended reaction,
so that a naive implementer has a good probability of
coding correctly.

Thanks,

Ran


From nobody Tue Nov 24 10:05:52 2015
Return-Path: <rja.lists@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 3AA0A1A0033 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:05:51 -0800 (PST)
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 HduylbzIjMdV for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:05:48 -0800 (PST)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D24A1A002A for <manet@ietf.org>; Tue, 24 Nov 2015 10:05:48 -0800 (PST)
Received: by qkao63 with SMTP id o63so7962072qka.2 for <manet@ietf.org>; Tue, 24 Nov 2015 10:05:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ntrho2zXa05tfeioiS5wzCZaWbCIyu8PNjLQf1/4K0w=; b=Fyv6tbsqhrFy9iO7fQ60A2Uuja3tzaPcCFyu3MhoAAZHxDqA9hwTF2cdXROXxt0PGo uXVzJSH7929je6pjtSYynCrD6wyapwzwrG7ebSe9tCjuWfri8L0BLnO/p9rYCDynobt1 gXIFP8MW3QalagpxaFm6TPcfZ4LXRvv6kh383qtOLfu9DBN1QWt9B9thLfrsNRij2NV9 og+6rJ6s11GyPQj3WBDlAUMf+OOMlcK4kZXphbAMh2rawJQgV6Q/SkHmJzdWKNVJhmaX o2BOjlqcSp7uPGUstz1CVq7K1ucm2SJL0VGjfgVlFXonCMZEtTSygxhpa/H3m9aYUeHl vobg==
X-Received: by 10.55.71.199 with SMTP id u190mr30339142qka.3.1448388347723; Tue, 24 Nov 2015 10:05:47 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id w75sm4509435qka.25.2015.11.24.10.05.47 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:05:47 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B04F12@tss-server1.home.tropicalstormsoftware.com>
Date: Tue, 24 Nov 2015 13:05:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <23B3A59F-4A50-454E-8A5E-F8C3C7FD0E62@gmail.com>
References: <4C2E2E59-68FB-45A8-A24F-4F8AC6E3D1EB@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04F12@tss-server1.home.tropicalstormsoftware.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/GuIeneeP2-Zz6uQMpnusP9z0dYo>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17:  well-known IPv4 link-local multicast 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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:05:51 -0000

> On 24  Nov 2015, at 11:12 , Rick Taylor =
<rick@tropicalstormsoftware.com> wrote:
>=20
> Ran,
>=20
> We resisted the urge to request one of the few remaining IPv4 =
multicast=20
> addresses, and went for the IPv4 broadcast address instead.  Discovery=20=

> is a single-hop process anyway.

Thanks for the clarification.


(OPINION)

A) I don=92t think that IPv4 link-local multicast addresses are =
particularly scarce.
   I checked that registry today before sending that note.

B) Use of broadcast seems impolite to other nodes on that link.  Modern
   IETF practice is to try to avoid using link-broadcast, in part =
because
   of widespread negative operational impacts of link-broadcast traffic.

Yours,

Ran



From nobody Tue Nov 24 10:08:58 2015
Return-Path: <rja.lists@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 7A2E81A0093 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:08:56 -0800 (PST)
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 DE5muNpbWfH8 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:08:55 -0800 (PST)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E1DD1A008B for <manet@ietf.org>; Tue, 24 Nov 2015 10:08:55 -0800 (PST)
Received: by qgec40 with SMTP id c40so16116212qge.2 for <manet@ietf.org>; Tue, 24 Nov 2015 10:08:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/cP89YBb4JrKg4TK4PWsWMFRKIhH1IEhi4olevZ3CFQ=; b=Dpvr2gcNJs8sw1OYc2RSqR89wS4eGQeVCaMZ54+4dGjhjgoVoJYq9ce2BQIb+qtoGT LXmPwki0cQ8UM1ovMvZE/uXWh3oVOr4ra2iCtRdxsNQehxyaRwMnykVsIbfEmG6YS9Iu 4MclgVhNof212NEwCXp1Z0cYsqCuIKOXpOACiu+4xnHzsOzNo/HdbcF7x1zzWq7ivL8w FESvY8Z0NvYf6Q4U0iSHZj/W74rPnjIcD5B5WFnfm0FY1Y7/95COR6XD1YvGJgZX8jcR VmSNEqHpKVLPP2Vi5EDPCBORuDH9aHAmenzo0BZ7/w5G1UtJuKwHr6DigbmEpHf6Xw2O rksg==
X-Received: by 10.140.94.201 with SMTP id g67mr34956881qge.43.1448388534346; Tue, 24 Nov 2015 10:08:54 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id w75sm4512305qka.25.2015.11.24.10.08.53 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:08:54 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <CALtoyonJV6bim0Yz-dXp_v1ENkp27W=b1pLsywaT1a9PGodAsg@mail.gmail.com>
Date: Tue, 24 Nov 2015 13:08:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <72B1DE6F-9C9A-4075-BE26-37F81A41BCAC@gmail.com>
References: <57909BAD-55EB-4AE7-913F-745166306D4A@gmail.com> <CALtoyonJV6bim0Yz-dXp_v1ENkp27W=b1pLsywaT1a9PGodAsg@mail.gmail.com>
To: Stan Ratliff <ratliffstan@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/y0Shp5BkdW0KQHx5eQZDHxT-axk>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Assumptions
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:08:56 -0000

> On 24  Nov 2015, at 11:26 , Stan Ratliff <ratliffstan@gmail.com> =
wrote:
>=20
> Ran,=20
>=20
> Please note that this specification covers *only* the local connection =
between a router
> and it's attached radio - the spec does not intend to imply that the =
radio must support IPv6 OTA.=20

I certainly know of radios, deployed in the thousands, that might get
updated to support DLEP but have NO CHANCE of ever getting IPv6 support,
(not even IPv6 Link-local on a wired/optical Ethernet interface).

Hence my concern.

> That said, I don't believe there's any hard-and-fast mandate to use =
IPv6,
> just a recommendation that it be used. As Rick mentioned in an earlier =
email,
> the IPv4 broadcast address can be used for discovery, and there is no =
restriction
> that I'm aware of on the P2P session.=20

I sent a separate response to Rick=E2=80=99s reply, but I really think =
it ought
to avoid using IPv4 link-broadcast.  We have literally decades of =
negative
operational experience with IPv4 link-broadcast, and IPv4 link-local =
multicast
works very well (much more favorable operational experience than =
broadcast).

Thanks,

Ran


From nobody Tue Nov 24 10:09:41 2015
Return-Path: <rja.lists@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 EF1D71A00A5 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:09:39 -0800 (PST)
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 MNDZuI36X1ob for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:09:38 -0800 (PST)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59E211A009C for <manet@ietf.org>; Tue, 24 Nov 2015 10:09:38 -0800 (PST)
Received: by qgec40 with SMTP id c40so16131446qge.2 for <manet@ietf.org>; Tue, 24 Nov 2015 10:09:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=S/TahH8czfpgRamH0e5BxuE4dp4Y2VzwWR+uxkBAwNQ=; b=mf7+x4lxoU3RTMgocJvF1hFAPA6tTr6W0ROEubyyw8HPHgJugPI7TZw/VBWN52cJ4M Sl9EbhLP6b5osLfk6vSwTTSOLPhhNxk8wHXRKZBCczsGOwNgw/cBf8QRmAvM76ZYxSVu epFN3fPw/BKB/trTUeihsvfz+J/PisyY7JVTe+WTqnjSiL/4hBP6nz5d8xUfXAR9bCQ9 kmhZ88N6+Uk+lSy8QXsDSWhBS7v3Ok7GIqgbf9ZhwBjZItg8z5f9HdC2AaPB25xAJVFa oQ4LYchOTqVFjbnS470X7l4niVqkugfZgMDRvtV+FQEGZGblEP6NhVTjYv1aKF4vFqx2 VymQ==
X-Received: by 10.140.174.68 with SMTP id u65mr37271686qhu.62.1448388577654; Tue, 24 Nov 2015 10:09:37 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id w75sm4512305qka.25.2015.11.24.10.09.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:09:37 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <CAGnRvurvHDFv=TFrRNZYf64Tt8BOXc0JFzJX2MPZguHB61=4CQ@mail.gmail.com>
Date: Tue, 24 Nov 2015 13:09:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <21BFF2D0-BB1C-41FA-A10D-6576E347EDF4@gmail.com>
References: <447C1544-14DF-40C3-BA23-97F4F146A374@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04EE5@tss-server1.home.tropicalstormsoftware.com> <CAGnRvurvHDFv=TFrRNZYf64Tt8BOXc0JFzJX2MPZguHB61=4CQ@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/F-aOGaU4B7qdjeiAqbJYucrgW-8>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: error handling during "In-Session" state
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:09:40 -0000

> On 24  Nov 2015, at 11:27 , Henning Rogge <hrogge@gmail.com> wrote:
>=20
> On Tue, Nov 24, 2015 at 5:10 PM, Rick Taylor
> <rick@tropicalstormsoftware.com> wrote:
>> Thanks Ran,
>>=20
>> My current thoughts are to add a blanket statement to Section 5, =
saying
>> something along the lines of "A TCP reset in any state causes an
>> immediate transition to the relevant initial state, clearing any =
session
>> information bases."
>>=20
>> I don't see the need for special handling for particular states, or =
any
>> kind of 'gentle' restarting.
>=20
> As far as I read the draft the "reset" is a termination both of the
> TCP session and the protocol data associated with the session.
>=20
> You tear everything down and start a completely new connection.

If that=E2=80=99s the answer, please say so explicitly.  Right now the
I-D is not so crystal clear.

Thanks,

Ran


From nobody Tue Nov 24 10:21:58 2015
Return-Path: <rja.lists@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 C638E1A0856 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:21:55 -0800 (PST)
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 aFe0gkYk79Px for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:21:54 -0800 (PST)
Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AFBD1A1A1C for <manet@ietf.org>; Tue, 24 Nov 2015 10:21:54 -0800 (PST)
Received: by qgea14 with SMTP id a14so16406865qge.0 for <manet@ietf.org>; Tue, 24 Nov 2015 10:21:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=aS0NXjmK0/51wCtZkH6c6bmYT2jt0PjDi6LuDASPR9s=; b=gwpzGjJ8NoqFQYWPz7PwRxMzZow2GepUIvrmCg1Z0pEHaVT6rD0jg9La2sQsLrVlG2 7D4v7phxYOuOoTH5a9P4/DYGtmKBPad7ovzeB5rSnyxcrKf/Smq3bfLmTYEmkq4FS7MQ 3FsKCFKDUsz0FrKmo4jRryGOOg1I79BtY7pIgi+V6DvyeV4kvDPcabbA/SBxPIWIg1cc V6Ay5/oMxpVnHWg9i5QktbcPjcXwayoI+6SlswWWQGEosbBKMtPA86QKhVQBlGsiJ58T 5IQfSkRltJMaRU/vniResgCNo/0pOKpmfuujNK1t/C2YaXeBVyJOGn4ExgUt+Z46xQVN aBGA==
X-Received: by 10.140.175.65 with SMTP id v62mr36607542qhv.75.1448389313302; Tue, 24 Nov 2015 10:21:53 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id m23sm4541490qkh.46.2015.11.24.10.21.52 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:21:52 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B0500C@tss-server1.home.tropicalstormsoftware.com>
Date: Tue, 24 Nov 2015 13:21:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <18E52109-97E3-47D7-A474-F708D20AD677@gmail.com>
References: <57909BAD-55EB-4AE7-913F-745166306D4A@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B0500C@tss-server1.home.tropicalstormsoftware.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/w749DOO3QN_KGZtajz04MOao1eY>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Assumptions
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:21:55 -0000

> On 24  Nov 2015, at 11:28 , Rick Taylor =
<rick@tropicalstormsoftware.com> wrote:
>=20
> Ran,
>=20
> I was working under the assumption (and yes, I know it is an =
assumption)=20
> that in 2015 the IETF would mandate IPv6, and not let us get away with=20=

> an either/or approach.

I don=E2=80=99t think that is a valid assumption.

The IETF generally mandates that IPv6 support must be specified,
but generally also still supports IPv4 in IETF specifications.

As a concrete example, OSPFv3 can carry both IPv6 and IPv4 prefixes,
yet IETF OSPF WG is adding =E2=80=9Csegment routing extensions=E2=80=9D =
to OSPFv2=20
(and OSPFv2 ONLY supports IPv4 prefixes and ONLY runs over IPv4).
Separately, there is also OSPF WG draft on how to frame OSPFv3 over =
IPv4,
primarily as an IPv6-transition aid.

> I totally understand the difficulties of IPv6 and legacy equipment,
> but DLEP must mandate 1 method of discovery, and I can't see the IESG=20=

> letting us mandate IPv4.

What DLEP **can** do (and SHOULD do) is specify both how DLEP works=20
in an IPv6 environment =E2=80=94 and also how DLEP works in an IPv4 =
environment. =20

> If, however, someone has an approach that allows IPv4 only, and will =
get=20
> through the IETF processes, then I would love to hear it.

I am NOT saying that DLEP should be IPv4-only.  I am saying that
there definitely exists legacy IPv4-only equipment that might=20
support DLEP in the future, but is extremely unlikely ever to support=20
IPv6.

Assertions:
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94
DLEP routers want to be able to communicate with any DLEP modem.
If a radio only supports IPv4, it can=E2=80=99t hear an IPv6 anything.
If a radio only supports IPv6, it can=E2=80=99t hear an IPv4 anything.
If a radio supports both IPv4 & IPv6, it will hear both IPv4 & IPv6.

For example, this means that one tailors the recommendation to
the operational deployment:
	- in a dual-stack operational deployment, the RECOMMENDATION=20
          is to send DLEP Discovery messages twice, once with IPv4=20
          link-local multicast AND again with IPv6 link-local multicast
	- in an IPv6-only operational deployment, the RECOMMENDATION
          is to send DLEP Discovery messages only using IPv6 link-local=20=

          multicast.
	- in an IPv4-only operational deployment, the RECOMMENDATION
          is to send DLEP Discovery messages using IPv4 link-local =
multicast.

Yours,

Ran


From nobody Tue Nov 24 10:29:16 2015
Return-Path: <rja.lists@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 5FE801A1B27 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:29:15 -0800 (PST)
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 WaBqo9ENZAMh for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:29:13 -0800 (PST)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9116C1A009C for <manet@ietf.org>; Tue, 24 Nov 2015 10:29:13 -0800 (PST)
Received: by qkas77 with SMTP id s77so8314464qka.0 for <manet@ietf.org>; Tue, 24 Nov 2015 10:29:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hPxeyAcCtep5Zx/0Zt0yVgH9fOU9DtBqVPGQ2LF6WhI=; b=khUtXZ7FwrjTm59WdI2NH+yifhpVBhqOz7aVE5FD/10u4PbOuJ/RzaVdGvbl3lbF3i oraorbk1arMnYWL2MTNvHAp64Vkt/BKIDhi/5EFQcQ6YphUAscVwRbYMYVEC5Wnwprpa ze9eeWey86382+Geh4azeFjH1kPBjpyyx+Zaz8w2FliicEIauH2oBdZgsH3ULntqtT90 VwHrz3dosvuH2fVc3aC4i3IXbC9JPy87oRmcb2I9BoMIOU2Qrq2Ac8R2gWkiO+6bdTH+ kTVnbZ7x6soSPguGgKF08XAakMMTf6kMSaGd7WHNi60Oea5ZtAP0xk2ycPwAhm+0qDGX /MgQ==
X-Received: by 10.55.75.87 with SMTP id y84mr34367172qka.56.1448389752690; Tue, 24 Nov 2015 10:29:12 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id d4sm4483531qga.39.2015.11.24.10.29.12 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:29:12 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <CAGnRvuqAf8b+cmdpTnJWuWcJ_Xnft8WyjOB7-cN7rpgzXCCT=w@mail.gmail.com>
Date: Tue, 24 Nov 2015 13:29:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FEE2BD6-C9EA-4840-A870-5E30361DEC03@gmail.com>
References: <8C867205-4F66-4026-AEA7-471B66D00FC9@gmail.com> <CAGnRvuqAf8b+cmdpTnJWuWcJ_Xnft8WyjOB7-cN7rpgzXCCT=w@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/SzntE4NEWShkrdBqUu8uJ1VO8qw>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Section 5.1, security concern
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:29:15 -0000

> On 24  Nov 2015, at 11:39 , Henning Rogge <hrogge@gmail.com> wrote:
>=20
> On Tue, Nov 24, 2015 at 5:24 PM, RJ Atkinson <rja.lists@gmail.com> =
wrote:
>>=20
>> In Section 5.1, top of page 13, this sentence exists:
>>        The modem MUST accept a TCP connection on only one (1)
>>        address/port combination per session.
>=20
> "per session"...
>=20
> so its more a matter if "multiple sessions on the same radio" makes
> sense. If the radio only implements "pushing metrics to the router" it
> could easily handle multiple sessions. If you want to do "request link
> characteristics or even flow control", only a single session makes
> sense.

If that is the consensus, then please edit the draft to capture
the thought above.

>> A quick reading of this yields confusion.
>>=20
>> On the surface, it appears to say that the modem can ONLY have
>> 1 peer at a time.  If correct, then an off-link attacker could
>> deny service to a legitimate router by opening a DLEP session
>> with the modem (while pretending to be a legitimate router).
>=20
> off-link would mean TLS... because linklocal IP traffic is not
> forwarded between the off-link attacker and the DLEP instance.

TLS doesn=E2=80=99t prevent a DOS attack such as this.  Also, TLS *use*
for off-link sessions is an operational decision by the network
operator (at least at present).  If folks want to require that
TLS be *used* for any off-link DLEP session, I=E2=80=99m ok with that,
but that isn=E2=80=99t what the current draft seems to say.

>> If the paragraph above is a correct description, then this
>> security vulnerability needs to be clearly disclosed in the
>> Security Considerations section of this I-D.  One imagines
>> that using TLS with both client-certificate and server-certificate
>> for endpoint identity authentication would be a RECOMMENDATION
>> for situations where the threat environment included either
>> off-link or on-link attackers.
>=20
> If you have an on-link attacker you have lost anyways... because the
> attacker already controls the data-plane.

Maybe, but maybe not.  It depends on what =E2=80=9Con-link=E2=80=9D =
really means.

In a big yellow coaxial cable Ethernet, an on-link attacker could
jam all traffic.  Where the on-link attacker is connected to the
victim via an Ethernet switch, then there are various limitations
in what such an attacker could do.  Some of those limitations
vary with 802.1x, MACsec, and switch implementation-specific=20
features (e.g. MAC address filtering/lockdown).

> Unless you use something like 802.1x, which would keep the link safe
> (both data and control plane).

I=E2=80=99d suggest also using MACsec or similar link encryption.
RFCs can suggest using 802.1x as a mitigation, by the way.

> I still stand with my suggesting making linklocal IPs mandatory for
> DLEP and drop all the TLS stuff... if someone wants to deploy a
> layer-2 VPN, he/she can also deal with the necessary security for the
> VPN.

I=E2=80=99m ok with that, but its a change from the current =
specification,
and there still would need to be discussion of the new threats
that using an L2 VPN would bring.  It is possible that the IETF
Security Area would consider that sufficient, but I=E2=80=99m not =
certain.

IPv4 unicast link-local addressing does exist already, by the way.

Yours,

Ran


From nobody Tue Nov 24 10:37:56 2015
Return-Path: <rja.lists@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 6894B1A86DD for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:37:53 -0800 (PST)
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 bf8YDmCeKIcJ for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:37:51 -0800 (PST)
Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3EA01A8034 for <manet@ietf.org>; Tue, 24 Nov 2015 10:37:51 -0800 (PST)
Received: by qgeb1 with SMTP id b1so16886442qge.1 for <manet@ietf.org>; Tue, 24 Nov 2015 10:37:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JkXYjQeuYItW82jod3/VDxfzKH+CBC9sh2GukRiGnFs=; b=shFmLtTn5tMV+nHjKuy9uqvbINCD00okJTlt9uLqCdjNRZ+yr5ayT3/gMxahQnZREM MYUdTvbM2bIBt6PWYjuap3JmX6ERcRnJ0E+PBINONxRiEbtub4HM1sQZVnLrbv93h73c F26M+cf8W81Gf44jW49Hi3LxQlvxv6WqyU6VIM81TRYIBGmf+vc1/BxjCpF0qGgfZB/Y EpyjRd9I2w2BtaQdCc9FT+0Lc+5MlitCCHh9rUJX6RzYfHD7Ty/TvLLeQSZzuzzXTof+ KzrT3gIQI60f4VSoWw1ST3uoxa0o7tFc43XkoGs1VvLdXdEZMTdg+0XMbbSyyUHoKvKR ifHQ==
X-Received: by 10.140.96.45 with SMTP id j42mr34521428qge.92.1448390270930; Tue, 24 Nov 2015 10:37:50 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id v187sm4542697qka.9.2015.11.24.10.37.50 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:37:50 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com>
Date: Tue, 24 Nov 2015 13:37:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5CFA0FC-B2B4-44E0-9E0D-355E218E2102@gmail.com>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/PkfBHIIcBA1Ew3Ka-Jk0w8Ao4EI>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:37:53 -0000

> On 24  Nov 2015, at 12:18 , Rick Taylor =
<rick@tropicalstormsoftware.com> wrote:
>=20
> Ran,
>=20
> I really like your proposed changes to the Security Considerations, =
but=20
> I do have a concern.  Many major radio manufacturers consider TLS a =
step=20
> too far, and mandating it for environments where it is considered=20
> unnecessary will prevent uptake of DLEP.

If radio manufacturers are like some router vendors, they will claim=20
the DLEP RFC whether or not they implement TLS.  This is NOT good,=20
but the situation is not new to the IETF.

> I think we are all agreed that when there are multiple hops between=20
> modem and router then TLS is a MUST.  But when there is a single piece=20=

> of wire between the devices, people will (possibly correctly) argue =
that=20
> it is pointless.

It depends on whether one thinks that on-link attackers exist,
and whether one has various other tools (e.g. 802.1x, 802.1AE,
switch-specific features) to manage/limit such attacks.

> Do you have any advice on how we could add some text to your=20
> recommendation along the lines of:
>=20
> "If you can prevent DLEP running over multiple hops in your=20
> implementation, then you MAY choose not to implement TLS."
>=20
> How one prevents multi-hop is left as an exercise to the reader...
>=20
> This is an open question to the WG as well.

We discussed this last summer and I proposed that alternative to TLS=20
back then.  It did not seem to be accepted by the WG back then,=20
but maybe the mood has shifted in the mean time.

The obvious way to eliminate multi-hop is to add mandatory text
for implementers.  Here is some candidate text (one will need
multiple MUST and MUST NOT statements to nail the multi-hop
box shut):

	- DLEP implementations MUST NOT support routable IP addressing
          on DLEP-capable interfaces.
	- DLEP implementations that support IPv4 MUST ALSO support
          use of IPv4 link-local unicast for DLEP-capable interfaces
          and IPv4 link-local multicast for DLEP Discovery messages
	- DLEP implementations that support IPv6 MUST ALSO support
	  the use of IPv6 link-local unicast for for DLEP-capable
          interfaces and IPv6 link-local multicast for DLEP Discovery
          messages.
	- DLEP routers MUST NOT forward packets with link-local =
addressing
          between interfaces within that router.

Cheers,

Ran




From nobody Tue Nov 24 10:38:49 2015
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 CB7E31A8745 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:38:48 -0800 (PST)
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 g1E3yTglLtfx for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:38:47 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49AC71A86F0 for <manet@ietf.org>; Tue, 24 Nov 2015 10:38:47 -0800 (PST)
Received: by wmww144 with SMTP id w144so38732454wmw.0 for <manet@ietf.org>; Tue, 24 Nov 2015 10:38:45 -0800 (PST)
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=NicldkbrdrQ4ZoWiWCK2/LatKhVN50WAlC/RmbNWW3A=; b=VpfSUJ720VVN+YY9I9g2qOj8f8R9NSBVpIHlZGNXPh8Hlde7az/7btw5efUQViFrrx 11yNsN3v+Q4xm9aPKonwWTKTzCQu9VTnxBya/S8zyodeAfEsD/GnyEeVrryPWx4sSJme fcy5m8JqMDZKBLKCr9WZGRVsiTdgidTXIyfPXu+ocYlBiJkGALRUbLokmLVktDCvxXVV C5BI94da0+c4dqnysrAmuBvqApGxNOsiV6uGfDaJKPluLnySVz96BqHeIQkDoXgFQ+Jw jD77nFLhL2GGFJtx9nts/cQE1SKuAM1sOrHfs09+NzwnSXghaEyhXycevElwkuyTIwcl Siqw==
X-Received: by 10.194.2.193 with SMTP id 1mr33339856wjw.26.1448390325844; Tue, 24 Nov 2015 10:38:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Tue, 24 Nov 2015 10:38:16 -0800 (PST)
In-Reply-To: <7FEE2BD6-C9EA-4840-A870-5E30361DEC03@gmail.com>
References: <8C867205-4F66-4026-AEA7-471B66D00FC9@gmail.com> <CAGnRvuqAf8b+cmdpTnJWuWcJ_Xnft8WyjOB7-cN7rpgzXCCT=w@mail.gmail.com> <7FEE2BD6-C9EA-4840-A870-5E30361DEC03@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 24 Nov 2015 19:38:16 +0100
Message-ID: <CAGnRvup-a9GkDBH=RfgBMu=JRi=FuS6bMWeT3hyU43kVLGVbfw@mail.gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/PT-ErOHJtsUCqt0gI3JySk00vs8>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Section 5.1, security concern
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:38:49 -0000

On Tue, Nov 24, 2015 at 7:29 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
>> Unless you use something like 802.1x, which would keep the link safe
>> (both data and control plane).
>
> I=E2=80=99d suggest also using MACsec or similar link encryption.
> RFCs can suggest using 802.1x as a mitigation, by the way.

either ways the problem to secure a single link has already been
worked on in a generic way.

if your deployment is a dedicated ethernet card on the Router
connected with a cable direct to the router you could skip all
security.

if you do it with a manageable switch, you can deploy VLAN, 802.1x
and/or MACsec... depending on your switch and security needs.

>> I still stand with my suggesting making linklocal IPs mandatory for
>> DLEP and drop all the TLS stuff... if someone wants to deploy a
>> layer-2 VPN, he/she can also deal with the necessary security for the
>> VPN.
>
> I=E2=80=99m ok with that, but its a change from the current specification=
,
> and there still would need to be discussion of the new threats
> that using an L2 VPN would bring.  It is possible that the IETF
> Security Area would consider that sufficient, but I=E2=80=99m not certain=
.

Again, the advantage would be that a lot of security issues of a L2
VPN have already been talked about in other WGs... it would make it
unnecessary to re-invent the wheel for DLEP.

Henning Rogge


From nobody Tue Nov 24 10:42:19 2015
Return-Path: <rja.lists@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 9A60E1A8781 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:42:18 -0800 (PST)
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 yNhP4PHBWQoP for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:42:17 -0800 (PST)
Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3899B1A877A for <manet@ietf.org>; Tue, 24 Nov 2015 10:42:17 -0800 (PST)
Received: by qkdt187 with SMTP id t187so915686qkd.0 for <manet@ietf.org>; Tue, 24 Nov 2015 10:42:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ctee14RWievo5vf4t4qVbQnWxXVB1Q7y7KXzovdgDXE=; b=z7EjAbDrA4idr+9JFt2sMTM4usdtjRJkKkOf11rpAKlH8qCcfnyG2a6dlUz+d54CBy WglvZQmDnV+c66la/eb7gdwfxJsDLe8oHJdDthea8nbJJt4+OhjyxZJs+Qn0tl28Yqrd /nCLS37eD/a1drenSwuXMcR+B6UWWQV+Jad4gqKUDukTg4nPiFh0gpHR2DCOMilqMbSB cUm8SM3R+8DM+oyjA2ODAAsjuOvelKtML5kDMbQN2fvOaIPFTqTy0NM5pCPen9iGTxwb z8RnSf/JdE8B+Vy2VVXuvDdUlLs3ZvNlk+VQOS5sc6PFRL4z/e/2Epc0quZ+SyRrR0KY aeeQ==
X-Received: by 10.55.81.3 with SMTP id f3mr23559750qkb.35.1448390536362; Tue, 24 Nov 2015 10:42:16 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id z65sm4469745qhb.22.2015.11.24.10.42.15 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:42:16 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B0540F@tss-server1.home.tropicalstormsoftware.com>
Date: Tue, 24 Nov 2015 13:42:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F751B619-CC51-4767-A554-EAC0032C6C45@gmail.com>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B0540F@tss-server1.home.tropicalstormsoftware.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/QMsOQeEp8EKUWlGy_Q76vVtHfAY>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:42:18 -0000

> On 24  Nov 2015, at 12:32 , Rick Taylor =
<rick@tropicalstormsoftware.com> wrote:
>=20
> On 24/11/15 17:19, Rick Taylor wrote:
>>> When the modem and router are NOT both on the same layer-2
>>> link (e.g. IP subnetwork, Ethernet VLAN) then session messages
>>> could be altered by an off-link attacker in order to subvert the
>>> behavior of either or both DLEP participants.  In short,
>>> a man-in-the-middle attack by an off-link attacker is possible.
>>> In these situations, deployment and use of TLS with DLEP is
>>> RECOMMENDED.
>=20
> We assume layer-2 transparency for the data plane already with DLEP=20
> (Section 2, para 2).  If we assume the same layer-2 connectivity for =
the=20
> control plane, can't we remove the TLS requirement altogether?
>=20
> You go on to recommend Layer-2 VPNs requiring some kind of external=20
> security, so I'm starting to wonder if TLS is a red herring.

Security is annoying.  A chain is only as strong as its weakest link.

TLS is not a red herring, because the operational experience is
that off-link attackers are widespread and commonplace. =20

By contrast, many Ethernet-centric environments use a range of tools=20
(e.g. 802.1x, mac address lockdown in switches, others) to keep=20
unauthorized nodes from successfully connecting to a =
wired/cabled/optical
Ethernet link.

Any L2 VPN breaks many of the tools described in the paragraph just
above, which is why it is a separate case worth describing.

My sense is that you might be happiest with specifying DLEP
to ONLY support link-local addressing (for both IPv4 & IPv6).

I=E2=80=99m not sure what the WG overall thinks.

Yours,

Ran


From nobody Tue Nov 24 10:47:23 2015
Return-Path: <rja.lists@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 A0AF51A879C for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:47:20 -0800 (PST)
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 mMgeIuYVTF-N for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:47:19 -0800 (PST)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECA6B1A8799 for <manet@ietf.org>; Tue, 24 Nov 2015 10:47:18 -0800 (PST)
Received: by qgcc31 with SMTP id c31so16857454qgc.3 for <manet@ietf.org>; Tue, 24 Nov 2015 10:47:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9o9u6TB+wnab3GjdPaEuiKtCKaWZ+FokG1+aVsemcMg=; b=ov66y2YFoKgrsUKM6ZbhbFUAz6aC7hcLLebTv+WnGy8AqO5Lx151H5LaEccYs5i3+P jQ43mKMIRBlOZJVBkEceU7VBvUSOfpI+6CLtmSq39cdwI+7C18hmrUQ4ggAaryI2gAVc R8A/xg4uo/jaSoRZBsnyZF3gj1Zacrm1XYoT1nGfwOr34QjGcFpICIFr7waYrVMrnlmI v8Bw/3Be6j+kVvfBlP88AbLwBQ1mi52frOCGZlmr6mF303N4/H58mVm+PZn+kt7dWvIx ruvbYOnynLTOXeIkt04NxtTklPvrz9iW/6IrbeAqSUUJxjbH9lZCLWds+JvYln9UpTVG DD0A==
X-Received: by 10.140.16.21 with SMTP id 21mr34830861qga.87.1448390838172; Tue, 24 Nov 2015 10:47:18 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id 2sm4521259qgi.42.2015.11.24.10.47.17 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:47:17 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58B6@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
Date: Tue, 24 Nov 2015 13:47:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FC7C1F2-5F6B-4110-8B9D-1B54B655890C@gmail.com>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <17688_1448385550_56549C0E_17688_6973_1_38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com> <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58B6@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
To: "MATTY, Steven" <steven.matty@airbus.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/e_Kz6n9gy0f3gXKHrQNgGSxkGLM>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:47:20 -0000

> On 24  Nov 2015, at 12:39 , MATTY, Steven <steven.matty@airbus.com> =
wrote:
>=20
> Hi Rick et al
>=20
> Is this a confusion between the terms "implement" and =
"use"/"deploy?=E2=80=9D. =20
> I think Ran is saying that all DLEP solutions MUST implement TLS =
support
> but it is not mandatory to "use" TLS (this is something best left to =
the end user
> to decide whether to enable TLS when deploying)
>=20
> For a DLEP router or DLEP radio to claim conformance to the DLEP =
standard
> it MUST provide an implementation which allows the user to enable TLS.
> It just doesn't HAVE to be enabled.

s/enabled/enabled by default/

That is, use of TLS can be a user-configurable thing with any default=20
setting that the implementer chooses to pick.

> Regards
>=20
> Steve

Yes, that is exactly what I was trying to say (with the s// edit above).

Further, OpenSSL is freeware and has TLS code inside.  It also has a =
very
reasonable memory footprint.  So for a radio vendor to say TLS is too =
hard=20
to implement seems a bit silly.  All they need to do is port a bit of =
no-cost=20
open-source code into their radio. If their radio has SNMP, it probably
used the open-source NetSNMP code for that =E2=80=94 so porting =
open-source isn=E2=80=99t
a new concept to radio vendors.  (Further, for vendors in a governmental
environment, some OpenSSL versions have NIST FIPS-140 approval already.)

Thanks,

Ran




From nobody Tue Nov 24 10:48:54 2015
Return-Path: <sratliff@idirect.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 8CA461A21A0 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 LCEXWy4PikNV for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:48:50 -0800 (PST)
Received: from smtp1.idirect.net (smtp1.idirect.net [198.180.159.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B22801A8784 for <manet@ietf.org>; Tue, 24 Nov 2015 10:48:50 -0800 (PST)
IronPort-PHdr: 9a23:g6Um4hdC0P/IQlnD83EiCwTjlGMj4u6mDksu8pMizoh2WeGdxc+4Yh7h7PlgxGXEQZ/co6odzbGG7ua/Bydbv96oizMrTt9lb1c9k8IYnggtUoauKHbQC7rUVRE8B9lIT1R//nu2YgB/Ecf6YEDO8DXptWZBUiv2OQc9HOnpAIma153xjLDvvcKNKF4WzBOGIppMbzyO5T3LsccXhYYwYo0Q8TDu5kVyRuJN2GlzLkiSlRuvru25/Zpk7jgC86l5r50IeezAcq85Vb1VCig9eyBwvZWz9EqLcQza3FlUe3kVkxxTBA6NuAv4V9H1szDmrcJy3SCbOYv9SrViHXyY7qxoACPhmSMALXZt6mDcieRslqVDoRmoowdjxJTRe4abKOV3ZK6bdtQfEzlvRMFUAmZ7C5+4boUBS6I6Ie9eq4Ts7RNatgG3GQ2tCu3HyzNJnHL9wes83vh3QlKO5xApA99b6Cecl97yLqpHFLntlKQ=
X-IronPort-AV: E=Sophos;i="5.20,339,1444708800";  d="scan'208";a="755206"
X-IPAS-Result: A2DKAQBzsFRW/8n6+gpeGQEBAQEPAQEBAYRTvByCGgENgWWGBQoCgXsUAQEBAQEBAQGBCYItggcBAQEBAgE6PxACAQg2EDIlAgQBDQ2IHg2+SQEBAQEBAQEDAQEBAQEBAQEbhlaEfIk5BZZQAY0pnFIfAQGERoUWgQcBAQE
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: RJ Atkinson <rja.lists@gmail.com>, Rick Taylor <rick@tropicalstormsoftware.com>
Thread-Topic: [manet] DLEP-17: Security Considerations
Thread-Index: AQHRJshlrevIZHt8zk2sZ2u9y3aVYJ6r1K8A//+uoHA=
Date: Tue, 24 Nov 2015 18:48:48 +0000
Message-ID: <baf8b4987dc044389259136829f47f70@VAUSDITCHM2.idirect.net>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com> <D5CFA0FC-B2B4-44E0-9E0D-355E218E2102@gmail.com>
In-Reply-To: <D5CFA0FC-B2B4-44E0-9E0D-355E218E2102@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/_pUHwbw2NWXyRVpHLAxY738k9fg>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:48:52 -0000

> =

> If radio manufacturers are like some router vendors, they will claim the =
DLEP
> RFC whether or not they implement TLS.  This is NOT good, but the situati=
on
> is not new to the IETF.
> =


It's a sad state of affairs when the IETF is putting text into specificatio=
ns that we know people will ignore (and in some cases, we'll *tell them* to=
 ignore), but I guess that's a discussion for another thread. =


Stan


_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________


From nobody Tue Nov 24 10:50:45 2015
Return-Path: <sratliff@idirect.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 204991A87AF for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:50:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 tOE2N9OG7Okn for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:50:40 -0800 (PST)
Received: from smtp1.idirect.net (smtp1.idirect.net [198.180.159.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CAD71A87B9 for <manet@ietf.org>; Tue, 24 Nov 2015 10:50:38 -0800 (PST)
IronPort-PHdr: 9a23:rA+yxxbKQ21ElL5HKsCv7p7/LSx+4OfEezUN459isYplN5qZpM65bnLW6fgltlLVR4KTs6sC0LqL9f++Ejdeqb+681k8M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aJBzzOEJPK/jvHcaK1oLsh730pMOYOFsArQH+SI0xBS3+lR/WuMgSjNkqAYcK4TyNnEF1ff9Lz3hjP1OZkkW0zM6x+Jl+73YY4Kp5pIZoGJ/3dKUgTLFeEC9ucyVsvJWq5lH/Sl61xDM1TmYXlAFPBUCR9hPzGJPwqTfhnuV40Siee8bxSOZwEX6HxptXeVugszsKKTM/uimDkdB9kq9d5heouwBu64fVeouIL7x1eaaLLv0AQm8UFPxYSyhADI34J7ATBuwFMPcS593mvVISqRqwCyGtCOL1xzRUwHn7wftpgKwaDQja0Vl4TJo1u3POoYCwbf9KXA==
X-IronPort-AV: E=Sophos;i="5.20,339,1444708800";  d="scan'208";a="755236"
X-IPAS-Result: A2CkBABzsFRW/8n6+gpeGQEBAg8BAQEBhFO8HIQNhg8CHIFjEAEBAQEBAQEBgQmCLYIHAQEBAQIBIxFFEAIBCBoCJgICAjAVEAIEDg2IHg2uH5AqAQEBAQEBAQMBAQEBAQEBAQEagQGFVYR8h3WBRAWWUAGNKZxSOIQvhRaBBwEBAQ
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: RJ Atkinson <rja.lists@gmail.com>, "MATTY, Steven" <steven.matty@airbus.com>
Thread-Topic: [manet] DLEP-17: Security Considerations
Thread-Index: AQHRJshlrevIZHt8zk2sZ2u9y3aVYJ6rb1nAgABn+QD//6zIIA==
Date: Tue, 24 Nov 2015 18:50:36 +0000
Message-ID: <6b6423e6db0e42e5bcc58ec966730d8e@VAUSDITCHM2.idirect.net>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <17688_1448385550_56549C0E_17688_6973_1_38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com> <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58B6@AUK52982.UKN.UKNROOT.ASTRIUM.CORP> <7FC7C1F2-5F6B-4110-8B9D-1B54B655890C@gmail.com>
In-Reply-To: <7FC7C1F2-5F6B-4110-8B9D-1B54B655890C@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/vby-YfWJTnlFGzq-g1IUyZEq2t4>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:50:42 -0000

DQoNCj4gDQo+IEZ1cnRoZXIsIE9wZW5TU0wgaXMgZnJlZXdhcmUgYW5kIGhhcyBUTFMgY29kZSBp
bnNpZGUuICBJdCBhbHNvIGhhcyBhIHZlcnkNCj4gcmVhc29uYWJsZSBtZW1vcnkgZm9vdHByaW50
LiAgU28gZm9yIGEgcmFkaW8gdmVuZG9yIHRvIHNheSBUTFMgaXMgdG9vIGhhcmQgdG8NCj4gaW1w
bGVtZW50IHNlZW1zIGEgYml0IHNpbGx5LiAgQWxsIHRoZXkgbmVlZCB0byBkbyBpcyBwb3J0IGEg
Yml0IG9mIG5vLWNvc3Qgb3Blbi0NCj4gc291cmNlIGNvZGUgaW50byB0aGVpciByYWRpby4gSWYg
dGhlaXIgcmFkaW8gaGFzIFNOTVAsIGl0IHByb2JhYmx5IHVzZWQgdGhlDQo+IG9wZW4tc291cmNl
IE5ldFNOTVAgY29kZSBmb3IgdGhhdCDigJQgc28gcG9ydGluZyBvcGVuLXNvdXJjZSBpc27igJl0
IGEgbmV3DQo+IGNvbmNlcHQgdG8gcmFkaW8gdmVuZG9ycy4gIChGdXJ0aGVyLCBmb3IgdmVuZG9y
cyBpbiBhIGdvdmVybm1lbnRhbA0KPiBlbnZpcm9ubWVudCwgc29tZSBPcGVuU1NMIHZlcnNpb25z
IGhhdmUgTklTVCBGSVBTLTE0MCBhcHByb3ZhbCBhbHJlYWR5LikNCj4gDQoNCkp1c3QgdG8gbWFr
ZSBzdXJlIEkgdW5kZXJzdGFuZCAtIHBvcnRpbmcvaW1wbGVtZW50aW5nIFRMUyBpcyAnbm8gYmln
IHdob29wJywgYnV0IElQdjYgaXMgYSBub24tc3RhcnRlci4uLi4gDQoNClN0YW4NCg0KCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClRoaXMgZWxl
Y3Ryb25pYyBtZXNzYWdlIGFuZCBhbnkgZmlsZXMgdHJhbnNtaXR0ZWQgd2l0aCBpdCBjb250YWlu
cwppbmZvcm1hdGlvbiBmcm9tIGlEaXJlY3QsIHdoaWNoIG1heSBiZSBwcml2aWxlZ2VkLCBwcm9w
cmlldGFyeQphbmQvb3IgY29uZmlkZW50aWFsLiBJdCBpcyBpbnRlbmRlZCBzb2xlbHkgZm9yIHRo
ZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwKb3IgZW50aXR5IHRvIHdob20gdGhleSBhcmUgYWRkcmVz
c2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgb3JpZ2luYWwKcmVjaXBpZW50IG9yIHRoZSBwZXJzb24g
cmVzcG9uc2libGUgZm9yIGRlbGl2ZXJpbmcgdGhlIGVtYWlsIHRvIHRoZQppbnRlbmRlZCByZWNp
cGllbnQsIGJlIGFkdmlzZWQgdGhhdCB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsCmluIGVy
cm9yLCBhbmQgdGhhdCBhbnkgdXNlLCBkaXNzZW1pbmF0aW9uLCBmb3J3YXJkaW5nLCBwcmludGlu
Zywgb3IKY29weWluZyBvZiB0aGlzIGVtYWlsIGlzIHN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlv
dSByZWNlaXZlZCB0aGlzIGVtYWlsCmluIGVycm9yLCBwbGVhc2UgZGVsZXRlIGl0IGFuZCBpbW1l
ZGlhdGVseSBub3RpZnkgdGhlIHNlbmRlci4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18K


From nobody Tue Nov 24 10:56:05 2015
Return-Path: <rja.lists@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 4C6231A87BB for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:56:02 -0800 (PST)
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 8U-WNqilk0TE for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 10:56:00 -0800 (PST)
Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BAC91A87B9 for <manet@ietf.org>; Tue, 24 Nov 2015 10:56:00 -0800 (PST)
Received: by qgec40 with SMTP id c40so17103717qge.2 for <manet@ietf.org>; Tue, 24 Nov 2015 10:55:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wUoOr1bDggKNGv25NtaQSrWCfqzf75OJ6KBzxRe3EHA=; b=Lamb34/xZ1pulmqFqWFbnqScz8J1vedYJcI7ylM4a2MoUzDpt8NR97CVVB1lJMQUex yIqgSZGpuNgw7nHjRrNNVvGi6WrK3Mvzap5eqhg2gNkRMygOtsNaCriJTJ61/57UzrDt H3UZ+1/6t1T99t90pvjitxUVycEsZgQ5YrGUDbZGySxT+JSMVvJ78mnWt2c29GlMjoUi qoxvxQd8WrS79wKGBhk4gz2YNpfr0hCXtC5GuFDr6TK7G/IM24yHPMQ8aGrBChykmQba vCG9eQiKes4rnMt1CvYB47hjk7sFTVYxbkr5+41jM2iEgUB91KKg9aO1+YITuYDHhRBi w+8w==
X-Received: by 10.141.2.86 with SMTP id e83mr28811624qhd.64.1448391359566; Tue, 24 Nov 2015 10:55:59 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id f66sm3596356qkb.5.2015.11.24.10.55.58 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 10:55:59 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <CAGnRvup-a9GkDBH=RfgBMu=JRi=FuS6bMWeT3hyU43kVLGVbfw@mail.gmail.com>
Date: Tue, 24 Nov 2015 13:55:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B73EED4-EE24-4D1E-B9E7-F12322AE0299@gmail.com>
References: <8C867205-4F66-4026-AEA7-471B66D00FC9@gmail.com> <CAGnRvuqAf8b+cmdpTnJWuWcJ_Xnft8WyjOB7-cN7rpgzXCCT=w@mail.gmail.com> <7FEE2BD6-C9EA-4840-A870-5E30361DEC03@gmail.com> <CAGnRvup-a9GkDBH=RfgBMu=JRi=FuS6bMWeT3hyU43kVLGVbfw@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/4PrUuBzuoB_16lw6T_8vyaFBDcQ>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Section 5.1, security concern
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 18:56:02 -0000

> On 24  Nov 2015, at 13:38 , Henning Rogge <hrogge@gmail.com> wrote:
>=20
> On Tue, Nov 24, 2015 at 7:29 PM, RJ Atkinson <rja.lists@gmail.com> =
wrote:
>>> Unless you use something like 802.1x, which would keep the link safe
>>> (both data and control plane).
>>=20
>> I=E2=80=99d suggest also using MACsec or similar link encryption.
>> RFCs can suggest using 802.1x as a mitigation, by the way.
>=20
> either ways the problem to secure a single link has already been
> worked on in a generic way.

Yes.

> if your deployment is a dedicated ethernet card on the Router
> connected with a cable direct to the router you could skip all
> security.

Yes.

> if you do it with a manageable switch, you can deploy VLAN, 802.1x
> and/or MACsec... depending on your switch and security needs.

Yes, although the candidate mitigations would need to be documented
in DLEP=E2=80=99s Security Considerations, probably including =
informative
references to the appropriate IEEE 802 standards.

>>> I still stand with my suggesting making linklocal IPs mandatory for
>>> DLEP and drop all the TLS stuff... if someone wants to deploy a
>>> layer-2 VPN, he/she can also deal with the necessary security for =
the
>>> VPN.
>>=20
>> I=E2=80=99m ok with that, but its a change from the current =
specification,
>> and there still would need to be discussion of the new threats
>> that using an L2 VPN would bring.  It is possible that the IETF
>> Security Area would consider that sufficient, but I=E2=80=99m not =
certain.
>=20
> Again, the advantage would be that a lot of security issues of a L2
> VPN have already been talked about in other WGs... it would make it
> unnecessary to re-invent the wheel for DLEP.

Yes

I believe that the Layer-2/on-link security issues need to be =
documented.
I think most of the relevant security standards for layer-2 were done
in IEEE, which one could simply cite as mitigations for the operator
to consider using. =20

Cheers,

Ran



From nobody Tue Nov 24 11:00:58 2015
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 DD7BD1A6FB2 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 11:00:52 -0800 (PST)
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 mJfU0_uKG5RC for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 11:00:51 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BAF81A87A9 for <manet@ietf.org>; Tue, 24 Nov 2015 11:00:50 -0800 (PST)
Received: by wmww144 with SMTP id w144so151668197wmw.1 for <manet@ietf.org>; Tue, 24 Nov 2015 11:00:49 -0800 (PST)
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=zykYhyuaDrawbQtHab83ZirQIKIcmhm7xk+egZ/rNNo=; b=ttayM+XtE9vQMGzo9kgaUYLR5vOIqtZD91x+f4fzy4HdFhqbplA6YYo3iqpbJjEbl7 t6vg262Sv2engv/jHaMvAy09L3XBY2mfyFnNVW6sRFuHU/s0ibbKRZBEs29rOwdWeWLU RHMeJlIuOA88nOZeBNrd8BwFIZ0+laqbne2RlA4fjbqXRj+3+FCynniOITUXQ6qPBFrB WDOXj1QM/A4xERTPV8fHoR0fTnhbVK5ZMFgjeg4py642RCK/xW9CfpdDhgLmGiyH+nrS L4v55lWgTKJm3YKtGQcy2Cfb5u0sVq3e4m3ECMs7hKygh0K2iqadTzXcOIc9ypa83YYl CVlg==
X-Received: by 10.194.104.5 with SMTP id ga5mr39042843wjb.155.1448391649250; Tue, 24 Nov 2015 11:00:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Tue, 24 Nov 2015 11:00:19 -0800 (PST)
In-Reply-To: <3B73EED4-EE24-4D1E-B9E7-F12322AE0299@gmail.com>
References: <8C867205-4F66-4026-AEA7-471B66D00FC9@gmail.com> <CAGnRvuqAf8b+cmdpTnJWuWcJ_Xnft8WyjOB7-cN7rpgzXCCT=w@mail.gmail.com> <7FEE2BD6-C9EA-4840-A870-5E30361DEC03@gmail.com> <CAGnRvup-a9GkDBH=RfgBMu=JRi=FuS6bMWeT3hyU43kVLGVbfw@mail.gmail.com> <3B73EED4-EE24-4D1E-B9E7-F12322AE0299@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 24 Nov 2015 20:00:19 +0100
Message-ID: <CAGnRvur-y85hr6Pu2rGfhdQit=guxeF5v+-RGMStZCyOCSEqDg@mail.gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/fiWSF_SP8RRbAxT4cgvYZ1FMx-E>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Section 5.1, security concern
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 19:00:53 -0000

On Tue, Nov 24, 2015 at 7:55 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
> Yes, although the candidate mitigations would need to be documented
> in DLEP=E2=80=99s Security Considerations, probably including informative
> references to the appropriate IEEE 802 standards.

Yes...

>>>> I still stand with my suggesting making linklocal IPs mandatory for
>>>> DLEP and drop all the TLS stuff... if someone wants to deploy a
>>>> layer-2 VPN, he/she can also deal with the necessary security for the
>>>> VPN.
>>>
>>> I=E2=80=99m ok with that, but its a change from the current specificati=
on,
>>> and there still would need to be discussion of the new threats
>>> that using an L2 VPN would bring.  It is possible that the IETF
>>> Security Area would consider that sufficient, but I=E2=80=99m not certa=
in.
>>
>> Again, the advantage would be that a lot of security issues of a L2
>> VPN have already been talked about in other WGs... it would make it
>> unnecessary to re-invent the wheel for DLEP.
>
> Yes
>
> I believe that the Layer-2/on-link security issues need to be documented.
> I think most of the relevant security standards for layer-2 were done
> in IEEE, which one could simply cite as mitigations for the operator
> to consider using.

Yes... but that sounds like a lot LESS complexity than all the things
we have to consider by moving to TLS...

I am worried about things like "Certificate livetimes" or "Certificate
revocation" too... and interesting problems when DLEP implementations
only provide a limited set of cyphers/hashes.

Henning Rogge


From nobody Tue Nov 24 11:01:29 2015
Return-Path: <rja.lists@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 5C3E31A87D0 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 11:01:24 -0800 (PST)
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 NGT1R0reDji1 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 11:01:22 -0800 (PST)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A38B51A87DB for <manet@ietf.org>; Tue, 24 Nov 2015 11:01:16 -0800 (PST)
Received: by qkfo3 with SMTP id o3so8583376qkf.1 for <manet@ietf.org>; Tue, 24 Nov 2015 11:01:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=W+3RpMd+NfF+jGhFL9rcFsVlCLat38kPTb+d7Z0yXo8=; b=EzdWua2vpuMjdkk82JlixMUrQvzvLx1hiL8Gn6VpbindILB388VISFUnNFI1h1ooYs WJYWlh5Xgdls0iNOjn6nuGIXuXZh5MOOJq0IVNzkcETVuJSKc/ro5pmmjvFRGyiZnV2h lN/0eCgysHClSlWC0rnTiL6f3tmsiThx/GDiEB+JlUX63blFMWMTv6omCFWNR+byVN+h y6+SlVY39mh89Vcis7Z19g2RbCt6exnhahDY6DUy/D3/DcsSVZRTuJrzt/4FWO3jwxRd cH2EVT+T2CRSr8DiAnXJB0HiV84KfBK3Ya1gNNf38wSmuRD9qTuDVfjCdhRhOAgaUI1g yzwA==
X-Received: by 10.55.74.132 with SMTP id x126mr34351578qka.43.1448391675834; Tue, 24 Nov 2015 11:01:15 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id 66sm4526347qgh.33.2015.11.24.11.01.15 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 11:01:15 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <baf8b4987dc044389259136829f47f70@VAUSDITCHM2.idirect.net>
Date: Tue, 24 Nov 2015 14:01:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B4CA9B2-E86F-49FE-A637-7EF9B97C69C1@gmail.com>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com> <D5CFA0FC-B2B4-44E0-9E0D-355E218E2102@gmail.com> <baf8b4987dc044389259136829f47f70@VAUSDITCHM2.idirect.net>
To: "Ratliff, Stanley" <sratliff@idirect.net>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/7tdXg9PoKAwbqgEfJ_BxYJ5K7F4>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 19:01:24 -0000

> On 24  Nov 2015, at 13:48 , Ratliff, Stanley <sratliff@idirect.net> =
wrote:
>=20
>=20
>>=20
>> If radio manufacturers are like some router vendors, they will claim =
the DLEP
>> RFC whether or not they implement TLS.  This is NOT good, but the =
situation
>> is not new to the IETF.
>>=20
>=20
> It's a sad state of affairs when the IETF is putting text into =
specifications
> that we know people will ignore (and in some cases, we'll *tell them* =
to ignore),
> but I guess that's a discussion for another thread.=20

Stan,

I am hard pressed to think of any IETF standards-track RFC that was =
FULLY
implemented to the RFC by ALL implementations.  Even bits of RFC-791 =
weren=E2=80=99t
done the way it said - by some implementers.  Very sad indeed.

I=E2=80=99ve been around the IETF since the late 1980s.  I=E2=80=99ve =
seen very very large=20
router vendors selectively implement RFCs.  I don=E2=80=99t recommend =
it.  I did=20
not do it when I was implementing IETF protocols at various employers.
It creates a lot of operational problems, some with interoperability and
others with security.  I am NOT happy about it.  However, it is real
and it is NOT new.  Even back in the 1980s, =E2=80=9Cquality of =
implementation=E2=80=9D was
an important factor for operators/users to consider when deciding what
gear to purchase.

But, yes, that thread probably is for another list.

Yours,

Ran


From nobody Tue Nov 24 11:06:49 2015
Return-Path: <rja.lists@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 E08191A87E9 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 11:06:47 -0800 (PST)
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 gKfL51-_rgtv for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 11:06:46 -0800 (PST)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FACF1A87DB for <manet@ietf.org>; Tue, 24 Nov 2015 11:06:46 -0800 (PST)
Received: by qgea14 with SMTP id a14so17354659qge.0 for <manet@ietf.org>; Tue, 24 Nov 2015 11:06:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=X4pFZsC+4GS0cpD+ur3vImW2AFgQsLjPjbex08cN1+4=; b=IlMe3U56zVqPHslTK+RZHAAlbQDPC0Yfr9u1t1OLCqhcNO1eOaoJSRA1cq09RJyVgX H1T6sk1sU9OHEwTNfXe/Qiryz+lqQt/EMtIhmA/4XcZ8hcUZvD4jPx0/M3o23T0SJAM+ 5uOoPNoUsemrw8yPLvEWfsfI51+Is62k2J+cpF4TdERWxKIz5T42VwouMdF8E7wyN29B y0Z1O9AC/i8ryYF4it+58OBKZFnhS03oVqyGcGbIO6r5sww0GfJR7xllUeD059abIyPy cLwU/wV4Vzt9yqghMfvKlYRAUG532I0NTTzjkbJ64EzDfXnq7i6nU5umlt9P8d+hNK14 eKmw==
X-Received: by 10.140.217.138 with SMTP id n132mr37098943qhb.26.1448392005551;  Tue, 24 Nov 2015 11:06:45 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id y200sm4565123qka.48.2015.11.24.11.06.44 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 11:06:45 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <6b6423e6db0e42e5bcc58ec966730d8e@VAUSDITCHM2.idirect.net>
Date: Tue, 24 Nov 2015 14:06:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C758D61F-A65D-4612-A249-CECCC036AEE2@gmail.com>
References: <BBE4C48E-B400-4071-8B68-1A088B2C867D@gmail.com> <17688_1448385550_56549C0E_17688_6973_1_38A5475DE83986499AEACD2CFAFC3F9801A8B05334@tss-server1.home.tropicalstormsoftware.com> <D9712B947A4CCA43AB42F01B90AF1DEC011F5B58B6@AUK52982.UKN.UKNROOT.ASTRIUM.CORP> <7FC7C1F2-5F6B-4110-8B9D-1B54B655890C@gmail.com> <6b6423e6db0e42e5bcc58ec966730d8e@VAUSDITCHM2.idirect.net>
To: "Ratliff, Stanley" <sratliff@idirect.net>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/u__I6YgcNnzKq3OlOaHCd6UfaWY>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Security Considerations
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 19:06:48 -0000

> On 24  Nov 2015, at 13:50 , Ratliff, Stanley <sratliff@idirect.net> =
wrote:
>=20
>=20
>=20
>>=20
>> Further, OpenSSL is freeware and has TLS code inside.  It also has a =
very
>> reasonable memory footprint.  So for a radio vendor to say TLS is too =
hard to
>> implement seems a bit silly.  All they need to do is port a bit of =
no-cost open-
>> source code into their radio. If their radio has SNMP, it probably =
used the
>> open-source NetSNMP code for that =E2=80=94 so porting open-source =
isn=E2=80=99t a new
>> concept to radio vendors.  (Further, for vendors in a governmental
>> environment, some OpenSSL versions have NIST FIPS-140 approval =
already.)
>>=20
>=20
> Just to make sure I understand - porting/implementing TLS is 'no big =
whoop=E2=80=99,
> but IPv6 is a non-starter....=20

There are at least 2 separate issues that make TLS very much easier to =
port
into a small embedded system, such as a radio.

First, TLS is a library at the application layer, outside the kernel. =20=

IPv6 is deep inside the kernel, often touching device drivers, and=20
it is pervasive inside the kernel with tentacles many places.  In =
theory,
all RFC-compliant IPv6 implementations also have to support IPsec.

Second, porting IPv6 as it was in 1995 would have been easier, with
a much smaller memory footprint than today.  These days, after 2nd =
system=20
effect and all the endless tweaks to IPv6, ND alone today is probably=20
bigger than all of IPv6 was in 1995.  Been there, done that.  Sigh.

Yours,

Ran


From nobody Tue Nov 24 12:26:41 2015
Return-Path: <rja.lists@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 08B231A896A for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 12:26:39 -0800 (PST)
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 5JGqYXVG9DP2 for <manet@ietfa.amsl.com>; Tue, 24 Nov 2015 12:26:37 -0800 (PST)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C1591A8958 for <manet@ietf.org>; Tue, 24 Nov 2015 12:26:37 -0800 (PST)
Received: by qkao63 with SMTP id o63so9384658qka.2 for <manet@ietf.org>; Tue, 24 Nov 2015 12:26:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qX5ucQGF7UuPnKTzhzrF83y/xRe/qqrQOtZyHaAMm90=; b=Ae6a0CJ4LMlV7C+qPSIAWxB7POd/uBuPMftvR4FEyH6CRTOkWHvapQjntgifdcDsya 8kFPCsy6lF9PyluZ96m8tNJwRJS13v+po9D/ao7r4ir9rbIa0X6ha0z+nB0mLHGbo8uu HqLrs+Hod7uxZOSMfE3Z0V7dbKxMUSrJi44WNdbahjy4/j9DFpUnIXIE6lz8qLMTXn94 WA7uEhpAppMDNmLOyzpJjA7wM2imc8cGAGpd02/dhgE9GyaUtk0mET22bUtJEuy+6qoN qOTTCJiO2snHs6dEMQiKbmkQ5bB1S8hh8tFFLg5M+Bi4B4aWIq7Rj9Z2MuQCZJVk4dHF JJ3w==
X-Received: by 10.55.81.11 with SMTP id f11mr34976874qkb.10.1448396796836; Tue, 24 Nov 2015 12:26:36 -0800 (PST)
Received: from [10.30.20.14] (pool-108-31-161-77.washdc.fios.verizon.net. [108.31.161.77]) by smtp.gmail.com with ESMTPSA id n74sm3394931qgd.25.2015.11.24.12.26.36 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 24 Nov 2015 12:26:36 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B05464@tss-server1.home.tropicalstormsoftware.com>
Date: Tue, 24 Nov 2015 15:26:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B2A2EDB-809D-412B-B152-0BC8415EA982@gmail.com>
References: <09672065-ED6B-40F1-B36F-81E6B721061B@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B05464@tss-server1.home.tropicalstormsoftware.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/KggEEggo4ilklZM4WBLvRcdrnRM>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: IANA Considerations - example
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Nov 2015 20:26:39 -0000

> On 24  Nov 2015, at 12:36 , Rick Taylor =
<rick@tropicalstormsoftware.com> wrote:
>=20
> My gut feeling is that Messages should require Standards Action as =
they=20
> alter the protocol, where-as new metrics might only need Specification=20=

> Required.

At least at first glance, that seems plausible to me. =20

I don=92t immediately see as many situations where a new Signal/
Message Type really is needed, given the set that exist now.

By contrast, I can see lots of situations where use of some=20
new radio might be optimized by specifying some additional=20
Data Types.

I need to give Status Codes more thought.

> We will certainly give it some thought.

Thanks,

Ran



From nobody Wed Nov 25 01:41:12 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 414A61A038D for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 01:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] 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 ZrqbxRrc0gfF for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 01:41:10 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A17D61A0389 for <manet@ietf.org>; Wed, 25 Nov 2015 01:41:09 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id tAP9f7FW020639; Wed, 25 Nov 2015 10:41:07 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 861EF62017; Wed, 25 Nov 2015 10:41:07 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id brWxKNXo6Y1s; Wed, 25 Nov 2015 10:41:02 +0100 (CET)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 066CF61FBB; Wed, 25 Nov 2015 10:41:02 +0100 (CET)
Date: Wed, 25 Nov 2015 10:41:02 +0100
Message-ID: <87wpt6to0h.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Henning Rogge <hrogge@gmail.com>
In-Reply-To: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com>
References: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Wed, 25 Nov 2015 10:41:07 +0100 (CET)
X-Miltered: at korolev with ID 56558233.005 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 56558233.005 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 56558233.005 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/AD1YYj7ZpSsgOtTVaM3oruwDr0o>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 09:41:11 -0000

> From my point of view we are killing a really good part of DLEP, the
> zero configuration autodiscovery. Plug your DSL-Modem/Radio into your
> Router and it will work!

[...]

> Linklocal-only DLEP.

[...]

> And lets throw out ALL TLS out of the [base] DLEP draft.

Please listen to this man.  More experience is needed before we converge
on a sane security model for DLEP, and the base DLEP work should not be
held up by this.

-- Juliusz


From nobody Wed Nov 25 02:28:42 2015
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 E8DA41A1A78 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 02:28:40 -0800 (PST)
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 f-mpaYrh2q2c for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 02:28:39 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D85E1A1A76 for <manet@ietf.org>; Wed, 25 Nov 2015 02:28:39 -0800 (PST)
Received: by wmuu63 with SMTP id u63so131692620wmu.0 for <manet@ietf.org>; Wed, 25 Nov 2015 02:28:37 -0800 (PST)
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=t3UulW0i4CbJt0bIQyi2wwg47mfRY+sCLAPc3QVZ/FE=; b=kbu/qFUVNjTncXMSWCfd3cux3HJ+vylb0296zXiGjSiWcEULozDv4LmDnXWnh8tf/B HGxNDgz6Ep9QkTnGBzNwc+Jtr8ixLqbzAH8CMep4nH7fDeEJMcDU8aVD8PojtI/vWHbt e/psxjIGAQFAmSuroS3g+RGmm7/ct8dWClauuZYwXY1WVB3ChQBCR05cyD1RYL+HLK+P htmrAiS7wqoWLVwNeTvtLLmydRYvFdP+ilzAU7Fg6Nj51JZ0B97IH2pBkgbhdANVSccE RYsATDzPak6+U5+GnSono0jkBFVq3BfkGIxIkvdzBq+KU3iX3IohQYElDJyKsMo1fDfs Lq5g==
X-Received: by 10.28.141.17 with SMTP id p17mr3436919wmd.35.1448447317723; Wed, 25 Nov 2015 02:28:37 -0800 (PST)
Received: from [10.5.242.125] (dab-glb1-h-67-7.dab.02.net. [82.132.218.221]) by smtp.gmail.com with ESMTPSA id e83sm2790448wmc.23.2015.11.25.02.28.33 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 Nov 2015 02:28:36 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
References: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com> <87wpt6to0h.wl-jch@pps.univ-paris-diderot.fr>
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <87wpt6to0h.wl-jch@pps.univ-paris-diderot.fr>
Message-Id: <AD5BBEB7-5A04-4864-AB48-68FE1CE62FBE@gmail.com>
Date: Wed, 25 Nov 2015 10:22:01 +0000
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: iPhone Mail (13B143)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/BTbipMxMLvIjG_x8xEo1Zx-hU7s>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 10:28:41 -0000

Unfortunately or fortunately, depending on your point of view, that's not ho=
w it works. "Base spec now, security later" isn't accepted. (One argument is=
 about whether later ever arrives.) Separate documents, perhaps. But that wi=
ll still hold up the base spec.

-- =20
Christopher Dearlove
christopher.dearlove@gmail.com

On 25 Nov 2015, at 09:41, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>=
 wrote:

>> =46rom my point of view we are killing a really good part of DLEP, the
>> zero configuration autodiscovery. Plug your DSL-Modem/Radio into your
>> Router and it will work!
>=20
> [...]
>=20
>> Linklocal-only DLEP.
>=20
> [...]
>=20
>> And lets throw out ALL TLS out of the [base] DLEP draft.
>=20
> Please listen to this man.  More experience is needed before we converge
> on a sane security model for DLEP, and the base DLEP work should not be
> held up by this.
>=20
> -- Juliusz
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Wed Nov 25 04:40:47 2015
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 C35391B2C30 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 04:40:45 -0800 (PST)
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 1Fxmkio-mpi2 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 04:40:44 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 649AC1B2C23 for <manet@ietf.org>; Wed, 25 Nov 2015 04:40:44 -0800 (PST)
Received: by wmuu63 with SMTP id u63so136273062wmu.0 for <manet@ietf.org>; Wed, 25 Nov 2015 04:40:43 -0800 (PST)
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=EAv4UldQ+9VO6RRcMJOvy8I2ucudKrqnzM/StbV9Il4=; b=n2CG8KR8fbnZADgN1EzcXvS0Ig/3J/iJrVWTzw5fjQpJmY5iktRovjgTPGK04v+MdP rMEf9xLnuZWoCXDGmcbCFG46DwkgTb13qVM8JN1xPXxjddiNFTvzC+pSn7qGdcnRn71l 3it8QLHkVyZnW/jhSLRoPB5oFnPls10x8vvmhKT4DzM4IEY059l7CWJjDPzdU9wM2+h2 DjeY0IWQs5l3w2fXvjNE9yVpWFgFry0RMyBe7wHqd+xdGMwxNOcI9duol5C6543pk1hx IGdsP+S/hNIyQZA67U86cAc+/hQ5NiRM7Y9LCIm1oJ4wqIJiUgPY8RbHLYCqVcAQw1cq cirg==
X-Received: by 10.194.95.65 with SMTP id di1mr41267968wjb.134.1448455242951; Wed, 25 Nov 2015 04:40:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 25 Nov 2015 04:40:13 -0800 (PST)
In-Reply-To: <AD5BBEB7-5A04-4864-AB48-68FE1CE62FBE@gmail.com>
References: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com> <87wpt6to0h.wl-jch@pps.univ-paris-diderot.fr> <AD5BBEB7-5A04-4864-AB48-68FE1CE62FBE@gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 25 Nov 2015 13:40:13 +0100
Message-ID: <CAGnRvurRX8T9AUWk2WoubLoBJH_rOYNsg2rYs3k2kPJPvOeinw@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/H3CP_ifFV2KBhDaI8_9tCznPk-U>
Cc: MANET IETF <manet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 12:40:45 -0000

On Wed, Nov 25, 2015 at 11:22 AM, Christopher Dearlove
<christopher.dearlove@gmail.com> wrote:
> Unfortunately or fortunately, depending on your point of view, that's not=
 how it works. "Base spec now, security later" isn't accepted. (One argumen=
t is about whether later ever arrives.) Separate documents, perhaps. But th=
at will still hold up the base spec.

Yes it does work... in a certain way.

A "linklocal DLEP" can just point to the existing ways to secure a
link instead of modifying the protocol itself.

something like:

> Security Considerations (quick and dirty version):
> a) at best, use a dedicated plug on the router and a direct cable connect=
ion
> b) otherwise use a VLAN separation to keep the other traffic away from th=
e user/control data to the radio
>
> you can also add 802.1x to control the devices connected to your interfac=
es and/or MACsec to provide an encrypted link for both user and control tra=
ffic

the advantage of this is that NONE of these things make DLEP more
complex, they can be deployed independently.

I would also suggest to add something like
"by default, the DLEP radio should use linklocal addresses for both
UDP and TCP socket. If an administrator changes this, the link MUST be
secured with one or multiple of the options mentioned in the Security
Considerations."

Henning Rogge


From nobody Wed Nov 25 05:17:51 2015
Return-Path: <rick@tropicalstormsoftware.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 377FD1B2C53 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:17:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 XPJBOEYkP8s0 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:17:48 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F06DF1B2C4F for <manet@ietf.org>; Wed, 25 Nov 2015 05:17:47 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Wed, 25 Nov 2015 13:17:21 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>, Christopher Dearlove <christopher.dearlove@gmail.com>
Thread-Topic: [manet] Linklocal DLEP
Thread-Index: AQHRJt7l9LrXpBvSJE2u010DeCngeA==
Date: Wed, 25 Nov 2015 13:17:20 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B08CA7@tss-server1.home.tropicalstormsoftware.com>
References: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com> <87wpt6to0h.wl-jch@pps.univ-paris-diderot.fr> <AD5BBEB7-5A04-4864-AB48-68FE1CE62FBE@gmail.com> <CAGnRvurRX8T9AUWk2WoubLoBJH_rOYNsg2rYs3k2kPJPvOeinw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/4G33zWi5wu6_FF1vMsXYnuDu_jk>
Cc: MANET IETF <manet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:17:50 -0000

On 25/11/15 12:40, Henning Rogge wrote:=0A=
> On Wed, Nov 25, 2015 at 11:22 AM, Christopher Dearlove=0A=
> <christopher.dearlove@gmail.com> wrote:=0A=
>> Unfortunately or fortunately, depending on your point of view, that's no=
t how it works. "Base spec now, security later" isn't accepted. (One argume=
nt is about whether later ever arrives.) Separate documents, perhaps. But t=
hat will still hold up the base spec.=0A=
>=0A=
> Yes it does work... in a certain way.=0A=
>=0A=
> A "linklocal DLEP" can just point to the existing ways to secure a=0A=
> link instead of modifying the protocol itself.=0A=
>=0A=
> something like:=0A=
>=0A=
>> Security Considerations (quick and dirty version):=0A=
>> a) at best, use a dedicated plug on the router and a direct cable connec=
tion=0A=
>> b) otherwise use a VLAN separation to keep the other traffic away from t=
he user/control data to the radio=0A=
=0A=
The VLAN separation is actually required for the data plane anyway.=0A=
=0A=
>>=0A=
>> you can also add 802.1x to control the devices connected to your interfa=
ces and/or MACsec to provide an encrypted link for both user and control tr=
affic=0A=
>=0A=
> the advantage of this is that NONE of these things make DLEP more=0A=
> complex, they can be deployed independently.=0A=
>=0A=
> I would also suggest to add something like=0A=
> "by default, the DLEP radio should use linklocal addresses for both=0A=
> UDP and TCP socket. If an administrator changes this, the link MUST be=0A=
> secured with one or multiple of the options mentioned in the Security=0A=
> Considerations."=0A=
=0A=
+1, The hard part as I see it is crafting the words.=0A=
=0A=
Does anyone have any issue with what I see as emerging consensus around:=0A=
=0A=
1) STRONGLY RECOMMENDING Link-local addresses and/or direct connection.=0A=
=0A=
2) Referencing the various layer-2 security solutions for >1 hop =0A=
deployments.=0A=
=0A=
3) Removing the TLS requirement.=0A=
=0A=
Rick=0A=


From nobody Wed Nov 25 05:23:03 2015
Return-Path: <rick@tropicalstormsoftware.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 8FCF71B2C46 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:23:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 Cvg0Sbbi_2on for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:23:00 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6F901B2C6A for <manet@ietf.org>; Wed, 25 Nov 2015 05:22:59 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Wed, 25 Nov 2015 13:22:27 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>
Thread-Topic: [manet] DLEP-17:  well-known IPv4 link-local multicast address
Thread-Index: AQHRJs1t4NGRqeKuwESH7X34pLojhQ==
Date: Wed, 25 Nov 2015 13:22:26 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B08CFB@tss-server1.home.tropicalstormsoftware.com>
References: <4C2E2E59-68FB-45A8-A24F-4F8AC6E3D1EB@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04F12@tss-server1.home.tropicalstormsoftware.com> <23B3A59F-4A50-454E-8A5E-F8C3C7FD0E62@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/_5yw495miJ8IkaYQwPl57j4apyA>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17:  well-known IPv4 link-local multicast 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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:23:01 -0000

On 24/11/15 18:05, RJ Atkinson wrote:=0A=
>=0A=
>> On 24  Nov 2015, at 11:12 , Rick Taylor <rick@tropicalstormsoftware.com>=
 wrote:=0A=
>>=0A=
>> Ran,=0A=
>>=0A=
>> We resisted the urge to request one of the few remaining IPv4 multicast=
=0A=
>> addresses, and went for the IPv4 broadcast address instead.  Discovery=
=0A=
>> is a single-hop process anyway.=0A=
>=0A=
> Thanks for the clarification.=0A=
>=0A=
>=0A=
> (OPINION)=0A=
>=0A=
> A) I don=92t think that IPv4 link-local multicast addresses are particula=
rly scarce.=0A=
>     I checked that registry today before sending that note.=0A=
>=0A=
> B) Use of broadcast seems impolite to other nodes on that link.  Modern=
=0A=
>     IETF practice is to try to avoid using link-broadcast, in part becaus=
e=0A=
>     of widespread negative operational impacts of link-broadcast traffic.=
=0A=
>=0A=
=0A=
We might have fallen into the trap of making assumptions about IANA =0A=
here.  Personally I would prefer a link-local IPv4 multicast address.=0A=
=0A=
Rick=0A=
=0A=


From nobody Wed Nov 25 05:24:05 2015
Return-Path: <prvs=8771818a19=david.wiggins@ll.mit.edu>
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 328371B2C5E for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:24:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.784
X-Spam-Level: 
X-Spam-Status: No, score=-4.784 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, UNPARSEABLE_RELAY=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 TLwG-hxh9J02 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:23:58 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id AD1B61B2C46 for <manet@ietf.org>; Wed, 25 Nov 2015 05:23:58 -0800 (PST)
Received: from LLE2K10-HUB01.mitll.ad.local (LLE2K10-HUB01.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tAPDNv9R018737; Wed, 25 Nov 2015 08:23:57 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: Rick Taylor <rick@tropicalstormsoftware.com>, Henning Rogge <hrogge@gmail.com>, Christopher Dearlove <christopher.dearlove@gmail.com>
Thread-Topic: [manet] Linklocal DLEP
Thread-Index: AQHRJt71+D+bn+VeREO9Q2fK6jHHC56su1OA
Date: Wed, 25 Nov 2015 13:23:56 +0000
Message-ID: <D27B201E.12FD%David.Wiggins@ll.mit.edu>
References: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com> <87wpt6to0h.wl-jch@pps.univ-paris-diderot.fr> <AD5BBEB7-5A04-4864-AB48-68FE1CE62FBE@gmail.com> <CAGnRvurRX8T9AUWk2WoubLoBJH_rOYNsg2rYs3k2kPJPvOeinw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08CA7@tss-server1.home.tropicalstormsoftware.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B08CA7@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.59.174]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3531284635_83053478"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-11-25_10:2015-11-24,2015-11-25,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1508030000 definitions=main-1511250231
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/os9j4IkKXvEseckn4SD1F_wGHqs>
Cc: MANET IETF <manet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:24:04 -0000

--B_3531284635_83053478
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

On 11/25/15, 8:17 AM, "manet on behalf of Rick Taylor"
<manet-bounces@ietf.org on behalf of rick@tropicalstormsoftware.com> wrote:
>Does anyone have any issue with what I see as emerging consensus around:
>
>1) STRONGLY RECOMMENDING Link-local addresses and/or direct connection.
>
>2) Referencing the various layer-2 security solutions for >1 hop
>deployments.
>
>3) Removing the TLS requirement.

I like this general direction.  The ongoing hassle of certificate
management with TLS was starting to concern me.

David

--B_3531284635_83053478
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIMEgYJKoZIhvcNAQcCoIIMAzCCC/8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CfUwggT1MIID3aADAgECAgpar+vgAAAAADYOMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAMTCk1JVExMIENBLTMwHhcNMTUwNDA2MTE1OTM4WhcNMTYwNDA1MTE1OTM4WjBiMQsw
CQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMG
UGVvcGxlMSEwHwYDVQQDExhXaWdnaW5zLkRhdmlkLlAuNTAwMTUyMDcwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDdVA0BrVjbk6NP8JFi7Lks3SHtN8CxSBqFLPNRVWGjTgLG
W9pDcqqOrij0IHmGpAP404gR4dP9mUEb9KfOhKuDdFQFyZnVICDSRbyT4tGOxiTH7MIsV49d
UwrWhj2P/ms6wf1E5L2QwJqjOTMPZj3IClWAkcZsAix5jHkLvNXI5OilCe2u2TDihM1x2kfB
zgQpRy9tuXpxYtFZpoEb0XbqLIzS9FLkTbqlocSm4jwhPXTFQtFwbd6l4zzD4RVPgnpFxg/8
KpuV35lGkp5lbPvpkskz4+n3P9LoCvpoh1pgj3fS0CvCVRzWRAX+oNR/D7RmP1ug+7Ix+JCg
iAB3vLdFAgMBAAGjggG8MIIBuDAdBgNVHQ4EFgQUofYOKn4e6iCZO59iu2f0FxOad4MwDgYD
VR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUH
AQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcE
MDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAiBgNV
HSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMCMGA1UdEQQcMBqBGERhdmlkLldpZ2dpbnNAbGwubWl0LmVkdTAnBgkrBgEEAYI3FAIE
Gh4YAEwATABVAHMAZQByAFMAaQBnAC0AUwBXMA0GCSqGSIb3DQEBCwUAA4IBAQCgEybvvRIJ
tAlKEfYZyf5DIlcT+LfePOiebFcPxZatSTQW/hJHv4RX/TN8N3bQrx4Jkxe17eQfsKvJXhOi
R6as3vemCxYEMOFIKSsm5LEIC4D4GcXBRZ1CAJIHCY5ezXfKQUxBSdZAq82/fAoNEEP4KPEv
Y07m7OVwXMWpu7kz3CeBVOqL7xlL53pPvkyxtijQRtZrZ5coE9Qh9tHzATi7DW8UWoUv3Yhj
Qz9SnBn3T30ho0GtlTvMXso7UjGZFWLQI2JyR2QW5FYq8GGEq/5PRz/xslsKA5EoHxmSSeRh
eei3gpFbnUrRS+5JSS6kgA/HVoM7CRFo/O8KYXU5z/ihMIIE+DCCA+CgAwIBAgIKWrCpkwAA
AAA2DzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNv
bG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1
MDQwNjEyMDAyNloXDTE2MDQwNTEyMDAyNlowYjELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBlb3BsZTEhMB8GA1UEAxMYV2lnZ2lu
cy5EYXZpZC5QLjUwMDE1MjA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlEWD
uIm5kuHghfe7O+eMLVena6sNfAZtHLp2mwXLrNshaHM6wVKmml8zhxeSmJJXTF3Owyn7imKs
vHMWcIJD9EoFQyJoeBaFV5Ll75/fE2WKswtGn9ZSSejplI/Iy99SI/9Lna5B7/BDmPozGn66
jdzgl+JVFptqEUGx5NZlRUEEtVtXYUy+PllIq6SpR/242wFiYVslFqSoHu789mexaDDAl7p7
z3W9cYidPtZUoysjW0omzwZIoYMsIhTbUMnv+TkBuhJErBmaNvAXPf8Y3pNf3pYz8pnR4MyI
ibFv2CS/2KLGxJRE9xt1nrgHT8Wx+E6Ro6IYkYLPSdE6YgYAgwIDAQABo4IBvzCCAbswHQYD
VR0OBBYEFGww5LYEZSoVOkuJ7ZVJS+35ChrUMA4GA1UdDwEB/wQEAwIFIDAfBgNVHSMEGDAW
gBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0
cDovL2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2Nz
cC5sbC5taXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aG
rYcVg+rwRYW2oR8dhevQcIPr7SACAWQCAQQwJQYDVR0lBB4wHAYEVR0lAAYIKwYBBQUHAwQG
CisGAQQBgjcKAwQwGAYDVR0gBBEwDzANBgsqhkiG9xICAQMBCDAjBgNVHREEHDAagRhEYXZp
ZC5XaWdnaW5zQGxsLm1pdC5lZHUwJwYJKwYBBAGCNxQCBBoeGABMAEwAVQBzAGUAcgBFAG4A
YwAtAFMAVzANBgkqhkiG9w0BAQsFAAOCAQEATCsJT66TKeYNh9hrcC1wxRH08CricKt9JktB
I1WWl48F4CqcYDZlLMpvHuSe6GezZzTUH4oq1y2q3um9Txh1NjLPT7j0k5SSwdr2V7d8upDN
WOrXvCi59Cyz5RvuhleCPIE+6wPyDrQwfBRhte/cv8PVOrsG4tio4VOHi/nXcS+HLgC5qNxk
1/w1UBf8QkkNP8kIgum/uItm4QwVdVAJMuwe3te8dYjtp3M5nC2exfqQfk+Mmw/8fdZFpch0
rSYbpchMMOueBuy2UnWaYBF84uXldBH9fkONRX8AL8EQ3sQEOyzxqpwKQ/d0itjAGaPCCJCI
VgnSYSWYoFiN9idyaTGCAeUwggHhAgEBMF8wUTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTETMBEGA1UEAxMKTUlUTEwgQ0Et
MwIKWq/r4AAAAAA2DjAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFGJgWKP49INOjpb5
KMFJVFqq85ClMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MTEyNTEzMjM1NVowDQYJKoZIhvcNAQEBBQAEggEAtuaHekN0Hp66rqGs+RScwbdVIcbdI27L
SE6Y/qj+xpJesHfD9CdJ65PPK5ahnvCGckcenWUL944PEKAn+w0n2wjZugAcPCSrlDj75hVP
XYjAfkZc/0LPSyhNIWEPSH2vyUN+/qlXLQtKu6DoMsmNIlP+VfgdDTNJP7CcV+L+j02vxaN1
AqwNFfMTnD3SkVOci7YIlo/ZRSqKg2GpOxLH0sQBVnUJ9H29fIZg0mjR8trF5rQFU5l4DcHP
OP5zxQRUAQrJqZOkVLrqLfTCeEwoW9XiJHNMtD63EXDmoBigkb4xMK+iIQWoQa07n3LbDFVJ
gLd9GC1hppsetGOSerotyQ==

--B_3531284635_83053478--


From nobody Wed Nov 25 05:25:42 2015
Return-Path: <rick@tropicalstormsoftware.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 634411B2C6E for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:25:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 20gN7JqtR-tT for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:25:40 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7F1B1B2C46 for <manet@ietf.org>; Wed, 25 Nov 2015 05:25:39 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Wed, 25 Nov 2015 13:25:06 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>
Thread-Topic: [manet] DLEP-17: error handling during "In-Session" state
Thread-Index: AQHRJtBu2WxC5skuw0KB6S2DjRdVlA==
Date: Wed, 25 Nov 2015 13:25:05 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B08D14@tss-server1.home.tropicalstormsoftware.com>
References: <447C1544-14DF-40C3-BA23-97F4F146A374@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04EE5@tss-server1.home.tropicalstormsoftware.com> <71ECF18E-E2A7-4308-8261-4A3E188270EB@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/WWLRuC24HCBNEdW4c3DSm6NVVDM>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: error handling during "In-Session" state
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:25:41 -0000

On 24/11/15 18:03, RJ Atkinson wrote:=0A=
>=0A=
>> On 24  Nov 2015, at 11:10 , Rick Taylor <rick@tropicalstormsoftware.com>=
 wrote:=0A=
>>=0A=
>> Thanks Ran,=0A=
>>=0A=
>> My current thoughts are to add a blanket statement to Section 5, saying=
=0A=
>> something along the lines of "A TCP reset in any state causes an=0A=
>> immediate transition to the relevant initial state, clearing any session=
=0A=
>> information bases.=94=0A=
>=0A=
> I am unclear what =93relevant initial state=94 above means.  Perhaps=0A=
> say that when one receives a TCP Reset that (a) the current DLEP=0A=
> session terminates and (b) the receiver should do X=0A=
=0A=
The 'relevant initial state' text is used in the Session Flows section =0A=
to mean "discovery state or session initialization state if you are a =0A=
router and not doing discovery".  Out of context I can see it being unclear=
.=0A=
=0A=
>=0A=
> [alternately: "(b) the receiver should listen on the DLEP port=0A=
> as it would if the previous abruptly terminated DLEP session=0A=
> had never existed=94]=0A=
>=0A=
> I=92m not sure what you mean =93X" to be.  It could be do X or=0A=
> to do nothing.  Please edit to make it clear somehow.=0A=
>=0A=
>> I don't see the need for special handling for particular states, or any=
=0A=
>> kind of 'gentle' restarting.=0A=
>=0A=
> I=92m flexible about how to resolve this.=0A=
>=0A=
> The key thing for me is to document the intended reaction,=0A=
> so that a naive implementer has a good probability of=0A=
> coding correctly.=0A=
>=0A=
=0A=
Completely agree.=0A=
=0A=
Rick=0A=


From nobody Wed Nov 25 05:27:42 2015
Return-Path: <rick@tropicalstormsoftware.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 ED72F1B2C7C for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 06xCGBQkoxeM for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:27:39 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25A441B2C70 for <manet@ietf.org>; Wed, 25 Nov 2015 05:27:39 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Wed, 25 Nov 2015 13:27:04 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ Atkinson <rja.lists@gmail.com>
Thread-Topic: [manet] DLEP-17: Assumptions
Thread-Index: AQHRJtOAjDIAGYgxjUucJQUCqwsclA==
Date: Wed, 25 Nov 2015 13:27:02 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B08D45@tss-server1.home.tropicalstormsoftware.com>
References: <57909BAD-55EB-4AE7-913F-745166306D4A@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B0500C@tss-server1.home.tropicalstormsoftware.com> <18E52109-97E3-47D7-A474-F708D20AD677@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/NcYb2fZMBaxnP1zmpO8Ks7exnGQ>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: Assumptions
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:27:41 -0000

On 24/11/15 18:21, RJ Atkinson wrote:=0A=
>=0A=
>> On 24  Nov 2015, at 11:28 , Rick Taylor <rick@tropicalstormsoftware.com>=
 wrote:=0A=
>>=0A=
>> Ran,=0A=
>>=0A=
>> I was working under the assumption (and yes, I know it is an assumption)=
=0A=
>> that in 2015 the IETF would mandate IPv6, and not let us get away with=
=0A=
>> an either/or approach.=0A=
>=0A=
> I don=92t think that is a valid assumption.=0A=
>=0A=
> The IETF generally mandates that IPv6 support must be specified,=0A=
> but generally also still supports IPv4 in IETF specifications.=0A=
>=0A=
> As a concrete example, OSPFv3 can carry both IPv6 and IPv4 prefixes,=0A=
> yet IETF OSPF WG is adding =93segment routing extensions=94 to OSPFv2=0A=
> (and OSPFv2 ONLY supports IPv4 prefixes and ONLY runs over IPv4).=0A=
> Separately, there is also OSPF WG draft on how to frame OSPFv3 over IPv4,=
=0A=
> primarily as an IPv6-transition aid.=0A=
>=0A=
>> I totally understand the difficulties of IPv6 and legacy equipment,=0A=
>> but DLEP must mandate 1 method of discovery, and I can't see the IESG=0A=
>> letting us mandate IPv4.=0A=
>=0A=
> What DLEP **can** do (and SHOULD do) is specify both how DLEP works=0A=
> in an IPv6 environment =97 and also how DLEP works in an IPv4 environment=
.=0A=
>=0A=
>> If, however, someone has an approach that allows IPv4 only, and will get=
=0A=
>> through the IETF processes, then I would love to hear it.=0A=
>=0A=
> I am NOT saying that DLEP should be IPv4-only.  I am saying that=0A=
> there definitely exists legacy IPv4-only equipment that might=0A=
> support DLEP in the future, but is extremely unlikely ever to support=0A=
> IPv6.=0A=
>=0A=
> Assertions:=0A=
> =97=97=97=97=97=0A=
> DLEP routers want to be able to communicate with any DLEP modem.=0A=
> If a radio only supports IPv4, it can=92t hear an IPv6 anything.=0A=
> If a radio only supports IPv6, it can=92t hear an IPv4 anything.=0A=
> If a radio supports both IPv4 & IPv6, it will hear both IPv4 & IPv6.=0A=
>=0A=
> For example, this means that one tailors the recommendation to=0A=
> the operational deployment:=0A=
> 	- in a dual-stack operational deployment, the RECOMMENDATION=0A=
>            is to send DLEP Discovery messages twice, once with IPv4=0A=
>            link-local multicast AND again with IPv6 link-local multicast=
=0A=
> 	- in an IPv6-only operational deployment, the RECOMMENDATION=0A=
>            is to send DLEP Discovery messages only using IPv6 link-local=
=0A=
>            multicast.=0A=
> 	- in an IPv4-only operational deployment, the RECOMMENDATION=0A=
>            is to send DLEP Discovery messages using IPv4 link-local multi=
cast.=0A=
>=0A=
=0A=
You make a very good point about supporting equipment in IPv4 only =0A=
deployments as a valid target for IETF documents.  In light of that I am =
=0A=
in favour of updating the discovery text to something along the lines of =
=0A=
your suggestion.=0A=
=0A=
Rick=0A=
=0A=


From nobody Wed Nov 25 05:38:29 2015
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 165AB1B2C75 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:38:28 -0800 (PST)
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 HyiqMpDvoUJY for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:38:26 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74B1D1B2C74 for <manet@ietf.org>; Wed, 25 Nov 2015 05:38:26 -0800 (PST)
Received: by wmec201 with SMTP id c201so70509666wme.1 for <manet@ietf.org>; Wed, 25 Nov 2015 05:38:25 -0800 (PST)
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=04X/TA74jleUZD8V4UArVAIzPBfnq9kwGv4ShX5G2gE=; b=gfEZ/Q7frFpuheDTjsiqBrmzDM3xfas1fXTC/RLcKZrDNX398YyLqaFASyYAELIann 2E1M7iyje9Lcug+1p0Q4GTqL6RnexZKCyREkvhH6FgVSBdhorF0TaV5K2ZvuaY1NZDrG znIApdJdU/CACvpCazKs863t6rMOs6eQ/o+/TmbZrPBWqs+mNcBWeVxUh0mAKrwDb5Hy DQ8QWJ+3wOKVcK3iMF4WJkLh37rECnDB0LlgPeNpgESNZAM3MnJeO5n5Ufb15FPYvDxd 5Ls56UKstlNOwGIyCaJvv8SGfSAIF3hxD1uKJWCfkCXXloHSbowPGIrWo5nGso47ji/l 2L+g==
X-Received: by 10.194.104.5 with SMTP id ga5mr43643331wjb.155.1448458705008; Wed, 25 Nov 2015 05:38:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 25 Nov 2015 05:37:55 -0800 (PST)
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B08CA7@tss-server1.home.tropicalstormsoftware.com>
References: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com> <87wpt6to0h.wl-jch@pps.univ-paris-diderot.fr> <AD5BBEB7-5A04-4864-AB48-68FE1CE62FBE@gmail.com> <CAGnRvurRX8T9AUWk2WoubLoBJH_rOYNsg2rYs3k2kPJPvOeinw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08CA7@tss-server1.home.tropicalstormsoftware.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 25 Nov 2015 14:37:55 +0100
Message-ID: <CAGnRvuo0HYuHd+VYXKH3pnm81v4+CQ98p2XBtitJJyxrS9sSXA@mail.gmail.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/h5jprNywRjhcEOQ4_mASWbgGW4s>
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:38:28 -0000

On Wed, Nov 25, 2015 at 2:17 PM, Rick Taylor
<rick@tropicalstormsoftware.com> wrote:
> On 25/11/15 12:40, Henning Rogge wrote:
>> On Wed, Nov 25, 2015 at 11:22 AM, Christopher Dearlove
>> <christopher.dearlove@gmail.com> wrote:
>>> Unfortunately or fortunately, depending on your point of view, that's n=
ot how it works. "Base spec now, security later" isn't accepted. (One argum=
ent is about whether later ever arrives.) Separate documents, perhaps. But =
that will still hold up the base spec.
>>
>> Yes it does work... in a certain way.
>>
>> A "linklocal DLEP" can just point to the existing ways to secure a
>> link instead of modifying the protocol itself.
>>
>> something like:
>>
>>> Security Considerations (quick and dirty version):
>>> a) at best, use a dedicated plug on the router and a direct cable conne=
ction
>>> b) otherwise use a VLAN separation to keep the other traffic away from =
the user/control data to the radio
>
> The VLAN separation is actually required for the data plane anyway.

Yes... unless you have a dedicated ethernet card to connect to the radio.
>> the advantage of this is that NONE of these things make DLEP more
>> complex, they can be deployed independently.
>>
>> I would also suggest to add something like
>> "by default, the DLEP radio should use linklocal addresses for both
>> UDP and TCP socket. If an administrator changes this, the link MUST be
>> secured with one or multiple of the options mentioned in the Security
>> Considerations."
>
> +1, The hard part as I see it is crafting the words.
>
> Does anyone have any issue with what I see as emerging consensus around:
>
> 1) STRONGLY RECOMMENDING Link-local addresses and/or direct connection.
>
> 2) Referencing the various layer-2 security solutions for >1 hop
> deployments.

These are even useful for single-hop solutions if the deployment calls
for more security.

> 3) Removing the TLS requirement.
>
> Rick

Henning Rogge


From nobody Wed Nov 25 05:40:56 2015
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 642971B2C8E for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:40:55 -0800 (PST)
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 5IVEhD1UODno for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:40:54 -0800 (PST)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1200C1B2C78 for <manet@ietf.org>; Wed, 25 Nov 2015 05:40:54 -0800 (PST)
Received: by wmww144 with SMTP id w144so180543651wmw.1 for <manet@ietf.org>; Wed, 25 Nov 2015 05:40:52 -0800 (PST)
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=cRyr9bXVpS/zB/49y2HuSNYOa5WJar1wUGgsT2WBeaU=; b=f7nMrOUR5zu9IefM+KpUsH79laWT4V/pTNVgFX4BofaNwEr+M1Nwio8f/sqEveWOlp 1CYqteRBe5GfuQ/1W1KikAeoJn2o19tQ7MANTpSSdlIfrUDOHJvugx5OCUcUAjY0mpQi Ttd+RT1RknZA7cPCQ09y9PmokRW95MyHi4k+q3IL+BwqwKV4Ve31PddCZfS9wgMWMjmC k57YSVCBEhP5frM2N0lPpwtFOo4ZNWZXxFnFqH63nrg1iieu2HtqbPkso8QPCX7WLAag HB0FlKI4zU0UOmeukebVXCXnUyZjhyIhOnB+6nPJEA/+i3RooC6Diw3+clwMr4lWY+IK vfGg==
X-Received: by 10.28.68.213 with SMTP id r204mr4462299wma.35.1448458852726; Wed, 25 Nov 2015 05:40:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 25 Nov 2015 05:40:23 -0800 (PST)
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B08CFB@tss-server1.home.tropicalstormsoftware.com>
References: <4C2E2E59-68FB-45A8-A24F-4F8AC6E3D1EB@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04F12@tss-server1.home.tropicalstormsoftware.com> <23B3A59F-4A50-454E-8A5E-F8C3C7FD0E62@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08CFB@tss-server1.home.tropicalstormsoftware.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 25 Nov 2015 14:40:23 +0100
Message-ID: <CAGnRvurfq=8w+4Ub1Z7t3gpxzgWVSQsDo0-gQCH09NJ4Ne1k_Q@mail.gmail.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/R3it-UCLx1c6ps1cYhNvS_HUYno>
Cc: MANET IETF <manet@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [manet] DLEP-17: well-known IPv4 link-local multicast 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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:40:55 -0000

On Wed, Nov 25, 2015 at 2:22 PM, Rick Taylor
<rick@tropicalstormsoftware.com> wrote:
> We might have fallen into the trap of making assumptions about IANA
> here.  Personally I would prefer a link-local IPv4 multicast address.

To be fair, RFC5498 (RFC5444 IANA allocation) got 224.0.0.109... that
doesn't look like we are running out of multicast addresses any time
soon.

Henning Rogge


From nobody Wed Nov 25 05:45:24 2015
Return-Path: <rick@tropicalstormsoftware.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 859711B2C9E for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 hj4RAFOOVJLd for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:45:22 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFCA41B2C9D for <manet@ietf.org>; Wed, 25 Nov 2015 05:45:21 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Wed, 25 Nov 2015 13:44:57 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>
Thread-Topic: [manet] Linklocal DLEP
Thread-Index: AQHRJt7l9LrXpBvSJE2u010DeCngeA==
Date: Wed, 25 Nov 2015 13:44:56 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B08E23@tss-server1.home.tropicalstormsoftware.com>
References: <CAGnRvuoHkGcq9Dxo+g64EEokndpusjFf=sozPs74W_SfO2yHFA@mail.gmail.com> <87wpt6to0h.wl-jch@pps.univ-paris-diderot.fr> <AD5BBEB7-5A04-4864-AB48-68FE1CE62FBE@gmail.com> <CAGnRvurRX8T9AUWk2WoubLoBJH_rOYNsg2rYs3k2kPJPvOeinw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08CA7@tss-server1.home.tropicalstormsoftware.com> <CAGnRvuo0HYuHd+VYXKH3pnm81v4+CQ98p2XBtitJJyxrS9sSXA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/uBnf2zeddHLFB_5KbY0kkmeenbg>
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, MANET IETF <manet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [manet] Linklocal DLEP
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:45:23 -0000

On 25/11/15 13:38, Henning Rogge wrote:=0A=
> On Wed, Nov 25, 2015 at 2:17 PM, Rick Taylor=0A=
> <rick@tropicalstormsoftware.com> wrote:=0A=
>> On 25/11/15 12:40, Henning Rogge wrote:=0A=
>>> On Wed, Nov 25, 2015 at 11:22 AM, Christopher Dearlove=0A=
>>> <christopher.dearlove@gmail.com> wrote:=0A=
>>>> Unfortunately or fortunately, depending on your point of view, that's =
not how it works. "Base spec now, security later" isn't accepted. (One argu=
ment is about whether later ever arrives.) Separate documents, perhaps. But=
 that will still hold up the base spec.=0A=
>>>=0A=
>>> Yes it does work... in a certain way.=0A=
>>>=0A=
>>> A "linklocal DLEP" can just point to the existing ways to secure a=0A=
>>> link instead of modifying the protocol itself.=0A=
>>>=0A=
>>> something like:=0A=
>>>=0A=
>>>> Security Considerations (quick and dirty version):=0A=
>>>> a) at best, use a dedicated plug on the router and a direct cable conn=
ection=0A=
>>>> b) otherwise use a VLAN separation to keep the other traffic away from=
 the user/control data to the radio=0A=
>>=0A=
>> The VLAN separation is actually required for the data plane anyway.=0A=
>=0A=
> Yes... unless you have a dedicated ethernet card to connect to the radio.=
=0A=
=0A=
Of course.=0A=
=0A=
>>> the advantage of this is that NONE of these things make DLEP more=0A=
>>> complex, they can be deployed independently.=0A=
>>>=0A=
>>> I would also suggest to add something like=0A=
>>> "by default, the DLEP radio should use linklocal addresses for both=0A=
>>> UDP and TCP socket. If an administrator changes this, the link MUST be=
=0A=
>>> secured with one or multiple of the options mentioned in the Security=
=0A=
>>> Considerations."=0A=
>>=0A=
>> +1, The hard part as I see it is crafting the words.=0A=
>>=0A=
>> Does anyone have any issue with what I see as emerging consensus around:=
=0A=
>>=0A=
>> 1) STRONGLY RECOMMENDING Link-local addresses and/or direct connection.=
=0A=
>>=0A=
>> 2) Referencing the various layer-2 security solutions for >1 hop=0A=
>> deployments.=0A=
>=0A=
> These are even useful for single-hop solutions if the deployment calls=0A=
> for more security.=0A=
=0A=
Okay, agreed, so we could reference layer-2 security measures (802.1x =0A=
etc) for all link types.=0A=
=0A=
Rick=0A=


From nobody Wed Nov 25 05:46:44 2015
Return-Path: <rick@tropicalstormsoftware.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 8F7181B2CA0 for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, 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 7r0w-_DZfYDQ for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:46:42 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EA0D1B2C74 for <manet@ietf.org>; Wed, 25 Nov 2015 05:46:42 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Wed, 25 Nov 2015 13:46:16 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>
Thread-Topic: [manet] DLEP-17: well-known IPv4 link-local multicast address
Thread-Index: AQHRJ4bnXpveXaMsBkSciQJdtQHUFQ==
Date: Wed, 25 Nov 2015 13:46:15 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801A8B08E36@tss-server1.home.tropicalstormsoftware.com>
References: <4C2E2E59-68FB-45A8-A24F-4F8AC6E3D1EB@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04F12@tss-server1.home.tropicalstormsoftware.com> <23B3A59F-4A50-454E-8A5E-F8C3C7FD0E62@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08CFB@tss-server1.home.tropicalstormsoftware.com> <CAGnRvurfq=8w+4Ub1Z7t3gpxzgWVSQsDo0-gQCH09NJ4Ne1k_Q@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/FMZFSf6Y_na22g9BAH45ZKUc2uw>
Cc: MANET IETF <manet@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [manet] DLEP-17: well-known IPv4 link-local multicast 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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:46:43 -0000

On 25/11/15 13:40, Henning Rogge wrote:=0A=
> On Wed, Nov 25, 2015 at 2:22 PM, Rick Taylor=0A=
> <rick@tropicalstormsoftware.com> wrote:=0A=
>> We might have fallen into the trap of making assumptions about IANA=0A=
>> here.  Personally I would prefer a link-local IPv4 multicast address.=0A=
>=0A=
> To be fair, RFC5498 (RFC5444 IANA allocation) got 224.0.0.109... that=0A=
> doesn't look like we are running out of multicast addresses any time=0A=
> soon.=0A=
>=0A=
=0A=
That's a good observation Henning.  Does anyone remember RFC5444 getting =
=0A=
any negative feedback about the use of IPv4 link-local multicast?=0A=
=0A=
Rick=0A=


From nobody Wed Nov 25 05:56:03 2015
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 EBBD91B2CAF for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:56:01 -0800 (PST)
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 09YBVXlH29_b for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 05:56:01 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B72AD1A6F7F for <manet@ietf.org>; Wed, 25 Nov 2015 05:56:00 -0800 (PST)
Received: by wmvv187 with SMTP id v187so258211659wmv.1 for <manet@ietf.org>; Wed, 25 Nov 2015 05:55:59 -0800 (PST)
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=Vp7y4O1ydTxinpGWuOw3HAjTBM+NYdYP8xk+13l6ZRM=; b=fM+elV9aCZqs7BMoJvRNp/xWPXS48YwslxHNA8xjYWdR3pXS8XXBLmGAA6+OdDwtR6 0B1I1pmltw7BLrcaNtJZ8Tps332g4GA+ib7R7WogtevYUFH8Egnr8WymYAS2yy6wroXc s8dO2rZwE3W88gCpj13m3YrRohoUIumuupefGWK5eKfV9o2q8PKaejHiEnlLRVR6xZaE M2pgOxhclDwDONLd0b6HaJx41OAgAY9/ttlChc6bz805jTKcOCoy+5ccSdq4xFtwXWmv vRI/+ozJ8GXQpLwLYMO4P8L/Aen+vtgKPB0tIF3oRN3BwfESUfN5eQAO921LQd0Dz2CX ta3g==
X-Received: by 10.28.68.213 with SMTP id r204mr4542346wma.35.1448459759358; Wed, 25 Nov 2015 05:55:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 25 Nov 2015 05:55:29 -0800 (PST)
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801A8B08E36@tss-server1.home.tropicalstormsoftware.com>
References: <4C2E2E59-68FB-45A8-A24F-4F8AC6E3D1EB@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04F12@tss-server1.home.tropicalstormsoftware.com> <23B3A59F-4A50-454E-8A5E-F8C3C7FD0E62@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08CFB@tss-server1.home.tropicalstormsoftware.com> <CAGnRvurfq=8w+4Ub1Z7t3gpxzgWVSQsDo0-gQCH09NJ4Ne1k_Q@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08E36@tss-server1.home.tropicalstormsoftware.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 25 Nov 2015 14:55:29 +0100
Message-ID: <CAGnRvupdHtcTvCBoPiU3O8sS2WCYds-cv+e=kGERws7MVO2syw@mail.gmail.com>
To: Rick Taylor <rick@tropicalstormsoftware.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/KNrsRl0sZRZgpL69DaJitof9lak>
Cc: MANET IETF <manet@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [manet] DLEP-17: well-known IPv4 link-local multicast 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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 13:56:02 -0000

On Wed, Nov 25, 2015 at 2:46 PM, Rick Taylor
<rick@tropicalstormsoftware.com> wrote:
> That's a good observation Henning.  Does anyone remember RFC5444 getting
> any negative feedback about the use of IPv4 link-local multicast?

Using real multicast addresses is a bit more tricky in C because the
"default API" is... ... ... lets say it is not straightforward to use.

But everything else is fine as far as I know.

Henning Rogge


From nobody Wed Nov 25 07:28:57 2015
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 6E9021B2E1B for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 07:28:55 -0800 (PST)
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 McfCucIzGtyW for <manet@ietfa.amsl.com>; Wed, 25 Nov 2015 07:28:54 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 184AA1B2DF7 for <manet@ietf.org>; Wed, 25 Nov 2015 07:28:51 -0800 (PST)
Received: by wmww144 with SMTP id w144so73966429wmw.0 for <manet@ietf.org>; Wed, 25 Nov 2015 07:28:49 -0800 (PST)
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=9xr0Lgmxk2wJVgrm1nXD7eyu8HMcz2b07wCFDmj6bXs=; b=OrejhftEOGARJ3zkJLMPjIXzlnz1guBqxgcsgQdtHJrq4Vn4DAOJWVnJtMpC+7EB35 tSJzxHIj3lChxL+eMTSdzr/Td99pv5xAuHyuPV7Z3yg9mY/PuK6tfQjSg5UYGvS2XLW7 Voj4ycuVqFnNKJ73ETpqCDjYJzZqtFSseTxniIQ5IAr47k9KoUb8tzf7y6T1DVBqO5h9 D0wLtGMUXdNGnr1o3hzMTeWDMnNf7OeX2yGLmNe4beFz8zlXQwFihADoIxs8nUTPTQs+ +2o0TqZK+udtOal5hyXd1Une2+xByF0U1aBwjSJ0/YXOs+fY+eIvlp2AkXr6+CRzTck6 RINQ==
X-Received: by 10.194.95.65 with SMTP id di1mr42174747wjb.134.1448465329765; Wed, 25 Nov 2015 07:28:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 25 Nov 2015 07:28:20 -0800 (PST)
In-Reply-To: <C4E4091E-2D4C-4E2A-83EC-9967157F9A6F@mnemosyne.demon.co.uk>
References: <4C2E2E59-68FB-45A8-A24F-4F8AC6E3D1EB@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B04F12@tss-server1.home.tropicalstormsoftware.com> <23B3A59F-4A50-454E-8A5E-F8C3C7FD0E62@gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08CFB@tss-server1.home.tropicalstormsoftware.com> <CAGnRvurfq=8w+4Ub1Z7t3gpxzgWVSQsDo0-gQCH09NJ4Ne1k_Q@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801A8B08E36@tss-server1.home.tropicalstormsoftware.com> <C4E4091E-2D4C-4E2A-83EC-9967157F9A6F@mnemosyne.demon.co.uk>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 25 Nov 2015 16:28:20 +0100
Message-ID: <CAGnRvur0dQ3JX4ACMZvZqGNd6H0njydjBDJwTCe2eYcNweLUuQ@mail.gmail.com>
To: Christopher Dearlove <chris@mnemosyne.demon.co.uk>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/s8RQNcZQfbVA7nTbnINrhj3c2yw>
Cc: MANET IETF <manet@ietf.org>, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [manet] DLEP-17: well-known IPv4 link-local multicast 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: <https://mailarchive.ietf.org/arch/browse/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, 25 Nov 2015 15:28:55 -0000

On Wed, Nov 25, 2015 at 4:26 PM, Christopher Dearlove
<chris@mnemosyne.demon.co.uk> wrote:
> Of course it wouldn't have been 5444 that got the feedback on an allocation, but 5498. But 5444 didn't get any feedback, and I'm reasonably sure 5498 didn't, though I wasn't an author of the latter.
>
> (What surprised me was that 5498 got an IP protocol allocation, one of only 256.)

Yes... the IP protocol allocation was a big surprise.

I think someone liked the idea of having a common protocol
format/framework for mesh networks.

Henning Rogge


From nobody Mon Nov 30 03:16:49 2015
Return-Path: <akinpense2@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 0B4FC1A9100 for <manet@ietfa.amsl.com>; Mon, 30 Nov 2015 03:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.351
X-Spam-Level: **
X-Spam-Status: No, score=2.351 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, J_CHICKENPOX_47=0.6, J_CHICKENPOX_52=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 u9-4tRIUjywK for <manet@ietfa.amsl.com>; Mon, 30 Nov 2015 03:16:44 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1269A1A90FA for <manet@ietf.org>; Mon, 30 Nov 2015 03:16:44 -0800 (PST)
Received: by wmec201 with SMTP id c201so133229957wme.1 for <manet@ietf.org>; Mon, 30 Nov 2015 03:16:42 -0800 (PST)
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=ENBbqICRYiM/jH2Xw7mcVvjis5soue0e5SyaWPYKgBo=; b=0OwmFK67rxI8L8IxKqsjkfq5lNAwUwDmJN4ZXOX5acYeT5ix8xy6BEwgHc3FFSM9ov CwZaMjkY/7XD1Q+7H5cggRFKOZVnlkqCNm6+F9nyVQ6CSYYLXS4QgIiRn8I7uJP19yxX 40AGjCtrYwNVqNRf6NjlaXsHaMBvYQT0D7cT+t8HwD7TiGrk87s4regPKmYX46hidt1a ox5Lsc+4pgn3e5Ivyj2KJlTUUQ/tvYQZEkY32Euu8qyAuZNiopgQLDSFCM4a4ehtAjo7 lBmIxXnzO01JC4F895abZBFXvQU8Sle3tYLCr4Mu37Q//O73Myd/u61Rjm8u+D/BKs8f v7Nw==
MIME-Version: 1.0
X-Received: by 10.194.87.39 with SMTP id u7mr72585533wjz.11.1448882202581; Mon, 30 Nov 2015 03:16:42 -0800 (PST)
Received: by 10.194.200.69 with HTTP; Mon, 30 Nov 2015 03:16:42 -0800 (PST)
In-Reply-To: <CAAePS4BVMBHyETCoo1NzHVaGSkdqgTfOciZ_6vwRNxDDTRiFZQ@mail.gmail.com>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com> <CAAePS4BVMBHyETCoo1NzHVaGSkdqgTfOciZ_6vwRNxDDTRiFZQ@mail.gmail.com>
Date: Mon, 30 Nov 2015 03:16:42 -0800
Message-ID: <CACjBtK1KrmQHO8RdQ2ygzG4QA+fLeqkjTVpm_c+==Wqhp=spbA@mail.gmail.com>
From: Awokoya Emma <akinpense2@gmail.com>
To: Victoria Mercieca <vmercieca0@gmail.com>
Content-Type: multipart/alternative; boundary=089e0102def401a0fb0525c02dc6
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/AITiOQY0MyfIQ-IQoBeiUOLoi8M>
Cc: manet <manet@ietf.org>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Nov 2015 11:16:48 -0000

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

Update has being noted. Thank you Christopher and Thomas. Victoria you did
a good job in explaining their comments.  But your comment "But there was a
suggestion that this issue might be seen so infrequently in practise that
the overhead required to avoid this issue is not worth it (i.e. the extra
control traffic of acknowledging every link in every route ever requested,
even when some links are already known to be bidirectional" that might not
be the case especially with dynamic hoping.

On Mon, Nov 23, 2015 at 8:59 AM, Victoria Mercieca <vmercieca0@gmail.com>
wrote:

> Hi again,
>
> Regarding the comments on bidirectionality and acks, from Thomas Clausen'=
s
> email...specifically:
> * "Also on buffering, I am wondering if the "start delivering buffered
> packets" conditions (penultimate paragraph in 6.6, and of course through
> the processing sections) is sufficient; I suspect that the condition "Whe=
n
> a valid route is installed" is not sufficient - that there are situations
> where a routing table entry is installed, but the complete route is not
> available or is not bidirectional?This obviously is related to RREP_Ack
> being hop-by-hop and not end-to-end....*"
>
>
> Thomas is right about hop-by-hop RREP_Ack. For intermediate nodes who
> install a route to OrigAddr based on a one-hop RREP_Ack from their next h=
op
> toward OrigAddr, it's not guaranteed that the complete route to OrigAddr =
is
> available. Since the route is valid, the router may start forwarding data
> packets to OrigAddr. An issue occurs if data packets are forwarded to
> intermediate routers before the intermediate router installs a valid rout=
e.
> If this happened, those data packets would be dropped and RERRs generated
> (and regenerated toward the source of the data packets by any router usin=
g
> it), and the route to OrigAddr would be removed at some but maybe not all
> of the routers that installed it. A new RREQ would then have to go out on
> behalf of the source of the traffic. So this problem would eventually fix
> itself....but not without some dropped packets, RERRs, and a new RREQ/RRE=
P
> cycle. But there was a suggestion that this issue might be seen so
> infrequently in practise that the overhead required to avoid this issue i=
s
> not worth it (i.e. the extra control traffic of acknowledging every link =
in
> every route ever requested, even when some links are already known to be
> bidirectional).
>
> If you disagree, then we need to make RREP_Ack end-to-end and accept the
> fact that this will result in many more RREP_Ack messages being generated
> than in the current version.
>
> Kind regards,
> Victoria.
>
> On Thu, Nov 19, 2015 at 4:09 PM, Victoria Mercieca <vmercieca0@gmail.com>
> wrote:
>
>>
>> Hi Thomas and Christopher,
>>
>> Thank you for your comments.  If I may address just one point for
>> starters - regeneration vs forwarding. We use the term regeneration sinc=
e
>> forwarding seems inappropriate when the message content changes at each =
hop.
>>
>> The changes we make to the message content are:
>>
>> 1) We change the metric so that each router along the path learns a rout=
e
>> from the message, with the metric associated with the path up to that po=
int
>> 2) AckReq only applies between hops, so needs to be removed at each hop,
>> and a new AckReq element may need to be added for the next hop.
>> 3) ValidityTime could potentially be added by any intermediate router
>> that wishes to limit the time it will forward packets on the route.
>> 4) Stripping out Unreachable Addresses from RERR which did not affect ou=
r
>> route set.
>>
>> Can we really use the term "forwarding" if we are changing the metric
>> value, adding a validity time, adding/removing AckReq or removing addres=
ses
>> and their associated TLVs?
>>
>> Further, in reply to the comment about use of the msg-hop-count and
>> msg-hop-limit fields, I think it does not matter that a message only
>> travels one hop in that particular form, with that exact set of informat=
ion
>> enclosed. Hop limit and hop count are part of the message and used by th=
e
>> routing protocol, and so they refer to the multi-hop path that the AODVv=
2
>> message will follow, indicating when not to regenerate any further. So
>> AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit th=
e
>> number of hops across which it will regenerate a packet so as to "preven=
t
>> messages from endlessly circulating in a MANET".
>>
>> Kind regards,
>> Victoria.
>>
>> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <
>> christopher.dearlove@gmail.com> wrote:
>>
>>> I've not had time to look at either yet, though I hope to review DLEP
>>> very soon.
>>>
>>> But this has made me think about the RFC 6621 reference in AODVv2. It's
>>> always been clear this has been rather a throwaway comment that needed
>>> thought, but until now I hadn't really given it any.
>>>
>>> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's
>>> consider each on turn.
>>>
>>> AODVv2 is in the RFC 5444 structure. As has been noted on many
>>> occasions, AOVDVv2 gets to use messages, but packets are not in its
>>> competence.
>>>
>>> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets=
.
>>> It's about whether or not to forward them. But RFC 5444 packets aren't =
just
>>> not forwarded in unchanged IP packets, they aren't even forwarded at al=
l.
>>> They are each a single hop construct, and if a message is forwarded (wh=
ich
>>> is by the routing protocol, as far as RFC 5444 is concerned, it's a new
>>> message) it will be in a new packet, with possibly new companions.
>>>
>>> If AODVv2 wants to use a more efficient flooding process, it needs one
>>> at the message level. Now an example of that exists - the mechanism on =
RFC
>>> 7181. Unfortunately we didn't break that out as a separate draft (we wo=
uld
>>> have liked to, but there were reasons we didn't).
>>>
>>> And even if (by reference or other means) it were used - or some relate=
d
>>> mechanism such as a CDS - that processing/forwarding mechanism assumes =
you
>>> have defined MPRs (or similarly, that you have defined a CDS). And that
>>> needs a local exchange of information, such as NHDP's HELLO messages (a=
nd
>>> the rest of NHDP) augmented with RFC 7181's MPR TLV (though only the
>>> flooding bit is needed).
>>>
>>> In other words, taking some real work to define. And also raising a
>>> question for the WG - why do we want a reactive protocol? The main
>>> attraction as I see it is the "if you're not doing anything, you're not
>>> transmitting" property. Which adding this voids. Of course maybe the WG
>>> doesn't value that. Or it is acceptable as an option. But if so it need=
s to
>>> be an option that all routers use, or none. And if all, compatibly. (MP=
R
>>> flooding allows different MPR selection algorithms - but only as long a=
s
>>> they satisfy the fundamental MPR algorithm properties.)
>>>
>>> In short, RFC 6621 must go. The alternative is nothing, or significant
>>> work.
>>>
>>> --
>>> Christopher Dearlove
>>> christopher.dearlove@gmail.com (iPhone)
>>> chris@mnemosyne.demon.co.uk (home)
>>>
>>> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote=
:
>>>
>>> Dear all,
>>>
>>> I have started looking through the recently
>>> updated draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not=
 to
>>> have had a blow-by-bow comeback to the previous review comments  - woul=
d
>>> have made it a somewhat easier task to check if all have been addressed=
 or
>>> not.
>>>
>>> But, I will work through it and produce a detailed review - but from my
>>> first quick read-through there're a couple of issue that jumped at me a=
s
>>> worth bringing forward on a more global level already.
>>>
>>> The first relates to  how RREQs are forwarded -- or, more generally, ar=
e
>>> not.
>>>
>>> The protocol currently talks about "message is regenerated" rather than
>>> "forwarded". I have understood that this means that a RREQ is actually =
not
>>> an "end to end" entity, but is a "hop by hop" entity.
>>>
>>> First, that is a curious design choice, is there any reason why this is
>>> so considered?
>>>
>>> Second, if a RREQ message is hop-by-hop only, then I do not think that
>>> the use of the RFC5444 hop-limit/hop-count fields is appropriate.
>>>
>>> Third, the statement in section 6.5 on the use of RFC6621 is incorrect
>>> in two ways: RFC6621 does specify how messages are *forwarded* (but, as
>>> discussed above, you are not forwarding messages).
>>>
>>> More seriously, this paragraph is incorrect:
>>>
>>>
>>> "Implementations MAY choose to employ techniques to reduce the number
>>>    of multicast messages sent.  Use of [RFC6621 <https://tools.ietf.org=
/html/rfc6621>] in deployments is
>>>    recommended.  Employing [RFC6621 <https://tools.ietf.org/html/rfc662=
1>] in a subset of the operational
>>>    AODVv2 routers in a network, or configuring different algorithms on
>>>    different routers, will not cause interoperability issues, but will
>>>    reduce the effectiveness of the multicast reduction scheme."
>>>
>>>
>>> Different routers using different relay selection algorithms in the sam=
e
>>> network will not *just* cause loss of efficiency, but *will* cause
>>> interoperability issues.
>>>
>>> For example if "router A" decides to suppress its message relaying
>>> because it estimates that "router B" provides sufficient coverage - and
>>> conversely "router B" suppresses relaying for the same reason: neither =
A
>>> nor B would relay, and so any routers reachable only via A and B would =
not
>>> be covered.
>>>
>>> This is not a far-sought example: it can be as simple as A and B simply
>>> using self-selecting relay algorithms with different tie-breakers.
>>>
>>> In short: I think that the whole message flooding/regeneration part
>>> requires serious work.
>>>
>>> The second issue is that I also suspect that there is some issue with
>>> buffering, or rather with how it is specified; starting in section 6.6,=
 I
>>> am not sure that leaving that as "a matter of policy at each router" is
>>> entirely right.
>>>
>>> Also on buffering, I am wondering if the "start delivering buffered
>>> packets" conditions (penultimate paragraph in 6.6, and of course throug=
h
>>> the processing sections) is sufficient; I suspect that the condition "W=
hen
>>> a valid route is installed" is not sufficient - that there are situatio=
ns
>>> where a routing table entry is installed, but the complete route is not
>>> available or is not bidirectional?This obviously is related to RREP_Ack
>>> being hop-by-hop and not end-to-end....
>>>
>>> Either way, the parts of the specification that relate to buffering
>>> contain a mixture of normative and non-normative verbiage (a lot of "ca=
n"
>>> but also a lot of MUST/SHOULD) which I think could do with a tightening=
 up.
>>>
>>> But....is buffering even something that should be specified by this
>>> document? It does not impact interoperability and it interferes
>>> substantially with transport and congestion control, and I am not sure =
that
>>> we understand the consequences (I am not convinced that the claims in t=
he
>>> document on benefits to TCP are substantiated or even true).
>>>
>>> As I indicated, a complete review will follow, but I thought that these
>>> was a global enough topics to call out and get engineered right.
>>>
>>> Thomas
>>>
>>> PS: I remain convinced that the security considerations section is
>>> insufficient ; I will try to articulate my thoughts on why that is, but=
 for
>>> starters looking at the recently raised (by somebody else, the Chris
>>> replied) AODV security questions would probably be helpful
>>>
>>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote=
:
>>>
>>> Hello WG participants =E2=80=93
>>>
>>>
>>>
>>> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct.
>>> 16 (DLEP). The co-authors and the chairs ask that you please take some =
time
>>> to review and comment on the new submissions.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Stan
>>>
>>>
>>>
>>>
>>>
>>> _____________________________________________________
>>> This electronic message and any files transmitted with it contains
>>> information from iDirect, which may be privileged, proprietary
>>> and/or confidential. It is intended solely for the use of the individua=
l
>>> or entity to whom they are addressed. If you are not the original
>>> recipient or the person responsible for delivering the email to the
>>> intended recipient, be advised that you have received this email
>>> in error, and that any use, dissemination, forwarding, printing, or
>>> copying of this email is strictly prohibited. If you received this emai=
l
>>> in error, please delete it and immediately notify the sender.
>>> _____________________________________________________
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>> _______________________________________________
>>> 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
>
>


--=20

Kind Regards,

*Akin-Awokoya Emmanuel*

Data/Telecommication Network Engineer and Web/Content Developer

Member IEEE, NSE, ISOC, CTO, DSA, ICANN



*Interested in volunterism, project research*

*Startups, opendatamining, open data research*

*TVWhitespace technology*



I can be on the next boat, next ship, next plane, next bus as long as where
I am going I could

help someone have a better access and create local contents on the Internet=
.



*Twitter:@pensebien <https://twitter.com/penseBien>*

*Facebook:* emma.awokoya

*Linkedin: EmmaAwokoya <https://ng.linkedin.com/in/emmaawokoya>*

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

<div dir=3D"ltr">Update has being noted. Thank you Christopher and Thomas. =
Victoria you did a good job in explaining their comments.=C2=A0<span style=
=3D"font-size:12.8px">=C2=A0But your comment &quot;But there was a suggesti=
on that this issue might be seen so infrequently in practise that the overh=
ead required to avoid this issue is not worth it (i.e. the extra control tr=
affic of acknowledging every link in every route ever requested, even when =
some links are already known to be bidirectional&quot; that might not be th=
e case especially with dynamic hoping.</span></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Mon, Nov 23, 2015 at 8:59 AM, Victoria=
 Mercieca <span dir=3D"ltr">&lt;<a href=3D"mailto:vmercieca0@gmail.com" tar=
get=3D"_blank">vmercieca0@gmail.com</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div dir=3D"ltr">Hi again,<br><br>Regarding the comments o=
n bidirectionality and acks, from Thomas Clausen&#39;s
        email...specifically:<span class=3D""><i><br>
          &quot;<span>Also on buffering, I am wondering if the &quot;start
            delivering buffered packets&quot; conditions (penultimate
            paragraph in 6.6, and of course through the processing
            sections) is sufficient; I suspect that the condition &quot;Whe=
n
            a valid route is installed&quot; is not sufficient - that there
            are situations where a routing table entry is installed, but
            the complete route is not available or is not
            bidirectional?This obviously is related to RREP_Ack being
            hop-by-hop and not end-to-end....</span></i>&quot;<br><div><i>
              <br></i></div></span><div><br>Thomas is right about hop-by-ho=
p RREP_Ack. For intermediate nodes who install a route to OrigAddr based on=
 a one-hop RREP_Ack from their next hop toward OrigAddr, it&#39;s not guara=
nteed that the complete route to OrigAddr is available. Since the route is =
valid, the router may start forwarding data packets to OrigAddr. An issue o=
ccurs if data packets
            are forwarded to intermediate routers before the
            intermediate router installs a valid route. If this happened, t=
hose data packets would be dropped and RERRs generated (and regenerated tow=
ard the source of the data packets by any router using it), and the route t=
o OrigAddr would be removed at some but maybe not all of the routers that i=
nstalled it. A new RREQ would then
            have to go out on behalf of the source of the traffic. So
            this problem would eventually fix itself....but not without
some dropped packets, RERRs, and a new RREQ/RREP cycle. But there was a sug=
gestion that this
            issue might be seen so infrequently in practise that the
overhead required to avoid this issue is not worth it (i.e. the extra contr=
ol traffic of acknowledging every link in every route ever requested, even =
when some links are already known to be bidirectional).<br><br></div><div>I=
f you disagree, then we need to make RREP_Ack end-to-end and accept the fac=
t that this will result in many more RREP_Ack messages being generated than=
 in the current version.<br></div><div><br></div><div>Kind regards,<br></di=
v><div>Victoria.<br></div></div><div class=3D"HOEnZb"><div class=3D"h5"><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Nov 19, 2015=
 at 4:09 PM, Victoria Mercieca <span dir=3D"ltr">&lt;<a href=3D"mailto:vmer=
cieca0@gmail.com" target=3D"_blank">vmercieca0@gmail.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div><div><div dir=3D"ltr"><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr"><p dir=3D"ltr">Hi Thomas and Christop=
her,</p>
<p dir=3D"ltr">Thank you for your comments.=C2=A0 If I may address just one=
=20
point for starters - regeneration vs forwarding. We use the term=20
regeneration since forwarding seems inappropriate when the message=20
content changes at each hop.</p>
<p dir=3D"ltr">The changes we make to the message content are:</p>
<p dir=3D"ltr">1) We change the metric so that each router along the path=
=20
learns a route from the message, with the metric associated with the=20
path up to that point<br>
2) AckReq only applies between hops, so needs to be removed at each hop,
 and a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router=20
that wishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our r=
oute set.</p>
<p dir=3D"ltr">Can we really use the term &quot;forwarding&quot; if we are =
changing=20
the metric value, adding a validity time, adding/removing AckReq or=20
removing addresses and their associated TLVs?</p>
<p dir=3D"ltr">Further, in reply to the comment about use of the=20
msg-hop-count and msg-hop-limit fields, I think it does not matter that a
=20
message only travels one hop in that particular form, with that exact=20
set of information enclosed. Hop limit and hop count are part of the=20
message=20
and used by the routing protocol, and so they=20
refer to the multi-hop path that the AODVv2 message will follow,=20
indicating when not to regenerate any further. So=20
AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit=20
the number of hops across which it will regenerate a packet so as to=20
&quot;prevent messages from endlessly circulating in a MANET&quot;. </p>
<p dir=3D"ltr">Kind regards,<br>
Victoria.</p></div><div><div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <span dir=
=3D"ltr">&lt;<a href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_b=
lank">christopher.dearlove@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div dir=3D"auto"><div>I&#39;ve not had time to look at e=
ither yet, though I hope to review DLEP very soon.</div><div><br></div><div=
>But this has made me think about the RFC 6621 reference in AODVv2. It&#39;=
s always been clear this has been rather a throwaway comment that needed th=
ought, but until now I hadn&#39;t really given it any.</div><div><br></div>=
<div>And it doesn&#39;t work. RFC 6621 is fundamentally unusable here. Let&=
#39;s consider each on turn.=C2=A0</div><div><br></div><div>AODVv2 is in th=
e RFC 5444 structure. As has been noted on many occasions, AOVDVv2 gets to =
use messages, but packets are not in its competence.</div><div><br></div><d=
iv>RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.=
 It&#39;s about whether or not to forward them. But RFC 5444 packets aren&#=
39;t just not forwarded in unchanged IP packets, they aren&#39;t even forwa=
rded at all. They are each a single hop construct, and if a message is forw=
arded (which is by the routing protocol, as far as RFC 5444 is concerned, i=
t&#39;s a new message) it will be in a new packet, with possibly new compan=
ions.</div><div><br></div><div>If AODVv2 wants to use a more efficient floo=
ding process, it needs one at the message level. Now an example of that exi=
sts - the mechanism on RFC 7181. Unfortunately we didn&#39;t break that out=
 as a separate draft (we would have liked to, but there were reasons we did=
n&#39;t).</div><div><br></div><div>And even if (by reference or other means=
) it were used - or some related mechanism such as a CDS - that processing/=
forwarding mechanism assumes you have defined MPRs (or similarly, that you =
have defined a CDS). And that needs a local exchange of information, such a=
s NHDP&#39;s HELLO messages (and the rest of NHDP) augmented with RFC 7181&=
#39;s MPR TLV (though only the flooding bit is needed).</div><div><br></div=
><div>In other words, taking some real work to define. And also raising a q=
uestion for the WG - why do we want a reactive protocol? The main attractio=
n as I see it is the &quot;if you&#39;re not doing anything, you&#39;re not=
 transmitting&quot; property. Which adding this voids. Of course maybe the =
WG doesn&#39;t value that. Or it is acceptable as an option. But if so it n=
eeds to be an option that all routers use, or none. And if all, compatibly.=
 (MPR flooding allows different MPR selection algorithms - but only as long=
 as they satisfy the fundamental MPR algorithm properties.)</div><div><br><=
/div><div>In short, RFC 6621 must go. The alternative is nothing, or signif=
icant work.<br><br><div>-- =C2=A0<span><font color=3D"#888888"><div>Christo=
pher Dearlove</div><div><a href=3D"mailto:christopher.dearlove@gmail.com" t=
arget=3D"_blank">christopher.dearlove@gmail.com</a> (iPhone)</div><div><a h=
ref=3D"mailto:chris@mnemosyne.demon.co.uk" target=3D"_blank">chris@mnemosyn=
e.demon.co.uk</a> (home)</div></font></span></div></div><div><div><div><br>=
On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a href=3D"mailto:ietf@thomasc=
lausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt; wrote:<br><br>=
</div><blockquote type=3D"cite"><div>
<div>Dear all,</div><div><br></div><div>I have started looking through the =
recently updated=C2=A0draft-ietf-manet-aodvv2-12. A lot has changed, and I =
regret not to have had a blow-by-bow comeback to the previous review commen=
ts =C2=A0- would have made it a somewhat easier task to check if all have b=
een addressed or not.</div><div><br></div><div>But, I will work through it =
and produce a detailed review - but from my first quick read-through there&=
#39;re a couple of issue that jumped at me as worth bringing forward on a m=
ore global level already.</div><div><br></div><div>The first relates to =C2=
=A0how RREQs are forwarded -- or, more generally, are not.</div><div><br></=
div><div>The protocol currently talks about &quot;message is regenerated&qu=
ot; rather than &quot;forwarded&quot;. I have understood that this means th=
at a RREQ is actually not an &quot;end to end&quot; entity, but is a &quot;=
hop by hop&quot; entity.=C2=A0</div><div><br></div><div>First, that is a cu=
rious design choice, is there any reason why this is so considered?</div><d=
iv><br></div><div>Second, if a RREQ message is hop-by-hop only, then I do n=
ot think that the use of the RFC5444 hop-limit/hop-count fields is appropri=
ate.</div><div><br></div><div>Third, the statement in section 6.5 on the us=
e of RFC6621 is incorrect in two ways: RFC6621 does specify how messages ar=
e *forwarded* (but, as discussed above, you are not forwarding messages).</=
div><div><br></div><div>More seriously, this paragraph <span style=3D"backg=
round-color:rgba(255,255,255,0)">is incorrect</span>:</div><div><pre style=
=3D"margin-top:0px;margin-bottom:0px"><font face=3D"UICTFontTextStyleTallBo=
dy"><span style=3D"white-space:normal;background-color:rgba(255,255,255,0)"=
><br></span></font></pre><pre style=3D"margin-top:0px;margin-bottom:0px"><b=
lockquote type=3D"cite"><font face=3D"UICTFontTextStyleTallBody"><span styl=
e=3D"white-space:normal;background-color:rgba(255,255,255,0)">&quot;Impleme=
ntations MAY choose to employ techniques to reduce the number
   of multicast messages sent.  Use of [<a href=3D"https://tools.ietf.org/h=
tml/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;" target=
=3D"_blank">RFC6621</a>] in deployments is
   recommended.  Employing [<a href=3D"https://tools.ietf.org/html/rfc6621"=
 title=3D"&quot;Simplified Multicast Forwarding&quot;" target=3D"_blank">RF=
C6621</a>] in a subset of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction scheme.&quot;</span>=
</font><span style=3D"font-size:19px">
</span></blockquote></pre></div><div><br></div><div>Different routers using=
 different relay selection algorithms in the same network will not *just* c=
ause loss of efficiency, but *will* cause interoperability issues.</div><di=
v><br></div><div>For example if &quot;router A&quot; decides to suppress it=
s message relaying because it estimates that &quot;router B&quot; provides =
sufficient coverage - and conversely &quot;router B&quot; suppresses relayi=
ng for the same reason: neither A nor B would relay, and so any routers rea=
chable only via A and B would not be covered.</div><div><br></div><div>This=
 is not a far-sought example: it can be as simple as A and B simply using s=
elf-selecting relay algorithms with different tie-breakers.</div><div><br><=
/div><div>In short: I think that the whole message flooding/regeneration pa=
rt requires serious work.</div><div><br></div><div><div><span style=3D"back=
ground-color:rgba(255,255,255,0)">The second issue is that I also suspect t=
hat there is some issue with buffering, or rather with how it is specified;=
 starting in section 6.6, I am not sure that leaving that as &quot;a matter=
 of policy at each router&quot; is entirely right.=C2=A0</span></div><div><=
span style=3D"background-color:rgba(255,255,255,0)"><br></span></div><div><=
span style=3D"background-color:rgba(255,255,255,0)">Also on buffering, I am=
 wondering if the &quot;start delivering buffered packets&quot; conditions =
(penultimate paragraph in 6.6, and of course through the processing section=
s) is sufficient; I suspect that the condition &quot;When a valid route is =
installed&quot; is not sufficient - that there are situations where a routi=
ng table entry is installed, but the complete route is not available or is =
not bidirectional?This obviously is related to RREP_Ack being hop-by-hop an=
d not end-to-end....</span></div><div><span style=3D"background-color:rgba(=
255,255,255,0)"><br></span></div><div><span style=3D"background-color:rgba(=
255,255,255,0)">Either way, the parts of the specification that relate to b=
uffering contain a mixture of normative and non-normative verbiage (a lot o=
f &quot;can&quot; but also a lot of MUST/SHOULD) which I think could do wit=
h a tightening up.=C2=A0</span></div><div><span style=3D"background-color:r=
gba(255,255,255,0)"><br></span></div><div><span style=3D"background-color:r=
gba(255,255,255,0)">But....is buffering even something that should be speci=
fied by this document? It does not impact interoperability and it interfere=
s substantially with transport and congestion control, and I am not sure th=
at we understand the consequences (I am not convinced that the claims in th=
e document on benefits to TCP are substantiated or even true).</span></div>=
<div><span style=3D"background-color:rgba(255,255,255,0)"><br></span><div>A=
s I indicated, a complete review will follow, but I thought that these was =
a global enough topics to call out and get engineered right.</div></div></d=
iv><div><br></div><div>Thomas</div><div><br></div><div>PS: I remain convinc=
ed that the security considerations section is insufficient ; I will try to=
 articulate my thoughts on why that is, but for starters looking at the rec=
ently raised (by somebody else, the Chris replied) AODV security questions =
would probably be helpful</div><div><div></div></div><div><br>On 10 Nov 201=
5, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sratliff@idirect.net" t=
arget=3D"_blank">sratliff@idirect.net</a>&gt; wrote:<br><br></div><blockquo=
te type=3D"cite"><div>






<div>
<p class=3D"MsoNormal">Hello WG participants =E2=80=93 <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">The above referenc=
ed drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (DLEP). The co-auth=
ors and the chairs ask that you please take some
 time to review and comment on the new submissions. <u></u><u></u></span></=
p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>=C2=A0<u></=
u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Regards,<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Stan<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>=C2=A0<u></=
u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<br><span style=3D"font-size:8pt;font-family:Arial,sans-serif;color:#003366=
">_____________________________________________________<br>This electronic =
message and any files transmitted with it contains<br>information from iDir=
ect, which may be privileged, proprietary<br>and/or confidential. It is int=
ended solely for the use of the individual<br>or entity to whom they are ad=
dressed. If you are not the original<br>recipient or the person responsible=
 for delivering the email to the<br>intended recipient, be advised that you=
 have received this email<br>in error, and that any use, dissemination, for=
warding, printing, or<br>copying of this email is strictly prohibited. If y=
ou received this email<br>in error, please delete it and immediately notify=
 the sender.<br>_____________________________________________________</span=
>

</div></blockquote><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/listinfo/manet" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a></span><br><=
/div></blockquote></div></blockquote><blockquote type=3D"cite"><div><span>_=
______________________________________________</span><br><span>manet mailin=
g 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/=
listinfo/manet" target=3D"_blank">https://www.ietf.org/mailman/listinfo/man=
et</a></span><br></div></blockquote></div></div></div><br>_________________=
______________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>
</div></div></div><br></div>
</div></div></blockquote></div><br></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" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature"><div dir=3D"ltr"><p>Kind Regards,</p>

<p><b><span style=3D"color:#1f497d">Akin-Awokoya Emmanuel</span></b></p>

<p><span style=3D"color:#1f497d">Data/Telecommication Network
Engineer and Web/Content Developer</span></p>

<p><span style=3D"color:#1f497d">Member IEEE, NSE, ISOC, CTO, DSA, ICANN</s=
pan></p>

<p><span style=3D"color:#1f497d">=C2=A0</span></p>

<p><i><span style=3D"color:#1f497d">Interested in volunterism,
project research</span></i></p>

<p><i><span style=3D"color:#1f497d">Startups, opendatamining,
open data research</span></i></p>

<p><i><span style=3D"color:#1f497d">TVWhitespace technology</span></i></p>

<p><i><span style=3D"color:#1f497d">=C2=A0</span></i></p>

<p><span style=3D"color:#1f497d">I can be on the next boat, next
ship, next plane, next bus as long as where I am going I could</span></p>

<p><span style=3D"color:#1f497d">help someone have a better
access and create local contents on the Internet.</span></p>

<p><i><span style=3D"color:#1f497d">=C2=A0</span></i></p>

<p><b><font color=3D"#6fa8dc">Twitter:<a href=3D"https://twitter.com/penseB=
ien" target=3D"_blank">@pensebien</a></font></b></p><p><b><font color=3D"#0=
b5394">Facebook</font>:</b> emma.awokoya</p><p><font color=3D"#6fa8dc"><b>L=
inkedin: <a href=3D"https://ng.linkedin.com/in/emmaawokoya" target=3D"_blan=
k">EmmaAwokoya</a></b></font></p></div></div>
</div>

--089e0102def401a0fb0525c02dc6--


From nobody Mon Nov 30 03:43:39 2015
Return-Path: <ietf@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 84C781A92BA for <manet@ietfa.amsl.com>; Mon, 30 Nov 2015 03:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.6
X-Spam-Level: 
X-Spam-Status: No, score=0.6 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, MIME_QP_LONG_LINE=0.001, SPF_HELO_PASS=-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 Lqjrki1XJaH1 for <manet@ietfa.amsl.com>; Mon, 30 Nov 2015 03:43:33 -0800 (PST)
Received: from mxb2.tigertech.net (mxb2.tigertech.net [208.80.4.164]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3AC31A92DE for <manet@ietf.org>; Mon, 30 Nov 2015 03:43:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 954612C0E61; Mon, 30 Nov 2015 03:43:33 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [129.104.73.214] (unknown [129.104.73.214]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id BF7E91C0E2D; Mon, 30 Nov 2015 03:43:32 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-DAE8C2CA-D792-4602-8EA7-D56526044226
Mime-Version: 1.0 (1.0)
From: Thomas Clausen <ietf@thomasclausen.org>
X-Mailer: iPad Mail (13B143)
In-Reply-To: <CAAePS4BVMBHyETCoo1NzHVaGSkdqgTfOciZ_6vwRNxDDTRiFZQ@mail.gmail.com>
Date: Mon, 30 Nov 2015 12:43:32 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <FD27FCB3-2305-4F94-B390-366BDA9E74EA@thomasclausen.org>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com> <CAAePS4BVMBHyETCoo1NzHVaGSkdqgTfOciZ_6vwRNxDDTRiFZQ@mail.gmail.com>
To: Victoria Mercieca <vmercieca0@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/VzdgIovNL4CUD4fdJwyJVwnHZE0>
Cc: manet <manet@ietf.org>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Nov 2015 11:43:37 -0000

--Apple-Mail-DAE8C2CA-D792-4602-8EA7-D56526044226
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

I think that what I wrote can be summarized into two comments:

	o	It would seem that buffering, as specified, does not accomp=
lish what=20
		it states that it accomplishes: packets are (as you describ=
e) still being
		sent while no route is available, and therefore will be dro=
pped later.

		=3D>	Consequently, it seems that buffering is a futile e=
xercise?

	o	(This part you did not address) Buffers have huge impacts o=
n TCP
		performance, and I doubt if (even disregarding the issue ab=
ove) the
		issues on e.g. TCP are well enough understood by this WG
		(Bufferbloat was an example of where people got it wrong, d=
espite
		having extensive experience).

And then, a comment on what you write:

> "But there was a suggestion that this issue might be seen so infrequently i=
n practise that the overhead required to avoid this issue is not worth it "

I do not know from where the referred to suggestion comes, but  ... I do not=
 know that there's substantial enough deployment experience with the protoco=
l for "so infrequently in practice" to make the above an actual argument aga=
inst the  issues raised (and, which you confirm, I understand?) --- this cer=
tainly not if targeting std. track.

Best,

Thomas

Sent from my iPad

> On 23 Nov 2015, at 17:59, Victoria Mercieca <vmercieca0@gmail.com> wrote:
>=20
> Hi again,
>=20
> Regarding the comments on bidirectionality and acks, from Thomas Clausen's=
 email...specifically:
> "Also on buffering, I am wondering if the "start delivering buffered packe=
ts" conditions (penultimate paragraph in 6.6, and of course through the proc=
essing sections) is sufficient; I suspect that the condition "When a valid r=
oute is installed" is not sufficient - that there are situations where a rou=
ting table entry is installed, but the complete route is not available or is=
 not bidirectional?This obviously is related to RREP_Ack being hop-by-hop an=
d not end-to-end...."
>=20
>=20
> Thomas is right about hop-by-hop RREP_Ack. For intermediate nodes who inst=
all a route to OrigAddr based on a one-hop RREP_Ack from their next hop towa=
rd OrigAddr, it's not guaranteed that the complete route to OrigAddr is avai=
lable. Since the route is valid, the router may start forwarding data packet=
s to OrigAddr. An issue occurs if data packets are forwarded to intermediate=
 routers before the intermediate router installs a valid route. If this happ=
ened, those data packets would be dropped and RERRs generated (and regenerat=
ed toward the source of the data packets by any router using it), and the ro=
ute to OrigAddr would be removed at some but maybe not all of the routers th=
at installed it. A new RREQ would then have to go out on behalf of the sourc=
e of the traffic. So this problem would eventually fix itself....but not wit=
hout some dropped packets, RERRs, and a new RREQ/RREP cycle. But there was a=
 suggestion that this issue might be seen so infrequently in practise that t=
he overhead required to avoid this issue is not worth it (i.e. the extra con=
trol traffic of acknowledging every link in every route ever requested, even=
 when some links are already known to be bidirectional).
>=20
> If you disagree, then we need to make RREP_Ack end-to-end and accept the f=
act that this will result in many more RREP_Ack messages being generated tha=
n in the current version.
>=20
> Kind regards,
> Victoria.
>=20
>> On Thu, Nov 19, 2015 at 4:09 PM, Victoria Mercieca <vmercieca0@gmail.com>=
 wrote:
>>=20
>> Hi Thomas and Christopher,
>>=20
>> Thank you for your comments.  If I may address just one point for starter=
s - regeneration vs forwarding. We use the term regeneration since forwardin=
g seems inappropriate when the message content changes at each hop.
>>=20
>> The changes we make to the message content are:
>>=20
>> 1) We change the metric so that each router along the path learns a route=
 from the message, with the metric associated with the path up to that point=

>> 2) AckReq only applies between hops, so needs to be removed at each hop, a=
nd a new AckReq element may need to be added for the next hop.
>> 3) ValidityTime could potentially be added by any intermediate router tha=
t wishes to limit the time it will forward packets on the route.
>> 4) Stripping out Unreachable Addresses from RERR which did not affect our=
 route set.
>>=20
>> Can we really use the term "forwarding" if we are changing the metric val=
ue, adding a validity time, adding/removing AckReq or removing addresses and=
 their associated TLVs?
>>=20
>> Further, in reply to the comment about use of the msg-hop-count and msg-h=
op-limit fields, I think it does not matter that a message only travels one h=
op in that particular form, with that exact set of information enclosed. Hop=
 limit and hop count are part of the message and used by the routing protoco=
l, and so they refer to the multi-hop path that the AODVv2 message will foll=
ow, indicating when not to regenerate any further. So  AODVv2 uses these fie=
lds as suggested in RFC5444 Appendix B, to limit the number of hops across w=
hich it will regenerate a packet so as to "prevent messages from endlessly c=
irculating in a MANET".
>>=20
>> Kind regards,
>> Victoria.
>>=20
>>=20
>>> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <christopher.dearl=
ove@gmail.com> wrote:
>>> I've not had time to look at either yet, though I hope to review DLEP ve=
ry soon.
>>>=20
>>> But this has made me think about the RFC 6621 reference in AODVv2. It's a=
lways been clear this has been rather a throwaway comment that needed though=
t, but until now I hadn't really given it any.
>>>=20
>>> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's cons=
ider each on turn.=20
>>>=20
>>> AODVv2 is in the RFC 5444 structure. As has been noted on many occasions=
, AOVDVv2 gets to use messages, but packets are not in its competence.
>>>=20
>>> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.=
 It's about whether or not to forward them. But RFC 5444 packets aren't just=
 not forwarded in unchanged IP packets, they aren't even forwarded at all. T=
hey are each a single hop construct, and if a message is forwarded (which is=
 by the routing protocol, as far as RFC 5444 is concerned, it's a new messag=
e) it will be in a new packet, with possibly new companions.
>>>=20
>>> If AODVv2 wants to use a more efficient flooding process, it needs one a=
t the message level. Now an example of that exists - the mechanism on RFC 71=
81. Unfortunately we didn't break that out as a separate draft (we would hav=
e liked to, but there were reasons we didn't).
>>>=20
>>> And even if (by reference or other means) it were used - or some related=
 mechanism such as a CDS - that processing/forwarding mechanism assumes you h=
ave defined MPRs (or similarly, that you have defined a CDS). And that needs=
 a local exchange of information, such as NHDP's HELLO messages (and the res=
t of NHDP) augmented with RFC 7181's MPR TLV (though only the flooding bit i=
s needed).
>>>=20
>>> In other words, taking some real work to define. And also raising a ques=
tion for the WG - why do we want a reactive protocol? The main attraction as=
 I see it is the "if you're not doing anything, you're not transmitting" pro=
perty. Which adding this voids. Of course maybe the WG doesn't value that. O=
r it is acceptable as an option. But if so it needs to be an option that all=
 routers use, or none. And if all, compatibly. (MPR flooding allows differen=
t MPR selection algorithms - but only as long as they satisfy the fundamenta=
l MPR algorithm properties.)
>>>=20
>>> In short, RFC 6621 must go. The alternative is nothing, or significant w=
ork.
>>>=20
>>> -- =20
>>> Christopher Dearlove
>>> christopher.dearlove@gmail.com (iPhone)
>>> chris@mnemosyne.demon.co.uk (home)
>>>=20
>>>> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote=
:
>>>>=20
>>>> Dear all,
>>>>=20
>>>> I have started looking through the recently updated draft-ietf-manet-ao=
dvv2-12. A lot has changed, and I regret not to have had a blow-by-bow comeb=
ack to the previous review comments  - would have made it a somewhat easier t=
ask to check if all have been addressed or not.
>>>>=20
>>>> But, I will work through it and produce a detailed review - but from my=
 first quick read-through there're a couple of issue that jumped at me as wo=
rth bringing forward on a more global level already.
>>>>=20
>>>> The first relates to  how RREQs are forwarded -- or, more generally, ar=
e not.
>>>>=20
>>>> The protocol currently talks about "message is regenerated" rather than=
 "forwarded". I have understood that this means that a RREQ is actually not a=
n "end to end" entity, but is a "hop by hop" entity.=20
>>>>=20
>>>> First, that is a curious design choice, is there any reason why this is=
 so considered?
>>>>=20
>>>> Second, if a RREQ message is hop-by-hop only, then I do not think that t=
he use of the RFC5444 hop-limit/hop-count fields is appropriate.
>>>>=20
>>>> Third, the statement in section 6.5 on the use of RFC6621 is incorrect i=
n two ways: RFC6621 does specify how messages are *forwarded* (but, as discu=
ssed above, you are not forwarding messages).
>>>>=20
>>>> More seriously, this paragraph is incorrect:
>>>>=20
>>>>> "Implementations MAY choose to employ techniques to reduce the number o=
f multicast messages sent. Use of [RFC6621] in deployments is recommended. E=
mploying [RFC6621] in a subset of the operational AODVv2 routers in a networ=
k, or configuring different algorithms on different routers, will not cause i=
nteroperability issues, but will reduce the effectiveness of the multicast r=
eduction scheme."
>>>>=20
>>>>=20
>>>> Different routers using different relay selection algorithms in the sam=
e network will not *just* cause loss of efficiency, but *will* cause interop=
erability issues.
>>>>=20
>>>> For example if "router A" decides to suppress its message relaying beca=
use it estimates that "router B" provides sufficient coverage - and converse=
ly "router B" suppresses relaying for the same reason: neither A nor B would=
 relay, and so any routers reachable only via A and B would not be covered.
>>>>=20
>>>> This is not a far-sought example: it can be as simple as A and B simply=
 using self-selecting relay algorithms with different tie-breakers.
>>>>=20
>>>> In short: I think that the whole message flooding/regeneration part req=
uires serious work.
>>>>=20
>>>> The second issue is that I also suspect that there is some issue with b=
uffering, or rather with how it is specified; starting in section 6.6, I am n=
ot sure that leaving that as "a matter of policy at each router" is entirely=
 right.=20
>>>>=20
>>>> Also on buffering, I am wondering if the "start delivering buffered pac=
kets" conditions (penultimate paragraph in 6.6, and of course through the pr=
ocessing sections) is sufficient; I suspect that the condition "When a valid=
 route is installed" is not sufficient - that there are situations where a r=
outing table entry is installed, but the complete route is not available or i=
s not bidirectional?This obviously is related to RREP_Ack being hop-by-hop a=
nd not end-to-end....
>>>>=20
>>>> Either way, the parts of the specification that relate to buffering con=
tain a mixture of normative and non-normative verbiage (a lot of "can" but a=
lso a lot of MUST/SHOULD) which I think could do with a tightening up.=20
>>>>=20
>>>> But....is buffering even something that should be specified by this doc=
ument? It does not impact interoperability and it interferes substantially w=
ith transport and congestion control, and I am not sure that we understand t=
he consequences (I am not convinced that the claims in the document on benef=
its to TCP are substantiated or even true).
>>>>=20
>>>> As I indicated, a complete review will follow, but I thought that these=
 was a global enough topics to call out and get engineered right.
>>>>=20
>>>> Thomas
>>>>=20
>>>> PS: I remain convinced that the security considerations section is insu=
fficient ; I will try to articulate my thoughts on why that is, but for star=
ters looking at the recently raised (by somebody else, the Chris replied) AO=
DV security questions would probably be helpful
>>>>=20
>>>>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrot=
e:
>>>>>=20
>>>>> Hello WG participants =E2=80=93
>>>>>=20
>>>>> =20
>>>>>=20
>>>>> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct.=
 16 (DLEP). The co-authors and the chairs ask that you please take some time=
 to review and comment on the new submissions.
>>>>>=20
>>>>> =20
>>>>>=20
>>>>> Regards,
>>>>>=20
>>>>> Stan
>>>>>=20
>>>>> =20
>>>>>=20
>>>>> =20
>>>>>=20
>>>>>=20
>>>>> _____________________________________________________
>>>>> This electronic message and any files transmitted with it contains
>>>>> information from iDirect, which may be privileged, proprietary
>>>>> and/or confidential. It is intended solely for the use of the individu=
al
>>>>> or entity to whom they are addressed. If you are not the original
>>>>> recipient or the person responsible for delivering the email to the
>>>>> intended recipient, be advised that you have received this email
>>>>> in error, and that any use, dissemination, forwarding, printing, or
>>>>> copying of this email is strictly prohibited. If you received this ema=
il
>>>>> in error, please delete it and immediately notify the sender.
>>>>> _____________________________________________________
>>>>> _______________________________________________
>>>>> 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
>>>=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-DAE8C2CA-D792-4602-8EA7-D56526044226
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>I think that what I wrote can be summa=
rized into two comments:</div><div id=3D"AppleMailSignature"><br></div><div i=
d=3D"AppleMailSignature"><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>It would seem that buffering, as specified, does not accomplish what=
&nbsp;</div><div id=3D"AppleMailSignature"><span class=3D"Apple-tab-span" st=
yle=3D"white-space:pre">		</span>it states that it accomplish=
es: packets are (as you describe) still being</div><div id=3D"AppleMailSigna=
ture"><span class=3D"Apple-tab-span" style=3D"white-space:pre">		</s=
pan>sent while no route is available, and therefore will be dropped later.</=
div><div id=3D"AppleMailSignature"><br></div><div id=3D"AppleMailSignature">=
<span class=3D"Apple-tab-span" style=3D"white-space:pre">		</s=
pan>=3D&gt;<span class=3D"Apple-tab-span" style=3D"white-space:pre">	</s=
pan>Consequently, it seems that buffering is a futile exercise?</div><div id=
=3D"AppleMailSignature"><br></div><div id=3D"AppleMailSignature"><span class=
=3D"Apple-tab-span" style=3D"white-space:pre">	</span>o<span class=3D"Appl=
e-tab-span" style=3D"white-space:pre">	</span>(This part you did not addre=
ss) Buffers have huge impacts on TCP</div><div id=3D"AppleMailSignature"><sp=
an class=3D"Apple-tab-span" style=3D"white-space:pre">		</span>perf=
ormance, and I doubt if (even disregarding the issue above) the</div><div id=
=3D"AppleMailSignature"><span class=3D"Apple-tab-span" style=3D"white-space:=
pre">		</span>issues on e.g. TCP are well enough understood by thi=
s WG</div><div id=3D"AppleMailSignature"><span class=3D"Apple-tab-span" styl=
e=3D"white-space:pre">		</span>(Bufferbloat was an example of where=
 people got it wrong, despite</div><div id=3D"AppleMailSignature"><span clas=
s=3D"Apple-tab-span" style=3D"white-space:pre">		</span>having exten=
sive experience).</div><div id=3D"AppleMailSignature"><br></div><div id=3D"A=
ppleMailSignature">And then, a comment on what you write:</div><div id=3D"Ap=
pleMailSignature"><br></div><div id=3D"AppleMailSignature"><blockquote type=3D=
"cite"><span style=3D"background-color: rgba(255, 255, 255, 0);"><i>"But the=
re was a suggestion that this issue might be seen so infrequently in practis=
e that the overhead required to avoid this issue is not worth it "</i></span=
><br></blockquote><div id=3D"AppleMailSignature"><br></div>I do not know fro=
m where the referred to suggestion comes, but &nbsp;... I do not know that t=
here's substantial enough deployment experience with the protocol for "so in=
frequently in practice" to make the above an actual argument against the &nb=
sp;issues raised (and, which you confirm, I understand?) --- this certainly n=
ot if targeting std. track.</div><div id=3D"AppleMailSignature"><br></div><d=
iv id=3D"AppleMailSignature">Best,</div><div id=3D"AppleMailSignature"><br><=
/div><div id=3D"AppleMailSignature">Thomas</div><div id=3D"AppleMailSignatur=
e"><br>Sent from my iPad</div><div><br>On 23 Nov 2015, at 17:59, Victoria Me=
rcieca &lt;<a href=3D"mailto:vmercieca0@gmail.com">vmercieca0@gmail.com</a>&=
gt; wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"ltr">Hi a=
gain,<br><br>Regarding the comments on bidirectionality and acks, from Thoma=
s Clausen's
        email...specifically:<i><br>
          "<span>Also on buffering, I am wondering if the "start
            delivering buffered packets" conditions (penultimate
            paragraph in 6.6, and of course through the processing
            sections) is sufficient; I suspect that the condition "When
            a valid route is installed" is not sufficient - that there
            are situations where a routing table entry is installed, but
            the complete route is not available or is not
            bidirectional?This obviously is related to RREP_Ack being
            hop-by-hop and not end-to-end....</span></i>"<br><div><i>
              <br></i></div><div><br>Thomas is right about hop-by-hop RREP_A=
ck. For intermediate nodes who install a route to OrigAddr based on a one-ho=
p RREP_Ack from their next hop toward OrigAddr, it's not guaranteed that the=
 complete route to OrigAddr is available. Since the route is valid, the rout=
er may start forwarding data packets to OrigAddr. An issue occurs if data pa=
ckets
            are forwarded to intermediate routers before the
            intermediate router installs a valid route. If this happened, th=
ose data packets would be dropped and RERRs generated (and regenerated towar=
d the source of the data packets by any router using it), and the route to O=
rigAddr would be removed at some but maybe not all of the routers that insta=
lled it. A new RREQ would then
            have to go out on behalf of the source of the traffic. So
            this problem would eventually fix itself....but not without
some dropped packets, RERRs, and a new RREQ/RREP cycle. But there was a sugg=
estion that this
            issue might be seen so infrequently in practise that the
overhead required to avoid this issue is not worth it (i.e. the extra contro=
l traffic of acknowledging every link in every route ever requested, even wh=
en some links are already known to be bidirectional).<br><br></div><div>If y=
ou disagree, then we need to make RREP_Ack end-to-end and accept the fact th=
at this will result in many more RREP_Ack messages being generated than in t=
he current version.<br></div><div><br></div><div>Kind regards,<br></div><div=
>Victoria.<br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Thu, Nov 19, 2015 at 4:09 PM, Victoria Mercieca <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:vmercieca0@gmail.com" target=3D"_blank">vmercieca0@gm=
ail.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"><div class=3D=
"HOEnZb"><div class=3D"h5"><div dir=3D"ltr"><br><div class=3D"gmail_quote"><=
div dir=3D"ltr"><p dir=3D"ltr">Hi Thomas and Christopher,</p>
<p dir=3D"ltr">Thank you for your comments.&nbsp; If I may address just one=20=

point for starters - regeneration vs forwarding. We use the term=20
regeneration since forwarding seems inappropriate when the message=20
content changes at each hop.</p>
<p dir=3D"ltr">The changes we make to the message content are:</p>
<p dir=3D"ltr">1) We change the metric so that each router along the path=20=

learns a route from the message, with the metric associated with the=20
path up to that point<br>
2) AckReq only applies between hops, so needs to be removed at each hop,
 and a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router=20
that wishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our ro=
ute set.</p>
<p dir=3D"ltr">Can we really use the term "forwarding" if we are changing=20=

the metric value, adding a validity time, adding/removing AckReq or=20
removing addresses and their associated TLVs?</p>
<p dir=3D"ltr">Further, in reply to the comment about use of the=20
msg-hop-count and msg-hop-limit fields, I think it does not matter that a
=20
message only travels one hop in that particular form, with that exact=20
set of information enclosed. Hop limit and hop count are part of the=20
message=20
and used by the routing protocol, and so they=20
refer to the multi-hop path that the AODVv2 message will follow,=20
indicating when not to regenerate any further. So=20
AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit=20
the number of hops across which it will regenerate a packet so as to=20
"prevent messages from endlessly circulating in a MANET". </p>
<p dir=3D"ltr">Kind regards,<br>
Victoria.</p></div><div><div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <span dir=3D=
"ltr">&lt;<a href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_blank=
">christopher.dearlove@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"><div dir=3D"auto"><div>I've not had time to look at either yet, th=
ough I hope to review DLEP very soon.</div><div><br></div><div>But this has m=
ade me think about the RFC 6621 reference in AODVv2. It's always been clear t=
his has been rather a throwaway comment that needed thought, but until now I=
 hadn't really given it any.</div><div><br></div><div>And it doesn't work. R=
FC 6621 is fundamentally unusable here. Let's consider each on turn.&nbsp;</=
div><div><br></div><div>AODVv2 is in the RFC 5444 structure. As has been not=
ed on many occasions, AOVDVv2 gets to use messages, but packets are not in i=
ts competence.</div><div><br></div><div>RFC 6621 is about packets. But not e=
ven RFC 5444 packets but IP packets. It's about whether or not to forward th=
em. But RFC 5444 packets aren't just not forwarded in unchanged IP packets, t=
hey aren't even forwarded at all. They are each a single hop construct, and i=
f a message is forwarded (which is by the routing protocol, as far as RFC 54=
44 is concerned, it's a new message) it will be in a new packet, with possib=
ly new companions.</div><div><br></div><div>If AODVv2 wants to use a more ef=
ficient flooding process, it needs one at the message level. Now an example o=
f that exists - the mechanism on RFC 7181. Unfortunately we didn't break tha=
t out as a separate draft (we would have liked to, but there were reasons we=
 didn't).</div><div><br></div><div>And even if (by reference or other means)=
 it were used - or some related mechanism such as a CDS - that processing/fo=
rwarding mechanism assumes you have defined MPRs (or similarly, that you hav=
e defined a CDS). And that needs a local exchange of information, such as NH=
DP's HELLO messages (and the rest of NHDP) augmented with RFC 7181's MPR TLV=
 (though only the flooding bit is needed).</div><div><br></div><div>In other=
 words, taking some real work to define. And also raising a question for the=
 WG - why do we want a reactive protocol? The main attraction as I see it is=
 the "if you're not doing anything, you're not transmitting" property. Which=
 adding this voids. Of course maybe the WG doesn't value that. Or it is acce=
ptable as an option. But if so it needs to be an option that all routers use=
, or none. And if all, compatibly. (MPR flooding allows different MPR select=
ion algorithms - but only as long as they satisfy the fundamental MPR algori=
thm properties.)</div><div><br></div><div>In short, RFC 6621 must go. The al=
ternative is nothing, or significant work.<br><br><div>-- &nbsp;<span><font c=
olor=3D"#888888"><div>Christopher Dearlove</div><div><a href=3D"mailto:chris=
topher.dearlove@gmail.com" target=3D"_blank">christopher.dearlove@gmail.com<=
/a> (iPhone)</div><div><a href=3D"mailto:chris@mnemosyne.demon.co.uk" target=
=3D"_blank">chris@mnemosyne.demon.co.uk</a> (home)</div></font></span></div>=
</div><div><div><div><br>On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a hre=
f=3D"mailto:ietf@thomasclausen.org" target=3D"_blank">ietf@thomasclausen.org=
</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>
<div>Dear all,</div><div><br></div><div>I have started looking through the r=
ecently updated&nbsp;draft-ietf-manet-aodvv2-12. A lot has changed, and I re=
gret not to have had a blow-by-bow comeback to the previous review comments &=
nbsp;- would have made it a somewhat easier task to check if all have been a=
ddressed or not.</div><div><br></div><div>But, I will work through it and pr=
oduce a detailed review - but from my first quick read-through there're a co=
uple of issue that jumped at me as worth bringing forward on a more global l=
evel already.</div><div><br></div><div>The first relates to &nbsp;how RREQs a=
re forwarded -- or, more generally, are not.</div><div><br></div><div>The pr=
otocol currently talks about "message is regenerated" rather than "forwarded=
". I have understood that this means that a RREQ is actually not an "end to e=
nd" entity, but is a "hop by hop" entity.&nbsp;</div><div><br></div><div>Fir=
st, that is a curious design choice, is there any reason why this is so cons=
idered?</div><div><br></div><div>Second, if a RREQ message is hop-by-hop onl=
y, then I do not think that the use of the RFC5444 hop-limit/hop-count field=
s is appropriate.</div><div><br></div><div>Third, the statement in section 6=
.5 on the use of RFC6621 is incorrect in two ways: RFC6621 does specify how m=
essages are *forwarded* (but, as discussed above, you are not forwarding mes=
sages).</div><div><br></div><div>More seriously, this paragraph <span style=3D=
"background-color:rgba(255,255,255,0)">is incorrect</span>:</div><div><pre s=
tyle=3D"margin-top:0px;margin-bottom:0px"><font face=3D"UICTFontTextStyleTal=
lBody"><span style=3D"white-space:normal;background-color:rgba(255,255,255,0=
)"><br></span></font></pre><pre style=3D"margin-top:0px;margin-bottom:0px"><=
blockquote type=3D"cite"><font face=3D"UICTFontTextStyleTallBody"><span styl=
e=3D"white-space:normal;background-color:rgba(255,255,255,0)">"Implementatio=
ns MAY choose to employ techniques to reduce the number
   of multicast messages sent.  Use of [<a href=3D"https://tools.ietf.org/ht=
ml/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;" target=3D"=
_blank">RFC6621</a>] in deployments is
   recommended.  Employing [<a href=3D"https://tools.ietf.org/html/rfc6621" t=
itle=3D"&quot;Simplified Multicast Forwarding&quot;" target=3D"_blank">RFC66=
21</a>] in a subset of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction scheme."</span></font=
><span style=3D"font-size:19px">
</span></blockquote></pre></div><div><br></div><div>Different routers using d=
ifferent relay selection algorithms in the same network will not *just* caus=
e loss of efficiency, but *will* cause interoperability issues.</div><div><b=
r></div><div>For example if "router A" decides to suppress its message relay=
ing because it estimates that "router B" provides sufficient coverage - and c=
onversely "router B" suppresses relaying for the same reason: neither A nor B=
 would relay, and so any routers reachable only via A and B would not be cov=
ered.</div><div><br></div><div>This is not a far-sought example: it can be a=
s simple as A and B simply using self-selecting relay algorithms with differ=
ent tie-breakers.</div><div><br></div><div>In short: I think that the whole m=
essage flooding/regeneration part requires serious work.</div><div><br></div=
><div><div><span style=3D"background-color:rgba(255,255,255,0)">The second i=
ssue is that I also suspect that there is some issue with buffering, or rath=
er with how it is specified; starting in section 6.6, I am not sure that lea=
ving that as "a matter of policy at each router" is entirely right.&nbsp;</s=
pan></div><div><span style=3D"background-color:rgba(255,255,255,0)"><br></sp=
an></div><div><span style=3D"background-color:rgba(255,255,255,0)">Also on b=
uffering, I am wondering if the "start delivering buffered packets" conditio=
ns (penultimate paragraph in 6.6, and of course through the processing secti=
ons) is sufficient; I suspect that the condition "When a valid route is inst=
alled" is not sufficient - that there are situations where a routing table e=
ntry is installed, but the complete route is not available or is not bidirec=
tional?This obviously is related to RREP_Ack being hop-by-hop and not end-to=
-end....</span></div><div><span style=3D"background-color:rgba(255,255,255,0=
)"><br></span></div><div><span style=3D"background-color:rgba(255,255,255,0)=
">Either way, the parts of the specification that relate to buffering contai=
n a mixture of normative and non-normative verbiage (a lot of "can" but also=
 a lot of MUST/SHOULD) which I think could do with a tightening up.&nbsp;</s=
pan></div><div><span style=3D"background-color:rgba(255,255,255,0)"><br></sp=
an></div><div><span style=3D"background-color:rgba(255,255,255,0)">But....is=
 buffering even something that should be specified by this document? It does=
 not impact interoperability and it interferes substantially with transport a=
nd congestion control, and I am not sure that we understand the consequences=
 (I am not convinced that the claims in the document on benefits to TCP are s=
ubstantiated or even true).</span></div><div><span style=3D"background-color=
:rgba(255,255,255,0)"><br></span><div>As I indicated, a complete review will=
 follow, but I thought that these was a global enough topics to call out and=
 get engineered right.</div></div></div><div><br></div><div>Thomas</div><div=
><br></div><div>PS: I remain convinced that the security considerations sect=
ion is insufficient ; I will try to articulate my thoughts on why that is, b=
ut for starters looking at the recently raised (by somebody else, the Chris r=
eplied) AODV security questions would probably be helpful</div><div><div></d=
iv></div><div><br>On 10 Nov 2015, at 02:10, Ratliff, Stanley &lt;<a href=3D"=
mailto:sratliff@idirect.net" target=3D"_blank">sratliff@idirect.net</a>&gt; w=
rote:<br><br></div><blockquote type=3D"cite"><div>






<div>
<p class=3D"MsoNormal">Hello WG participants =E2=80=93 <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">The above referenced=
 drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (DLEP). The co-authors=
 and the chairs ask that you please take some
 time to review and comment on the new submissions. <u></u><u></u></span></p=
>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>&nbsp;<u></u>=
</span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Regards,<u></u><u></=
u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Stan<u></u><u></u></=
span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-siz=
e:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>&nbsp;<u></u>=
</span></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<br><span style=3D"font-size:8pt;font-family:Arial,sans-serif;color:#003366"=
>_____________________________________________________<br>This electronic me=
ssage and any files transmitted with it contains<br>information from iDirect=
, which may be privileged, proprietary<br>and/or confidential. It is intende=
d solely for the use of the individual<br>or entity to whom they are address=
ed. If you are not the original<br>recipient or the person responsible for d=
elivering the email to the<br>intended recipient, be advised that you have r=
eceived this email<br>in error, and that any use, dissemination, forwarding,=
 printing, or<br>copying of this email is strictly prohibited. If you receiv=
ed this email<br>in error, please delete it and immediately notify the sende=
r.<br>_____________________________________________________</span>

</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" target=3D"_blank">manet@ietf.org</a></s=
pan><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a></span><br></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" target=3D"_blank">manet@ie=
tf.org</a></span><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/=
manet" target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a></sp=
an><br></div></blockquote></div></div></div><br>____________________________=
___________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>
</div></div></div><br></div>
</div></div></blockquote></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-DAE8C2CA-D792-4602-8EA7-D56526044226--


From nobody Mon Nov 30 03:49:46 2015
Return-Path: <akinpense2@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 89D7B1A92EB for <manet@ietfa.amsl.com>; Mon, 30 Nov 2015 03:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.351
X-Spam-Level: **
X-Spam-Status: No, score=2.351 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, J_CHICKENPOX_47=0.6, J_CHICKENPOX_52=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 9VGDIwfUV6MZ for <manet@ietfa.amsl.com>; Mon, 30 Nov 2015 03:49:41 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531C61A92BD for <manet@ietf.org>; Mon, 30 Nov 2015 03:49:40 -0800 (PST)
Received: by wmuu63 with SMTP id u63so125749992wmu.0 for <manet@ietf.org>; Mon, 30 Nov 2015 03:49:39 -0800 (PST)
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=aG72udFe1Z5OCJ/F9w6KDMf076gfWklCwCQ0AMgwFVk=; b=TjbHpbp2PUZHon/8XjPPmsPzT15lUgnVp4NZyoDLbAzS+W87nqe5TB5P7AGfSZHVvf 3XTRVP2AFl9KlHf7wNbz0oKRPA62cSGXhdFi7pNwYNlX5zwo0pM2rmin9cBYjN/Ep1M4 YbThELiMVuKzIBVRr40wob4rHhS3646iCV2X1HqPtc5RFauuQEcn3uUaPqoprsNKjLZs c0XyjhkBQbU51Bno0xTFghVDp+LQzyu3Ors22Ir/VOfuhV+Iu/Lme5YQCTdty92H6Eay 1csY29JXnHf+wdkSb1+5QXkHxnSZvV6HuNzPYIM9YP0dK0uEOlgVTJEKwVdHwme4h05S 5MXg==
MIME-Version: 1.0
X-Received: by 10.28.136.149 with SMTP id k143mr26463183wmd.57.1448884178878;  Mon, 30 Nov 2015 03:49:38 -0800 (PST)
Received: by 10.194.200.69 with HTTP; Mon, 30 Nov 2015 03:49:38 -0800 (PST)
In-Reply-To: <FD27FCB3-2305-4F94-B390-366BDA9E74EA@thomasclausen.org>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com> <CAAePS4BVMBHyETCoo1NzHVaGSkdqgTfOciZ_6vwRNxDDTRiFZQ@mail.gmail.com> <FD27FCB3-2305-4F94-B390-366BDA9E74EA@thomasclausen.org>
Date: Mon, 30 Nov 2015 03:49:38 -0800
Message-ID: <CACjBtK3Xv4tqVv8C5kk=VWpv85XXZcVwkfsD6gpyFQJOfdtB8w@mail.gmail.com>
From: Awokoya Emma <akinpense2@gmail.com>
To: Thomas Clausen <ietf@thomasclausen.org>
Content-Type: multipart/alternative; boundary=001a11443ed8cd87e80525c0a29b
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/bHcodwpEobtDbEMXWTmGL80LZVE>
Cc: manet <manet@ietf.org>, Victoria Mercieca <vmercieca0@gmail.com>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Nov 2015 11:49:44 -0000

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

Dear Thomas
So I hope Victoria would consider your recommendation more in a future
comment.



On Mon, Nov 30, 2015 at 3:43 AM, Thomas Clausen <ietf@thomasclausen.org>
wrote:

> I think that what I wrote can be summarized into two comments:
>
> o It would seem that buffering, as specified, does not accomplish what
> it states that it accomplishes: packets are (as you describe) still being
> sent while no route is available, and therefore will be dropped later.
>
> =3D> Consequently, it seems that buffering is a futile exercise?
>
> o (This part you did not address) Buffers have huge impacts on TCP
> performance, and I doubt if (even disregarding the issue above) the
> issues on e.g. TCP are well enough understood by this WG
> (Bufferbloat was an example of where people got it wrong, despite
> having extensive experience).
>
> And then, a comment on what you write:
>
> *"But there was a suggestion that this issue might be seen so infrequentl=
y
> in practise that the overhead required to avoid this issue is not worth i=
t
> "*
>
>
> I do not know from where the referred to suggestion comes, but  ... I do
> not know that there's substantial enough deployment experience with the
> protocol for "so infrequently in practice" to make the above an actual
> argument against the  issues raised (and, which you confirm, I understand=
?)
> --- this certainly not if targeting std. track.
>
> Best,
>
> Thomas
>
> Sent from my iPad
>
> On 23 Nov 2015, at 17:59, Victoria Mercieca <vmercieca0@gmail.com> wrote:
>
> Hi again,
>
> Regarding the comments on bidirectionality and acks, from Thomas Clausen'=
s
> email...specifically:
> * "Also on buffering, I am wondering if the "start delivering buffered
> packets" conditions (penultimate paragraph in 6.6, and of course through
> the processing sections) is sufficient; I suspect that the condition "Whe=
n
> a valid route is installed" is not sufficient - that there are situations
> where a routing table entry is installed, but the complete route is not
> available or is not bidirectional?This obviously is related to RREP_Ack
> being hop-by-hop and not end-to-end....*"
>
>
> Thomas is right about hop-by-hop RREP_Ack. For intermediate nodes who
> install a route to OrigAddr based on a one-hop RREP_Ack from their next h=
op
> toward OrigAddr, it's not guaranteed that the complete route to OrigAddr =
is
> available. Since the route is valid, the router may start forwarding data
> packets to OrigAddr. An issue occurs if data packets are forwarded to
> intermediate routers before the intermediate router installs a valid rout=
e.
> If this happened, those data packets would be dropped and RERRs generated
> (and regenerated toward the source of the data packets by any router usin=
g
> it), and the route to OrigAddr would be removed at some but maybe not all
> of the routers that installed it. A new RREQ would then have to go out on
> behalf of the source of the traffic. So this problem would eventually fix
> itself....but not without some dropped packets, RERRs, and a new RREQ/RRE=
P
> cycle. But there was a suggestion that this issue might be seen so
> infrequently in practise that the overhead required to avoid this issue i=
s
> not worth it (i.e. the extra control traffic of acknowledging every link =
in
> every route ever requested, even when some links are already known to be
> bidirectional).
>
> If you disagree, then we need to make RREP_Ack end-to-end and accept the
> fact that this will result in many more RREP_Ack messages being generated
> than in the current version.
>
> Kind regards,
> Victoria.
>
> On Thu, Nov 19, 2015 at 4:09 PM, Victoria Mercieca <vmercieca0@gmail.com>
> wrote:
>
>>
>> Hi Thomas and Christopher,
>>
>> Thank you for your comments.  If I may address just one point for
>> starters - regeneration vs forwarding. We use the term regeneration sinc=
e
>> forwarding seems inappropriate when the message content changes at each =
hop.
>>
>> The changes we make to the message content are:
>>
>> 1) We change the metric so that each router along the path learns a rout=
e
>> from the message, with the metric associated with the path up to that po=
int
>> 2) AckReq only applies between hops, so needs to be removed at each hop,
>> and a new AckReq element may need to be added for the next hop.
>> 3) ValidityTime could potentially be added by any intermediate router
>> that wishes to limit the time it will forward packets on the route.
>> 4) Stripping out Unreachable Addresses from RERR which did not affect ou=
r
>> route set.
>>
>> Can we really use the term "forwarding" if we are changing the metric
>> value, adding a validity time, adding/removing AckReq or removing addres=
ses
>> and their associated TLVs?
>>
>> Further, in reply to the comment about use of the msg-hop-count and
>> msg-hop-limit fields, I think it does not matter that a message only
>> travels one hop in that particular form, with that exact set of informat=
ion
>> enclosed. Hop limit and hop count are part of the message and used by th=
e
>> routing protocol, and so they refer to the multi-hop path that the AODVv=
2
>> message will follow, indicating when not to regenerate any further. So
>> AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit th=
e
>> number of hops across which it will regenerate a packet so as to "preven=
t
>> messages from endlessly circulating in a MANET".
>>
>> Kind regards,
>> Victoria.
>>
>> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <
>> christopher.dearlove@gmail.com> wrote:
>>
>>> I've not had time to look at either yet, though I hope to review DLEP
>>> very soon.
>>>
>>> But this has made me think about the RFC 6621 reference in AODVv2. It's
>>> always been clear this has been rather a throwaway comment that needed
>>> thought, but until now I hadn't really given it any.
>>>
>>> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's
>>> consider each on turn.
>>>
>>> AODVv2 is in the RFC 5444 structure. As has been noted on many
>>> occasions, AOVDVv2 gets to use messages, but packets are not in its
>>> competence.
>>>
>>> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets=
.
>>> It's about whether or not to forward them. But RFC 5444 packets aren't =
just
>>> not forwarded in unchanged IP packets, they aren't even forwarded at al=
l.
>>> They are each a single hop construct, and if a message is forwarded (wh=
ich
>>> is by the routing protocol, as far as RFC 5444 is concerned, it's a new
>>> message) it will be in a new packet, with possibly new companions.
>>>
>>> If AODVv2 wants to use a more efficient flooding process, it needs one
>>> at the message level. Now an example of that exists - the mechanism on =
RFC
>>> 7181. Unfortunately we didn't break that out as a separate draft (we wo=
uld
>>> have liked to, but there were reasons we didn't).
>>>
>>> And even if (by reference or other means) it were used - or some relate=
d
>>> mechanism such as a CDS - that processing/forwarding mechanism assumes =
you
>>> have defined MPRs (or similarly, that you have defined a CDS). And that
>>> needs a local exchange of information, such as NHDP's HELLO messages (a=
nd
>>> the rest of NHDP) augmented with RFC 7181's MPR TLV (though only the
>>> flooding bit is needed).
>>>
>>> In other words, taking some real work to define. And also raising a
>>> question for the WG - why do we want a reactive protocol? The main
>>> attraction as I see it is the "if you're not doing anything, you're not
>>> transmitting" property. Which adding this voids. Of course maybe the WG
>>> doesn't value that. Or it is acceptable as an option. But if so it need=
s to
>>> be an option that all routers use, or none. And if all, compatibly. (MP=
R
>>> flooding allows different MPR selection algorithms - but only as long a=
s
>>> they satisfy the fundamental MPR algorithm properties.)
>>>
>>> In short, RFC 6621 must go. The alternative is nothing, or significant
>>> work.
>>>
>>> --
>>> Christopher Dearlove
>>> christopher.dearlove@gmail.com (iPhone)
>>> chris@mnemosyne.demon.co.uk (home)
>>>
>>> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote=
:
>>>
>>> Dear all,
>>>
>>> I have started looking through the recently
>>> updated draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not=
 to
>>> have had a blow-by-bow comeback to the previous review comments  - woul=
d
>>> have made it a somewhat easier task to check if all have been addressed=
 or
>>> not.
>>>
>>> But, I will work through it and produce a detailed review - but from my
>>> first quick read-through there're a couple of issue that jumped at me a=
s
>>> worth bringing forward on a more global level already.
>>>
>>> The first relates to  how RREQs are forwarded -- or, more generally, ar=
e
>>> not.
>>>
>>> The protocol currently talks about "message is regenerated" rather than
>>> "forwarded". I have understood that this means that a RREQ is actually =
not
>>> an "end to end" entity, but is a "hop by hop" entity.
>>>
>>> First, that is a curious design choice, is there any reason why this is
>>> so considered?
>>>
>>> Second, if a RREQ message is hop-by-hop only, then I do not think that
>>> the use of the RFC5444 hop-limit/hop-count fields is appropriate.
>>>
>>> Third, the statement in section 6.5 on the use of RFC6621 is incorrect
>>> in two ways: RFC6621 does specify how messages are *forwarded* (but, as
>>> discussed above, you are not forwarding messages).
>>>
>>> More seriously, this paragraph is incorrect:
>>>
>>>
>>> "Implementations MAY choose to employ techniques to reduce the number
>>>    of multicast messages sent.  Use of [RFC6621 <https://tools.ietf.org=
/html/rfc6621>] in deployments is
>>>    recommended.  Employing [RFC6621 <https://tools.ietf.org/html/rfc662=
1>] in a subset of the operational
>>>    AODVv2 routers in a network, or configuring different algorithms on
>>>    different routers, will not cause interoperability issues, but will
>>>    reduce the effectiveness of the multicast reduction scheme."
>>>
>>>
>>> Different routers using different relay selection algorithms in the sam=
e
>>> network will not *just* cause loss of efficiency, but *will* cause
>>> interoperability issues.
>>>
>>> For example if "router A" decides to suppress its message relaying
>>> because it estimates that "router B" provides sufficient coverage - and
>>> conversely "router B" suppresses relaying for the same reason: neither =
A
>>> nor B would relay, and so any routers reachable only via A and B would =
not
>>> be covered.
>>>
>>> This is not a far-sought example: it can be as simple as A and B simply
>>> using self-selecting relay algorithms with different tie-breakers.
>>>
>>> In short: I think that the whole message flooding/regeneration part
>>> requires serious work.
>>>
>>> The second issue is that I also suspect that there is some issue with
>>> buffering, or rather with how it is specified; starting in section 6.6,=
 I
>>> am not sure that leaving that as "a matter of policy at each router" is
>>> entirely right.
>>>
>>> Also on buffering, I am wondering if the "start delivering buffered
>>> packets" conditions (penultimate paragraph in 6.6, and of course throug=
h
>>> the processing sections) is sufficient; I suspect that the condition "W=
hen
>>> a valid route is installed" is not sufficient - that there are situatio=
ns
>>> where a routing table entry is installed, but the complete route is not
>>> available or is not bidirectional?This obviously is related to RREP_Ack
>>> being hop-by-hop and not end-to-end....
>>>
>>> Either way, the parts of the specification that relate to buffering
>>> contain a mixture of normative and non-normative verbiage (a lot of "ca=
n"
>>> but also a lot of MUST/SHOULD) which I think could do with a tightening=
 up.
>>>
>>> But....is buffering even something that should be specified by this
>>> document? It does not impact interoperability and it interferes
>>> substantially with transport and congestion control, and I am not sure =
that
>>> we understand the consequences (I am not convinced that the claims in t=
he
>>> document on benefits to TCP are substantiated or even true).
>>>
>>> As I indicated, a complete review will follow, but I thought that these
>>> was a global enough topics to call out and get engineered right.
>>>
>>> Thomas
>>>
>>> PS: I remain convinced that the security considerations section is
>>> insufficient ; I will try to articulate my thoughts on why that is, but=
 for
>>> starters looking at the recently raised (by somebody else, the Chris
>>> replied) AODV security questions would probably be helpful
>>>
>>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote=
:
>>>
>>> Hello WG participants =E2=80=93
>>>
>>>
>>>
>>> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct.
>>> 16 (DLEP). The co-authors and the chairs ask that you please take some =
time
>>> to review and comment on the new submissions.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Stan
>>>
>>>
>>>
>>>
>>>
>>> _____________________________________________________
>>> This electronic message and any files transmitted with it contains
>>> information from iDirect, which may be privileged, proprietary
>>> and/or confidential. It is intended solely for the use of the individua=
l
>>> or entity to whom they are addressed. If you are not the original
>>> recipient or the person responsible for delivering the email to the
>>> intended recipient, be advised that you have received this email
>>> in error, and that any use, dissemination, forwarding, printing, or
>>> copying of this email is strictly prohibited. If you received this emai=
l
>>> in error, please delete it and immediately notify the sender.
>>> _____________________________________________________
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>


--=20

Kind Regards,

*Akin-Awokoya Emmanuel*

Data/Telecommication Network Engineer and Web/Content Developer

Member IEEE, NSE, ISOC, CTO, DSA, ICANN



*Interested in volunterism, project research*

*Startups, opendatamining, open data research*

*TVWhitespace technology*



I can be on the next boat, next ship, next plane, next bus as long as where
I am going I could

help someone have a better access and create local contents on the Internet=
.



*Twitter:@pensebien <https://twitter.com/penseBien>*

*Facebook:* emma.awokoya

*Linkedin: EmmaAwokoya <https://ng.linkedin.com/in/emmaawokoya>*

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

<div dir=3D"ltr">Dear Thomas<div>So I hope Victoria would consider your rec=
ommendation more in a future comment.</div><div><br></div><div><br></div></=
div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Nov 3=
0, 2015 at 3:43 AM, Thomas Clausen <span dir=3D"ltr">&lt;<a href=3D"mailto:=
ietf@thomasclausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><div>I thin=
k that what I wrote can be summarized into two comments:</div><div><br></di=
v><div><span style=3D"white-space:pre-wrap">	</span>o<span style=3D"white-s=
pace:pre-wrap">	</span>It would seem that buffering, as specified, does not=
 accomplish what=C2=A0</div><div><span style=3D"white-space:pre-wrap">		</s=
pan>it states that it accomplishes: packets are (as you describe) still bei=
ng</div><div><span style=3D"white-space:pre-wrap">		</span>sent while no ro=
ute is available, and therefore will be dropped later.</div><div><br></div>=
<div><span style=3D"white-space:pre-wrap">		</span>=3D&gt;<span style=3D"wh=
ite-space:pre-wrap">	</span>Consequently, it seems that buffering is a futi=
le exercise?</div><div><br></div><div><span style=3D"white-space:pre-wrap">=
	</span>o<span style=3D"white-space:pre-wrap">	</span>(This part you did no=
t address) Buffers have huge impacts on TCP</div><div><span style=3D"white-=
space:pre-wrap">		</span>performance, and I doubt if (even disregarding the=
 issue above) the</div><div><span style=3D"white-space:pre-wrap">		</span>i=
ssues on e.g. TCP are well enough understood by this WG</div><div><span sty=
le=3D"white-space:pre-wrap">		</span>(Bufferbloat was an example of where p=
eople got it wrong, despite</div><div><span style=3D"white-space:pre-wrap">=
		</span>having extensive experience).</div><span class=3D""><div><br></div=
><div>And then, a comment on what you write:</div><div><br></div></span><di=
v><span class=3D""><blockquote type=3D"cite"><span style=3D"background-colo=
r:rgba(255,255,255,0)"><i>&quot;But there was a suggestion that this issue =
might be seen so infrequently in practise that the overhead required to avo=
id this issue is not worth it &quot;</i></span><br></blockquote><div><br></=
div></span>I do not know from where the referred to suggestion comes, but =
=C2=A0... I do not know that there&#39;s substantial enough deployment expe=
rience with the protocol for &quot;so infrequently in practice&quot; to mak=
e the above an actual argument against the =C2=A0issues raised (and, which =
you confirm, I understand?) --- this certainly not if targeting std. track.=
</div><div><br></div><div>Best,</div><div><br></div><div>Thomas</div><div><=
br>Sent from my iPad</div><div><div class=3D"h5"><div><br>On 23 Nov 2015, a=
t 17:59, Victoria Mercieca &lt;<a href=3D"mailto:vmercieca0@gmail.com" targ=
et=3D"_blank">vmercieca0@gmail.com</a>&gt; wrote:<br><br></div><blockquote =
type=3D"cite"><div><div dir=3D"ltr">Hi again,<br><br>Regarding the comments=
 on bidirectionality and acks, from Thomas Clausen&#39;s
        email...specifically:<i><br>
          &quot;<span>Also on buffering, I am wondering if the &quot;start
            delivering buffered packets&quot; conditions (penultimate
            paragraph in 6.6, and of course through the processing
            sections) is sufficient; I suspect that the condition &quot;Whe=
n
            a valid route is installed&quot; is not sufficient - that there
            are situations where a routing table entry is installed, but
            the complete route is not available or is not
            bidirectional?This obviously is related to RREP_Ack being
            hop-by-hop and not end-to-end....</span></i>&quot;<br><div><i>
              <br></i></div><div><br>Thomas is right about hop-by-hop RREP_=
Ack. For intermediate nodes who install a route to OrigAddr based on a one-=
hop RREP_Ack from their next hop toward OrigAddr, it&#39;s not guaranteed t=
hat the complete route to OrigAddr is available. Since the route is valid, =
the router may start forwarding data packets to OrigAddr. An issue occurs i=
f data packets
            are forwarded to intermediate routers before the
            intermediate router installs a valid route. If this happened, t=
hose data packets would be dropped and RERRs generated (and regenerated tow=
ard the source of the data packets by any router using it), and the route t=
o OrigAddr would be removed at some but maybe not all of the routers that i=
nstalled it. A new RREQ would then
            have to go out on behalf of the source of the traffic. So
            this problem would eventually fix itself....but not without
some dropped packets, RERRs, and a new RREQ/RREP cycle. But there was a sug=
gestion that this
            issue might be seen so infrequently in practise that the
overhead required to avoid this issue is not worth it (i.e. the extra contr=
ol traffic of acknowledging every link in every route ever requested, even =
when some links are already known to be bidirectional).<br><br></div><div>I=
f you disagree, then we need to make RREP_Ack end-to-end and accept the fac=
t that this will result in many more RREP_Ack messages being generated than=
 in the current version.<br></div><div><br></div><div>Kind regards,<br></di=
v><div>Victoria.<br></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Nov 19, 2015 at 4:09 PM, Victoria Mercieca <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:vmercieca0@gmail.com" target=3D"_blank">vm=
ercieca0@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div><div><div dir=3D"ltr"><br><div class=3D"gmail_quote"><div dir=3D"ltr">=
<p dir=3D"ltr">Hi Thomas and Christopher,</p>
<p dir=3D"ltr">Thank you for your comments.=C2=A0 If I may address just one=
=20
point for starters - regeneration vs forwarding. We use the term=20
regeneration since forwarding seems inappropriate when the message=20
content changes at each hop.</p>
<p dir=3D"ltr">The changes we make to the message content are:</p>
<p dir=3D"ltr">1) We change the metric so that each router along the path=
=20
learns a route from the message, with the metric associated with the=20
path up to that point<br>
2) AckReq only applies between hops, so needs to be removed at each hop,
 and a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router=20
that wishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our r=
oute set.</p>
<p dir=3D"ltr">Can we really use the term &quot;forwarding&quot; if we are =
changing=20
the metric value, adding a validity time, adding/removing AckReq or=20
removing addresses and their associated TLVs?</p>
<p dir=3D"ltr">Further, in reply to the comment about use of the=20
msg-hop-count and msg-hop-limit fields, I think it does not matter that a
=20
message only travels one hop in that particular form, with that exact=20
set of information enclosed. Hop limit and hop count are part of the=20
message=20
and used by the routing protocol, and so they=20
refer to the multi-hop path that the AODVv2 message will follow,=20
indicating when not to regenerate any further. So=20
AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit=20
the number of hops across which it will regenerate a packet so as to=20
&quot;prevent messages from endlessly circulating in a MANET&quot;. </p>
<p dir=3D"ltr">Kind regards,<br>
Victoria.</p></div><div><div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <span dir=
=3D"ltr">&lt;<a href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_b=
lank">christopher.dearlove@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div dir=3D"auto"><div>I&#39;ve not had time to look at e=
ither yet, though I hope to review DLEP very soon.</div><div><br></div><div=
>But this has made me think about the RFC 6621 reference in AODVv2. It&#39;=
s always been clear this has been rather a throwaway comment that needed th=
ought, but until now I hadn&#39;t really given it any.</div><div><br></div>=
<div>And it doesn&#39;t work. RFC 6621 is fundamentally unusable here. Let&=
#39;s consider each on turn.=C2=A0</div><div><br></div><div>AODVv2 is in th=
e RFC 5444 structure. As has been noted on many occasions, AOVDVv2 gets to =
use messages, but packets are not in its competence.</div><div><br></div><d=
iv>RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.=
 It&#39;s about whether or not to forward them. But RFC 5444 packets aren&#=
39;t just not forwarded in unchanged IP packets, they aren&#39;t even forwa=
rded at all. They are each a single hop construct, and if a message is forw=
arded (which is by the routing protocol, as far as RFC 5444 is concerned, i=
t&#39;s a new message) it will be in a new packet, with possibly new compan=
ions.</div><div><br></div><div>If AODVv2 wants to use a more efficient floo=
ding process, it needs one at the message level. Now an example of that exi=
sts - the mechanism on RFC 7181. Unfortunately we didn&#39;t break that out=
 as a separate draft (we would have liked to, but there were reasons we did=
n&#39;t).</div><div><br></div><div>And even if (by reference or other means=
) it were used - or some related mechanism such as a CDS - that processing/=
forwarding mechanism assumes you have defined MPRs (or similarly, that you =
have defined a CDS). And that needs a local exchange of information, such a=
s NHDP&#39;s HELLO messages (and the rest of NHDP) augmented with RFC 7181&=
#39;s MPR TLV (though only the flooding bit is needed).</div><div><br></div=
><div>In other words, taking some real work to define. And also raising a q=
uestion for the WG - why do we want a reactive protocol? The main attractio=
n as I see it is the &quot;if you&#39;re not doing anything, you&#39;re not=
 transmitting&quot; property. Which adding this voids. Of course maybe the =
WG doesn&#39;t value that. Or it is acceptable as an option. But if so it n=
eeds to be an option that all routers use, or none. And if all, compatibly.=
 (MPR flooding allows different MPR selection algorithms - but only as long=
 as they satisfy the fundamental MPR algorithm properties.)</div><div><br><=
/div><div>In short, RFC 6621 must go. The alternative is nothing, or signif=
icant work.<br><br><div>-- =C2=A0<span><font color=3D"#888888"><div>Christo=
pher Dearlove</div><div><a href=3D"mailto:christopher.dearlove@gmail.com" t=
arget=3D"_blank">christopher.dearlove@gmail.com</a> (iPhone)</div><div><a h=
ref=3D"mailto:chris@mnemosyne.demon.co.uk" target=3D"_blank">chris@mnemosyn=
e.demon.co.uk</a> (home)</div></font></span></div></div><div><div><div><br>=
On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a href=3D"mailto:ietf@thomasc=
lausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt; wrote:<br><br>=
</div><blockquote type=3D"cite"><div>
<div>Dear all,</div><div><br></div><div>I have started looking through the =
recently updated=C2=A0draft-ietf-manet-aodvv2-12. A lot has changed, and I =
regret not to have had a blow-by-bow comeback to the previous review commen=
ts =C2=A0- would have made it a somewhat easier task to check if all have b=
een addressed or not.</div><div><br></div><div>But, I will work through it =
and produce a detailed review - but from my first quick read-through there&=
#39;re a couple of issue that jumped at me as worth bringing forward on a m=
ore global level already.</div><div><br></div><div>The first relates to =C2=
=A0how RREQs are forwarded -- or, more generally, are not.</div><div><br></=
div><div>The protocol currently talks about &quot;message is regenerated&qu=
ot; rather than &quot;forwarded&quot;. I have understood that this means th=
at a RREQ is actually not an &quot;end to end&quot; entity, but is a &quot;=
hop by hop&quot; entity.=C2=A0</div><div><br></div><div>First, that is a cu=
rious design choice, is there any reason why this is so considered?</div><d=
iv><br></div><div>Second, if a RREQ message is hop-by-hop only, then I do n=
ot think that the use of the RFC5444 hop-limit/hop-count fields is appropri=
ate.</div><div><br></div><div>Third, the statement in section 6.5 on the us=
e of RFC6621 is incorrect in two ways: RFC6621 does specify how messages ar=
e *forwarded* (but, as discussed above, you are not forwarding messages).</=
div><div><br></div><div>More seriously, this paragraph <span style=3D"backg=
round-color:rgba(255,255,255,0)">is incorrect</span>:</div><div><pre style=
=3D"margin-top:0px;margin-bottom:0px"><font face=3D"UICTFontTextStyleTallBo=
dy"><span style=3D"white-space:normal;background-color:rgba(255,255,255,0)"=
><br></span></font></pre><pre style=3D"margin-top:0px;margin-bottom:0px"><b=
lockquote type=3D"cite"><font face=3D"UICTFontTextStyleTallBody"><span styl=
e=3D"white-space:normal;background-color:rgba(255,255,255,0)">&quot;Impleme=
ntations MAY choose to employ techniques to reduce the number
   of multicast messages sent.  Use of [<a href=3D"https://tools.ietf.org/h=
tml/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;" target=
=3D"_blank">RFC6621</a>] in deployments is
   recommended.  Employing [<a href=3D"https://tools.ietf.org/html/rfc6621"=
 title=3D"&quot;Simplified Multicast Forwarding&quot;" target=3D"_blank">RF=
C6621</a>] in a subset of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction scheme.&quot;</span>=
</font><span style=3D"font-size:19px">
</span></blockquote></pre></div><div><br></div><div>Different routers using=
 different relay selection algorithms in the same network will not *just* c=
ause loss of efficiency, but *will* cause interoperability issues.</div><di=
v><br></div><div>For example if &quot;router A&quot; decides to suppress it=
s message relaying because it estimates that &quot;router B&quot; provides =
sufficient coverage - and conversely &quot;router B&quot; suppresses relayi=
ng for the same reason: neither A nor B would relay, and so any routers rea=
chable only via A and B would not be covered.</div><div><br></div><div>This=
 is not a far-sought example: it can be as simple as A and B simply using s=
elf-selecting relay algorithms with different tie-breakers.</div><div><br><=
/div><div>In short: I think that the whole message flooding/regeneration pa=
rt requires serious work.</div><div><br></div><div><div><span style=3D"back=
ground-color:rgba(255,255,255,0)">The second issue is that I also suspect t=
hat there is some issue with buffering, or rather with how it is specified;=
 starting in section 6.6, I am not sure that leaving that as &quot;a matter=
 of policy at each router&quot; is entirely right.=C2=A0</span></div><div><=
span style=3D"background-color:rgba(255,255,255,0)"><br></span></div><div><=
span style=3D"background-color:rgba(255,255,255,0)">Also on buffering, I am=
 wondering if the &quot;start delivering buffered packets&quot; conditions =
(penultimate paragraph in 6.6, and of course through the processing section=
s) is sufficient; I suspect that the condition &quot;When a valid route is =
installed&quot; is not sufficient - that there are situations where a routi=
ng table entry is installed, but the complete route is not available or is =
not bidirectional?This obviously is related to RREP_Ack being hop-by-hop an=
d not end-to-end....</span></div><div><span style=3D"background-color:rgba(=
255,255,255,0)"><br></span></div><div><span style=3D"background-color:rgba(=
255,255,255,0)">Either way, the parts of the specification that relate to b=
uffering contain a mixture of normative and non-normative verbiage (a lot o=
f &quot;can&quot; but also a lot of MUST/SHOULD) which I think could do wit=
h a tightening up.=C2=A0</span></div><div><span style=3D"background-color:r=
gba(255,255,255,0)"><br></span></div><div><span style=3D"background-color:r=
gba(255,255,255,0)">But....is buffering even something that should be speci=
fied by this document? It does not impact interoperability and it interfere=
s substantially with transport and congestion control, and I am not sure th=
at we understand the consequences (I am not convinced that the claims in th=
e document on benefits to TCP are substantiated or even true).</span></div>=
<div><span style=3D"background-color:rgba(255,255,255,0)"><br></span><div>A=
s I indicated, a complete review will follow, but I thought that these was =
a global enough topics to call out and get engineered right.</div></div></d=
iv><div><br></div><div>Thomas</div><div><br></div><div>PS: I remain convinc=
ed that the security considerations section is insufficient ; I will try to=
 articulate my thoughts on why that is, but for starters looking at the rec=
ently raised (by somebody else, the Chris replied) AODV security questions =
would probably be helpful</div><div><div></div></div><div><br>On 10 Nov 201=
5, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sratliff@idirect.net" t=
arget=3D"_blank">sratliff@idirect.net</a>&gt; wrote:<br><br></div><blockquo=
te type=3D"cite"><div>






<div>
<p class=3D"MsoNormal">Hello WG participants =E2=80=93 <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">The above referenc=
ed drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (DLEP). The co-auth=
ors and the chairs ask that you please take some
 time to review and comment on the new submissions. <u></u><u></u></span></=
p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>=C2=A0<u></=
u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Regards,<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif">Stan<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:12.0pt;font-family:&quot;Times New Roman&quot;,serif"><u></u>=C2=A0<u></=
u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<br><span style=3D"font-size:8pt;font-family:Arial,sans-serif;color:#003366=
">_____________________________________________________<br>This electronic =
message and any files transmitted with it contains<br>information from iDir=
ect, which may be privileged, proprietary<br>and/or confidential. It is int=
ended solely for the use of the individual<br>or entity to whom they are ad=
dressed. If you are not the original<br>recipient or the person responsible=
 for delivering the email to the<br>intended recipient, be advised that you=
 have received this email<br>in error, and that any use, dissemination, for=
warding, printing, or<br>copying of this email is strictly prohibited. If y=
ou received this email<br>in error, please delete it and immediately notify=
 the sender.<br>_____________________________________________________</span=
>

</div></blockquote><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/listinfo/manet" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a></span><br><=
/div></blockquote></div></blockquote><blockquote type=3D"cite"><div><span>_=
______________________________________________</span><br><span>manet mailin=
g 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/=
listinfo/manet" target=3D"_blank">https://www.ietf.org/mailman/listinfo/man=
et</a></span><br></div></blockquote></div></div></div><br>_________________=
______________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>
</div></div></div><br></div>
</div></div></blockquote></div><br></div>
</div></blockquote><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/listinfo/manet" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a></span><br><=
/div></blockquote></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" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature"><div dir=3D"ltr"><p>Kind Regards,</p>

<p><b><span style=3D"color:#1f497d">Akin-Awokoya Emmanuel</span></b></p>

<p><span style=3D"color:#1f497d">Data/Telecommication Network
Engineer and Web/Content Developer</span></p>

<p><span style=3D"color:#1f497d">Member IEEE, NSE, ISOC, CTO, DSA, ICANN</s=
pan></p>

<p><span style=3D"color:#1f497d">=C2=A0</span></p>

<p><i><span style=3D"color:#1f497d">Interested in volunterism,
project research</span></i></p>

<p><i><span style=3D"color:#1f497d">Startups, opendatamining,
open data research</span></i></p>

<p><i><span style=3D"color:#1f497d">TVWhitespace technology</span></i></p>

<p><i><span style=3D"color:#1f497d">=C2=A0</span></i></p>

<p><span style=3D"color:#1f497d">I can be on the next boat, next
ship, next plane, next bus as long as where I am going I could</span></p>

<p><span style=3D"color:#1f497d">help someone have a better
access and create local contents on the Internet.</span></p>

<p><i><span style=3D"color:#1f497d">=C2=A0</span></i></p>

<p><b><font color=3D"#6fa8dc">Twitter:<a href=3D"https://twitter.com/penseB=
ien" target=3D"_blank">@pensebien</a></font></b></p><p><b><font color=3D"#0=
b5394">Facebook</font>:</b> emma.awokoya</p><p><font color=3D"#6fa8dc"><b>L=
inkedin: <a href=3D"https://ng.linkedin.com/in/emmaawokoya" target=3D"_blan=
k">EmmaAwokoya</a></b></font></p></div></div>
</div>

--001a11443ed8cd87e80525c0a29b--


From nobody Mon Nov 30 05:30:12 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 47BA21A6F7F; Mon, 30 Nov 2015 05:30:10 -0800 (PST)
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: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151130133010.20830.23926.idtracker@ietfa.amsl.com>
Date: Mon, 30 Nov 2015 05:30:10 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/p_9mElHJMIwNaxd4viXJ80KcwMI>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-ibs-04.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: <https://mailarchive.ietf.org/arch/browse/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, 30 Nov 2015 13:30:10 -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-04.txt
	Pages           : 17
	Date            : 2015-11-30

Abstract:
   This document extends 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:
https://tools.ietf.org/html/draft-ietf-manet-ibs-04

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


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/

