draft-ietf-eai-rfc5721bis-05.txt   draft-ietf-eai-rfc5721bis-06.txt 
Network Working Group R. Gellens Network Working Group R. Gellens
Internet-Draft QUALCOMM Incorporated Internet-Draft QUALCOMM Incorporated
Obsoletes: 5721 (if approved) C. Newman Obsoletes: 5721 (if approved) C. Newman
Intended status: Standards Track Oracle Intended status: Standards Track Oracle
Expires: December 14, 2012 J. Yao Expires: January 17, 2013 J. Yao
CNNIC CNNIC
K. Fujiwara K. Fujiwara
JPRS JPRS
June 12, 2012 July 16, 2012
POP3 Support for UTF-8 POP3 Support for UTF-8
draft-ietf-eai-rfc5721bis-05.txt draft-ietf-eai-rfc5721bis-06.txt
Abstract Abstract
This specification extends the Post Office Protocol version 3 (POP3) This specification extends the Post Office Protocol version 3 (POP3)
to support un-encoded international characters in user names, to support un-encoded international characters in user names,
passwords, mail addresses, message headers, and protocol-level passwords, mail addresses, message headers, and protocol-level
textual strings. textual strings.
Status of This Memo Status of This Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 14, 2012. This Internet-Draft will expire on January 17, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 8, line 27 skipping to change at page 8, line 27
UTF8 command. (Because this is a protocol error as opposed to a UTF8 command. (Because this is a protocol error as opposed to a
failure based on conditions, an extended response code [RFC2449] is failure based on conditions, an extended response code [RFC2449] is
not specified.) not specified.)
3.2. USER Argument to UTF8 Capability 3.2. USER Argument to UTF8 Capability
If the USER argument is included with this capability, it indicates If the USER argument is included with this capability, it indicates
that the server accepts UTF-8 user names and passwords. that the server accepts UTF-8 user names and passwords.
Servers that include the USER argument in the UTF8 capability Servers that include the USER argument in the UTF8 capability
response SHOULD apply SASLprep [RFC4013] to the arguments of the USER response SHOULD apply SASLprep [RFC4013] or one of its standards-
and PASS commands. track successors to the arguments of the USER and PASS commands.
A client or server that supports APOP and permits UTF-8 in user names A client or server that supports APOP and permits UTF-8 in user names
or passwords MUST apply SASLprep [RFC4013] to the user name and or passwords MUST apply SASLprep [RFC4013] or one of its standards-
password used to compute the APOP digest. track successors to the user name and password used to compute the
APOP digest.
When applying SASLprep [RFC4013], servers MUST reject UTF-8 user When applying SASLprep [RFC4013], servers MUST reject UTF-8 user
names or passwords that contain a Unicode character listed in Section names or passwords that contain a Unicode character listed in Section
2.3 of SASLprep [RFC4013]. When applying SASLprep to the USER 2.3 of SASLprep [RFC4013]. When applying SASLprep to the USER
argument, the PASS argument, or the APOP username argument, a argument, the PASS argument, or the APOP username argument, a
compliant server or client MUST treat them as a query string compliant server or client MUST treat them as a query string
[RFC3454](i.e., unassigned Unicode code points are allowed). When [RFC3454](i.e., unassigned Unicode code points are allowed). When
applying SASLprep to the APOP password argument, a compliant server applying SASLprep to the APOP password argument, a compliant server
or client MUST treat them as a stored string [RFC3454] (i.e., or client MUST treat them as a stored string [RFC3454] (i.e.,
unassigned Unicode code points are prohibited). unassigned Unicode code points are prohibited).
 End of changes. 6 change blocks. 
8 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/