[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[INDEP] Re: Last call on draft-klensin-independent...
I did note an issue which I think could use more clarification in this document,
which is whether the Independent Submission track is solely for
publication of Informational/Experimental RFCs, or whether it can be also
used to publish BCPs or Standards track RFCs. I would like to see an
explicit statement in the document saying that the process only applies to
Informational/Experimental documents, and cannot be used for other
purposes.
RFC 3932 Section 1 says that it solely concerns "RFC Editor
documents to Experimental/ Informational" status. This implies that
the process defined in that document can't be used for Standard track
documents, but it doesn't preclude other documents from specifying such a
process. Given this, I would like to make sure that
draft-klensin-independent isn't construed as widening the applicability of
the Independent submission process beyond Informational/Experimental RFC
publication.
RFC 3932 Section 4 notes that a boilerplate should be included on the
document which says: "This RFC is not a candidate for any level of
Internet Standard", which would again seem to imply exclusion of
Standards Track documents, and possibly even Experimental documents, which
typically include a statement more along these lines:
This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind.
Since documents published as Experimental can eventually be moved onto the
standards track, while they don't specify Internet standards, they remain
candidates for consideration.
_______________________________________________
INDEPENDENT mailing list
INDEPENDENT at ietf.org
https://www1.ietf.org/mailman/listinfo/indepenFrom independent-bounces at ietf.org Thu Dec 28 14:39:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1H015m-0002RU-G5; Thu, 28 Dec 2006 14:39:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1Gze1J-00037j-9R
for independent at ietf.org; Wed, 27 Dec 2006 14:00:57 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gze1G-0004pf-2I
for independent at ietf.org; Wed, 27 Dec 2006 14:00:57 -0500
Received: from c-24-16-66-58.hsd1.mn.comcast.net ([24.16.66.58]
helo=internaut.com) by outbound.mailhop.org with esmtpa (Exim 4.63)
(envelope-from <aboba at internaut.com>) id 1Gze1D-000OhT-9J
for independent at ietf.org; Wed, 27 Dec 2006 14:00:51 -0500
Received: by internaut.com (Postfix, from userid 1000)
id 7177B65AF5; Wed, 27 Dec 2006 11:00:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
by internaut.com (Postfix) with ESMTP id 62ADD4FB0F
for <independent at ietf.org>; Wed, 27 Dec 2006 11:00:51 -0800 (PST)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.66.58
X-Report-Abuse-To: abuse at dyndns.com (see
http://www.mailhop.org/outbound/abuse.html for abuse reporting
information)
X-MHO-User: aboba
Date: Wed, 27 Dec 2006 11:00:51 -0800 (PST)
From: Bernard Aboba <aboba at internaut.com>
To: independent at ietf.org
Message-ID: <Pine.LNX.4.64.0612271045340.1096 at internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
X-Mailman-Approved-At: Thu, 28 Dec 2006 14:39:04 -0500
Subject: [INDEP] Re: Last call on draft-klensin-independent...
X-BeenThere: independent at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of RFC Editor independent submissions proposal
<independent.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
<mailto:independent-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent at ietf.org>
List-Help: <mailto:independent-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
<mailto:independent-request at ietf.org?subject=subscribe>
Errors-To: independent-bounces at ietf.org
I did note an issue which I think could use more clarification in this document,
which is whether the Independent Submission track is solely for
publication of Informational/Experimental RFCs, or whether it can be also
used to publish BCPs or Standards track RFCs. I would like to see an
explicit statement in the document saying that the process only applies to
Informational/Experimental documents, and cannot be used for other
purposes.
RFC 3932 Section 1 says that it solely concerns "RFC Editor
documents to Experimental/ Informational" status. This implies that
the process defined in that document can't be used for Standard track
documents, but it doesn't preclude other documents from specifying such a
process. Given this, I would like to make sure that
draft-klensin-independent isn't construed as widening the applicability of
the Independent submission process beyond Informational/Experimental RFC
publication.
RFC 3932 Section 4 notes that a boilerplate should be included on the
document which says: "This RFC is not a candidate for any level of
Internet Standard", which would again seem to imply exclusion of
Standards Track documents, and possibly even Experimental documents, which
typically include a statement more along these lines:
This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind.
Since documents published as Experimental can eventually be moved onto the
standards track, while they don't specify Internet standards, they remain
candidates for consideration.
_______________________________________________
INDEPENDENT mailing list
INDEPENDENT at ietf.org
https://www1.ietf.org/mailman/listinfo/independent