Re: [ietf-nomcom] Experiment in "full transparency"
"Salz, Rich" <rsalz@akamai.com> Tue, 17 October 2017 15:35 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 B822D132C2A for <ietf-nomcom@ietfa.amsl.com>; Tue, 17 Oct 2017 08:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 Kyra9p4c9jwg for <ietf-nomcom@ietfa.amsl.com>; Tue, 17 Oct 2017 08:35:00 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 0FA0B132320 for <ietf-nomcom@ietf.org>; Tue, 17 Oct 2017 08:34:59 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v9HFMgFm019290; Tue, 17 Oct 2017 16:34:58 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=p46H3/whYUwugjF8TexDD64NPBkf3LphqsQwG1dMoNE=; b=iqREvVmUySNrS7UtDVMES0aU/HpFLNCRG4Xfn+1UASoygZsRUFEqGJbwSF78aF0B/H5q nLhWdULFAalDm+lIRtQF4dM3HBUE/yOhvwLlqkxQLNvremStsd2gcVkeuWE1G2p6QFYR FnUxn3FC6vY0zCGjfF7pAoB71pkbjZdrTS8GLLm5fzBFc2pXnGfDqYTfxWBmj4xBgc9o XpF68sjlPhendhVexMoAuS1fELCuvMs5mr3wuLy2DtkJoNmezhjim/goSWoPpUsDVfkP s2grg310XAQzvOucHyyhYyFaBj8XgKH3ZO0ySBnlzxTxiXyGSXuLUndRxn/GkyJiBWS7 EQ==
Received: from prod-mail-ppoint3 ([96.6.114.86]) by m0050096.ppops.net-00190b01. with ESMTP id 2dkb05gvat-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 Oct 2017 16:34:57 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id v9HFVeiE004087; Tue, 17 Oct 2017 11:34:56 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint3.akamai.com with ESMTP id 2dkdww2v61-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 17 Oct 2017 11:34:56 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 17 Oct 2017 11:34:55 -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:34:55 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
CC: "ietf-nomcom@ietf.org" <ietf-nomcom@ietf.org>
Thread-Topic: Experiment in "full transparency"
Thread-Index: AQHTR1inDnNd28hDxEu7OgqXzvQ1YKLoazQAgAAB0ICAAAJQAA==
Date: Tue, 17 Oct 2017 15:34:55 +0000
Message-ID: <03C88ED2-0327-468E-B4F1-BC14EF08E53F@akamai.com>
References: <CAHbuEH6=LLgj-uEonv-fWxc=Qz+TshOb8JAOecYpnieFMetMzA@mail.gmail.com> <51CD0D35-1B13-45AE-8B99-8525645B3606@akamai.com> <CAHbuEH73YSmmqz-D1A-sSn3AtMcKQZPdB=UhAo1v-zs9BwDyOQ@mail.gmail.com>
In-Reply-To: <CAHbuEH73YSmmqz-D1A-sSn3AtMcKQZPdB=UhAo1v-zs9BwDyOQ@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: <BDAF1752C9C9D04DB4EB9E166803ADD7@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-1710170218
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-1710170217
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/oHTM80ixZrPzQU0H8hTsXAf0QyQ>
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:35:02 -0000
I agree, I mis-summarized what you said. I hope the important point -- that I learned something from our conversation – doesn’t get lost. On 10/17/17, 11:27 AM, "Kathleen Moriarty" <kathleen.moriarty.ietf@gmail.com> wrote: Rich, It was a misquote and I'm not embarrassed as I never said we should start up new WGs that don't have value. I felt it was important to clarify since my thoughts are very different from your statement. I do believe in the work of the WGs for which I am the responsible AD and have spent the time to understand the importance of their work. Best, Kathleen On Tue, Oct 17, 2017 at 11:20 AM, Salz, Rich <rsalz@akamai.com> wrote: > 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 > > -- Best regards, Kathleen
- [ietf-nomcom] Experiment in "full transparency" Kathleen Moriarty
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… Kathleen Moriarty
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… Kathleen Moriarty