Re: ISMS working group and charter problems

Dave Crocker <dhc2@dcrocker.net> Tue, 06 September 2005 20:06 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECjho-0005Wx-6k; Tue, 06 Sep 2005 16:06:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECjhm-0005Wg-6l; Tue, 06 Sep 2005 16:06:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21349; Tue, 6 Sep 2005 16:06:04 -0400 (EDT)
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECjkm-0000DA-Bp; Tue, 06 Sep 2005 16:09:14 -0400
Received: from [192.168.0.2] (adsl-64-175-241-69.dsl.sntc01.pacbell.net [64.175.241.69]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id j86K6ZQq009099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Sep 2005 13:06:35 -0700
Message-ID: <431DF69D.5090108@dcrocker.net>
Date: Tue, 06 Sep 2005 13:05:49 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <431DD3BD.9090108@cisco.com> <431DD94C.8070907@dcrocker.net> <tslfysi2ge8.fsf@cz.mit.edu>
In-Reply-To: <tslfysi2ge8.fsf@cz.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Found to be clean
X-Songbird-From: dhc2@dcrocker.net
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, iesg@ietf.org
Subject: Re: ISMS working group and charter problems
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


> Certainly one of the reasons I requested IETF-wide review for the ISMS
> recharter is so that decisions like this can be reviewed by the
> community.  The IAB gets to see charters at about the same time as the
> IESG does; they have sent no negative comments to this charter.


Sam, I've tried to search the ietf-announce archives, google, etc. for any sort 
of announcements, outside of the isms working group, concerning the draft 
re-chartering text for isms.  Unfortunately I have not been able to find it, so 
I do not know what request of yours you are referring to.

In any event, I think the significance of Eliot's (and Steve Bellovin's) 
postings have less to do with a chartering event and more to do with decisions 
made DURING a working group's normal activities.  In particular, when a working 
group gets to the point of making a decision that has broad architectural or 
operational impact, it is the expertise of ADs, IAB members, and other senior 
participants, that can serve to raise a question to the larger community, 
exactly as Eliot is now doing.

What I took from Steve Bellovin's posting was the implication that his valid 
concerns were expressed in a more limited context.  What I am suggesting is that 
we should get into the habit of having such concerns raised in the broader 
community, when the impact is this large.

-- 
 
   d/

  Dave Crocker
  Brandenburg InternetWorking
  +1.408.246.8253
  dcrocker  a t ...
  WE'VE MOVED to:  www.bbiw.net

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf