* Andras Salamon:
>ftp://ftp.rfc-editor.org/in-notes/rfc1535.txt
Have you noticed that this document calls for the implementation of a
public suffix lis? 8-)
> I routinely dot-terminate domain names and disable search lists,
This doesn't work reliably with HTTP as deployed, by the way.
I d
> On Sat, Jul 05, 2008 at 01:11:36AM -0400, Brian Dickson wrote:
> > That's precisely why it makes sense to think about the partial name
> > problem, before big problems happen for lots of ISPs.
>
> My feeling is that search lists for DNS are a bad optimization that
> should never have happened.
On Sat, Jul 05, 2008 at 01:11:36AM -0400, Brian Dickson wrote:
> That's precisely why it makes sense to think about the partial name
> problem, before big problems happen for lots of ISPs.
My feeling is that search lists for DNS are a bad optimization that
should never have happened. After publi
Mark Andrews wrote:
names which do not terminate in "." (and in some cases, which might not
permit such name termination).
Consider the label "foo.bar", a stub resolver, a recursive resolver, new
TLD "bar", and existing SLD "example.com".
Partially qualified domains and search l
> (Thread originated on main IETF mailing list...)
>
> In a discussion concerning new TLD names and namespace collisions that
> might (and to
> some extent, are likely to) occur, Mark Andrews wrote:
> >> So the "problem" isn't whether some string not listed in 2606
> >> can be allocated, it is h
(Thread originated on main IETF mailing list...)
In a discussion concerning new TLD names and namespace collisions that
might (and to
some extent, are likely to) occur, Mark Andrews wrote:
So the "problem" isn't whether some string not listed in 2606
can be allocated, it is how it is used afte
