Opened 9 years ago

Last modified 8 years ago

#44 new defect

Reference Unicode TR 46, and if yes, how?

Reported by: duerst@… Owned by: duerst@…
Priority: major Milestone:
Component: comparison Version:
Severity: - Keywords:


See and surrounding emails for some data points.

Change History (4)

comment:1 Changed 9 years ago by duerst@…

  • Owner set to addison@…

From interim teleconference 2010-10-05:

Larry: No harm in doing non-normative reference. Editorial. need text.
Joseph: agree to have non-normative reference.
ACTION: Addison to propose text on #44

comment:2 Changed 8 years ago by chris@…

Wouldn't section 3.4 "Mapping ireg-name" be the most appropriate place to talk a little more about TR46 strategies? Also section 10 "Security Considerations".

comment:3 Changed 8 years ago by duerst@…

It may make sense to watch other internet drafts as they move through the IESG for approval, and then look at how we can reuse their text. (As an example, mentions both IDNA 2003 and 2008, in, IDNA dependency and migration.)

comment:4 Changed 8 years ago by duerst@…

  • Component changed from 3987bis to comparison
  • Owner changed from addison@… to duerst@…

Issue moved to comparison document. Look at text in

Note: See TracTickets for help on using tickets.