headers
Harald Tveit Alvestrand | 4 Sep 2008 00:51
Picon

Re: Deciding what to do with IRIs in List-* headers

Harald Alvestrand skrev:
> Hello,
>
> at our Dublin meeting, the issue of how to handle headers with URLs 
> that contain non-ASCII characters (that is, they are IRIs in an URI 
> slot) came up - in the context of List-* headers.
>
> I see two possible ways forward:
>
> 1 - Don't address the issue at this time. Let such headers be turned 
> into Downgraded-* headers, effectively hidden from the user's MUA. Add 
> a comment that this will happen. This is the fastest path to getting 
> -downgrade submitted.
>
> 2 - Add a new mechanism to -downgrade section 5
Given that I haven't heard anything resembling enthusiasm for solution 
2, I'm taking the group consensus to be that we should stay with the 
current text in -downgrade; any List-* header containing non-ASCII 
characters will be turned into Downgraded-List-* headers.

Decision made. With that out of the way, I think it's time for the WG 
Last Call on -downgrade.

                      Harald
Permalink | Reply | 1 comment |
headers
arfan mansoor | 4 Sep 2008 06:04
Picon

Re: help

Will Punycode converter work for EAI as it works for IDNs where we convert IDN to ASCII string through Punycode algorithm?

Regards
Arfan

On Fri, Aug 29, 2008 at 6:38 AM, YAO Jiankang <yaojk <at> cnnic.cn> wrote:

----- Original Message -----
From: "Stephane Bortzmeyer" <bortzmeyer <at> nic.fr>
To: "arfan mansoor" <arfan.mansoor <at> gmail.com>
Cc: <IMA <at> ietf.org>
Sent: Thursday, August 28, 2008 8:51 PM
Subject: Re: [EAI] help


> On Thu, Aug 21, 2008 at 11:50:47AM +0500,
> arfan mansoor <arfan.mansoor <at> gmail.com> wrote
> a message of 38 lines which said:
>
>> We are doing work for Urdu (Pakistan language) EAI.  I want to know
>> progress about other languages, has any one implemented this
>> successfully and at what level this implementation is possible?
>
> I feel confused. There is nothing language-specific in the EAI
> standards, so any good EAI mail server should work for every language
> on earth.

yes, agree.

arfan mansoor's meaning may be that whether some tests of the email address based on Urdu  has been done. is the email address of [Urdu Name] <at> [Urdu IDN] workable? or are there someone who configured the EAI email server to support [Urdu Name] <at> [Urdu IDN] ?


>
> May be you are talking about the development of a MUA, where,
> certainly, language-specific issues are to be considered? But, if it
> is the case, isn't it quite ott-topic for this group?
> _______________________________________________
> IMA mailing list
> IMA <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>

_______________________________________________
IMA mailing list
IMA <at> ietf.org
https://www.ietf.org/mailman/listinfo/ima
Permalink | Reply | 1 comment |
headers
YAO Jiankang | 4 Sep 2008 06:56
Picon

Re: help

a lot of issues you raised has been discussed; you'd better take a look at the  list
 
 
 
----- Original Message -----
Sent: Thursday, September 04, 2008 12:04 PM
Subject: Re: [EAI] help

Will Punycode converter work for EAI as it works for IDNs where we convert IDN to ASCII string through Punycode algorithm?

Regards
Arfan

On Fri, Aug 29, 2008 at 6:38 AM, YAO Jiankang <yaojk <at> cnnic.cn> wrote:

----- Original Message -----
From: "Stephane Bortzmeyer" <bortzmeyer <at> nic.fr>
To: "arfan mansoor" <arfan.mansoor <at> gmail.com>
Cc: <IMA <at> ietf.org>
Sent: Thursday, August 28, 2008 8:51 PM
Subject: Re: [EAI] help


> On Thu, Aug 21, 2008 at 11:50:47AM +0500,
> arfan mansoor <arfan.mansoor <at> gmail.com> wrote
> a message of 38 lines which said:
>
>> We are doing work for Urdu (Pakistan language) EAI.  I want to know
>> progress about other languages, has any one implemented this
>> successfully and at what level this implementation is possible?
>
> I feel confused. There is nothing language-specific in the EAI
> standards, so any good EAI mail server should work for every language
> on earth.

yes, agree.

arfan mansoor's meaning may be that whether some tests of the email address based on Urdu  has been done. is the email address of [Urdu Name] <at> [Urdu IDN] workable? or are there someone who configured the EAI email server to support [Urdu Name] <at> [Urdu IDN] ?


>
> May be you are talking about the development of a MUA, where,
> certainly, language-specific issues are to be considered? But, if it
> is the case, isn't it quite ott-topic for this group?
> _______________________________________________
> IMA mailing list
> IMA <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>

_______________________________________________
IMA mailing list
IMA <at> ietf.org
https://www.ietf.org/mailman/listinfo/ima
Permalink | Reply | 0 comments |
headers
Stephane Bortzmeyer | 4 Sep 2008 09:59
Picon

Re: help

On Thu, Sep 04, 2008 at 09:04:05AM +0500,
 arfan mansoor <arfan.mansoor <at> gmail.com> wrote 
 a message of 96 lines which said:

> Will Punycode converter work for EAI as it works for IDNs where we
> convert IDN to ASCII string through Punycode algorithm?

There are not many uses of Punycode in EAI. One is, for instance, the
initial greeting EHLO where you cannot (yet) use UTF-8 for the host
name. But, apart from a few cases like this one, why worrying about
Punycode?
Permalink | Reply | 0 comments |
headers
rfc-editor | 6 Sep 2008 02:07
Favicon

RFC 5335 on Internationalized Email Headers


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5335

        Title:      Internationalized Email Headers 
        Author:     Y. Abel, Ed.
        Status:     Experimental
        Date:       September 2008
        Mailbox:    abelyang <at> twnic.net.tw
        Pages:      14
        Characters: 27945
        Updates:    RFC2045, RFC2822

        I-D Tag:    draft-ietf-eai-utf8headers-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5335.txt

Full internationalization of electronic mail requires not only the
capabilities 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 the 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.
This form is permitted in transmission only if authorized by an SMTP
extension, as specified in an associated specification.  This
specification Updates section 6.4 of RFC 2045 to conform with the
requirements.  This memo defines an Experimental Protocol for the Internet
community.

This document is a product of the Email Address Internationalization Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor <at> rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute
Permalink | Reply | 0 comments |
headers
rfc-editor | 6 Sep 2008 02:07
Favicon

RFC 5336 on SMTP Extension for Internationalized Email Addresses


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5336

        Title:      SMTP Extension for Internationalized Email 
                    Addresses 
        Author:     J. Yao, Ed.,
                    W. Mao, Ed.
        Status:     Experimental
        Date:       September 2008
        Mailbox:    yaojk <at> cnnic.cn, 
                    maowei_ietf <at> cnnic.cn
        Pages:      22
        Characters: 48110
        Updates:    RFC2821, RFC2822, RFC4952

        I-D Tag:    draft-ietf-eai-smtpext-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5336.txt

This document specifies an SMTP extension for transport and delivery
of email messages with internationalized email addresses or header
information.  Communication with systems that do not implement this
specification is specified in another document.  This document
updates some syntaxes and rules defined in RFC 2821 and RFC 2822, and
has some material updating RFC 4952This memo defines an Experimental 
Protocol for the Internet community.

This document is a product of the Email Address Internationalization Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor <at> rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute
Permalink | Reply | 0 comments |
headers
rfc-editor | 6 Sep 2008 02:07
Favicon

RFC 5337 on Internationalized Delivery Status and Disposition Notifications


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5337

        Title:      Internationalized Delivery Status and Disposition 
                    Notifications 
        Author:     C. Newman, A. Melnikov, Ed.
        Status:     Experimental
        Date:       September 2008
        Mailbox:    chris.newman <at> sun.com, 
                    Alexey.Melnikov <at> isode.com
        Pages:      18
        Characters: 36324
        Updates:    RFC3461, RFC3464, RFC3798

        I-D Tag:    draft-ietf-eai-dsn-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5337.txt

