IETF Logo Mail Archive

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

Lou Berger <lberger@labn.net> Tue, 20 February 2018 19:07 UTC

Return-Path: <lberger@labn.net>
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 F3DEF12DA00 for <manet@ietfa.amsl.com>; Tue, 20 Feb 2018 11:07:32 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 OmEpfflTu41w for <manet@ietfa.amsl.com>; Tue, 20 Feb 2018 11:07:32 -0800 (PST)
Received: from gproxy10-pub.mail.unifiedlayer.com (gproxy10-pub.mail.unifiedlayer.com [69.89.20.226]) (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 E255512D95C for <manet@ietf.org>; Tue, 20 Feb 2018 11:07:31 -0800 (PST)
Received: from CMOut01 (unknown [10.0.90.82]) by gproxy10.mail.unifiedlayer.com (Postfix) with ESMTP id 70C4614071E for <manet@ietf.org>; Tue, 20 Feb 2018 12:07:31 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id D77T1x0122SSUrH0177W9m; Tue, 20 Feb 2018 12:07:31 -0700
X-Authority-Analysis: v=2.2 cv=Rf/gMxlv c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=Op4juWPpsa0A:10 a=48vgC7mUAAAA:8 a=wU2YTnxGAAAA:8 a=jvHO9dImqAaqpHzfXpsA:9 a=7P_OSIAwS9NavnPG:21 a=yYBGcWs_i0kSykXu:21 a=CjuIK1q_8ugA:10 a=w1C3t2QeGrPiZgrLijVG:22 a=Yz9wTY_ffGCQnEDHKrcv:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject: References:In-Reply-To:Message-ID:Date:CC:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=UfAEzulUGH+L2m0nE7r7HUM+WdjmoXltW/Pvda9qdtw=; b=dInbA+hn0ak/QCUxSALLNVsCvS ++wljTx5r5Uyrkk5FR/DPmdPqaYApJk2mX6hWvsg96jDyRKT97um2py99xY+prRKeoqkdf/9+0xM6 rd9M09mUgyCrKxhtDzO2On1yc;
Received: from [172.58.185.61] (port=22954 helo=[IPV6:2607:fb90:64ba:b75d:0:3:59bf:6501]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89_1) (envelope-from <lberger@labn.net>) id 1eoDGB-001VHa-8T; Tue, 20 Feb 2018 12:07:27 -0700
From: Lou Berger <lberger@labn.net>
To: "Wiggins, David - 0665 - MITLL" <david.wiggins@ll.mit.edu>, Abdussalam Baryun <abdussalambaryun@gmail.com>
CC: manet <manet@ietf.org>, draft-ietf-manet-dlep-latency-extension@ietf.org
Date: Tue, 20 Feb 2018 14:07:24 -0500
Message-ID: <161b49d01e0.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <4FEB14CD-DE8D-4735-9FCA-8912EB49AB82@ll.mit.edu>
References: <151865086912.7521.1302513672018061966@ietfa.amsl.com> <e7dfe5c2-ba21-fc0b-121f-908f37cf6618@labn.net> <CADnDZ8-Kw6jDbBNer8nBmPFPwhin+hHDxovV1VajizPrK2Ra_Q@mail.gmail.com> <b183af7e-c416-85be-46b2-a2e32004cbcc@labn.net> <CADnDZ8_jLnnXcvT=bpXCK6Rc1DiB3Kx2uHUFJ3rMeTHDM_NboA@mail.gmail.com> <1b0c761b-9fda-49e0-8344-52750c232b74@labn.net> <4FEB14CD-DE8D-4735-9FCA-8912EB49AB82@ll.mit.edu>
User-Agent: AquaMail/1.13.2-730 (build: 101300200)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 172.58.185.61
X-Exim-ID: 1eoDGB-001VHa-8T
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([IPV6:2607:fb90:64ba:b75d:0:3:59bf:6501]) [172.58.185.61]:22954
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/pu5cy35pih8NZJgGrkanlhtyOQg>
X-Mailman-Approved-At: Thu, 22 Feb 2018 08:55:17 -0800
Subject: Re: [manet] I-D Action: draft-ietf-manet-dlep-latency-extension-02.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: Tue, 20 Feb 2018 19:07:33 -0000

That's reasonable.

Thanks,
Lou


On February 20, 2018 1:47:57 PM "Wiggins, David - 0665 - MITLL" 
<David.Wiggins@ll.mit.edu> wrote:

> On 2/20/18, 12:42 PM, "manet on behalf of Lou Berger" 
> <manet-bounces@ietf.org on behalf of lberger@labn.net> wrote:
>     On 2/19/2018 9:19 PM, Abdussalam Baryun wrote:
>     > But IMO it is not clear where the Latency Range item operates within
>     > 8175,
>     >
>
>     The draft currently says:
>
>           The Latency Range Data Item MAY be carried in the same messages
>     ... as  the Latency Data Item defined in [RFC8175].
>
>     Is this not sufficient?
>
> Perhaps AB is reading this as "if a specific, on-the-wire message has a Latency
> Data Item in it, then that particular message is allowed to have a Latency 
> Range
> Data Item.  Otherwise, it cannot have a Latency Range Data Item.
> AB, is that your interpretation?  If so, then maybe just saying "message types"
> instead of "messages" is enough clarification.
>
> David
>

v2.23.0 | Report a Bug | By Email