Re: [6tisch] T: FW: I-D Action: draft-satish-6tisch-6top-sf1-00.txt
"S.V.R.Anand" <anand@ece.iisc.ernet.in> Thu, 09 June 2016 18:35 UTC
Return-Path: <anand@ece.iisc.ernet.in>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E52912D82B for <6tisch@ietfa.amsl.com>; Thu, 9 Jun 2016 11:35:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.026
X-Spam-Level:
X-Spam-Status: No, score=-4.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-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 g2G-5k7jzcM8 for <6tisch@ietfa.amsl.com>; Thu, 9 Jun 2016 11:35:39 -0700 (PDT)
Received: from relay.iisc.ernet.in (relay.iisc.ernet.in [203.200.35.65]) by ietfa.amsl.com (Postfix) with SMTP id 64D5D12D7B9 for <6tisch@ietf.org>; Thu, 9 Jun 2016 11:35:37 -0700 (PDT)
Received: from ece.iisc.ernet.in (mail.ece.iisc.ernet.in [10.32.1.10]) by relay.iisc.ernet.in (Postfix) with ESMTP id 0D25AAE3163; Fri, 10 Jun 2016 00:05:24 +0530 (IST)
Received: from [10.3.1.181] ([10.3.1.181]) by ece.iisc.ernet.in (8.14.7/8.14.7) with ESMTP id u59IaK8D002202; Fri, 10 Jun 2016 00:06:20 +0530
To: "Satish Anamalamudi (Satish Anamalamudi)" <satish.anamalamudi@huawei.com>, Lijo Thomas <lijo@cdac.in>, "6tisch@ietf.org" <6tisch@ietf.org>
References: <BC1182E86737A7438C540E3B93DB7E5120B6BE9E@SZXEMI507-MBS.china.huawei.com> <006a01d1c249$11cfb080$356f1180$@cdac.in> <BC1182E86737A7438C540E3B93DB7E5120B6CA73@SZXEMI507-MBS.china.huawei.com>
From: "S.V.R.Anand" <anand@ece.iisc.ernet.in>
Message-ID: <5759B6E4.6070508@ece.iisc.ernet.in>
Date: Fri, 10 Jun 2016 00:05:16 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <BC1182E86737A7438C540E3B93DB7E5120B6CA73@SZXEMI507-MBS.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------030203020109070703080207"
X-IISc-MailScanner-Information: Please contact nethelp@serc.iisc.in for more information
X-IISc-MailScanner-ID: 0D25AAE3163.A6A68
X-IISc-MailScanner: Found to be clean
X-IISc-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.314, required 6.5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, HTML_MESSAGE 0.00, NO_RDNS2 0.01, RP_MATCHES_RCVD -1.43, URIBL_BLOCKED 0.00)
X-IISc-MailScanner-From: anand@ece.iisc.ernet.in
MailScanner-NULL-Check: 1466102124.48013@7lCDe+0yGrp5VaqYEi48hw
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/8r468FxorVCgw5QnoiTPkCaal5g>
Subject: Re: [6tisch] T: FW: I-D Action: draft-satish-6tisch-6top-sf1-00.txt
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2016 18:35:43 -0000
Hi Lijo, Your question on the lifetime of a TrackID can be split into two sub-questions. One relates to the time itself, and the other is the track termination procedure. A short answer to the first is, it is application specific. The second is more involved as there are several ways of terminating a track. (i) One of the P2P end nodes can signal the PCE via a teardown message so that PCE can release the chunks allocated to the intermediate nodes during the resource reservation. The flip side of this seemingly graceful way is that if there are plenty of short-lived tracks in the network, then the network will be loaded with many control messages, not desirable in LLNs (ii) PCE automatically reclaim the chunks based on the degree of idleness based on the information obtained from NME. There is a trade-off here too. Hope the above addresses your question. Anand On Thursday 09 June 2016 06:20 PM, Satish Anamalamudi (Satish Anamalamudi) wrote: > Hello Lijo, > > Thank you for your questions. > > Main role of TrackID : > 1. Track forwarding is very similar to IP forwarding where each and every hop is related to local Track-ID (like IP address) to switch the tracks towards Destination. Later, cells are used as implicit labels to switch it to next-hop cells of associated Track-ID. > 2. To identify the associated L2-bundles at each and every hop to forward the data to next-hop neighbors and dynamically adapt the cells in associated L2-bundles. > > As of now I don't have exact answer for "Life time of a TrackID". I will message to you very soon once I know the answer for it. > > With Regards, > Satish. > -----®öö----- > Ñöº: Lijo Thomas [mailto:lijo@cdac.in] > Ñöô: 2016t69å 20:19 > 6öº: Satish Anamalamudi (Satish Anamalamudi); 6tisch@ietf.org > ;: RE: [6tisch] FW: I-D Action: draft-satish-6tisch-6top-sf1-00.txt > > Hi Satish, > > I have a couple of queries regarding the SF1 draft . > > 1. In the draft it says a TrackID is generated for each 1 hop communication. > I had a feeling that the TrackID remains the same for an end-to-end packet flow. Please correct me if I am wrong > > 2. Life time of a TrackID > > Hope these are relevant to your draft : > > Thanks & Regards, > Lijo Thomas > > > -----Original Message----- > From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Satish Anamalamudi (Satish Anamalamudi) > Sent: 06 June 2016 15:31 > To: 6tisch@ietf.org > Subject: [6tisch] FW: I-D Action: draft-satish-6tisch-6top-sf1-00.txt > > Hello everyone, > > A new draft is proposed for hop-by-hop scheduling through Scheduling Function One(SF1). Your comments are highly appreciated. > > With Regards, > Satish. > >> -----Original Message----- >> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of >> internet-drafts@ietf.org >> Sent: 2016t66å 17:54 >> To: i-d-announce@ietf.org >> Subject: I-D Action: draft-satish-6tisch-6top-sf1-00.txt >> >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> >> >> Title : Scheduling Function One (SF1) for hop-by-hop >> Scheduling in 6tisch Networks >> Authors : Satish Anamalamudi >> Mingui Zhang >> Charles E. Perkins >> S.V.R Anand >> Filename : draft-satish-6tisch-6top-sf1-00.txt >> Pages : 10 >> Date : 2016-06-06 >> >> Abstract: >> This document defines a 6top Scheduling Function called "Scheduling >> Function One" (SF1) to schedule end-to-end dedicated L2-bundles hop- >> by-hop for each instance. In addition, SF1 dynamically adapts the >> number of reserved cells in scheduled end-to-end L2-bundles of an >> ongoing instance through a Resource Reservation Protocol. SF1 uses >> the 6P signaling messages with a TrackID to add/delete cells in end- >> to-end L2-bundles of each instance. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-satish-6tisch-6top-sf1/ >> >> There's also a htmlized version available at: >> https://tools.ietf.org/html/draft-satish-6tisch-6top-sf1-00 >> >> >> Please note that it may take a couple of minutes from the time of >> submission until the htmlized version and diff are available at >> tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> I-D-Announce mailing list >> I-D-Announce@ietf.org >> https://www.ietf.org/mailman/listinfo/i-d-announce >> Internet-Draft directories: http://www.ietf.org/shadow.html or >> ftp://ftp.ietf.org/ietf/1shadow-sites.txt > _______________________________________________ > 6tisch mailing list > 6tisch@ietf.org > https://www.ietf.org/mailman/listinfo/6tisch > > > ------------------------------------------------------------------------------------------------------------------------------- > [ 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. > ------------------------------------------------------------------------------------------------------------------------------- > > _______________________________________________ > 6tisch mailing list > 6tisch@ietf.org > https://www.ietf.org/mailman/listinfo/6tisch
- [6tisch] FW: I-D Action: draft-satish-6tisch-6top… Satish Anamalamudi (Satish Anamalamudi)
- Re: [6tisch] FW: I-D Action: draft-satish-6tisch-… Lijo Thomas
- [6tisch] 答复: FW: I-D Action: draft-satish-6tisch-… Satish Anamalamudi (Satish Anamalamudi)
- Re: [6tisch] T: FW: I-D Action: draft-satish-6tis… S.V.R.Anand
- Re: [6tisch] T: FW: I-D Action: draft-satish-6tis… Lijo Thomas
- Re: [6tisch] T: FW: I-D Action: draft-satish-6tis… Xavi Vilajosana Guillén
- Re: [6tisch] T: FW: I-D Action: draft-satish-6tis… S.V.R.Anand
- [6tisch] 答复: T: FW: I-D Action: draft-satish-6tis… Satish Anamalamudi (Satish Anamalamudi)