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

"Lijo Thomas" <lijo@cdac.in> Tue, 24 July 2018 09:03 UTC

Return-Path: <lijo@cdac.in>
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 5647B131056; Tue, 24 Jul 2018 02:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 pIuzLL20Mzke; Tue, 24 Jul 2018 02:03:48 -0700 (PDT)
Received: from mailsender.cdac.in (mailsender.cdac.in [196.1.113.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FE87131051; Tue, 24 Jul 2018 02:03:47 -0700 (PDT)
Received: from ims.pune.cdac.in (ims.pune.cdac.in [10.208.1.15]) by mailsender.cdac.in (8.14.2/8.14.2) with ESMTP id w6O92lJK008141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 24 Jul 2018 14:32:52 +0530
Received: from mailgw.pune.cdac.in ([10.208.1.4]) by ims.pune.cdac.in (8.14.4/8.14.4) with ESMTP id w6O92dIq027650; Tue, 24 Jul 2018 14:32:39 +0530
X-AuthUser: lijo
Received: from LijoPC (lijo_new_pc.tvm.cdac.in [10.176.10.234]) (authenticated bits=0) by mailgw.pune.cdac.in (8.14.2/8.13.8) with ESMTP id w6O92WNa020459 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 24 Jul 2018 14:32:35 +0530
From: Lijo Thomas <lijo@cdac.in>
To: "'Georgios Z. Papadopoulos'" <georgios.papadopoulos@imt-atlantique.fr>
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
References: <SN4PR2101MB07342E73E66510570E7D306495B60@SN4PR2101MB0734.namprd21.prod.outlook.com> <13FBBD0C-CCF0-4315-B497-E40DEBF4A867@imt-atlantique.fr> <006301d42318$fd3a2320$f7ae6960$@cdac.in> <CC8DB2AB-EBA8-4FED-A667-277E1639313B@imt-atlantique.fr>
In-Reply-To: <CC8DB2AB-EBA8-4FED-A667-277E1639313B@imt-atlantique.fr>
Date: Tue, 24 Jul 2018 14:34:57 +0530
Message-ID: <002701d4232d$68fb7f00$3af27d00$@cdac.in>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01D4235B.82B604F0"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQHi7ifeHzwJdAbh3UI9dbovTKK1tgJLIco5AiSGZuQCwUDGYqRG8MaQ
Content-Language: en-in
X-CDAC-PUNE-MailScanner-ID: w6O92dIq027650
X-CDAC-PUNE-MailScanner: Found to be clean, Found to be clean
X-CDAC-PUNE-MailScanner-MCPCheck-IMS: MCP-Clean, MCP-Checker (score=0, required 1)
X-CDAC-PUNE-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-0.198, required 6, autolearn=disabled, ALL_TRUSTED -1.00, BAYES_50 0.80, HTML_MESSAGE 0.00, URIBL_BLOCKED 0.00), not spam, SpamAssassin (not cached, score=-2.539, required 6, autolearn=disabled, ALL_TRUSTED -1.80, BAYES_20 -0.74, HTML_MESSAGE 0.00)
X-CDAC-PUNE-MailScanner-Information: Please contact npsfhelp@cdac.in/mailadmin@cdac.in for more information
X-MailScanner-ID: w6O92lJK008141
X-CDAC-PUNE-MailScanner-From: lijo@cdac.in
X-CDAC-MailScanner-Spam-Status: No
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/YTiJnNgPdPZrKpj0eYEbc9wHkd8>
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 09:03:54 -0000

Dear Georgios,

 

Thanks for the feedback, responding to your query : 

 

Deadline Time (DT) by itself does not guarantee deterministic behaviour, but its information enables intermediate nodes to implement delay sensitive scheduling and routing algorithms towards achieving deterministic behaviour.

 

As a use case application of our draft,  we implemented a basic EDF policy in OpenWSN 6tisch stack. 

 

Please find the link for our openwsn implementation

 

https://github.com/openwsn-berkeley/openwsn-fw/tree/develop/openapps/uexpiration

 

 

Thanks & Regards,

Lijo Thomas 

 

From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Georgios Z. Papadopoulos
Sent: 24 July 2018 13:49
To: Lijo Thomas
Cc: draft-ietf-6lo-deadline-time@ietf.org; anand@ece.iisc.ernet.in; Malati Hegde; Samita Chakrabarti; Gabriel Montenegro; lo; Charlie Perkins; satishnaidu80@gmail.com
Subject: Re: [6lo] working group last call (wg lc) on https://datatracker.ietf.org/doc/draft-ietf-6lo-deadline-time/

 

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 <mailto: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:  <mailto:lijo@cdac.in> lijo@cdac.in
Cc:  <mailto:draft-ietf-6lo-deadline-time@ietf.org> draft-ietf-6lo-deadline-time@ietf.org;  <mailto:anand@ece.iisc.ernet.in> anand@ece.iisc.ernet.in; Malati Hegde; Samita Chakrabarti; Gabriel Montenegro; lo; Charlie Perkins;  <mailto:satishnaidu80@gmail.com> 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/> 

____________________________________

 

 

 


-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------