From independent-bounces@ietf.org Wed Jan 03 07:35:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H25Kp-0001gG-DU; Wed, 03 Jan 2007 07:35:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H25Kn-0001gB-TE
	for independent@ietf.org; Wed, 03 Jan 2007 07:35:09 -0500
Received: from mtagate6.uk.ibm.com ([195.212.29.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H25Kl-0002pC-EB
	for independent@ietf.org; Wed, 03 Jan 2007 07:35:09 -0500
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate6.uk.ibm.com (8.13.8/8.13.8) with ESMTP id l03CZ5FP224640
	for <independent@ietf.org>; Wed, 3 Jan 2007 12:35:05 GMT
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com
	[9.149.37.212])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with
	ESMTP id l03CZ5gR1884202
	for <independent@ietf.org>; Wed, 3 Jan 2007 12:35:05 GMT
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av01.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l03CZ5u9027789
	for <independent@ietf.org>; Wed, 3 Jan 2007 12:35:05 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d06av01.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l03CZ5Hr027782; Wed, 3 Jan 2007 12:35:05 GMT
Received: from [9.4.210.68] ([9.4.210.68])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id NAA234994; 
	Wed, 3 Jan 2007 13:35:04 +0100
Message-ID: <459BA2FA.6090500@zurich.ibm.com>
Date: Wed, 03 Jan 2007 13:35:06 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
Subject: Re: [INDEP] Re: Last call on draft-klensin-independent...
References: <Pine.LNX.4.64.0612271045340.1096@internaut.com>
In-Reply-To: <Pine.LNX.4.64.0612271045340.1096@internaut.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

On 2006-12-27 20:00, Bernard Aboba wrote:
> 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.

It would do no harm, but since RFC 2026 prescribes that BCPs and
standards track documents must be discussed in the IETF and
approved by the IESG, I don't think there is any possible
ambiguity.

> 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. 

I am quite sure there are zero instances of an Experimental RFC
being promoted to standards track without any revision.
At the minimum, it would need revision to to remove those words
saying it isn't on the standards track. So I think this is a
non-problem.

    Brian

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 03 07:46:06 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H25VM-0001Ds-Nd; Wed, 03 Jan 2007 07:46:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H25VL-0001Dg-Cg
	for independent@ietf.org; Wed, 03 Jan 2007 07:46:03 -0500
Received: from mtagate5.de.ibm.com ([195.212.29.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H25VH-0003vX-Is
	for independent@ietf.org; Wed, 03 Jan 2007 07:46:03 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate5.de.ibm.com (8.13.8/8.13.8) with ESMTP id l03Cjwur240480
	for <independent@ietf.org>; Wed, 3 Jan 2007 12:45:58 GMT
Received: from d12av01.megacenter.de.ibm.com (d12av01.megacenter.de.ibm.com
	[9.149.165.212])
	by d12nrmr1607.megacenter.de.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with
	ESMTP id l03CjwhX2715678
	for <independent@ietf.org>; Wed, 3 Jan 2007 13:45:58 +0100
Received: from d12av01.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av01.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l03CjwKd015441
	for <independent@ietf.org>; Wed, 3 Jan 2007 13:45:58 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av01.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l03CjwW2015428; Wed, 3 Jan 2007 13:45:58 +0100
Received: from [9.4.210.68] ([9.4.210.68])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id NAA69820;
	Wed, 3 Jan 2007 13:45:57 +0100
Message-ID: <459BA586.6060205@zurich.ibm.com>
Date: Wed, 03 Jan 2007 13:45:58 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: Re: [INDEP] Re: FYI: Last Call for "Independent Submissions to the
	RFC	Editor"
References: <5A14378A-E40A-4BD7-BF40-E70E61691A20@NLnetLabs.nl>
	<459445D7.45C9@xyzzy.claranet.de>
In-Reply-To: <459445D7.45C9@xyzzy.claranet.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

On 2006-12-28 23:31, Frank Ellermann wrote:
> Olaf M. Kolkman wrote:
> 
>>     "Independent Submissions to the RFC Editor"
>>     http://tools.ietf.org/id/draft-klensin-rfc-independent-05.txt
> 
> There are some "historically" in this text, where my interpretations
> of "not more relevant" or "not more true" don't fit.  It starts in
> chapter 1.1, the given definitions of "independent submission" and
> "individual submission" are fine, not only "historically".
> 
> In chapter 2 the "historically" starts to worry me:
> 
> |  o  Technical contributions (e.g., RFC 1810 [RFC1810]) and,
> |     historically,
> |  o  RFC Editor and, at least prior to the handoff between ISI and
> |     ICANN and the June 2000 MOU [RFC2860], IANA Policy Statements
> |     (e.g., [RFC2223] and RFC 1591 [RFC1591]).
> 
> They (RfC-editor + ICANN) should be free to continue this tradition.
> Important texts like 2223bis.08 available "only" as I-D aren't ideal.

The text doesn't prevent the RFC Editor from submitting an Independent
Submission to itself, or IANA from submitting one. So I don't see
any restriction introduced by the factual "historically." I would be
against creating explicit "document streams" for the RFC Editor or
IANA; it's complicated enough already.

I would also argue that neither of the examples are good ones for
the future. RFC 2223 is procedural material that should be easy
to update - ideal for an ION. RFC 1591 is a wonderful document,
but unfortunately the world went mad the year after it was published,
and I don't ever expect to see a 1591bis.

    Brian

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 03 21:09:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2I2c-0006Ie-Qv; Wed, 03 Jan 2007 21:09:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2I2b-0006IT-8v
	for independent@ietf.org; Wed, 03 Jan 2007 21:09:13 -0500
Received: from montage.altserver.com ([72.34.52.22]
	helo=montage2.altserver.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2I2a-0005XV-Hi
	for independent@ietf.org; Wed, 03 Jan 2007 21:09:13 -0500
Received: from i03m-212-195-38-17.d4.club-internet.fr ([212.195.38.17]
	helo=asus) by montage2.altserver.com with esmtp (Exim 4.52)
	id 1H2I2Z-00084y-4C
	for independent@ietf.org; Wed, 03 Jan 2007 18:09:11 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 04 Jan 2007 03:09:01 +0100
To: Brian E Carpenter <brc@zurich.ibm.com>,
	Frank Ellermann <nobody@xyzzy.claranet.de>
From: JFC Morfin <jefsey@jefsey.com>
Subject: Re: [INDEP] Last Call for "Independent Submissions to the RFC	Editor"
In-Reply-To: <459BA586.6060205@zurich.ibm.com>
References: <5A14378A-E40A-4BD7-BF40-E70E61691A20@NLnetLabs.nl>
	<459445D7.45C9@xyzzy.claranet.de> <459BA586.6060205@zurich.ibm.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-78D92306;
	boundary="=======AVGMAIL-459C61BD34B8======="
X-Antivirus-Scanner: Clean mail though you should still use an Antivirus
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org
Message-Id: <E1H2I2c-0006Ie-Qv@megatron.ietf.org>

--=======AVGMAIL-459C61BD34B8=======
Content-Type: multipart/alternative;
	boundary="=====================_4948453==.ALT";
	x-avg-checked=avg-ok-78D92306

--=====================_4948453==.ALT
Content-Type: text/plain; charset=us-ascii; format=flowed;
	x-avg-checked=avg-ok-78D92306

At 13:45 03/01/2007, Brian E Carpenter wrote:
>RFC 1591 is a wonderful document, but unfortunately the world went 
>mad the year after it was published, and I don't ever expect to see a 1591bis.

There is an RFC 1591 independent submission candidate: the ICP-1 
ICANN document. Its update is currently under discussion by ICANN 
(http://icann.org/announcements/announcement-2-05dec06.htm). At the 
end of the debate, ICANN will have to produce an independent 
submission to state its policy in the discussed area (the 
IETF/ICANN/IANA MoU makes this kind of decision free from any IETF review).


1) This illustrates one of the issues that I do not see addressed in 
John's document (I am travelling and was not able to print it)

This is the name of the I_D to be initially submitted. Independent 
submissions of primary interest to the RFC series and IETF are I_D 
submitted by other SSDOs, and national or international entities - 
including governments (in particular, this is of the essence if we 
would like to retain the unity of the Multilingual Internet, with 
nationally defined TLDs, such as in China). My understanding is that 
only a limited number of organisations belonging to the IETF sphere 
can name their I_D texts with their name (e.g. iesg-xxx-01.txt). This 
seems inadequate for two reasons:

a) it does not permit one to support the mechanism that produced the 
document. For example, why would Paul Twomey or David Conrad affix 
their name to a text approved by the ICANN BoD? At the same time, I 
cannot see an iana-xxx-01.txt being introduced without having been 
approved by the ICANN BoD, most probably by the GAC and certainly by 
the NTIA (along with the NTIA/ICANN agreement).

b) this creates an imbalance between SSDOs. As the Draft underlines 
it, the IETF is only one of the users/clients of the RFC Editor. All 
of the SSDOs should be treated the same. This means that when an 
independent submission results from an organised task force, a public 
entity, or an international organisation it should be able to sign 
its I_D with its own name.


2) the Draft is not clear about the proposed I_D revision process.

There are many reasons provided for the proposed I_Ds to be 
discussed, challenged, delayed, or blocked. There is no documentation 
about the way the proposed I_D can be modified and further reviewed. 
The current procedure seems to imply that an I_D is always proposed 
as -00.txt and can only be proposed anew. This may lead to tension 
and extra-work, of which a procedure could help avoid. For example, I 
would suggest that every Independent Submission, once it is 
established that its subject matter lies in the RFC Editor area, be 
assigned a Shepherd. He would help the authors to adapt to the RFC 
Editor's constraints and to take into account the different reviews 
it may receive, as well as to discuss with the reviewers if the 
changes made match their "discuss". Moreover, that the procedure will 
be documented but as a related ION, so it can adapt to experience 
without resulting in an RFC Change.


3) I have another concern, which is translation. Independent 
Submissions can result from the effort made by foreign entities or 
SSDOs to document their positions to the benefit of the Internet 
Community at large. These positions can be expressed in different 
languages. I suggest the following:

a) the Independent Submissions MUST indicate if they are the text of 
reference, or if they only are a translation of a text of reference 
in a non-English language.
b) if the text of reference is not in English, it should be attached 
as an appendix to the RFC (to make sure that the same versions are referred to)
c) only texts of reference in one of the relevant languages as 
documented by ISO 3166-1:2006 should then be accepted.

jfc



--=====================_4948453==.ALT
Content-Type: text/html; charset=us-ascii; x-avg-checked=avg-ok-78D92306

<html>
<body>
At 13:45 03/01/2007, Brian E Carpenter wrote:<br>
<blockquote type=cite class=cite cite="">RFC 1591 is a wonderful
document, but unfortunately the world went mad the year after it was
published, and I don't ever expect to see a 1591bis.</blockquote><br>
<font size=2>There is an RFC 1591 independent submission candidate: the
ICP-1 ICANN document. Its update is currently under discussion by ICANN
(</font>
<a href="http://icann.org/announcements/announcement-2-05dec06.htm" eudora="autourl">
<font color="#000080"><u>
http://icann.org/announcements/announcement-2-05dec06.htm</a></u></font>
<font size=2>). At the end of the debate, ICANN will have to produce an
independent submission to state its policy in the discussed area (the
IETF/ICANN/IANA MoU makes this kind of decision free from any IETF
review).<br><br>
<br>
1) This illustrates one of the issues that I do not see addressed in
John's document (I am travelling and was not able to print it)<br><br>
This is the name of the I_D to be initially submitted. Independent
submissions of primary interest to the RFC series and IETF are I_D
submitted by other SSDOs, and national or international entities -
including governments (in particular, this is of the essence if we would
like to retain the unity of the Multilingual Internet, with nationally
defined TLDs, such as in China). My understanding is that only a limited
number of organisations belonging to the IETF sphere can name their I_D
texts with their name (e.g. iesg-xxx-01.txt). This seems inadequate for
two reasons: <br><br>
a) it does not permit one to support the mechanism that produced the
document. For example, why would Paul Twomey or David Conrad affix their
name to a text approved by the ICANN BoD? At the same time, I cannot see
an iana-xxx-01.txt being introduced without having been approved by the
ICANN BoD, most probably by the GAC and certainly by the NTIA (along with
the NTIA/ICANN agreement).<br><br>
b) this creates an imbalance between SSDOs. As the Draft underlines it,
the IETF is only one of the users/clients of the RFC Editor. All of the
SSDOs should be treated the same. This means that when an independent
submission results from an organised task force, a public entity, or an
international organisation it should be able to sign its I_D with its own
name.<br><br>
<br>
2) the Draft is not clear about the proposed I_D revision process.
<br><br>
There are many reasons provided for the proposed I_Ds to be discussed,
challenged, delayed, or blocked. There is no documentation about the way
the proposed I_D can be modified and further reviewed. The current
procedure seems to imply that an I_D is always proposed as -00.txt and
can only be proposed anew. This may lead to tension and extra-work, of
which a procedure could help avoid. For example, I would suggest that
every Independent Submission, once it is established that its subject
matter lies in the RFC Editor area, be assigned a Shepherd. He would help
the authors to adapt to the RFC Editor's constraints and to take into
account the different reviews it may receive, as well as to discuss with
the reviewers if the changes made match their &quot;discuss&quot;.
Moreover, that the procedure will be documented but as a related ION, so
it can adapt to experience without resulting in an RFC Change.<br><br>
<br>
3) I have another concern, which is translation. Independent Submissions
can result from the effort made by foreign entities or SSDOs to document
their positions to the benefit of the Internet Community at large. These
positions can be expressed in different languages. I suggest the
following: <br><br>
a) the Independent Submissions MUST indicate if they are the text of
reference, or if they only are a translation of a text of reference in a
non-English language.<br>
b) if the text of reference is not in English, it should be attached as
an appendix to the RFC (to make sure that the same versions are referred
to)<br>
c) only texts of reference in one of the relevant languages as documented
by ISO 3166-1:2006 should then be accepted. <br><br>
jfc<br><br>
</font><img src="http://i.msgtag.com/anjA/vbncygla/EDjwvrcrdrf/knhqrCxjF.gif" alt=" " border="0" id="MSGTAGImage"/></body>
</html>


--=====================_4948453==.ALT--
--=======AVGMAIL-459C61BD34B8=======
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent

--=======AVGMAIL-459C61BD34B8=======--





From independent-bounces@ietf.org Sat Jan 06 11:49:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3EjW-0001XP-2G; Sat, 06 Jan 2007 11:49:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3EjV-0001XK-Gw
	for independent@ietf.org; Sat, 06 Jan 2007 11:49:25 -0500
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H3EjS-0003aI-67
	for independent@ietf.org; Sat, 06 Jan 2007 11:49:25 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1H3EjJ-00030m-46
	for independent@ietf.org; Sat, 06 Jan 2007 17:49:13 +0100
Received: from du-017a-032.access.de.clara.net ([213.221.75.32])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <independent@ietf.org>; Sat, 06 Jan 2007 17:49:13 +0100
Received: from nobody by du-017a-032.access.de.clara.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <independent@ietf.org>; Sat, 06 Jan 2007 17:49:13 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: independent@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Sat, 06 Jan 2007 17:45:17 +0100
Organization: <URL:http://purl.net/xyzzy>
Lines: 37
Message-ID: <459FD21D.849@xyzzy.claranet.de>
References: <5A14378A-E40A-4BD7-BF40-E70E61691A20@NLnetLabs.nl>
	<459445D7.45C9@xyzzy.claranet.de> <459BA586.6060205@zurich.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: du-017a-032.access.de.clara.net
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: [INDEP] Re: FYI: Last Call for "Independent Submissions to the RFC
	Editor"
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

Brian E Carpenter wrote:

> I don't see any restriction introduced by the factual "historically."

Maybe it's a bad case of DEnglish on my side, but I'd still prefer to
remove the "historically" from the draft before publication.

> I would be against creating explicit "document streams" for the
> RFC Editor

+1

> or IANA

That could be tricky, but getting a proper RFC number for their "ICP"
documents, US ASCII and all, I'd like that.  The status could be also
"informational", like RFCs published by the IAB, IESG, or IASA.

> RFC 2223 is procedural material that should be easy to update - ideal
> for an ION.

It will be soon ten years old, it doesn't change often enough for an
ION.  Or rather that's my concept of ION:  Needing modifications often,
like your roadmap text.  Maybe your concept of ION is more like "doesn't
need the complete last call + approval + RFC editor bureaucracy", that
would be somewhat different.

> RFC 1591 is a wonderful document, but unfortunately the world went
> mad the year after it was published, and I don't ever expect to see
> a 1591bis.

What happened 1995 ?  RFC 1591 is clearly better than RFC 1032, but in
that case the official status is critical to cover the relevant parts
of RFC 954.

Frank



_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Sun Jan 07 03:21:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H3THk-0000fa-2Q; Sun, 07 Jan 2007 03:21:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H3THi-0000fU-4Z
	for independent@ietf.org; Sun, 07 Jan 2007 03:21:42 -0500
Received: from mtagate6.uk.ibm.com ([195.212.29.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H3THf-0002PR-DE
	for independent@ietf.org; Sun, 07 Jan 2007 03:21:42 -0500
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate6.uk.ibm.com (8.13.8/8.13.8) with ESMTP id l078Lcf1104778
	for <independent@ietf.org>; Sun, 7 Jan 2007 08:21:38 GMT
Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com
	[9.149.37.228])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with
	ESMTP id l078Lcj31781986
	for <independent@ietf.org>; Sun, 7 Jan 2007 08:21:38 GMT
Received: from d06av02.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av02.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l078LcBB011496
	for <independent@ietf.org>; Sun, 7 Jan 2007 08:21:38 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d06av02.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l078LcfD011491; Sun, 7 Jan 2007 08:21:38 GMT
Received: from [9.4.210.68] ([9.4.210.68])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id JAA107716; 
	Sun, 7 Jan 2007 09:21:37 +0100
Message-ID: <45A0AD95.7010306@zurich.ibm.com>
Date: Sun, 07 Jan 2007 09:21:41 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: Re: [INDEP] Re: FYI: Last Call for "Independent Submissions to the
	RFC	Editor"
References: <5A14378A-E40A-4BD7-BF40-E70E61691A20@NLnetLabs.nl>	<459445D7.45C9@xyzzy.claranet.de>
	<459BA586.6060205@zurich.ibm.com> <459FD21D.849@xyzzy.claranet.de>
In-Reply-To: <459FD21D.849@xyzzy.claranet.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org


> What happened 1995 ?  

pimples.com was registered, which for me was a clear sign of world
insanity. Please excuse me; this is off topic.

    Brian

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Fri Jan 12 04:38:56 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5Irl-0001Sq-Gz; Fri, 12 Jan 2007 04:38:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5Irj-0001S3-3J; Fri, 12 Jan 2007 04:38:27 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H5Iri-0004qI-Ty; Fri, 12 Jan 2007 04:38:27 -0500
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42])
	by ns1.neustar.com (Postfix) with ESMTP id DC66926F04;
	Fri, 12 Jan 2007 09:38:26 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43)
	id 1H5Iri-00084h-QA; Fri, 12 Jan 2007 04:38:26 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: Leslie Daigle <leslie@thinkingcat.com>
