Re: [DNSOP] Public Suffix List

Gervase Markham wrote:
> - "No, sorry, you can't do any of the things for which you might want
> this data"
> 
> - "It's fine to want this data, but you should get it via this
> alternative method:..."

I'm inclined to suggest: Gather and hard-code your list into Firefox,
and also provide a mechanism by which domain authorities can publish
information which overrides your list for their domain.

E.g. When evaluating online.myservice.free.fr, Firefox could look up
DNS records for online.myservice.free.fr, myservice.free.fr, free.fr
and .fr (in that order), and if there's a record use that.  If not,
use the hard-coded information you have gathered for that domain.

In this case, you would expect, eventually, that free.fr may publish a
record indicating that $NAME.free.fr are independent adminstratives
entities, and that's the first record you'll fine.

One day, someone creates dyndns.littleisp.free.fr, and lets people
register themselves underneath that domain.  (Such as
littlecustomer.dyndns.littleisp.free.fr).  Then, instead of contacting
you and trying to get their information into your next Firefox update,
they would simply publish a DNS record on dyndns.littleisp.free.fr,
and the information would be live immediately.  Not just for Firefox,
but for any web client which adopts the same scheme.

(By the way, although we're talking about administrative divides in
the DNS tree, a little thought might be given to administrative
divides in URL trees.  There are a fair number of sites containing
http://domain.com/user1/* and http://domain.com/user2/*, where those
prefixes indicates separately administered URL spaces.  Do similar
cookie issues apply?  Should a mechanism for publishing details of
administrative divides include URL spaces for the same reasons?)

-- Jamie

Received on Tuesday, 10 June 2008 11:15:40 UTC