Re: [arch-d] Domain-based Message Authentication, Reporting & Conformance (dmarc) WG Virtual Meeting: 2020-06-11

S Moonesamy <sm+ietf@elandsys.com> Tue, 12 May 2020 22:54 UTC

Message-Id: <6.2.5.6.2.20200512152625.124c1588@elandnews.com>
Date: Tue, 12 May 2020 15:47:15 -0700
To: iab@iab.org, architecture-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <158920530782.23655.6622928751672901506@ietfa.amsl.com>
References: <158920530782.23655.6622928751672901506@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/xp4QvWMT3EmdH95AQMvD6LYVu7w>
Subject: Re: [arch-d] Domain-based Message Authentication, Reporting & Conformance (dmarc) WG Virtual Meeting: 2020-06-11
Precedence: list

Dear Internet Architecture Board,
At 06:55 AM 11-05-2020, IESG Secretary wrote:
>The Domain-based Message Authentication, Reporting & Conformance 
>(dmarc) Working Group will hold
>a virtual interim meeting on 2020-06-11 from 16:00 to 17:00 UTC.
>
>Agenda:
>Joint DMARC 2.0 Discussion (M3AAWG and IETF)

During a discussion in an IETF Working Group it was argued that the 
working group is a standards development organization.  I am 
subscribed to several IETF mailing lists.  It is the first time I 
heard such a statement.

I was a bit surprised to read the above announcement about a meeting 
between an external organization and an IETF Working Group which is 
described as a discussion between the external organization and the 
IETF.  I could not find any recent liaison communication between the 
external organization and the IETF.  Would it be possible to share a 
summary of the discussions which led to the above interim meeting?

Regards,
S. Moonesamy

Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Stephen Farrell
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Stephen Farrell
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Stephen Farrell
Re: [arch-d] Domain-based Message Authentication,… Murray S. Kucherawy
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Murray S. Kucherawy
Re: [arch-d] Domain-based Message Authentication,… Barry Leiba
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Barry Leiba
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Barry Leiba
[arch-d] Liaison reports (was: Domain-based Messa… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Murray S. Kucherawy
Re: [arch-d] Liaison reports Wes Hardaker
Re: [arch-d] Liaison reports S Moonesamy
Re: [arch-d] Liaison reports Guntur Wiseno Putra
Re: [arch-d] Liaison reports Guntur Wiseno Putra
Re: [arch-d] Liaison reports S Moonesamy
Re: [arch-d] Liaison reports (was: Domain-based M… Mirja Kuehlewind
Re: [arch-d] Liaison reports (was: Domain-based M… S Moonesamy
Re: [arch-d] Liaison reports (was: Domain-based M… Bob Hinden
Re: [arch-d] Liaison reports (was: Domain-based M… Mirja Kuehlewind
Re: [arch-d] Liaison reports Alexandre Petrescu
Re: [arch-d] Liaison reports Wes Hardaker
Re: [arch-d] Liaison reports S Moonesamy
Re: [arch-d] Liaison reports Wes Hardaker
Re: [arch-d] Liaison reports S Moonesamy
Re: [arch-d] Liaison reports (was: Domain-based M… Spencer Dawkins at IETF
Re: [arch-d] Liaison reports Spencer Dawkins at IETF
Re: [arch-d] Liaison reports Mirja Kuehlewind