What the TSV ADs say about what TSVAREA said about the TSV AD position at IETF 92
Martin Stiemerling <mls.ietf <at> gmail.com>
2015-06-23 20:32:14 GMT
Spencer and I have been collecting input from the Transport community
about the Transport Area Director (AKA TSV AD) positions at IETF-92.
This email summarizes in a bullet style list what the TSV ADs say about
what TSVAREA said about the TSV AD position
Let us know what your thoughts and ideas are!
Format of this text (exported from a working slide set, so do not get
confused if the text says 'slides' in many places :)
Suggestions from IETF 92 TSVAREA session.
“Q:” slides are unedited suggestions.
“A:” slides are TSV AD thoughts on “Q:” slides.
This material is from the community. It is not from the current ADs
Two TSV folk talked to last year’s Nomcom about splitting one AD
position and working out the details between them
Neither was able to serve as the only replacement for Spencer
They said Nomcom rejected the idea
We had talked about this before IETF92.
It would be challenging for Nomcom (but maybe easier than finding one AD).
If this morphed into a multi-person Area Director function, that could
give you a Smallerized IESG.
This would be similar to the RFC Editor morphing from Jon Postel to the
function we have today.
Q: Splitting the AD role
Details need to be worked (“duh!”). But you need a title for employers
(something like “Deputy AD”).
Deputy ADs would perform some, but not all, tasks that ADs perform today.
This is not delegation unless there’s an appeal.
A: Splitting the AD role
This may touch a fair amount of BCP text immediately.
This could be consistent with the initial Smallerizing proposal,
depending on where that goes. If so ...
We need to move fast on the Smallerizing proposal in the next six
months, if this is going to help TSV.
Q: Add a third AD
Same description as generic AD, but time commitment is 15-25 hours
instead of 20-40
Open to the possibility that all three ADs might not be peers
Potentially unequal time commitments
A: Add a third AD
We are already reducing the time commitment is 15-25 hours for TSV ADs,
whether we have two ADs, or three, so that part is happening.
This was the smallest change we could think of.
If we don’t add a third TSV AD, we need to make bigger changes (“go big
or go home”).
Q: Fix the funding problem directly
Funding problem is the worst for academics and researchers
Can’t get US researchers funded as ADs at all. EU researchers a little
better but still very hard
Funding from ISOC? Funding from ICANN?
Google concerned that direct funding would cause (apparent or real)
conflicts of interest
A: Fix the funding problem directly
Biggest change the community proposed.
Not sure how it helps attract researchers and academics.
We’ve heard concerns about “full time standards people” for years. This
may be more so.
If we do this, it’s not clear why the proposal would be limited to TSV.
Q: Size the area for available ADs
Stop doing academic exercises
Start closing working groups
Reduce the number of documents in process
A: Size the area for available ADs
We are closing working groups now.
We are giving away working groups now.
Not clear how much more we can downsize.
“Core TSV only” is still something like 10 WGs.
Much new IAB Stack Evo work fits in core TSV.
**Summary of TSV AD responses
Jobsharing - would help
Use Deputy ADs - would help
Add a third AD - would help
Fix funding problem - wouldn’t help
Resize TSV area - wouldn’t help
Spencer and Martin