BCP 25, RFC 7776 on IETF Anti-Harassment Procedures

rfc-editor@rfc-editor.org Thu, 03 March 2016 20:02 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B421B42A0 for <ietf-announce@ietfa.amsl.com>; Thu, 3 Mar 2016 12:02:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.908
X-Spam-Level:
X-Spam-Status: No, score=-106.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 vWisIh3ioVYw for <ietf-announce@ietfa.amsl.com>; Thu, 3 Mar 2016 12:02:06 -0800 (PST)
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 9E7041B424D for <ietf-announce@ietf.org>; Thu, 3 Mar 2016 12:01:49 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AA43F18000B; Thu, 3 Mar 2016 12:00:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 25, RFC 7776 on IETF Anti-Harassment Procedures
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160303200049.AA43F18000B@rfc-editor.org>
Date: Thu, 03 Mar 2016 12:00:49 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/9rPUrKXvqET0eGPICG0BcTQn3vo>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: Thu, 03 Mar 2016 20:02:08 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 25        
        RFC 7776

        Title:      IETF Anti-Harassment Procedures 
        Author:     P. Resnick,
                    A. Farrel
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2016
        Mailbox:    presnick@qti.qualcomm.com, 
                    adrian@olddog.co.uk
        Pages:      18
        Characters: 42853
        Updates:    RFC 2418, RFC 7437
        See Also:   BCP 25

        I-D Tag:    draft-farrresnickel-harassment-10.txt

        URL:        https://www.rfc-editor.org/info/rfc7776

        DOI:        http://dx.doi.org/10.17487/RFC7776

IETF Participants must not engage in harassment while at IETF
meetings, virtual meetings, or social events or while participating
in mailing lists.  This document lays out procedures for managing and
enforcing this policy.

This document updates RFC 2418 by defining new working group
guidelines and procedures.  This document updates RFC 7437 by
allowing the Ombudsteam to form a recall petition without further
signatories.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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