IETF Logo Mail Archive

Re: The purpose of a Last Call

Sam Hartman <hartmans-ietf@mit.edu> Fri, 07 November 2008 20:14 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 9581128C0EB; Fri, 7 Nov 2008 12:14:15 -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 67EBC3A6B7D for <ietf@core3.amsl.com>; Fri, 7 Nov 2008 12:14:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.214
X-Spam-Level:
X-Spam-Status: No, score=-2.214 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 l60RtQoWfSRt for <ietf@core3.amsl.com>; Fri, 7 Nov 2008 12:14:13 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) by core3.amsl.com (Postfix) with ESMTP id AFDEB3A69A4 for <ietf@ietf.org>; Fri, 7 Nov 2008 12:14:13 -0800 (PST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id A9AC1CC006; Fri, 7 Nov 2008 15:14:01 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
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]>
Date: Fri, 07 Nov 2008 15:14:01 -0500
In-Reply-To: <p06250114c53a48e8f406@[75.145.176.242]> (Pete Resnick's message of "Fri, 7 Nov 2008 14:03:30 -0600")
Message-ID: <tslk5bfb8fq.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Cc: 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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>>>>> "Pete" == Pete Resnick <presnick@qualcomm.com> writes:

    Pete> http://tools.ietf.org/rfc/rfc4844.txt
    Pete> http://tools.ietf.org/id/draft-irtf-rfcs-03.txt

    Pete> We have (IMO) historically screwed up with regard to IRTF
    Pete> and individual documents and not given them a proper stream
    Pete> to the RFC Editor. The above documents are dealing with that
    Pete> problem.

As far as I can tell we're in agreement.  Implicit in my comment was
that this document was being published through the IETF stream.  (I'll
leave as an excersise for the pedants what happens if the IRTF tries
to publish an informational document for the IETF stream.)

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email