[art] Re: Domain Connect Protocol

[[e-mail]]

Hi Stephen,

Answers inline.

On 21.10.24 21:27, Stephen Farrell wrote:
>
> Hiya,
>
> I had a quick scan and have a couple of initial questions:
>
> I'm working on [1] so wonder if/how those may be related, any
> idea? If not, should they be?

They are in a sense that they address the same problem of one party 
wanting to put an update to the DNS outside of its realm.

Domain connect solves it by pushing the updates from the party (service 
provider) to the DNS operator. It can be one time or permanent (with 
OAuth). It also addresses the whole process of DNS operator discovery, 
authorisation flow and standard API.

draft-ietf-tls-wkech seems to approach it by DNS operator pulling the 
data from the other party. It's OK for a server operator not willing to 
expose any API and seems to me a complementary approach to domain 
connect for this specific situation. I don't see any obvious overlap or 
common parts between the two drafts.

I understand the link between ZF and backend is configured out-of-band. 
Domain connect defines a way to have fully automated setup process. 
Maybe here an extension of domain connect could 
complement draft-ietf-tls-wkech through pseudo-records, similar as 
redirects are also specified in the extension part.

>
> I'm also not clear on the status of this - is this a case of
> wanting to get something long-used under IETF change control
> or something else?

Yes, to get something long-used under IETF change control is the goal.

Kind Regards,

Pawel