See <ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsext-unknown-rrs-00.txt>.
Donald
From: Bill Manning <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] (Randy Bush)
Date: Thu, 18 Jan 2001 04:14:09 -0800 (PST)
Cc: [EMAIL PROTECTED] (Perry E. Metzger), [EMAIL PROTECTED] (Jim Bound),
[EMAIL PROTECTED], [EMAIL PROTECTED] (dns op wg),
[EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]> from "Randy Bush" at Jan 17, 2001
10:39:15 PM
>% an example of a worry is cache poisoning of an antique v4 bind.
>% ----
>% and there are thousands of vulnerable v4 binds still out there.
>%
>% randy
>%
>
> One might argue that we have only applied the carrot.
> We still have broken/vulnerable code, some pushing
> 15 years w/o an upgrade. Perhaps its time to apply
> a stick and let folks know that things will stop working
> or won't be the same unless they upgrade.
> I note that we will have this problem regardless and more
> esp. as we hit "unknown" RR types. Zones won't load.
> Perhaps we should have dnsops worry about the deployment of
> new types, be it RR or Class?
>
>--
>--bill