Message-Id: <E1H5Iri-00084h-QA@ietf.org>
Date: Fri, 12 Jan 2007 04:38:26 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: independent@ietf.org, iab@ietf.org
Subject: [INDEP] Impending publication: draft-iab-rfc-editor-03.txt and 
 draft-iab-publication-00.txt 
X-BeenThere: independent@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iab@ietf.org
List-Id: Discussion of RFC Editor independent submissions proposal
	<independent.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

The IAB is ready to ask the RFC-Editor to publish


1/ draft-iab-rfc-editor-03.txt
   "The RFC Series and RFC Editor"
   http://www.ietf.org/internet-drafts/draft-iab-rfc-editor-03.txt

  Abstract

   This document describes the framework for an RFC Series and an RFC
   Editor function that incorporate the principles of organized
   community involvement and accountability that has become necessary as
   the Internet technical community has grown, thereby enabling the RFC
   Series to continue to fulfill its mandate.


2/ draft-iab-publication-00.txt
   "Process for Publication of IAB RFCs"
   http://www.ietf.org/internet-drafts/draft-iab-publication-00.txt

  Abstract

   From time to time, the Internet Architecture Board (IAB) publishes
   documents as Requests for Comments (RFCs).  This document defines the
   process by which those documents are produced, reviewed, and
   published in the RFC series.

The IAB solicits comments by February 9, 2007. Please send
comments to the IAB (iab@iab.org).


Leslie Daigle,
for the IAB.

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 17 13:41:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7Fi6-0004F1-Ns; Wed, 17 Jan 2007 13:40:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7Fi5-0004Et-Ai; Wed, 17 Jan 2007 13:40:33 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H7Fi1-0008QB-4h; Wed, 17 Jan 2007 13:40:33 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l0HIdZ3f010311;
	Wed, 17 Jan 2007 10:39:35 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id KAA19524;
	Wed, 17 Jan 2007 10:39:35 -0800 (PST)
Date: Wed, 17 Jan 2007 10:39:35 -0800 (PST)
Message-Id: <200701171839.KAA19524@gra.isi.edu>
To: independent@ietf.org, olaf@NLnetLabs.nl
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08aa56e70047071f9a3037af5750d40e
Cc: klensin@jck.com, braden@ISI.EDU, iab@ietf.org, rfc-editor@rfc-editor.org
Subject: [INDEP] Re: comments on draft-klensin-independent-05.txt
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org


----- Begin Included Message -----

>From braden@ISI.EDU  Wed Jan 10 12:47:23 2007
X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.0
From: Bob Braden <braden@ISI.EDU>
Date: Wed, 10 Jan 2007 12:46:32 -0800 (PST)
To: braden@ISI.EDU
Subject: Re: comments on draft-klensin-independent-05.txt
Cc: ginzoa@ISI.EDU, hagens@ISI.EDU
X-ISI-4-43-8-MailScanner: Found to be clean


  *> 
  *> 
  *> Network Working Group                                    J. Klensin, Ed.
  *> Internet-Draft                                         December 21, 2006
  *> Intended status: Informational
  *> Expires: June 24, 2007
  *> 
  *> 
  *>                Independent Submissions to the RFC Editor
  *>                  draft-klensin-rfc-independent-05.txt
  *> 
  *> Status of this Memo
  *> 
  *>    By submitting this Internet-Draft, each author represents that any
  *>    applicable patent or other IPR claims of which he or she is aware
  *>    have been or will be disclosed, and any of which he or she becomes
  *>    aware will be disclosed, in accordance with Section 6 of BCP 79.
  *> 
  *>    Internet-Drafts are working documents of the Internet Engineering
  *>    Task Force (IETF), its areas, and its working groups.  Note that
  *>    other groups may also distribute working documents as Internet-
  *>    Drafts.
  *> 
  *>    Internet-Drafts are draft documents valid for a maximum of six months
  *>    and may be updated, replaced, or obsoleted by other documents at any
  *>    time.  It is inappropriate to use Internet-Drafts as reference
  *>    material or to cite them other than as "work in progress."
  *> 
  *>    The list of current Internet-Drafts can be accessed at
  *>    http://www.ietf.org/ietf/1id-abstracts.txt.
  *> 
  *>    The list of Internet-Draft Shadow Directories can be accessed at
  *>    http://www.ietf.org/shadow.html.
  *> 
  *>    This Internet-Draft will expire on June 24, 2007.
  *> 
  *> Copyright Notice
  *> 
  *>    Copyright (C) The Internet Society (2006).
  *> 
  *> Abstract
  *> 
  *>    There is a long-term tradition in the Internet community, predating
  *>    the IETF by many years, of use of the RFC series to publish materials
  *>    that are not rooted in the IETF standards process and its review and
  *>    approval mechanisms.  These documents, known as "independent
  *>    submissions", serve a number of important functions for the Internet
  *>    community, both inside and outside of the community of active IETF
  *>    participants.  This document discusses the independent submission
  *>    model and some reasons why it is important.  It then describes
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 1]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *>    editorial and processing norms that can be used for independent
  *>    submissions as the community goes forward into new relationships
  *>    between the IETF community and its primary technical publisher.
  *> 
  *> 
  *> Table of Contents
  *> 
  *>    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
  *>      1.1.  Terminology Note . . . . . . . . . . . . . . . . . . . . .  3
  *>      1.2.  Context and Philosophical Assumptions  . . . . . . . . . .  4
  *>    2.  The Role of Independent Submissions  . . . . . . . . . . . . .  4
  *>    3.  Document Submission  . . . . . . . . . . . . . . . . . . . . .  5
  *>    4.  The Review Process . . . . . . . . . . . . . . . . . . . . . .  6
  *>      4.1.  Posting of Draft . . . . . . . . . . . . . . . . . . . . .  6
  *>      4.2.  Request for Publication  . . . . . . . . . . . . . . . . .  6
  *>      4.3.  Initial RFC Editor Review  . . . . . . . . . . . . . . . .  6
  *>      4.4.  Document Rejection . . . . . . . . . . . . . . . . . . . .  7
  *>      4.5.  Review and Evaluation  . . . . . . . . . . . . . . . . . .  7
  *>      4.6.  Unsolicited Reviews  . . . . . . . . . . . . . . . . . . .  7
  *>      4.7.  Additional Reviews . . . . . . . . . . . . . . . . . . . .  7
  *>      4.8.  Final IESG Review  . . . . . . . . . . . . . . . . . . . .  7
  *>      4.9.  Final Decision and Notification  . . . . . . . . . . . . .  8
  *>      4.10. Final Editing and Publication  . . . . . . . . . . . . . .  9
  *>    5.  The Editorial Review Board . . . . . . . . . . . . . . . . . .  9
  *>    6.  Status and Availability of Reviews . . . . . . . . . . . . . .  9
  *>      6.1.  Documents in process or rejected . . . . . . . . . . . . . 10
  *>      6.2.  Published Documents and Documents Approved for
  *>            Publication  . . . . . . . . . . . . . . . . . . . . . . . 10
  *>    7.  Intellectual Property Rights . . . . . . . . . . . . . . . . . 10
  *>    8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
  *>    9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 12
  *>    10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 12
  *>    11. Change log . . . . . . . . . . . . . . . . . . . . . . . . . . 12
  *>      11.1. Changes between version -02 and version -03  . . . . . . . 12
  *>      11.2. Changes for -04  . . . . . . . . . . . . . . . . . . . . . 13
  *>      11.3. Changes for -05  . . . . . . . . . . . . . . . . . . . . . 14
  *>    12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
  *>      12.1. Normative References . . . . . . . . . . . . . . . . . . . 14
  *>      12.2. Informative References . . . . . . . . . . . . . . . . . . 14
  *>    Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 15
  *>    Intellectual Property and Copyright Statements . . . . . . . . . . 16
  *> 
  *> 
  *> 
  *> 
  *> 
  *> 
  *> 
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 2]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *> 1.  Introduction
  *> 
  *>    There is a long-term tradition in the Internet community, predating
  *>    the IETF by many years, of use of the RFC series to publish materials
  *>    that are not rooted in the IETF standards process and its review and
  *>    approval mechanisms.  These documents, known as "independent
  *>    submissions", serve a number of important functions for the Internet
  *>    community, both inside and outside of the community of active IETF
  *>    participants.  This document discusses the independent submission
  *>    model and some reasons why it is important.  It then describes
  *>    editorial and processing norms that can be used for independent
  *>    submissions as the community goes forward into new relationships
  *>    between the IETF community and its primary technical publisher.
  *> 
  *>    To understand the perspective of this document, it is important to
  *>    remember that the RFC-Editor function predates the creation of the
  *>    IETF.  As of the time of this writing, the RFC series goes back 36
  *>    years 

     insert reference: [RFC2555]

  *>    while the IETF is celebrating its 20th anniversary.  All of the
  *>    documents that were published before the IETF was created, and for
  *>    some years thereafter, would be considered independent submissions
  *>    today.  As the IETF evolved, the IAB and then the IETF itself chose
  *>    to publish IETF documents as RFCs while fully understanding that the
  *>    RFC-Editor function was an independent publication mechanism.  Other
  *>    decisions were possible: e.g., the IETF could have decided to create
  *>    it own publication series.  It was felt that there was considerable
  *>    value in continuing to publish the IETF work in the same series as
  *>    the one used to publish the basic protocols for the Internet.
  *> 
  *> 1.1.  Terminology Note
  *> 
  *>    This document describes what have historically been referred to as
  *>    "independent submissions".  That term is distinguished from those
  *>    IETF and IAB community documents that originate from formal groups --
  *>    IAB, IRTF, IETF WGs -- and from submissions submitted to the IESG for
  *>    standards-track, informational, or experimental processing.
  *>    Documents produced by individuals, rather than IETF WGs or others
  *>    IETF-affiliated groups, but submitted for publication under Area
  *>    Director sponsorship, have been known historically as "individual

s/have been known historicall/are known/

  *>    submissions".
  *> 
  *>    For convenience and obvious historical reasons, the editor and
  *>    publisher of documents that are not processed through the IETF is
  *>    known below as the "RFC Editor".  The RFC Editor will typically be an
  *>    organization or one or more senior people and associated staff, and

s/staff/editorial staff/

  *>    the term is used collectively below.  That term is not intended to
  *>    predict the future, either in terms of who does the job or what they,
  *>    or the document series, are called.
  *> 
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 3]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *> 1.2.  Context and Philosophical Assumptions
  *> 
  *>    This document contains text that, if agreed to by the community, may
  *>    suggest a reexamination of and a corresponding update to RFC 3932
  *>    [RFC3932].  Those issues, and proposals for changes, are discussed in
  *>    a different document [RFC3932upd], but they are semi-independent of
  *>    the content of this document, which focuses on the review and
  *>    approval process for independent submissions.
  *> 
  *>    This document complements the discussion and guidelines in [RFC4714],
  *>    which focuses on standards track documents.  It takes a somewhat
  *>    stronger view than the discussions that lead up to that document,

s/lead to/led/

  *>    starting from the belief that independent submissions are most
  *>    valuable if they are, in fact, independent of the IETF process.  From
  *>    the perspective of the IETF, independent submissions are especially
  *>    important as checks on the IETF processes even though such checks are
  *>    not the only, or even a common, reason for them.  That role is
  *>    compromised if IETF-related entities are able to block or deprecate
  *>    such documents to a degree beyond that needed to avoid difficulties
  *>    with the standards process.
  *> 
  *> 
  *> 2.  The Role of Independent Submissions
  *> 
  *>    When the RFC series was fairly new, RFCs could be used to publish

s/could be/were/

  *>    general papers on networking as well as the types of documents we
  *>    would describes as standards today.  Those roles also developed as

s/describes/describe/

"also"?


  *>    part of the early design and development of the ARPANET, long before
  *>    anyone dreamt of the IETF and when the distinction between, e.g.,
  *>    standards and informational documents was less precisely drawn.  In
  *>    more recent years, independent submissions have become important for
  *>    multiple reasons, some of them relatively new.  They include:
  *> 
  *>    o  Discussion of Internet-related technologies that are not part of
  *>       the IETF agenda.
  *>    o  Introduction of important new ideas as a bridge publication venue
  *>       between academia and IETF engineering.
  *>    o  Informational discussions of technologies, options, or experience
  *>       with protocols.
  *>    o  Informational publication of vendor-specific protocols.
  *>    o  Critiques and discussions of alternatives to IETF standards-track
  *>       protocols.  The potential for such critiques provides an important
  *>       check on the IETF's standards processes and should be seen in that
  *>       light.
  *>    o  Documents considered by IETF Working Groups but not standardized.
  *>       While many documents of this type are published via the IESG
  *>       approval path (see RFC 3932, Section 1 [RFC3932]), the independent
  *>       submission path has traditionally been open to them.  Because of
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 4]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *>       their intimate connection to the IETF Standards Process and WG
  *>       activites and the consequent sensitivity to exact statements of
  *>       relationships and to timing, there is reason to believe that all
  *>       such documents should be published only at IESG request.  In any
  *>       event, these documents are published for the historical record.
  *>    o  Satirical materials.
  *>    o  Meeting notes and reports (RFC 164 [RFC0164] is the earliest, 1109
  *>       [RFC1109] probably the most important).
  *>    o  Editorials (the best example is IEN-137, not an RFC).

Please insert reference:

[IEN137] Cohen, D., "On Holy Wars and a Quest for Peace", IEN 137,
         April 1980.

  *>    o  Eulogies (RFC 2441 [RFC2441])
  *>    o  Technical contributions (e.g., RFC 1810 [RFC1810]) and,
  *>       historically,
  *>    o  RFC Editor and, at least prior to the handoff between ISI and
  *>       ICANN and the June 2000 MOU [RFC2860], IANA Policy Statements
  *>       (e.g., [RFC2223] and RFC 1591 [RFC1591]).
  *> 
  *>    It should be clear from the list above that, to be effective, the
  *>    review and approval process for independent submissions should be
  *>    largely independent of the IETF.  As a important principle that has
  *>    been applied historically, the RFC Editor should seek advice from the

s/should seek/seeks/

  *>    IESG about possible relationships and conflicts with IETF work.  The
  *>    IESG may ask that, as a courtesy, publication of particular documents
  *>    be deferred because their untimely publication could cause confusion
  *>    or other harm with proposals under consideration for standardization.
  *>    Absent compelling arguments to the contrary, the RFC Editor will
  *>    honor such requests.  Similarly, any submission that constitutes an
  *>    alternative to, or is in conflict with, an IETF Standard or proposal
  *>    for standards-track adoption must clearly indicate that relationship.
  *>    The IESG may identify such conflicts as part of its review.  If the
  *>    IESG identifies issues, it may recommend explanatory or qualifying
  *>    text for the RFC Editor to include in the document if it is
  *>    published.
  *> 
  *>    The specific procedures to be followed in review are described in
  *>    Section 4.
  *> 
  *> 
  *> 3.  Document Submission
  *> 
  *>    Independent submissions are submitted directly to the RFC Editor.
  *>    They must first be posted as Internet Drafts, so the submission is
  *>    typically simply a note requesting that the RFC Editor consider a
  *>    particular Internet Draft for publication.  The process is described
  *>    in more detail in [RFC2223] and a working draft of an update to it
  *>    [RFC2223bis].
  *> 
  *>    Any document that meets the requirements of this specification, of
  *>    [RFC2223] and its successors, and of any intellectual property or
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 5]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *>    other conditions that may be established from time to time, may be
  *>    submitted to the RFC Editor for consideration as an Independent
  *>    Submission.  However, the RFC Editor prefers that documents created
  *>    through IETF processes (e.g., working group output) be considered by
  *>    the IESG and submitted using this path only if a working group, or
  *>    the IESG, decline to publish it.  In the latter cases, the review
  *>    process is likely to be more efficient if the authors provide a

s/is likely to be/will be/

  *>    history of consideration and reviews of the document at the time of
  *>    submission.
  *> 
  *> 
  *> 4.  The Review Process
  *> 
  *>    While this document is consistent with the broad outline of
  *>    independent submission and review as practiced over the years, it
  *>    specifies some new arrangements in RFC Editor processing that will
  *>    improve the balance between openness and independent decisions.
  *> 

I have a little trouble with "specifies new arrangements" -- I would
prefer "clarify and documents procedures", but if you are going to say
"new arrangements", it seems to me you need to summarize what the new
arrangements are, so all parties can agree.

  *>    In general, the steps in the review process are identified in the
  *>    subsections below.  Any of them may be iterated and, at the
  *>    discretion of the RFC Editor, steps after the first may be taken out
  *>    of order.
  *> 
  *> 4.1.  Posting of Draft
  *> 
  *>    The author(s) or editor(s) of a document post it as an Internet
  *>    Draft.
  *> 
  *> 4.2.  Request for Publication
  *> 
  *>    After the normal opportunity for community review and feedback
  *>    provided by the submission of the I-D and the I-D repository
  *>    announcement thereof, the author or editor sends a request for
  *>    consideration for publication to the RFC Editor at
  *>    rfc-editor@rfc-editor.org.  That request should note any community
  *>    discussion or reviews of the document that have occurred before
  *>    submission.
  *> 
  *> 4.3.  Initial RFC Editor Review
  *> 
  *>    RFC Editor Staff perform an initial check on the document.  If they

s/Staff perform/staff performs/

  *>    believe there is a high likelihood of conflicts or other interactions
  *>    with IETF efforts (including believing that the document is one that
  *>    the IESG should probably process), they may forward it to the IESG,
  *>    or relevant ADs, for preliminary evaluation and comment.
  *> 

Comment: Nice theory, but in practice some IESG members have been
less than responsive to such requests from the RFC Editor.

  *> 
  *> 
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 6]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *> 4.4.  Document Rejection
  *> 
  *>    If the document does not appear publishable, the RFC Editor may
  *>    reject a submitted document at any point in the process specified
  *>    here.  Such rejection would normally be based on the conclusion that
  *>    the submission does not meet the technical or editorial standards of
  *>    the RFC Series or is not relevant to the areas that the series
  *>    covers.  Alternatively, the RFC Editor Staff may, at their
  *>    discretion, iterate with the author on the document to improve its
  *>    quality. 

