UpdatedPROPOSED STANDARDIETF stream

RFC 4642: Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)

Still current, but amended. Parts of this document are changed or extended by RFC 8143, RFC 8996. Read both.

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
Updated by:
RFC 8143, RFC 8996

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.

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?

canonical URL: /rfc/4642-using-transport-layer-security-tls-with-network-news-transfer-protocol-nntp