+1,000,000 The argument that an RFC, retrieved from the web, is more accessible than a web page or wiki, retrieved from the web, does not reflect reality. The argument that if the questions do not change much from venue to venue needs to be an RFC, and not a web page or wiki, does not hold water. RFCs are supposed to NEVER change. That is why we still have RFC 1000, 2000, 3000 available. Do we really need 6 RFCs covering "what makes a good host", because we keep thinking of new items or to fix old ones? The argument that we need an RFC or twelve to show potential hosts, instead of a "how to host an IETF" web page is beyond wrong. One thing that keeps coming up is the people who do the on-the-ground hosting of IETFs are not people who attend IETFs. They are the "party planners," hotel coordinators, swag printers, etc. For them an RFC is entirely alien. I would be amazed if they (1) could find an RFC and (2) if they read beyond the 1.5 pages of IETF Trust boiler plate. Conversely, these people are totally used to going to a web page to pick up tips or requirements for hosting. In theory I could be swayed for making this data available as a managed web page, but in practice it will get done if it is a wiki. Instead of 16 messages on why we should or should not publish an RFC, which most would agree would be obsolete before it gets published, we could have had 12 entries in a wiki. With Wes' work as a seed, we would be done by now. On Dec 7, 2011, at 3:08 PM, Melinda Shore wrote: > On 12/07/2011 10:51 AM, Ole Jacobsen wrote: >> But a template for the required information would indeed be useful. > > I guess I'm not seeing anything here that looks to me like > requirements, or anything here that can't be satisfied with > something totally open, like a wiki. > > This whole business of trying to formalize this strikes me as > rather of a piece with non-"Bar" non-"BOFs" and ossification > of IETF processes. I think it's great that Wes put together > a proposal and I hope that it's seen as a starting point for > a wiki or some such rather than as yet something else that > needs an editor and needs an approval process and that isn't > as lightweight and responsive as something like an attendees > info sheet should be. > > Melinda > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf
<<attachment: smime.p7s>>
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf