RFC 8143 on Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)
rfc-editor@rfc-editor.org Sat, 22 April 2017 04:38 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 9610C129411 for <ietf-announce@ietfa.amsl.com>; Fri, 21 Apr 2017 21:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 BdWJo6yAkE2D for <ietf-announce@ietfa.amsl.com>; Fri, 21 Apr 2017 21:38:12 -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 0EB45128616 for <ietf-announce@ietf.org>; Fri, 21 Apr 2017 21:38:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 97B4CB80E5A; Fri, 21 Apr 2017 21:37:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8143 on Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)
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
Message-Id: <20170422043754.97B4CB80E5A@rfc-editor.org>
Date: Fri, 21 Apr 2017 21:37:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/QjISMQ_6nrcod6qgEfj7XOj-iUI>
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: Sat, 22 Apr 2017 04:38:13 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8143
Title: Using Transport Layer Security (TLS)
with Network News Transfer Protocol (NNTP)
Author: J. Elie
Status: Standards Track
Stream: IETF
Date: April 2017
Mailbox: julien@trigofacile.com
Pages: 13
Characters: 28484
Updates: RFC 4642
I-D Tag: draft-elie-nntp-tls-recommendations-05.txt
URL: https://www.rfc-editor.org/info/rfc8143
DOI: 10.17487/RFC8143
This document provides recommendations for improving the security of
the Network News Transfer Protocol (NNTP) when using Transport Layer
Security (TLS). It modernizes the NNTP usage of TLS to be consistent
with TLS best current practices. This document updates RFC 4642.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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