Hi
Just a thought - I don't know if it is a good one.
Can you not use the SOA record to make this determination?
I would suggest that information should be shared only if two domains have
the same SOA.
That is, we check for existence of an SOA record for a domain, it's parent,
etc. until we find an SOA record.
To check two domains, we use this function on both, and compare for
equality.
example1.co.uk
and
example2.co.uk
will each have their own SOA record, so it is clear information should not
be shared.
There might be instances where this is too restrictive, but it should be
fairly good I think.
George Barwood
----- Original Message -----
From: "Yngve N. Pettersen (Developer Opera Software ASA)" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, November 03, 2008 10:47 PM
Subject: [DNSOP] Fwd: I-D Action:draft-pettersen-subtld-structure-04.txt
Hi,
FYI, this draft removes the central repository requirement, and moves the
method for collecting the information out of scope.
Suggestions for how to collect the information are welcomed.
------- Forwarded message -------
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: I-D Action:draft-pettersen-subtld-structure-04.txt
Date: Mon, 03 Nov 2008 23:15:01 +0100
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
Title : The TLD Subdomain Structure Protocol and its use for
Cookie domain validation
Author(s) : Y. Pettersen
Filename : draft-pettersen-subtld-structure-04.txt
Pages : 14
Date : 2008-11-03
This document defines a protocol and specification format that can be
used by a client to discover how a Top Level Domain (TLD) is
organized in terms of what subdomains are used to place closely
related but independent domains, e.g. commercial domains in country
code TLDs (ccTLD) like .uk are placed in the .co.uk subTLD domain.
This information is then used to limit which domains an Internet
service can set cookies for, strengthening the rules already defined
by the cookie specifications.Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-pettersen-subtld-structure-04.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
--
Sincerely,
Yngve N. Pettersen
********************************************************************
Senior Developer Email: [EMAIL PROTECTED]
Opera Software ASA http://www.opera.com/
Phone: +47 24 16 42 60 Fax: +47 24 16 40 01
********************************************************************
--------------------------------------------------------------------------------
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
