From julien at trigofacile.com  Sat Apr 22 06:12:22 2017
From: julien at trigofacile.com (=?UTF-8?Q?Julien_=c3=89LIE?=)
Date: Sat, 22 Apr 2017 15:12:22 +0200
Subject: [NNTP] New RFC 8143 on Using TLS with NNTP
In-Reply-To: <20170422043754.97B4CB80E5A__43187.9896474586$1492835902$gmane$org@rfc-editor.org>
References: <20170422043754.97B4CB80E5A__43187.9896474586$1492835902$gmane$org@rfc-editor.org>
Message-ID: <1813db57-0fe3-ace7-2610-44b173e2630d@trigofacile.com>

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.