Re: [6tsch] About the special type of event to ask PCE to create a track
Thomas Watteyne <watteyne@eecs.berkeley.edu> Thu, 05 September 2013 17:47 UTC
Return-Path: <twatteyne@gmail.com>
X-Original-To: 6tsch@ietfa.amsl.com
Delivered-To: 6tsch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41A6E11E825B for <6tsch@ietfa.amsl.com>; Thu, 5 Sep 2013 10:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.582
X-Spam-Level:
X-Spam-Status: No, score=-1.582 tagged_above=-999 required=5 tests=[AWL=-0.205, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2157DF8wvc42 for <6tsch@ietfa.amsl.com>; Thu, 5 Sep 2013 10:47:14 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D5C9811E8258 for <6tsch@ietf.org>; Thu, 5 Sep 2013 10:47:13 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so2135369pdj.1 for <6tsch@ietf.org>; Thu, 05 Sep 2013 10:47:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=4r2WXpOTYSsubHoq+myPOG8ZmMy7rm+WKk+fZ36A+/k=; b=tlySN4MJqwakRfSou9juim9WUlz+6DDhqFW2MFqn+teFIht35t+gmGj+6ZF5Y5yZus Hxliu+bqdAHoDmZ8N0+j2V4AeQNAE7bP06Ql2wZQruuQni18dumDVUEQdy25NAce2jB+ Z9/iz22SZ1CMZLnWxFYsNsRtf4Xat8oeEm17OxrT0CfPj+Sl99BtgtLKwxWKZrd44ZL8 7KQMBazQDrxFsd+kvweRYa5vquGthgv9psHsu0anab67sR/SqsJgLzhcWMMaxmGDkdWI HVBzqEOjrXzEiDvMmA2yORyUQm9RU1jEt0Je10iqH8JVYERXrbLOS2UgIpuHKq9GmmfG Jlng==
X-Received: by 10.66.142.107 with SMTP id rv11mr10790318pab.17.1378403233561; Thu, 05 Sep 2013 10:47:13 -0700 (PDT)
MIME-Version: 1.0
Sender: twatteyne@gmail.com
Received: by 10.66.147.193 with HTTP; Thu, 5 Sep 2013 10:46:53 -0700 (PDT)
In-Reply-To: <E045AECD98228444A58C61C200AE1BD84145A186@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD84145A186@xmb-rcd-x01.cisco.com>
From: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Date: Thu, 05 Sep 2013 10:46:53 -0700
X-Google-Sender-Auth: GqbsaQtmT8C7LJqt-Yhbn5MiuvQ
Message-ID: <CADJ9OA_EyfO-rmpi=SB0iDD1jwYv6_j0PsT2YYaOBv06d25BbA@mail.gmail.com>
To: "6tsch@ietf.org" <6tsch@ietf.org>
Content-Type: multipart/alternative; boundary="001a11331e461804ae04e5a68356"
Subject: Re: [6tsch] About the special type of event to ask PCE to create a track
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
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" <6tsch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tsch>, <mailto:6tsch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tsch>
List-Post: <mailto:6tsch@ietf.org>
List-Help: <mailto:6tsch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tsch>, <mailto:6tsch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Sep 2013 17:47:17 -0000
Pascal, Just trying to make sure I'm on the same page. The second "schedule update request" flow would come from a different entity than the mote, right? I'm thinking for example about a controller on the Internet wanting to send data to a mote, and which contacts the PCE to update the schedule accordingly. What's your example? That being said, I believe we are in line here, and I agree taht it's a good idea to merge the two "schedule update request" flow flavors. Thomas On Thu, Sep 5, 2013 at 12:25 AM, Pascal Thubert (pthubert) < pthubert@cisco.com> wrote: > Yes…**** > > ** ** > > And the aim should be to make sure that the PCE has queued the request to > build a track.**** > > That request may be served asynchronously, considering that the PCE > sometimes needs to defragment / reoptimize multiple flows, and it may stack > some requests for a short while.**** > > When the PCE is finally ready, it computes the track, and pushes it > through an action flow; but I would consider that a different flow, not an > embedded flow for the reason above.**** > > ** ** > > Makes sense?**** > > ** ** > > Pascal**** > > ** ** > > *From:* Maria Rita PALATTELLA [mailto:maria-rita.palattella@uni.lu] > *Sent:* jeudi 5 septembre 2013 09:16 > > *To:* Pascal Thubert (pthubert); Qin Wang > *Cc:* Thomas Watteyne; 6tsch@ietf.org > *Subject:* RE: [6tsch] About the special type of event to ask PCE to > create a track**** > > ** ** > > It makes sense for me. Even though they are generated by different > entities, they are both addressed to the PCE, and they have the same final > aim.**** > > Maria Rita**** > > **** > > *From:* Pascal Thubert (pthubert) [mailto:pthubert@cisco.com<pthubert@cisco.com>] > > *Sent:* Thursday, September 05, 2013 9:02 AM > *To:* Maria Rita PALATTELLA; Qin Wang > *Cc:* Thomas Watteyne; 6tsch@ietf.org > *Subject:* RE: [6tsch] About the special type of event to ask PCE to > create a track**** > > **** > > Fine with me Maria Rita,**** > > **** > > But note that there is also a flow that fits the name “schedule flow” that > is stimulated by the Net mgt Entity in the admin console as opposed to the > mt entity in the device.**** > > Same thing, this creates a req to the PCE to install a track. Do we want > to merge those 2 flows? – I think so.**** > > **** > > Cheers,**** > > **** > > Pascal**** > > **** > > *From:* Maria Rita PALATTELLA [mailto:maria-rita.palattella@uni.lu<maria-rita.palattella@uni.lu>] > > *Sent:* jeudi 5 septembre 2013 08:47 > *To:* Pascal Thubert (pthubert); Qin Wang > *Cc:* Thomas Watteyne; 6tsch@ietf.org > *Subject:* RE: [6tsch] About the special type of event to ask PCE to > create a track**** > > **** > > I agree too. If we want to cut the name shorter, maybe we can just call it > “ Schedule Flow” (removing the update).**** > > In the end, we know that this flow will happen when a node asks the PCE to > update its schedule, and add/remove cells/tracks. What do you think?**** > > Maria Rita**** > > **** > > *From:* 6tsch-bounces@ietf.org [mailto:6tsch-bounces@ietf.org<6tsch-bounces@ietf.org>] > *On Behalf Of *Pascal Thubert (pthubert) > *Sent:* Thursday, September 05, 2013 7:29 AM > *To:* Qin Wang > *Cc:* Thomas Watteyne; 6tsch@ietf.org > *Subject:* Re: [6tsch] About the special type of event to ask PCE to > create a track**** > > **** > > +1 > > Pascal**** > > > Le 5 sept. 2013 à 00:10, "Qin Wang" <qinwang@berkeley.edu> a écrit :**** > > Thomas, **** > > **** > > I think "Flow" is a process to exchange messages for a given objective. > For example, action flow consists of a Action Request from ME to 6top, and > a Execution Confirm (Succ/Fail) from 6top to ME. But, "Schedule update > request" looks like one step of a process. I would like to suggest that the > 5th flow is called "Schedule update flow", consists of a "Schedule update > request" from node to PCE, and something like "Track/cell installation" > from PCE to node.**** > > **** > > Make sense?**** > > Qin**** > > **** > > On Thu, Sep 5, 2013 at 5:29 AM, Thomas Watteyne < > watteyne@eecs.berkeley.edu> wrote:**** > > I would agree that a 5th flow makes sense, especially because it allows us > to use different transport mechanisms for the report flow (CoAP?) and this > new flows (CoAP now? maybe PCEP later?). **** > > **** > > Do what do we call this new flow? "Schedule update request" is a bit long. > **** > > **** > > Thomas**** > > **** > > On Wed, Sep 4, 2013 at 2:12 PM, Qin Wang <qinwang@berkeley.edu> wrote:**** > > Hi Thomas, **** > > **** > > Thanks for your explanation. You are saying the request packet from node > is generated by the upper layer of 6top, correct? **** > > **** > > If so, since the request packet is generated by upper layer of 6top, > instead of 6top internal events like alarm, I think it is reasonable to add > the 5th control flow.**** > > **** > > What do you think?**** > > **** > > Qin**** > > **** > > On Wed, Sep 4, 2013 at 10:12 AM, Thomas Watteyne < > watteyne@eecs.berkeley.edu> wrote:**** > > Qin, **** > > **** > > Thanks for bringing that up. Allow me to answer in Pascal's place. We are > talking about the format of the packets exchanged between the ME and the > nodes. In the centralized case, these are application-level packets, i.e. > packet generated by an entity a couple of layer above 6top. That entity > talks with the PCE over the network, and with 6top through the API > (internal to the node) as defined in > http://tools.ietf.org/html/draft-wang-6tsch-6top-00#section-2.4.**** > > **** > > If we agree on that, the question is whether the packet the node sends to > establish a new track is part of the event flow, or not. In both cases, it > would originate from this application-level entity, but possibly > transported in different ways.**** > > **** > > Thomas**** > > **** > > On Fri, Aug 30, 2013 at 11:01 AM, Qin Wang <qinwang@berkeley.edu> wrote:** > ** > > Hi Pascal, **** > > **** > > My understanding is that 6top is a passive role in dealing with cell/track > reservation. In another word, the 6top in a node can report its state, > including neighbor table, cell usage, and other statistics information, but > can not make decision on if some cells/track should be added or removed, > which should be the responsibility of PCE in centralized case or upper > layer in distributed case. Thus, I can not see when the 5th flow will be > used. Can you explain more?**** > > **** > > Thanks**** > > Qin**** > > **** > > On Sat, Aug 31, 2013 at 12:08 AM, Pascal Thubert (pthubert) < > pthubert@cisco.com> wrote:**** > > Dear all, > > We discussed at the call that the(PCEP?) request to ask for a track > establishment could be seen as an event, or could be a new flow. > At the call, I suggested that it could be a new, 5th flow. My arguments > are that this flow: > - Probably yields different data format. The demand carries and points, > end to end latency and bandwidth. That's quite specific. > - Probably yields a different flow. Events do not necessarily have a > response. > - Probably uses a different transport as well (PCEP vs. CoAP) > > What do you think? > > Pascal > _______________________________________________ > 6tsch mailing list > 6tsch@ietf.org > https://www.ietf.org/mailman/listinfo/6tsch**** > > **** > > > _______________________________________________ > 6tsch mailing list > 6tsch@ietf.org > https://www.ietf.org/mailman/listinfo/6tsch**** > > > _______________________________________________ > 6tsch mailing list > 6tsch@ietf.org > https://www.ietf.org/mailman/listinfo/6tsch**** > > **** > > **** > > > _______________________________________________ > 6tsch mailing list > 6tsch@ietf.org > https://www.ietf.org/mailman/listinfo/6tsch**** > > **** > > _______________________________________________ > 6tsch mailing list > 6tsch@ietf.org > https://www.ietf.org/mailman/listinfo/6tsch**** > >
- Re: [6tsch] About the special type of event to as… Qin Wang
- [6tsch] About the special type of event to ask PC… Pascal Thubert (pthubert)
- Re: [6tsch] About the special type of event to as… Qin Wang
- Re: [6tsch] About the special type of event to as… Thomas Watteyne
- Re: [6tsch] About the special type of event to as… Thomas Watteyne
- Re: [6tsch] About the special type of event to as… Qin Wang
- Re: [6tsch] About the special type of event to as… Pascal Thubert (pthubert)
- Re: [6tsch] About the special type of event to as… Thomas Watteyne
- Re: [6tsch] About the special type of event to as… Maria Rita PALATTELLA
- Re: [6tsch] About the special type of event to as… Pascal Thubert (pthubert)
- Re: [6tsch] About the special type of event to as… Maria Rita PALATTELLA
- Re: [6tsch] About the special type of event to as… Pascal Thubert (pthubert)
- Re: [6tsch] About the special type of event to as… Prof. Diego Dujovne
- Re: [6tsch] About the special type of event to as… Qin Wang
- Re: [6tsch] About the special type of event to as… Thomas Watteyne
- Re: [6tsch] About the special type of event to as… Thomas Watteyne
- Re: [6tsch] About the special type of event to as… Pascal Thubert (pthubert)
- Re: [6tsch] About the special type of event to as… Prof. Diego Dujovne
- Re: [6tsch] About the special type of event to as… Pascal Thubert (pthubert)