From delivering@dario2o.bid Sat Nov 26 04:33:14 2016 Return-Path: X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6175B129635 for ; Sat, 26 Nov 2016 04:33:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.361 X-Spam-Level: *** X-Spam-Status: No, score=3.361 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_SBL_CSS=3.335, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=no 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 OLuG3NY7si7q for ; Sat, 26 Nov 2016 04:33:11 -0800 (PST) Received: from glas.dario2o.bid (glas.dario2o.bid [206.221.184.150]) by ietfa.amsl.com (Postfix) with SMTP id C33E31295B5 for ; Sat, 26 Nov 2016 04:33:10 -0800 (PST) Date: Sat, 26 Nov 2016 06:30:55 -0600 From: "honorabilities" To: Subject: news Message-Id: <201611260630_178983699d44e13f68e390b@dario2o.bid> MIME-Version: 1.0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org Mon Nov 28 13:27:33 2016 Return-Path: X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69024129FC8 for ; Mon, 28 Nov 2016 13:27:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.896 X-Spam-Level: X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-1.497] 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 3_MT8In6F89A for ; Mon, 28 Nov 2016 13:27:31 -0800 (PST) Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAF25129A7A for ; Mon, 28 Nov 2016 13:27:31 -0800 (PST) Received: from hope.eyrie.org (localhost [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 93B7768516 for ; Mon, 28 Nov 2016 13:27:30 -0800 (PST) X-Original-To: ietf-nntp@lists.eyrie.org Delivered-To: ietf-nntp@lists.eyrie.org Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by hope.eyrie.org (Postfix) with ESMTPS id 6E43468267 for ; Mon, 28 Nov 2016 13:27:28 -0800 (PST) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d02 with ME id DZTR1u00V17Lgi403ZTSHm; Mon, 28 Nov 2016 22:27:27 +0100 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Mon, 28 Nov 2016 22:27:27 +0100 X-ME-IP: 92.170.5.52 X-Mozilla-News-Host: news://news.gmane.org:119 To: ietf-nntp@lists.eyrie.org From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: Date: Mon, 28 Nov 2016 22:27:25 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: [NNTP] NNTP COMPRESS extension X-BeenThere: ietf-nntp@lists.eyrie.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: NNTP protocol discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org Sender: "ietf-nntp" Hi all, Just to tell you that the NNTP COMPRESS extension has been accepted to be published on the standards track. We're waiting for the RFC Editor to update its tools to handle UTF-8 in names (Acknowledgments Section) and addresses. It will happen in a few weeks/months, and will permit to remove Section 1.3 of the document. We accepted the delay in publishing the document, as we're not in a hurry anyway to publish the RFC. News clients and servers wishing to implement the NNTP COMPRESS extension can go ahead with the following document: https://www.ietf.org/id/draft-murchison-nntp-compress-06.txt It will be the one that will be published (modulo minor editorial changes that may happen during the final stage of the publication). Latest versions of INN, flnews and Cyrus NNTP are already implementing COMPRESS. Thanks again to all who reviewed it. -- Julien Ã‰LIE Â« â€“ Je me sens un peu rouillÃ© ! C'est sÃ»rement Ã cause des pluies provoquÃ©es par Assurancetourix ! â€“ En attendant c'est nous qui dÃ©rouillons ! Â» (AstÃ©rix) From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org Mon Nov 28 13:28:07 2016 Return-Path: X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DAAE129A7A for ; Mon, 28 Nov 2016 13:28:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.896 X-Spam-Level: X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-1.497] 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 E3n-gDHMTCgE for ; Mon, 28 Nov 2016 13:28:04 -0800 (PST) Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4D87129FC9 for ; Mon, 28 Nov 2016 13:28:04 -0800 (PST) Received: from hope.eyrie.org (localhost [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 40FF868516 for ; Mon, 28 Nov 2016 13:28:04 -0800 (PST) X-Original-To: ietf-nntp@lists.eyrie.org Delivered-To: ietf-nntp@lists.eyrie.org Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by hope.eyrie.org (Postfix) with ESMTPS id 8EBD268267 for ; Mon, 28 Nov 2016 13:28:02 -0800 (PST) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d02 with ME id DZU11u00P17Lgi403ZU1Kq; Mon, 28 Nov 2016 22:28:01 +0100 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Mon, 28 Nov 2016 22:28:01 +0100 X-ME-IP: 92.170.5.52 References: <148035153084.5510.13278742493736503746.idtracker@ietfa.amsl.com> To: ietf-nntp@lists.eyrie.org From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ X-Forwarded-Message-Id: <148035153084.5510.13278742493736503746.idtracker@ietfa.amsl.com> Message-ID: <81e67a36-c913-c9b5-b613-51c7f184eab6@trigofacile.com> Date: Mon, 28 Nov 2016 22:28:01 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: <148035153084.5510.13278742493736503746.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Subject: [NNTP] =?utf-8?q?Fwd=3A_Last_Call=3A_=3Cdraft-elie-nntp-tls-recom?= =?utf-8?q?mendations-01=2Etxt=3E_=28Use_of_Transport_Layer_Security_=28TL?= =?utf-8?b?UykgaW7CoHRoZcKgTmV0d29ya8KgTmV3c8KgVHJhbnNmZXLCoFByb3RvY29s?= =?utf-8?q?_=28NNTP=29=29_to_Proposed_Standard?= X-BeenThere: ietf-nntp@lists.eyrie.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: NNTP protocol discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org Sender: "ietf-nntp" Hi all, An update to RFC 4642 (use of TLS with NNTP) is currently in IETF Last Call. You can see the current document here: https://tools.ietf.org/html/draft-elie-nntp-tls-recommendations-01 In case you have any comments, please tell me. Thanks beforehand for your review. -- Julien ÉLIE « Ça n'a été qu'un coup de glaive dans l'eau. » (Astérix) -------- Message transféré -------- Sujet : Last Call: (Use of Transport Layer Security (TLS) in the Network News Transfer Protocol (NNTP)) to Proposed Standard Date : Mon, 28 Nov 2016 08:45:30 -0800 De : The IESG Pour : IETF-Announce The IESG has received a request from an individual submitter to consider the following document: - 'Use of Transport Layer Security (TLS) in the Network News Transfer Protocol (NNTP)' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2016-12-26. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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. If approved, this document updates RFC 4642. The file can be obtained via https://datatracker.ietf.org/doc/draft-elie-nntp-tls-recommendations/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-elie-nntp-tls-recommendations/ballot/ No IPR declarations have been submitted directly on this I-D. From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org Mon Nov 28 13:44:06 2016 Return-Path: X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F7C129F77 for ; Mon, 28 Nov 2016 13:44:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.896 X-Spam-Level: X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-1.497] 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 qAg6jFoIEZGG for ; Mon, 28 Nov 2016 13:44:05 -0800 (PST) Received: from hope.eyrie.org (hope.eyrie.org [166.84.7.155]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9566012945D for ; Mon, 28 Nov 2016 13:44:05 -0800 (PST) Received: from hope.eyrie.org (localhost [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id E547B68516 for ; Mon, 28 Nov 2016 13:44:04 -0800 (PST) X-Original-To: ietf-nntp@lists.eyrie.org Delivered-To: ietf-nntp@lists.eyrie.org Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by hope.eyrie.org (Postfix) with ESMTPS id 0BF3C68267 for ; Mon, 28 Nov 2016 13:44:02 -0800 (PST) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d02 with ME id DZk11u00S17Lgi403Zk2T7; Mon, 28 Nov 2016 22:44:02 +0100 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Mon, 28 Nov 2016 22:44:02 +0100 X-ME-IP: 92.170.5.52 To: ietf-nntp@lists.eyrie.org References: <148035153084.5510.13278742493736503746.idtracker@ietfa.amsl.com> <81e67a36-c913-c9b5-b613-51c7f184eab6@trigofacile.com> From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <6fd124c5-6c1c-38b0-76a9-635bc96e2d1c@trigofacile.com> Date: Mon, 28 Nov 2016 22:44:01 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: <81e67a36-c913-c9b5-b613-51c7f184eab6@trigofacile.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [NNTP] =?utf-8?q?Fwd=3A_Last_Call=3A_=3Cdraft-elie-nntp-tls-recom?= =?utf-8?q?mendations-01=2Etxt=3E_=28Use_of_Transport_Layer_Security_=28TL?= =?utf-8?b?UykgaW7CoHRoZcKgTmV0d29ya8KgTmV3c8KgVHJhbnNmZXLCoFByb3RvY29s?= =?utf-8?q?_=28NNTP=29=29_to_Proposed_Standard?= X-BeenThere: ietf-nntp@lists.eyrie.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: NNTP protocol discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org Sender: "ietf-nntp" Hi all, > An update to RFC 4642 (use of TLS with NNTP) is currently in IETF Last > Call. > You can see the current document here: > https://tools.ietf.org/html/draft-elie-nntp-tls-recommendations-01 Does anyone have an opinion about the third issue in Appendix E? Basically, news servers use either port 119 (NNTP) or port 433 (NNSP); news clients use either port 119 (NNTP) or 563 (NNTP/TLS). The use of 119/433 ports is described in Sections 3.4.1 and 3.4.2 of RFC 3977: The official TCP port for the NNTP service is 119. However, if a host wishes to offer separate servers for transit and reading clients, port 433 SHOULD be used for the transit server and 119 for the reading server. As strict TLS over a dedicated port is the current TLS best practice to use, what should we do for transit servers? We currently have no NNSP/TLS port. Do you believe we should ask to register a new port NNSP/TLS? Otherwise, what should we recommend? (My fear is that adoption and use of that new port by news servers will be slow, or even will never be happening...) -- Julien ÉLIE « Love is blind but marriage is an eye-opener. » From ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org Tue Nov 29 03:57:22 2016 Return-Path: X-Original-To: ietfarch-nntpext-archive@ietfa.amsl.com Delivered-To: ietfarch-nntpext-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96881299BF for ; Tue, 29 Nov 2016 03:57:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.286 X-Spam-Level: X-Spam-Status: No, score=-3.286 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RP_MATCHES_RCVD=-1.497, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=me.com 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 kxvJEZQwy55c for ; Tue, 29 Nov 2016 03:57:21 -0800 (PST) Received: from hope.eyrie.org (hope.eyrie.org [IPv6:2001:470:30:84:e276:63ff:fe62:3535]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0EBF129AEC for ; Tue, 29 Nov 2016 03:52:27 -0800 (PST) Received: from hope.eyrie.org (localhost [IPv6:::1]) by hope.eyrie.org (Postfix) with ESMTP id 72BCE68516 for ; Tue, 29 Nov 2016 03:52:26 -0800 (PST) X-Original-To: ietf-nntp@lists.eyrie.org Delivered-To: ietf-nntp@lists.eyrie.org Received: from pv33p04im-asmtp001.me.com (pv33p04im-asmtp001.me.com [17.143.181.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by hope.eyrie.org (Postfix) with ESMTPS id 0B61968267 for ; Tue, 29 Nov 2016 03:52:24 -0800 (PST) Received: from process-dkim-sign-daemon.pv33p04im-asmtp001.me.com by pv33p04im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OHE00F00JN04O00@pv33p04im-asmtp001.me.com> for ietf-nntp@lists.eyrie.org; Tue, 29 Nov 2016 11:52:23 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1480420343; bh=LnQ68HeERleHrUEeb4irSLrJlbZKtxvODPxiJqRc3vA=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=EZa1Z0/2WDkdhtDy4syjsecVB3LskuoNtdMnh/1VqIB/6QtntBLTTEQ/ZLIOpcyDh LjNoaQkAO07XZ3a7GZZGAjUQ8jElYnVprOqAm01kgpu/e3lHUSbJv2Fp30e9jG6vYB Nr8kavld2WWNwriXgzw416YjOuU0f+CXIfjUck8/HeppwhcHA0UsBOIg9/HIeGCur+ qt1Mgjtl9D6RO2/xh8KraIfEyvX6p9w9e/NQPhXdEd28yokxmL6X5+HqnrB9iQqN84 r03NLR222RWdKhK+hvg4qck44EhAJIf2tR9wUMKAzeGwvTV5DMTHQOLMdAqJlJKtOt /NfNbw76Kg2jQ== Received: from [172.16.16.155] (unknown [90.155.50.12]) by pv33p04im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OHE00FGZJN8V840@pv33p04im-asmtp001.me.com>; Tue, 29 Nov 2016 11:52:23 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-11-29_01:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1611290202 Content-type: text/plain; charset=windows-1252 MIME-version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: Sabahattin Gucukoglu In-reply-to: <6fd124c5-6c1c-38b0-76a9-635bc96e2d1c@trigofacile.com> Date: Tue, 29 Nov 2016 11:52:19 +0000 Content-transfer-encoding: quoted-printable Message-id: References: <148035153084.5510.13278742493736503746.idtracker@ietfa.amsl.com> <81e67a36-c913-c9b5-b613-51c7f184eab6@trigofacile.com> <6fd124c5-6c1c-38b0-76a9-635bc96e2d1c@trigofacile.com> To: =?windows-1252?Q?Julien_=C9LIE?= X-Mailer: Apple Mail (2.2104) Cc: ietf-nntp@lists.eyrie.org Subject: Re: [NNTP] =?windows-1252?q?Last_Call=3A_=3Cdraft-elie-nntp-tls-recom?= =?windows-1252?q?mendations-01=2Etxt=3E_=28Use_of_Transport_Layer_Securit?= =?windows-1252?q?y_=28TLS=29_in=A0the=A0Network=A0News=A0Transfer=A0Proto?= =?windows-1252?q?col_=28NNTP=29=29_to_Proposed_Standard?= X-BeenThere: ietf-nntp@lists.eyrie.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: NNTP protocol discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ietf-nntp-bounces+nntpext-archive=ietf.org@lists.eyrie.org Sender: "ietf-nntp" On 28 Nov 2016, at 21:44, Julien =C9LIE wrote: > As strict TLS over a dedicated port is the current TLS best practice = to use, what should we do for transit servers? We currently have no = NNSP/TLS port. Do you believe we should ask to register a new port = NNSP/TLS? > Otherwise, what should we recommend? (My fear is that adoption and = use of that new port by news servers will be slow, or even will never be = happening...) Not for me to argue with the wisdom of the crowd, I'm sure, but I've = never liked the idea of going back to TLS "wrapper" ports; it just = wastes precious IANA resources for absolutely no reason whatsoever and, = as you just highlighted, is in any event unlikely to make a meaningful = impact in practice. Maybe you could compromise; describe the use of the secure port, give it = a name, but then only register that port when implementers go looking = for it. Downside is that the RFC cannot specify a fixed port number.=