I didn't say reading _all_ IETF mail.
But 'don't miss stuff' is a maxim. And filters can be blinders.
Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Thomas Narten [narten(_at_)us(_dot_)ibm(_dot_)com]
Sent: 28 February 2014 12:54
To: Wood L Dr (Electronic Eng)
Cc: chaitanyabd(_at_)gmail(_dot_)com; ted(_dot_)lemon(_at_)nominum(_dot_)com;
ietf(_at_)ietf(_dot_)org
Subject: Re: Clarifying IETF process [Was: A private club]
For an Area Director and IESG member, reading IETF mail, not
discarding it unread, is one of the responsibilities of the role.
This is a blanket statement that I cannot support.
IESG members (as well as IETFers in general) need to be smart about
using their limited cycles. They do not have cycles to read every
piece of email and read every document that they are "responsible"
for.
Reading every piece of IETF email definitely is not prioritizing
resources properly. Indeed, it is not uncommon to see threads that
exhibit properties often associated with DOS attacks.
Thomas