RFC 4642: Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)
In plain English — editorial summary, not part of the RFC
This memo defines an extension to the Network News Transfer Protocol (NNTP) that allows an NNTP client and server to use Transport Layer Security (TLS). The primary goal is to provide encryption for single-link confidentiality purposes, but data integrity, (optional) certificate-based peer entity authentication, and (optional) data compression are also possible. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4642
- Published
- October 2006
- Authors
- K. Murchison; J. Vinocur; C. Newman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2617HTTP Authentication: Basic and Digest Access AuthenticationObsoleted
June 1999
- RFC 4752The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) MechanismCurrent
November 2006
- RFC 4491Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL ProfileCurrent
May 2006
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 4822RIPv2 Cryptographic AuthenticationCurrent
February 2007
- RFC 4422Simple Authentication and Security Layer (SASL)Current
June 2006
- RFC 4253The Secure Shell (SSH) Transport Layer ProtocolUpdated
January 2006
- RFC 4211Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)Updated
September 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?