On Wed, Apr 30, 2008 at 10:51 AM, Vlado Handziski <[EMAIL PROTECTED]> wrote: > On Wed, Apr 30, 2008 at 6:52 PM, Matt Welsh <[EMAIL PROTECTED]> wrote: > > > I think we're on the same page here but there are some details to work > > out. > > > > Anything in "tos" could be assigned an AM ID range by the net2 WG. The > > question is how do things move from "contrib", "apps", etc. to "tos"? > > An example might be a new timesync protocol that someone develops and > > wants to be part of the official release (by which I mean, in "tos"). > > There needs to be a clear way for someone to (a) get their code in > > there and (b) get the AM IDs assigned for it. Being a member of the > > net2 WG is one way to do that, but I would hope there are other > > avenues that permit inclusion of third-party protocols as part of the > > standard tree. > > > > > > The current policy on this is that code should move into the core only via > the TEP process. The TEPs are reviewed by the corresponding WGs, but anyone > in the community is free to write a TEP and submit it for review. >
Right. And if the protocol wants to be a part of net2 protcols, we would like the contributor/maintainer to be a member of net2 because net2, as a group, will be responsible for supporting the protocol. Garbage collection will get triggered if net2 loses that official maintainer for that piece of software and can not find a new person to support the software. In summary, at least until now, net2's policy has been to put the TEP in the standards track and software in the release track only through membership in the group. For TEP, I can see the value of being more flexible with this policy because someone could submit a TEP with some nice observations about some protocols or best practices in network protocol which we would be happy to sponsor. Back to AM IDs - the various entities involved are: protocols that are distributed with the core, protocols with assigned AM IDs, protocols that are in contrib, applications and protocols in apps, and finally applications and protocols "users" want to write and test for their experiments and deployments. For the protocols that are distributed with the core (lib/net), it is clear that we want ID allocation and they MUST not conflict. The applications and protocols in apps directory distributed with the core, should probably also use allocated IDs. What to do with the protocols in contrib? Although we don't want to patrol, it would be good provide some guidelines for these protocols and applications too. For the user applications and protocols, it is clear that they should use the unassigned addresses. Can there be an "official" protocol with an assigned ID that is not a member of one of these four classes of applications and protocols? - om_p _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
