[discuss] Comcast undertakes 9 year IETF cosponsorship!?

[Stephen Farrell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


One clarification...

On 03/23/2014 12:22 AM, David Conrad wrote:
> 
> The question of whether or not members of "the Board" can
> influence those standards is slightly different. Again,
> over-simplifying a lot, IETF standards must be approved by the IESG
> which is made up of the Area Directors. For sake of argument, one
> could posit a scenario where an evil company could capture some or
> all of the IESG (challenging as it would require compromising the
> Nomcom process or buying off AD members).

Buying off would be required, since for the IESG, nomcom generally
limit one organisation to 2 ADs. There are exceptions when there
are 3 IESG members from the same orgnaisation. There are 15 area
directors who currently make up the IESG.

For Michael's benefit: all the nomcom details can be found, as
usual, in RFCs, with some surrounding text at [1]. Not enthralling
reading to be sure, but if you do read those RFCs you'll get a
good feel for that part of the IETF. And recall that all those
RFCs have been through the usual IETF consensus process.

> However the only impact this would have in standards setting would
> be to delay/block the publication of a document as an RFC. In most
> cases, this would be unlikely to impact the setting of standards
> since folks interested in the standard would probably just go an
> implement the Internet Draft (the pre-RFC document) produced by the
> working group. The blockage would also be public and obvious. It is
> also unrelated to sponsorship.

Well, an AD can also propose a new WG on a topic but needs to
get the rest of the IESG to agree. There are bits and pieces
of AD influence that are not solely related to delaying stuff.
But the steering part of being an AD requires people who want
to be steered, an AD can't really push against the tide.

> As Stephen said, "you're barking up the wrong tree."

Very much so.

Cheers,
S.

[]1 https://www.ietf.org/nomcom/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQEcBAEBAgAGBQJTLjFZAAoJEC88hzaAX42iiMAH/ji4j/3dqIa+GGy+9zIybKBl
VJ/Bs3d6/qyyhrcOm848u2LWZrQEChxvt27KtW1KeLx5A9sSxEvNvvaU8dfYxTkn
r4/ZJzsvvYsh5gQDC8Sc8ntHh119nrjlIft5mUD7SAP2x7bd38EKWsA62XMuWMhm
Yl8epmxRCRb/qERuT0hjlzlb7SoLFeQ6I99Rfm8bQ2tzl8nv+2Lsu8nfcF9E4N6l
iMbjtCT1/7YCR/UvouegqBUygzmb5g5IObJTkeY1C29zdxhVEHPZa8eXuSCebOg+
p1Ar9kucmQNM8yjI5kgyhiZq2tf2sJ3hnNgVTtcUObYs4jb4dwV5QdGO1BsxCg8=
=iRfu
-----END PGP SIGNATURE-----