Re: IESG review of RFC Editor documents

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Few questions:

1. Section 4 say that "For documents that are independent of the IETF process:
This document is not a candidate for any level of Internet Standard."

Does this means that an individual submission can only be Informational only?
ie. not even experimental? If so, how does this fit into what happened in IMAA
BoF in Seoul?

(The conclusion is no working group, but wrap up and docs some of the
implementations as possibly experimental RFCs via individual submissions)

2. Section 3 talks about the various IESG responses. Most of it makes sense
but the last one: "The IESG thinks that this document extends an IETF protocol
in a way that requires IETF review, and should therefore not be published
without IETF review."

It wasn't very clear when will the above apply.

Beside, wasn't individual submission already (maybe) subjected to 4 weeks last
call? Does this qualify as 'IETF review'?

Or 'IETF review' implies review by a IETF Working Group?

-James Seng

----- Original Message ----- 
From: "Harald Tveit Alvestrand" <harald@xxxxxxxxxxxxx>
To: <ietf@xxxxxxxx>
Sent: Friday, March 26, 2004 10:51 PM
Subject: IESG review of RFC Editor documents


> The IESG has proposed a change in its present review procedures for IESG
> review of documents submitted directly to the RFC Editor for publication.
>
> The IESG will be discussing this in detail, and with the RFC Editor, next
> week - the input document for that discussion is published as an I-D below
>
> Your input is welcome!
>
> Copy of the announcement below.
>
> (note - between solutions, icar, poised and the IETF list, I chose the IETF
> list - I will post notes to the 3 other lists saying that I've asked for
> discussion of this on the IETF list.... judgment call).
>
>               Harald
>
>
>                 Harald Alvestrand
>
> ---------- Forwarded Message ----------
> Date: 25. mars 2004 15:38 -0500
> From: Internet-Drafts@xxxxxxxx
> To: IETF-Announce
> Cc: iesg@xxxxxxxx
> Subject: I-D ACTION:draft-iesg-rfced-documents-00.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Internet Engineering Steering
> Group Working Group of the IETF.
>
> Title : The IESG and RFC Editor documents: Procedures
> Author(s) : H. Alvestrand
> Filename : draft-iesg-rfced-documents-00.txt
> Pages : 6
> Date : 2004-3-25
>
> This document gives the IESG's procedures for handling documents
>    submitted for RFC publication via the RFC Editor, subsequent to the
>    changes proposed by the IESG at the Seoul IETF, March 2004.
>
>    NOTE IN DRAFT: These guidelines are proposed, not adopted. Comments
>    are welcome - please send them to iesg@xxxxxxxxx
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-iesg-rfced-documents-00.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-iesg-rfced-documents-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> mailserv@xxxxxxxxx
> In the body type:
> "FILE /internet-drafts/draft-iesg-rfced-documents-00.txt".
>
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility.  To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command.  To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader.  Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> ---------- End Forwarded Message ----------
>
>
>
>



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]