Closed Bug 621710 Opened 9 years ago Closed 9 years ago
.nl to PSL
Dear Publicsuffix, In he near future we will start giving out registrations for foo.bv.nl to dutch companies that are a registered BV (besloten vennootschap). For correct browser behaviour we would like to be included in the list. Also, can you advise on how to get this same issue solved on IE and safari? Attached you will find our diff. Regards, Marius Karthaus BVpuntNL bv.diff --- tld.dat 2010-12-10 06:10:56.000000000 +0100 +++ tld.bv.dat 2010-12-12 21:42:26.821109002 +0100 @@ -2647,7 +2647,8 @@ // Confirmed by registry <Antoin.Verschuren@sidn.nl> (with technical // reservations) 2008-06-08 nl - +// BV.nl will be a registry for dutch BV's (besloten vennootschap) +*.bv.nl // no : http://www.norid.no/regelverk/index.en.html // The Norwegian registry has declined to notify us of updates. The web pages // referenced below are the official source of the data. There is also an
This diff says that we should treat <something>,bv.nl as a public suffix - and therefore that the website for e.g. Foo B.V. is going to be registered at foo.<something>.bv.nl. However, the English text of the email says that websites are going to be registered at foo.bv.nl. I have emailed the bv.nl registry to ask them to clarify. Gerv
Looking at the list and the examples I do not understand why I chose to submit '*.bv.nl' You are right to assume that we need to have plain 'bv.nl' Thank you for spotting this.
As agreed. Gerv
Assignee: nobody → gerv
Status: NEW → ASSIGNED
Attachment #507210 - Flags: approval2.0?
Comment on attachment 507210 [details] [diff] [review] Patch v.1 a=beltzner
Attachment #507210 - Flags: approval2.0? → approval2.0+
http://hg.mozilla.org/mozilla-central/rev/4aa1a8bc87fd (I used the wrong bug number, though; I'll comment there.)
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0
Comment on attachment 507210 [details] [diff] [review] Patch v.1 Approved for 188.8.131.52 and 184.108.40.206, a=dveditz
You need to log in before you can comment on or make changes to this bug.