* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #44 (new defect)

Opened 5 years ago

Last modified 4 years ago

Reference Unicode TR 46, and if yes, how?

Reported by: duerst@it.aoyama.ac.jp Owned by: duerst@it.aoyama.ac.jp
Priority: major Milestone:
Component: comparison Version:
Severity: - Keywords:


See http://lists.w3.org/Archives/Public/public-iri/2010Sep/0016.html and surrounding emails for some data points.

Change History

comment:1 Changed 5 years ago by duerst@it.aoyama.ac.jp

  • Owner set to addison@lab126.com

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 4 years ago by chris@lookout.net

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 4 years ago by duerst@it.aoyama.ac.jp

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, http://tools.ietf.org/html/draft-ietf-websec-origin-06 mentions both IDNA 2003 and 2008, in http://tools.ietf.org/html/draft-ietf-websec-origin-06#section-8.4, IDNA dependency and migration.)

comment:4 Changed 4 years ago by duerst@it.aoyama.ac.jp

  • Owner changed from addison@lab126.com to duerst@it.aoyama.ac.jp
  • Component changed from 3987bis to comparison

Issue moved to comparison document. Look at text in http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-04.

Note: See TracTickets for help on using tickets.