To:
"Brian W. Spolarich" <briansp@walid.com>
Cc:
"Edward Lewis" <lewis@tislabs.com>, <ietf-provreg@cafax.se>, <jaap@sidn.nl>
From:
Edward Lewis <lewis@tislabs.com>
Date:
Wed, 4 Apr 2001 12:32:03 -0400
In-Reply-To:
<IPEMICCPDPPICMIONJIOGEALCFAA.briansp@walid.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: Provreg WG Last Call announcement
Yes, in the terms that an RFC itself can't be edited. However, an RFC isn't (necessarily) the final word on a topic. So - once this document becomes an RFC, you can't comment on "it." But you can comment on the need to replace it later on. A little more clarification - a "standards track document" can ascend three levels - draft, proposed, and full. Each level has more stringent requirements. Also there is an STD series, which are RFC's that are "standards." The requirements document will likely be an informational document, which isn't standards track. See RFC 2026 for more details - a link to it is on the IETF home page. At 9:40 AM -0400 4/4/01, Brian W. Spolarich wrote: > >| It is important to note that it is never too late to comment on a >| document, even when a last call expires. (Well, once the document >| is an RFC, it is too late!) > > Really? RFC != Request For Comments? :-) > > -bws -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis NAI Labs Phone: +1 443-259-2352 Email: lewis@tislabs.com Dilbert is an optimist. Opinions expressed are property of my evil twin, not my employer.