Comment: While the above is factually correct, the community should be
aware that the RFC Editor often expends considerable effort and sometimes
3-65 go-arounds with authors to get their submissions up to publishable
quality.  Unlike IETF documents, which have received considerable
scrutiny before they are submitted to us, independent submissions
are more likely to come from a single author, often isolated from the
IETF, with revision level -00.  We just like to receive credit for
what we do.

  *>    If a document is rejected by the RFC Editor, the author may
  *>    request an additional review from the IAB, as described below, but
  *>    the IAB is not obligated to do that review, nor is the RFC Editor
  *>    obligated to publish even with a favorable IAB review.
  *> 
  *> 4.5.  Review and Evaluation
  *> 
  *>    The RFC Editor arranges for one or more reviews of the document.
  *>    This may include Editorial Board (see Section 5) reviews or
  *>    evaluation of reviews by others.
  *> 
  *> 4.6.  Unsolicited Reviews
  *> 
  *>    Unsolicited reviews from parties independent of the author are
  *>    welcome at any time and will be handled as above.  Unsolicited
  *>    reviews will be shared with the author including the identity of the
  *>    reviewer.
  *> 

   s/author including/author, including/

The last sentence seems to belong in Section 6, or maybe it should
be repeated there.


  *> 4.7.  Additional Reviews
  *> 
  *>    If the author is unsatisfied with the review(s), the author may
  *>    request that the RFC Editor solicit additional reviews.  In
  *>    exceptional circumstances, the author may request that the IAB review
  *>    the documents.  Such requests to the IAB, and any reviews the IAB
  *>    chooses to perform, will occur according to procedures of the IAB's
  *>    choosing.  However, the IAB is not required to initiate a review or
  *>    comply with a request for one: a request to the IAB for a review is
  *>    not an appeal process.  The RFC Editor is expected to consider all
  *>    competent reviews carefully, and in the absence of some unusual
  *>    circumstance, a preponderance of favorable reviews should lead to
  *>    publication.
  *> 
  *> 4.8.  Final IESG Review
  *> 
  *>    Once the RFC Editor has made a tentative decision to publish, the
  *>    document is forwarded to the IESG for evaluation with a relatively
  *>    short timeout.
  *> 
  *>    The IESG evaluation is not a technical one.  Instead, it covers the
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 7]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *>    issues listed in RFC 3932 or its successors, presumably from the
  *>    perspective outlined above in Section 1.2.  That is, the evaluation
  *>    should focus exclusively on conflicts or confusion with IETF process
  *>    and attempts to subvert ("end run") working group activities.
  *> 
  *>    At the time the document is forwarded to the IESG, the RFC Editor
  *>    will post an indication on its web pages that the document is under

s/will post/posts/   [explanation: TO state in queue]

  *>    IESG review and that comments on conflicts can be sent to the IESG
  *>    with copies to the RFC Editor.  Additional mechanisms may be
  *>    developed from time to time to inform a community that a document is
  *>    entering formal prepublication review.  Comments not directly related
  *>    to IETF procedures or conflicts may be sent directly to the author(s)
  *>    and RFC Editor.
  *> 
  *>    In addition to the IESG review for conflict with IETF work,
  *>    individuals in the IESG, or in the broader IETF community, are free
  *>    to review a draft and, if they have comments of any kind --including
  *>    the extreme case of believing that the proposal is damaging to the
  *>    Internet as a whole-- these comments should be directed to the
  *>    authors and the RFC Editor.

Comment: a balanced document would include transparency requirements on
the IESG, in this process, although that is covered elsewhere, I
guess.

  *> 
  *>    If the IESG, after completing its review, concludes that publication
  *>    of the document should be delayed for a reasonable period of time,
  *>    the RFC Editor will grant that request.  The current agreement
  *>    between the RFC Editor and the IESG on requested delays is expected
  *>    to continue.  That agreement permits the IESG to ask for a delay of
  *>    up to six months and, if necessary, to renew that request twice, for
  *>    a total possible delay of 18 months.
  *> 
  *>    If the IESG concludes that the document should not be published as an
  *>    RFC, it will request that the RFC Editor not publish and provide
  *>    appropriate justification for that request.  The RFC Editor will
  *>    consider the request to not publish the document.
  *> 
  *>    The RFC Editor or the author may request that the IAB review the
  *>    IESG's request to delay or not publish the document and request that
  *>    the IAB provide an additional opinion.  Such a request will be made
  *>    public via the RFC Editor web site.  As with the IESG review itself,
  *>    the IAB's opinion, if any, will be advisory.  And, as with author
  *>    requests for an IAB technical review (see Section 4.7), the IAB is
  *>    not obligated to perform this type of review and may decline the
  *>    request.
  *> 
  *> 4.9.  Final Decision and Notification
  *> 
  *>    In all cases, the ultimate decision to publish or not publish, and
  *>    with what language, rests with the RFC Editor.
  *> 
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 8]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *>    Information about the IESG requested publication delay or request to
  *>    not publish a document will be posted to the RFC Editor web site to
  *>    supplement document status information.
  *> 
  *> 4.10.  Final Editing and Publication
  *> 
  *>    Once a document is approved for publication, it is handled in a
  *>    fashion similar to other RFCs, with principles about priorities
  *>    worked out with the IAB as appropriate.
  *> 
  *> 
  *> 5.  The Editorial Review Board
  *> 
  *>    The RFC Editor appoints and maintains an Editorial Review Board
  *>    which, much like the Editorial Boards of professional journals and
  *>    publishers, provides the RFC Editor with both advice and reviews of
  *>    particular proposed publications and general and strategic policy
  *>    advice.  The membership list of the Editorial Review Board is public
  *>    and can be found at http://www.rfc-editor.org/edboard.html.
  *>    Editorial Board members serve at the pleasure of the RFC Editor.
  *>    From time to time, the RFC Editor will solicit suggestions for new
  *>    appointees from the IAB and other sources and will seek IAB comments
  *>    on those to be appointed and on the effectiveness of the review
  *>    process and the quality of documents being published and criteria
  *>    applied.  However, to ensure the independence of the independent
  *>    submission process, the final decision to appoint (or not appoint)
  *>    Editorial Board members rests with the RFC Editor.
  *> 
  *> 
  *> 6.  Status and Availability of Reviews
  *> 
  *>    The RFC Editor will conduct the reviews discussed above with the
  *>    intent of balancing fairness to authors, transparancy of the review
  *>    process to the general community, protection of reviewers from
  *>    possible retaliation or undue pressure, and the interest of the
  *>    community in having any significant dissents from published documents
  *>    available to the community with the same degree of scrutiny that the
  *>    original documents received.  To this end, reviews and information
  *>    about reviewers will be made public under the following
  *>    circumstances.  In special cases in which other considerations apply,
  *>    the RFC Editor may adopt special provisions after reviewing the
  *>    circumstances and proposed action with the IAB.
  *> 
  *>    Any reviewer participating in the process outlined in this document
  *>    does so on condition of giving consent to handling of the reviews as
  *>    outlined in this section.  In special cases, individual arrangements
  *>    may be worked out in advance with the RFC Editor.
  *> 
  *> 
  *> 
  *> 
  *> Klensin                   Expires June 24, 2007                 [Page 9]
  *> 
  *> Internet-Draft           Independent Submissions           December 2006
  *> 
  *> 
  *> 6.1.  Documents in process or rejected
  *> 
  *>    For documents in process, reviews may be made public and posted on
  *>    the RFC Editor web site at the request of the author.  The names of

I don't understand this discussion of documents in progress.
There is a bit of a time warp here.  The RFC Editor (or the author)
cannot know whether 6.1 or 6.2 applies until the end of the review
process, so reviews cannot be posted until that time, if at all.
The time warp gets worse if the author appeals to the IAB.

Question: Section 6.2 says the RFC Editor has an option of not posting
a review, but there is no such statement for 6.1; is the implication
that the RFC Editor is obliged to publish negative reviews?  Must the
reviewer(s) be identified?

  *>    reviewers associated with each review will normally accompany their
  *>    reviews, but may be withheld at the request of the reviewer.
  *> 
  *>    If the RFC Editor declines to publish a document, the document author

/s/If the RFC Editor declines to publish a document,/For rejected documents,/

  *>    may request that reviews be made public, as above, However, that
  *>    request must be timely, generally within thirty days of the author's
  *>    notification that the document would not be published.
  *> 
  *>    With or without a document author request, the RFC Editor may post
  *>    the full set of reviews associated with a document in process or
  *>    rejected for publication if they conclude that doing so would be in
  *>    the best interest of the community.  The author will be notified that
  *>    this action is about to be taken and may optionally request that the
  *>    request to publish the document be withdrawn and the reviews kept
  *>    private.  Under normal circumstances, the RFC Editor will honor that
  *>    request.
  *> 
  *> 6.2.  Published Documents and Documents Approved for Publication
  *> 
  *>    For documents that are published, either the author or any reviewer
  *>    may request that reviews be made public.  The RFC Editor may, but is
  *>    not required to, do so.  In considering whether to make review
  *>    materials public, the RFC Editor is expected to note, first, that the
  *>    best way to comment on, or dissent from, an RFC is generally another
  *>    RFC; that reviews critical of a document are not themselves reviewed
  *>    and that the author generally does not have the right to publish a
  *>    refutation to an unfavorable review; and that a reviewer who feels
  *>    strongly about a subject about which a review has already been
  *>    written often would not need to do significant additional work to
  *>    produce an RFC-format document from that review.
  *> 
  *>    Nothing in this section or the subsections above precludes private
  *>    communications between reviewers, the Editorial Board, and the RFC
  *>    Editor; such communications will remain confidential.  At minimum,
  *>    the author of either an accepted or rejected document shall receive a
  *>    written summary of the review(s).
  *> 

The last sentence above seems important enough to appears much earlier and
not be an afterthought.

 
(I had no comments after this point).

Bob Braden


----- End Included Message -----


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 17 14:10:31 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7GAx-0003GC-Js; Wed, 17 Jan 2007 14:10:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7GAw-0003G4-QI; Wed, 17 Jan 2007 14:10:22 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H7GAt-0004Z6-V3; Wed, 17 Jan 2007 14:10:22 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1H7GAp-000DNH-0y; Wed, 17 Jan 2007 14:10:15 -0500
Date: Wed, 17 Jan 2007 14:10:13 -0500
From: John C Klensin <john-ietf@jck.com>
To: Bob Braden <braden@ISI.EDU>, independent@ietf.org, olaf@NLnetLabs.nl
Message-ID: <01FE16A1FA71855F7BFF2A9A@p3.JCK.COM>
In-Reply-To: <200701171839.KAA19524@gra.isi.edu>
References: <200701171839.KAA19524@gra.isi.edu>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: iab@ietf.org, rfc-editor@rfc-editor.org
Subject: [INDEP] Re: comments on draft-klensin-independent-05.txt
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

Bob,

Most of these comments are editorial matters that could easily
and properly be remedied by RFC Editor processing should the IAB
decide to publish.   I'll incorporate them into the source if
the IAB tells me to, but am not feeling a strong need to discuss
them further.   Exceptions are discussed below...

If you have further comments, please do not include the entire
text of the I-D: that just makes finding the real change
proposals harder for all of us.

--On Wednesday, 17 January, 2007 10:39 -0800 Bob Braden
<braden@ISI.EDU> wrote:
 
> ----- Begin Included Message -----
> 
> From braden@ISI.EDU  Wed Jan 10 12:47:23 2007
>...
> From: Bob Braden <braden@ISI.EDU>
> Date: Wed, 10 Jan 2007 12:46:32 -0800 (PST)
> To: braden@ISI.EDU
> Subject: Re: comments on draft-klensin-independent-05.txt
> Cc: ginzoa@ISI.EDU, hagens@ISI.EDU
>...

> group, or   *>    the IESG, decline to publish it.  In the
> latter cases, the review   *>    process is likely to be more
> efficient if the authors provide a
> 
> s/is likely to be/will be/

I don't object to this change, but, since this has not been the
common practice, its contribution to efficiency is unproven.

> practiced over the years, it   *>    specifies some new
> arrangements in RFC Editor processing that will   *>
> improve the balance between openness and independent decisions.

> I have a little trouble with "specifies new arrangements" -- I
> would prefer "clarify and documents procedures", but if you
> are going to say "new arrangements", it seems to me you need
> to summarize what the new arrangements are, so all parties can
> agree.

I'll leave this one to the IAB but (i) there are several
provisions in this document, including those about availability
of reviews, requests for reviews to the IAB, etc., that were
definitely new when the first draft of this document was posted
and (ii) several aspects of the "traditional" review process
remain fairly opaque to this day.   For example, I note that one
recent document was sent to the IESG for formal (RFC3932) review
without being first circulated to the Editorial Board.

To put the issue I see here differently, if the RFC Editor
wanted to supply a precise description of the procedures that
were consistently followed before this document was written, I
would be happy to generate a section of this document that
describes the changes.
 
>...
>   *>    believe there is a high likelihood of conflicts or
> other interactions   *>    with IETF efforts (including
> believing that the document is one that   *>    the IESG
> should probably process), they may forward it to the IESG,
> *>    or relevant ADs, for preliminary evaluation and comment. 
> 
> Comment: Nice theory, but in practice some IESG members have
> been less than responsive to such requests from the RFC Editor.

I presume from the above that some IESG members _have_ been
responsive.  This is an optional step designed to save both the
IESG and the RFC Editor time.  If the relevant AD(s) don't care,
then you move on to the next step, presumably pointing out to
the IESG when the 3932 review is requested that you tried to get
input earlier but didn't.

If you don't believe that the text is sufficiently clear on that
subject, please suggest alternate or additional text.

>...
> of   *>    the RFC Series or is not relevant to the areas that
> the series   *>    covers.  Alternatively, the RFC Editor
> Staff may, at their   *>    discretion, iterate with the
> author on the document to improve its   *>    quality. 
> 
> Comment: While the above is factually correct, the community
> should be aware that the RFC Editor often expends considerable
> effort and sometimes 3-65 go-arounds with authors to get their
> submissions up to publishable quality.  Unlike IETF documents,
> which have received considerable scrutiny before they are
> submitted to us, independent submissions are more likely to
> come from a single author, often isolated from the IETF, with
> revision level -00.  We just like to receive credit for what
> we do.

If you believe some textual change to the document would be
appropriate, please suggest text.

>   *>    In addition to the IESG review for conflict with IETF
> work,   *>    individuals in the IESG, or in the broader IETF
> community, are free   *>    to review a draft and, if they
> have comments of any kind --including   *>    the extreme case
> of believing that the proposal is damaging to the   *>
> Internet as a whole-- these comments should be directed to the
>   *>    authors and the RFC Editor.
> 
> Comment: a balanced document would include transparency
> requirements on the IESG, in this process, although that is
> covered elsewhere, I guess.

In response to comments on earlier drafts, the current version
of this document has been constructed to avoid imposing
requirements on the IESG beyond those to which the IESG has
already explicitly committed (and to avoid commenting on the
latter).

>...
>   *> 6.1.  Documents in process or rejected
>   *> 
>   *>    For documents in process, reviews may be made public
> and posted on   *>    the RFC Editor web site at the request
> of the author.  The names of
> 
> I don't understand this discussion of documents in progress.
> There is a bit of a time warp here.  The RFC Editor (or the
> author) cannot know whether 6.1 or 6.2 applies until the end
> of the review process, so reviews cannot be posted until that
> time, if at all. The time warp gets worse if the author
> appeals to the IAB.
> 
> Question: Section 6.2 says the RFC Editor has an option of not
> posting a review, but there is no such statement for 6.1; is
> the implication that the RFC Editor is obliged to publish
> negative reviews?  Must the reviewer(s) be identified?

Please indicate how you would like this to be clarified, ideally
with text.
 
>...
> the Editorial Board, and the RFC   *>    Editor; such
> communications will remain confidential.  At minimum,   *>
> the author of either an accepted or rejected document shall
> receive a   *>    written summary of the review(s).
>   *> 
> 
> The last sentence above seems important enough to appears much
> earlier and not be an afterthought.

s/appears/appear/??

Please suggest where you would like it or leave this for the
final editing process.

thanks for your careful reading.
    john


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 08:52:56 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9M4j-0007LO-C8; Tue, 23 Jan 2007 08:52:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9M4i-0007LF-5n
	for independent@ietf.org; Tue, 23 Jan 2007 08:52:36 -0500
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9M4g-0006RK-SX
	for independent@ietf.org; Tue, 23 Jan 2007 08:52:36 -0500
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id CE3A319876D;
	Tue, 23 Jan 2007 15:52:33 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 809CD19876C;
	Tue, 23 Jan 2007 15:52:33 +0200 (EET)
Message-ID: <45B61322.2070407@piuha.net>
Date: Tue, 23 Jan 2007 15:52:34 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: independent@ietf.org
Subject: [INDEP] Re: comments on draft-klensin-independent-05.txt
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

>
>   *>    believe there is a high likelihood of conflicts or other interactions
>   *>    with IETF efforts (including believing that the document is one that
>   *>    the IESG should probably process), they may forward it to the IESG,
>   *>    or relevant ADs, for preliminary evaluation and comment.
>   *> 
>
> Comment: Nice theory, but in practice some IESG members have been
> less than responsive to such requests from the RFC Editor.
>   

I would be willing to work with you on finding better
ways to approach this. We generally respond on a timely
manner (I think) on the requests that come to us
for an official RFC 3932 decision. But given the two week
review deadlines, events in the WGs, etc. I know I at
least sometimes miss other mails and requests.

I wonder if John's goal would be met by the RFC Editor
deciding what order it runs the different steps in. For
instance, if the RFC Editor suspects that a collision
is very likely, sending the draft for RFC 3932 at that
time would seem more useful than spend half a year
in ISR process and only then finding out that, say,
IANA rules prevent publication.

Jari


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 08:59:16 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9MB5-0003UD-55; Tue, 23 Jan 2007 08:59:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9MB4-0003RX-IZ
	for independent@ietf.org; Tue, 23 Jan 2007 08:59:10 -0500
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9MAu-0000p7-PU
	for independent@ietf.org; Tue, 23 Jan 2007 08:59:10 -0500
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id EC71019876D;
	Tue, 23 Jan 2007 15:58:59 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 9B6B819876C;
	Tue, 23 Jan 2007 15:58:59 +0200 (EET)
Message-ID: <45B614A4.1050200@piuha.net>
Date: Tue, 23 Jan 2007 15:59:00 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: independent@ietf.org
Subject: [INDEP] comments on draft-klensin-rfc-independent-05
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

John,

I read this draft a few days ago, and was generally very
happy with it. A few comments, however:

1. There is no mention of IANA rules that sometimes
dictate what kind of documents may allocate new
numbers. While the rules and their use is defined
in other documents (the actual protocol RFCs,
RFC 2434, RFC 3932), it would seem useful to
mention the issue here as well. If not for other
reasons, at least for the benefit of folks who
consider making an independent submission.

2. I would like to synchronize draft-iesg-sponsoring-
guidelines and this draft. Here's what this draft
currently says:
>    o  Documents considered by IETF Working Groups but not standardized.
>       While many documents of this type are published via the IESG
>       approval path (see RFC 3932, Section 1 [RFC3932]), the independent
>       submission path has traditionally been open to them.  Because of
>       their intimate connection to the IETF Standards Process and WG
>       activites and the consequent sensitivity to exact statements of
>       relationships and to timing, there is reason to believe that all
>       such documents should be published only at IESG request.  In any
>       event, these documents are published for the historical record.
and here's my planned text for the next revision
of the IESG draft wrt. AD sponsoring historical
record RFCs:

> Relevance
>
>       ...
>
>       A document specifying a particular vendor's proprietary protocol
>       is typically more suitable as an independent submission than being
>       sponsored by an AD.  A document specifying an alternate approach
>       to an existing Standards Track solution is typically not a likely
>       candidate either.  But this is a judgment call.  For instance, if
>       there is general agreement in a WG for publishing a "road not
>       followed" document for the record, but the WG itself considers it
>       out of scope, AD sponsoring might be appropriate.
>
>    History
>
>       Sometimes the IETF, IESG, and the WG has more information about
>       the history of the document than the RFC Editor.  This is the case
>       with the "road not followed" documents mentioned above as well as
>       with other documents recently seriously considered in the IETF.
>       If the publication of these documents is appropriate, they are
> likely
>       more suitable as individual submissions than as independent
>       submissions.
This seems generally aligned, but the IESG draft is slightly less
strict, leaving some room for interpretation.

Note that "considered by a WG" is not an exact definition.

Any guidance from this list on this matter?

3. At the end of Section 2, you explain how the RFC Editor and the
IESG work together with regards to conflicts with the IETF standards
process. But this explanation only talks about delays and IESG
notes, not the possibility of not publishing at all which Section 4.8
lists also as a possibility. Please update Section 2.

4. Is the below reference correct, or should you simply be pointing
to RFC 2026? (Draft-iab-rfc-editor refers to RFC 2026 and draft-iesg-
sponsoring-guidelines when it talks about the IETF stream.)
>    o  Documents considered by IETF Working Groups but not standardized.
>       While many documents of this type are published via the IESG
>       approval path (see RFC 3932, Section 1 [RFC3932]),
5. I cannot find this reference, even after searching for it from
the set of old drafts:
>    [RFC3932upd]
>               Klensin, J., Ed., "IESG Notes on Independent Submissions
>               to the RFC Editor".
6. It was not obvious to me what the issues mentioned below
are. It also seems more appropriate to deal with those issues
in the RFC 3932bis work, than here. Or are they so deeply
related that we cannot talk about them separately?
>    This document contains text that, if agreed to by the community, may
>    suggest a reexamination of and a corresponding update to RFC 3932
>    [RFC3932].  Those issues, and proposals for changes, are discussed in
>    a different document [RFC3932upd], but they are semi-independent of
>    the content of this document, which focuses on the review and
>    approval process for independent submissions.
7. I am not sure that the second step may be taken out
of order below. If it was taken out of order, would it
imply that the RFC Editor is performing reviews
etc. even before the request for publication comes
in?
>    ... at the
>    discretion of the RFC Editor, steps after the first may be taken out
>    of order.
>
> 4.1.  Posting of Draft
>
>    The author(s) or editor(s) of a document post it as an Internet
>    Draft.
>
> 4.2.  Request for Publication
8. I am somewhat concerned that we're building quite a lot
of process for the independent submission path. I like the
transparency, use of reviewers, ability to escalate a problem
to the IAB, etc, but we should not attempt to build a
process which is similar to the IETF. In particular, Section
4.8 says:
>    ... comments on conflicts can be sent to the IESG
>    with copies to the RFC Editor.  Additional mechanisms may be
>    developed from time to time to inform a community that a document is
>    entering formal prepublication review. Comments not directly related
>    to IETF procedures or conflicts may be sent directly to the author(s)
>    and RFC Editor. 
I hope we are not developing an "RFC Editor Last Call" procedure
where the same community of Internet experts is expected to
provide feedback to both IETF and independent submissions.
Yet another mailing list to subscribe for everyone; yet more
documents to look at in a situation where we already get
too little LC review per document. I like the independent
submission process very much, and have a lot of trust in
the RFC editor and their selected reviewers for doing
competent publication decisions. But I think one of the
values of this system is that is indeed run by an independent
set of people, not calling for the general community
review in the same manner as IETF does.

I would suggest deleting the text in question.

9. Are these two text excerpts consistent:
>    o  Documents considered by IETF Working Groups but not standardized.
>       While many documents of this type are published via the IESG
>       approval path (see RFC 3932, Section 1 [RFC3932]), the independent
>       submission path has traditionally been open to them.  Because of
>       their intimate connection to the IETF Standards Process and WG
>       activites and the consequent sensitivity to exact statements of
>       relationships and to timing, there is reason to believe that all
>       such documents should be published only at IESG request.
>    However, the RFC Editor prefers that documents created
>    through IETF processes (e.g., working group output) be considered by
>    the IESG and submitted using this path only if a working group, or
>    the IESG, decline to publish it.
Jari


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 10:04:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9NCL-0000SP-24; Tue, 23 Jan 2007 10:04:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9NCJ-0000SB-2i
	for independent@ietf.org; Tue, 23 Jan 2007 10:04:31 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9NCG-0008CR-0F
	for independent@ietf.org; Tue, 23 Jan 2007 10:04:31 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1H9NCE-000FTM-VV; Tue, 23 Jan 2007 10:04:27 -0500
Date: Tue, 23 Jan 2007 10:04:25 -0500
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>
Message-ID: <E52F21E4346EF4F9A78A2BFE@p3.JCK.COM>
In-Reply-To: <45B614A4.1050200@piuha.net>
References: <45B614A4.1050200@piuha.net>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 325b777e1a3a618c889460b612a65510
Cc: independent@ietf.org
Subject: [INDEP] Re: comments on draft-klensin-rfc-independent-05
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

A few observations on this, mostly in my personal capacity.
I'll leave the rest to list discussion and will start making
changes when Olaf tells me to.

--On Tuesday, 23 January, 2007 15:59 +0200 Jari Arkko
<jari.arkko@piuha.net> wrote:

>...
> 2. I would like to synchronize draft-iesg-sponsoring-
> guidelines and this draft. 
>...
> [This] seems generally aligned, but the IESG draft is slightly
> less strict, leaving some room for interpretation.
> 
> Note that "considered by a WG" is not an exact definition.

As you may know, there was recently an extended discussion on
this general topic.  A position has developed that is not
reflected exactly by either of the above sets of definitions,
but that may be more workable if the IESG is willing to agree.
I won't claim any consensus, but where some of us stand on this
could probably be summarized as follows:

	If a document is the result of an IETF process, then we
	would prefer that the IESG consider it and render an
	opinion of some sort before it is submitted to the RFC
	Editor.  That opinion might be a decision by an AD to
	sponsor the document, it might be similar to any of the
	comments or categories called out in RFC 3932, it might
	be some less formal comment.  But the expectation is
	that the initial responsibility for a document emerging
	from an IETF process lies with the IESG and its members.
	An author or other proponent of such a document who
	submits it to the RFC Editor (as an independent
	submission) will be expected to present evidence that he
	or she made a diligent effort to obtain IESG review or
	comments.
	
	We believe that, in general, if the IESG wants something
	published (as normative, historical, or anything in
	between), then the IESG should say so.  The condition of
	an AD telling someone, about a document that resulted
	from an IETF process, "the IESG doesn't care about this
	enough to even consider it, why don't you try the RFC
	Editor" has the odor of encouraging forum-shopping and
	should be very rare. 
	
	The term "resulting from an IETF process" is
	(deliberately) even more vague than "considered by a WG"
	but is a superset of it that includes products of
	formally-constituted design teams, reports on the
	conclusions of BOFs, etc.
	
	For documents that result from IETF processes that the
	IESG does not decide to sponsor, the RFC Editor will
	consider the IESG's comments, if any, as part of the
	review process.  IESG recommendations and comments (or a
	decision to not comment, even on the degree of
	historical importance) will be given especially strong
	consideration when the relevant document is related to
	IETF processes rather than having strong technical or
	operational content.
	
The net result of this model is that, if a document results from
an IETF process, it is unlikely to be published as an RFC unless
it receives either sponsorship or, at least a positive review
and recommendation, from the IESG _or_ it represents a critical
review of an IETF conclusion or inability to reach a conclusion.


> 3. At the end of Section 2, you explain how the RFC Editor and
> the IESG work together with regards to conflicts with the IETF
> standards process. But this explanation only talks about
> delays and IESG notes, not the possibility of not publishing
> at all which Section 4.8 lists also as a possibility. Please
> update Section 2.

I would encourage some discussion of this subject on-list.   The
general assumption underlying the document is that the RFC
Editor and independent submission process is actually
independent.   Under that model of independence and subject only
to constraints the IESG imposes on itself (e.g., with RFC 3932
and its successors), the IESG can recommend anything it likes,
including publishing a document in PDF format with gold trim
along the edges of every page, specific changes or additions to
text, or a public burning of the document at the next IETF
social event.  The RFC Editor may then take the advice, modify
it, or ignore it as seems appropriate.  Since the RFC Editor
and, presumably all future RFC Editors, hold the opinions of the
IESG in high regard, it is unlikely that advice will be lightly
ignored.  However, many of us believe that it is very important
that the RFC Editor be permitted to publish documents that are
highly critical of IETF conclusions and, indeed, of the IETF.
That requirement implies not giving the IESG any sort of "DNP"
veto power.

> 4. Is the below reference correct, or should you simply be
> pointing to RFC 2026? (Draft-iab-rfc-editor refers to RFC 2026
> and draft-iesg- sponsoring-guidelines when it talks about the
> IETF stream.)
>>    o  Documents considered by IETF Working Groups but not
>>    standardized. While many documents of this type are
>>       published via the IESG approval path (see RFC 3932,
>>       Section 1 [RFC3932]),

The reference was intentional although, of course, if the IAB
wants it changed, I will change it.   The discussion above may
have some impact on this question.

> 5. I cannot find this reference, even after searching for it
> from the set of old drafts:
>>    [RFC3932upd]
>>               Klensin, J., Ed., "IESG Notes on Independent
>>               Submissions to the RFC Editor".

It has never been posted.  It is more or less the material that
appeared in earlier versions of draft-klensin-rfc-independent
that suggested modifications in 3932.   I should probably remove
the reference since I have been encouraged to not post it until
this document is settled.   In addition, if the principle of
"advice, not control" that is outlined above is agreed, that
document may become largely irrelevant.

> 6. It was not obvious to me what the issues mentioned below
> are. It also seems more appropriate to deal with those issues
> in the RFC 3932bis work, than here. Or are they so deeply
> related that we cannot talk about them separately?
>>    This document contains text that, if agreed to by the
>>    community, may suggest a reexamination of and a
>>    corresponding update to RFC 3932 [RFC3932].  Those issues,
>>    and proposals for changes, are discussed in a different
>>    document [RFC3932upd], but they are semi-independent of
>>    the content of this document, which focuses on the review
>>    and approval process for independent submissions.

See above.  If there is concensus about "advice, not control",
then this text can be removed after appropriate other text is
developed.

> 7. I am not sure that the second step may be taken out
> of order below. If it was taken out of order, would it
> imply that the RFC Editor is performing reviews
> etc. even before the request for publication comes
> in?
>>    ... at the
>>    discretion of the RFC Editor, steps after the first may be
>>    taken out of order.

As with almost everything else associated with the IETF and much
of the Internet community, there are times in which informal
inquiries and informal processes can save everyone a good deal
of time and energy.  I can't speak for how much it has happened
in the past (and the answers for the recent past and the more
distant past may differ) but I certainly would not want to
prevent the RFC Editor from responding, informally, to an
inquiry about whether or not a document with some particular
outline or subject matter would be acceptable for publication.
And, yes, that implies a mini-review prior to a formal request
for publication.

>> 4.1.  Posting of Draft
>> 
>>    The author(s) or editor(s) of a document post it as an
>>    Internet Draft.
>> 
>> 4.2.  Request for Publication
> 8. I am somewhat concerned that we're building quite a lot
> of process for the independent submission path. I like the
> transparency, use of reviewers, ability to escalate a problem
> to the IAB, etc, but we should not attempt to build a
> process which is similar to the IETF. In particular, Section
> 4.8 says:
>>    ... comments on conflicts can be sent to the IESG
>>    with copies to the RFC Editor.  Additional mechanisms may
>>    be developed from time to time to inform a community that
>>    a document is entering formal prepublication review.
>>    Comments not directly related to IETF procedures or
>>    conflicts may be sent directly to the author(s) and RFC
>>    Editor. 
> I hope we are not developing an "RFC Editor Last Call"
> procedure where the same community of Internet experts is
> expected to provide feedback to both IETF and independent
> submissions. Yet another mailing list to subscribe for
> everyone; yet more documents to look at in a situation where
> we already get too little LC review per document. I like the
> independent submission process very much, and have a lot of
> trust in the RFC editor and their selected reviewers for doing
> competent publication decisions. But I think one of the values
> of this system is that is indeed run by an independent set of
> people, not calling for the general community
> review in the same manner as IETF does.

> I would suggest deleting the text in question.

Personally, I share your concerns and would be happy to remove
that text.  However, during earlier discussions, there was a
great deal of interest expressed in more transparency, more
community review and input, etc.  There is obviously a tradeoff
in this: if one wants more assurance of transparency and
community review, then it is difficult to avoid more process and
formality.  The community needs to make up its collective mind.

> 9. Are these two text excerpts consistent:
>>    o  Documents considered by IETF Working Groups but not
>>    standardized. While many documents of this type are
>>       published via the IESG approval path (see RFC 3932,
>>       Section 1 [RFC3932]), the independent submission path
>>       has traditionally been open to them.  Because of their
>>       intimate connection to the IETF Standards Process and WG
>>       activites and the consequent sensitivity to exact
>>       statements of relationships and to timing, there is
>>       reason to believe that all such documents should be
>>       published only at IESG request. 
>>    However, the RFC Editor
>>    prefers that documents created through IETF processes
>>    (e.g., working group output) be considered by the IESG and
>>    submitted using this path only if a working group, or the
>>    IESG, decline to publish it.

Please see the discussion above, which this text more or less
predicted but did not resolve.  As far as consistency is
concerned, the statements indicate that a policy shift in
underway... a shift from "the RFC Editor has certainly published
many IETF products as independent submissions in the past" to
"maybe that is a bad idea in today's context and, in general,
the only such documents that should be handled as independent
submissions are explicit critiques of IETF results or
non-results.

     regards,
       john



_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 11:06:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9OA3-0001V8-DY; Tue, 23 Jan 2007 11:06:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9OA1-0001V0-NP
	for independent@ietf.org; Tue, 23 Jan 2007 11:06:13 -0500
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9O9z-0004nf-2e
	for independent@ietf.org; Tue, 23 Jan 2007 11:06:13 -0500
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id D6EB519876D;
	Tue, 23 Jan 2007 18:06:09 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 85B6619876C;
	Tue, 23 Jan 2007 18:06:09 +0200 (EET)
Message-ID: <45B63272.2070903@piuha.net>
Date: Tue, 23 Jan 2007 18:06:10 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [INDEP] Re: comments on draft-klensin-rfc-independent-05
References: <45B614A4.1050200@piuha.net> <E52F21E4346EF4F9A78A2BFE@p3.JCK.COM>
In-Reply-To: <E52F21E4346EF4F9A78A2BFE@p3.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

John,
> 	If a document is the result of an IETF process, then we
> 	would prefer that the IESG consider it and render an
> 	opinion of some sort before it is submitted to the RFC
> 	Editor.  That opinion might be a decision by an AD to
> 	sponsor the document, it might be similar to any of the
> 	comments or categories called out in RFC 3932, it might
> 	be some less formal comment.  But the expectation is
> 	that the initial responsibility for a document emerging
> 	from an IETF process lies with the IESG and its members.
> 	An author or other proponent of such a document who
> 	submits it to the RFC Editor (as an independent
> 	submission) will be expected to present evidence that he
> 	or she made a diligent effort to obtain IESG review or
> 	comments.
> 	
> 	We believe that, in general, if the IESG wants something
> 	published (as normative, historical, or anything in
> 	between), then the IESG should say so.  The condition of
> 	an AD telling someone, about a document that resulted
> 	from an IETF process, "the IESG doesn't care about this
> 	enough to even consider it, why don't you try the RFC
> 	Editor" has the odor of encouraging forum-shopping and
> 	should be very rare. 
> 	
> 	The term "resulting from an IETF process" is
> 	(deliberately) even more vague than "considered by a WG"
> 	but is a superset of it that includes products of
> 	formally-constituted design teams, reports on the
> 	conclusions of BOFs, etc.
> 	
> 	For documents that result from IETF processes that the
> 	IESG does not decide to sponsor, the RFC Editor will
> 	consider the IESG's comments, if any, as part of the
> 	review process.  IESG recommendations and comments (or a
> 	decision to not comment, even on the degree of
> 	historical importance) will be given especially strong
> 	consideration when the relevant document is related to
> 	IETF processes rather than having strong technical or
> 	operational content.
> 	
> The net result of this model is that, if a document results from
> an IETF process, it is unlikely to be published as an RFC unless
> it receives either sponsorship or, at least a positive review
> and recommendation, from the IESG _or_ it represents a critical
> review of an IETF conclusion or inability to reach a conclusion.
>   
This sounds reasonable to me.
>> 3. At the end of Section 2, you explain how the RFC Editor and
>> the IESG work together with regards to conflicts with the IETF
>> standards process. But this explanation only talks about
>> delays and IESG notes, not the possibility of not publishing
>> at all which Section 4.8 lists also as a possibility. Please
>> update Section 2.
>>     
>
> ...  However, many of us believe that it is very important
> that the RFC Editor be permitted to publish documents that are
> highly critical of IETF conclusions and, indeed, of the IETF.
> That requirement implies not giving the IESG any sort of "DNP"
> veto power.
>   
Sure. But I was not commenting on the lack of veto
power. I was commenting on the inconsistency between
two document parts. I think its fine if the RFC Editor
makes its own decision about the publication, having gotten
IESG's input. That's what "independent" means.
But your Section 4.8 and the current RFC 3932
implies that the IESG has the ability to provide the "DNP"
input. I think that ability should be retained, and reflected
in the same manner in Sections 2 and 4.8.
> See above.  If there is concensus about "advice, not control",
> then this text can be removed after appropriate other text is
> developed.
>   
Ok.
> As with almost everything else associated with the IETF and much
> of the Internet community, there are times in which informal
> inquiries and informal processes can save everyone a good deal
> of time and energy.  I can't speak for how much it has happened
> in the past (and the answers for the recent past and the more
> distant past may differ) but I certainly would not want to
> prevent the RFC Editor from responding, informally, to an
> inquiry about whether or not a document with some particular
> outline or subject matter would be acceptable for publication.
> And, yes, that implies a mini-review prior to a formal request
> for publication.
>   
Ok.
>> 8. I am somewhat concerned that we're building quite a lot
>> of process for the independent submission path. I like the
>> transparency, use of reviewers, ability to escalate a problem
>> to the IAB, etc, but we should not attempt to build a
>> process which is similar to the IETF. In particular, Section
>> 4.8 says:
>>     
>>>    ... comments on conflicts can be sent to the IESG
>>>    with copies to the RFC Editor.  Additional mechanisms may
>>>    be developed from time to time to inform a community that
>>>    a document is entering formal prepublication review.
>>>    Comments not directly related to IETF procedures or
>>>    conflicts may be sent directly to the author(s) and RFC
>>>    Editor. 
>>>       
>> I hope we are not developing an "RFC Editor Last Call"
>> procedure where the same community of Internet experts is
>> expected to provide feedback to both IETF and independent
>> submissions. Yet another mailing list to subscribe for
>> everyone; yet more documents to look at in a situation where
>> we already get too little LC review per document. I like the
>> independent submission process very much, and have a lot of
>> trust in the RFC editor and their selected reviewers for doing
>> competent publication decisions. But I think one of the values
>> of this system is that is indeed run by an independent set of
>> people, not calling for the general community
>> review in the same manner as IETF does.
>>     
>
>   
>> I would suggest deleting the text in question.
>>     
>
> Personally, I share your concerns and would be happy to remove
> that text. 
OK
> However, during earlier discussions, there was a
> great deal of interest expressed in more transparency, more
> community review and input, etc.  There is obviously a tradeoff
> in this: if one wants more assurance of transparency and
> community review, then it is difficult to avoid more process and
> formality.  The community needs to make up its collective mind.
>   
Right. It is important that we settle on what the
general direction is. I believe very much in transparency,
ability to challenge bad decisions, etc. But I'm not sure
adding significant community review is compatible with
the idea of an independent submission process, at
least if the community ~ the people who also attend
the IETF.

