Re: [manet] I-D Action: draft-ietf-manet-dlep-latency-extension-01.txt

"Velt, R. (Ronald) in 't" <Ronald.intVelt@tno.nl> Wed, 08 November 2017 14:34 UTC

Return-Path: <Ronald.intVelt@tno.nl>
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 0C8C1126D45 for <manet@ietfa.amsl.com>; Wed, 8 Nov 2017 06:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 8IJ2UcqVrer8 for <manet@ietfa.amsl.com>; Wed, 8 Nov 2017 06:34:17 -0800 (PST)
Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87DFC126CD6 for <manet@ietf.org>; Wed, 8 Nov 2017 06:34:16 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.44,364,1505772000"; d="scan'208";a="2903018"
From: "Velt, R. (Ronald) in 't" <Ronald.intVelt@tno.nl>
To: Henning Rogge <hrogge@gmail.com>, Lou Berger <lberger@labn.net>
CC: MANET IETF <manet@ietf.org>
Thread-Topic: [manet] I-D Action: draft-ietf-manet-dlep-latency-extension-01.txt
Thread-Index: AQHTUan8M+3VPOcbr0GFvRDQG5rOTqL8oLEAgA1t6gCAAIngkA==
Date: Wed, 08 Nov 2017 14:34:14 +0000
Message-ID: <c568f217119f4d26bfffcd38378421dc@tno.nl>
References: <150938684459.7924.12734346764675720800@ietfa.amsl.com> <73f0c278-746d-89ad-1f22-fa409a1ad085@labn.net> <CAGnRvurZ4DTHsjFo2TVcarCd2s_zw0WKe7s+1RqyPwU7-gAzsw@mail.gmail.com>
In-Reply-To: <CAGnRvurZ4DTHsjFo2TVcarCd2s_zw0WKe7s+1RqyPwU7-gAzsw@mail.gmail.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.221.225.191]
x-esetresult: clean, is OK
x-esetid: 37303A296E4DB26C667661
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/qILQoCeIG6LiETc-bm6iSRKe_74>
Subject: Re: [manet] I-D Action: draft-ietf-manet-dlep-latency-extension-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.22
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, 08 Nov 2017 14:34:24 -0000

Hi Lou, all,

Also in the nitpicking department: What is "Lantency"? Latency of the LAN between router and radio, perhaps? 😝
(See I-D title).

Ronald

> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Henning Rogge
> Sent: woensdag 8 november 2017 8:15
> To: Lou Berger <lberger@labn.net>
> Cc: MANET IETF <manet@ietf.org>
> Subject: Re: [manet] I-D Action: draft-ietf-manet-dlep-latency-extension-
> 01.txt
> 
> two nitpicks for Chapter 3:
> 
> the second sentence of the first paragraph should read
> 
> The Latency Range Item MAY be carried in the same  messages and MUST be
> processed according to the same rules as the  Latency Data Item defined in
> [RFC8175].
> 
> There is no "Latency Range Data Item" in RFC8175.
> 
> Second, maybe moving to nanoseconds is a good idea? The range is still
> "longer than humans used radio", but we already have radios with sub-
> microsecond timings I think.
> 
> Henning Rogge
> 
> On Mon, Oct 30, 2017 at 7:10 PM, Lou Berger <lberger@labn.net> wrote:
> > Hi,
> >
> > This version included updated references and some minor editorial fixes.
> >
> > Lou (for authors)
> >
> >
> > On 10/30/2017 2:07 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 WG of the IETF.
> >>
> >>         Title           : DLEP Lantency Range Extension
> >>         Authors         : Bow-Nan Cheng
> >>                           Lou Berger
> >>       Filename        : draft-ietf-manet-dlep-latency-extension-01.txt
> >>       Pages           : 5
> >>       Date            : 2017-10-30
> >>
> >> Abstract:
> >>    This document defines an extension to the DLEP protocol to provide
> >>    the range of latency that may be experienced on a link.
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-latency-extens
> >> ion/
> >>
> >> There are also htmlized versions available at:
> >> https://tools.ietf.org/html/draft-ietf-manet-dlep-latency-extension-0
> >> 1
> >> https://datatracker.ietf.org/doc/html/draft-ietf-manet-dlep-latency-e
> >> xtension-01
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-dlep-latency-exten
> >> sion-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/
> >>
> >> _______________________________________________
> >> 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
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.