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@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf