> It is broken, anyone that has proposed to host an IETF meeting know it. What
> you can read in the actual web page about hosting a meeting is not correct
> in the reality, and can't be 100% subjective (yes there will be a decision
> at the end, and that imply certain degree of subjectivity, but a criteria
> helps to make it as much objective and fair as possible).
>
> Regards,
> Jordi
>
having hosted an IETF, i'll make the comment that i -really- wanted a
document like this as a "handbook" of things to expect. But that was back in
the
day... I wrote up some notes and passed them on to the next local host. a few
mtgs later, Mark Prior ran into some of the same concerns when he hosted an
IETF.
and so a few of us who -had- hosted IETF mtgs got together and wrote up an ID on
hosting requirements. That draft went 'round the IESG a couple times and then
died
a quiet death. And rightly so. Such a document is not w/in the IETF remit of
defining
Internet Protocols. So i really understand why you too, would like to see
something
like this be in the IETF archives.... but it is NOT in the remit of the IETF as
I understand
it. However, the IETF of today is clearly NOT the IETF i spent time with, so
things
could have changed.
--bill
_______________________________________________
Ietf mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf
