IETF Logo Mail Archive

Re: [6lo] Working Group call for adoption on draft-lijo-6lo-expiration-time

Rashid Sangi <sangi_bahrian@yahoo.com> Wed, 25 October 2017 10:08 UTC

Return-Path: <sangi_bahrian@yahoo.com>
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 725F113B261 for <6lo@ietfa.amsl.com>; Wed, 25 Oct 2017 03:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.31
X-Spam-Level:
X-Spam-Status: No, score=0.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 qO8y9VhndgSB for <6lo@ietfa.amsl.com>; Wed, 25 Oct 2017 03:08:22 -0700 (PDT)
Received: from sonic317-36.consmr.mail.ne1.yahoo.com (sonic317-36.consmr.mail.ne1.yahoo.com [66.163.184.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C32B13B29C for <6lo@ietf.org>; Wed, 25 Oct 2017 03:08:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1508926094; bh=kHxo0+zFIDp55zcpGrs84H58nOebxwcUf/PMC3IuD4w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=C+A2/EgBRexu12yFFuTVHOf2FdBbT+aFhJCIFmueDs2W8yGO2iUJlPKbrft4G3iD2GSDApiV9sBoTG6ht0++tAhEolHLVezzIHx+cw9uAuuKb+H4pHmrDGwJndYJzIWzp2u6xIaJNG1oI5EFbMrYGsgIu117brW7Ugn5vQrGLBKNzN689cyGEjrI1zRrM7LX+uZoSE4G0kzSuppois2ox/HLPLHp0cJugNYTE+WldaVN4wa0qRvNef2iHjb+A9fyAs4Ncbn52aaTy8eWEa2Qa5rMu37SBMVbZzhGBj2tMZu/iTJqR4uTebMIMFkF1fnPsFvyuGM/yuxnvWMo8hiuxg==
X-YMail-OSG: cdBwLigVM1kjyhi01CZ39lQpdcXCI6pZwP3kH0aqDUIfhTvB4coBNEZQFBlDYu4 Cr1BMeq4IqOssb3l_KwoURhH6jM65nzp.WqrgD8F51qHzyxubsSslQyM5885q_s.P2MDHNzwKlj8 a4pfhPSDnoe1DWLJuyq8FFC.asSYnkcNFNXKcbYINjCjsKhBUFiLAC5fqoeH2mMJo4_veK.FhHbF KHD4wqjC3oIIjZPi.xqUfT5rvKQ44SW2Pj9kVRN_aX.AWbljIltbp4dLgUklrYMFy_s.GITCTZMh pykasG6ZID44zRuoXYjUggdFU.carJp4mlLdjqgpXPrbNTggivjo0RM5fGDm4aEAaNziiVpWwPQN SaziSJSZe43KIJkV0UBMShCBK0MXwjSYRGtKKsWJAbaMy.cHoGv1_oyeVwPPmv38v.aRvps1bgW5 15p2Sogla4NwLsdWacDbrllZW_xkXsG9vc4J6JDh1JEmr9DlXLeqVHiFR
Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.ne1.yahoo.com with HTTP; Wed, 25 Oct 2017 10:08:14 +0000
Date: Wed, 25 Oct 2017 10:07:12 +0000
From: Rashid Sangi <sangi_bahrian@yahoo.com>
Reply-To: Rashid Sangi <sangi_bahrian@yahoo.com>
To: "6lo@ietf.org" <6lo@ietf.org>
Cc: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, Samita Chakrabarti <samitac.ietf@gmail.com>
Message-ID: <2007061243.4012133.1508926032795@mail.yahoo.com>
In-Reply-To: <CAAdgstSq+oLqXMrzJKQy170nT1YoT52PdCR+de3bB1FCOgE3dg@mail.gmail.com>
References: <BY2PR21MB00817D3CC9BBE891BAC14F8595470@BY2PR21MB0081.namprd21.prod.outlook.com> <4552F0907735844E9204A62BBDD325E7AAEC603A@NKGEML515-MBS.china.huawei.com> <0045a46aca1041af98c992cbba0e90f0@XCH-RCD-001.cisco.com> <00d801d34d71$80f63a60$82e2af20$@cdac.in> <CAAdgstSq+oLqXMrzJKQy170nT1YoT52PdCR+de3bB1FCOgE3dg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_4012132_215121207.1508926032788"
X-Mailer: WebService/1.1.10801 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/lfz4d1yoUSyPmFKBABHfcz0HH6I>
Subject: Re: [6lo] Working Group call for adoption on draft-lijo-6lo-expiration-time
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 25 Oct 2017 10:08:24 -0000

Hi Chairs and all,
I support this work to get adopted.
Regards,Rashid Sangi.

      From: Tengfei Chang <tengfei.chang@inria.fr>
 To: Shalu <shalur@cdac.in> 
Cc: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>; Samita Chakrabarti <samitac.ietf@gmail.com>; 6lo@ietf.org
 Sent: Wednesday, October 25, 2017 5:20 PM
 Subject: Re: [6lo] Working Group call for adoption on draft-lijo-6lo-expiration-time
   
Hi,
I support the adoption of this work. 
Tengfei
On Wed, Oct 25, 2017 at 11:13 AM, Shalu <shalur@cdac.in> wrote:

Hi all,  +1. As an implementer of the draft in OpenWSN platform, I support the adoption. The packet expiration will help in meeting delay constraints in a deterministic network. For real time applications, the expiration time information will help not only in making delay sensitive scheduling decisions, but also discard those packets which have crossed the deadline thereby saving bandwidth and energy in a LLN.  Thanks & RegardsShalu  From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
Sent: Tuesday, October 24, 2017 7:00 PM
To: Zhangmingui (Martin); Gabriel Montenegro; 6lo@ietf.org; Samita Chakrabarti
Cc: draft-lijo-6lo-expiration- time@ietf.org
Subject: Re: [6lo] Working Group call for adoption on draft-lijo-6lo-expiration-time +1. We still have to agree on the complete scope of the document but this is a great start. From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Zhangmingui (Martin)
Sent: mardi 24 octobre 2017 11:17
To: Gabriel Montenegro <Gabriel.Montenegro@microsoft. com>; 6lo@ietf.org; Samita Chakrabarti <samitac.ietf@gmail.com>
Cc: draft-lijo-6lo-expiration- time@ietf.org
Subject: Re: [6lo] Working Group call for adoption on draft-lijo-6lo-expiration-time Hi, I read the draft and found the new 6LoRH Type is useful. Support for adoption. Thanks,Martin From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Gabriel Montenegro
Sent: Tuesday, October 24, 2017 8:40 AM
To: 6lo@ietf.org; Samita Chakrabarti
Cc: draft-lijo-6lo-expiration- time@ietf.org
Subject: [6lo] Working Group call for adoption on draft-lijo-6lo-expiration-time Hi Folks, This document has been discussed at face to face meetings as well as on the list.  https://datatracker.ietf.org/ doc/draft-lijo-6lo-expiration- time/  There is some reasonable interest and an implementation in OpenWSN. Per the last meeting, after a revision we would issue a call for adoption, and are pursuing now. Please send your opinion (for or against) to the mailing list on adopting this document as a 6lo WG document. This call for adoption will end at 00:00 UTC on November 6, 2017. Regards, Chairs 
------------------------------ ------------------------------ ------------------------------ ------------------------------ -------
[ 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.
------------------------------ ------------------------------ ------------------------------ ------------------------------ -------
______________________________ _________________
6lo mailing list
6lo@ietf.org
https://www.ietf.org/mailman/ listinfo/6lo





-- 
Chang Tengfei,Pre-Postdoctoral Research Engineer, Inria_______________________________________________
6lo mailing list
6lo@ietf.org
https://www.ietf.org/mailman/listinfo/6lo

v2.23.0 | Report a Bug | By Email