On 7/16/2013 11:56 PM, Reinaldo Penno (repenno) wrote:
I understand technical skills are very important, but they comprise
most of the list. There is mention of "and this requires good soft
skills" but I wonder if we can say something more concrete?
How about "management experience" ? Without detracting from the
technical requirements, in my opinion given an AD role soft skills are
as important. ADs should have "strong soft skills". This is a good
opportunity to balance things a bit more.
Hi, Reinaldo,
Although Martin included this pointer to a "Generic Expertise" write-up
in his earlier e-mail asking for feedback, I didn't include it in the
e-mail you replied to (sorry!)
http://trac.tools.ietf.org/group/iesg/trac/wiki/GenericExpertise
We're thinking that the "Generic Expertise" section captures much of
what we needed to say about the needed "soft skills" for TSV ADs, but
your note reminded us that the TSVAREA Nomcom discussion at IETF 86 ALSO
skipped over the "Generic Expertise" material, so we're adding a
back-reference to "Generic Expertise" in the TSV description.
So, thank you for sending your note - it had an effect.
Spencer and Martin
thanks,
Reinaldo
------------------------------------------------------------------------
*From:* [email protected] [[email protected]] on
behalf of Spencer Dawkins [[email protected]]
*Sent:* Tuesday, July 16, 2013 7:13 PM
*To:* Jim Gettys
*Cc:* Martin Stiemerling; [email protected]
*Subject:* Re: Feedback request: The desired expertise of a Transport
Area Director (updated)
On 7/16/2013 7:38 PM, Jim Gettys wrote:
On Tue, Jul 16, 2013 at 6:40 PM, Joe Touch <[email protected]
<mailto:[email protected]>> wrote:
I would suggest rewording it to avoid repeated reference to
congestion, and include these other issues:
A Transport AD should have a broad understanding of core end-to-end
transport topics such as congestion, control loops and
hysteresis, flow control, reliability issues, connection issues,
and interactions with the network layer, the application layer,
and middleboxes.
There are two words missing entirely that are key:
Queuing and, even more important, Latency
Thank you both, Joe and Jim, for quick and actionable suggestions!
Spencer
