Re: [DNSOP] Public Suffix List

Gervase Markham <gerv@mozilla.org> Wed, 11 June 2008 09:15 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@optimus.ietf.org
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73B2F3A6A3C; Wed, 11 Jun 2008 02:15:05 -0700 (PDT)
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C6B43A6A3C for <dnsop@core3.amsl.com>; Wed, 11 Jun 2008 02:15:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.086
X-Spam-Level:
X-Spam-Status: No, score=-4.086 tagged_above=-999 required=5 tests=[AWL=-0.487, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWDB1fOD4CUC for <dnsop@core3.amsl.com>; Wed, 11 Jun 2008 02:15:03 -0700 (PDT)
Received: from jet.mythic-beasts.com (jet.mythic-beasts.com [193.201.200.50]) by core3.amsl.com (Postfix) with ESMTP id C69823A6A1C for <dnsop@ietf.org>; Wed, 11 Jun 2008 02:15:02 -0700 (PDT)
Received: from grmarkham.plus.com ([80.229.30.161] helo=[192.168.1.6]) by jet.mythic-beasts.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1K6MQP-00011L-OO; Wed, 11 Jun 2008 10:15:26 +0100
Message-ID: <484F97A7.6020709@mozilla.org>
Date: Wed, 11 Jun 2008 10:15:19 +0100
From: Gervase Markham <gerv@mozilla.org>
User-Agent: Thunderbird 3.0a1 (X11/2008050714)
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
References: <Pine.LNX.4.44.0806101207560.5176-100000@citation2.av8.net>
In-Reply-To: <Pine.LNX.4.44.0806101207560.5176-100000@citation2.av8.net>
Received-SPF: none (jet.mythic-beasts.com: domain of gerv@mozilla.org does not designate permitted sender hosts) client-ip=80.229.30.161 envelope-from=gerv@mozilla.org helo=[192.168.1.6]
X-BlackCat-Spam-Score: -18
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, David Conrad <drc@virtualized.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Subject: Re: [DNSOP] Public Suffix List
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

Dean Anderson wrote:
>> That's unfortunate; but I must say this upset was not communicated to me.
> 
> Probably that's because you are using SORBS to filter your email. SORBS
> has an unusually high number of false positives, and for example,
> falsely claims that that 130.105/16 and 198.3.136/21 are hijacked. You 
> can find more information about SORBS on http://www.iadl.org/

No-one can have control over and knowledge of everything their ISP does
with relation to the services they provide. I confess I've only ever
vaguely heard the name SORBS, and had no idea that my provider was using
it. But I don't believe that using it makes me uncontactable. My phone
number and address are on my personal web page.

I can hardly imagine some TLD administrator saying "I'm so irritated
about Firefox's TLD IDN whitelist. I'm going to send Gerv a nasty email.
Hang on, my email's been rejected. Oh well, I guess I'll just have to
live with it."

>> That policy of ours should have no effect whatsoever on TLDs with a
>> responsible attitude to homographs. Our registration requirements are
>> not onerous.
> 
> ??? This statement doesn't seem very credible. What authority do you
> have to decide what a 'responsible attitude to homegraphs' would be?  

What's your answer to that question? (Hint: the answer "no-one" is
equivalent to the answer "the registries", which has been shown not to
work. See http://www.shmoo.com/idn/ .)

> Mozilla.org doesn't represent the internet industry nor any government
> or governing organization. 

No, we represent our users, and we make all sorts of security decisions
for them on a regular basis. One of the reasons Firefox is popular is
precisely because it doesn't wimp out of security decisions with
user-irritating popup questions they have no information to answer. But,
as someone else has said, if people don't like the decisions we make,
they can either become part of "we" and seek to change them, or they can
change or build their copy, or can distribute an alternative browser.

> Why should TLD's think they need to register
> with Mozilla.org? 

They don't have to. Why should TLDs think they have an automatic right
to have Firefox display domains they have issued which allow our users
to be fooled or defrauded?

Gerv
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop