[Uta] New RFC 8143 on Using TLS with NNTP

Julien ÉLIE <julien@trigofacile.com> Sat, 22 April 2017 13:12 UTC

Return-Path: <julien@trigofacile.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0C81294BE for <uta@ietfa.amsl.com>; Sat, 22 Apr 2017 06:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.535
X-Spam-Level:
X-Spam-Status: No, score=-3.535 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_SOFTFAIL=0.665] 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 pQHqBAAfcwsb for <uta@ietfa.amsl.com>; Sat, 22 Apr 2017 06:12:27 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp02.smtpout.orange.fr [80.12.242.124]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9890D1294AF for <uta@ietf.org>; Sat, 22 Apr 2017 06:12:25 -0700 (PDT)
Received: from mbpdejulienelie.home ([92.170.5.52]) by mwinf5d03 with ME id BRCN1v00q17Lgi403RCPAW; Sat, 22 Apr 2017 15:12:24 +0200
X-ME-Helo: mbpdejulienelie.home
X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg==
X-ME-Date: Sat, 22 Apr 2017 15:12:24 +0200
X-ME-IP: 92.170.5.52
References: <20170422043754.97B4CB80E5A__43187.9896474586$1492835902$gmane$org@rfc-editor.org>
To: ietf-nntp@lists.eyrie.org, uta@ietf.org
From: Julien ÉLIE <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
X-Forwarded-Message-Id: <20170422043754.97B4CB80E5A__43187.9896474586$1492835902$gmane$org@rfc-editor.org>
Message-ID: <1813db57-0fe3-ace7-2610-44b173e2630d@trigofacile.com>
Date: Sat, 22 Apr 2017 15:12:22 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170422043754.97B4CB80E5A__43187.9896474586$1492835902$gmane$org@rfc-editor.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/Rq4wdfp28jaCROhvJScmkzwwk6k>
Subject: [Uta] New RFC 8143 on Using TLS with NNTP
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 13:12:29 -0000

Hi all,

RFC 8143 has just been published.  It updates RFC 4642 notably
by modernizing the NNTP usage of TLS to be consistent with
TLS best current practices described in BCP 195 (RFC 7525).

  https://tools.ietf.org/html/rfc8143

Thanks to all involved, especially folks in UTA and (concluded)
NNTP working groups.

-- 
Julien ÉLIE



-------- Message transféré --------
Date : Fri, 21 Apr 2017 21:37:54 -0700 (PDT)

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
        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.