Anyway, we are discussing about philosophy while
the actual change that I suggested was fairly small...

Jari



_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 11:15:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9OIa-0005bY-9j; Tue, 23 Jan 2007 11:15:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9OIZ-0005as-5j
	for independent@ietf.org; Tue, 23 Jan 2007 11:15:03 -0500
Received: from mtagate7.uk.ibm.com ([195.212.29.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9OHZ-0006Lt-L1
	for independent@ietf.org; Tue, 23 Jan 2007 11:14:03 -0500
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate7.uk.ibm.com (8.13.8/8.13.8) with ESMTP id l0NGE11t181698
	for <independent@ietf.org>; Tue, 23 Jan 2007 16:14:01 GMT
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com
	[9.149.37.212])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v8.2) with
	ESMTP id l0NGE0Nc1499388
	for <independent@ietf.org>; Tue, 23 Jan 2007 16:14:00 GMT
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av01.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l0NGE07W029003
	for <independent@ietf.org>; Tue, 23 Jan 2007 16:14:00 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d06av01.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l0NGE0Zl028986; Tue, 23 Jan 2007 16:14:00 GMT
Received: from [9.4.210.68] ([9.4.210.68])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id RAA322122; 
	Tue, 23 Jan 2007 17:13:57 +0100
Message-ID: <45B63445.40905@zurich.ibm.com>
Date: Tue, 23 Jan 2007 17:13:57 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [INDEP] Re: comments on draft-klensin-rfc-independent-05
References: <45B614A4.1050200@piuha.net> <E52F21E4346EF4F9A78A2BFE@p3.JCK.COM>
In-Reply-To: <E52F21E4346EF4F9A78A2BFE@p3.JCK.COM>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: independent@ietf.org, Jari Arkko <jari.arkko@piuha.net>
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org


On 2007-01-23 16:04, John C Klensin wrote:
> A few observations on this, mostly in my personal capacity.
> I'll leave the rest to list discussion and will start making
> changes when Olaf tells me to.
> 
> --On Tuesday, 23 January, 2007 15:59 +0200 Jari Arkko
> <jari.arkko@piuha.net> wrote:
> 

<snip>

> 	
> The net result of this model is that, if a document results from
> an IETF process, it is unlikely to be published as an RFC unless
> it receives either sponsorship or, at least a positive review
> and recommendation, from the IESG _or_ it represents a critical
> review of an IETF conclusion or inability to reach a conclusion.

That seems to exclude publication of simply dissenting views.
Is that the intention? Personally I am generally in favour
of the IETF publishing "road not followed" documents, but we do
have various instances of such things not getting published.
Should we exclude independent submission as a backstop mechanism?

>> 3. At the end of Section 2, you explain how the RFC Editor and
>> the IESG work together with regards to conflicts with the IETF
>> standards process. But this explanation only talks about
>> delays and IESG notes, not the possibility of not publishing
>> at all which Section 4.8 lists also as a possibility. Please
>> update Section 2.
> 
> I would encourage some discussion of this subject on-list.   The
> general assumption underlying the document is that the RFC
> Editor and independent submission process is actually
> independent.   Under that model of independence and subject only
> to constraints the IESG imposes on itself (e.g., with RFC 3932
> and its successors), the IESG can recommend anything it likes,
> including publishing a document in PDF format with gold trim
> along the edges of every page, specific changes or additions to
> text, or a public burning of the document at the next IETF
> social event.  The RFC Editor may then take the advice, modify
> it, or ignore it as seems appropriate.  Since the RFC Editor
> and, presumably all future RFC Editors, hold the opinions of the
> IESG in high regard, it is unlikely that advice will be lightly
> ignored.  However, many of us believe that it is very important
> that the RFC Editor be permitted to publish documents that are
> highly critical of IETF conclusions and, indeed, of the IETF.
> That requirement implies not giving the IESG any sort of "DNP"
> veto power.

I didn't read Jari's comment as asking for that. But it does seem
fair to stipulate that the RFC Editor is expected to do the right
thing in flagrant cases (e.g. documents that infringe explicit
IANA considerations). That is, after all, why 3932 was written
in the first place.

<snip>

>> 6. It was not obvious to me what the issues mentioned below
>> are. It also seems more appropriate to deal with those issues
>> in the RFC 3932bis work, than here. Or are they so deeply
>> related that we cannot talk about them separately?
>>>    This document contains text that, if agreed to by the
>>>    community, may suggest a reexamination of and a
>>>    corresponding update to RFC 3932 [RFC3932].  Those issues,
>>>    and proposals for changes, are discussed in a different
>>>    document [RFC3932upd], but they are semi-independent of
>>>    the content of this document, which focuses on the review
>>>    and approval process for independent submissions.
> 
> See above.  If there is concensus about "advice, not control",
> then this text can be removed after appropriate other text is
> developed.

I don't object to this text, but it's true that the fewer such
cross-references we have, the easier it is to make orthogonal
document updates.

<snip>

>> 8. I am somewhat concerned that we're building quite a lot
>> of process for the independent submission path. I like the
>> transparency, use of reviewers, ability to escalate a problem
>> to the IAB, etc, but we should not attempt to build a
>> process which is similar to the IETF. In particular, Section
>> 4.8 says:
>>>    ... comments on conflicts can be sent to the IESG
>>>    with copies to the RFC Editor.  Additional mechanisms may
>>>    be developed from time to time to inform a community that
>>>    a document is entering formal prepublication review.
>>>    Comments not directly related to IETF procedures or
>>>    conflicts may be sent directly to the author(s) and RFC
>>>    Editor. 
>> I hope we are not developing an "RFC Editor Last Call"
>> procedure where the same community of Internet experts is
>> expected to provide feedback to both IETF and independent
>> submissions. Yet another mailing list to subscribe for
>> everyone; yet more documents to look at in a situation where
>> we already get too little LC review per document. I like the
>> independent submission process very much, and have a lot of
>> trust in the RFC editor and their selected reviewers for doing
>> competent publication decisions. But I think one of the values
>> of this system is that is indeed run by an independent set of
>> people, not calling for the general community
>> review in the same manner as IETF does.
> 
>> I would suggest deleting the text in question.
> 
> Personally, I share your concerns and would be happy to remove
> that text.  However, during earlier discussions, there was a
> great deal of interest expressed in more transparency, more
> community review and input, etc.  There is obviously a tradeoff
> in this: if one wants more assurance of transparency and
> community review, then it is difficult to avoid more process and
> formality.  The community needs to make up its collective mind.

Personal opinion: I want the ISR process to be as transparent as
possible. If it's to be a backstop for any untoward behaviour
in the IETF process, it needs to be at least as transparent as the
IETF process, where we have an increasing tendency towards public
reviews (e.g. http://www.alvestrand.no/ietf/gen/art/gen-art.html).
But I don't think we need rules here so much as an agreed principle
of openness, and practical steps to implement it, such as public
email archives whenever possible.

    Brian

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 12:11:21 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9PAf-0008JE-Ay; Tue, 23 Jan 2007 12:10:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9PAe-0008IF-9j
	for independent@ietf.org; Tue, 23 Jan 2007 12:10:56 -0500
Received: from adsl-68-22-232-249.dsl.lgtpmi.ameritech.net ([68.22.232.249]
	helo=aland.bbn.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H9PAc-0003BI-Vz
	for independent@ietf.org; Tue, 23 Jan 2007 12:10:56 -0500
Received: by aland.bbn.com (Postfix, from userid 19883)
	id 3E28764; Tue, 23 Jan 2007 12:10:50 -0500 (EST)
Received: from aland.bbn.com (localhost [127.0.0.1])
	by aland.bbn.com (Postfix) with ESMTP id 3BD9D5F;
	Tue, 23 Jan 2007 12:10:50 -0500 (EST)
To: Brian E Carpenter <brc@zurich.ibm.com>
Subject: Re: [INDEP] Re: comments on draft-klensin-rfc-independent-05 
In-Reply-To: Your message of "Tue, 23 Jan 2007 17:13:57 +0100."
	<45B63445.40905@zurich.ibm.com> 
Date: Tue, 23 Jan 2007 12:10:50 -0500
From: Craig Partridge <craig@aland.bbn.com>
Message-Id: <20070123171050.3E28764@aland.bbn.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: John C Klensin <john-ietf@jck.com>, independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org


In message <45B63445.40905@zurich.ibm.com>, Brian E Carpenter writes:

>On 2007-01-23 16:04, John C Klensin wrote:
>...
>> --On Tuesday, 23 January, 2007 15:59 +0200 Jari Arkko
>> <jari.arkko@piuha.net> wrote:
>> 
>
><snip>
>
>> 	
>> The net result of this model is that, if a document results from
>> an IETF process, it is unlikely to be published as an RFC unless
>> it receives either sponsorship or, at least a positive review
>> and recommendation, from the IESG _or_ it represents a critical
>> review of an IETF conclusion or inability to reach a conclusion.
>
>That seems to exclude publication of simply dissenting views.
>Is that the intention? Personally I am generally in favour
>of the IETF publishing "road not followed" documents, but we do
>have various instances of such things not getting published.
>Should we exclude independent submission as a backstop mechanism?

Since the IESG was created, the issue of coordinating the RFC Editor's
decisions with the IESG has been something of a third rail.  And
labeling the independent RFC series as a place to document "road
not followed" (or more vigorously dissenting opinions) in defiance of
the IESG seems an invitation to institutional conflict.

I agree this creates a challenge, namely, that one can present a road
not followed provided it never appears in a WG, but actually participating
in a WG may cause the idea to be unpublishable as an RFC (assuming
a sufficiently unreasonable AD -- I assume a reasonable AD is happy to
allow such publications).  But on balance, the current plan seems the
better of two evils.  Here's my logic.

    If the RFC Editor gets to publish road not followed documents
    over IESG objections, we have institutional clashes if either
    the RFC Editor is unreasonable or an AD is unreasonable.

    If the IESG gets to determine if road not followed documents
    are published, then the only clash is unreasonable AD with
    authors.

Thanks!

Craig

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 12:30:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9PTL-0008Pz-AX; Tue, 23 Jan 2007 12:30:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9PTK-0008Pu-PX
	for independent@ietf.org; Tue, 23 Jan 2007 12:30:14 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9PTJ-0000tq-E1
	for independent@ietf.org; Tue, 23 Jan 2007 12:30:14 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l0NHTKh6002319;
	Tue, 23 Jan 2007 09:29:20 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id JAA21072;
	Tue, 23 Jan 2007 09:29:19 -0800 (PST)
Date: Tue, 23 Jan 2007 09:29:19 -0800 (PST)
Message-Id: <200701231729.JAA21072@gra.isi.edu>
To: independent@ietf.org, aboba@internaut.com
Subject: Re: [INDEP] Re: Last call on draft-klensin-independent...
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@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.

Bernard,

Certainly everyone understands this, and I thought that 2026 already
stated it.  Whatever. It is not clear that this is the correct place
for defining legal mappings of document streams onto RFC categories,
but as a pragmatic matter, fine, let's make sure draft-klensin is
explicit about what categories are allowed.

  *> 
  *> 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 

Wow!! You have missed a calling as a lawyer!! Or ARE you a lawyer?
That implication seems far-fetched to me, and clearly was not intended.

Bob Braden

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 12:40:12 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9Pcr-0005wn-IQ; Tue, 23 Jan 2007 12:40:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Pcr-0005wg-0C
	for independent@ietf.org; Tue, 23 Jan 2007 12:40:05 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9Pcp-00072G-Pq
	for independent@ietf.org; Tue, 23 Jan 2007 12:40:04 -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@internaut.com>)
	id 1H9Pcp-0005fG-Ac; Tue, 23 Jan 2007 12:40:03 -0500
Received: by internaut.com (Postfix, from userid 1000)
	id 1701D3A708; Tue, 23 Jan 2007 09:40:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by internaut.com (Postfix) with ESMTP id 08EE439FC3;
	Tue, 23 Jan 2007 09:40:05 -0800 (PST)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.66.58
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: aboba
Date: Tue, 23 Jan 2007 09:40:04 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: Bob Braden <braden@ISI.EDU>
Subject: Re: [INDEP] Re: Last call on draft-klensin-independent...
In-Reply-To: <200701231729.JAA21072@gra.isi.edu>
Message-ID: <Pine.LNX.4.64.0701230937350.16599@internaut.com>
References: <200701231729.JAA21072@gra.isi.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

> Certainly everyone understands this, and I thought that 2026 already
> stated it.  Whatever. It is not clear that this is the correct place
> for defining legal mappings of document streams onto RFC categories,
> but as a pragmatic matter, fine, let's make sure draft-klensin is
> explicit about what categories are allowed.

My concern in part derives from recent Independent Submissions which, 
while specified as Informational Status, modify Standards Track 
documents, or request the allocation of IANA parameters reserved for 
Standards Action or IETF Consensus.  This does not appear to be precluded 
by this document, yet if allowed to proceed would circumvent RFC 2026. 

> 
>   *> 
>   *> 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 
> 
> Wow!! You have missed a calling as a lawyer!! Or ARE you a lawyer?
> That implication seems far-fetched to me, and clearly was not intended.


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 13:06:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9Q2U-0002WL-TG; Tue, 23 Jan 2007 13:06:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Q2T-0002Vx-N8
	for independent@ietf.org; Tue, 23 Jan 2007 13:06:33 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9Q2Q-0000br-CS
	for independent@ietf.org; Tue, 23 Jan 2007 13:06:32 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l0NI5e2r013674;
	Tue, 23 Jan 2007 10:05:40 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id KAA21127;
	Tue, 23 Jan 2007 10:05:40 -0800 (PST)
Date: Tue, 23 Jan 2007 10:05:40 -0800 (PST)
Message-Id: <200701231805.KAA21127@gra.isi.edu>
To: braden@ISI.EDU, aboba@internaut.com
Subject: Re: [INDEP] Re: Last call on draft-klensin-independent...
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org


 
  *> My concern in part derives from recent Independent Submissions which, 
  *> while specified as Informational Status, modify Standards Track 
  *> documents, or request the allocation of IANA parameters reserved for 
  *> Standards Action or IETF Consensus.  This does not appear to be precluded 
  *> by this document, yet if allowed to proceed would circumvent RFC 2026. 
  *> 
  *> > 

I hear with your concerns.  Let's try to talk about specific examples.
The IANA parameters are clearly wrong.  Now, an Independent Submission
should be able to DISCUSS or SUGGEST a POSSIBLE change in a standards
track protocol, I believe; it should not go beyond that, and it should
be clear.  Do you think we have violated this?

Bob Braden


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 14:13:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9R4w-0001ZV-1h; Tue, 23 Jan 2007 14:13:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9R4v-0001Yn-67
	for independent@ietf.org; Tue, 23 Jan 2007 14:13:09 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9R4f-0005P6-6K
	for independent@ietf.org; Tue, 23 Jan 2007 14:13:09 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1H9R4e-000IE0-6q; Tue, 23 Jan 2007 14:12:52 -0500
Date: Tue, 23 Jan 2007 14:12:51 -0500
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>
Message-ID: <4CBCDF149EFB3BC373672625@p3.JCK.COM>
In-Reply-To: <45B63272.2070903@piuha.net>
References: <45B614A4.1050200@piuha.net> <E52F21E4346EF4F9A78A2BFE@p3.JCK.COM>
	<45B63272.2070903@piuha.net>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: independent@ietf.org
Subject: [INDEP] Section 2 and Section 4.8 (was: Re: comments on
 draft-klensin-rfc-independent-05)
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



--On Tuesday, 23 January, 2007 18:06 +0200 Jari Arkko
<jari.arkko@piuha.net> wrote:

>> ...  However, many of us believe that it is very important
>> that the RFC Editor be permitted to publish documents that are
>> highly critical of IETF conclusions and, indeed, of the IETF.
>> That requirement implies not giving the IESG any sort of "DNP"
>> veto power.
>>   
> Sure. But I was not commenting on the lack of veto
> power. I was commenting on the inconsistency between
> two document parts. I think its fine if the RFC Editor
> makes its own decision about the publication, having gotten
> IESG's input. That's what "independent" means.
> But your Section 4.8 and the current RFC 3932
> implies that the IESG has the ability to provide the "DNP"
> input. I think that ability should be retained, and reflected
> in the same manner in Sections 2 and 4.8.

We agree that it should be fixed. 

I was just trying to stimulate some discussion about what the
fix should be.

    john
 




_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 14:33:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9ROk-0003F6-Bf; Tue, 23 Jan 2007 14:33:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9ROj-0003F1-DH
	for independent@ietf.org; Tue, 23 Jan 2007 14:33:37 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9ROh-0001zz-M4
	for independent@ietf.org; Tue, 23 Jan 2007 14:33:37 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1H9ROe-000ITY-IL; Tue, 23 Jan 2007 14:33:32 -0500
Date: Tue, 23 Jan 2007 14:33:31 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brc@zurich.ibm.com>
Subject: Re: [INDEP] Re: comments on
 draft-klensin-rfc-independent-05
Message-ID: <BD762EB61BBF0CC1DEBFCC6F@p3.JCK.COM>
In-Reply-To: <45B63445.40905@zurich.ibm.com>
References: <45B614A4.1050200@piuha.net> <E52F21E4346EF4F9A78A2BFE@p3.JCK.COM>
	<45B63445.40905@zurich.ibm.com>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: independent@ietf.org, Jari Arkko <jari.arkko@piuha.net>
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



--On Tuesday, 23 January, 2007 17:13 +0100 Brian E Carpenter
<brc@zurich.ibm.com> wrote:

> ...
>> The net result of this model is that, if a document results
>> from an IETF process, it is unlikely to be published as an
>> RFC unless it receives either sponsorship or, at least a
>> positive review and recommendation, from the IESG _or_ it
>> represents a critical review of an IETF conclusion or
>> inability to reach a conclusion.
> 
> That seems to exclude publication of simply dissenting views.
> Is that the intention? Personally I am generally in favour
> of the IETF publishing "road not followed" documents, but we do
> have various instances of such things not getting published.
> Should we exclude independent submission as a backstop
> mechanism?

Certainly not, at least IMO, but I may have coded a bit too much
into "critical review".  If the IESG is unwilling to take
responsibility for publishing a "road not followed" document
that is connected to IETF outputs or processes, I'm suggesting a
slightly higher standard for independent submission RFC
publication.  To vastly oversimplify the problem, suppose that
the IETF has agreed upon, and published, a standards-track
document that says "when there is a conflict, the packet that
arrives on the higher-bandwidth connection should be preferred
and forwarded".  I believe that is wrong and that the packet
that arrives on the lower-bandwidth connection should be given
preference.    Assuming I'd like my views published, I can
generate two types of documents:

	(1) A document that simply parallels the standards-track
	one except that it reaches the opposite conclusion.
	This is a "dissenting view".    Presumably the IESG asks
	the RFC Editor to slap warning labels all over the thing
	and maybe even requests non-publication.
	
	(2) A document that reviews the IETF decision in some
	careful and critical way (I know you know this, but, for
	the benefit of others, remember "critical" doesn't imply
	negative) and that explains why, in the opinion of the
	author, the decision may have been the wrong one.

Now I contend that the first document is historically nearly
useless: it has no value other than to document the fact that
there was not complete consensus in the IETF.  The second
document, however, if it is competent, should be published even
if it make the IESG unhappy... perhaps _especially_ if it makes
the IESG unhappy, because the dissenting position is likely to
be historically useful and possibly even important.

>>> 3. At the end of Section 2, you explain how the RFC Editor
>>> and the IESG work together with regards to conflicts with
>>> the IETF standards process. But this explanation only talks
>>> about delays and IESG notes, not the possibility of not
>>> publishing at all which Section 4.8 lists also as a
>>> possibility. Please update Section 2.
>> 
>> I would encourage some discussion of this subject on-list.
>> The general assumption underlying the document is that the RFC
>> Editor and independent submission process is actually
>> independent.   Under that model of independence and subject
>> only to constraints the IESG imposes on itself (e.g., with
>> RFC 3932 and its successors), the IESG can recommend anything
>...

> I didn't read Jari's comment as asking for that. But it does
> seem
> fair to stipulate that the RFC Editor is expected to do the
> right
> thing in flagrant cases (e.g. documents that infringe explicit
> IANA considerations). That is, after all, why 3932 was written
> in the first place.

IMO, the RFC Editor is _always_ expected to do the right thing.
It is not clear to me that making a list of specific cases does
much more than brand the omitted cases as one in which the
community doesn't care whether the RFC Editor does the right
thing or not.  To paraphrase a remark Jari made elsewhere in his
note, we probably do not need more rules and procedures here.

But, if someone has specific language they would like in the
document to describe these situations, please propose it and
I'll happily let the IAB figure out what to do with it :-).

>...

>>> 8. I am somewhat concerned that we're building quite a lot
>>> of process for the independent submission path. I like the
>>> transparency, use of reviewers, ability to escalate a problem
>>> to the IAB, etc, but we should not attempt to build a
>>> process which is similar to the IETF. In particular, Section
>...
>>> I hope we are not developing an "RFC Editor Last Call"
>>> procedure where the same community of Internet experts is
>>> expected to provide feedback to both IETF and independent
>>> submissions. Yet another mailing list to subscribe for
>>> everyone; yet more documents to look at in a situation where
>>> we already get too little LC review per document. I like the
>>> independent submission process very much, and have a lot of
>>> trust in the RFC editor and their selected reviewers for
>>> doing competent publication decisions. But I think one of
>>> the values of this system is that is indeed run by an
>>> independent set of people, not calling for the general
>>> community review in the same manner as IETF does.
>> 
>>> I would suggest deleting the text in question.

>> Personally, I share your concerns and would be happy to remove
>> that text.  However, during earlier discussions, there was a
>> great deal of interest expressed in more transparency, more
>> community review and input, etc.  There is obviously a
>> tradeoff in this: if one wants more assurance of transparency
>> and community review, then it is difficult to avoid more
>> process and formality.  The community needs to make up its
>> collective mind.
> 
> Personal opinion: I want the ISR process to be as transparent
> as
> possible. If it's to be a backstop for any untoward behaviour
> in the IETF process, it needs to be at least as transparent as
> the
> IETF process, where we have an increasing tendency towards
> public reviews (e.g.
> http://www.alvestrand.no/ietf/gen/art/gen-art.html).
> But I don't think we need rules here so much as an agreed
> principle
> of openness, and practical steps to implement it, such as
> public email archives whenever possible.

That difference of opinion is why the text is the way it is,
more or less.  As I tried to say, there is a tension among
reasonable objectives.

     john


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 14:45:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9RaK-0000mE-RF; Tue, 23 Jan 2007 14:45:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9RaJ-0000lc-CA
	for independent@ietf.org; Tue, 23 Jan 2007 14:45:35 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9RaH-0003pM-Vo
	for independent@ietf.org; Tue, 23 Jan 2007 14:45:35 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1H9RaF-000IWH-OR; Tue, 23 Jan 2007 14:45:31 -0500
Date: Tue, 23 Jan 2007 14:45:31 -0500
From: John C Klensin <john-ietf@jck.com>
To: Bernard Aboba <aboba@internaut.com>, Bob Braden <braden@ISI.EDU>
Subject: Re: [INDEP] Re: Last call on
 draft-klensin-independent...
Message-ID: <5C8ACAC87DCC3872C9ADBDCC@p3.JCK.COM>
In-Reply-To: <Pine.LNX.4.64.0701230937350.16599@internaut.com>
References: <200701231729.JAA21072@gra.isi.edu>
	<Pine.LNX.4.64.0701230937350.16599@internaut.com>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



--On Tuesday, 23 January, 2007 09:40 -0800 Bernard Aboba
<aboba@internaut.com> wrote:

>> Certainly everyone understands this, and I thought that 2026
>> already stated it.  Whatever. It is not clear that this is
>> the correct place for defining legal mappings of document
>> streams onto RFC categories, but as a pragmatic matter, fine,
>> let's make sure draft-klensin is explicit about what
>> categories are allowed.
> 
> My concern in part derives from recent Independent Submissions
> which,  while specified as Informational Status, modify
> Standards Track  documents, or request the allocation of IANA
> parameters reserved for  Standards Action or IETF Consensus.
> This does not appear to be precluded  by this document, yet if
> allowed to proceed would circumvent RFC 2026. 

In practical terms, if such a document reaches the IESG on
RFC3932 review, the IESG should say "whoops, RFCs 2026 and 9999
require that the actions specified here by done only in
standards track documents, so we are taking over responsibility"
and the IANA should say "the document can't do that because
those things can be done only in a standards-track document".  

While I would expect the RFC Editor to speak up if they
discovered these, or similar problems (that is exactly what
asking a relevant AD to do an early-stage review is all above),
requiring that the RFC Editor detect such things would be
pointless: we can't expect them to have the needed comprehensive
knowledge and that fact is what the required IESG and IANA
reviews are all about.  If I recall, the drafts doesn't
explicitly require an IANA review -- perhaps that should be
fixed, or perhaps we can rely on the RFC Editor's good sense
when a document appears to require IANA actions).

It seems to me that your request is getting close to a provision
that says "the RFC Editor will not be stupid and will avoid
acting in ways that are obviously intended to end-run
established IETF or IANA procedures or otherwise against the
clear best interests of the community".   If there is consensus
that such a statement should be added, and on appropriate text,
I'll be happy to add it.   However...

    john


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 15:03:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9Rr8-0000lK-SE; Tue, 23 Jan 2007 15:02:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Rr7-0000jE-Rc
	for independent@ietf.org; Tue, 23 Jan 2007 15:02:57 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9Rr5-0006ac-FE
	for independent@ietf.org; Tue, 23 Jan 2007 15:02:57 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l0NK2PKW017013;
	Tue, 23 Jan 2007 12:02:25 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id MAA21265;
	Tue, 23 Jan 2007 12:02:24 -0800 (PST)
Date: Tue, 23 Jan 2007 12:02:24 -0800 (PST)
Message-Id: <200701232002.MAA21265@gra.isi.edu>
To: aboba@internaut.com, braden@ISI.EDU, john-ietf@jck.com
Subject: Re: [INDEP] Re: Last call on
 draft-klensin-independent...
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org


  *> explicitly require an IANA review -- perhaps that should be
  *> fixed, or perhaps we can rely on the RFC Editor's good sense
  *> when a document appears to require IANA actions).
  *> 

