Re: Travel/Attendees list FAQ

Bob Hinden <bob.hinden@gmail.com> Wed, 07 December 2011 16:47 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C64821F8C55 for <ietf@ietfa.amsl.com>; Wed, 7 Dec 2011 08:47:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.465
X-Spam-Level:
X-Spam-Status: No, score=-103.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhR9BoMnpJIR for <ietf@ietfa.amsl.com>; Wed, 7 Dec 2011 08:47:15 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0D15921F8C5C for <ietf@ietf.org>; Wed, 7 Dec 2011 08:47:14 -0800 (PST)
Received: by faas1 with SMTP id s1so252699faa.31 for <ietf@ietf.org>; Wed, 07 Dec 2011 08:47:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=vBwCh7Kl5cLllZdzKJcsrARaagLsPb15kou2LPTOl8g=; b=FtLgGpmq8/xCQNysW96aIFWtUccPIuSdw8Pw3OmEj+Jan1kXmHv4WMMCtw353n5jqS 4ye8n2QqNKHIsrem7WA0bAk5B+pNKVAOY53Bc7q1TKFFy81ynW3Vw3B36ZmfKDnP0ETX ELFvu7LOBFUzTIWvmHoPmL6xjX7O0aklFfFR4=
Received: by 10.50.106.226 with SMTP id gx2mr20629287igb.13.1323276432393; Wed, 07 Dec 2011 08:47:12 -0800 (PST)
Received: from [10.0.0.26] (c-24-130-227-241.hsd1.ca.comcast.net. [24.130.227.241]) by mx.google.com with ESMTPS id wo4sm4661834igc.5.2011.12.07.08.47.11 (version=SSLv3 cipher=OTHER); Wed, 07 Dec 2011 08:47:11 -0800 (PST)
Subject: Re: Travel/Attendees list FAQ
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <83FFEB6E-1FA2-4BD4-A8CE-17F9DC6DC293@lilacglade.org>
Date: Wed, 07 Dec 2011 08:47:10 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE3EE569-AF68-4E75-B911-5CAE6D7EE267@gmail.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914531E0B6B@PRVPEXVS03.corp.twcable.com> <4EDF77EA.5010005@dcrocker.net> <83FFEB6E-1FA2-4BD4-A8CE-17F9DC6DC293@lilacglade.org>
To: Margaret Wasserman <mrw@lilacglade.org>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, dcrocker@bbiw.net, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Wed, 07 Dec 2011 16:47:16 -0000

On Dec 7, 2011, at 7:11 AM, Margaret Wasserman wrote:

> 
> What is the value in publishing a living document as an RFC (which inherently a static, archival document)?  Wouldn't it make more sense to convert the contents of this document to a Wiki page that we could jointly edit and maintain going forward?

+1

I think it's important that this be dynamic and easy to change.  

Bob


> 
> Margaret
> 
> On Dec 7, 2011, at 9:27 AM, Dave CROCKER wrote:
> 
>> 
>> 
>> On 12/7/2011 6:09 AM, George, Wes wrote:
>>> I'm also open to suggestions as to the appropriate publication track for
>>> thisdocument, whether I should look to have it sponsored as a GenArea doc or simply>
>>> put it forward as an individual submission.
>> 
>>> http://tools.ietf.org/html/draft-george-travel-faq
>> 
>> 
>> I suggest that this be processed as an individual submission.  It will still get IETF review but I believe it does not require the level of active consensus by a working group (pseudo or otherwise) that a typical technical specification does.
>> 
>> However I suggest that the document cast itself as a snapshot of an on-going documentation process, with the "master" copy being an IETF Wiki; the document should contain a point to the wiki.
>> 
>> I'll also suggest that there be an on-going mailing list for discussing meeting logistics issues, rather than a different mailing list for each meeting. (ietf-meeting?)
>> 
>> The current contents -- a template of information to be developed -- looks quite good.  But it can't be "complete", and the definition of "complete" is likely to change frequently.  That's a perfect candidate for a wiki effort.
>> 
>> d/
>> -- 
>> 
>> Dave Crocker
>> Brandenburg InternetWorking
>> bbiw.net
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf