RFC 8280 on Research into Human Rights Protocol Considerations
rfc-editor@rfc-editor.org Wed, 01 November 2017 04:55 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 762D013FB8B for <ietf-announce@ietfa.amsl.com>; Tue, 31 Oct 2017 21:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 vod1Pp6bW-Zm for <ietf-announce@ietfa.amsl.com>; Tue, 31 Oct 2017 21:55:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CD0013FB7C for <ietf-announce@ietf.org>; Tue, 31 Oct 2017 21:54:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BE000B81745; Tue, 31 Oct 2017 21:54:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: RFC 8280 on Research into Human Rights Protocol Considerations
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, hrpc@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20171101045427.BE000B81745@rfc-editor.org>
Date: Tue, 31 Oct 2017 21:54:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/IP7c1KHOkEm2jafAqyC6XgbmxrQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Nov 2017 04:55:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8280
Title: Research into Human Rights Protocol
Considerations
Author: N. ten Oever,
C. Cath
Status: Informational
Stream: IRTF
Date: October 2017
Mailbox: mail@nielstenoever.net,
corinnecath@gmail.com
Pages: 81
Characters: 199050
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-irtf-hrpc-research-14.txt
URL: https://www.rfc-editor.org/info/rfc8280
DOI: 10.17487/RFC8280
This document aims to propose guidelines for human rights
considerations, similar to the work done on the guidelines for
privacy considerations (RFC 6973). The other parts of this document
explain the background of the guidelines and how they were developed.
This document is the first milestone in a longer-term research
effort. It has been reviewed by the Human Rights Protocol
Considerations (HRPC) Research Group and also by individuals from
outside the research group.
This document is a product of the Human Rights Protocol Considerations of the IRTF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
https://www.irtf.org/mailman/listinfo/irtf-announce
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC