Hi,
On Fri, Oct 7, 2022 at 2:17 PM Peter Thomassen wrote:
> On 10/7/22 19:46, Roy Arends wrote:
> > Perhaps:
> >
> > What we refer to as "DNSSEC" is the third iteration of the DNSSEC
> specification; [RFC2065] being the first, [RFC2535] being the second.
> Earlier iterations have not been deploye
On Oct 7, 2022, at 14:18, Paul Hoffman wrote:
>
>
> I like Roy's text more than PaulW's two suggestions.
Me too !
Paul
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
On 10/7/22 19:46, Roy Arends wrote:
Perhaps:
What we refer to as "DNSSEC" is the third iteration of the DNSSEC specification;
[RFC2065] being the first, [RFC2535] being the second. Earlier iterations have not been deployed on
a significant scale. Throughout this document, "DNSSEC" means the pr
On Oct 7, 2022, at 10:46 AM, Roy Arends wrote:
>
>
>
>> On 7 Oct 2022, at 17:21, Paul Wouters wrote:
>>
>> On Fri, 7 Oct 2022, Paul Hoffman wrote:
>>
>>> On Monday, I'll do a new draft with:
>>>
>>> What we today call "DNSSEC" is the DNSSEC specification defined in
>>> {{RFC4033}}, {{RFC40
> On 7 Oct 2022, at 17:21, Paul Wouters wrote:
>
> On Fri, 7 Oct 2022, Paul Hoffman wrote:
>
>> On Monday, I'll do a new draft with:
>>
>> What we today call "DNSSEC" is the DNSSEC specification defined in
>> {{RFC4033}}, {{RFC4034}}, and {{RFC4035}}.
>> However, earlier incarnations of DNSS
On 07/10/2022 18.21, Paul Wouters wrote:
Perhaps even:
DNSSEC documents predating {{RFC4033}}, {{RFC4034}}, and {{RFC4035}}
specify obsoleted DNS RRtypes that never saw deployment beyond early
adopter testing, and haven't been deployed in nearly two decades,
and are of no concern to implementers
On Fri, 7 Oct 2022, Paul Hoffman wrote:
On Monday, I'll do a new draft 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 curr
On Monday, I'll do a new draft 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.
...unless there i
On 10/7/22 15:41, Warren Kumari wrote:
I'm personally fine with Paul's proposed text, minor tweaks on "incarnations",
Peter's modifications, whatever.
I don't feel very strongly either way.
Cheers,
Peter
--
https://desec.io/
___
DNSOP mailing lis
On Wed, Oct 05, 2022 at 3:59 PM, Paul Hoffman
wrote:
> On Oct 5, 2022, at 11:36 AM, Peter Thomassen wrote:
>
> On 10/5/22 20:25, Paul Hoffman wrote:
>
> 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
On Oct 5, 2022, at 11:36 AM, Peter Thomassen wrote:
>
> On 10/5/22 20:25, Paul Hoffman wrote:
>>> 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 {{RFC4
On 10/5/22 20:25, Paul Hoffman wrote:
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 si
> On Oct 5, 2022, at 11:00 AM, Peter Thomassen 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 incarnat
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.
Works for me.
regards
John
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 th
On Oct 5, 2022, at 10:44 AM, John Dickinson wrote:
>
> "What we today call "DNSSEC" is formally version 3 of the DNSSEC
> specification."
>
> The only version number I know of in DNSSEC is the Protocol Field in a DNSKEY
> RR. However this doesn't really version the whole of DNSSEC.
>
> So I
16 matches
Mail list logo
