[Tinyos Core WG] RFC model

[Kevin Klues]

I liked Vlado's suggestion of versioning finalized documents.  That
would mean that if the first "final" version had some small spelling
errors or required clarifications they could be added without
requriing an entirely new TEP to be created.  If there is a drastic
change, however, a new TEP can be issued that obsoletes an old one in
the same fashion as the RFCs.

Kevin

On 10/13/06, Philip Levis <pal at cs.stanford.edu> wrote:
> RFCs are finalized documents; they don't change. If an RFC needs
> significant changes, then you issue a new RFC that obsoletes the
> earlier one. If you look back in FTP, for example, you can see that
> the original FTP RFC did not use TCP. If it needs minor changes, then
> you can always issue a supplemental RFC (documentary or informational).
>
> As for spelling errors, there is an RFC editor. So, as with a book,
> if there's a spelling error you live with it.
>
> As for small wording changes or clarification, this can be
> problematic. E.g.:
>
> -----------
> If a platform has more than one link layer, it SHOULD define each of the
> message_t fields to be a union of the underlying link layer structures.
>
> vs
>
> If a platform has more than one link layer, it SHOULD define each of the
> message_t fields to be a union of the underlying link layer structures.
> This ensures that enough space is allocated for all underlying link
> layers.
> ------------
>
> The latter suggests the basis for the SHOULD and therefore changes
> the tone of what someone ought to consider before not following it.
>
> Phil
> _______________________________________________
> Tinyos-2.0wg mailing list
> Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>


-- 
~Kevin