Fwd: WG Review: Internationalized Domain Name (idn)
Lisa Dusseault <[email protected]> Wed, 27 Feb 2008 08:59:36 -0800
| Newsgroups | gmane.ietf.idnabis,gmane.ietf.idn |
|---|---|
| Message-ID | <[email protected]> |
--===============1296881572== Content-Type: multipart/alternative; boundary=Apple-Mail-2-338593725 --Apple-Mail-2-338593725 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed FYI -- comments welcome. There's a meeting scheduled in Philadelphia, which could turn into a WG meeting if this is approved for a WG charter; otherwise it will remain a BOF meeting. Thanks, Lisa Begin forwarded message: > From: The IESG <[email protected]> > Date: February 26, 2008 9:57:35 AM PST > To: IETF Announcement list <[email protected]> > Cc: [email protected] > Subject: WG Review: Internationalized Domain Name (idn) > Reply-To: [email protected] > > A new IETF working group has been proposed in the Applications > Area. The > IESG has not made any determination as yet. The following draft > charter > was submitted, and is provided for informational purposes only. > Please > send your comments to the IESG mailing list ([email protected]) by > March 4, > 2008. > > Internationalized Domain Name (idn) > ============================= > Last modified: 2008-02-18 > > Current Status: Proposed Working Group > > Chair(s): > > TBD > > Applications Area Directors: > > Lisa Dusseault ([email protected]) > Chris Newman ([email protected]) > > Applications Area Advisor: > > Lisa Dusseault ([email protected]) > > Mailing List: > > General Discussion: [email protected] > To Subscribe: > http://www.alvestrand.no/mailman/listinfo/idna-update > Archive: http://www.alvestrand.no/pipermail/idna-update/ > > Description: > > The original Internationalized Domain Name (IDN) WG set the > requirements for international characters in domain names in > RFC 3454, RFC3490, RFC3491 and RFC3492 in 2002. These documents > were tied to Unicode version 3.2 and an update to the current > version (5.x) is required to accommodate additional scripts. > In addition, experience has shown a number of real or perceived > defects or inadequacies with the protocol. Some of them are > described in an IAB review (RFC4690), which also provides a good > introduction to the subject matter. > > IDNA is currently tied to an obsolete version of Unicode. This WG > is chartered to untie IDNA from specific versions of Unicode using > algorithms that define validity based on Unicode properties. It is > recognized that some explicit exceptions may be necessary in any > case, but attempts would be made to minimize these exceptions. > > Additional goals: > > - Separate requirements for valid IDNs at registration time, > vs. at resolution time > - Revise bi-directional algorithms to produce a deterministic > answer whether a label is allowed or not > - Determine whether bi-directional algorithm should allow > additional mnemonics labels > - Permit effective use of some scripts that were > inadvertently excluded by the original protocols. > > The constraints of the original IDN WG still apply, namely to > avoid disturbing the current use and operation of the domain > name system, and for the DNS to continue to allow any system > to resolve any domain name. The basic approach of the original > IDN work will be maintained -- substantially new protocols or > mechanisms are not in scope. In particular, IDNs continue to > use the "xn--" prefix and the same ASCII-compatible encoding, > and the bidirectional algorithm follows the same basic design. > > The WG will work to ensure practical stability of the validity > algorithms for IDNs (whether based on character properties or > inclusion/exclusion lists). > > The work is currently organized into four deliverables, all > Standards Track. The WG will verify that it has consensus > to adopt the proposed documents as a starting point. The > Overview document with explanation and rationale is intended > for Standards Track status because it has definitions and > other normative text required by the other documents. The > protocol specification explains how to map non-ASCII > characters into ASCII DNS labels. It relies normatively on > two other documents that are separate for readability: the > bidirectional algorithm specification and the character > validity tables. The validity of characters in IDNs is > almost exclusively based on Unicode properties but is > organized as tables and categories for readability. > > Goals and milestones: > > Mar 08: WG Last Call for Overview/Rationale document > Apr 08: Revised Overview/Rationale document > Apr 08: WG Last Call for Protocol, Bidi and Tables documents > May 08: Revised Protocol, Bidi and Tables documents > May 08: Review Overview document again if needed > Jul 08: Request for publication for all documents > > Documents: > > http://tools.ietf.org/html/draft-klensin-idnabis-issues > http://tools.ietf.org/html/draft-klensin-idnabis-protocol > http://tools.ietf.org/html/draft-faltstrom-idnabis-tables > http://tools.ietf.org/html/draft-alvestrand-idna-bidi > --Apple-Mail-2-338593725 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 <HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; = -khtml-line-break: after-white-space; "><DIV><BR = class=3D"khtml-block-placeholder"></DIV>FYI -- comments welcome.=A0 = There's a meeting scheduled in Philadelphia, which could turn into a WG = meeting if this is approved for a WG charter; otherwise it will remain a = BOF meeting.=A0=A0<DIV><BR = class=3D"khtml-block-placeholder"></DIV><DIV>Thanks,</DIV><DIV>Lisa<BR><DI= V><BR><DIV>Begin forwarded message:</DIV><BR = class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" color=3D"#000000" = style=3D"font: 12.0px Helvetica; color: #000000"><B>From: = </B></FONT><FONT face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px = Helvetica">The IESG <<A = href=3D"mailto:[email protected]">[email protected]</A>></FONT></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" color=3D"#000000" = style=3D"font: 12.0px Helvetica; color: #000000"><B>Date: = </B></FONT><FONT face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px = Helvetica">February 26, 2008 9:57:35 AM PST</FONT></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" color=3D"#000000" = style=3D"font: 12.0px Helvetica; color: #000000"><B>To: </B></FONT><FONT = face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica">IETF = Announcement list <<A = href=3D"mailto:[email protected]">[email protected]</A>></FON= T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: = 0px; margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" = color=3D"#000000" style=3D"font: 12.0px Helvetica; color: = #000000"><B>Cc: </B></FONT><FONT face=3D"Helvetica" size=3D"3" = style=3D"font: 12.0px Helvetica"><A = href=3D"mailto:[email protected]">[email protected]</A></F= ONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" = size=3D"3" color=3D"#000000" style=3D"font: 12.0px Helvetica; color: = #000000"><B>Subject: </B></FONT><FONT face=3D"Helvetica" size=3D"3" = style=3D"font: 12.0px Helvetica"><B>WG Review: Internationalized Domain = Name (idn)<SPAN = class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"3" color=3D"#000000" = style=3D"font: 12.0px Helvetica; color: #000000"><B>Reply-To: = </B></FONT><FONT face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px = Helvetica"><A = href=3D"mailto:[email protected]">[email protected]</A></FONT></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV style=3D"margin-top:= 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A new = IETF working group has been proposed in the Applications Area.<SPAN = class=3D"Apple-converted-space">=A0 </SPAN>The</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">IESG has not made any determination as yet.<SPAN = class=3D"Apple-converted-space">=A0 </SPAN>The following draft = charter</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">was submitted, and is provided = for informational purposes only.<SPAN class=3D"Apple-converted-space">=A0 = </SPAN>Please</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">send your comments to the IESG = mailing list (<A href=3D"mailto:[email protected]">[email protected]</A>) by = March 4,</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">2008.</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">Internationalized Domain Name (idn)</DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Last modified: 2008-02-18<SPAN = class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Current = Status: Proposed Working Group</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: = 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Chair(s):</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">TBD</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Applications Area Directors:</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Lisa = Dusseault (<A = href=3D"mailto:[email protected]">[email protected]</A>)</DIV>= <DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Chris Newman (<A = href=3D"mailto:[email protected]">[email protected]</A>)</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">Applications Area Advisor:</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: = 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Lisa Dusseault (<A = href=3D"mailto:[email protected]">[email protected]</A>)</DIV>= <DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Mailing = List:</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">General Discussion: <A = href=3D"mailto:[email protected]">[email protected]</A></D= IV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">To Subscribe:</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A = href=3D"http://www.alvestrand.no/mailman/listinfo/idna-update">http://www.= alvestrand.no/mailman/listinfo/idna-update</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Archive: <A = href=3D"http://www.alvestrand.no/pipermail/idna-update/">http://www.alvest= rand.no/pipermail/idna-update/</A></DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: = 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Description:</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The = original Internationalized Domain Name (IDN) WG set the</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">requirements for international characters in domain = names in</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">RFC 3454, RFC3490, RFC3491 and = RFC3492 in 2002. These documents</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">were tied to = Unicode version 3.2 and an update to the current</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">version (5.x) is required to accommodate additional = scripts.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">In addition, experience has = shown a number of real or perceived</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">defects or = inadequacies with the protocol. Some of them are</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">described in an IAB review (RFC4690), which also = provides a good</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">introduction to the subject = matter.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">IDNA is currently tied to an obsolete version of = Unicode. This WG</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">is chartered to untie IDNA from = specific versions of Unicode using</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">algorithms = that define validity based on Unicode properties. It is</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">recognized that some explicit exceptions may be = necessary in any</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">case, but attempts would be made = to minimize these exceptions.</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: = 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Additional goals:</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- = Separate requirements for valid IDNs at registration time,</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">vs. at resolution time</DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- Revise = bi-directional algorithms to produce a deterministic</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">answer whether a label is allowed or not</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">- Determine whether bi-directional algorithm should = allow</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">additional mnemonics = labels</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">- Permit effective use of some = scripts that were</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">inadvertently excluded by the = original protocols.</DIV><DIV style=3D"margin-top: 0px; margin-right: = 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; = "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">The constraints of the original = IDN WG still apply, namely to</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">avoid = disturbing the current use and operation of the domain</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">name system, and for the DNS to continue to allow = any system</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">to resolve any domain name. The = basic approach of the original</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">IDN work will = be maintained -- substantially new protocols or</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">mechanisms are not in scope. In particular, IDNs = continue to</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">use the "xn--" prefix and the = same ASCII-compatible encoding,</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">and the = bidirectional algorithm follows the same basic design.</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The WG = will work to ensure practical stability of the validity</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">algorithms for IDNs (whether based on character = properties or</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">inclusion/exclusion = lists).</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">The work is currently organized into four = deliverables, all</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Standards Track. The WG will = verify that it has consensus</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to adopt the = proposed documents as a starting point. The</DIV><DIV style=3D"margin-top:= 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">Overview document with explanation and rationale is intended</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">for Standards Track status because it has = definitions and</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">other normative text required by = the other documents. The</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">protocol = specification explains how to map non-ASCII</DIV><DIV style=3D"margin-top:= 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = ">characters into ASCII DNS labels. It relies normatively on</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">two other documents that are separate for = readability: the</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">bidirectional algorithm = specification and the character</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">validity = tables. The validity of characters in IDNs is</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">almost exclusively based on Unicode properties but = is</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: = 0px; margin-left: 0px; ">organized as tables and categories for = readability.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Goals and milestones:</DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; = min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Mar 08: WG = Last Call for Overview/Rationale document</DIV><DIV style=3D"margin-top: = 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Apr 08: = Revised Overview/Rationale document</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Apr 08: WG = Last Call for Protocol, Bidi and Tables documents</DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">May 08: Revised Protocol, Bidi and Tables = documents</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">May 08: Review Overview document = again if needed</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; ">Jul 08: Request for publication = for all documents</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; ">Documents:</DIV><DIV style=3D"margin-top: 0px; = margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: = 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; = margin-bottom: 0px; margin-left: 0px; "><A = href=3D"http://tools.ietf.org/html/draft-klensin-idnabis-issues">http://to= ols.ietf.org/html/draft-klensin-idnabis-issues</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><A = href=3D"http://tools.ietf.org/html/draft-klensin-idnabis-protocol">http://= tools.ietf.org/html/draft-klensin-idnabis-protocol</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><A = href=3D"http://tools.ietf.org/html/draft-faltstrom-idnabis-tables">http://= tools.ietf.org/html/draft-faltstrom-idnabis-tables</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; "><A = href=3D"http://tools.ietf.org/html/draft-alvestrand-idna-bidi">http://tool= s.ietf.org/html/draft-alvestrand-idna-bidi</A></DIV><DIV = style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; = margin-left: 0px; min-height: 14px; "><BR></DIV> = </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>= --Apple-Mail-2-338593725-- --===============1296881572== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idna-update mailing list [email protected] http://www.alvestrand.no/mailman/listinfo/idna-update --===============1296881572==--