> On Dec 24, 2021, at 11:27 AM, Benjamin Kaduk wrote:
>
> Caution: This email originated from outside the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
> Hi Duane,
>
> Sorry for the very delayed response.
> I will g
Hi Duane,
Sorry for the very delayed response.
I will go update my ballot position shortly, but please see
https://github.com/jtkristoff/draft-ietf-dnsop-dns-tcp-requirements/pull/11
for some further edits to the text for discuss point (1).
On Mon, Nov 08, 2021 at 10:35:21PM +, Wessels, Duane
> On Nov 8, 2021, at 4:24 PM, Joe Abley wrote:
>
> Caution: This email originated from outside the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
> On Nov 8, 2021, at 17:35, Wessels, Duane
> wrote:
>
>> Is this bet
On Nov 8, 2021, at 17:35, Wessels, Duane
wrote:
> Is this better?
>
> The use of TLS places even stronger operational burdens on DNS
> clients and servers. Cryptographic functions for authentication and
> encryption requires additional processing.
Require, not requires. I know, I know.
Hi Ben, thank you for the detailed review. It has taken me a while to work
through
all of your comments and suggestions, but hopefully this addresses them
sufficiently.
> On Oct 25, 2021, at 3:51 PM, Benjamin Kaduk via Datatracker
> wrote:
>
>
> ---
Benjamin Kaduk has entered the following ballot position for
draft-ietf-dnsop-dns-tcp-requirements-13: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please re