Note that the problem is not just any IANA action... an experimental
protocol that is outside the IETF may register with IANA.  The bug is
if the action for an independent submission is treated as a STANDARDS
registration, subject to IETF consensus, etc.

  *> It seems to me that your request is getting close to a provision
  *> that says "the RFC Editor will not be stupid and will avoid
  *> acting in ways that are obviously intended to end-run
  *> established IETF or IANA procedures or otherwise against the
  *> clear best interests of the community".   If there is consensus

The RFC Editor agrees to not be stupid and to avoid acting in ways
that are obviously intended to end-run established community procedures
or in any other way act against the best interests of the community.

In fact, come to think of it, the RFC Editor has been trying its best
to accomplish this since before a number of you were born.  Hey,
let's codify Truth, Justics, and the American Way of Life!

Bob Braden

  *> that such a statement should be added, and on appropriate text,
  *> I'll be happy to add it.   However...
  *> 
  *>     john
  *> 

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Tue Jan 23 15:31:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9SIM-0006ev-Dv; Tue, 23 Jan 2007 15:31:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9SIL-0006bD-3G
	for independent@ietf.org; Tue, 23 Jan 2007 15:31:05 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9SIJ-000312-Mh
	for independent@ietf.org; Tue, 23 Jan 2007 15:31:05 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l0NKThqi023399;
	Tue, 23 Jan 2007 12:29:43 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id MAA21304;
	Tue, 23 Jan 2007 12:29:43 -0800 (PST)
Date: Tue, 23 Jan 2007 12:29:43 -0800 (PST)
Message-Id: <200701232029.MAA21304@gra.isi.edu>
To: braden@ISI.EDU, jari.arkko@piuha.net
Subject: Re: [INDEP] Re: comments on draft-klensin-independent-05.txt
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org


.
  *> >   *> 
  *> >
  *> > Comment: Nice theory, but in practice some IESG members have been
  *> > less than responsive to such requests from the RFC Editor.
  *> >   
  *> 
  *> I would be willing to work with you on finding better

We would welcome that cooperation.

  *> ways to approach this. We generally respond on a timely
  *> manner (I think) on the requests that come to us
  *> for an official RFC 3932 decision. But given the two week
  *> review deadlines, events in the WGs, etc. I know I at
  *> least sometimes miss other mails and requests.
  *> 
  *> I wonder if John's goal would be met by the RFC Editor
  *> deciding what order it runs the different steps in. For
  *> instance, if the RFC Editor suspects that a collision
  *> is very likely, sending the draft for RFC 3932 at that
  *> time would seem more useful than spend half a year
  *> in ISR process and only then finding out that, say,
  *> IANA rules prevent publication.

So, I am confused.  "Yes, exactly, that's the problem."  The
RFC Editor receives an independent submission, and a quick
read makes us suspect a conflict.  We send a message to an
(overworked!) AD, asking for a quick opinion, but we hear nothing.

All sugestions to make this work better are welcome.

Bob Braden

  *> 
  *> Jari
  *> 
  *> 
  *> _______________________________________________
  *> INDEPENDENT mailing list
  *> INDEPENDENT@ietf.org
  *> https://www1.ietf.org/mailman/listinfo/independent
  *> 

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 24 06:56:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9gjP-0007x4-6b; Wed, 24 Jan 2007 06:55:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9gjN-0007wr-98
	for independent@ietf.org; Wed, 24 Jan 2007 06:55:57 -0500
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9gjM-0002qM-0e
	for independent@ietf.org; Wed, 24 Jan 2007 06:55:57 -0500
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id E0A71198770;
	Wed, 24 Jan 2007 13:55:52 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id A48F119876E;
	Wed, 24 Jan 2007 13:55:52 +0200 (EET)
Message-ID: <45B7494A.90301@piuha.net>
Date: Wed, 24 Jan 2007 13:55:54 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
Subject: Re: [INDEP] Re: comments on draft-klensin-independent-05.txt
References: <200701232029.MAA21304@gra.isi.edu>
In-Reply-To: <200701232029.MAA21304@gra.isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

Bob,
> We would welcome that cooperation.
>   
Great, I think we can work out something.
> So, I am confused.  "Yes, exactly, that's the problem."  The
> RFC Editor receives an independent submission, and a quick
> read makes us suspect a conflict.  We send a message to an
> (overworked!) AD, asking for a quick opinion, but we hear nothing.
>   
The part about "quick opinion" may be the issue
here. What I suggested was that you send
the _official_ RFC 3932 check request at that time.
These are tracked, visible to all ADs, have a set
deadline when they are handled in the telechat,
etc.

Jari


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 24 12:35:50 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9m1a-0006Wy-J6; Wed, 24 Jan 2007 12:35:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9m1Z-0006Wt-TA
	for independent@ietf.org; Wed, 24 Jan 2007 12:35:05 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9m1Y-00024R-GS
	for independent@ietf.org; Wed, 24 Jan 2007 12:35:05 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l0OHYQEI003838;
	Wed, 24 Jan 2007 09:34:26 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id JAA21675;
	Wed, 24 Jan 2007 09:34:26 -0800 (PST)
Date: Wed, 24 Jan 2007 09:34:26 -0800 (PST)
Message-Id: <200701241734.JAA21675@gra.isi.edu>
To: braden@ISI.EDU, jari.arkko@piuha.net
Subject: Re: [INDEP] Re: comments on draft-klensin-independent-05.txt
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



  *> >   
  *> The part about "quick opinion" may be the issue
  *> here. What I suggested was that you send
  *> the _official_ RFC 3932 check request at that time.
  *> These are tracked, visible to all ADs, have a set
  *> deadline when they are handled in the telechat,
  *> etc.
  *> 
  *> Jari
  *> 

Well, that would be a significant change in procedure, but if it
works for the IESG, I guess it works for us.  But... beware of
getting what you ask for.

Before 3932 was written and the IESG expected to make a serious
judgment of technical contents of independent submissions, we used to
submit them to the IESG for approval first.  Then, the IESG quite
correctly complained that they were sometimes given crappy documents to
read, since the RFC Editor had not yet taken the passes with the author
that we often go through before accepting a document.

So, we revised the procedure, to move the IESG review to the end of the
independent submission editorial review process.  The RFC Editor does
the high-level editorial review, gets detailed technical reviews, e.g
from the Editorial Board, and makes a decision in favor of publishing
BEFORE we bother the IESG with a 3932 review.  Quite a few independent
submissions never get to the IESG, as a result.  If we follow your
suggestion, sending them to the IESG at the beginning, we will be back
at square 1.

Maybe your suggestion is not such a good idea.  Been there...

Bob Braden


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 24 14:20:37 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9nfW-0002fZ-30; Wed, 24 Jan 2007 14:20:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9nfU-0002e0-Mj
	for independent@ietf.org; Wed, 24 Jan 2007 14:20:24 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9nfR-0004Im-EF
	for independent@ietf.org; Wed, 24 Jan 2007 14:20:24 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1H9nfO-0003Nk-P9; Wed, 24 Jan 2007 14:20:19 -0500
Date: Wed, 24 Jan 2007 14:20:17 -0500
From: John C Klensin <john-ietf@jck.com>
To: Bob Braden <braden@ISI.EDU>
Subject: Re: [INDEP] Re: comments on
 draft-klensin-independent-05.txt
Message-ID: <7648F33ED284F219B5F29FB8@p3.JCK.COM>
In-Reply-To: <200701241734.JAA21675@gra.isi.edu>
References: <200701241734.JAA21675@gra.isi.edu>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: independent@ietf.org, jari.arkko@piuha.net
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



--On Wednesday, 24 January, 2007 09:34 -0800 Bob Braden
<braden@ISI.EDU> wrote:

>   *> The part about "quick opinion" may be the issue
>   *> here. What I suggested was that you send
>   *> the _official_ RFC 3932 check request at that time.
>   *> These are tracked, visible to all ADs, have a set
>   *> deadline when they are handled in the telechat,
>   *> etc.
>   *> 
>   *> Jari
> 
> Well, that would be a significant change in procedure, but if
> it works for the IESG, I guess it works for us.  But... beware
> of getting what you ask for.
> 
> Before 3932 was written and the IESG expected to make a serious
> judgment of technical contents of independent submissions, we
> used to submit them to the IESG for approval first.  Then, the
> IESG quite correctly complained that they were sometimes given
> crappy documents to read, since the RFC Editor had not yet
> taken the passes with the author that we often go through
> before accepting a document.
> 
> So, we revised the procedure, to move the IESG review to the
> end of the independent submission editorial review process.
> The RFC Editor does the high-level editorial review, gets
> detailed technical reviews, e.g from the Editorial Board, and
> makes a decision in favor of publishing BEFORE we bother the
> IESG with a 3932 review.  Quite a few independent submissions
> never get to the IESG, as a result.  If we follow your
> suggestion, sending them to the IESG at the beginning, we will
> be back at square 1.
> 
> Maybe your suggestion is not such a good idea.  Been there...

Bob,

Maybe there is a middle ground here.  Maybe.

Even before you were submitting everything to the IESG before
internal review, the rule (which I think is still in 2026, but I
may have lost track of sequencing) was that the RFC Editor would
decide what documents needed to be reviewed by the IESG.  After
a few episodes in which the IESG decided, post-publication, that
they would have preferred to see some documents that they
didn't, things shifted to "everything goes to the IESG".

Perhaps the middle ground would be to combine that original idea
with Jari's suggestion and the current procedure, leaving us
with:

	* When a document comes in, the RFC Editor performs a
	preliminary review and makes a determination as to
	whether it seems likely that the IESG will have strong
	opinions on the document.   
	
	* If "yes", then the document goes to the IESG, both as
	a 3932 review and in the hope of eliciting comments from
	the IESG (or ADs as individuals) that will make the
	review and editing process more efficient.
	
	* If no, then the sequence outlined in the I-D is
	followed, i.e., RFC Editor review and at least some
	editing first, then 3932 review by the IESG.

Or even better, the RFC Editor decides when, in the document
processing cycle, to initiate the RFC 3932 review: before the Ed
Board sees it, in the middle of Ed Board review if someone notes
that there is a relevant active WG that would probably need to
be involved, before or after [semi-]final editing, etc.

