+1 to turning Domain Connect I-D into a standard track RFC will be helpful for the community. I work in the email space and the DKIM, SPF, DMARC and the nascent "DKIM2" authentication protocols need to be published to DNS. A blessed Domain Connect standard can help with its availability and that will make it easier for senders to deploy email authentication. Agreed that having its own WG will facilitate this work. -Wei
On Thu, Apr 24, 2025 at 12:21 AM Pawel Kowalik <kowa...@denic.de> wrote: > Hi, > > After the AD decision not to proceed with the domain connect draft as > AD-sponsored the preferred way forward seems to be forming a working > group tasked with this work. > > Orie asked me to propose a charter text and initiate the discussion here. > > I kept the charter in a very narrow scope, so that this potentially new > working group can finish the work in a foreseeable timeframe. > > > Please feel free to comment in the document directly or provide feedback > over the mailing list. > > https://docs.google.com/document/d/1fDVD4RoJ0vHJ5CsSlshZpzm5dfq145sb > > > There was a number of people, who expressed interest for this work and > in the potential working group in the previous discussion. > > A feedback or even +1 would be of a value. Thanks. > > > PS: cross-posting to all working groups with potential interest, but > please just post (and subscribe) to dconn mailing list when responding. > > Kind Regards, > > Pawel > > _______________________________________________ > art mailing list -- a...@ietf.org > To unsubscribe send an email to art-le...@ietf.org >
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
