IETF Logo Mail Archive

Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs

Allison Mankin <allison.mankin@gmail.com> Fri, 21 September 2018 02:38 UTC

Return-Path: <allison.mankin@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 B529F1271FF; Thu, 20 Sep 2018 19:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 d9TdtvFwzahj; Thu, 20 Sep 2018 19:38:32 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 423F0124D68; Thu, 20 Sep 2018 19:38:32 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id j26-v6so5255543pfi.10; Thu, 20 Sep 2018 19:38:32 -0700 (PDT)
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=hdP5e86exHia5JYnea3PL0Ps5hKUG2Dv9JTmn3545OU=; b=ghmKqqIsNdOvbeywFmdBHRFuvyHrCNn3HeHpB+dxJllUYkchuKNd0Pxw4nXvpwH5Ub gQ5gU4DAtEHduMiigmS0P3fSHZJzzV4VKfYP6SVWiFO1daXcPWhvjD1/EMVdTUukme7E cP+eGDhqB4rrzKPAdaESCUPGNO1ruFljEINbhzoY7QeCoZl6aiBM2zOd60c/fQM3V3pn 4FMB5/pKpAlbs16ekhLMUMpAeD6+BdU7wqumX8C7p8OxDrWieiu9qbm7e5swC8ou6BXL Xi5US2vYNr6CO5wgsG8xclsOw9+d493Oh5lqkZP2zmKNE1t5hkh6XdOuuKh5aWTCWf5o evNg==
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=hdP5e86exHia5JYnea3PL0Ps5hKUG2Dv9JTmn3545OU=; b=eri1V/JvOhPWxEgc8vrhwvemZyS9ZcZQinwq9ZpA4FRQTzNtp9mAxyGn5+YDXP1P2n k1G0f/VPAHBlPFlzBbHGgap+TDB/H98s89Ltc9K9EzZASNFwavCRAS94iQbESdXwUd3W D2xVFAqIh3e8FRxsBkKoOR4w+QyTnPpMOBatzyJYuyJFC0ZJX3ST4oGELsVE8vRNcSBh NQT8UsF8QbXm3FHjyBAogk/E1p2ayPM027aUNF3aNQujEi91wCOr6V3kXSs5S/dRtv76 Hqay+eFkFCUlyvPTInnanpiv2eMiFqoId1rRzZsjtr3EQbOzhJC38kOyXEdOeaEBEtrp nVWg==
X-Gm-Message-State: APzg51Ayso3xivDrv0Z4xmQzFtCydMiqN9AF8LTQrHZzyDh25Oi9ZVkd eKD5I+oAaEiweCZ/CNIQpet6JaypJH2yYxaV3aw=
X-Google-Smtp-Source: ANB0VdZ7r3OVB20L3vY43ABy8v7Xn5mN3M6s75l/NeAWNMc4RyhsD5YXDHKxLD76UFISbpPJMYkJDkJfjgJe36rK2Kw=
X-Received: by 2002:a63:b207:: with SMTP id x7-v6mr39984493pge.401.1537497511614; Thu, 20 Sep 2018 19:38:31 -0700 (PDT)
MIME-Version: 1.0
References: <20180920233440.238CA20051DDE5@ary.qy> <5BA45326.8070707@signal100.com> <564477a2-80c0-acfd-a21d-1f4bdb5a7363@gmail.com>
In-Reply-To: <564477a2-80c0-acfd-a21d-1f4bdb5a7363@gmail.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Thu, 20 Sep 2018 22:38:29 -0400
Message-ID: <CAP8yD=tMyta0dkupfSzpDHqmHcmi0nT58jQee1V5pvoBXae28g@mail.gmail.com>
Subject: Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs
To: Melinda Shore <melinda.shore@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>, hrpc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000005df140576588907"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-0NQMbUZquZqAtQdJHIHKjcQ5PI>
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: Fri, 21 Sep 2018 02:38:35 -0000

Thanks for sharing the draft list, Melinda.  I'm also adding the chairs in
case they want to chime in.  There
is some work in planning that hasn't been drafted yet.

I think that people should not consider this discussion on IETF discuss as
a representation of the group.
I support the general discussion, but the HRPC work is extensive, and
there's no good reason to discuss it
at length outside of its own mailing list (subscription link:
https://www.irtf.org/mailman/listinfo/hrpc)

Finally, if anyone wants to start drafts on Human Rights articles not
already tackled, that door is open.

Allison

On Thu, 20 Sep 2018 at 22:30, Melinda Shore <melinda.shore@gmail.com> wrote:

> On 9/20/18 6:10 PM, Mark Rousell wrote:
> > On 21/09/2018 00:34, John Levine wrote:
> >> There are real human rights problems that HRPC could engage with, but
> >> don't.  They need to make up their mind whether they're serious.
> > Well said.
>
> Here's the current list of drafts, plus some contributions
> that haven't been adopted by the RG:
> https://datatracker.ietf.org/rg/hrpc/documents/
>
> Melinda
>
>

v2.23.0 | Report a Bug | By Email