Re: [secdir] What and who is SecDir?

Steven Bellovin <smb@cs.columbia.edu> Fri, 15 April 2011 18:31 UTC

Return-Path: <smb@cs.columbia.edu>
X-Original-To: secdir@ietfc.amsl.com
Delivered-To: secdir@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 38DB2E079D for <secdir@ietfc.amsl.com>; Fri, 15 Apr 2011 11:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gVgQkMNQ48kL for <secdir@ietfc.amsl.com>; Fri, 15 Apr 2011 11:31:45 -0700 (PDT)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfc.amsl.com (Postfix) with ESMTP id 741A1E06B0 for <secdir@ietf.org>; Fri, 15 Apr 2011 11:31:45 -0700 (PDT)
Received: from [192.168.147.175] (74-202-225-34.static.twtelecom.net [74.202.225.34] (may be forged)) (user=smb2132 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id p3FIVA30009012 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Apr 2011 14:31:41 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <sjmd3knl7fl.fsf@pgpdev.ihtfp.org>
Date: Fri, 15 Apr 2011 14:31:09 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <A8B2E730-CEEC-45AF-8DDE-1C4FD30F265F@cs.columbia.edu>
References: <BANLkTikPFip0_ozfe=E-GzfwzmDqZ5t+gQ@mail.gmail.com> <sjmd3knl7fl.fsf@pgpdev.ihtfp.org>
To: Derek Atkins <derek@ihtfp.com>
X-Mailer: Apple Mail (2.1084)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
Cc: Barry Leiba <barryleiba@computer.org>, "secdir@ietf.org" <secdir@ietf.org>
Subject: Re: [secdir] What and who is SecDir?
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 18:31:46 -0000

On Apr 15, 2011, at 2:02 06PM, Derek Atkins wrote:

> Barry Leiba <barryleiba@computer.org> writes:
> 
>> For my part, I certainly think, Nico, that you do still belong here.
>> I'd hate to see people leave this directorate just because they no
>> longer chair any sec-area WGs.  That we don't always agree, as a
> 
> If that were the case I'd have left the directorate a while ago, and a
> number of current members would never have been on it (because they have
> not been chairs of security-area working groups).  I don't think that
> having a blue dot is a requirement to be on the sec-dir (although I
> think that the inverse is true, having a blue dot (in the security area)
> should require you to join sec-dir.

As the former SEC AD who set up the current structure, you're quite right.
I (re)started it as a group of people whom I thought could contribute to
security in IETF protocols, and shortly thereafter (I forget on whose
suggestion) added the SEC WG chairs.

		--Steve Bellovin, https://www.cs.columbia.edu/~smb