Re: [ietf-nomcom] Experiment in "full transparency"

"Salz, Rich" <rsalz@akamai.com> Tue, 17 October 2017 13:16 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A00621332CD for <ietf-nomcom@ietfa.amsl.com>; Tue, 17 Oct 2017 06:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gpjvM9p8ephV for <ietf-nomcom@ietfa.amsl.com>; Tue, 17 Oct 2017 06:16:39 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [67.231.149.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80B4D13416B for <ietf-nomcom@ietf.org>; Tue, 17 Oct 2017 06:16:36 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v9HDCaCc030698; Tue, 17 Oct 2017 14:16:23 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=jHrhI1hhFkwizE/CMDrVCROBLIZP1ywiX0tNsduHWPI=; b=WQ7hRYsmduj+PdbLEyBhLmCA1SnHOFEdL/6mfc64tPRV0gO2fHCEVXvkivK/m8+xeQEF XkFA2AjyOM2ewv3CLkNcM71l9X/CPTLz9Jp9vl13htye1bMmzfQWVCkUKrHQR9pNuij0 kHeFx4MdOojODC1LY1gxvMuVttF3dUoA5+ZT43SZuh2XkniGQrpyDO4pl5s2MrpgM8qb KLNHFVy3AFtJHGy/p9HaXR3AxYSCSP5g3qyUNHiZsoKDzdloSeqjesxdNRQ/errQCO0z sxKAi1G3depYHokTj7F0NGPT4Id1kpTbPf4WcPuNMP9QGl6bM6dsGYqPOdtt1AYHinsF PQ==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by mx0a-00190b01.pphosted.com with ESMTP id 2dkame8d8f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 Oct 2017 14:16:23 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.21/8.16.0.21) with SMTP id v9HDBP6J014139; Tue, 17 Oct 2017 09:16:22 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint1.akamai.com with ESMTP id 2dkdwu8kv0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 17 Oct 2017 09:16:22 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 17 Oct 2017 09:16:21 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1263.000; Tue, 17 Oct 2017 09:16:21 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: S Moonesamy <sm+ietf@elandsys.com>, "ietf-nomcom@ietf.org" <ietf-nomcom@ietf.org>
Thread-Topic: Experiment in "full transparency"
Thread-Index: AQHTRsiE55WWCJX6hk63Iqd9YTsfKKLoSbsA
Date: Tue, 17 Oct 2017 13:16:20 +0000
Message-ID: <3E158B61-DCF7-485C-B350-DA14B2B8CBDA@akamai.com>
References: <6.2.5.6.2.20171016135236.12dcaa60@elandnews.com>
In-Reply-To: <6.2.5.6.2.20171016135236.12dcaa60@elandnews.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.26.0.170902
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.46.247]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C2804A15886C54499F4C9459240DF93A@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-17_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710170186
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-17_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710170187
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/pIHtvlVEEsNrvJoSUeeOj4kpjo8>
Subject: Re: [ietf-nomcom] Experiment in "full transparency"
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-nomcom/>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Oct 2017 13:16:40 -0000

    
    There is a mailing list to discuss [1] about NomCom.

Is that a public list, or is it for the nomcom members?  I don’t recall seeing it mentioned in any of the email about a public list, but maybe I missed it.  I was thinking of something more like the “99attendees” type of list, or the wg-chairs lists where people who are interested in the *process* or perhaps just this year’s crop of nominees could talk about it.  Is that what this list is for?
    
    Is being selected as Area Director about winning?  The persons whom 
    you are running against are the persons with whom you will have to 
    work with over the next few years.  They may have expertise which 
    complement yours.

Did I give that impression?  I didn’t mean to; but, of course, I want to be AD otherwise I would not have gone through the process.  I freely acknowledge that the other nominees, and almost everyone in the IETF, has traits and talents that complement mine.  Which is to say, that they are better than me at some things. I am probably better than them at some things. If you think I said otherwise, please point out where so that I can improve.

On the other hand, an open and frank statement is better than private triangulation.  If I were to say that I hope you don’t re-pick Jari because he has nasty fish-breath, that’s not right to say in private – if I have a concern like that I should approach the person directly.  The IESG isn’t a children’s playground and the Nomcom aren’t the playground monitors. There is plenty of time for private discussion in the interview.
  
    What is the probability of having diversity from a pool of 
    attendees?  Although the selection of the pool is random, that does 
    not encourage diversity.  I suggest going over the results from 
    several years ago and to see what prompted a change over the last few years.

I don’t quite understand – going over which results, the Nomcom selections?  If that’s what you mean, I would guess that increased sensitivity to the lack of diversity. That’s usually the way things work, especially in high tech. It would be interesting to have an academic study of the diversity in IETF attendance and leadership. I am certainly not qualified to do so, but I think it would probably be worth having.

    The IESG already has a liaison on NomCom.  What good would it do for 
    the IETF Chair to appoint one or more persons to NomCom?
    
I think there should be a voting member.  Nearly half of nomcom is non-voting liaisons and such. That looks strange to me.  As I’ve said, picking randomly picking members from a fairly homogeneous population gets you representative membership, but not diverse membership.  Until the membership if more diverse, I think we need an outside influence. I am not yet sure of the best way to do that; the chair appointment was one possibility.

    I'll comment about some of your responses to the questions.  Will 
    there be a conflict of interest if you are actively involved in 
    OpenSSL?  How will you manage that?
    
I don’t see why it would be any more of a conflict than folks working on Cisco VPN or S/Wan or Firefox or such.  Do you think there is a special concern with OpenSSL?

    What's your opinion about allow "peeking" into TLS? :-)

I am opposed. But the discussion seems premature to me.
    
    Should a Security Area Director be a "SecDir" reviewer or should 
    he/she be there to provide guidance?

In retrospect, I think secdir provides input to the AD’s and that it was wrong to say I’ll continue on secdir. You don’t get two bites at the apple (lawyer saying).  Had I gotten this posted before, the open review probably would have caught that bug. :)

    
    Regards,
    S. Moonesamy

Thank you very much for taking the time to write!  Happy to continue this thread.