Re: [manet] I-D Action: draft-ietf-manet-dlep-27.txt

Rick Taylor <rick@tropicalstormsoftware.com> Wed, 25 January 2017 14:23 UTC

Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F996129953 for <manet@ietfa.amsl.com>; Wed, 25 Jan 2017 06:23:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.1
X-Spam-Level:
X-Spam-Status: No, score=-5.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 PoAqxyLXnMJx for <manet@ietfa.amsl.com>; Wed, 25 Jan 2017 06:23: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 B610812995C for <manet@ietf.org>; Wed, 25 Jan 2017 06:23: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; Wed, 25 Jan 2017 14:23:22 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "hrogge@gmail.com" <hrogge@gmail.com>, "manet@ietf.org" <manet@ietf.org>
Thread-Topic: [manet] I-D Action: draft-ietf-manet-dlep-27.txt
Thread-Index: AQHSdl2fqSnpVOrRAkOko5MVXcnvsqFJMwmAgAANZoA=
Date: Wed, 25 Jan 2017 14:23:23 +0000
Message-ID: <1485354203.14098.14.camel@tropicalstormsoftware.com>
References: <148527472522.12598.17039375382524226738.idtracker@ietfa.amsl.com> <CAGnRvuo_LNWBor9ShCpLimkMgK9Qykc1DzfAAptd07Xgm7UDug@mail.gmail.com>
In-Reply-To: <CAGnRvuo_LNWBor9ShCpLimkMgK9Qykc1DzfAAptd07Xgm7UDug@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="utf-8"
Content-ID: <8decb824-1307-4943-a8e4-b41ae16533ca>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/yKZM-lg7dJwQmK-1xzuGX9w0IjY>
Subject: Re: [manet] I-D Action: draft-ietf-manet-dlep-27.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.17
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 Jan 2017 14:23:52 -0000

Henning,

I take your point that the 'Secured Medium' flag does not give any
fine-grained information about what security is applied on the over-
the-air signalling.

It was added to address an entirely valid DISCUSS, where it was pointed
out that a router has no idea whether to blindly trust the remote
destination information, or whether some kind of deployment specific
restriction should be applied.

The alternative approach was to add *more* specificity, i.e. extra Data
Items and specification of over-the-air signalling, and/or arbitrary
restrictions on what data items could/should be trusted or not.  This
approach was discarded as it just added more 'weight' that would be
better addressed in extensions.

The 'Secure Medium' flag is not a panacea, and purely acts as a simple
canary for use in unplanned/ad-hoc deployments.  An extension draft
that addresses specific security aspects, for example 802.11
WEP/WPA/etc modes, is indeed more useful.

In short: we believe the 'Secured Medium' flag is a compromise of least
impact.

Cheers,

Rick

On Wed, 2017-01-25 at 14:35 +0100, Henning Rogge wrote:
> Hi,
> 
> I am a bit worried about the "secure" flag being pulled into the main
> RFC... security comes in different "flavors", which could be an
> excellent point in writing a DLEP extension where the radio informs
> the router about the security concerns (per radio channel, per
> client,
> ...) and maybe even gives the router an information how to send
> secured/unsecured frames.
> 
> Just a single bit is not really that helpful.
> 
> If we need more revisions for DLEP we should work on making them
> leaner, not heavier.
> 
> Henning Rogge
> 
> On Tue, Jan 24, 2017 at 5:18 PM,  <internet-drafts@ietf.org> wrote:
> > 
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the Mobile Ad-hoc Networks of the
> > IETF.
> > 
> >         Title           : Dynamic Link Exchange Protocol (DLEP)
> >         Authors         : Stan Ratliff
> >                           Shawn Jury
> >                           Darryl Satterwhite
> >                           Rick Taylor
> >                           Bo Berry
> >         Filename        : draft-ietf-manet-dlep-27.txt
> >         Pages           : 78
> >         Date            : 2017-01-24
> > 
> > Abstract:
> >    When routing devices rely on modems to effect communications
> > over
> >    wireless links, they need timely and accurate knowledge of the
> >    characteristics of the link (speed, state, etc.) in order to
> > make
> >    routing decisions.  In mobile or other environments where these
> >    characteristics change frequently, manual configurations or the
> >    inference of state through routing or transport protocols does
> > not
> >    allow the router to make the best decisions.  DLEP describes a
> > new
> >    protocol for a bidirectional, event-driven communication channel
> >    between the router and the modem to facilitate communication of
> >    changing link characteristics.
> > 
> > 
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-manet-dlep/
> > 
> > There's also a htmlized version available at:
> > https://tools.ietf.org/html/draft-ietf-manet-dlep-27
> > 
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-dlep-27
> > 
> > 
> > Please note that it may take a couple of minutes from the time of
> > submission
> > until the htmlized version and diff are available at
> > tools.ietf.org.
> > 
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet