BCP 200, RFC 1984 on IAB and IESG Statement on Cryptographic Technology and the Internet

rfc-editor@rfc-editor.org Thu, 24 September 2015 19:30 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 D8FC91A87ED for <ietf-announce@ietfa.amsl.com>; Thu, 24 Sep 2015 12:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 yUct9GnuIGO8 for <ietf-announce@ietfa.amsl.com>; Thu, 24 Sep 2015 12:30:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id B71701A87EB for <ietf-announce@ietf.org>; Thu, 24 Sep 2015 12:30:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EE92A187E42; Thu, 24 Sep 2015 12:29:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 200, RFC 1984 on IAB and IESG Statement on Cryptographic Technology and the Internet
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150924192927.EE92A187E42@rfc-editor.org>
Date: Thu, 24 Sep 2015 12:29:27 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/7ZimfvlArCXPg4BLZ32mJP578Ow>
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, 24 Sep 2015 19:30:30 -0000

RFC 1984 been elevated to Best Current Practice (BCP).  

        BCP 200        
        RFC 1984

        Title:      IAB and IESG Statement on 
                    Cryptographic Technology and the Internet 
        Author:     IAB, IESG
        Status:     Best Current Practice
        Stream:     IETF
        Date:       August 1996
        Mailbox:    brian@dxcoms.cern.ch, fred@cisco.com
        Pages:      5
        Characters: 10738
        See Also:   BCP 200

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

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

The Internet Architecture Board (IAB) and the Internet Engineering Steering Group (IESG), the bodies which oversee architecture and standards for the Internet, are concerned by the need for increased protection of international commercial transactions on the Internet, and by the need to offer all Internet users an adequate degree of privacy. This memo provides information for the Internet community.  This memo does not specify an Internet standard of any kind.  


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/rfc.html

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