Protocol Action: The SYS and AUTH POP Response Codes to Proposed Standard
The IESG <iesg-secretary@ietf.org> Fri, 30 November 2001 15:42 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16469; Fri, 30 Nov 2001 10:42:31 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id KAA00507 for ietf-123-outbound.10@ietf.org; Fri, 30 Nov 2001 10:35:03 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id KAA00036 for <all-ietf@loki.ietf.org>; Fri, 30 Nov 2001 10:03:00 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14473; Fri, 30 Nov 2001 10:02:57 -0500 (EST)
Message-Id: <200111301502.KAA14473@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@isi.edu>
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: The SYS and AUTH POP Response Codes to Proposed Standard
Date: Fri, 30 Nov 2001 10:02:56 -0500
Sender: scoya@cnri.reston.va.us
The IESG has approved the Internet-Draft 'The SYS and AUTH POP Response Codes' <draft-gellens-pop-err-01.txt> as a Proposed Standard. This has been reviewed in the IETF but is not the product of an IETF Working Group. Technical Summary RFC 2449 [POP-EXT] defined extended [POP3] response codes, to give clients more information about errors so clients can respond more appropriately. This memo proposes two additional response codes: SYS and AUTH, which enable clients to unambiguously determine an optimal response to an authentication failure. It also defines a new capability, AUTH-RESP-CODE, whose presence assures the client that only errors with the AUTH code are caused by credential problems. Working Group Summary This document was reviewed on the IETF POP3 Extensions mailing list, <ietf-pop3ext@imc.org>. However, it is an individual submission, not the product of a working group. Protocol Summary Ned Freed reviewed this document for the IESG. Note to RFC Editor: Section 3 "Comments" should be removed prior to publication. The text in the Security Considerations section should reference section 6, not section 3.