Internet-Drafts | 8 Feb 2008 20:30
Picon
Favicon

I-D ACTION:draft-ietf-eai-utf8headers-09.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Email Address Internationalization Working Group of the IETF.

	Title		: Internationalized Email Headers
	Author(s)	: J. Yeh
	Filename	: draft-ietf-eai-utf8headers-09.txt
	Pages		: 16
	Date		: 2008-2-8
	
Full internationalization of electronic mail requires not only the capability to transmit non-ASCII
content, to encode selected
information in specific header fields, and to use non-ASCII
characters in envelope addresses.  It also requires being able to
express those addresses and information based on them in mail header
fields.  This document specifies an experimental variant of Internet
mail that permits the use of Unicode encoded in UTF-8, rather than
ASCII, as the base form for Internet email header field bodies.  This form is permitted in transmission only
if authorized by an SMTP
extension, as specified in an associated specification.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-utf8headers-09.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

(Continue reading)

Harald Tveit Alvestrand | 10 Feb 2008 04:32
Picon

EAI - Requested session has been scheduled for IETF 71 (fwd)

For your information.

------------ Forwarded Message ------------
Date: 9. februar 2008 01:27 -0800
From: IETF Secretariat <agenda <at> ietf.org>
To: harald <at> alvestrand.no
Cc: lee <at> cnnic.cn, chris.newman <at> sun.com, lisa <at> osafoundation.org, 
session-request <at> ietf.org
Subject: EAI - Requested session has been scheduled for IETF 71

Dear Harald Alvestrand,

The sessions that you have requested have been scheduled.
Below is the scheduled session information followed by
the information of sessions that you have requested.

EAI Session 1 (2 hours)
Thursday, Afternoon Session I 1300-1500
Room Name: Breakout Room
----------------------------------------------

Requested Information:

---------------------------------------------------------
Working Group Name: eai
Area Name: Applications Area
Session Requester: Harald Alvestrand

Number of Sessions: 1
Length of Session(s):  2 hours
(Continue reading)

Yao Jiankang | 13 Feb 2008 05:13
Picon

Re: draft-ietf-eai-smtpext-11


thanks a lot for your detail comments for refining this document.

I will try to update it in the next version.

YAO Jiankang

>From: Alfred HÎnes <ah <at> tr-sys.de>
>Reply-To: 
>To: yaojk <at> cnnic.cn, maowei_ietf <at> cnnic.cn
>Subject: draft-ietf-eai-smtpext-11
>Date:Tue, 12 Feb 2008 10:56:48 +0100 (MEZ)
>
>Hello,
> after studying the Internet-Draft authored/edited by you,
>                 draft-ietf-eai-smtpext-11,
> I'd like to submit a few comments, mostly addressing textual
> flaws I found in that memo, and suggesting further improvements.
> 
> The items below are presented in textual order.
> To give more context, sometimes I quote larger blocks of text
> literally and show the replacement proposed using the shorthand
> notation:
> 
>    <original draft text>
> ---
>    <modified text>
> 
> I use change bars ('|' in column 1) and occasionally
> up/down pointing marker lines ('^^^'/'vvv') to emphasize
(Continue reading)

Internet-Drafts | 14 Feb 2008 14:00
Picon
Favicon

I-D Action:draft-ietf-eai-downgrade-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email Address Internationalization Working Group of the IETF.

	Title           : Downgrading mechanism for Email Address Internationalization
	Author(s)       : Y. Yoneya, K. Fujiwara
	Filename        : draft-ietf-eai-downgrade-06.txt
	Pages           : 24
	Date            : 2008-02-14

Traditional mail systems handle only ASCII characters in SMTP
envelope and mail header fields.  The Email Address
Internationalization (UTF8SMTP) extension allows UTF-8 characters in
SMTP envelope and mail header fields.  To avoid bouncing
internationalized Email messages when a server in the delivery path
does not support the UTF8SMTP extension, some sort of converting
mechanism is required.  This document describes a downgrading
mechanism for Email Address Internationalization.  Note that this is
a way to downgrade, not tunnel.  There is no associated up-conversion
mechanism, although internationalized email clients might use
original internationalized addresses or other data when displaying or
replying to downgraded messages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-downgrade-06.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
(Continue reading)

fujiwara | 15 Feb 2008 09:45
Picon
Favicon

downgrade-06 and downgraded-display-00

I submitted two documents, draft-ietf-eai-downgrade-06 and
draft-fujiwara-eai-downgraded-display-00.

Appendix A of downgrade-05 document is moved to new document
draft-fujiwara-eai-downgraded-display-00.

Please comment them.

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Displaying Downgraded Messages for Email Address Internationalization
	Author(s)       : K. Fujiwara
	Filename        : draft-fujiwara-eai-downgraded-display-00.txt
	Pages           : 14
	Date            : 2008-02-14

This document describes how to display downgraded messages which
originally contain internationalized E-mail addresses or
internationalized header fields.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-fujiwara-eai-downgraded-display-00.txt

--
Kazunori Fujiwara, JPRS <fujiwara <at> jprs.co.jp>
Harald Tveit Alvestrand | 17 Feb 2008 06:12
Picon

Call for interop proposals (fwd)

this was mentioned in the Vancouver meeting as something EAI might want to 
participate in.

It may be too early still; while interoperability results are traditionally 
"we don't talk about other people's problems", I don't think it is 
realistic to keep secret who participates in such an event.

                   Harald

------------ Forwarded Message ------------
Date: 9. januar 2008 17:13 -0800
From: Lisa Dusseault <ldusseault <at> commerce.net>
To: Apps Discuss <discuss <at> apps.ietf.org>
Cc: Lisa Dusseault's Chairs <lisa-dusseault-chairs <at> tools.ietf.org>, 
chris-newman-chairs <at> tools.ietf.org
Subject: Call for interop proposals

At the Apps area open meeting in Vancouver, Chris & I mentioned the
possibility of doing a day of interoperability events at the next IETF
meeting.  This would replace a day of Apps area meetings during the normal
meeting hours and in the normal meeting location.  Ideally it would allow
people to come to the IETF for more than just "their" meeting (although we
have always hoped they can attend other WG meetings as well) and
participants may get more benefit and better justification for attending.

If we're going to do this, we need proposals: what topic  ( IDs, RFCs,
suites or functionality) will be tested.  I don't think interops will need
a lot of management but volunteer coordinators would be ideal.  Proposals
will need to be followed quickly by some indications of who will
participate.  WG scheduling is already open and we need to tell the
(Continue reading)

Internet-Drafts | 18 Feb 2008 14:00
Picon
Favicon

I-D Action:draft-ietf-eai-mailto-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Email Address Internationalization Working Group of the IETF.

	Title           : An update to the mailto URI scheme for Email Address Internationalization
	Author(s)       : M. Duerst
	Filename        : draft-ietf-eai-mailto-00.txt
	Pages           : 7
	Date            : 2008-02-18

This document updates the definition of the mailto: URI Scheme for
use with internationalized email addresses.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-mailto-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-eai-mailto-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

(Continue reading)

John C Klensin | 19 Feb 2008 01:48

Quick comments on draft-ietf-eai-mailto-00

Martin,

Some quick reactions...

(1) This is really ugly.  Perhaps nothing can be done about it,
but I think that is worth noting, especially since we have gone
out of our way to make
non-ASCII-string <at> non-ASCII-string.whatever.tld a value email
address.

(2) It might be a bit less ugly if you used only envelope
addresses (RFC2821-derived) rather than header (RFC2822-derived)
ones.  In particular, I really see little need to incorporate
name phrases in these strings and much less need to incorporate
comments.  See also (6) below.

(3) It is perhaps worth a comment that "?" is a valid character
in a local-part.  More %-encoding, I assume.  The first Note 1
in Section 2 doesn't go quite far enough in that regard, even
though the requirement for surrounding "<" and ">" might
eliminate the parsing problem for i18n addresses.

(4) In Section 2's final set of notes (below "Non-ASCII
characters can be encoded in "hvalue"...), your first bullet
says "SHOULD".  If the sending system ignores that
recommendation, what do you think will happen?  Think someone
might apply the UTF-8 encoding algorithm to ISO 8859-6
characters?

(5) While I sympathize with the reasons for Section 3, it is
(Continue reading)

Frank Ellermann | 19 Feb 2008 04:45
Picon
Picon

Re: I-D Action:draft-ietf-eai-mailto-00.txt

> An update to the mailto URI scheme for Email Address Internationalization

Oops, I thought the idea was to finish mailto-bis *before*
tackling mailto-eai.  Maybe putting this all on hold until
2822upd is no moving target, which could be really soon.

The draft says that mailto-eai is based on RFCXXXX, that's
mailto-bis.  Apparently RFCYYYY is the utf8headers draft.

Where RFCXXXX mailto-bis uses <addr-spec> mailto-eai needs
RFCYYYY <utf8-addr-spec>, not the <mailbox> like RFC 2368:

Replacing the x822 <mailbox> by the x821 <Mailbox>, or in
other words x822 <addr-spec>, is one the mailto-bis points,
no comments (etc.) in mailto-eai or mailto-bis, as already
noted by John.

| to = [ mailbox *("%2C" mailbox ) ]  

Compare <http://article.gmane.org/gmane.ietf.rfc822/12049>

I'm not sure about the necessity of "%2C" instead of ","
here.  Plus a few other issues like reserving "?" in the
query part, or reserving ";" before the query part (or at
all, see the original mailto-bis review at the given link).

mailto-bis got rid of <urlc> because it's not more defined
in STD 66.  Apparently mailto-eai is based on an obsolete
mailto-bis-00 or mailto-bis-01. 

(Continue reading)

Martin Duerst | 19 Feb 2008 10:26
Picon
Gravatar

Re: Quick comments on draft-ietf-eai-mailto-00

Hello John,

Many thanks (also to Frank) for your very quick feedback.

At 09:48 08/02/19, John C Klensin wrote:
>Martin,
>
>Some quick reactions...
>
>(1) This is really ugly.  Perhaps nothing can be done about it,
>but I think that is worth noting, especially since we have gone
>out of our way to make
>non-ASCII-string <at> non-ASCII-string.whatever.tld a value email
>address.

What are you referring to by "This"? If it's all the %-escaping,
then I fully agree with you. That's why we have IRIs :-).
I can guarantee that the draft would contain quite a few IRI
examples if the ID/RFC format allowed non-ASCII.

But we can't change the fact that we have to escape '<' and '>'
and so on.

More later.      Regards,    Martin.

>(2) It might be a bit less ugly if you used only envelope
>addresses (RFC2821-derived) rather than header (RFC2822-derived)
>ones.  In particular, I really see little need to incorporate
>name phrases in these strings and much less need to incorporate
>comments.  See also (6) below.
(Continue reading)


Gmane