On mån, 2008-06-09 at 17:28 +0100, Gervase Markham wrote:
> It would be an appropriate mechanism; when it does contain this
> information, let me know.
It won't until someone specifies in how the data should be represented
in DNS. And DNS is where it belongs, in the zone it relates to.
Regards
H
On tis, 2008-06-10 at 11:13 +0100, Gervase Markham wrote:
> OK. Then we are basically back to Yngve's suggestion. But this does
> require universal take-up for universal support - and that, as someone
> else has pointed out, makes it (in my opinion) doomed.
Not really. By proper design you can ea
On tis, 2008-06-10 at 13:45 +0200, Henrik Nordstrom wrote:
> On mån, 2008-06-09 at 17:28 +0100, Gervase Markham wrote:
>
> > It would be an appropriate mechanism; when it does contain this
> > information, let me know.
>
> It won't until someone specifies in how t
On tis, 2008-06-10 at 21:05 +0200, Florian Weimer wrote:
> stuff). This must work by default, without explicit marking by the web
> site operator, or tons of deployed applications will break.
I seriously question this "will break" part. Sure, they will get
annoyed, but in nearly all possible sol
On tis, 2008-06-10 at 21:25 +0200, Florian Weimer wrote:
> Isn't this the wrong direction, that is, should you start from the TLD?
Not if done for the receiving site, but yes if done based on the site
setting the cookie..
Regards
Henrik
signature.asc
Description: This is a digitally signed mes
On ons, 2008-06-11 at 10:10 +0100, Gervase Markham wrote:
> Other list participants were warning about the possibility of people
> abandoning Firefox in droves if there were cookie-related problems
> caused by its use of public suffix list.
If you do this wronly yes.
> You, on the other hand, ar