That might be more efficient from everyone's standpoint than
requiring either a "early" or "late" IESG review for every case.
And, of course, earlier rejection of documents that aren't going
anywhere free up resources for faster processing and editing of
documents that will be published.

With regard to the "independent" I-D, and noting that I'm
writing as an individual, not as Editor, it seems to me that
this dialog suggests that we should be making the document less
specific, rather than more specific, about steps to be followed
and the order in which they are applied.  The right way to
resolve these issues, IMnvHO, is periodic discussion between the
RFC Editor and the IESG about whether the "what gets sent early"
bar is being set too high or too low and regular recalibration
of that filter.    All we do by overspecifying that sort of
situation is to tie people's hands and prevent good things from
happening smoothly and efficiently.

     john


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 24 14:27:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9nmc-0007am-0e; Wed, 24 Jan 2007 14:27:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9nma-0007ag-Mi
	for independent@ietf.org; Wed, 24 Jan 2007 14:27:44 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9nmZ-0006cs-9Z
	for independent@ietf.org; Wed, 24 Jan 2007 14:27:44 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l0OJQYYB007139;
	Wed, 24 Jan 2007 11:26:34 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id LAA21833;
	Wed, 24 Jan 2007 11:26:34 -0800 (PST)
Date: Wed, 24 Jan 2007 11:26:34 -0800 (PST)
Message-Id: <200701241926.LAA21833@gra.isi.edu>
To: braden@ISI.EDU, john-ietf@jck.com
Subject: Re: [INDEP] Re: comments on
 draft-klensin-independent-05.txt
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: independent@ietf.org, jari.arkko@piuha.net
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



  *> 
  *> Bob,
  *> 
  *> Maybe there is a middle ground here.  Maybe.
  *> 
  *> Even before you were submitting everything to the IESG before
  *> internal review, the rule (which I think is still in 2026, but I
  *> may have lost track of sequencing) was that the RFC Editor would
  *> decide what documents needed to be reviewed by the IESG.  After
  *> a few episodes in which the IESG decided, post-publication, that
  *> they would have preferred to see some documents that they
  *> didn't, things shifted to "everything goes to the IESG".
  *> 
  *> Perhaps the middle ground would be to combine that original idea
  *> with Jari's suggestion and the current procedure, leaving us
  *> with:
  *> 
  *> 	* When a document comes in, the RFC Editor performs a
  *> 	preliminary review and makes a determination as to
  *> 	whether it seems likely that the IESG will have strong
  *> 	opinions on the document.   
  *> 	
  *> 	* If "yes", then the document goes to the IESG, both as
  *> 	a 3932 review and in the hope of eliciting comments from
  *> 	the IESG (or ADs as individuals) that will make the
  *> 	review and editing process more efficient.
  *> 	
  *> 	* If no, then the sequence outlined in the I-D is
  *> 	followed, i.e., RFC Editor review and at least some
  *> 	editing first, then 3932 review by the IESG.
  *> 
  *> Or even better, the RFC Editor decides when, in the document
  *> processing cycle, to initiate the RFC 3932 review: before the Ed
  *> Board sees it, in the middle of Ed Board review if someone notes
  *> that there is a relevant active WG that would probably need to
  *> be involved, before or after [semi-]final editing, etc.
  *> 

This might work; worth some further careful thought.

  *> That might be more efficient from everyone's standpoint than
  *> requiring either a "early" or "late" IESG review for every case.
  *> And, of course, earlier rejection of documents that aren't going
  *> anywhere free up resources for faster processing and editing of
  *> documents that will be published.
  *> 
  *> With regard to the "independent" I-D, and noting that I'm
  *> writing as an individual, not as Editor, it seems to me that
  *> this dialog suggests that we should be making the document less
  *> specific, rather than more specific, about steps to be followed
  *> and the order in which they are applied.  The right way to

Yes, that seems to be the implication.  The doc should there MUST be
a 3932 review, leaving it up to the RFC Editor as to when in the process
it happens.  That seems to cover all cases.

  *> resolve these issues, IMnvHO, is periodic discussion between the
  *> RFC Editor and the IESG about whether the "what gets sent early"
  *> bar is being set too high or too low and regular recalibration
  *> of that filter.    All we do by overspecifying that sort of
  *> situation is to tie people's hands and prevent good things from
  *> happening smoothly and efficiently.
  *> 
  *>      john
  *> 

Sure, we have been fine-tuning this stuff since 1999, and I am
sure we are not done yet!

Bob


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 24 14:37:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9nwO-0004jR-4G; Wed, 24 Jan 2007 14:37:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9nwM-0004jJ-D6
	for independent@ietf.org; Wed, 24 Jan 2007 14:37:50 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9nwL-0000nS-07
	for independent@ietf.org; Wed, 24 Jan 2007 14:37:50 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1H9nwJ-0003XZ-Kb; Wed, 24 Jan 2007 14:37:47 -0500
Date: Wed, 24 Jan 2007 14:37:46 -0500
From: John C Klensin <john-ietf@jck.com>
To: Bob Braden <braden@ISI.EDU>
Subject: Re: [INDEP] Re: comments on
 draft-klensin-independent-05.txt
Message-ID: <F22F99E1F28D234AC2C95F81@p3.JCK.COM>
In-Reply-To: <200701241926.LAA21833@gra.isi.edu>
References: <200701241926.LAA21833@gra.isi.edu>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: independent@ietf.org, jari.arkko@piuha.net
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



--On Wednesday, 24 January, 2007 11:26 -0800 Bob Braden
<braden@ISI.EDU> wrote:

>...
>   *> With regard to the "independent" I-D, and noting that I'm
>   *> writing as an individual, not as Editor, it seems to me
> that   *> this dialog suggests that we should be making the
> document less   *> specific, rather than more specific, about
> steps to be followed   *> and the order in which they are
> applied.  The right way to
> 
> Yes, that seems to be the implication.  The doc should there
> MUST be a 3932 review, leaving it up to the RFC Editor as to
> when in the process it happens.  That seems to cover all cases.

One additional tuning suggestion.   If we are going to move
toward posting a notice that a document has gone into RFC Editor
review as an independent submission somewhere, I think we should
allow the IESG to notify the RFC Editor that _they_ are
initiating that review as well.  If they never take advantage of
it, nothing is lost.  But, again in the interest of efficiency
and flexibility, if an AD happens to notice a document headed
down the "independent" path that seems problematic, in the
spirit of this exchange I don't see any reason to prevent the
IESG from initiating the review if they think that is
appropriate.

     john


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Wed Jan 24 16:21:15 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9pYB-0006LP-KX; Wed, 24 Jan 2007 16:20:59 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H9pCR-0002Zo-PI
	for independent@ietf.org; Wed, 24 Jan 2007 15:58:32 -0500
Received: from boreas.isi.edu ([128.9.160.161])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H9pBy-0001m5-EB
	for independent@ietf.org; Wed, 24 Jan 2007 15:58:30 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l0OKvPCd005819;
	Wed, 24 Jan 2007 12:57:25 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id MAA21916;
	Wed, 24 Jan 2007 12:57:25 -0800 (PST)
Date: Wed, 24 Jan 2007 12:57:25 -0800 (PST)
Message-Id: <200701242057.MAA21916@gra.isi.edu>
To: braden@ISI.EDU, john-ietf@jck.com
Subject: Re: [INDEP] Re: comments on
 draft-klensin-independent-05.txt
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: independent@ietf.org, jari.arkko@piuha.net
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org


  *> 
  *> One additional tuning suggestion.   If we are going to move
  *> toward posting a notice that a document has gone into RFC Editor
  *> review as an independent submission somewhere, I think we should
  *> allow the IESG to notify the RFC Editor that _they_ are
  *> initiating that review as well.  If they never take advantage of
  *> it, nothing is lost.  But, again in the interest of efficiency
  *> and flexibility, if an AD happens to notice a document headed
  *> down the "independent" path that seems problematic, in the
  *> spirit of this exchange I don't see any reason to prevent the
  *> IESG from initiating the review if they think that is
  *> appropriate.
  *> 
  *>      john
  *> 

Not unreasonable, although the program begins to get rather obscure
with locks and signals! ;-)

The information that a given draft is in RFC Editor review as an
independent submission is of course always available in the RFC
Editor quueue, but I suppose there could be a display that shows
the time derivative of the queue.

Boib


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Sat Jan 27 11:15:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAqCN-0000wD-H2; Sat, 27 Jan 2007 11:14:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAqCM-0000w0-9N
	for independent@ietf.org; Sat, 27 Jan 2007 11:14:38 -0500
Received: from mtagate3.de.ibm.com ([195.212.29.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAqCK-0004tv-Op
	for independent@ietf.org; Sat, 27 Jan 2007 11:14:38 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate3.de.ibm.com (8.13.8/8.13.8) with ESMTP id l0RGEYTR148534
	for <independent@ietf.org>; Sat, 27 Jan 2007 16:14:36 GMT
Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com
	[9.149.165.229])
	by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.2) with
	ESMTP id l0RGEXoQ782468
	for <independent@ietf.org>; Sat, 27 Jan 2007 17:14:33 +0100
Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l0RGEXXF017591
	for <independent@ietf.org>; Sat, 27 Jan 2007 17:14:33 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l0RGEX9Y017588; Sat, 27 Jan 2007 17:14:33 +0100
Received: from [9.145.248.71] (sig-9-145-248-71.de.ibm.com [9.145.248.71])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id RAA128332; 
	Sat, 27 Jan 2007 17:14:30 +0100
Message-ID: <45BB7A66.60202@zurich.ibm.com>
Date: Sat, 27 Jan 2007 17:14:30 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
Subject: Re: [INDEP] Re: comments on draft-klensin-independent-05.txt
References: <200701242057.MAA21916@gra.isi.edu>
In-Reply-To: <200701242057.MAA21916@gra.isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: john-ietf@jck.com, independent@ietf.org, jari.arkko@piuha.net
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

I don't think we should overdesign process here. But to be
clear, if a draft shows up at the RFC Editor named something
like draft-AUTHOR-WGNAME-foobar or draft-AUTHOR-PROTOCOLNAME-foobar
then a check on the IETF side before serious ISR review
really seems like common sense. And if experience shows
that private notes to the relevant AD get lost, then we should
use a common sense way of getting it on the IESG's radar.

For IANA, we've recently encouraged them to directly add items
to the IESG agenda when they need our attention. There's no
reason we can't do the same for the RFC Editor, without launching
a premature RFC 3932 review. This doesn't need rules, IMHO.
It's Management 101 stuff.

    Brian

On 2007-01-24 21:57, Bob Braden wrote:
>   *> 
>   *> One additional tuning suggestion.   If we are going to move
>   *> toward posting a notice that a document has gone into RFC Editor
>   *> review as an independent submission somewhere, I think we should
>   *> allow the IESG to notify the RFC Editor that _they_ are
>   *> initiating that review as well.  If they never take advantage of
>   *> it, nothing is lost.  But, again in the interest of efficiency
>   *> and flexibility, if an AD happens to notice a document headed
>   *> down the "independent" path that seems problematic, in the
>   *> spirit of this exchange I don't see any reason to prevent the
>   *> IESG from initiating the review if they think that is
>   *> appropriate.
>   *> 
>   *>      john
>   *> 
> 
> Not unreasonable, although the program begins to get rather obscure
> with locks and signals! ;-)
> 
> The information that a given draft is in RFC Editor review as an
> independent submission is of course always available in the RFC
> Editor quueue, but I suppose there could be a display that shows
> the time derivative of the queue.
> 
> Boib
> 
> 
> _______________________________________________
> INDEPENDENT mailing list
> INDEPENDENT@ietf.org
> https://www1.ietf.org/mailman/listinfo/independent
> 

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Sat Jan 27 11:16:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAqEJ-0001Uy-NF; Sat, 27 Jan 2007 11:16:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAqEH-0001UK-AI
	for independent@ietf.org; Sat, 27 Jan 2007 11:16:38 -0500
