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.")
At APRICOT, we've developed an "Ops Manual"[1] that covers everything
from room setup to "no kareoke" at the social event. I am not saying
that our document needs to be an RFC, but we don't have a lot of
alternative ways to publish things that can be quickly retrieved,
printed off and so on.
[1] http://www.apricot.net/docs/APRICOT-Op-Man.pdf
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, Bob Hinden wrote:
>
> While I agree that the questions won't change as often as the
> answers, it will likely change. We have come a long way from just
> asking how many cookies there will be.
>
> Also, if it gets published as an RFC, it is going to be viewed as a
> "specification". I think it's best to avoid that and just have a
> wiki. I would be surprised if this topic continues to be as active
> area of discussion in the future, making it unlikely that there
> would be new RFCs published.
>
> Further, is this something we really want in the historical record.
>
> Bob
>
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf