[Tinyos Core WG] RFC model
Philip Levis
pal at cs.stanford.edu
Sun Oct 15 21:07:40 PDT 2006
On Oct 13, 2006, at 2:45 PM, Vlado Handziski wrote:
> After looking at the PEP process (no procedure for fixing the PEP
> after it is in final state, can only be obsoleted like the RFCs)
> and thinking about this a bit more, I agree with Phil's position
> that we should stick with the same model with the following additions.
>
> To handle the problem of finding the relationship between the
> original and changed TEPs, I propose the following steps:
>
> 1. We declare the TEP metadata part not to be protected by the
> "final" state
> 2. We introduce a new metadata attributes: obsoletes and extends
> 3. The new TEP has to reference the obsoleted/extended TEP in the
> metadata
> 4. Upon finalization of the new TEP, the old TEP's _metadata_ will
> be changed to state: obsoleted by/extended by: new_TEP number
>
This all sounds reasonable to me. The current TEP 1 does not go into
this, and I think your specification is nice and crisp.
Phil
More information about the Tinyos-2.0wg
mailing list