Congratulations :-)
2017-07-09 9:34 GMT+02:00 tengfei.chang :
> That's great news! Thanks a lot!
>
>
>
> Sent from my Mi phone
> On Jonathan Muñoz , Jul 9, 2017 9:27 AM wrote:
>
> Hello all,
>
> Just to inform you that Wireshark has been updated
Hello Yasuyuki,
Le ven. 23 juin 2017 à 10:10, Yasuyuki Tanaka
a écrit :
> Development versions would have; they are available at the following page.
>
> https://www.wireshark.org/download/automated/
Thanks :-) I didn't know this existed :-)
> While I'm working
I'm going to add 6LoRH as requirement to implement for the td.
Le mer. 21 juin 2017 à 12:07, Thomas Watteyne a
écrit :
> +1
>
> There is only 1-2 tests that require multi-hop.
>
> On Tue, Jun 20, 2017 at 1:44 PM, Xavi Vilajosana Guillen <
> xvilajos...@uoc.edu> wrote:
ransaction before 6N2 and locked the
> resources. Note that the request message lock the resources.
>
> I want to hear other view as well about this.
>
> regards,
> X
>
> 2017-06-19 18:14 GMT+02:00 Remy Leone <remy.le...@inria.fr>:
>
>> If it is a concurrent
Hello,
I got a question about 6P04:
obj: Check that concurrent transaction cannot request for the same cells
in the schedule according to draft-ietf-6tisch-6top-protocol-05
cfg: star
ref: IEEE802.15.4-2015, draft-ietf-6tisch-6top-protocol-05
pre:
- The DAGroot sends EBs periodically,
;
>>>> It says a ping echo request packet is used to test the timing template.
>>>> I think we shouldn't use layer 3 packets to test layer 2 behaviors.
>>>>
>>>> What other layer 2 packet can we use for this test? keep alive packet
>>>> can
Hello,
I created a pull request containing the test descriptions program for the
next plugfest.
https://bitbucket.org/6tisch/td-6tisch/pull-requests/5/ietf99/diff
It's the first draft.
It will be discussed on Friday and the final one will be published on June
15th.
Once this list of test
Hello,
I've reviewed the 6TiSCH test description and I got some suggestions that
I've written as issues:
https://bitbucket.org/6tisch/td-6tisch/issues?status=new=open
Could you please comment, open new issues if you see some. My goal is to
have as many test descriptions phrased with Falsifiable
ues directly
> through the tracker rather than the ML, but would very much appreciate if
> you could keep the WG updated with major developments.
> Thomas
>
> On Wed, May 3, 2017 at 4:18 PM, Remy Leone <remy.le...@inria.fr> wrote:
>
>> No problem.
>> I've activated
at sounds great. Having a CI keeping an up-to-date version of the PDF
> version at all times seems like the best of all worlds. Thanks for doing
> the conversion exercise!
>
> On Wed, May 3, 2017 at 3:21 PM, Remy Leone <remy.le...@inria.fr> wrote:
>
>> I would like to use
l
> files into e.g. a PDF version of the TD?
>
> On Wed, May 3, 2017 at 3:06 PM, Remy Leone <remy.le...@inria.fr> wrote:
>
>> Hello,
>>
>> I've just pushed a first version of the 6TiSCH test description in the
>> following repository:
>>
>> htt
Hello,
I've just pushed a first version of the 6TiSCH test description in the
following repository:
https://bitbucket.org/6tisch/td-6tisch
I've used the content present in the test description document provided by
ETSI during 6TiSCH plugtest events.
Using a git-based workflow to change those
écrit :
> Hi Remy,
>
> Regarding to your question on 4.2.6. 6P CellOptions, the first column is
> the cell's type from node A's point of view, and the second column is the
> cell's type from node B's point of view. Does it make sense?
>
> Thanks
> Qin
>
>
> On Thursda
Hello,
I got a bunch of remarks about the 6P draft
https://tools.ietf.org/html/draft-ietf-6tisch-6top-protocol-03
*4.1.1. 2-step 6top Transaction*
*4.1.2. 3-step 6top Transaction*
Maybe it would be nice to add at the end of the workflow that if the
transaction was successful, the schedule
14 matches
Mail list logo