Harald Alvestrand wrote:
Andy Bierman wrote:
Ray Pelletier wrote:
...
A more workable model would be to treat the current
type of meeting as an Annual Plenary, full of Power-Point
laden 2 hour BOFs, and status meetings of almost no value
in the production of standards-track protocols.
The other 2 IETFs would be Working Group Meetings.
Essentially, this as a collection of WG Interim Meetings.
WGs meet for 1-3 days and mash through documents and
get them done fast. Decisions validated on the WG mailing
list within 2 weeks of IETF Friday.
are you seeing these as meetings of *all* WGs, or do you envision
multiple meetings, each with some subset of WGs?
If (guesstimate) 50 of 120 WGs decide to meet in this format, the number
of parallell tracks at one monster meeting will run between 15 and 30.
There would need to be lots of overlap. Lots of preparation
for joint-meetings would be needed. Not everybody
can work on everything at once. (More accurately, most
people won't be able to read email while ignoring the
meeting in as many WGs. ;-)
Meeting slots would be divided into 3 categories, times, allocations,
and proportions decided by the IESG.
- WG
- intra-area
- inter-area
This might even lead to more shared work, more cross area review,
more consistency. You know -- proper Engineering.
(Maybe we have way too many WGs.
That problem is out of scope here.)
It should take 1 year to get a standards-track RFC out the door.
Not 6+ years. The solution is obvious. Quit messing around
and get some work done. This turtle pace has got to end.
Interim meetings should not be a almost-never way to get
work done. Any IETF veteran knows it's the only way
anything gets done around here.
I'm intrigued by the idea of replacing one or more IETF meetings with
"large interims", but would like to work through exactly what's being
proposed. (Of course, scheduling 2 years out DOES interfere with "quick"
experiments....)
The meeting slot allocation (General Agenda)
is set in stone 30 days in advance of IETF Sunday.
BOF agendas are due 30 days in advance of IETF Sunday.
WG agendas are due 15 days in advance of IETF Sunday.
No exceptions.
....and cancellation on those WGs who do not provide such agendas? Just
checking....
Remote audio and jabber for all meetings of course,
and better remote meeting participation tools over time.
If the meeting fees could be lowered over time because
smaller venues are needed 2 out of 3 IETFs, then more
people will be able to participate.
The meeting fee represented 41% of the total cost of
my attendance to IETF 65. IMO, sponsors at the Plenary
meeting would be appropriate, and could help the IETF
fund a cheaper, more stable, IETF-controlled, conference.
My cost for this meeting (VERY rough, off the top of my head):
- Hotel: 800 dollars
- Food: 400 dollars
- Airfare: 1200 dollars
- Meeting fee: 550 dollars
- Misc: 50 dollars
Total: 3000 dollars. Meeting fee percentage: 18%.
But we've been around the "how much does the meeting fee matter" bush
before.
Next time I go to Europe instead of US, our expense ratios
will be reversed. These 2 data points aren't meaningful.
Cheaper is better, and how much it matters varies widely between people.
Harald
Andy
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf