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 23:47 UTC

Message-Id: <6.2.5.6.2.20200512162358.0b239160@elandnews.com>
Date: Tue, 12 May 2020 16:46:28 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, iab@iab.org, architecture-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <d798d383-9bab-50f8-b6ee-dabb9cc37c2a@cs.tcd.ie>
References: <158920530782.23655.6622928751672901506@ietfa.amsl.com> <6.2.5.6.2.20200512152625.124c1588@elandnews.com> <d798d383-9bab-50f8-b6ee-dabb9cc37c2a@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/l_CQSffRTRupi9-Dl-dp50CKhiw>
Subject: Re: [arch-d] Domain-based Message Authentication, Reporting & Conformance (dmarc) WG Virtual Meeting: 2020-06-11
Precedence: list

Hi Stephen,
At 04:15 PM 12-05-2020, Stephen Farrell wrote:
>I'm not seeing why this is an IAB matter. Current IETF
>WGs are looked after by the IESG.

I'll list a two points:

   (a) The liaison relationships with external organizations are 
managed by the IAB.

   (b) The liaison representatives who speak on behalf of the IETF 
fall under the IAB.

I understand that existing IETF Working Groups fall under the 
IESG.  However, asking the IESG about a matter which falls under the 
IAB could be viewed as the IAB not having any role in (a) or (b).

Out of curiosity, what are the specific responsibilities of the 
liaison representative in the current case?

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