[Tinyos-devel] Fwd: Request for Comments: TEP 123 - Collection Tree Protocol

[Martín René]

That  scenario could be addressed with standardized access to the routing
tables and internal status even if it isn't a complete solution but it could
work.
Besides you can always add that information yourself (like MVIZ)

Saludos

Felices Fiestas!

Martín René Vilugrón
San Carlos de Bariloche
Patagonia Argentina


On Thu, Dec 11, 2008 at 1:41 PM, Omprakash Gnawali <gnawali at usc.edu> wrote:

> Yes, we thought about this scenario. You see a few of these proposals
> in the literature and TinyDB also did something similar - I am not
> sure how well it worked. Our focus is on a practical protocol so we
> could not say if hop-count based duty-cycling is feasible for the
> protocols that can change parents at a given rate. If there is
> evidence otherwise, we are open to putting the hop-count in the
> routing frame.
>
> - om_p
>
> On Thu, Dec 11, 2008 at 8:33 AM, Andreas Köpke <koepke at tkn.tu-berlin.de>
> wrote:
> > I could imagine one application: if we want to make the duty cycle
> dependent
> > on the hop count to the destination.
> > But that might be a bit artificial.
> > Best, Andreas
> >
> > Omprakash Gnawali wrote:
> >> One of the discussions we had was if we wanted a hop-count field in
> >> the frames. We decided not to include it because we could not a
> >> compelling reason to include it. If people have an opinion on this
> >> one, it would be good to hear. Without a good X in "I could not do X
> >> without hop count in the frames and I need to do X in my application",
> >> it does not make sense to include hop count.
> >>
> >> - om_p
> >>
> >> On Mon, Dec 8, 2008 at 11:40 AM, Jonathan Hui <jwhui at cs.berkeley.edu>
> wrote:
> >> > TinyOS Developers,
> >> >
> >> > I have been asked to shepherd TEP 123 (The Collection Tree Protocol).
> >> > As the title suggests, TEP 123 documents the Collection Tree Protocol
> >> > (CTP), which provides a best-effort anycast datagram communication
> >> > service to one or more root nodes.
> >> >
> >> > Getting feedback from TinyOS developers is an essential part of the
> >> > TEP process. If you have any comments or suggestions for improving TEP
> >> > 123, please email them to me (or the list) by Tuesday, December 23rd,
> >> > 2008. After the review period, I will work with the authors to ensure
> >> > that each of the comments are addressed before TEP 123 is finalized.
> >> >
> >> > The current draft of TEP 123 can be found at:
> >> >
> http://tinyos.cvs.sourceforge.net/viewvc/tinyos/tinyos-2.x/doc/txt/tep123
> >> >.txt?revision=1.13&view=markup
> >> >
> >> > --
> >> > Jonathan Hui
> >> > _______________________________________________
> >> > Tinyos-devel mailing list
> >> > Tinyos-devel at millennium.berkeley.edu
> >> >
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
> >>
> >> _______________________________________________
> >> Tinyos-devel mailing list
> >> Tinyos-devel at millennium.berkeley.edu
> >>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
> >
> >
>
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20081211/be65604d/attachment.htm