Re: [DNSOP] Public Suffix List

[Niall O'Reilly <[e-mail]>]

On 12 Jun 2008, at 12:25, Gervase Markham wrote:

> The second question is one of resources and client complexity. I am
> meeting resistance to the idea of having the existing list regularly
> dynamically downloaded, which would be the simplest method of  
> providing
> more frequent updates than the six-to-eight week Firefox security
> releases. An assemble-and-cache-the-data-from-DNS scheme would be an
> order of magnitude more complex.

	I'm not sure why you would need to assemble anything.
	Couldn't you seize the data you need, on demand,From [e-mail]  Thu Jun 12 05:54:00 2008
Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 31A3C28C118;
	Thu, 12 Jun 2008 05:54:00 -0700 (PDT)
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D095428C112
	for <[e-mail]>; Thu, 12 Jun 2008 05:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4]
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 9G2-m2887XrY for <[e-mail]>;
	Thu, 12 Jun 2008 05:53:54 -0700 (PDT)
Received: from dakota.ucd.ie (mailhub1.ucd.ie [193.1.169.34])
	by core3.amsl.com (Postfix) with ESMTP id 95F3228C122
	for <[e-mail]>; Thu, 12 Jun 2008 05:53:54 -0700 (PDT)
Received: from conversion-daemon.dakota.ucd.ie by dakota.ucd.ie
	(Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005))
	id <[e-mail]> (original mail from
	[e-mail])
	for [e-mail]; Thu, 12 Jun 2008 13:54:21 +0100 (IST)
Received: from [193.1.143.96] (dhcp-c1018f60.ucd.ie [193.1.143.96])
	by dakota.ucd.ie
	(Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005))
	with ESMTPSA id <[e-mail]> for [e-mail];
	Thu, 12 Jun 2008 13:54:21 +0100 (IST)
Date: Thu, 12 Jun 2008 13:54:32 +0100
From: Niall O'Reilly <[e-mail]>
In-reply-to: <[e-mail]>
To: IETF DNSOP WG <[e-mail]>
Message-id: <[e-mail]>
MIME-version: 1.0
X-Mailer: Apple Mail (2.753)
X-Pgp-Agent: GPGMail 1.1.2 (Tiger)
References: <[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]>
	<[e-mail]>
	<[e-mail]>
	<[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]> <[e-mail]>
	<[e-mail]>
	<[e-mail]>
Cc: Niall O'Reilly <[e-mail]>
Subject: Re: [DNSOP] Public Suffix List
X-BeenThere: [e-mail]
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:[e-mail]?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dnsop>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>,
	<mailto:[e-mail]?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2084958239=="
Sender: [e-mail]
Errors-To: [e-mail]

On 12 Jun 2008, at 12:25, Gervase Markham wrote:

> The second question is one of resources and client complexity. I am
> meeting resistance to the idea of having the existing list regularly
> dynamically downloaded, which would be the simplest method of  
> providing
> more frequent updates than the six-to-eight week Firefox security
> releases. An assemble-and-cache-the-data-from-DNS scheme would be an
> order of magnitude more complex.

	I'm not sure why you would need to assemble anything.
	Couldn't you seize the data you need, on demand, from
	the DNS (and cache at will).


	Best regards,

	Niall O'Reilly
	University College Dublin IT Services

	PGP key ID: AE995ED9 (see www.pgp.net)
	Fingerprint: 23DC C6DE 8874 2432 2BE0 3905 7987 E48D AE99 5ED9

_______________________________________________
DNSOP mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dnsop