Return-Path: X-Original-To: dnsop@mail2.ietf.org Delivered-To: dnsop@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E3A951FBDD16 for ; Tue, 22 Apr 2025 20:27:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.094 X-Spam-Level: X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CU0vo-eGHzUB for ; Tue, 22 Apr 2025 20:27:23 -0700 (PDT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0C3A71FBDCC8 for ; Tue, 22 Apr 2025 20:27:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1745378836; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gBg+bDet3kAog9HxS5pKmruTPZKQM8Q6VG/ToxlSg4c=; b=honB3VGlnLOPKJpNFCkOYQW3VNmpLX1k021C8MFg8Q3q0hT78CdDj8+XvlOA5474lOJrHp yXFsWCISn4jhuv4Chk6gvDerYCE1mDxElh6DTQEfYvm8IBAHZ0yzNgBHovvRENymJqQldk bBy1rQbfBt4gX2k5tl9jJ0no3oMnEHQ= Received: from mail-pj1-f70.google.com (mail-pj1-f70.google.com [209.85.216.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-90-E-N5m4scPm2KfqT5LN6v6w-1; Tue, 22 Apr 2025 23:27:14 -0400 X-MC-Unique: E-N5m4scPm2KfqT5LN6v6w-1 X-Mimecast-MFC-AGG-ID: E-N5m4scPm2KfqT5LN6v6w_1745378834 Received: by mail-pj1-f70.google.com with SMTP id 98e67ed59e1d1-3085f5855c4so5420564a91.1 for ; Tue, 22 Apr 2025 20:27:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745378834; x=1745983634; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=gBg+bDet3kAog9HxS5pKmruTPZKQM8Q6VG/ToxlSg4c=; b=h+ifFFLuIkSlg/3rzd/PiQbPRywoyNftPe2K3H8y2yJXMSzk3c9R2gcfOSoU7wPdMK pNK6b9USu9qCHOBByUBdUyhGiZ6POG3b7jLSFQf1zXxVPB6UNx77Yt6ZY1uotIod3e0E iki0QqAdDcqYhb/g5jJEC8E06aTeAPOz7jQ5B69zwG2UbnY+MFQ9FPI8uBDmPloK7IgI Rc2jJsvWpYoZHib5b39WXX2cj1mS31q2avs+XFpoHDygBh17DvO0T0fq5DgCIr++JUlL g5413PVjJgi194TmC+WqDRTc8z+5Gw2YT3m4ewEYF1sRfAbaxxzDk0dNI8G76gAXWvXp cF8g== X-Forwarded-Encrypted: i=1; AJvYcCXLXDR0QIDK+re2zwEDsMyKXxY+QJVVCQSoNU6bzEJhnu8q88BqXPCv8pYhJywAGF1wXnQJTQ==@ietf.org X-Gm-Message-State: AOJu0YyjUhNwND2NUszwhE7jffINULwW6CRnmOawMNYJ+8pynoXgTtTD JQsnvXWDOWXJmNY8V4uh4MOaYIr8+ezGFM+S4Vyc/vex5ROh/tNS0xn/703BP/fhwWckV7VPkl3 avFyLDKjA/WE0q3uD+xFBdwDZ3j2F0jVfLVwSfVexcQv1AQraILyaZj0qOl0d1ujFtTBiWXBYJX k55oxh9bfu0UCBY2sIlA== X-Gm-Gg: ASbGncupzGCyRVP7sk3GvJWG4ryP0Svr+LxLp9YE5113wqZm3hddI9Q7J9cuu6MzHPl EXbDI77jSK6MK2Vro3AVDfZ6QMI6Vq/JRjGO4BywzO+vtWPCNKncDpIRvcveAy6uOe17p3ysw1w == X-Received: by 2002:a17:90b:53c5:b0:2ee:8430:b831 with SMTP id 98e67ed59e1d1-3087bb3e7a6mr27506454a91.2.1745378833594; Tue, 22 Apr 2025 20:27:13 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGotFyOjfNXCslKHJP+xX/DbRyxALcEDzZ68SDTL2PY2jcRYKdtQJwn3/4SYn/LObDC2hdQw/WU6RxCNeoyQb0= X-Received: by 2002:a17:90b:53c5:b0:2ee:8430:b831 with SMTP id 98e67ed59e1d1-3087bb3e7a6mr27506419a91.2.1745378833237; Tue, 22 Apr 2025 20:27:13 -0700 (PDT) MIME-Version: 1.0 References: <174465840535.1140913.7319759953755231962@dt-datatracker-64c5c9b5f9-hz6qg> In-Reply-To: From: Nabeel Cocker Date: Tue, 22 Apr 2025 23:27:02 -0400 X-Gm-Features: ATxdqUFGfmhDY4OoiDckkxd5XtpDTBQu9nb_ia8LNOVpvrdZ8KQbClRqmjWY164 Message-ID: To: Wes Hardaker X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: WHSYvNHhvwzo0XAZ4FizQbAF_7QRwWhD--9uynjE22U_1745378834 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="0000000000005aa953063369ad35" Message-ID-Hash: CTNNPTSEDA5V2IQDLWE2SDI2G4ROE4BK X-Message-ID-Hash: CTNNPTSEDA5V2IQDLWE2SDI2G4ROE4BK X-MailFrom: ncocker@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Nabeel Cocker via Datatracker , ops-dir@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-rfc8624-bis.all@ietf.org, last-call@ietf.org X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BDNSOP=5D_Re=3A_=5BOPS-DIR=5DRe=3A_Opsdir_ietf_last_call_partial?= =?utf-8?q?_review_of_draft-ietf-dnsop-rfc8624-bis-09?= List-Id: IETF DNSOP WG mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000005aa953063369ad35 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Wes, Sorry forgot to ask when the updated draft will be uploaded? thanks Nabeel On Tue, Apr 22, 2025 at 11:06=E2=80=AFPM Nabeel Cocker = wrote: > Hello Wes, > > Your updates totally work! > > thanks for the updates! > > Regards, > Nabeel > > On Tue, Apr 22, 2025 at 1:08=E2=80=AFPM Wes Hardaker wrote: > >> Nabeel Cocker via Datatracker writes: >> >> Hi Nabeel, >> >> > Section 1.2, paragraph 3: >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >> > "This will allow for deprecated algorithms to become used less and les= s >> over >> > time." >> > >> > Perhaps say it like "This ensures that the use of deprecated algorithm= s >> > decreases over time." >> >> Done! >> >> >> > Section 2: >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> > The last paragraph states >> > The "Implement for" column values are transcribed from >> > [RFC8624]. The "Use for" columns are set to the same values as the >> > "implement for" ... >> > "implement for" has a lower case "i". >> >> Good catch, thanks. >> >> > Section 2: >> > ---------- >> > The last paragraph states: >> > The "Implement for" column values are transcribed from >> > [RFC8624]. The "Use for" columns are set to the same values as the >> > "implement for" values since the general interpretation to date >> > indicates they have been treated as values for both "implementation= " >> > and "use". We note that the values for "Implement for" and "Use fo= r" >> > may diverge in the future. >> > >> > The above text indicates that the "Implement for" and "Use for" column= s >> should >> > have identical values. However, when I look at Table 2, there are >> differences >> > between the values in the "Implement for" and the "Use for" for number >> 5, 7, 8, >> > 10 and 13, For example, in number 5 where Use for DNSSEC Validation is >> > "RECOMMEND" but the Implement for DNSSEC Validation is "MUST" >> >> That's a good point and we don't discuss it in the document. The WG >> wished to not use MUST and MUST-NOT for the Use for column, so we >> replaced them with RECOMMENDED. As such, I added a sentence to the >> document that now says: >> >> Note that the "Use for" columns values use "RECOMMENDED" when the >> corresponding "Implement for" column is a "MUST" value. >> >> Does that work for you? >> -- >> Wes Hardaker >> USC/ISI >> >> _______________________________________________ >> OPS-DIR mailing list -- ops-dir@ietf.org >> To unsubscribe send an email to ops-dir-leave@ietf.org >> > > > -- > *Nabeel Cocker* > Senior Principal Architect, Global Telco Consulting Practice > > M: +1-845-240-2587 > > Email: ncocker@redhat.com > > --=20 *Nabeel Cocker* Senior Principal Architect, Global Telco Consulting Practice M: +1-845-240-2587 Email: ncocker@redhat.com --0000000000005aa953063369ad35 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Wes,

Sorry forgot to ask when the= updated draft will be uploaded?

thanks
= Nabeel

On Tue, Apr 22, 2025 at 11:06=E2=80=AFPM = Nabeel Cocker <ncocker@redhat.com<= /a>> wrote:
<= div dir=3D"ltr">Hello Wes,

Your updates totally work!

thanks for the updates!

Reg= ards,
Nabeel

On Tue, Apr 22, 2025 at 1:08=E2=80=AFPM Wes H= ardaker <wjhns= 1@hardakers.net> wrote:
Nabeel Cocker via Datatracker <noreply@ietf.org> writes:

Hi Nabeel,

> Section 1.2, paragraph 3:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D
> "This will allow for deprecated algorithms to become used less an= d less over
> time."
>
> Perhaps say it like "This ensures that the use of deprecated algo= rithms
> decreases over time."

Done!


> Section 2:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> The last paragraph states
>=C2=A0 The "Implement for" column values are transcribed from=
>=C2=A0 =C2=A0 [RFC8624].=C2=A0 The "Use for" columns are set = to the same values as the
>=C2=A0 =C2=A0 "implement for" ...
> "implement for" has a lower case "i".

Good catch, thanks.

> Section 2:
> ----------
> The last paragraph states:
>=C2=A0 The "Implement for" column values are transcribed from=
>=C2=A0 =C2=A0 [RFC8624].=C2=A0 The "Use for" columns are set = to the same values as the
>=C2=A0 =C2=A0 "implement for" values since the general interp= retation to date
>=C2=A0 =C2=A0 indicates they have been treated as values for both "= ;implementation"
>=C2=A0 =C2=A0 and "use".=C2=A0 We note that the values for &q= uot;Implement for" and "Use for"
>=C2=A0 =C2=A0 may diverge in the future.
>
> The above text indicates that the "Implement for" and "= Use for" columns should
> have identical values. However, when I look at Table 2, there are diff= erences
> between the values in the "Implement for" and the "Use = for" for number 5, 7, 8,
> 10 and 13, For example, in number 5 where Use for DNSSEC Validation is=
> "RECOMMEND" but the Implement for DNSSEC Validation is "= ;MUST"

That's a good point and we don't discuss it in the document.=C2=A0 = The WG
wished to not use MUST and MUST-NOT for the Use for column, so we
replaced them with RECOMMENDED.=C2=A0 As such, I added a sentence to the document that now says:

=C2=A0 =C2=A0Note that the "Use for" columns values use "REC= OMMENDED" when the
=C2=A0 =C2=A0corresponding "Implement for" column is a "MUST= " value.

Does that work for you?
--
Wes Hardaker
USC/ISI

_______________________________________________
OPS-DIR mailing list -- ops-dir@ietf.org
To unsubscribe send an email to ops-dir-leave@ietf.org


--
Nabeel = Cocker
Senior Principal Architect, Global Tel= co Consulting=C2=A0Practice

M: +1-845-240-2587=C2=A0 =C2=A0

Emai= l: ncocker@redhat.c= om=C2=A0



--
Nabeel = Cocker
Senior Principal Architect, Global Tel= co Consulting=C2=A0Practice

M: +1-845-240-2587=C2=A0 =C2=A0

Emai= l: ncocker@redhat.c= om=C2=A0

--0000000000005aa953063369ad35--