idnits 2.17.1 draft-gellens-pop-err-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3206 5 Title: The SYS and AUTH POP Response Codes 6 Author(s): R. Gellens 7 Status: Standards Track 8 Date: February 2002 9 Mailbox: randy@qualcomm.com 10 Pages: 6 11 Characters: 9917 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-gellens-pop-err-01.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3206.txt 18 This memo proposes two response codes: SYS and AUTH, which enable 19 clients to unambiguously determine an optimal response to an 20 authentication failure. In addition, a new capability 21 (AUTH-RESP-CODE) is defined. 23 This is now a Proposed Standard Protocol. 25 This document specifies an Internet standards track protocol for 26 the Internet community, and requests discussion and suggestions 27 for improvements. Please refer to the current edition of the 28 "Internet Official Protocol Standards" (STD 1) for the 29 standardization state and status of this protocol. Distribution 30 of this memo is unlimited. 32 This announcement is sent to the IETF list and the RFC-DIST list. 33 Requests to be added to or deleted from the IETF distribution list 34 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 35 added to or deleted from the RFC-DIST distribution list should 36 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 38 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 39 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 40 help: ways_to_get_rfcs. For example: 42 To: rfc-info@RFC-EDITOR.ORG 43 Subject: getting rfcs 45 help: ways_to_get_rfcs 47 Requests for special distribution should be addressed to either the 48 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 49 specifically noted otherwise on the RFC itself, all RFCs are for 50 unlimited distribution.echo 51 Submissions for Requests for Comments should be sent to 52 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 53 Authors, for further information.