The default bug view has changed. See this FAQ.

Add .asia to IDN TLD whitelist

RESOLVED FIXED

Status

()

Core
Networking: Domain Lists
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: gerv, Assigned: gerv)

Tracking

({verified1.9.2})

unspecified
verified1.9.2
Points:
---

Firefox Tracking Flags

(status2.0 .x-fixed, status1.9.2 .18-fixed, status1.9.1 .20-fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

6 years ago
Edmon Chung writes: 

Hi Gervase,

As .ASIA prepares for our IDN launch, we have published our draft IDN Language Policies at: http://www.idn.asia/main/2011/03/asia-cjk-chinese-japanese-korean-idn-policies.html.  They should be finalized shortly and posted on our set of completed policies.

Wanted to see how we can work on having .ASIA on the whitelist.

Edmon
(Assignee)

Comment 1

6 years ago
They are using the JET guidelines which deal with anti-spoofing for Chinese/Japanese/Korean characters, so that's OK.

Gerv
(Assignee)

Comment 2

6 years ago
Created attachment 519712 [details] [diff] [review]
Patch v.1
Assignee: nobody → gerv
Status: NEW → ASSIGNED

Comment 3

6 years ago
I spoke face to face with Edmon at the ICANN meeting in San Francisco last week.  They are working with the JET guidelines as Gerv mentions, and additionally their registry service provider, Afilias, is working tightly with the Anti-Phishing working groups to ensure good hygiene happens in this implementation of IDN.

FWIW I see their effort as totally aligned with (and perhaps stronger than many of) those TLDs that are currently whitelisted.  Not sure if I count as a +1 here but...

+1
(Assignee)

Comment 4

6 years ago
http://hg.mozilla.org/mozilla-central/rev/52add75e45f8

Gerv
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

6 years ago
Attachment #519712 - Flags: approval2.0?
Attachment #519712 - Flags: approval1.9.2.18?
Attachment #519712 - Flags: approval1.9.1.20?
Comment on attachment 519712 [details] [diff] [review]
Patch v.1

Approved for 1.9.2.18 and 1.9.1.20, a=dveditz for release-drivers
Approved for the mozilla2.0 repository, a=dveditz for release-drivers
Attachment #519712 - Flags: approval2.0?
Attachment #519712 - Flags: approval2.0+
Attachment #519712 - Flags: approval1.9.2.18?
Attachment #519712 - Flags: approval1.9.2.18+
Attachment #519712 - Flags: approval1.9.1.20?
Attachment #519712 - Flags: approval1.9.1.20+
(Assignee)

Comment 6

6 years ago
http://hg.mozilla.org/releases/mozilla-2.0/rev/93709d2e3f37
http://hg.mozilla.org/releases/mozilla-1.9.2/rev/15e7e752aba3
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/d16776f157b8

Gerv
status1.9.1: --- → .20-fixed
status1.9.2: --- → .18-fixed
status2.0: --- → .x-fixed
Verified for 1.9.2.18 in source.
Keywords: verified1.9.2
You need to log in before you can comment on or make changes to this bug.