Re: Diversity and Inclusiveness in the IETF

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Tue, 23 February 2021 15:21 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 904513A2C5C; Tue, 23 Feb 2021 07:21:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 OtoKGjNbKa4z; Tue, 23 Feb 2021 07:21:30 -0800 (PST)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BB7B3A2C8F; Tue, 23 Feb 2021 07:21:29 -0800 (PST)
Received: by mail-ua1-x92f.google.com with SMTP id t15so5651551ual.6; Tue, 23 Feb 2021 07:21:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7pcvps3xOGwjcSGAtufYWPdsFnx3uuJpgOZqqZ+wsz0=; b=I9I9/Py5zQO2S5Sw22/UeNA8kgTHLYainOFGnEi/7rsI5BvbTqQQObmpusQZqaKttL 8ggnd/NDTZSvZ4ZYKnroWr2AYMTDsIRYA//YDnPGlBmvGINBCfc6YWGtf0lr4xoKV4WN 6BVVEobm1rIUvAkoIBgAGpKfO7Wu7hzeGAL+zpgCCyfXyP2py9Ei6Hj2ecXMv+CslQRH IAxOf2s27msLK9brGarQLXpAZHU0n9/GJZrEH5K1fNpzEogJ/JQ9l3KjgR4iWp3qkIuH xS4s8ZrBVSK+rO6mawSXQszJ2ponk2AivG4fkGv2C9dYTBWDBaaClPeRXPTOmkhRDo02 UTXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7pcvps3xOGwjcSGAtufYWPdsFnx3uuJpgOZqqZ+wsz0=; b=kTo5QbISQdQn/lYDrzDTCC6y/jH3hRZ0XM84WYdjhaFsAad5e2V3mV4AwuG3cAikUQ zC7U6BhzJCDpl8wdo42m++Ke5XC39QP30hT50dsNydZiBHHUYaM844mUDW8Vd95zHQAn 2QlM08gtFoR/F8MpQXuOlse1p2NHJe3ey3JCl/yEsozX5PhOFH1ZL4kv5sgdDa0AplYT a1GPh/6ovYL8k/pnl2L3rKZR7dYTDDm5Ts6vgGZp8EUo02VbuQtopNV6lYSV79lFakzv Q7AWPpGJp8sZ/nDZMpDOFyjj0JFBEeQH32awtiPdRrL+bB+605lUe/teKQPR5wv17O+S aXsA==
X-Gm-Message-State: AOAM530zdQkomZakUO47UXZwbtbJwPbSpCXkN4qcpGCnvfZGnzXm+o2i v+sOnwYtEzP9C2uiGqd4ZIc2TX7QhxZEXaeYzt1ATH/F
X-Google-Smtp-Source: ABdhPJzGhPYTx9/v+D3i/gLyPbAfgDJvkTQv+wkeRWYPwatYBvrZ2Ubxukfv4wnwGl4d0u7x+RzUhE+ZkD6Cv/rZe6w=
X-Received: by 2002:ab0:5963:: with SMTP id o32mr17685992uad.11.1614093687285; Tue, 23 Feb 2021 07:21:27 -0800 (PST)
MIME-Version: 1.0
References: <37eecb9b-f0eb-e21c-b162-b1f0339e4981@si6networks.com> <3c2d646d-f18d-4d88-b458-29dbd486432b@beta.fastmail.com> <AM0PR08MB371669108E9CEA561BEC9EF6FA809@AM0PR08MB3716.eurprd08.prod.outlook.com> <d6648437-332b-4668-a1c7-591f2c287539@dogfood.fastmail.com> <CADNypP8GKTY-Jhpb6AEfcpXOihwLap7OrrByNemGc2GNvZLeog@mail.gmail.com> <10fd9d2d-afb4-44aa-b618-fb5ce1efa69e@dogfood.fastmail.com> <c21477c8f68047cabac7aeae60a688f2@cert.org>
In-Reply-To: <c21477c8f68047cabac7aeae60a688f2@cert.org>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Tue, 23 Feb 2021 10:20:51 -0500
Message-ID: <CAHbuEH7Qvc3AaBxbk1kXd4knS4_+Wrs3P7WNETRNNoFP-dGNCA@mail.gmail.com>
Subject: Re: Diversity and Inclusiveness in the IETF
To: Roman Danyliw <rdd@cert.org>
Cc: Bron Gondwana <brong@fastmailteam.com>, Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dd6bbd05bc02780e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F97ozfsjENT0-RDxn82QOcFtwus>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2021 15:21:33 -0000

On Tue, Feb 23, 2021 at 9:30 AM Roman Danyliw <rdd@cert.org> wrote:

> Hi!
>
>
>
> *From:* ietf <ietf-bounces@ietf.org> *On Behalf Of * Bron Gondwana
> *Sent:* Tuesday, February 23, 2021 7:47 AM
> *To:* Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>
> *Cc:* ietf@ietf.org; oauth@ietf.org
> *Subject:* Re: Diversity and Inclusiveness in the IETF
>
>
>
> On Tue, Feb 23, 2021, at 23:40, Rifaat Shekh-Yusef wrote:
>
> So you have never reached out to us to try to bring any work to the WG,
> and based on attending one meeting and hearing from a few people, you
> formed a strong opinion and declared that "nothing would get done"? that
> seems odd.
>
>
>
> Based on a few meetings, and having heard from many people.
>
>
>
> For your information, last year we published 4 RFCs, and we already have 3
> documents with the IESG and more to come.
>
>
>
> That's good to hear.
>
>
>
> [Roman] In addition to regular cadence of proposed standard publications
> noted above, I would additionally note that all of these documents came
> with a model behavior of multiple implementations by WGLC – typically 3+.
> The WG has not only managed to steadily complete its work items in the IETF
> but also interest an implementor community to ensure this work is used.
>

And way back when I was AD, OAuth was by far the most productive working
group I managed.  They put out what felt like about 3 documents a meeting
for full publication.  I was the AD for 3 years, ending in 2017 when EKR
became an AD.

There was a bit of management as a result of the number of experts and
varying use cases for their environments, but even with that, OAuth was
very productive.  Since your document was 2016, I was likely the AD.  Yes,
the meetings had challenges at times, but we worked through it and things
got done.

Best regards,
Kathleen


>
> Regards,
>
> Roman
>
>
>


-- 

Best regards,
Kathleen