RFC 4643: Network News Transfer Protocol (NNTP) Extension for Authentication
In plain English — editorial summary, not part of the RFC
This document defines an extension to the Network News Transfer Protocol (NNTP) that allows a client to indicate an authentication mechanism to the server, to perform an authentication protocol exchange, and optionally to negotiate a security layer for subsequent protocol interactions during the remainder of an NNTP session. This document updates and formalizes the AUTHINFO USER/PASS authentication method specified in RFC 2980 and deprecates the AUTHINFO SIMPLE and AUTHINFO GENERIC authentication methods. Additionally, this document defines a profile of the Simple Authentication and Security Layer (SASL) for NNTP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4643
- Published
- October 2006
- Authors
- J. Vinocur; K. Murchison
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 24
- Also known as
- —
- Updates:
- RFC 2980
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4013SASLprep: Stringprep Profile for User Names and PasswordsObsoleted
March 2005
- RFC 5803Lightweight Directory Access Protocol (LDAP) Schema for Storing Salted Challenge Response Authentication Mechanism (SCRAM) SecretsCurrent
July 2010
- RFC 2831Using Digest Authentication as a SASL MechanismObsoleted
May 2000
- RFC 4752The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) MechanismCurrent
November 2006
- RFC 4422Simple Authentication and Security Layer (SASL)Current
June 2006
- RFC 4954SMTP Service Extension for AuthenticationUpdated
July 2007
- RFC 5802Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API MechanismsUpdated
July 2010
- RFC 7804Salted Challenge Response HTTP Authentication MechanismCurrent
March 2016
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?