Re: [Idna-update] FWD: Last Calls on two IDNA documents

["J-F C. Morfin" <[e-mail]>]

John,
all of us trust Patrick's and your competence and wiseness IRT iDNs. 
And thank you for your constant updating. However, I observe that the 
retained solution regularly calls for updates.
I am considering a polynym (strict lingual synonyms) oriented DDDS 
service (bigdata multilingual database labels for cross-origin data). 
A first idea is to build it on a similar basis as iDNs. However 
concerns are about Unicode stability over decades.
The need is for a string in any language returning the its polynym in 
any other language indicated by its langtag. Would you have a better 
suggestion? The project is to try to locate the service at a 
meditarean group of universities.
Best
jfc

At 23:15 02/08/2019, John C Klensin wrote:
>For those who don't follow the IETF-announce list and are
>interested, Last Calls were announced today  on
>draft-klensin-idna-unicode-review and
>draft-klensin-idna-rfc5891bis.  The former is the clarification
>to the "new Unicode version" review process discussed
>extensively while we were working on the Unicode 11.0 and 12.0
>updates and IANA tables early in the year (and on
>draft-faltstrom-unicode11 and draft-faltstrom-unicode12).  The
>latter is a significantly updated version of clarification to
>the "registry restrictions" material that has been kicking
>around for a few years.
>
>If you have comments, please follow the Last Call instructions
>included below.
>
>best,
>    john
>
>
>---------- Forwarded Message ----------
>Date: Friday, August 2, 2019 09:08 -0700
>From: The IESG <[e-mail]>
>To: IETF-Announce <[e-mail]>
>Cc: [e-mail],
>[e-mail], [e-mail]
>Subject: Last Call: <draft-klensin-idna-unicode-review-02.txt>
>(IDNA Review for New Unicode Versions) to Proposed Standard
>
>
>The IESG has received a request from an individual submitter to
>consider the following document: - 'IDNA Review for New Unicode
>Versions'   <draft-klensin-idna-unicode-review-02.txt> as
>Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and
>solicits final comments on this action. Please send substantive
>comments to the [e-mail] mailing lists by 2019-08-30.
>Exceptionally, comments may be sent to [e-mail] instead. In
>either case, please retain the beginning of the Subject line to
>allow automated sorting.
>
>Abstract
>
>
>    The standards for Internationalized Domain Names in
>Applications    (IDNA) require a review of each new version of
>Unicode to determine    whether incompatibilities with prior
>version or other issues exist    and, where appropriate, to
>allow the IETF to decide on the trade-offs    between
>compatibility with prior IDNA versions and compatibility with
>Unicode going forward.  That requirement, and its relationship to
>    tables maintained by IANA, has caused significant confusion
>in the    past.  This document makes adjustments to the review
>procedure based    on experience and updates IDNA, specifically
>RFC 5892, to reflect    those changes and clarify the various
>relationships involved.  It    also makes other minor
>adjustments to align that document with    experience.
>
>
>
>
>The file can be obtained via
>https://datatracker.ietf.org/doc/draft-klensin-idna-unicode-revi
>ew/
>
>IESG discussion can be tracked via
>https://datatracker.ietf.org/doc/draft-klensin-idna-unicode-revi
>ew/ballot/
>
>
>No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>_______________________________________________
>IETF-Announce mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/ietf-announce
>
>---------- End Forwarded Message ----------
>
>
>
>---------- Forwarded Message ----------
>Date: Friday, August 2, 2019 13:30 -0700
>From: The IESG <[e-mail]>
>To: IETF-Announce <[e-mail]>
>Cc: [e-mail],
>[e-mail], [e-mail]
>Subject: Last Call: <draft-klensin-idna-rfc5891bis-04.txt>
>(Internationalized Domain Names in Applications (IDNA): Registry
>Restrictions and Recommendations) to Proposed Standard
>
>
>The IESG has received a request from an individual submitter to
>consider the following document: - 'Internationalized Domain
>Names in Applications (IDNA): Registry
>    Restrictions and Recommendations'
>   <draft-klensin-idna-rfc5891bis-04.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and
>solicits final comments on this action. Please send substantive
>comments to the [e-mail] mailing lists by 2019-08-30.
>Exceptionally, comments may be sent to [e-mail] instead. In
>either case, please retain the beginning of the Subject line to
>allow automated sorting.
>
>Abstract
>    The IDNA specifications for internationalized domain names
>combine    rules that determine the labels that are allowed in
>the DNS without    violating the protocol itself and an
>assignment of responsibility,    consistent with earlier
>specifications, for determining the labels    that are allowed
>in particular zones.  Conformance to IDNA by    registries and
>other implementations requires both parts.  Experience
>strongly suggests that the language describing those
>responsibilities    was insufficiently clear to promote safe and
>interoperable use of the    specifications and that more details
>and discussion of circumstances    would have been helpful.
>Without making any substantive changes to    IDNA, this
>specification updates two of the core IDNA documents (RFC
>5980 and 5891) and the IDNA explanatory document (RFC 5894) to
>provide that guidance and to correct some technical errors in the
>    descriptions.
>
>
>The file can be obtained via
>https://datatracker.ietf.org/doc/draft-klensin-idna-rfc5891bis/
>
>When IESG discussion has begun, it can be tracked via
>https://datatracker.ietf.org/doc/draft-klensin-idna-rfc5891bis/b
>allot/
>
>
>No IPR declarations have been submitted directly on this I-D.
>
>
>The document contains these normative downward references.
>See RFC 3967 for additional information:
>     rfc5894: Internationalized Domain Names for Applications
>(IDNA): Background, Explanation, and Rationale (Informational -
>IETF stream)     rfc1591: Domain Name System Structure and
>Delegation (Informational - Legacy stream)
>
>_______________________________________________
>IETF-Announce mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/ietf-announce
>
>---------- End Forwarded Message ----------
>
>
>
>
>_______________________________________________
>IDNA-UPDATE mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/idna-update