Re: [6lo] working group last call (wg lc) on https://datatracker.ietf.org/doc/draft-ietf-6lo-deadline-time/

"Georgios Z. Papadopoulos" <georgios.papadopoulos@imt-atlantique.fr> Tue, 24 July 2018 08:19 UTC

Return-Path: <georgios.papadopoulos@imt-atlantique.fr>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35078131047; Tue, 24 Jul 2018 01:19:09 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=imt-atlantique.fr
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 U388cQqT7Yq6; Tue, 24 Jul 2018 01:19:05 -0700 (PDT)
Received: from zproxy120.enst.fr (zproxy120.enst.fr [137.194.2.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02539131045; Tue, 24 Jul 2018 01:19:05 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by zproxy120.enst.fr (Postfix) with ESMTP id 4345F816EC; Tue, 24 Jul 2018 10:19:03 +0200 (CEST)
Received: from zproxy120.enst.fr ([IPv6:::1]) by localhost (zproxy120.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 5rQmINVTAz3p; Tue, 24 Jul 2018 10:19:00 +0200 (CEST)
Received: from localhost (localhost [IPv6:::1]) by zproxy120.enst.fr (Postfix) with ESMTP id 8F9E7816F4; Tue, 24 Jul 2018 10:19:00 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy120.enst.fr 8F9E7816F4
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1532420340; bh=VjCBrONhE4e31BZ7MZ6YKBPPDEJq5B8xcEB5y/MdsSo=; h=Mime-Version:From:Date:Message-Id:To; b=OvGMLSnYIS4DT62zyrsHSacWP6x0hWWIxbx5L75lOEY9b70FRoX5cElxmiRL3g/GG sGxTI4EY63xMT+lJ8b+dCsovR3ZQ9BCjFUav0trNx/tJenbQdzvMAU4Agj/LsSN67U fT3UJfkKx7AUbir3NEdVFmOsY+U799gPsI2hDMMs=
X-Virus-Scanned: amavisd-new at zproxy120.enst.fr
Received: from zproxy120.enst.fr ([IPv6:::1]) by localhost (zproxy120.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id empq4Zpv1hFH; Tue, 24 Jul 2018 10:19:00 +0200 (CEST)
Received: from [192.168.43.206] (unknown [37.168.77.107]) by zproxy120.enst.fr (Postfix) with ESMTPSA id A9C808032B; Tue, 24 Jul 2018 10:18:58 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_55D53D6B-EAAE-48FE-B3B0-4D063F5FEFA9"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: "Georgios Z. Papadopoulos" <georgios.papadopoulos@imt-atlantique.fr>
In-Reply-To: <006301d42318$fd3a2320$f7ae6960$@cdac.in>
Date: Tue, 24 Jul 2018 11:18:57 +0300
Cc: draft-ietf-6lo-deadline-time@ietf.org, anand@ece.iisc.ernet.in, Malati Hegde <malati@ece.iisc.ernet.in>, Samita Chakrabarti <samitac.ietf@gmail.com>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, lo <6lo@ietf.org>, Charlie Perkins <charles.perkins@earthlink.net>, satishnaidu80@gmail.com
Message-Id: <CC8DB2AB-EBA8-4FED-A667-277E1639313B@imt-atlantique.fr>
References: <SN4PR2101MB07342E73E66510570E7D306495B60@SN4PR2101MB0734.namprd21.prod.outlook.com> <13FBBD0C-CCF0-4315-B497-E40DEBF4A867@imt-atlantique.fr> <006301d42318$fd3a2320$f7ae6960$@cdac.in>
To: Lijo Thomas <lijo@cdac.in>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/Vqd-ZlWLcI0Z327V4-WYExZN6TY>
Subject: Re: [6lo] working group last call (wg lc) on https://datatracker.ietf.org/doc/draft-ietf-6lo-deadline-time/
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2018 08:19:10 -0000

Hello Lijo,

Thank you so much for your detailed comments. I appreciate it very much.
I am happy with your response, I just have one last clarification point, see below:


> On Jul 24, 2018, at 09:38, Lijo Thomas <lijo@cdac.in> wrote:
> 
> Dear Georgios,
>  
> Thanks for your valuable suggestions and we really appreciate for taking your valuable time for the review .
>  
> Please find our comments inline below marked as (*** [LT]) 
>  
> We will be happy to receive your further inputs !!!
>  
>  
> Thanks & Regards, <>
> Lijo Thomas 
> 
>  
> From: <> 6lo [mailto:6lo-bounces@ietf.org <mailto:6lo-bounces@ietf.org>] On Behalf Of Georgios Z. Papadopoulos
> Sent: 17 July 2018 21:40
> To: lijo@cdac.in <mailto:lijo@cdac.in>
> Cc: draft-ietf-6lo-deadline-time@ietf.org <mailto:draft-ietf-6lo-deadline-time@ietf.org>; anand@ece.iisc.ernet.in <mailto:anand@ece.iisc.ernet.in>; Malati Hegde; Samita Chakrabarti; Gabriel Montenegro; lo; Charlie Perkins; satishnaidu80@gmail.com <mailto:satishnaidu80@gmail.com>
> Subject: Re: [6lo] working group last call (wg lc) on https://datatracker.ietf.org/doc/draft-ietf-6lo-deadline-time/ <https://datatracker.ietf.org/doc/draft-ietf-6lo-deadline-time/>
>  
> Dear Lijo and co-authors,
>  
> I went through the draft, please find my comments below:
> — — 
>  
> High level comments:
> */ [GP] The draft defines the Deadline Time (DT), but it is not clear to me how the arrival of the datagram within this pre-defined DT period is guaranteed?
> Indeed, the draft provides the necessary DT information, however, the only action I could observe is the delay-sensitive datagram to be dropped if the indicated DT is elapsed.
>  
>  
> *** [LT] Yes, the Deadline Time (DT) specifies the maximum allowable delay
> before which the packet should be delivered to the destination. The proposed
> draft provides a mechanism for transporting the DT information. By incorporating
> deadline based scheduling/routing mechanisms within the intermediate nodes
> using DT, one could guarantee deterministic behavior in terms of delay. 


[GP] Would you agree that this draft do not guarantees deterministic behavior in terms of delay, but it provides
the information of maximum allowable delay for a packet to be delivered to the destination?

To be more precise, for instance, lets us consider the following multi-hop network A—> B —> C.
According this draft, it will required 2 timeslots (or 20ms) for a packet to be delivered at the DODAG Root C.
However, if there is an external interference from A to B, then A may need to retransmit multiple times
in order the datagram to be received by B. Then there are two options according to the draft:
a) the datagram is dropped, to reduce the traffic, energy consumption.
b) the datagram is delivered even if the deadline time is crossed, i.e., as you said in your e-mail “in some scenarios where the intention is also to know the total delay experienced by the packets in a network”

In both bases, a and b, there is no guarantee that the datagram will be delivered in predefined time, i.e., in deterministic behavior. 

— — 
Thank you so much,
Georgios

____________________________________

Georgios Z. Papadopoulos, Ph.D.
Associate Professor, IMT Atlantique, Rennes

web: 	 www.georgiospapadopoulos.com <http://www.georgiospapadopoulos.com/>
twitter: 	@gzpapadopoulos <https://twitter.com/gzpapadopoulos?ref_src=twsrc%5Etfw&ref_url=http://georgiospapadopoulos.com/>
____________________________________