Re: Knowing what BOFs are being thought about [was: Re: IETF 65 BOF Announcement: Digital Identity Exchange (DIX)]
Dave Crocker <dhc2@dcrocker.net> Fri, 10 February 2006 20:27 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7ery-0006e2-Gt; Fri, 10 Feb 2006 15:27:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7erv-0006bB-6d for ietf@megatron.ietf.org; Fri, 10 Feb 2006 15:27:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25483 for <ietf@ietf.org>; Fri, 10 Feb 2006 15:26:08 -0500 (EST)
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7f4v-00077I-8y for ietf@ietf.org; Fri, 10 Feb 2006 15:41:21 -0500
Received: from [192.168.0.2] (adsl-71-131-19-20.dsl.sntc01.pacbell.net [71.131.19.20]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k1AKS3JP007374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Feb 2006 12:28:04 -0800
Message-ID: <43ECF72C.6070704@dcrocker.net>
Date: Fri, 10 Feb 2006 12:27:24 -0800
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 1.5 (Windows/20051025)
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>
References: <courier.43ECB50B.00002ACA@zeke.ecotroph.net> <43ECE35E.8070600@dial.pipex.com>
In-Reply-To: <43ECE35E.8070600@dial.pipex.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Found to be clean
X-Songbird-From: dhc2@dcrocker.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Knowing what BOFs are being thought about [was: Re: IETF 65 BOF Announcement: Digital Identity Exchange (DIX)]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dcrocker@bbiw.net
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
Elwyn Davies wrote: > Finding out what BOFs are being plotted is not very easy AFAIK. In the > case below there doesn't appear to have been any widespread public > announcement of the start of the mailing list and I suspect that is the > case for many others. > > Obviously an announcement of intent to the IETF list or the Announce > list is one way for people to tell the world. Indeed. The current model for BOFs tends to view the first one as a free shot. No history required. Given how poorly such first meetings tend to go, I am at a loss to understand why this model persists. Remember that a BOF is for gauging community interest in the working group. That simply is not possible when the topic has no meaningful IETF online history. I am in the camp that believes that IETF meeting time is extremely valuable and that the IETF is still predicated on email list discussion as its primary venue(s). As such -- particularly a BOF targeting working group formation -- we should require that a pre-wg BOF be required to have: a) formed an online discussion, some months ahead of any possible BOF b) its formation announced on ietf-announce b) put forward a sample charter on that discussion list c) conducted discussion of that charter, prior to the BOF. That way, there is a basis for recruiting informed participation, as well as gauging a degree of community interest. d/ ps. I suggest that the DIX BOF is a particularly good candidate for going poorly. Online identity has a history for which a description of "problematic" would be a vast understatement. Even better, the IETF's track record in the arena of digitizing human constructs is, well, limited. -- Dave Crocker Brandenburg InternetWorking <http://bbiw.net> _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- IETF 65 BOF Announcement: Digital Identity Exchan… John Merrells
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Richard Shockey
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Scott Hollenbeck
- Knowing what BOFs are being thought about [was: R… Elwyn Davies
- Re: Knowing what BOFs are being thought about [wa… Dave Crocker
- Re: Knowing what BOFs are being thought about Spencer Dawkins
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hallam-Baker, Phillip
- Re: Knowing what BOFs are being thought about Frank Ellermann
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Steven M. Bellovin
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Dave Crocker
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hallam-Baker, Phillip
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Steven M. Bellovin
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hollenbeck, Scott
- Re: IETF 65 BOF Announcement: Digital Identity Ex… JFC (Jefsey) Morfin
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Steven M. Bellovin
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Dave Crocker
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Jari Arkko
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hollenbeck, Scott
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hallam-Baker, Phillip
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Dave Crocker
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hallam-Baker, Phillip
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hollenbeck, Scott
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Richard Shockey
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Richard Shockey
- Re: IETF 65 BOF Announcement: Digital Identity Ex… RL 'Bob' Morgan
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Dave Crocker
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hallam-Baker, Phillip
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hallam-Baker, Phillip
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Gray, Eric
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Jeff.Hodges
- Re: IETF 65 BOF Announcement: Digital Identity Ex… Dave Crocker
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hallam-Baker, Phillip
- RE: IETF 65 BOF Announcement: Digital Identity Ex… Hollenbeck, Scott