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

Melinda Shore <melinda.shore@gmail.com> Fri, 21 September 2018 02:30 UTC

Return-Path: <melinda.shore@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 0D3D9130DF0 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 19:30:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 xwv2t3u5u3le for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2018 19:30:02 -0700 (PDT)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 20EFF128B14 for <ietf@ietf.org>; Thu, 20 Sep 2018 19:30:02 -0700 (PDT)
Received: by mail-pl1-x636.google.com with SMTP id b12-v6so5221472plr.8 for <ietf@ietf.org>; Thu, 20 Sep 2018 19:30:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=V7Cs3cFA1xc10h7We/N2sSdStTbdpq/HYj0ndJMUYcY=; b=Jfr6UAoA8obXSkQClxyRULnNZZghyQqKaWMhHkXiR8F/rKRFjoUJvYiPkSlAi5UoTV V3e+qSN09EH0xOV9SCFbnb1qH+diWDWfOs/GIhefw0s+9gOyYSmYTat4XZVkpX3sti1m OC7z4e52GIQFNlopRPYPrxwdoLgLIAvc24UDZr8QJkFGEawGkAhWCMvrBjnud6FUzp/R uzpvBBgu6rplwoKyW4/tm5GvhmPGF4xTZa3aXI6fxMPQD2Hbd4yPotI6mBM43zbYhzei WmM+c/Hoy2qvKsw085Q0/9gUuzXalhhat+aincWYX5WOt8Iqirk9j8oPOLCRx4g5Tt6/ aDuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=V7Cs3cFA1xc10h7We/N2sSdStTbdpq/HYj0ndJMUYcY=; b=dv3w+R2INiFrFc5dXRc9VtB9onIEELHr3STbDRWkdH9Oe8hsN7bEjNz/usZfjmBxjz EZ7o/DVhZgRcl+AGlpzgs1n4vlClwP2zZJsz4FCKJfrHOijfHgwsudDoTqEKwbEpyzyO pQVsvTDPTideA/TPMsX0KlBGtsROOizuCDrS/Pg9CHfLtJbG6YlR8trlCuB5vJxLrGg5 SlhmDWkZj7LjiYIwPuU9tLufl2tqxEkbW4jmfxy+AWwJRB1Z3WkmPzBQT23f8NUhpFQE CxSVezXyFaOmmjc7oSu8g8Rmv5ZJKXT6ZmRWa9LTM296fdkNzyZmF1Pycr/eCFqPUt91 pIVw==
X-Gm-Message-State: APzg51CXEPlAF9ydX7nD4aV5O/WBhh1C0BrrsAHLTzEMuOqUP7GRXjPV Z5bIt3995RLL7jmKLmJ+ZngpSwd1
X-Google-Smtp-Source: ANB0VdZPGEGzCOoMeLAzABM+B75CftR9IGvGGkInJ2SCKtd7IRQcrZXmDaeLXMqxHcRwHUn4nJCXFg==
X-Received: by 2002:a17:902:981:: with SMTP id 1-v6mr41699797pln.60.1537497001219; Thu, 20 Sep 2018 19:30:01 -0700 (PDT)
Received: from aspen.local ([63.140.88.205]) by smtp.gmail.com with ESMTPSA id h10-v6sm37706855pfj.78.2018.09.20.19.30.00 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Sep 2018 19:30:00 -0700 (PDT)
Subject: Re: why exactly is HRPC for, was Diversity and offensive terminology in RFCs
To: ietf@ietf.org
References: <20180920233440.238CA20051DDE5@ary.qy> <5BA45326.8070707@signal100.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <564477a2-80c0-acfd-a21d-1f4bdb5a7363@gmail.com>
Date: Thu, 20 Sep 2018 18:29:59 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <5BA45326.8070707@signal100.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_9SrYYrKCoqmsACJX_WuI1MoLB0>
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:30:04 -0000

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