Re: Issues around sponsoring individual documents

Lars Eggert <lars.eggert@nokia.com> Mon, 10 September 2007 11:17 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUhHB-0002bS-Pe; Mon, 10 Sep 2007 07:17:57 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IUhHA-0002b5-Vw for discuss-confirm+ok@megatron.ietf.org; Mon, 10 Sep 2007 07:17:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUhHA-0002ag-MA for discuss@apps.ietf.org; Mon, 10 Sep 2007 07:17:56 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IUhH9-0000wO-7A for discuss@apps.ietf.org; Mon, 10 Sep 2007 07:17:56 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l8ABHSmj007881; Mon, 10 Sep 2007 14:17:53 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10 Sep 2007 14:17:40 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10 Sep 2007 14:17:39 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10 Sep 2007 14:17:38 +0300
Received: from [172.21.35.195] (esdhcp035195.research.nokia.com [172.21.35.195]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l8ABHX0X014300; Mon, 10 Sep 2007 14:17:33 +0300
In-Reply-To: <76D1FAA9-6605-4D54-9DCC-068BC8242420@commerce.net>
References: <76D1FAA9-6605-4D54-9DCC-068BC8242420@commerce.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/signed; micalg="sha1"; boundary="Apple-Mail-42-662451505"; protocol="application/pkcs7-signature"
Message-Id: <549EFD98-2A83-4E57-994C-E52A40729152@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: Issues around sponsoring individual documents
Date: Mon, 10 Sep 2007 14:17:28 +0300
To: ext Lisa Dusseault <ldusseault@commerce.net>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 10 Sep 2007 11:17:39.0025 (UTC) FILETIME=[3273DC10:01C7F39C]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: Apps Discuss <discuss@apps.ietf.org>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Hi,

you've gotten a lot of good feedback already. My viewpoint differs a  
bit, in that I'm more hesitant about the widespread use of the IS  
path. An IS should be a rare exception, with the much more well- 
defined and -tested WG process the rule.

Because people see the IS path as a shortcut - and even worse, an  
"insider" shortcut -  the more you let them take it, the more  
requests you will get in the future. It starts to erode the process.  
Just say no. Or, actually, ask yourself if the gain from pushing  
something through as an IS is worth the pain in terms of extra  
management and maybe future work. If the gain is worth it *to you*  
(don't forget the IS path is at your discretion, and your judgement  
decides) then sure, go ahead.

But in general, I'd encourage you to tell people to publish their  
documents through the appropriate working group, and if there isn't  
one, tell them to prepare a BOF. WGs have existed to only work on one  
or two documents (PMTUD, for example). WGs come with chairs and they  
come with an established management process, both of which reduce  
your workload (even more so with PROTO).

Lars

PS: Another alternative to IS is something like TSVWG (and now  
OPSAWG) to work in a more open fashion on documents and topics that  
maybe don't warrant their own WG.