> On Oct 5, 2022, at 11:00 AM, Peter Thomassen <pe...@desec.io> wrote:
>
> Hi,
>
> On 10/5/22 19:56, Paul Hoffman wrote:
>> I propose to replace that paragraph with:
>> What we today call "DNSSEC" is the DNSSEC specification defined in
>> {{RFC4033}}, {{RFC4034}}, and {{RFC4035}}.
>> However, earlier incarnations of DNSSEC were thinly deployed and
>> significantly less
>> visible than the current DNSSEC specification.
>
> I think that's much better, but it remains vague in that it leaves open what
> those other versions were.
>
> I know there are some RFCs that defined KEY records etc. Is that's what's
> meant? Perhaps we should add something like:
>> For the historic record of these, see RFC 2535 and related documents.
>
> (Or whatever is the appropriate set of documents.)Given that we don't have clear version numbers, I would kinda prefer not to do that. Does RFC 2535 represent a clear description of an earlier incarnation/version of DNSSEC? It doesn't feel that way to me. --Paul Hoffman
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
