Re: Travel/Attendees list FAQ

Margaret Wasserman <mrw@lilacglade.org> Wed, 07 December 2011 15:12 UTC

Return-Path: <mrw@lilacglade.org>
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 20D3B21F8B01 for <ietf@ietfa.amsl.com>; Wed, 7 Dec 2011 07:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level:
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 mzLx8pgZGwVa for <ietf@ietfa.amsl.com>; Wed, 7 Dec 2011 07:12:10 -0800 (PST)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 599D621F8AFE for <ietf@ietf.org>; Wed, 7 Dec 2011 07:12:10 -0800 (PST)
Received: from [10.36.0.36] (pool-108-7-232-64.bstnma.fios.verizon.net [108.7.232.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id 0AC9020198; Wed, 7 Dec 2011 10:12:12 -0500 (EST)
Subject: Re: Travel/Attendees list FAQ
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <4EDF77EA.5010005@dcrocker.net>
Date: Wed, 07 Dec 2011 10:11:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <83FFEB6E-1FA2-4BD4-A8CE-17F9DC6DC293@lilacglade.org>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914531E0B6B@PRVPEXVS03.corp.twcable.com> <4EDF77EA.5010005@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
Cc: 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 15:12:11 -0000

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?

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