Re: [DNSOP] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-01.txt

On 2019-05-12 23:51 -0500, Jim Reid wrote: [Unless Telnic's T&Cs have changed, registrants can't delegate these names to arbitrary name servers.] This has changed. As written on frontpage of registry website: "Now also available as a generic anything-you-want-it-to-be top-level domain"

Re: [DNSOP] ANAME in answer or additional section [issue #62]

On Wed, Jun 12, 2019 at 1:11 AM Matthijs Mekking wrote: > Brian, > > Thanks for the detailed background on why DNAME worked. There are a few > things that caught my attention: > > > When a recursive queried an authority server, if it got back a DNAME > but did not understand it, it ignored the DN

Re: [DNSOP] ANAME in answer or additional section [issue #62]

Hey Matthijs, On 12 Jun 2019, at 04:11, Matthijs Mekking wrote: > Thanks for the detailed background on why DNAME worked. There are a few > things that caught my attention: > >> When a recursive queried an authority server, if it got back a DNAME >> but did not understand it, it ignored the DNA

Re: [DNSOP] ANAME in answer or additional section [issue #62]

On Thu, Jun 13, 2019 at 1:50 PM Brian Dickson wrote: > > > On Wed, Jun 12, 2019 at 1:11 AM Matthijs Mekking > wrote: > >> Brian, >> >> Thanks for the detailed background on why DNAME worked. There are a few >> things that caught my attention: >> >> > When a recursive queried an authority server,

Re: [DNSOP] ANAME in answer or additional section [issue #62]

On Thu, Jun 13, 2019 at 1:51 PM Bob Harold wrote: > > On Thu, Jun 13, 2019 at 1:50 PM Brian Dickson < > brian.peter.dick...@gmail.com> wrote: > >> >> >> On Wed, Jun 12, 2019 at 1:11 AM Matthijs Mekking >> wrote: >> >>> Brian, >>> >>> Thanks for the detailed background on why DNAME worked. There

[DNSOP] Verifying TLD operator authorisation

I'm working on a system that needs to authenticate a TLD owner/operator in order to take specific actions. We had intended to handle this by requiring them to publish a token in a TXT record under a subdomain of nic.tld, but it's been brought to our attention that we can't rely on nic.tld being own

Re: [DNSOP] Verifying TLD operator authorisation

On Jun 13, 2019, at 22:18, Nick Johnson wrote: > I'm working on a system that needs to authenticate a TLD owner/operator in > order to take specific actions. Can you give an example of the actions? When you say "owner/operator" what exactly do you mean? > We had intended to handle this by req

Re: [DNSOP] Verifying TLD operator authorisation

On Fri, Jun 14, 2019 at 2:30 PM Joe Abley wrote: > On Jun 13, 2019, at 22:18, Nick Johnson > wrote: > > > I'm working on a system that needs to authenticate a TLD owner/operator > in order to take specific actions. > > Can you give an example of the actions? > We build and maintain ENS, a namin

Re: [DNSOP] Verifying TLD operator authorisation

> On 13 Jun 2019, at 23:18, Nick Johnson > wrote: > > I'm working on a system that needs to authenticate a TLD owner/operator in > order to take specific actions. We had intended to handle this by requiring > them to publish a token in a TXT record under a subdomain of nic.tld, but > it's b

Re: [DNSOP] Verifying TLD operator authorisation

On Fri, Jun 14, 2019 at 2:51 PM Rubens Kuhl wrote: > > > On 13 Jun 2019, at 23:18, Nick Johnson > wrote: > > I'm working on a system that needs to authenticate a TLD owner/operator in > order to take specific actions. We had intended to handle this by requiring > them to publish a token in a TXT

Re: [DNSOP] Verifying TLD operator authorisation

> On 13 Jun 2019, at 23:56, Nick Johnson wrote: > > On Fri, Jun 14, 2019 at 2:51 PM Rubens Kuhl > wrote: > > >> On 13 Jun 2019, at 23:18, Nick Johnson > > wrote: >> >> I'm working on a system that needs to authenticate a TLD

Re: [DNSOP] Verifying TLD operator authorisation

On Fri, Jun 14, 2019 at 3:02 PM Rubens Kuhl wrote: > > > On 13 Jun 2019, at 23:56, Nick Johnson wrote: > > On Fri, Jun 14, 2019 at 2:51 PM Rubens Kuhl wrote: > >> >> >> On 13 Jun 2019, at 23:18, Nick Johnson < >> nick=40ethereum@dmarc.ietf.org> wrote: >> >> I'm working on a system that need