Re: The purpose of a Last Call

Leslie Daigle <leslie@thinkingcat.com> Fri, 07 November 2008 21:39 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC4F73A6BB9; Fri, 7 Nov 2008 13:39:23 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EADC3A6BB5 for <ietf@core3.amsl.com>; Fri, 7 Nov 2008 13:39:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSHrMx2gIhB4 for <ietf@core3.amsl.com>; Fri, 7 Nov 2008 13:39:21 -0800 (PST)
Received: from zeke.ecotroph.net (zeke.ecotroph.net [70.164.19.155]) by core3.amsl.com (Postfix) with ESMTP id 60BF03A6B96 for <ietf@ietf.org>; Fri, 7 Nov 2008 13:39:21 -0800 (PST)
Received: from beethoven.local ([::ffff:209.183.196.229]) (AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Fri, 07 Nov 2008 16:39:15 -0500 id 0158838E.4914B583.00004369
Message-ID: <4914B57B.2000301@thinkingcat.com>
Date: Fri, 07 Nov 2008 16:39:07 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: The purpose of a Last Call
References: <20081107111744.GA31018@nic.fr> <20081107141821.79303.qmail@simone.iecc.com> <20081107145257.GA28398@nic.fr> <4914655E.40701@dcrocker.net> <tsl3ai3cvho.fsf@mit.edu> <49147D28.9050900@bbiw.net> <p06250114c53a48e8f406@[75.145.176.242]>
In-Reply-To: <p06250114c53a48e8f406@[75.145.176.242]>
Cc: Sam Hartman <hartmans-ietf@mit.edu>, Dave CROCKER <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

+1

If it's going to be an IETF Standard, it has to have IETF consensus.

This seems consistent with the way individual (i.e., non-WG) submissions 
are handled through the IESG.

Leslie.


Pete Resnick wrote:
> On 11/7/08 at 9:38 AM -0800, Dave CROCKER wrote:
> 
>> Sam Hartman wrote:
>>> It seems quite clear to me that RFC 2418 does not apply at all to the 
>>> output of an RG.
>>
>> I've looked around and the WG Guidelines doc happens to be the only 
>> place I could find that defines the purpose of a Last Call. The mere 
>> fact that the title of document is about "working" groups doesn't 
>> obviously limit the scope of that definition.
>>
>> Please explain.  Perhaps there is documentation for the individual and 
>> RG avenues that I missed?
> 
> http://tools.ietf.org/rfc/rfc4844.txt
> http://tools.ietf.org/id/draft-irtf-rfcs-03.txt
> 
> We have (IMO) historically screwed up with regard to IRTF and individual 
> documents and not given them a proper stream to the RFC Editor. The 
> above documents are dealing with that problem.
> 
> However, for this particular case, I'm with Sam: An IRTF document that 
> is going into the *IETF* standards track is pretty much akin to an any 
> other organizations documents going into the IETF standards track. It 
> may be the case that the IETF and IRTF have a lot more sharing of 
> resources and visibility, than say the IETF and ITU or IEEE, and 
> therefore the hand-off should be quite a bit easier. However, there is 
> no doubt that this is *different* than a WG handing off a document to 
> the IESG for standards track approval. A WG has (ostensibly) been 
> subject to the direct observation of an AD all along and therefore the 
> IESG should have a pretty full understanding of the IETF-wide consensus 
> that has built up around any document coming out of that WG by the time 
> the Last Call comes around. That's not going to be the case for an IRTF 
> (or individual or other external organization) document.
> 
> Yes, this is a less-than-efficient use of IETF Last Call. But if you 
> want to make efficient use of the process for an *IETF* standards track 
> document, work on it in the IETF.
> 
> pr

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf