RE: Diversity and Inclusiveness in the IETF
Hannes Tschofenig <Hannes.Tschofenig@arm.com> Tue, 23 February 2021 11:00 UTC
Return-Path: <Hannes.Tschofenig@arm.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 54E8E3A2A5D; Tue, 23 Feb 2021 03:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.1
X-Spam-Level: *
X-Spam-Status: No, score=1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RAND_MKTG_HEADER=2.999, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=a9wkn6mh; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=a9wkn6mh
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 4mEq_lSpnjUg; Tue, 23 Feb 2021 03:00:23 -0800 (PST)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00043.outbound.protection.outlook.com [40.107.0.43]) (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 961B63A138A; Tue, 23 Feb 2021 03:00:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hvqJDA5WBv2Ne3+466uiW+g0/+2DnaxPz12Q1f6egKc=; b=a9wkn6mhaGSt0nphiOOVRldU0b9sU4mJbxOpB8ePurAygxdH+ARrKI8Y/4bMaL7UmTyQbRCZnHkMWTvqdxaPYc4jqvgOxcliwMwkhhbzOTu6BnSrpE9XsFTS0oeRG1CQxa6bMxKVYOrR3jjYlhLim5bz0LqsfcNNYjAswWcNs8I=
Received: from DB8P191CA0011.EURP191.PROD.OUTLOOK.COM (2603:10a6:10:130::21) by DB7PR08MB3385.eurprd08.prod.outlook.com (2603:10a6:10:4b::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.27; Tue, 23 Feb 2021 11:00:14 +0000
Received: from DB5EUR03FT015.eop-EUR03.prod.protection.outlook.com (2603:10a6:10:130:cafe::83) by DB8P191CA0011.outlook.office365.com (2603:10a6:10:130::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.27 via Frontend Transport; Tue, 23 Feb 2021 11:00:14 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT015.mail.protection.outlook.com (10.152.20.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.27 via Frontend Transport; Tue, 23 Feb 2021 11:00:13 +0000
Received: ("Tessian outbound 2db1bbc8a1d2:v71"); Tue, 23 Feb 2021 11:00:13 +0000
X-CR-MTA-TID: 64aa7808
Received: from ef68ab6b064a.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id 808B97F5-EA1D-40A1-829F-C43FD5ED2BB9.1; Tue, 23 Feb 2021 11:00:08 +0000
Received: from EUR04-HE1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id ef68ab6b064a.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Tue, 23 Feb 2021 11:00:08 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mSUUWwXvdFMYlWP2iGBa4Gwn+7GVDKzW2zWpkNVp5md2KYRDd3udYjyzq8Y07E1VPACpZZrNLa+xWCEz+tZdBx7TAW6nWIa1sl0fYvuqnF5utkdTL1r0YIjpDf8qOZJz58SHeY1cqpH6P+tKRW+nRb5sBjbPzn2t+CyRhs+w1cjaJx43+A21GsPHcg+ow2pPZBMm71VNvBqAKOC/taqElxvVS1uXmQV4KMR1tteg0+sdtBAdTc/tS6Oa7bpjynqw2g093LwC55418/Ws/oXX5Xgk1r4Skqt8/2YnQ7GYy7Wwbs57oHA/0qrD6/2XQUuJwC8T3xO2rqTK7HAS5MKNBQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hvqJDA5WBv2Ne3+466uiW+g0/+2DnaxPz12Q1f6egKc=; b=ksMTFWTiwZztt3R/2ORFFy601I4vQfmxMWDwNkQYIHLkrWojKTb6ZOl0PYBhLmKAnzzo0pdv3sjxYKh/SZ+VNl+XESFmxlc0VXjQKqdRe9BldxUCynV9CmXA9w2lAcwUms9JePOIO2uAjg82Q4Ee1a4faYaYSnEzdce5j1RFBrGPve98KBCOLxHLdMczJgvDx9Z13OwG2478xIArRsmTfpu+n61h019qKIrjmjlUjWi7avRi1vIgj4M1xRAlciKKVZZAcWfrA48OpptPoETHLoIMX95aEujuJcTwRG1vCGBB/Bvl/oHJkI7q+i5hR81TtmYZr4ZNeQp/a8getu6YWQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hvqJDA5WBv2Ne3+466uiW+g0/+2DnaxPz12Q1f6egKc=; b=a9wkn6mhaGSt0nphiOOVRldU0b9sU4mJbxOpB8ePurAygxdH+ARrKI8Y/4bMaL7UmTyQbRCZnHkMWTvqdxaPYc4jqvgOxcliwMwkhhbzOTu6BnSrpE9XsFTS0oeRG1CQxa6bMxKVYOrR3jjYlhLim5bz0LqsfcNNYjAswWcNs8I=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM8PR08MB6529.eurprd08.prod.outlook.com (2603:10a6:20b:354::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.27; Tue, 23 Feb 2021 11:00:04 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::7484:8c2b:e664:648]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::7484:8c2b:e664:648%7]) with mapi id 15.20.3868.033; Tue, 23 Feb 2021 11:00:04 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Bron Gondwana <brong@fastmailteam.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "oauth@ietf.org" <oauth@ietf.org>
Subject: RE: Diversity and Inclusiveness in the IETF
Thread-Topic: Diversity and Inclusiveness in the IETF
Thread-Index: AQHXCXgbtlRdrPa6OEShU5hVFqdRTqplIz0AgABqRRA=
Date: Tue, 23 Feb 2021 11:00:04 +0000
Message-ID: <AM0PR08MB371669108E9CEA561BEC9EF6FA809@AM0PR08MB3716.eurprd08.prod.outlook.com>
References: <37eecb9b-f0eb-e21c-b162-b1f0339e4981@si6networks.com> <3c2d646d-f18d-4d88-b458-29dbd486432b@beta.fastmail.com>
In-Reply-To: <3c2d646d-f18d-4d88-b458-29dbd486432b@beta.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ts-tracking-id: 8628E5505CC33F41BB1971E5BAC2EB20.0
x-checkrecipientchecked: true
Authentication-Results-Original: fastmailteam.com; dkim=none (message not signed) header.d=none;fastmailteam.com; dmarc=none action=none header.from=arm.com;
x-originating-ip: [80.92.115.86]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 34da12ef-9f91-4ade-43c6-08d8d7ea3240
x-ms-traffictypediagnostic: AM8PR08MB6529:|DB7PR08MB3385:
X-Microsoft-Antispam-PRVS: <DB7PR08MB3385FFD29C9E82BC9857B3EAFA809@DB7PR08MB3385.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:9508;OLM:6430;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: aLRldCcl0QZRD8fSLXW90AI+HegokpF97YrYjMTjUmwDNXSZ8eWs9zMbk0L8SLXU5I1LKKMnhyYlrbibk4DJWBDWCc4h/W5ODVNVWWF0YnBaV4gRBLMtVSRltfDdKG7lh4CcqdnDyg4piczuKL/j2oucFNpOHd2/eAc7wU/hi7ByQnV1NPnUntWki9WSsmlpuTzIyOmJbmxXq2/kSj4IXBmNAP53zG0R6d0Cl9hIiGkVNrCRDuUI8QZC5mWCj4a+gh6IL9t8v9oG5yUVGM5VXZZh+IpYr6R+wT2yXhmSGR3t/wD0/3Unix4RuvC748djk8o1SnoW0Jz7p+TyavCx7REDf3FKAcFh0CzRHJP4/cSFq4u14o1/mIpckYJTDPzvl39i6VgEz2eXiL6TYcVtwL9a8NdRtHjgpO8ssWhjbDdxv2aacSlsX+eEXBI8yUeskPUfl66ExZxUELFQkpyNrVGoTHWXfGTrsi4sn9rYQFNB8MQTZNdAAEqENtN+94PS6JoWmxuvszFk6rrmcoUnqCjV7+vxq4v4eqWhOr+qeh/sZuF9a31WMAtVW0kl0NRBH3vOWe5NMYGZSGOj3bJ/jCJLM1CNCcRW9FcDXhyuxQg=
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(346002)(376002)(136003)(366004)(396003)(52536014)(7696005)(33656002)(966005)(86362001)(83380400001)(8936002)(2906002)(478600001)(55016002)(66446008)(26005)(53546011)(66476007)(76116006)(66946007)(64756008)(6506007)(186003)(110136005)(66556008)(166002)(316002)(4326008)(8676002)(71200400001)(5660300002)(9326002)(9686003)(66574015); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: LUNvN364YVFzVIYz1ouOSB4li6nJn1SbtNrL7sAzAK2ZTIz972gMBnAf1/N2xBMs1mjM+nr/yrWuxUw2ZKePDoniP8x/uEh/WhS7hf0i0b2AzydtqdnkFt78M3L4/WRMDMLqr1TuqUEtRYYG6oCNs7wgyjh5zqzh71IQkOyBivTkMKjqdb3d6QGpeKrHixUePbbCKYUAVIQaptpsGLuBXA+eLSk5gjQoDMONgLi031wZwRqb2YSioJoM8BkhikwFvWL3DNewB7CODihxQOFaoCkt+cTiFmuZrMWvlsc3OM0Kh8TNTRgwA8lXJQCle3LBn+QhLANKQYM14A9SX3GqHDUB6vPgCxqdFnolER8VRKEj7FuxOY6nBnwZfnLCrvy8/vlCyl+C6ijtb6cf/KtOP2oiXsR3LNwFNxGTOyz8Yf1G1pbW1wXJSLPQaRwCHobMUvVc0TOH1od+GteSlfkQSgazFjTfAs43IwPoLwpl/ojttDsrKzzoPasmAlmZxv6/PKWRTfaZ0DEP2Yp4/WhHgk4ZmGqts2HXIc5xHKQ+tgjoYbt/I1aZBxI3Dddud3j5gogiKFwuf3+k3Cj2kCeH+luyM7LLRYgn7vy0jsU2A0TriLeYi0Jzdu/BhUYx3k3dByeDv45gdp5B/WMRH0XAajclZLJZT71zrhR22p9t4XkTIoP6OOZBFR4Pia+2F3se6MWjHvEkijpMNmU6GfQOaVhYRnDnRiwmzWQIqz0GkWqbmxhjLP6fwq08UYE4vEdnSuQVrFcWz2aPR5APxVFkWK6/HZ4ioSSmdaDyex9thTBgmMVh+g+v+lH3OeYUkT96lqSZqsB6g+Yh+WD0fHozU2wqxz9PZZEiFclpeIAGh1/U13fGYYJeIXsm75VGtQ5+e8Tlf9zP5WBpCU4LFq2eHf3F85EPlZUJ/7vtuxN74OTcH0/1sEbePvaB9flj2XdWVvyhPA3Quq4jDMQ/dOt1FVLqJ/K10F84nMgtDwazIZ6cSQOaGIzMIXBLksq4OSswmek09jHb/3veEuUwok0s6vIohCUeEJ6V/PQdGtA2qktr2z3enRa0SFfVGPMuLMhHuv3ozUzc1KmUYAv1OxS7AWTR0hrGo/zXNTLwbRL51fOXyAyjbGRo9k7kGm0FG9UwWwzNipEF30AAPHi9uhVDBAU4DeHjGiaBA9BmlNKA0c8fQK0bjVqUtCPHN735wMGHYaoIXCmur+TOaCM8V2aQFMSLudBOu5Tq8hyMFTFLH1Zo2+TfRf9EQ9/GXDO/Qgq9h5fm+VwHFfSHILXmkuFwHUOpPG9mgct0ZeIEpMTc4llRbayiq8IOP4ngD5FirfMb
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB371669108E9CEA561BEC9EF6FA809AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR08MB6529
Original-Authentication-Results: fastmailteam.com; dkim=none (message not signed) header.d=none;fastmailteam.com; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT015.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: ba6ed54b-9bc4-43f1-b7ef-08d8d7ea2ccd
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: dxoqYiRDdJV0QU1UeK4ZtwWClDCRBdJ1yn6yZdQmUX1oGJeBRUkX+D1WEum03xYxK6HL3cid6GfOvnFG/WR4JhUV7fSZ3Op4gbBUpeQi4jYO6XNCWbVvI/P2hVmbjb+/aq6K1pEmAFKau+uw1/vry8w8aach1GrIJs/QcL32kox88vixNGekzlEukp42a/2D/uebRDSGsl6CGrWX7RdUVaIke9mLK4uCDK0IhNOblg+oxiTD+fnf809GUWfVwSwVKkwmlYHH+aS3xTVzt+sYgXeGqS0ovpO1Orb235lpxvr22JaXXSKApwTsBAsmdiKs7b8v2thK0+855WV8ySKFCssDrX2kCq7lgc0C8KxyXwlqW1PxS34BaBcJnbZNdTHM5s8riVDNvmwI9i7jpEa2peLLq7IcuSavj4yjd49J9/FrxRD59U1gSj0WFUQ2BLb2Otyg2LFMk3l8Je/TsiPqbRCFkPezH0WF2DuGi/sQrQNeyOT8kt8wVRpZmO8rRK6KJQaKHq4usy5tu4ZAoRRAzeiLluMqocBvjKi5JMWEtgQd4sPGuGj6gOqtJmOl9ddeHXIhBpdSTuDzk9VFluxMM83L1luCwSOpEoD1wuWWvdtRoOCMLjuLiq4PNI5vy1qSjhrEATj3og3cXtHxGOIXUqMsZgN+DVdJ5FaBLN0vfK7Rc9zqKDH1Fr/wySUs+UWuVpGqx1M4SeEjP/ttxV7VF57BPxD9WBujDpw2XBmc98I=
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com; PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(136003)(376002)(396003)(346002)(39860400002)(36840700001)(46966006)(2906002)(26005)(82310400003)(8936002)(53546011)(55016002)(82740400003)(5660300002)(9326002)(186003)(8676002)(86362001)(450100002)(47076005)(966005)(36860700001)(356005)(83380400001)(336012)(7696005)(33656002)(9686003)(81166007)(52536014)(70206006)(478600001)(110136005)(166002)(70586007)(316002)(66574015)(6506007)(4326008); DIR:OUT; SFP:1101;
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Feb 2021 11:00:13.8211 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 34da12ef-9f91-4ade-43c6-08d8d7ea3240
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123]; Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: DB5EUR03FT015.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR08MB3385
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-IWga67csgyZUIKasjraEzDNpJk>
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 11:00:29 -0000
Hi Bron, I have to respond to your statements about the OAuth working group below. While we do not pay attention to keeping the charter page up-to-date, we have been able to advance our documents, produce many implementations, and got those deployed all over the Internet. The bar for acceptance of new work varies among working group in the IETF. Some working groups develop technology that got widely deployed and hence randomly changing specs isn't such a great idea because you have to consider the deployment situation as well. This is a situation many IETF working groups face. Reaching (widespread) deployment is great on one hand and a pain on the other. There are other groups, which are early in their lifecycle. In those groups you do not need to worry about deployments, backwards compatibility or even any source code. In general, Rifaat and I are always open for anyone in the IETF (and outside) to reach out to us, if they want to bring new work forward to the group. Sometimes proposed work fits into the group and sometimes it does not. The work on JOSE, for example, was put into a separate working group even though it was initially developed for use with JSON Web Tokens. I don't recall having chatted with you or with someone from the JMAP community on the use of OAuth. Sorry if my memory does not serve me well today. Typically, applications just use OAuth and therefore there is no need to reach out to the OAuth working group. Ciao Hannes From: ietf <ietf-bounces@ietf.org> On Behalf Of Bron Gondwana Sent: Tuesday, February 23, 2021 5:20 AM To: ietf@ietf.org Subject: Re: Diversity and Inclusiveness in the IETF Thanks Fernando, I would add to this document something about inertia, backwards compatibility and existing dysfunction. Many ideas are shut down because they aren't in the right place, or don't fit comfortably into the existing corpus of IETF documents. When we brought JMAP to the IETF it was after a long process of socialisation, and still there was significant work in the first couple of meetings just to convince people that "this is worth doing, the existing work the IETF has done in this neighborhood is not sufficient". JMAP also had an authentication scheme in it originally. It was a good authentication scheme, but applications don't do authentication schemes, that's the bailiwick of OAUTH, where ideas go to die (in my experience, that working group has been dysfunctional for my entire time at IETF - exhibit 'A' being the "Milestones" section of the about page, which lists 6 items all due in 2017) So we just removed all mention of authentication method and handwaved "the connection will be authenticated", because we wanted to publish something during the decade with years starting '201'. ... all that to say. One of the biggest barriers to entry in the IETF is stumbling across an area in which no work is able to progress due to entrenched issues within that area. And I'm not arguing for "no barriers to entry", because there needs to be a sanity check that we're actually producing high quality specifications, and that our specifications are compatible with each other so the entirety of the IETF's work product is a coherent whole. But it's hard to get started if you don't already have the connections to have your work sponsored by somebody who already knows their way around the IETF's idiosyncrasies. I'm doing some of that sponsoring myself now for the people from tc39 who are trying to get the IETF to look at defining an extended datetime format. Cheers, Bron. On Tue, Feb 23, 2021, at 11:07, Fernando Gont wrote: Folks, We have submitted a new I-D, entitled "Diversity and Inclusiveness in the IETF". The I-D is available at: https://www.ietf.org/archive/id/draft-gont-diversity-analysis-00.txt We expect that our document be discussed in the gendispatch wg (https://datatracker.ietf.org/wg/gendispatch/about/). But given the breadth of the topic and possible views, we'll be glad to discuss it where necessary/applicable/desired. As explicitly noted in our I-D, we're probably only scratching the surface here -- but we believe that our document is probably a good start to discuss many aspects of diversity that deserve discussion. Thanks! Regards, -- Fernando Gont SI6 Networks e-mail: fgont@si6networks.com<mailto:fgont@si6networks.com> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492 -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com<mailto:brong@fastmailteam.com> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
- Diversity and Inclusiveness in the IETF Fernando Gont
- Re: Diversity and Inclusiveness in the IETF Bron Gondwana
- Re: Diversity and Inclusiveness in the IETF Keith Moore
- Re: Diversity and Inclusiveness in the IETF Dominique Lazanski
- Re: Diversity and Inclusiveness in the IETF Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Dominique Lazanski
- Re: Diversity and Inclusiveness in the IETF Carsten Bormann
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- Re: Diversity and Inclusiveness in the IETF Bron Gondwana
- Re: Diversity and Inclusiveness in the IETF Rifaat Shekh-Yusef
- Re: Diversity and Inclusiveness in the IETF Bron Gondwana
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- Re: [Gendispatch] Diversity and Inclusiveness in … Stephen Farrell
- Re: Diversity and Inclusiveness in the IETF Keith Moore
- Re: [Gendispatch] Diversity and Inclusiveness in … Dan Harkins
- RE: Diversity and Inclusiveness in the IETF Roman Danyliw
- Re: Diversity and Inclusiveness in the IETF Kathleen Moriarty
- Re: Diversity and Inclusiveness in the IETF Donald Eastlake
- Re: Diversity and Inclusiveness in the IETF Fernando Gont
- Re: Diversity and Inclusiveness in the IETF Carsten Bormann
- Making headway in the IETF [was Diversity and Inc… Brian E Carpenter
- Re: Making headway in the IETF [was Diversity and… Keith Moore
- Re: Diversity and Inclusiveness in the IETF Brian E Carpenter
- Re: Diversity and Inclusiveness in the IETF Mark Nottingham
- Re: Diversity and Inclusiveness in the IETF Keith Moore
- Re: [OAUTH-WG] Diversity and Inclusiveness in the… Rifaat Shekh-Yusef
- Re: [OAUTH-WG] Diversity and Inclusiveness in the… Bron Gondwana
- Re: [Gendispatch] Diversity and Inclusiveness in … Mary Barnes
- Re: [Gendispatch] Diversity and Inclusiveness in … Bill Woodcock
- Re: Diversity and Inclusiveness in the IETF Tim Bray
- Re: [OAUTH-WG] Diversity and Inclusiveness in the… Eric Rescorla
- Re: [OAUTH-WG] Diversity and Inclusiveness in the… Bron Gondwana
- Re: Diversity and Inclusiveness in the IETF Keith Moore
- Re: Diversity and Inclusiveness in the IETF Jim Fenton
- Re: Diversity and Inclusiveness in the IETF Phillip Hallam-Baker
- Building Real Internet Platforms Mark Nottingham
- RE: Diversity and Inclusiveness in the IETF Larry Masinter
- Re: [OAUTH-WG] Diversity and Inclusiveness in the… Jim Manico
- Re: Diversity and Inclusiveness in the IETF Carsten Bormann
- We appear to still be litigating OAuth, oops Bron Gondwana
- Re: Diversity and Inclusiveness in the IETF S Moonesamy
- Re: Diversity and Inclusiveness in the IETF Keith Moore
- RE: [Gendispatch] Diversity and Inclusiveness in … Hannes Tschofenig
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- Re: [Gendispatch] Diversity and Inclusiveness in … Vittorio Bertola
- coders in IETF (was: Diversity and Inclusiveness … Keith Moore
- Re: [OAUTH-WG] We appear to still be litigating O… Carsten Bormann
- RE: [Gendispatch] Diversity and Inclusiveness in … Hannes Tschofenig
- Re: [OAUTH-WG] We appear to still be litigating O… Bron Gondwana
- Re: coders in IETF (was: Diversity and Inclusiven… Bron Gondwana
- Re: [OAUTH-WG] We appear to still be litigating O… Bron Gondwana
- Re: [OAUTH-WG] We appear to still be litigating O… Neil Madden
- Re: [OAUTH-WG] We appear to still be litigating O… Aaron Parecki
- Re: [OAUTH-WG] We appear to still be litigating O… Jim Willeke
- Re: Diversity and Inclusiveness in the IETF Phillip Hallam-Baker
- Re: [OAUTH-WG] We appear to still be litigating O… Justin Richer
- Re: [OAUTH-WG] We appear to still be litigating O… Aaron Parecki
- Re: [Gendispatch] Diversity and Inclusiveness in … Mary Barnes
- Re: coders in IETF (was: Diversity and Inclusiven… Phillip Hallam-Baker
- Re: [OAUTH-WG] We appear to still be litigating O… Tim Bray
- Re: [Gendispatch] Diversity and Inclusiveness in … Christian Huitema
- Re: [OAUTH-WG] We appear to still be litigating O… Warren Parad
- Re: [OAUTH-WG] We appear to still be litigating O… Warren Parad
- Re: [OAUTH-WG] We appear to still be litigating O… Warren Parad
- Re: [OAUTH-WG] We appear to still be litigating O… Michael Richardson
- Re: [OAUTH-WG] We appear to still be litigating O… Phillip Hunt
- Re: [Gendispatch] Diversity and Inclusiveness in … Phillip Hallam-Baker
- Re: Diversity and Inclusiveness in the IETF Michael Thomas
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- Re: [Gendispatch] Diversity and Inclusiveness in … Vittorio Bertola
- Re: Diversity and Inclusiveness in the IETF Keith Moore
- Re: [Gendispatch] Diversity and Inclusiveness in … Keith Moore
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Michael Thomas
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: coders in IETF (was: Diversity and Inclusiven… Christian Hopps
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [OAUTH-WG] We appear to still be litigating O… Bron Gondwana
- Re: coders in IETF (was: Diversity and Inclusiven… Christian Huitema
- Re: [Gendispatch] Diversity and Inclusiveness in … Jen Linkova
- Academia (Re: Diversity and Inclusiveness in the … Theresa Enghardt
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Dan Harkins
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Theresa Enghardt
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Christian Huitema
- Re: Diversity and Inclusiveness in the IETF S Moonesamy
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Fernando Gont
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Fernando Gont
- RE: [Gendispatch] Diversity and Inclusiveness in … Hannes Tschofenig
- RE: Diversity and Inclusiveness in the IETF Hannes Tschofenig
- RE: Diversity and Inclusiveness in the IETF S Moonesamy
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Theresa Enghardt
- Re: [OAUTH-WG] We appear to still be litigating O… Warren Parad
- Re: [OAUTH-WG] We appear to still be litigating O… Seán Kelleher
- Re: [OAUTH-WG] We appear to still be litigating O… Seán Kelleher
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Lars Eggert
- RE: [Gendispatch] Diversity and Inclusiveness in … Andrew Campling
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Salz, Rich
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Salz, Rich
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Salz, Rich
- Re: [Gendispatch] Diversity and Inclusiveness in … Marc Petit-Huguenin
- document writing/editing tools used by IETF Keith Moore
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Salz, Rich
- Re: Diversity and Inclusiveness in the IETF Brian E Carpenter
- Re: [Gendispatch] Diversity and Inclusiveness in … Marc Petit-Huguenin
- Re: [Gendispatch] Diversity and Inclusiveness in … Eric Rescorla
- Re: [Gendispatch] Diversity and Inclusiveness in … Keith Moore
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Brian E Carpenter
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Keith Moore
- Re: [Gendispatch] Diversity and Inclusiveness in … Eric Rescorla
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Brian E Carpenter
- Re: [Gendispatch] Diversity and Inclusiveness in … Salz, Rich
- Re: [Gendispatch] Diversity and Inclusiveness in … Salz, Rich
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Salz, Rich
- Re: [Gendispatch] Diversity and Inclusiveness in … Keith Moore
- Re: document writing/editing tools used by IETF Phillip Hallam-Baker
- Re: document writing/editing tools used by IETF Carsten Bormann
- Re: document writing/editing tools used by IETF Joel M. Halpern
- RE: document writing/editing tools used by IETF Larry Masinter
- Re: document writing/editing tools used by IETF Phillip Hallam-Baker
- Re: document writing/editing tools used by IETF Keith Moore
- Re: document writing/editing tools used by IETF Phillip Hallam-Baker
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: Diversity and Inclusiveness in the IETF S Moonesamy
- RE: document writing/editing tools used by IETF Larry Masinter
- Re: document writing/editing tools used by IETF Carsten Bormann
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Lars Eggert
- Re: document writing/editing tools used by IETF Ladislav Lhotka
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Lars Eggert
- Re: document writing/editing tools used by IETF Julian Reschke
- Re: [Gendispatch] Diversity and Inclusiveness in … Lars Eggert
- Re: [Gendispatch] Diversity and Inclusiveness in … Lars Eggert
- Re: [Gendispatch] Diversity and Inclusiveness in … Fernando Gont
- Re: [Gendispatch] Diversity and Inclusiveness in … Lars Eggert
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Colin Perkins
- Re: document writing/editing tools used by IETF Andrew McConachie
- Re: [Gendispatch] Diversity and Inclusiveness in … Vittorio Bertola
- Re: [Gendispatch] Diversity and Inclusiveness in … Bill Woodcock
- Re: document writing/editing tools used by IETF Behcet Sarikaya
- Re: document writing/editing tools used by IETF Carsten Bormann
- Re: [OAUTH-WG] We appear to still be litigating O… Justin Richer
- Re: document writing/editing tools used by IETF Ladislav Lhotka
- Re: document writing/editing tools used by IETF Phillip Hallam-Baker
- Re: [OAUTH-WG] We appear to still be litigating O… Tim Bray
- Re: [OAUTH-WG] We appear to still be litigating O… Aaron Parecki
- How to tell people... Was: We appear to still be … Phillip Hallam-Baker
- Re: document writing/editing tools used by IETF Keith Moore
- Re: How to tell people... Was: We appear to still… Keith Moore
- Re: document writing/editing tools used by IETF Julian Reschke
- Re: document writing/editing tools used by IETF Carsten Bormann
- RE: document writing/editing tools used by IETF STARK, BARBARA H
- Re: [OAUTH-WG] We appear to still be litigating O… Christian Huitema
- Re: [OAUTH-WG] We appear to still be litigating O… Michael Thomas
- Re: [OAUTH-WG] We appear to still be litigating O… David Waite
- Re: [OAUTH-WG] We appear to still be litigating O… Aaron Parecki
- Re: coders in IETF (was: Diversity and Inclusiven… Charles Eckel (eckelcu)
- Re: [OAUTH-WG] We appear to still be litigating O… Phillip Hallam-Baker
- Re: document writing/editing tools used by IETF Phillip Hallam-Baker
- Re: document writing/editing tools used by IETF John Levine
- Re: document writing/editing tools used by IETF Carsten Bormann
- Re: document writing/editing tools used by IETF Michael Richardson
- Re: document writing/editing tools used by IETF Phillip Hallam-Baker
- Re: document writing/editing tools used by IETF Phillip Hallam-Baker
- Re: document writing/editing tools used by IETF Carsten Bormann
- Re: document writing/editing tools used by IETF Keith Moore
- Re: document writing/editing tools used by IETF Carsten Bormann
- Re: document writing/editing tools used by IETF Brian E Carpenter
- Re: How to tell people... Was: We appear to still… Michael Richardson
- Re: How to tell people... Was: We appear to still… Phillip Hallam-Baker
- Re: document writing/editing tools used by IETF John Levine
- Re: document writing/editing tools used by IETF Keith Moore
- Re: document writing/editing tools used by IETF Michael Richardson
- Re: document writing/editing tools used by IETF Christian Huitema
- Re: document writing/editing tools used by IETF Carsten Bormann
- Re: [Gendispatch] Academia (Re: Diversity and Inc… John Wroclawski
- Re: document writing/editing tools used by IETF John Levine
- Re: [OAUTH-WG] We appear to still be litigating O… Bron Gondwana
- Re: [Gendispatch] Diversity and Inclusiveness in … Bron Gondwana
- HTML for email (was: Re: document writing/editing… Keith Moore
- Re: [OAUTH-WG] We appear to still be litigating O… Vittorio Bertola
- Re: HTML for email (was: Re: document writing/edi… Phillip Hallam-Baker
- Re: [OAUTH-WG] We appear to still be litigating O… Warren Parad
- Re: [OAUTH-WG] We appear to still be litigating O… Jeff Craig
- Re: document writing/editing tools used by IETF Behcet Sarikaya
- Re: HTML for email tom petch
- RE: HTML for email Larry Masinter
- Re: document writing/editing tools used by IETF Salz, Rich
- RE: document writing/editing tools used by IETF STARK, BARBARA H
- Re: HTML for email Keith Moore
- Re: HTML for email Benjamin Kaduk
- Re: HTML for email (was: Re: document writing/edi… Viktor Dukhovni
- Re: HTML for email Nico Williams
- Re: HTML for email Nico Williams
- Re: HTML for email Nico Williams
- Re: HTML for email Benjamin Kaduk
- Re: HTML for email Keith Moore
- Re: HTML for email Benjamin Kaduk
- Re: HTML for email Bron Gondwana
- Re: HTML for email John Levine
- RE: HTML for email Larry Masinter
- Re: HTML for email Brian E Carpenter
- Re: HTML for email Phillip Hallam-Baker
- Re: HTML for email tom petch
- Re: HTML for email tom petch
- Re: HTML for email ned+ietf
- Re: HTML for email Nick Hilliard
- Re: HTML for email Keith Moore
- Re: HTML for email ned+ietf
- Re: HTML for email tom petch
- Re: HTML for email Nick Hilliard
- Re: HTML for email Nico Williams
- Re: HTML for email tom petch
- Re: HTML for email Nico Williams
- Re: HTML for email Phillip Hallam-Baker
- Re: HTML for email Keith Moore
- RE: HTML for email Larry Masinter
- Re: HTML for email Phillip Hallam-Baker
- Re: HTML for email Keith Moore
- Re: HTML for email Phillip Hallam-Baker
- Re: HTML for email Keith Moore
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Phillip Hallam-Baker
- Re: [Gendispatch] Academia (Re: Diversity and Inc… Wes Hardaker