Bruce,
Bruce Lilly wrote:
Date: 2005-03-02 07:59 From: Brian E Carpenter <brc@xxxxxxxxxxxxxx>
Bruce,
> It's unclear what the status of the document is intended to be. > I suspect it should probably be a BCP RFC.
At the risk of flamage, IMHO it shouldn't. I think we need more flexibility in operational procedures than we can get from the BCP mechanism.
Rationale for BCP: 1. I suspect we want the procedures to be readily visible to potential authors
Yes, and right there behind the "Internet Drafts" link on www.ietf.org meets that.
2. I suspect we want authors to know that the issues addressed in the guidelines have the backing of the IESG
Indeed. That can be made clear in the text.
3. The suggested IANA Considerations section implies some sort of RFC
Certainly, there's no doubt that the guidelines need to refer to BCP RFCs when approriate.
Asking for community input, and posting the resulting text on the web site, seems to give that flexibility.
Perhaps, but it is not clear that the document has any standing,
I suspect that the fact that the IESG minutes its approval of an update would serve.
noris it necessarily easy to find (*which* web site(s)?).
See above.
Would IANA take note of direction given in some random (non-RFC) document?
If we ask them to.
If there's another sort of official document for administrative procedures and guidelines, that might work; are there? If so, where does one find them?
Good question. We may need to formalize that... that operational procedures, after consensus discussion and IESG approval, are effective as soon as posted at www.ietf.org.
It's not clear what sort of flexibility would be lacking in a BCP
RFC, given that guidelines can be expressed in RFC 2119 terms "MAY",
"OPTIONAL", "RECOMMENDED", "SHOULD", and even "MUST" where
appropriate, and that BCPs can be (and are) updated when necessary.
But it takes 6 months to a year to do so.
What sort of flexibility did you have in mind?
2 week reaction time when we find a need for operational changes.
Brian
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf