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

"Salz, Rich" <rsalz@akamai.com> Tue, 17 October 2017 15:20 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 3D749132D22 for <ietf-nomcom@ietfa.amsl.com>; Tue, 17 Oct 2017 08:20:18 -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 n-izIpJx1Zxa for <ietf-nomcom@ietfa.amsl.com>; Tue, 17 Oct 2017 08:20:17 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 1EECF132C2A for <ietf-nomcom@ietf.org>; Tue, 17 Oct 2017 08:20:17 -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 v9HFIm5c027461; Tue, 17 Oct 2017 16:20:14 +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=4IRYRgG3ZWUfpEXubzMDB3eK/N2Ozrq6jHHDdafnNfU=; b=gUaGuaH8sTfb8s4TrHv6hT64GzWa2/KYZrmnLpKtWTSDeKawRz9Uo4apWjWQGVQ5+bTm rNUE0AHhnUIOnEjP1Y71RhrkRZbbNqcq6i18D99cJT+sV/QBOAKXLVeF39AIwIUpjV8d qTXawAYuv1Zyi2/adqJiEXWAI+sDD95+q5S06lPEjJ5D0DdQ/fQiJ8ziUPyxNneaugB5 j7YEibqZ31D4PGzokoXTeNpDOAiPY6pcsFBHmBxkIhjya1StbKFodb0NCLQBeMRWplW+ dirDbvHVnzsPtH0DQvu7lm8lbnsEq0K3f1vcfkDI5rvEOUv4XMUp8TkVrtcIVbxH8MDb EQ==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by mx0a-00190b01.pphosted.com with ESMTP id 2dkame8qxh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 Oct 2017 16:20:14 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id v9HFGwWW028260; Tue, 17 Oct 2017 11:20:13 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 2dkdwu90rb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 17 Oct 2017 11:20:11 -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 Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 17 Oct 2017 11:20:09 -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 11:20:09 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "ietf-nomcom@ietf.org" <ietf-nomcom@ietf.org>
Thread-Topic: Experiment in "full transparency"
Thread-Index: AQHTR1inDnNd28hDxEu7OgqXzvQ1YKLoazQA
Date: Tue, 17 Oct 2017 15:20:09 +0000
Message-ID: <51CD0D35-1B13-45AE-8B99-8525645B3606@akamai.com>
References: <CAHbuEH6=LLgj-uEonv-fWxc=Qz+TshOb8JAOecYpnieFMetMzA@mail.gmail.com>
In-Reply-To: <CAHbuEH6=LLgj-uEonv-fWxc=Qz+TshOb8JAOecYpnieFMetMzA@mail.gmail.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.39.87]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BCEBB6640AB2BF45829C286CDE9DA986@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-17_11:, , 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-1710170215
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-17_11:, , 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-1710170215
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/-KbsndvtNZ5jRb3Md_8TzbyZEvY>
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 15:20:18 -0000

Kathleen,

I apologize if I embarrassed you in any way.

On 10/17/17, 11:00 AM, "Kathleen Moriarty" <kathleen.moriarty.ietf@gmail.com> wrote:

    Hello,
    
    Since Rich's submission includes comments from our private
    conversation, I'll rehash the conversation to clarify my the points I
    made with some (not all) background on my thinking.
    
    I had asked Rich what he was interested to do as AD.  He responded
    that he would close down I2NSF first.  As responsible AD for that WG,
    I was surprised and tried to explain the value of the work as it
    probably wasn't an area of expertise for him.  As such, my response
    started off with something along the lines of customers brought that
    work into the IETF and we rarely get customers with a problem coming.
    Then I explained the value of the work that is coming from the group
    with an example of a draft that was adopted shortly after we spoke.
    The draft automates provisioning of IPsec sessions within a hosted
    service provider environment.  Many similar drafts will follow to
    remotely provision security services.
    
    Side note: having been a CISO and been responsible for enterprise
    security, being able to provision your security infrastructure and
    deploy security controls for your hosted environments will be a big
    step forward for many. The enterprises ability to generate reports on
    their security controls will help for their internal security
    assessments as well as internal/external audits. I would hope any new
    AD would take the time to understand work they may be managing before
    making decisions to close it down.  Maybe he would do that, but it
    might be a question to dig into more.
    
    Then I explained that with new work comes new people to the IETF.  In
    the case of I2NSF, they are engaging in multiple WGs and that's a
    really positive thing.  Having customers engaged early in the process
    will only improve the outcome.  Then I went into numbers and
    apparently, that's what stuck in Rich's mind and not that I see the
    work of I2NSF as valuable.  With 10 new people for a WG across 130
    some odd WGs, we have over 1000 active people contributing to the
    IETF.  It does bring in new people as as work closes down, others
    leave.
    
    IMO, it's great that some people engaging in new WGs understand the
    IETF way and begin to contribute in other WGs, review work of others
    so they in turn have their work reviewed and improved.
    
    In "full transparency", that's just a few of my thoughts on this
    complicated topic.
    
    
    
    -- 
    
    Best regards,
    Kathleen