[rfc-dist] RFC 8404 on Effects of Pervasive Encryption on Operators

rfc-editor@rfc-editor.org Tue, 24 July 2018 22:46 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72E1E131227 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 24 Jul 2018 15:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 PCGep2u5x7fG for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 24 Jul 2018 15:46:34 -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 6A13C13124B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 24 Jul 2018 15:46:26 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 853A8B8164F; Tue, 24 Jul 2018 15:45:57 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0A337B8164C; Tue, 24 Jul 2018 15:45:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180724224556.0A337B8164C@rfc-editor.org>
Date: Tue, 24 Jul 2018 15:45:56 -0700
Subject: [rfc-dist] RFC 8404 on Effects of Pervasive Encryption on Operators
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8404

        Title:      Effects of Pervasive Encryption on 
                    Operators 
        Author:     K. Moriarty, Ed.,
                    A. Morton, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       July 2018
        Mailbox:    Kathleen.Moriarty@dell.com, 
                    acmorton@att.com
        Pages:      53
        Characters: 143895
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-mm-wg-effect-encrypt-25.txt

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

        DOI:        10.17487/RFC8404

Pervasive monitoring attacks on the privacy of Internet users are of
serious concern to both user and operator communities.  RFC 7258
discusses the critical need to protect users' privacy when developing
IETF specifications and also recognizes that making networks
unmanageable to mitigate pervasive monitoring is not an acceptable
outcome: an appropriate balance is needed.  This document discusses
current security and network operations as well as management
practices that may be impacted by the shift to increased use of
encryption to help guide protocol development in support of
manageable and secure networks.


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 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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org