Received: from mtagate5.de.ibm.com ([195.212.29.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAqEF-0005Aa-JF
	for independent@ietf.org; Sat, 27 Jan 2007 11:16:37 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate5.de.ibm.com (8.13.8/8.13.8) with ESMTP id l0RGGYYA254770
	for <independent@ietf.org>; Sat, 27 Jan 2007 16:16:34 GMT
Received: from d12av01.megacenter.de.ibm.com (d12av01.megacenter.de.ibm.com
	[9.149.165.212])
	by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.2) with
	ESMTP id l0RGGYOA983190
	for <independent@ietf.org>; Sat, 27 Jan 2007 17:16:34 +0100
Received: from d12av01.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av01.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l0RGGYQi005232
	for <independent@ietf.org>; Sat, 27 Jan 2007 17:16:34 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av01.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l0RGGXrw005227; Sat, 27 Jan 2007 17:16:34 +0100
Received: from [9.145.248.71] (sig-9-145-248-71.de.ibm.com [9.145.248.71])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id RAA367302; 
	Sat, 27 Jan 2007 17:16:32 +0100
Message-ID: <45BB7ADF.2090808@zurich.ibm.com>
Date: Sat, 27 Jan 2007 17:16:31 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [INDEP] Re: comments on draft-klensin-rfc-independent-05
References: <45B614A4.1050200@piuha.net>
	<E52F21E4346EF4F9A78A2BFE@p3.JCK.COM>	<45B63445.40905@zurich.ibm.com>
	<BD762EB61BBF0CC1DEBFCC6F@p3.JCK.COM>
In-Reply-To: <BD762EB61BBF0CC1DEBFCC6F@p3.JCK.COM>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: independent@ietf.org, Jari Arkko <jari.arkko@piuha.net>
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

Let me clarify that I have no objection to the
present text - I was just looking for a way to handle
Jari's comments. Generally, I agree with John's responses.

     Brian

On 2007-01-23 20:33, John C Klensin wrote:
> 
> --On Tuesday, 23 January, 2007 17:13 +0100 Brian E Carpenter
> <brc@zurich.ibm.com> wrote:
> 
>> ...
>>> The net result of this model is that, if a document results
>>> from an IETF process, it is unlikely to be published as an
>>> RFC unless it receives either sponsorship or, at least a
>>> positive review and recommendation, from the IESG _or_ it
>>> represents a critical review of an IETF conclusion or
>>> inability to reach a conclusion.
>> That seems to exclude publication of simply dissenting views.
>> Is that the intention? Personally I am generally in favour
>> of the IETF publishing "road not followed" documents, but we do
>> have various instances of such things not getting published.
>> Should we exclude independent submission as a backstop
>> mechanism?
> 
> Certainly not, at least IMO, but I may have coded a bit too much
> into "critical review".  If the IESG is unwilling to take
> responsibility for publishing a "road not followed" document
> that is connected to IETF outputs or processes, I'm suggesting a
> slightly higher standard for independent submission RFC
> publication.  To vastly oversimplify the problem, suppose that
> the IETF has agreed upon, and published, a standards-track
> document that says "when there is a conflict, the packet that
> arrives on the higher-bandwidth connection should be preferred
> and forwarded".  I believe that is wrong and that the packet
> that arrives on the lower-bandwidth connection should be given
> preference.    Assuming I'd like my views published, I can
> generate two types of documents:
> 
> 	(1) A document that simply parallels the standards-track
> 	one except that it reaches the opposite conclusion.
> 	This is a "dissenting view".    Presumably the IESG asks
> 	the RFC Editor to slap warning labels all over the thing
> 	and maybe even requests non-publication.
> 	
> 	(2) A document that reviews the IETF decision in some
> 	careful and critical way (I know you know this, but, for
> 	the benefit of others, remember "critical" doesn't imply
> 	negative) and that explains why, in the opinion of the
> 	author, the decision may have been the wrong one.
> 
> Now I contend that the first document is historically nearly
> useless: it has no value other than to document the fact that
> there was not complete consensus in the IETF.  The second
> document, however, if it is competent, should be published even
> if it make the IESG unhappy... perhaps _especially_ if it makes
> the IESG unhappy, because the dissenting position is likely to
> be historically useful and possibly even important.
> 
>>>> 3. At the end of Section 2, you explain how the RFC Editor
>>>> and the IESG work together with regards to conflicts with
>>>> the IETF standards process. But this explanation only talks
>>>> about delays and IESG notes, not the possibility of not
>>>> publishing at all which Section 4.8 lists also as a
>>>> possibility. Please update Section 2.
>>> I would encourage some discussion of this subject on-list.
>>> The general assumption underlying the document is that the RFC
>>> Editor and independent submission process is actually
>>> independent.   Under that model of independence and subject
>>> only to constraints the IESG imposes on itself (e.g., with
>>> RFC 3932 and its successors), the IESG can recommend anything
>> ...
> 
>> I didn't read Jari's comment as asking for that. But it does
>> seem
>> fair to stipulate that the RFC Editor is expected to do the
>> right
>> thing in flagrant cases (e.g. documents that infringe explicit
>> IANA considerations). That is, after all, why 3932 was written
>> in the first place.
> 
> IMO, the RFC Editor is _always_ expected to do the right thing.
> It is not clear to me that making a list of specific cases does
> much more than brand the omitted cases as one in which the
> community doesn't care whether the RFC Editor does the right
> thing or not.  To paraphrase a remark Jari made elsewhere in his
> note, we probably do not need more rules and procedures here.
> 
> But, if someone has specific language they would like in the
> document to describe these situations, please propose it and
> I'll happily let the IAB figure out what to do with it :-).
> 
>> ...
> 
>>>> 8. I am somewhat concerned that we're building quite a lot
>>>> of process for the independent submission path. I like the
>>>> transparency, use of reviewers, ability to escalate a problem
>>>> to the IAB, etc, but we should not attempt to build a
>>>> process which is similar to the IETF. In particular, Section
>> ...
>>>> I hope we are not developing an "RFC Editor Last Call"
>>>> procedure where the same community of Internet experts is
>>>> expected to provide feedback to both IETF and independent
>>>> submissions. Yet another mailing list to subscribe for
>>>> everyone; yet more documents to look at in a situation where
>>>> we already get too little LC review per document. I like the
>>>> independent submission process very much, and have a lot of
>>>> trust in the RFC editor and their selected reviewers for
>>>> doing competent publication decisions. But I think one of
>>>> the values of this system is that is indeed run by an
>>>> independent set of people, not calling for the general
>>>> community review in the same manner as IETF does.
>>>> I would suggest deleting the text in question.
> 
>>> Personally, I share your concerns and would be happy to remove
>>> that text.  However, during earlier discussions, there was a
>>> great deal of interest expressed in more transparency, more
>>> community review and input, etc.  There is obviously a
>>> tradeoff in this: if one wants more assurance of transparency
>>> and community review, then it is difficult to avoid more
>>> process and formality.  The community needs to make up its
>>> collective mind.
>> Personal opinion: I want the ISR process to be as transparent
>> as
>> possible. If it's to be a backstop for any untoward behaviour
>> in the IETF process, it needs to be at least as transparent as
>> the
>> IETF process, where we have an increasing tendency towards
>> public reviews (e.g.
>> http://www.alvestrand.no/ietf/gen/art/gen-art.html).
>> But I don't think we need rules here so much as an agreed
>> principle
>> of openness, and practical steps to implement it, such as
>> public email archives whenever possible.
> 
> That difference of opinion is why the text is the way it is,
> more or less.  As I tried to say, there is a tension among
> reasonable objectives.
> 
>      john
> 
> 
> _______________________________________________
> INDEPENDENT mailing list
> INDEPENDENT@ietf.org
> https://www1.ietf.org/mailman/listinfo/independent
> 

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Sat Jan 27 11:27:53 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAqP2-0007c0-3e; Sat, 27 Jan 2007 11:27:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAqP0-0007bs-Qv
	for independent@ietf.org; Sat, 27 Jan 2007 11:27:42 -0500
Received: from mtagate4.de.ibm.com ([195.212.29.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAqOy-00081I-A3
	for independent@ietf.org; Sat, 27 Jan 2007 11:27:42 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate4.de.ibm.com (8.13.8/8.13.8) with ESMTP id l0RGRbPi038278
	for <independent@ietf.org>; Sat, 27 Jan 2007 16:27:37 GMT
Received: from d12av01.megacenter.de.ibm.com (d12av01.megacenter.de.ibm.com
	[9.149.165.212])
	by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.2) with
	ESMTP id l0RGRbro811058
	for <independent@ietf.org>; Sat, 27 Jan 2007 17:27:37 +0100
Received: from d12av01.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av01.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l0RGRbPX009294
	for <independent@ietf.org>; Sat, 27 Jan 2007 17:27:37 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av01.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l0RGRaxK009287; Sat, 27 Jan 2007 17:27:36 +0100
Received: from [9.145.248.71] (sig-9-145-248-71.de.ibm.com [9.145.248.71])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id RAA245852; 
	Sat, 27 Jan 2007 17:27:34 +0100
Message-ID: <45BB7D75.3090600@zurich.ibm.com>
Date: Sat, 27 Jan 2007 17:27:33 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Craig Partridge <craig@aland.bbn.com>
Subject: Re: [INDEP] Re: comments on draft-klensin-rfc-independent-05
References: <20070123171050.3E28764@aland.bbn.com>
In-Reply-To: <20070123171050.3E28764@aland.bbn.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: John C Klensin <john-ietf@jck.com>, independent@ietf.org
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

On 2007-01-23 18:10, Craig Partridge wrote:
> In message <45B63445.40905@zurich.ibm.com>, Brian E Carpenter writes:
> 
>> On 2007-01-23 16:04, John C Klensin wrote:
>> ...
>>> --On Tuesday, 23 January, 2007 15:59 +0200 Jari Arkko
>>> <jari.arkko@piuha.net> wrote:
>>>
>> <snip>
>>
>>> 	
>>> The net result of this model is that, if a document results from
>>> an IETF process, it is unlikely to be published as an RFC unless
>>> it receives either sponsorship or, at least a positive review
>>> and recommendation, from the IESG _or_ it represents a critical
>>> review of an IETF conclusion or inability to reach a conclusion.
>> That seems to exclude publication of simply dissenting views.
>> Is that the intention? Personally I am generally in favour
>> of the IETF publishing "road not followed" documents, but we do
>> have various instances of such things not getting published.
>> Should we exclude independent submission as a backstop mechanism?
> 
> Since the IESG was created, the issue of coordinating the RFC Editor's
> decisions with the IESG has been something of a third rail.

I believe, from personal observations, that formalizing the
procedure via RFC 3932 has actually removed most of the third
rail effect. (I recognize that some people don't like the
boilerplate notes as they appear in 3932, but that is relatively
speaking a detail.)

>  And
> labeling the independent RFC series as a place to document "road
> not followed" (or more vigorously dissenting opinions) in defiance of
> the IESG seems an invitation to institutional conflict.
> 
> I agree this creates a challenge, namely, that one can present a road
> not followed provided it never appears in a WG, but actually participating
> in a WG may cause the idea to be unpublishable as an RFC (assuming
> a sufficiently unreasonable AD -- I assume a reasonable AD is happy to
> allow such publications).  But on balance, the current plan seems the
> better of two evils.  Here's my logic.
> 
>     If the RFC Editor gets to publish road not followed documents
>     over IESG objections, we have institutional clashes if either
>     the RFC Editor is unreasonable or an AD is unreasonable.
> 
>     If the IESG gets to determine if road not followed documents
>     are published, then the only clash is unreasonable AD with
>     authors.

But look at the appeal paths in both cases. A clash within
the IETF may end up with the IAB. A clash with the RFC Editor
may end up with an IAB review. So I'm not sure that there is that
much practical difference (once people start being unreasonable).

However, this isn't a showstopper issue for me. I'd rather
get this done soon, and trust people to be reasonable.

    Brian

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Sat Jan 27 12:37:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HArTk-0000r9-2U; Sat, 27 Jan 2007 12:36:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HArTi-0000r4-Ba
	for independent@ietf.org; Sat, 27 Jan 2007 12:36:38 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HArTg-0006k7-RB
	for independent@ietf.org; Sat, 27 Jan 2007 12:36:38 -0500
Received: from [127.0.0.1] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1HArTe-0006D0-9f; Sat, 27 Jan 2007 12:36:34 -0500
Date: Sat, 27 Jan 2007 12:36:33 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brc@zurich.ibm.com>, Bob Braden <braden@ISI.EDU>
Subject: Re: [INDEP] Re: comments on
 draft-klensin-independent-05.txt
Message-ID: <A10C38873A18D895BDDDDEA4@p3.JCK.COM>
In-Reply-To: <45BB7A66.60202@zurich.ibm.com>
References: <200701242057.MAA21916@gra.isi.edu> <45BB7A66.60202@zurich.ibm.com>
X-Mailer: Mulberry/4.0.7 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: independent@ietf.org, jari.arkko@piuha.net
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



--On Saturday, 27 January, 2007 17:14 +0100 Brian E Carpenter
<brc@zurich.ibm.com> wrote:

> I don't think we should overdesign process here. But to be
> clear, if a draft shows up at the RFC Editor named something
> like draft-AUTHOR-WGNAME-foobar or
> draft-AUTHOR-PROTOCOLNAME-foobar
> then a check on the IETF side before serious ISR review
> really seems like common sense. And if experience shows
> that private notes to the relevant AD get lost, then we should
> use a common sense way of getting it on the IESG's radar.
> 
> For IANA, we've recently encouraged them to directly add items
> to the IESG agenda when they need our attention. There's no
> reason we can't do the same for the RFC Editor, without
> launching
> a premature RFC 3932 review. This doesn't need rules, IMHO.
> It's Management 101 stuff.

Ok.  Let me make a suggestion as participant, not editor.  If we
can agree on the outline of the principle, we can then try to
get the text right.   I think this discussion suggests that we
do two things:

(1) We modify the "steps" in the documented review process to
remove the formal IESG review (aka the RFC 3932 review) from the
sequence.  We leave the requirement for that review there, but
place the point at which it is requested at the discretion of
the RFC Editor on a document by document basis.  If it seems
necessary to anyone, we also add very general language that
guides the RFC Editor to request that review at a time that
seems optimal from the standpoint of conserving both IESG and
RFC Editor time and noting that the initiation of an RFC 3932
review does not _require_ that work on the document stop until
the IESG responds.

(2) We encourage the IESG and the RFC Editor to develop
less-formal arrangements, on an ongoing basis, that are intended
to make things go more smoothly and efficiently.    I would
think that such arrangements might include:

	* provisions for the IESG to tell the RFC Editor "this
	doesn't look to us like the right time to do a 3932
	review on this document for the following reasons, would
	you be willing to ask again later"
	
	* arrangements, such as the one Brian's note implies,
	for the RFC Editor to ask the IESG for preliminary
	comments on draft-AUTHOR-WGNAME-foobar or
	draft-AUTHOR-PROTOCOLNAME-foobar documents (or things
	that look like them no matter how they are named).  I
	would assume that the IESG could respond to such a
	request with "we want to take this over", "please
	initiate the 3932 review right now", "no obvious
	problems, proceed as normal", or any amount of informal
	free advice or background.

	* ways for the RFC Editor to put something on the IESG
	agenda, as Brian suggests, whether it is related to a
	specific document or some more general principle.

There are probably others.  In my personal opinion, it would be
stupid to try to write the things in the second category down. I
would hope the "independent" document (and the IAB RFC Editor
document, etc.) don't even need to say that informal
communications and arrangements are possible and encouraged.
But, if that much needs to be said, let's say it and move on.

As I have said many times in the year these discussions have
been going on, I think we all succeed to the degree that the RFC
process can be seen as a collaboration and partnership between
the RFC Editor and the various parties in the IAB/ IESG/ IAOC/
and general IETF groupings.   If we can do that, and everyone
behaves reasonably at least most of the time and assumes
everyone else will to, then we can sort most of the details out
on an ongoing basis without needing a lot of specific procedural
rules.  If we cannot, but instead have to get into battles about
who can give directions to whom, specific procedural rules
aren't going to save us from the fate we will probably deserve.

      john


_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Sat Jan 27 15:21:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HAu3I-0007oM-3v; Sat, 27 Jan 2007 15:21:32 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HAu3G-0007oH-V6
	for independent@ietf.org; Sat, 27 Jan 2007 15:21:31 -0500
Received: from mtagate7.uk.ibm.com ([195.212.29.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HAu3F-0004eT-DA
	for independent@ietf.org; Sat, 27 Jan 2007 15:21:30 -0500
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate7.uk.ibm.com (8.13.8/8.13.8) with ESMTP id l0RKKRW0082204
	for <independent@ietf.org>; Sat, 27 Jan 2007 20:20:27 GMT
Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com
	[9.149.37.216])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v8.2) with
	ESMTP id l0RKKRPe250038
	for <independent@ietf.org>; Sat, 27 Jan 2007 20:20:27 GMT
Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av04.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id l0RKKQ9P013612
	for <independent@ietf.org>; Sat, 27 Jan 2007 20:20:27 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d06av04.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id l0RKKQlS013604; Sat, 27 Jan 2007 20:20:26 GMT
Received: from [9.146.222.219] (sig-9-146-222-219.de.ibm.com [9.146.222.219])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id
	VAA367924; Sat, 27 Jan 2007 21:20:23 +0100
Message-ID: <45BBB409.3030703@zurich.ibm.com>
Date: Sat, 27 Jan 2007 21:20:25 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [INDEP] Re: comments on draft-klensin-independent-05.txt
References: <200701242057.MAA21916@gra.isi.edu> <45BB7A66.60202@zurich.ibm.com>
	<A10C38873A18D895BDDDDEA4@p3.JCK.COM>
In-Reply-To: <A10C38873A18D895BDDDDEA4@p3.JCK.COM>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: independent@ietf.org, Bob Braden <braden@ISI.EDU>, jari.arkko@piuha.net
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

Violent agreement.

    Brian

On 2007-01-27 18:36, John C Klensin wrote:
> 
> --On Saturday, 27 January, 2007 17:14 +0100 Brian E Carpenter
> <brc@zurich.ibm.com> wrote:
> 
>> I don't think we should overdesign process here. But to be
>> clear, if a draft shows up at the RFC Editor named something
>> like draft-AUTHOR-WGNAME-foobar or
>> draft-AUTHOR-PROTOCOLNAME-foobar
>> then a check on the IETF side before serious ISR review
>> really seems like common sense. And if experience shows
>> that private notes to the relevant AD get lost, then we should
>> use a common sense way of getting it on the IESG's radar.
>>
>> For IANA, we've recently encouraged them to directly add items
>> to the IESG agenda when they need our attention. There's no
>> reason we can't do the same for the RFC Editor, without
>> launching
>> a premature RFC 3932 review. This doesn't need rules, IMHO.
>> It's Management 101 stuff.
> 
> Ok.  Let me make a suggestion as participant, not editor.  If we
> can agree on the outline of the principle, we can then try to
> get the text right.   I think this discussion suggests that we
> do two things:
> 
> (1) We modify the "steps" in the documented review process to
> remove the formal IESG review (aka the RFC 3932 review) from the
> sequence.  We leave the requirement for that review there, but
> place the point at which it is requested at the discretion of
> the RFC Editor on a document by document basis.  If it seems
> necessary to anyone, we also add very general language that
> guides the RFC Editor to request that review at a time that
> seems optimal from the standpoint of conserving both IESG and
> RFC Editor time and noting that the initiation of an RFC 3932
> review does not _require_ that work on the document stop until
> the IESG responds.
> 
> (2) We encourage the IESG and the RFC Editor to develop
> less-formal arrangements, on an ongoing basis, that are intended
> to make things go more smoothly and efficiently.    I would
> think that such arrangements might include:
> 
> 	* provisions for the IESG to tell the RFC Editor "this
> 	doesn't look to us like the right time to do a 3932
> 	review on this document for the following reasons, would
> 	you be willing to ask again later"
> 	
> 	* arrangements, such as the one Brian's note implies,
> 	for the RFC Editor to ask the IESG for preliminary
> 	comments on draft-AUTHOR-WGNAME-foobar or
> 	draft-AUTHOR-PROTOCOLNAME-foobar documents (or things
> 	that look like them no matter how they are named).  I
> 	would assume that the IESG could respond to such a
> 	request with "we want to take this over", "please
> 	initiate the 3932 review right now", "no obvious
> 	problems, proceed as normal", or any amount of informal
> 	free advice or background.
> 
> 	* ways for the RFC Editor to put something on the IESG
> 	agenda, as Brian suggests, whether it is related to a
> 	specific document or some more general principle.
> 
> There are probably others.  In my personal opinion, it would be
> stupid to try to write the things in the second category down. I
> would hope the "independent" document (and the IAB RFC Editor
> document, etc.) don't even need to say that informal
> communications and arrangements are possible and encouraged.
> But, if that much needs to be said, let's say it and move on.
> 
> As I have said many times in the year these discussions have
> been going on, I think we all succeed to the degree that the RFC
> process can be seen as a collaboration and partnership between
> the RFC Editor and the various parties in the IAB/ IESG/ IAOC/
> and general IETF groupings.   If we can do that, and everyone
> behaves reasonably at least most of the time and assumes
> everyone else will to, then we can sort most of the details out
> on an ongoing basis without needing a lot of specific procedural
> rules.  If we cannot, but instead have to get into battles about
> who can give directions to whom, specific procedural rules
> aren't going to save us from the fate we will probably deserve.
> 
>       john
> 

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Sun Jan 28 16:24:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBHUC-0003A2-EA; Sun, 28 Jan 2007 16:22:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBHUC-00039x-47
	for independent@ietf.org; Sun, 28 Jan 2007 16:22:52 -0500
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]
	helo=carter-zimmerman.mit.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBHU8-0002PE-Rr
	for independent@ietf.org; Sun, 28 Jan 2007 16:22:52 -0500
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
	id AA4BBE00B3; Sun, 28 Jan 2007 16:22:34 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: independent@ietf.org
Date: Sun, 28 Jan 2007 16:22:34 -0500
Message-ID: <tslr6teonhh.fsf@cz.mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [INDEP] Last call comments
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org



In general, it seems like the independent submissions draft represents
a careful balance between a lot of issues that we've been trying to
wrap our minds around.  I think it does a good job and should be
published.

There is one area that seems to be missing: the interactions between
the independent stream and IANA.  Can an independent submission
establish an IANA registry?  How are expert reviews for IANA
allocation handled?  What happens if an expert declines a necessary
codepoint?  Presumably the same thing happens if IETF consensus is
required for something that an independent submission tries to
allocate.

I don't think this is a critical flaw; I think the document would be
improved by discussing these issues, but I think we can get along
without this discussion.  One area where I do think advice would be
very useful to authors is in how to take a document that was a
protocol spec and thus requires IANA allocations and to turn it into
something that is simply a description of potential extensions to a
protocol without IANA allocations.  I think that's the only way to
easily publish an alternative to an IETF proposal requiring IANA
allocations over the IETF's objection.  Perhaps this is the wrong
document for that advice but it would be useful never the less.

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



From independent-bounces@ietf.org Mon Jan 29 12:28:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBaIl-00007I-FP; Mon, 29 Jan 2007 12:28:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBaIj-000071-B0
	for independent@ietf.org; Mon, 29 Jan 2007 12:28:17 -0500
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBaIh-00034E-TU
	for independent@ietf.org; Mon, 29 Jan 2007 12:28:17 -0500
Received: from [10.20.30.108] (dsl-63-249-108-169.cruzio.com [63.249.108.169])
	(authenticated bits=0)
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l0THSDbr078708
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 29 Jan 2007 10:28:14 -0700 (MST)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240807c1e3de22676c@[10.20.30.108]>
In-Reply-To: <tslr6teonhh.fsf@cz.mit.edu>
References: <tslr6teonhh.fsf@cz.mit.edu>
Date: Mon, 29 Jan 2007 09:27:56 -0800
To: Sam Hartman <hartmans-ietf@mit.edu>, independent@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [INDEP] Last call comments
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: 
X-BeenThere: independent@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@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/independent>
List-Post: <mailto:independent@ietf.org>
List-Help: <mailto:independent-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/independent>,
	<mailto:independent-request@ietf.org?subject=subscribe>
Errors-To: independent-bounces@ietf.org

At 4:22 PM -0500 1/28/07, Sam Hartman wrote:
>In general, it seems like the independent submissions draft represents
>a careful balance between a lot of issues that we've been trying to
>wrap our minds around.  I think it does a good job and should be
>published.
>
>There is one area that seems to be missing: the interactions between
>the independent stream and IANA.  Can an independent submission
>establish an IANA registry?  How are expert reviews for IANA
>allocation handled?  What happens if an expert declines a necessary
>codepoint?  Presumably the same thing happens if IETF consensus is
>required for something that an independent submission tries to
>allocate.
>
>I don't think this is a critical flaw; I think the document would be
>improved by discussing these issues, but I think we can get along
>without this discussion.  One area where I do think advice would be
>very useful to authors is in how to take a document that was a
>protocol spec and thus requires IANA allocations and to turn it into
>something that is simply a description of potential extensions to a
>protocol without IANA allocations.  I think that's the only way to
>easily publish an alternative to an IETF proposal requiring IANA
>allocations over the IETF's objection.  Perhaps this is the wrong
>document for that advice but it would be useful never the less.

Sam's concerns should indeed be addressed in this document. 
Formalizing how the IANA deals with the IESG on new registries and 
changes to existing registries has caused a significant reduction in 
the number of muffed IANA registries. Independent submission RFCs 
making additions to IANA registries whose elements are "RFC required" 
are important to the IETF.

--Paul Hoffman, Director
--VPN Consortium

_______________________________________________
INDEPENDENT mailing list
INDEPENDENT@ietf.org
https://www1.ietf.org/mailman/listinfo/independent



