RFC 3206: The SYS and AUTH POP Response Codes
In plain English — editorial summary, not part of the RFC
This memo proposes two response codes: SYS and AUTH, which enable clients to unambiguously determine an optimal response to an authentication failure. In addition, a new capability (AUTH-RESP-CODE) is defined. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3206
- Published
- February 2002
- Authors
- R. Gellens
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2808The SecurID(r) SASL MechanismCurrent
April 2000
- RFC 3129Requirements for Kerberized Internet Negotiation of KeysCurrent
June 2001
- RFC 3007Secure Domain Name System (DNS) Dynamic UpdateCurrent
November 2000
- RFC 3610Counter with CBC-MAC (CCM)Current
September 2003
- RFC 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent
November 2003
- RFC 2725Routing Policy System SecurityUpdated
December 1999
- RFC 3833Threat Analysis of the Domain Name System (DNS)Current
August 2004
- RFC 2540Detached Domain Name System (DNS) InformationCurrent
March 1999
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?