I am not arguing against the wiki, I am just saying that there is value in having a single "file", or "document", or maybe "checklist" that can be retrieved (and printed) too. And we have lots of docs that could hardly be described as "formal". But a template for the required information would indeed be useful. Ole Ole J. Jacobsen Editor and Publisher, The Internet Protocol Journal Cisco Systems Tel: +1 408-527-8972 Mobile: +1 415-370-4628 E-mail: ole@xxxxxxxxx URL: http://www.cisco.com/ipj Skype: organdemo On Wed, 7 Dec 2011, Melinda Shore wrote: > On 12/07/2011 10:33 AM, Ole Jacobsen wrote: > > The flip side of this argument is that it could be viewed as a helpful > > guide for the hosts/sponsors at any given venue. ("This is the kind of > > information you should provide.") > > I don't see any reason that couldn't be wikified, either. > > I am not sure that there needs to be a document describing what > should be made available, other than as a tool to structure the > discussion. I'm also pretty sure (not 100%, but somewhere north > of 50%) that there really aren't any serious archival requirements > for the material under discussion. > > We're not the ITU-T, we're not ETSI, etc - not everything needs to > be formalized. > > Melinda > _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf