Re: [DNSOP] Webex details Re: correction Re: virtual interim DNSOP WG meeting and current status, special use names

Will the jabber room at dn...@jabber.ietf.org also be used? Scott From: DNSOP [mailto:dnsop-boun...@ietf.org] On Behalf Of Suzanne Woolf Sent: Wednesday, February 15, 2017 6:50 PM To: dnsop Subject: [EXTERNAL] [DNSOP] Webex details Re: correction Re: virtual in

Re: [DNSOP] Call for Adoption: draft-huque-dnsop-multi-provider-dnssec

> -Original Message- > From: DNSOP On Behalf Of Petr Špacek > Sent: Tuesday, July 17, 2018 7:19 AM > To: dnsop@ietf.org > Subject: [EXTERNAL] Re: [DNSOP] Call for Adoption: draft-huque-dnsop- > multi-provider-dnssec > > On 14.7.2018 06:12, Shumon Huque wrote: > >> On Tue, Jul 10, 2018 at 1

[DNSOP] FW: [regext] WGLC: draft-ietf-regext-datadictionary-03

This may be of interest to dnsop folks, too. At least two of the terms included in this dictionary ("Domain Name" and "NS") are commonly used in DNS specifications. Scott > -Original Message- > From: regext On Behalf Of James Galvin > Sent: Monday, February 6, 2023 9:40 AM > To: REGEXT

Re: [DNSOP] [Ext] WGLC rfc8499bis one week extension for lame delegation definition

> -Original Message- > From: DNSOP On Behalf Of Wessels, Duane > Sent: Monday, May 1, 2023 12:43 PM > To: Paul Hoffman > Cc: DNSOP Working Group > Subject: [EXTERNAL] Re: [DNSOP] [Ext] WGLC rfc8499bis one week extension > for lame delegation definition > > Caution: This email originated

[DNSOP] FW: New Version Notification for draft-hollenbeck-regext-epp-delete-bcp-00.txt

pp-delete-bcp Thanks for your attention, Scott > -Original Message- > From: internet-dra...@ietf.org > Sent: Friday, June 23, 2023 10:57 AM > To: Hollenbeck, Scott ; Carroll, William > > Subject: [EXTERNAL] New Version Notification for > draft-hollenbeck-rege

Re: [DNSOP] FW: New Version Notification for draft-hollenbeck-regext-epp-delete-bcp-00.txt

> -Original Message- > From: Andrew Newton > Sent: Tuesday, June 27, 2023 10:18 AM > To: Hollenbeck, Scott > Cc: reg...@ietf.org; dnsop@ietf.org > Subject: [EXTERNAL] Re: [DNSOP] FW: New Version Notification for draft- > hollenbeck-regext-epp-delete-bcp-00.txt &g

[DNSOP] Best Practices for Managing Existing Delegations When Deleting a Domain or Host

Folks, we could really use feedback from people with DNS expertise to help document a set of best practices for managing existing DNS delegations at the TLD level when EPP domain and host objects are deleted. As described in this draft: https://datatracker.ietf.org/doc/draft-hollenbeck-regext-e

Re: [DNSOP] Best Practices for Managing Existing Delegations When Deleting a Domain or Host

Thanks for the feedback, Brian. Notes below… From: Brian Dickson Sent: Tuesday, July 11, 2023 6:23 PM To: Hollenbeck, Scott Cc: dnsop@ietf.org Subject: [EXTERNAL] Re: [DNSOP] Best Practices for Managing Existing Delegations When Deleting a Domain or Host Caution: This email originated

Re: [DNSOP] Best Practices for Managing Existing Delegations When Deleting a Domain or Host

> -Original Message- > From: Andrew Newton > Sent: Thursday, July 13, 2023 1:00 PM > To: Hollenbeck, Scott > Cc: brian.peter.dick...@gmail.com; dnsop@ietf.org; Registration Protocols > Extensions > Subject: [EXTERNAL] Re: [DNSOP] Best Practices for Managing Existi

Re: [DNSOP] WGLC rfc8499bis for revised lame delegation definition

> -Original Message- > From: DNSOP On Behalf Of k claffy > Sent: Tuesday, July 18, 2023 12:41 AM > To: George Michaelson > Cc: Benno Overeinder ; DNSOP Working Group > ; DNSOP Chairs > Subject: [EXTERNAL] Re: [DNSOP] WGLC rfc8499bis for revised lame > delegation definition > > Caution: T

Re: [DNSOP] I-D Action: draft-hollenbeck-regext-epp-delete-bcp-01.txt

> -Original Message- > From: I-D-Announce On Behalf Of > internet-dra...@ietf.org > Sent: Tuesday, September 19, 2023 12:02 PM > To: i-d-annou...@ietf.org > Subject: [EXTERNAL] I-D Action: draft-hollenbeck-regext-epp-delete-bcp- > 01.txt > > Caution: This email originated from outside the

Re: [DNSOP] I-D Action: draft-hollenbeck-regext-epp-delete-bcp-01.txt

> -Original Message- > From: DNSOP On Behalf Of Hollenbeck, Scott > Sent: Tuesday, September 19, 2023 12:17 PM > To: reg...@ietf.org; dnsop@ietf.org > Subject: [EXTERNAL] Re: [DNSOP] I-D Action: draft-hollenbeck-regext-epp- > delete-bcp-01.txt [SAH] [snip] > This d

Re: [DNSOP] IETF 118 Call for Agenda Items DNSOP WG

Benno, could I have 5 minutes to discuss the delegation management aspects of my EPP object deletion draft? Scott > On Oct 18, 2023, at 12:04 PM, Benno Overeinder wrote: > > Caution: This email originated from outside the organization. Do not click > links or open attachments unless you reco

Re: [DNSOP] [dbound] Related Domains By DNS (RDBD) Draft

> -Original Message- > From: DNSOP On Behalf Of Stephen Farrell > Sent: Wednesday, February 27, 2019 11:15 AM > To: Paul Wouters ; Brotman, Alexander > > Cc: a...@ietf.org; dnsop@ietf.org; dbo...@ietf.org > Subject: [EXTERNAL] Re: [DNSOP] [dbound] Related Domains By DNS (RDBD) > Draft > >

[DNSOP] Security Considerations Suggestion for draft-ietf-dnsop-rfc7816bis

I've recently been reading draft-ietf-dnsop-rfc7816bis and I'd like to propose some additional text for the Security Considerations section in the spirit of this sentence from the abstract: "Future versions of this draft will contain descriptions of different minimisation implementation choices

Re: [DNSOP] Security Considerations Suggestion for draft-ietf-dnsop-rfc7816bis

> -Original Message- > From: Olafur Gudmundsson > Sent: Wednesday, July 10, 2019 6:29 PM > To: Hollenbeck, Scott > Cc: dnsop@ietf.org > Subject: [EXTERNAL] Re: [DNSOP] Security Considerations Suggestion for > draft-ietf-dnsop-rfc7816bis > > > Hi Scott, some

[DNSOP] DNS for Cloud Resources in draft-ietf-rtgwg-net2cloud-problem-statement-08

(Sorry, this is a late response to a review request original sent to the dnsop list on 11 February) Section 3.4 (DNS for Cloud Resources) includes these sentences: "Globally unique names do prevent any possibility of collision at the present or in the future and they make DNSSEC trust manageabl

Re: [DNSOP] DNS for Cloud Resources in draft-ietf-rtgwg-net2cloud-problem-statement-08

You're welcome, and thanks for accepting the suggestion. Scott > -Original Message- > From: Linda Dunbar > Sent: Wednesday, March 18, 2020 6:54 PM > To: Hollenbeck, Scott > Cc: dnsop@ietf.org; rt...@ietf.org > Subject: [EXTERNAL] RE: DNS for Cloud Resour

[DNSOP] Security Considerations Suggestion for draft-ietf-dnsop-rfc7816bis

I originally sent this to the list last July. Olafur provided some feedback (which has been incorporated into the text suggested below), but it seems to have slipped past the document editors. Trying again since the document has been revived after it recently expired... I've recently been readi

Re: [DNSOP] [Ext] Security Considerations Suggestion for draft-ietf-dnsop-rfc7816bis

> -Original Message- > From: Paul Hoffman > Sent: Tuesday, March 31, 2020 11:01 AM > To: Hollenbeck, Scott > Cc: dnsop@ietf.org > Subject: [EXTERNAL] Re: [Ext] [DNSOP] Security Considerations Suggestion > for draft-ietf-dnsop-rfc7816bis > > On Mar 31, 2020, at

[DNSOP] draft-ietf-dnsop-rfc7816bis: More Results for the Experiment

Yesterday, Verisign published a blog post [1] that includes a description of the growth rate of QNAME-minimized queries that we've seen at the A and J root servers and the .COM and .NET name servers since 2018. Section 8 of draft-ietf-dnsop-rfc7816bis ("Results of the Experimentation") doesn't

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-rfc7816bis

I support publication of this document. I do have some "last call" feedback to share: Section 2, paragraph 4 states that "A resolver that implements QNAME minimisation changes the QNAME and QTYPE in queries directed to an authoritative nameserver that is not known to be responsible for the orig

Re: [DNSOP] SVCB without A/AAAA records at the service name

From: DNSOP On Behalf Of Ben Schwartz Sent: Tuesday, January 19, 2021 10:01 PM To: Martin Thomson Cc: dnsop Subject: [EXTERNAL] Re: [DNSOP] SVCB without A/ records at the service name On Tue, Jan 19, 2021 at 7:40 PM Martin Thomson mailto:m...@lowentropy.net>> wrote: On Wed, Jan 2

Re: [DNSOP] SVCB without A/AAAA records at the service name

From: Ben Schwartz Sent: Friday, January 22, 2021 1:29 PM To: Hollenbeck, Scott Cc: m...@lowentropy.net; dnsop@ietf.org Subject: [EXTERNAL] Re: Re: [DNSOP] SVCB without A/ records at the service name On Fri, Jan 22, 2021 at 12:43 PM Hollenbeck, Scott mailto:40verisign

Re: [DNSOP] SVCB without A/AAAA records at the service name

From: Ben Schwartz Sent: Monday, January 25, 2021 5:04 PM To: Hollenbeck, Scott Cc: m...@lowentropy.net; dnsop@ietf.org Subject: [EXTERNAL] Re: Re: Re: [DNSOP] SVCB without A/ records at the service name On Mon, Jan 25, 2021 at 8:06 AM Hollenbeck, Scott mailto:40verisign

Re: [DNSOP] New version of draft-ietf-dnsop-rfc7816bis after WG last call

> -Original Message- > From: DNSOP On Behalf Of Paul Hoffman > Sent: Thursday, April 15, 2021 7:15 PM > To: DNSOP Working Group > Subject: [EXTERNAL] [DNSOP] New version of draft-ietf-dnsop-rfc7816bis > after WG last call > > Greetings again. We have posted a very delayed version draft-ie

Re: [DNSOP] Empty Non-Terminal sentinel for Black Lies

From: DNSOP On Behalf Of Shumon Huque Sent: Tuesday, July 27, 2021 7:35 PM To: dnsop@ietf.org WG Subject: [EXTERNAL] [DNSOP] Empty Non-Terminal sentinel for Black Lies Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the