[ga] Re: [At-Large] internationalization of email addresses

["Jeffrey A. Williams" <jwkckid1@xxxxxxxxxxxxx>]

Thomas and all,

  I fully agree.  *Experimental* RFC's are not standards, nor
on a standards track, and should not be consider as such yet.

  I for one, don't necessarly look forward to any implimentations
of this RFC by any organization as it gives miscrients additional
avenues by which to ply their disgusting, disruptive, and sometimes
illegal activities.  I can just see the .RU and .CN domain name
holders with ganges of Cybercriminals smiling a huge smile as they
read this *Experimental* RFC and are hurring to devise ways to
exploit it's use for their errant means.

  I also feel sorry to a degree that LEA's will be deluged with
complaints from these Internationalize Email addresses and perhaps,
if not likely their associated IDN gTLD's by which such Email addresses
will be derived from.  I am fairly sure that DHS, the FBI, and the
Secret Service in my country are not adaquately prepaired for this
soon to be happening deluge.  >:(

Thomas Roessler wrote:

> It is worth noting that these are *experimental*, not standards
> track RFCs.  The proposed design is a bit of an experiment, and adds
> some significant complexity to the e-mail infrastructure.  It
> remains to be seen how successful these specifications will be.
> --
> Thomas Roessler   <roessler@xxxxxxxxxxxxxxxxxx>
>
> On 2008-09-08 04:39:45 -0700, Danny Younger wrote:
> > From: Danny Younger <dannyyounger@xxxxxxxxx>
> > To: at-large@xxxxxxxxxxxxxxxxxxxxxxx
> > Date: Mon, 8 Sep 2008 04:39:45 -0700 (PDT)
> > Subject: [At-Large] internationalization of email addresses
> > Reply-To: At-Large Worldwide <at-large@xxxxxxxxxxxxxxxxxxxxxxx>
> > List-Id: At-Large Worldwide
> >       <at-large_atlarge-lists.icann.org.atlarge-lists.icann.org>
> > X-Spam-Level:
> > X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.1.6
> >
> > submitted by Stephane Bortzmeyer to the Governance List:
> >
> > Since we often talk about internationalization...
> >
> > Three new RFCs have been published on friday. They (almost) finalize
> > the standards for the internationalization of email addresses (email
> > content in Unicode is standard since 1992). Soon :-) I'll be able to
> > use stéphane@xxxxxxxxxxxxx with the accent. Congratulations for the
> > EAI Working Group.
> >
> > Now, we can say that almost all the IETF standards are
> > Unicode-able.
> >
> > (The main missing one is FTP, which has an option TEXT which is only
> > for ASCII. An Unicode version is under work.)
> >
> >         RFC 5335
> >
> >         Title:      Internationalized Email Headers
> >         Author:     Y. Abel, Ed.
> >         Status:     Experimental
> >         Date:       September 2008
> >         Mailbox:    abelyang@xxxxxxxxxxxx
> >         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.
> >
> >
> >
> >         RFC 5336
> >
> >         Title:      SMTP Extension for Internationalized Email
> >                     Addresses
> >         Author:     J. Yao, Ed.,
> >                     W. Mao, Ed.
> >         Status:     Experimental
> >         Date:       September 2008
> >         Mailbox:    yaojk@xxxxxxxx,
> >                     maowei_ietf@xxxxxxxx
> >         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.
> >
> >
> >
> >         RFC 5337
> >
> >         Title:      Internationalized Delivery Status and Disposition
> >                     Notifications
> >         Author:     C. Newman, A. Melnikov, Ed.
> >         Status:     Experimental
> >         Date:       September 2008
> >         Mailbox:    chris.newman@xxxxxxx,
> >                     Alexey.Melnikov@xxxxxxxxx
> >         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.
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > At-Large mailing list
> > At-Large@xxxxxxxxxxxxxxxxxxxxxxx
> > http://atlarge-lists.icann.org/mailman/listinfo/at-large_atlarge-lists.icann.org
> >
> > At-Large Official Site: http://atlarge.icann.org
> >
> >
>
> _______________________________________________
> At-Large mailing list
> At-Large@xxxxxxxxxxxxxxxxxxxxxxx
> http://atlarge-lists.icann.org/mailman/listinfo/at-large_atlarge-lists.icann.org
>
> At-Large Official Site: http://atlarge.icann.org

Regards,

Spokesman for INEGroup LLA. - (Over 281k members/stakeholders strong!)
"Obedience of the law is the greatest freedom" -
   Abraham Lincoln

"Credit should go with the performance of duty and not with what is
very often the accident of glory" - Theodore Roosevelt

"If the probability be called P; the injury, L; and the burden, B;
liability depends upon whether B is less than L multiplied by
P: i.e., whether B is less than PL."
United States v. Carroll Towing  (159 F.2d 169 [2d Cir. 1947]
===============================================================
Updated 1/26/04
CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS.
div. of Information Network Eng.  INEG. INC.
ABA member in good standing member ID 01257402 E-Mail
jwkckid1@xxxxxxxxxxxxx
My Phone: 214-244-4827