Delivery status notifications (DSNs) are critical to the correct
operation of an email system.  However, the existing Draft Standards
(RFC 3461, RFC 3462, RFC 3464) are presently limited to US-ASCII text
in the machine-readable portions of the protocol.  This specification
adds a new address type for international email addresses so an
original recipient address with non-US-ASCII characters can be
correctly preserved even after downgrading.  This also provides
updated content return media types for delivery status notifications
and message disposition notifications to support use of the new
address type.

This document experimentally extends RFC 3461, RFC 3464, and RFC
3798.  This memo defines an Experimental Protocol for the Internet
community.

This document is a product of the Email Address Internationalization Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor <at> rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute
Permalink | Reply | 0 comments |
headers
Frank Ellermann | 7 Sep 2008 09:03
Picon
Picon

Re: For review: Original-Recipient

> PERMANENT MESSAGE HEADER FIELD REGISTRATION TEMPLATE:

> Header field name:         Original-Recipient
[...]
> Specification document(s): RFC 3798, draft-ietf-eai-dsn

Now RFC 5337.  Registration submitted 2008-09-07, [IANA #188861].
Permalink | Reply | 0 comments |
headers
arfan mansoor | 10 Sep 2008 08:51
Picon

Re: help

Dear Jiankang

> so any good EAI mail server should work for every language
> on earth.

Would you please list some examples of such EAI supported email servers? Is there any community working on EAI support in ThunderBird? 

On Fri, Aug 29, 2008 at 6:38 AM, YAO Jiankang <yaojk <at> cnnic.cn> wrote:

----- Original Message -----
From: "Stephane Bortzmeyer" <bortzmeyer <at> nic.fr>
To: "arfan mansoor" <arfan.mansoor <at> gmail.com>
Cc: <IMA <at> ietf.org>
Sent: Thursday, August 28, 2008 8:51 PM
Subject: Re: [EAI] help


> On Thu, Aug 21, 2008 at 11:50:47AM +0500,
> arfan mansoor <arfan.mansoor <at> gmail.com> wrote
> a message of 38 lines which said:
>
>> We are doing work for Urdu (Pakistan language) EAI.  I want to know
>> progress about other languages, has any one implemented this
>> successfully and at what level this implementation is possible?
>
> I feel confused. There is nothing language-specific in the EAI
> standards, so any good EAI mail server should work for every language
> on earth.

yes, agree.

arfan mansoor's meaning may be that whether some tests of the email address based on Urdu  has been done. is the email address of [Urdu Name] <at> [Urdu IDN] workable? or are there someone who configured the EAI email server to support [Urdu Name] <at> [Urdu IDN] ?


>
> May be you are talking about the development of a MUA, where,
> certainly, language-specific issues are to be considered? But, if it
> is the case, isn't it quite ott-topic for this group?
> _______________________________________________
> IMA mailing list
> IMA <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>

_______________________________________________
IMA mailing list
IMA <at> ietf.org
https://www.ietf.org/mailman/listinfo/ima
Permalink | Reply | 0 comments |
headers
arfan mansoor | 10 Sep 2008 09:18
Picon

Usage of Punycode in EAI

Referred to below quoted text; Why Punycode is not as helpful in EAI as it is in IDNs and what is meant by arbitrary free text in the below quoted text?
Can't we apply same restrictions to email addresses as we did in IDN case.


'"1.2 Interaction of protocol parts (Retrieved from http://www.ietf.org/rfc/rfc3492.txt on 4th Sept, 2008)

Punycode is used by the IDNA protocol [IDNA] for converting domain labels into ASCII; it is not designed for any other purpose. It is
explicitly not designed for processing arbitrary free text."


Regards
Arfan Mansoor

_______________________________________________
IMA mailing list
IMA <at> ietf.org
https://www.ietf.org/mailman/listinfo/ima
Permalink | Reply | 2 comments |

Gmane