Dear DNSOP,
As laid out at the DNSOP session on Tuesday,
draft-ietf-dnsop-generalized-notify (and also
draft-johani-dnsop-delegation-mgmt-via-ddns) require a method for locating the
parent-side endpoint (target) where the child DNS operator can send a NOTIFY
for DS update (or other kind of si
None of the above. Do what RFC 2136 does to send updates to the primary
authority, or do what RFC 1996 does to send notifications to all listed
authorities. Any new signaling is effectively a way to go out of band. The
system is complete as it is.
p vixie
On Nov 8, 2023 12:06, Peter Thomas
It appears that Paul Vixie said:
>-=-=-=-=-=-
>None of the above. Do what RFC 2136 does to send updates to the primary
>authority, or do what RFC 1996
>does to send notifications to all listed authorities. Any new signaling is
>effectively a way to go out
>of band. The system is complete as it
On 8 Nov 2023, at 18:50, John Levine wrote:
> It appears that Paul Vixie said:
>> -=-=-=-=-=-
>> None of the above. Do what RFC 2136 does to send updates to the primary
>> authority, or do what RFC 1996
>> does to send notifications to all listed authorities. Any new signaling is
>> effectiv
Hi all,
I am sorry not to be in Prague this week but I'm happy to hear that some of the
ideas that led me to write draft-jabley-dnsop-refer-00 a couple of years ago
have resurfaced, including I think the idea of signalling available transports
for a child along with the delegation which had als
It appears that Paul Vixie said:
-=-=-=-=-=-
None of the above. Do what RFC 2136 does to send updates to the primary
authority, or do what RFC 1996
does to send notifications to all listed authorities. Any new signaling is
effectively a way to go out
of band. The system is complete as it i
On Wed, Nov 8, 2023 at 7:20 PM Joe Abley wrote:
>
>
> Since I wasn't at the hackathon (and since there is no sign of related
> discussion about this on this list) I assume a lot of the ideas are being
> shared over beer. But if there's a mailing list or something else going on,
> I'd be intereste
On 8 Nov 2023, at 19:39, John R Levine wrote:
>
>>
>>
>>> It appears that Paul Vixie said:
-=-=-=-=-=-
None of the above. Do what RFC 2136 does to send updates to the primary
authority, or do what RFC 1996
does to send notifications to all listed authorities. Any new s
On Wed, 8 Nov 2023, Joe Abley wrote:
I think the idea is that these two existing and well-implemented mechanisms
should be considered first to see if they fit before anybody goes to the
trouble of inventing new ones.
The most likely use case for this stuff is for a domain registrant to
updat
I think what we have here is (as Daffy Duck famously put it) "pronoun
trouble".
The target for a NOTIFY would necessarily be found in the SOA record of the
registrant's zone, not the parent's zone. I think that's where the
confusion has arisen.
The SOA record would need to be initially configured
10 matches
Mail list logo
