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

Lou Berger <lberger@labn.net> Tue, 20 February 2018 22:53 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 EDACE12E03F for <manet@ietfa.amsl.com>; Tue, 20 Feb 2018 14:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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 eTo2QfdkZxvH for <manet@ietfa.amsl.com>; Tue, 20 Feb 2018 14:53:54 -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 0899C12E03C for <manet@ietf.org>; Tue, 20 Feb 2018 14:53:54 -0800 (PST)
Received: from CMOut01 (unknown [10.0.90.82]) by gproxy10.mail.unifiedlayer.com (Postfix) with ESMTP id 9E536140422 for <manet@ietf.org>; Tue, 20 Feb 2018 15:53:53 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id DAtp1x00Y2SSUrH01AtsZ4; Tue, 20 Feb 2018 15:53:53 -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=Op4juWPpsa0A:10 a=r77TgQKjGQsHNAKrUKIA:9 a=5vjwwrbCAAAA:8 a=pGLkceISAAAA:8 a=wU2YTnxGAAAA:8 a=48vgC7mUAAAA:8 a=jHhOQAr4w4N9wrIy8xsA:9 a=cNJ4cJaYNd3Wokg0:21 a=i22mnJ8XwL0LrqAK:21 a=CjuIK1q_8ugA:10 a=febuGJr95vwA:10 a=nKsp94PS5oGf0SHxE0wA:9 a=vbClT0Nyg4YcJFf-:21 a=nKEiJG1Xp44HKElE:21 a=cDCBgCen0qXA4sw3:21 a=_W_S_7VecoQA:10 a=rUtsQoudGX4PATiiMU9I:22 a=pV4yRLctw-KkoPKGQz8o:22 a=Yz9wTY_ffGCQnEDHKrcv:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:MIME-Version:Subject:References:In-Reply-To: Message-ID:Date:CC:To:From:Sender:Reply-To:Content-Transfer-Encoding: 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=0RrDkjrDYqnPQqardGkMPTbp5S9BrpnXW0KqbHLfh1I=; b=ke0npbP+UoMYDGoc2WrOf7cwRw 7sjGAJ+hPtfToar5JZ0ZBo7bljgVdZNRQiKpKAttg93eYFdLXJYuebp9as/zHjgLjrV0Fznaen51n oDCwdU7+7Eh3/fQ26ivws4+8W;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:58458 helo=[11.4.0.163]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89_1) (envelope-from <lberger@labn.net>) id 1eoGnF-002uCo-Cp; Tue, 20 Feb 2018 15:53:49 -0700
From: Lou Berger <lberger@labn.net>
To: Rick Taylor <rick@tropicalstormsoftware.com>, Stan Ratliff <ratliffstan@gmail.com>
CC: David - 0665 - MITLL Wiggins <david.wiggins@ll.mit.edu>, Abdussalam Baryun <abdussalambaryun@gmail.com>, manet@ietf.org, draft-ietf-manet-dlep-latency-extension@ietf.org
Date: Tue, 20 Feb 2018 17:53:47 -0500
Message-ID: <161b56c4090.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801D330F213@tss-server1.home.tropicalstormsoftware.com>
References: <38A5475DE83986499AEACD2CFAFC3F9801D330F213@tss-server1.home.tropicalstormsoftware.com>
User-Agent: AquaMail/1.13.2-730 (build: 101300200)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------161b56c4491194a27d3fe255d"
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: 100.15.86.101
X-Exim-ID: 1eoGnF-002uCo-Cp
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net ([11.4.0.163]) [100.15.86.101]:58458
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/bd1pMwbfctCCEjK-3FrwVDKH3GQ>
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 22:53:56 -0000

Agreed.


On February 20, 2018 5:17:20 PM Rick Taylor 
<rick@tropicalstormsoftware.com> wrote:

> As long as it is obvious that this is after a successful extension negotiation
>
> Rick
>
> (Sent from my phone)
>
> ----- Reply message -----
> From: "Stan Ratliff" <ratliffstan@gmail.com>
> To: "Lou Berger" <lberger@labn.net>
> Cc: "Rick Taylor" <rick@tropicalstormsoftware.com>, "Wiggins, David - 0665 
> - MITLL" <david.wiggins@ll.mit.edu>, "Abdussalam Baryun" 
> <abdussalambaryun@gmail.com>, "manet" <manet@ietf.org>, 
> "draft-ietf-manet-dlep-latency-extension@ietf.org" 
> <draft-ietf-manet-dlep-latency-extension@ietf.org>
> Subject: [manet] I-D Action: draft-ietf-manet-dlep-latency-extension-02.txt
> Date: Tue, Feb 20, 2018 21:32
>
> Lou,
>
>
> On Tue, Feb 20, 2018 at 4:29 PM, Lou Berger 
> <lberger@labn.net<mailto:lberger@labn.net>> wrote:
>
> Stan,
>
> "In lieu" of a mandatory 8175 item is a pretty big change.  I don't think 
> we want to go there.  I think the rest of the text is fine.
>
> Point taken. So, you're good with the second sentence changing to "The 
> latency Range Data Item MAY be carried in addition to the Latency Data 
> Item." ??
>
> Regards,
> Stan
>
>
>
> On February 20, 2018 4:27:16 PM Stan Ratliff 
> <ratliffstan@gmail.com<mailto:ratliffstan@gmail.com>> wrote:
>
> I agree with Rick on adding 'types'. So, I'll propose some text. Maybe this 
> will help?
>
> "The Latency Range Data Item MAY be carried in any message where the 
> Latency Data Item [RFC8175] is allowed. The Latency Range Data Item MAY be 
> carried in addition to, or in lieu of, the Latency Data Item."
>
> Regards,
> Stan
>
>
>>           The Latency Range Data Item MAY be carried in the same messages
>>     ... as  the Latency Data Item defined in [RFC8175].
>
>
> On Tue, Feb 20, 2018 at 4:05 PM, Rick Taylor 
> <rick@tropicalstormsoftware.com<mailto:rick@tropicalstormsoftware.com>> wrote:
> We have been fairly consistent in RFC8175 to refer to DLEP *messages*  I'm 
> not sure adding 'types' helps...
>
> Rick
>
>> -----Original Message-----
>> From: manet [mailto:manet-bounces@ietf.org<mailto:manet-bounces@ietf.org>] 
>> On Behalf Of Wiggins, David -
>> 0665 - MITLL
>> Sent: 20 February 2018 18:47
>> To: Lou Berger; Abdussalam Baryun
>> Cc: manet; 
>> draft-ietf-manet-dlep-latency-extension@ietf.org<mailto:draft-ietf-manet-dlep-latency-extension@ietf.org>
>> Subject: Re: [manet] I-D Action: draft-ietf-manet-dlep-latency-extension-
>> 02.txt
>>
>> On 2/20/18, 12:42 PM, "manet on behalf of Lou Berger" <manet-
>> bounces@ietf.org<mailto:bounces@ietf.org> on behalf of 
>> lberger@labn.net<mailto: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
>
> _______________________________________________
> manet mailing list
> manet@ietf.org<mailto:manet@ietf.org>
> https://www.ietf.org/mailman/listinfo/manet
>
>