Re: individual submission Last Call -- default yes/no.

"Tom Petch" <nwnetworks@dial.pipex.com> Fri, 07 January 2005 18:18 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03014; Fri, 7 Jan 2005 13:18:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cmytl-0004Ge-N8; Fri, 07 Jan 2005 13:31:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CmyeP-0000Ai-JD; Fri, 07 Jan 2005 13:15:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CmyaI-0007OT-BK for ietf@megatron.ietf.org; Fri, 07 Jan 2005 13:11:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02667 for <ietf@ietf.org>; Fri, 7 Jan 2005 13:11:34 -0500 (EST)
Received: from astro.systems.pipex.net ([62.241.163.6]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmynG-0003dZ-DP for ietf@ietf.org; Fri, 07 Jan 2005 13:25:05 -0500
Received: from pc6 (1Cust42.tnt3.lnd4.gbr.da.uu.net [62.188.132.42]) by astro.systems.pipex.net (Postfix) with SMTP id C3A53E0000F0; Fri, 7 Jan 2005 18:10:59 +0000 (GMT)
Message-ID: <065e01c4f4db$b2313140$0601a8c0@pc6>
From: Tom Petch <nwnetworks@dial.pipex.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
References: <200516104826.996163@bbprime> <ED5B83D1964A42A623818CE1@B50854F0A9192E8EC6CDA126>
Date: Fri, 07 Jan 2005 18:07:13 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Subject: Re: individual submission Last Call -- default yes/no.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

Looking at the recent announcements of I-Ds, I think we will get a
substantial number of URI/URL related drafts in the coming months which
will also test this procedure.  Their revision numbers are clocking up
so they are being discussed but not AFAICS on any IETF-related list. And
these seem to be standards track.

I am in the 'default no' camp.

Tom Petch

----- Original Message -----
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: "Dave Crocker" <dcrocker@bbiw.net>; <ietf@ietf.org>
Sent: Friday, January 07, 2005 10:46 AM
Subject: Re: individual submission Last Call -- default yes/no.


[note - this note does NOT talk about the language tags document]
Recent standards-track/BCP RFCs that came in as individual submisssions
(you can tell this from the draft name in the rfc-editor.xml file):

RFC 3936 - draft-kompella-rsvp-change
RFC 3935 - draft-alvestrand-ietf-mission
RFC 3934 - draft-wasserman-rfc2418-ml-update
RFC 3915 - draft-hollenbeck-epp-rgp
RFC 3912 - draft-daigle-rfc954bis

Apart from draft-alvestrand, I don't remember any of these causing much
of
a stir at Last Call. Still, I think the decision to advance them was
appropriate.
The usual case for an individual submission is, I think:

- there are a number of people who see a need for it
- there are a (usually far lower) number of people who are willing to
work
on it
- someone thinks that this isn't controversial enough for a WG, isn't
work
enough that the extra effort of setting up a WG is worth it, is too
urgently needed to wait for a WG to get up to speed, or other version of
"doesn't fit with our WG process
- nobody's significantly opposed to getting the work done

A "default no" doesn't seem like a correct procedure here.

              Harald

.ietf.org/mailman/listinfo/ietf


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