Re: [6tsch] About the special type of event to ask PCE to create a track

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

 <https://www.ietf.org/mailman/listinfo/6tsch>