Re: [Gendispatch] draft charter text: terminology-related WG
Alissa Cooper <alissa@cooperw.in> Mon, 15 February 2021 15:35 UTC
Return-Path: <alissa@cooperw.in>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340D13A0C70 for <gendispatch@ietfa.amsl.com>; Mon, 15 Feb 2021 07:35:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=cooperw.in header.b=QvcFd9Im; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Hhr/nW9m
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 JAJMuOFnZiCt for <gendispatch@ietfa.amsl.com>; Mon, 15 Feb 2021 07:35:26 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 298FD3A0C6F for <gendispatch@ietf.org>; Mon, 15 Feb 2021 07:35:26 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 9ADF05C0052 for <gendispatch@ietf.org>; Mon, 15 Feb 2021 10:35:24 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 15 Feb 2021 10:35:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:content-type:content-transfer-encoding:mime-version:subject :date:references:to:in-reply-to:message-id; s=fm2; bh=QkN6cm9vqn /rlEgkdFbBzTzWat2r6TFfOmoJZmf6NNI=; b=QvcFd9ImL99pAwc7dYY4bdR0q2 CJqxlns1uDMEyH42wMVOrYlA8XFrq0Nhl61I//pIqN/Nm4Y0G+iFtyGlgDzYZAOE 070DsTd83uMxZ//byYz4CtYKkMBuCsYtDRLZ2h3igQ8O7LEJsxStSCya0/7imOmI Y4yGBOMHAGPY9a+PCV6+ZWB7J1E68fF0UHARI7Z8ZGfOX47338C15ivZDllH8biE HUdz41KmgrT0krRyma/GJPX1vzy1dLvMla3IzAevf9U1mqPUZxY0VmVrSqPuwbQ4 WAx6WSJgkNQuMNEVc/7CzmkMrJWrLyIHkurRHLEemgAbM3y5fslpwgtjr/xg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=QkN6cm9vqn/rlEgkdFbBzTzWat2r6TFfOmoJZmf6N NI=; b=Hhr/nW9mNSSZJZnhMEWhzCYe80rgHhWUFpHeUVf8YeAJE5njwT2fs4atQ X29ovWWc/VDjMNzPywNT5Vp8YGy+Tj2MnmbDw01rLnqKv+7Wva8bK4fKevp40XUd BMpHgJfIU0icm2WGEbiHLlYykguPMbMW6+E03qX/K+bwjUlP4DmgVDB2jivcKAY/ Tk0dvG+YB86DrIJvrtRarUqAgcoA7cg/1wU0DCch67jE46TPrevYn5SDjtbEBJLm QK7eeR28lyb0vEn0AxbZWcdeFImDsya3UFPHnmhhNphEmX11smk8T30VPR4l+zir Wep5tyItzn2oZu0Uh1whTLj7N7nFA==
X-ME-Sender: <xms:vJQqYGrdDN2zioYktZFsbOX0i2XPct-0i6F6i1n8Yj1hXSfLm6Y4ZQ> <xme:vJQqYEqeFf9VYnSBy9GT-WUwLmgibF6a8Hn5gUiX9ZgKTum76_tAD2fSimxAZEklc o5KWv4k0KgCeIQh-g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrieekgdejhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhtgfgggfuffhfvfgjkffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuggftrfgrth htvghrnhepvdfffeejtdeijeeguedtgffgueegjeejffegjefgfeekheetueejjeehgfej hfelnecuffhomhgrihhnpehgihhthhhusgdrtghomhdpihgvthhfrdhorhhgnecukfhppe dujeefrdefkedruddujedrieehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:vJQqYLM5AxgSYXmAtW0lYGZ17JYB1oij7SHT85FUMoIlx1t83Hplog> <xmx:vJQqYF7PHc_IWyw81MY8iNyPoB3GEjBmiQiCYIWEwcp4M5ca-nvQBQ> <xmx:vJQqYF6D6-KCpTWeDGAof0dlOLnfVBcS7KzOK3aP4ghK2dQv-TMMkg> <xmx:vJQqYHHLz97VZNXXAp0TadVGGbiwIdvEzLOgEs9L-DtsgOfH1EHDJA>
Received: from rtp-vpn3-175.cisco.com (unknown [173.38.117.65]) by mail.messagingengine.com (Postfix) with ESMTPA id 0066F240057 for <gendispatch@ietf.org>; Mon, 15 Feb 2021 10:35:23 -0500 (EST)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 15 Feb 2021 10:35:23 -0500
References: <A531C377-33A4-4138-BE28-788FF5FE267E@sn3rd.com> <9ED61E90-CC72-431B-BB41-7801262A75AC@cooperw.in>
To: GENDISPATCH List <gendispatch@ietf.org>
In-Reply-To: <9ED61E90-CC72-431B-BB41-7801262A75AC@cooperw.in>
Message-Id: <BB601F16-71AC-4658-BEC2-F89C0D87D0FE@cooperw.in>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/NEUMqUPMjGltWE7hYbSMIq1e7f0>
Subject: Re: [Gendispatch] draft charter text: terminology-related WG
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2021 15:35:28 -0000
I forgot to mention that I added some recent references to https://github.com/ietf/terminology/ — 3GPP, the IEEE 1588 PAR, CNCF, Bluetooth SIG — but there have likely been other developments so please send PRs if you’re aware of others. Thanks, Alissa > On Feb 15, 2021, at 10:21 AM, Alissa Cooper <alissa@cooperw.in> wrote: > > Hi Sean, all, > > Thanks for proposing this charter. A few notes related to comments made in the thread thus far: > > (1) There were several documents proposed on this topic last year and in previous years. The GENDISPATCH process was run, including two virtual interim meetings focused specifically on this topic, and the result of that process was rough consensus to have a quick-spin WG to produce an informational document on this topic [1]. Re-hashing the dispatch discussion is not useful. Specific edits or suggestions about the charter text are useful. Thanks to those who have already provided suggestions. > > (2) Of note in [1] is Francesca and Pete’s observation about the proposed WG deliverable that "there were concerns about describing motivations in such a document for fear of ‘ratholing’.” Those concerns seem to apply equally to this charter discussion. Since there was significant discussion about motivations during the GENDISPATCH process last year, perhaps it would be better to avoid that discussion to the extent possible in the chartering phase as well. > > (3) Regarding diversity and inclusion, there is so much more work to do, and there are many places in the IETF constellation where components of that work can be done: WGs, EMODIR, the NomCom, the LLC, the IAB. Detailed proposals for specific pieces of work or new programs or ideas targeting any or multiple of these bodies are welcome, and a comprehensive analysis as a baseline is a great idea. It is disheartening, though, to see claims that nothing has been been done to increase diversity and inclusion in the IETF, because the many volunteers and staff who have put time and energy into the existing initiatives deserve credit for their work. The expanded and revamped newcomers program, the consensus publication of RFC 8719 and RFC 7776, the expansion of the systers networking events, the ANRP and ANRW, and a couple of travel/attendance assistance programs that were in the works for 2020 pre-pandemic are all examples of institution-level initiatives. These complement many other individual initiatives: regional and local mailing lists, remote hubs, selection of diverse WG chairs (which I have tried to make a priority personally), training for NomCom members, etc. Each of these on their own is small and together they do not amount to nearly enough, but we should acknowledge that they exist. > > Thanks, > Alissa > > [1] https://mailarchive.ietf.org/arch/msg/gendispatch/iHDh7KBVRvGB2EWKYYh11LjP95E/ > >> On Feb 11, 2021, at 3:39 PM, Sean Turner <sean@sn3rd.com> wrote: >> >> Hi!, >> >> Here is some proposed charter text to address the terminology-related WG. >> >> Cheers, >> spt >> >> ---------- >> >> Effective Terminology in IETF Documents (TERM) >> ---- >> >> The mission of the IETF as specified in BCP 95 is to produce high quality, relevant technical documents that influence the way people design, use, and manage the Internet. As RFC 7322 explains, "The ultimate goal of the RFC publication process is to produce documents that are readable, clear, consistent, and reasonably uniform." RFCs and Internet-drafts are most effective when they use terminology that is clear, precise, and widely accessible to readers from varying backgrounds and cultures. >> >> In the years leading up to the chartering of this working group, there has been discussion in the IETF, in other standards organizations, and in the technology industry about the use of certain terms (such as “master/slave” and “blacklist/whitelist”) in technical documentation and whether those and other terms have effects on inclusivity. While opinions vary among IETF participants about this topic, there is general agreement that the IETF community would benefit from informational recommendations about using effective and inclusive terminology in IETF documents. >> >> The TERM working group is therefore chartered to produce an Informational RFC containing recommendations on terminology to use in technical work produced by the IETF. >> >> Milestones: >> >> July 2021: Adopt draft providing informational terminology recommendations >> -- >> Gendispatch mailing list >> Gendispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/gendispatch > > -- > Gendispatch mailing list > Gendispatch@ietf.org > https://www.ietf.org/mailman/listinfo/gendispatch
- [Gendispatch] draft charter text: terminology-rel… Sean Turner
- Re: [Gendispatch] draft charter text: terminology… Eric Rescorla
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Stephen Farrell
- Re: [Gendispatch] draft charter text: terminology… Salz, Rich
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Bron Gondwana
- Re: [Gendispatch] draft charter text: terminology… Stephen Farrell
- Re: [Gendispatch] draft charter text: terminology… Lars Eggert
- Re: [Gendispatch] draft charter text: terminology… Vittorio Bertola
- Re: [Gendispatch] draft charter text: terminology… Rodney W. Grimes
- Re: [Gendispatch] draft charter text: terminology… Mallory Knodel
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Brian E Carpenter
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… John Levine
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Stephen Farrell
- Re: [Gendispatch] draft charter text: terminology… Mallory Knodel
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… S Moonesamy
- Re: [Gendispatch] draft charter text: terminology… Vittorio Bertola
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Stephen Farrell
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Eliot Lear
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Mark Nottingham
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Joel M. Halpern
- Re: [Gendispatch] draft charter text: terminology… Mark Nottingham
- Re: [Gendispatch] draft charter text: terminology… Salz, Rich
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Eric Rescorla
- Re: [Gendispatch] draft charter text: terminology… Stephen Farrell
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Mark Nottingham
- Re: [Gendispatch] draft charter text: terminology… Christian Huitema
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Christian Huitema
- Re: [Gendispatch] draft charter text: terminology… John Levine
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Salz, Rich
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Christian Huitema
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Rodney W. Grimes
- Re: [Gendispatch] draft charter text: terminology… S Moonesamy
- Re: [Gendispatch] draft charter text: terminology… Bob Hinden
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Jay Daley
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Jay Daley
- Re: [Gendispatch] draft charter text: terminology… Brian E Carpenter
- Re: [Gendispatch] draft charter text: terminology… Brian E Carpenter
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Bron Gondwana
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Mark Nottingham
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… S Moonesamy
- Re: [Gendispatch] draft charter text: terminology… Eliot Lear
- Re: [Gendispatch] draft charter text: terminology… Rob Wilton (rwilton)
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Alissa Cooper
- Re: [Gendispatch] draft charter text: terminology… Livingood, Jason
- Re: [Gendispatch] draft charter text: terminology… Alissa Cooper
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Bob Hinden
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Alissa Cooper
- Re: [Gendispatch] draft charter text: terminology… Jay Daley
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Brian E Carpenter
- Re: [Gendispatch] draft charter text: terminology… S Moonesamy
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Salz, Rich
- Re: [Gendispatch] draft charter text: terminology… Martin Thomson
- Re: [Gendispatch] draft charter text: terminology… Brian E Carpenter
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Salz, Rich
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Jay Daley
- Re: [Gendispatch] draft charter text: terminology… Salz, Rich
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Jay Daley
- Re: [Gendispatch] draft charter text: terminology… Fernando Gont
- Re: [Gendispatch] draft charter text: terminology… Lars Eggert
- Re: [Gendispatch] draft charter text: terminology… Eliot Lear
- Re: [Gendispatch] draft charter text: terminology… Lars Eggert
- Re: [Gendispatch] draft charter text: terminology… Mallory Knodel
- Re: [Gendispatch] draft charter text: terminology… Salz, Rich
- Re: [Gendispatch] draft charter text: terminology… Eliot Lear
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Francesca Palombini
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Eric Rescorla
- Re: [Gendispatch] draft charter text: terminology… Francesca Palombini
- Re: [Gendispatch] draft charter text: terminology… Pete Resnick
- Re: [Gendispatch] draft charter text: terminology… Dan Harkins
- Re: [Gendispatch] draft charter text: terminology… Francesca Palombini
- Re: [Gendispatch] draft charter text: terminology… Pete Resnick
- Re: [Gendispatch] draft charter text: terminology… Lars Eggert
- Re: [Gendispatch] draft charter text: terminology… Eliot Lear
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Bron Gondwana
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Niels ten Oever
- Re: [Gendispatch] draft charter text: terminology… Niels ten Oever
- Re: [Gendispatch] draft charter text: terminology… Keith Moore
- Re: [Gendispatch] draft charter text: terminology… Niels ten Oever
- Re: [Gendispatch] draft charter text: terminology… Eliot Lear
- [Gendispatch] revised (was: Re: draft charter tex… Sean Turner
- Re: [Gendispatch] revised (was: Re: draft charter… Joel M. Halpern
- Re: [Gendispatch] revised (was: Re: draft charter… Eric Rescorla
- Re: [Gendispatch] revised (was: Re: draft charter… Mallory Knodel
- Re: [Gendispatch] revised (was: Re: draft charter… Salz, Rich
- Re: [Gendispatch] revised (was: Re: draft charter… Livingood, Jason
- Re: [Gendispatch] revised (was: Re: draft charter… Stephen Farrell
- Re: [Gendispatch] revised Brian E Carpenter
- Re: [Gendispatch] revised (was: Re: draft charter… Bill Woodcock
- Re: [Gendispatch] revised Fernando Gont
- Re: [Gendispatch] revised Keith Moore
- Re: [Gendispatch] revised (was: Re: draft charter… Bron Gondwana
- Re: [Gendispatch] revised Fernando Gont
- Re: [Gendispatch] revised Dan Harkins
- Re: [Gendispatch] revised Salz, Rich
- Re: [Gendispatch] revised (was: Re: draft charter… Bob Hinden
- Re: [Gendispatch] revised Dan Harkins
- Re: [Gendispatch] revised Keith Moore
- Re: [Gendispatch] revised Salz, Rich
- Re: [Gendispatch] revised Dan Harkins
- Re: [Gendispatch] revised Salz, Rich
- Re: [Gendispatch] revised (was: Re: draft charter… Niels ten Oever
- Re: [Gendispatch] revised Dan Harkins
- Re: [Gendispatch] revised Salz, Rich
- Re: [Gendispatch] revised Brian E Carpenter
- [Gendispatch] New List (Was: revised) Pete Resnick
- Re: [Gendispatch] revised Mallory Knodel
- Re: [Gendispatch] revised Dan Harkins
- Re: [Gendispatch] revised Mallory Knodel
- Re: [Gendispatch] revised Tony Rutkowski
- Re: [Gendispatch] revised Mallory Knodel
- Re: [Gendispatch] revised Pete Resnick
- Re: [Gendispatch] revised Dan Harkins
- Re: [Gendispatch] revised Nico Williams
- Re: [Gendispatch] revised Phillip Hallam-Baker
- Re: [Gendispatch] revised Salz, Rich
- Re: [Gendispatch] revised Nico Williams
- Re: [Gendispatch] revised STARK, BARBARA H
- Re: [Gendispatch] revised Nico Williams