-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/07/2011 06: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.

Are you saying that we need a Wiki for the template that will be used to fill a
Wiki?

There is a finite number of things that an attendee needs - transportation,
visa, lodging, food, etc...  I do not think that there will be a lot of changes
after few iterations of the draft, and I am OK with publishing a new RFC when
teleportation devices will be available.

- -- 
Marc Petit-Huguenin
Personal email: [email protected]
Professional email: [email protected]
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk7ffgAACgkQ9RoMZyVa61fR+gCfQVOk6tapFFtXfr/L4UIEKjDn
100Ani5u7jiKkfGYZIM3Q5PI7+4mdqP+
=waa2
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf

Reply via email to