Skip to main content

Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)
draft-hoffman-rfc3491bis-01

Revision differences

Document history

Date Rev. By Action
2015-10-14
01 (System) Notify list changed from phoffman@imc.org, paf@cisco.com, amc+q3tovu@nicemice.net, Marc.Blanchet@hexago.com to amc+q3tovu@nicemice.net, paf@cisco.com, Marc.Blanchet@hexago.com
2005-05-26
01 (System) Ballot writeup text was added
2005-05-26
01 (System) Last call text was added
2005-05-26
01 (System) Ballot approval text was added
2005-05-26
01 (System) State Changes to Dead from AD is watching by IESG Secretary
2005-03-15
01 (System) Document has expired
2005-03-14
01 Scott Hollenbeck State Changes to AD is watching from Publication Requested by Scott Hollenbeck
2005-03-10
01 Thomas Narten Shepherding AD has been changed to Scott Hollenbeck from Thomas Narten
2004-05-17
01 Thomas Narten State Change Notice email list have been change to phoffman@imc.org, paf@cisco.com, amc+q3tovu@nicemice.net, Marc.Blanchet@hexago.com from Marc.Blanchet@viagenie.qc.ca, paul.hoffman@imc.org
2004-05-14
01 Thomas Narten
From: Paul Hoffman / IMC
To: Thomas Narten
Date: Thu, 22 Apr 2004 17:25:39 -0700
Subject: NUDGE: Publishing the new IDN RFCs

[[ Didn't ever …
From: Paul Hoffman / IMC
To: Thomas Narten
Date: Thu, 22 Apr 2004 17:25:39 -0700
Subject: NUDGE: Publishing the new IDN RFCs

[[ Didn't ever hear an ACK on this message, and the I-D tracker
doesn't indicate that you have accepted the documents yet. --Paul ]]

Greetings again. Patrik, Adam, Marc and I would like you to have the
following drafts published as replacing the current IDN-related RFCs:

draft-hoffman-rfc3454bis-02.txt
draft-hoffman-rfc3490bis-02.txt
draft-hoffman-rfc3491bis-01.txt
draft-costello-rfc3492bis-02.txt

Each one has clarifications and editorial nit changes; none of them
change the technical aspects of the original RFCs.

Please note that we are *not* asking to move the specifications to
Draft Standard at this time. While there are many interoperable
implementations of IDNs, I have found that most of them only
implement some of the protocol (and some implement other parts
wrong). I could probably find two examples of every feature done
correctly in two genetically separate implementations, but I think
that saying something is a Draft Standard also implies that it is
mature enough so that most people are doing it right. That is not yet
the case in the IDN world.

There has been little discussion about these on the IDN mailing list,
but once you issue an IETF last call, I hope that any niggling issues
will come out.

Thanks!

--Paul Hoffman, Director
--Internet Mail Consortium
2004-05-14
01 Thomas Narten Draft Added by Thomas Narten
2004-04-14
01 (System) New version available: draft-hoffman-rfc3491bis-01.txt
2003-10-07
00 (System) New version available: draft-hoffman-rfc3491bis-00.txt