Re: Issues around sponsoring individual documents

Lars Eggert <lars.eggert@nokia.com> Mon, 10 September 2007 11:05 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 1IUh55-0008Cd-82; Mon, 10 Sep 2007 07:05:27 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IUh53-00085W-Ax for discuss-confirm+ok@megatron.ietf.org; Mon, 10 Sep 2007 07:05:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUh52-00084l-NC for discuss@apps.ietf.org; Mon, 10 Sep 2007 07:05:25 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IUh51-0000hd-8A for discuss@apps.ietf.org; Mon, 10 Sep 2007 07:05:24 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l8AB5G2O000751; Mon, 10 Sep 2007 14:05:16 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10 Sep 2007 14:05:05 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10 Sep 2007 14:05:04 +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 l8AB4qdJ002898; Mon, 10 Sep 2007 14:04:54 +0300
In-Reply-To: <46E417BF.9050707@dcrocker.net>
References: <76D1FAA9-6605-4D54-9DCC-068BC8242420@commerce.net> <029c01c7f158$a61a3560$0601a8c0@pc6> <6.0.0.20.2.20070908104757.0783acd0@localhost> <46E417BF.9050707@dcrocker.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/signed; micalg="sha1"; boundary="Apple-Mail-41-661690838"; protocol="application/pkcs7-signature"
Message-Id: <6C8ADE70-5028-4876-9AA7-6E3DB297481B@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: Issues around sponsoring individual documents
Date: Mon, 10 Sep 2007 14:04:48 +0300
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 10 Sep 2007 11:05:04.0680 (UTC) FILETIME=[70D3F280:01C7F39A]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: Apps Discuss <discuss@apps.ietf.org>, Lisa Dusseault <ldusseault@commerce.net>
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

On 2007-9-9, at 18:56, ext Dave Crocker wrote:
> Martin Duerst wrote:
>> As for the Atom-related drafts that James was working on,
>> I think that's one situation where I could understand if the AD
>> just told the author and the WG: Please make this a WG draft.
>
> It is common for "related" drafts to be outside the scope of the wg  
> charter. The AD cannot simply instruct the wg to go beyond that  
> scope.  So it is not uncommon for an informal wg task to be pursued  
> formally as an individual submission.

The AD actually can, if the WG is interested, because the charter is  
negotiated between the AD and the WG, followed by an IESG approval.

(If the WG - i.e., the expert community around a protocol - is not  
interested in a document, that should indicate that further questions  
may need to be asked about it before it should become an IS.)

>> Creating a WG is a huge overhead, but having a WG being
>> formally responsible for a draft that they discuss anyway
>> isn't too much overhead. Just an idea.
>
> Given the need to modify the charter, it actually is very high  
> overhead.

Not really. Minor recharterings to add well-defined work items aren't  
complicated.

Lars