Two Internet Drafts of possible interest

John C Klensin <[email protected]>
Newsgroups gmane.ietf.idn
Message-ID <[email protected]>
Hi.

I've just posted new version of 
draft-klensin-reg-guidelines-03.txt and 
draft-klensin-idn-tld-02.txt.  The former is an attempt to 
discuss the issues involved in modifying the JET Guidelines (RFC 
3743) and applying them to non-CJK languages and scripts, 
replacing (with some encouragement from Paul) both 
draft-klensin-reg-guidelines-0(0 1 2) and 
draft-hoffman-idn-reg-02.txt.  The latter is a discussion of an 
alternate approach to the "multilingual TLD" issue.  The more 
common suggestions for dealing with that issue is to create 
additional root entries for the "translation" of the domain 
names into various languages.

Neither of these drafts are part of the agenda of the (former) 
IDN WG, since they move well into the area of thinking about 
policy and applications of IDNA that the WG excluded.  But, 
since I'm about to attempt a conversation with the IESG about 
what to do with them -- and to hand them off to the RFC Editor 
as individual submissions if the IESG doesn't see an appropriate 
way to process them as IETF documents -- it seems like the right 
time to call them to the attention of this mailing list in the 
event that anyone has comments.  Assume you have a week or less 
-- I'd like to get this in motion before I leave for INET.

best,
   john
I-D ACTION:draft-klensin-idn-tld-02.txt (message/rfc822, 4.9 KB)
Return-path: <[email protected]>
Envelope-to: [email protected]
Delivery-date: Wed, 28 Apr 2004 15:24:28 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BIvbX-0004BV-00
	for [email protected]; Wed, 28 Apr 2004 15:24:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIurJ-0003PY-RW; Wed, 28 Apr 2004 15:36:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BIukI-0001dp-8e
	for [email protected]; Wed, 28 Apr 2004 15:29:26 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11024
	for <[email protected]>; Wed, 28 Apr 2004 15:29:24 -0400 (EDT)
Message-Id: <[email protected]>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: [email protected]
From: [email protected]
Subject: I-D ACTION:draft-klensin-idn-tld-02.txt
Date: Wed, 28 Apr 2004 15:29:24 -0400
Sender: [email protected]
Errors-To: [email protected]
X-BeenThere: [email protected]
X-Mailman-Version: 2.0.12
Precedence: bulk
Reply-To: [email protected]
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:[email protected]?subject=unsubscribe>
List-Id: <i-d-announce.ietf.org>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:[email protected]?subject=subscribe>

--NextPart

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


	Title		: National and Local Characters in DNS TLD Names
	Author(s)	: J. Klensin
	Filename	: draft-klensin-idn-tld-02.txt
	Pages		: 13
	Date		: 2004-4-28
	
In the context of work on internationalizing the Domain Name System
(DNS), there have been extensive discussions about 'multilingual' or
'internationalized' top level domain names (TLDs), especially for
countries whose predominant language is not written in a Roman-based
script.  This document reviews some of the motivations for such
domains and the constraints that the DNS imposes.  It then suggests
an alternative, local translation, that may solve a superset of the
problem while avoiding protocol changes, serious deployment delays,
and other difficulties.  The suggestion utilizes a localization
technique to permit any TLD to be accessed using the characters of
any language not merely language- or country-specific 'multilingual'
TLDs in the language(s) and script(s) of that country.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-klensin-idn-tld-02.txt

To remove yourself from the I-D Announcement list, send a message to 
[email protected] 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-klensin-idn-tld-02.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


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email protected].
In the body type:
	"FILE /internet-drafts/draft-klensin-idn-tld-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email protected]"

Content-Type: text/plain
Content-ID:	<[email protected]>

ENCODING mime
FILE /internet-drafts/draft-klensin-idn-tld-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-klensin-idn-tld-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email protected]>

--OtherAccess--

--NextPart--



_______________________________________________
I-D-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i-d-announce
I-D ACTION:draft-klensin-reg-guidelines-03.txt (message/rfc822, 5.4 KB)
Return-path: <[email protected]>
Envelope-to: [email protected]
Delivery-date: Fri, 30 Apr 2004 15:50:08 -0500
Received: from [147.28.0.62] (helo=psg.com ident=mailnull)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BJexU-0009rS-00
	for [email protected]; Fri, 30 Apr 2004 15:50:08 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by psg.com with esmtp (Exim 4.30; FreeBSD)
	id 1BJexT-000D0K-JS
	for [email protected]; Fri, 30 Apr 2004 20:50:07 +0000
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJe7V-0003PJ-1U; Fri, 30 Apr 2004 15:56:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJdwl-0007Lu-Eo
	for [email protected]; Fri, 30 Apr 2004 15:45:19 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26296
	for <[email protected]>; Fri, 30 Apr 2004 15:45:15 -0400 (EDT)
Message-Id: <[email protected]>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: [email protected]
From: [email protected]
Subject: I-D ACTION:draft-klensin-reg-guidelines-03.txt
Date: Fri, 30 Apr 2004 15:45:15 -0400
Sender: [email protected]
Errors-To: [email protected]
X-BeenThere: [email protected]
X-Mailman-Version: 2.0.12
Precedence: bulk
Reply-To: [email protected]
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:[email protected]?subject=unsubscribe>
List-Id: <i-d-announce.ietf.org>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:[email protected]?subject=subscribe>

--NextPart

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


	Title		: Registration of Internationalized Domain Names: Overview and Method
	Author(s)	: J. Klensin
	Filename	: draft-klensin-reg-guidelines-03.txt
	Pages		: 23
	Date		: 2004-4-30
	
IETF has introduced standards-track mechanisms to enable the use of
   'internationalized, i.e., non-ASCII, names in the DNS and
   applications that use it.  This has led, in turn, to concerns that
   characters with similar meanings or appearance could cause user
   confusion and opportunities for deliberate deception and fraud.  Part
   of this problem can be addressed by limiting, on a per-zone (or
   per-registry) basis, the specific characters that can be used to be a
   subset of the list allowed by the standard and by creating
   'reservations' of labels that might create confusion with those that
   are permitted.  The model for doing this for languages that use
   characters that originated with Chinese has been extensively
   developed in another document.  This document discusses some of the
   issues in that design and relates them to considerations and
   mechanisms that might be appropriate for other languages and scripts,
   especially those involving alphabetic characters.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-klensin-reg-guidelines-03.txt

To remove yourself from the I-D Announcement list, send a message to 
[email protected] 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-klensin-reg-guidelines-03.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


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email protected].
In the body type:
	"FILE /internet-drafts/draft-klensin-reg-guidelines-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email protected]"

Content-Type: text/plain
Content-ID:	<[email protected]>

ENCODING mime
FILE /internet-drafts/draft-klensin-reg-guidelines-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-klensin-reg-guidelines-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email protected]>

--OtherAccess--

--NextPart--



_______________________________________________
I-D-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i-d-announce
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.