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

S Moonesamy <sm+ietf@elandsys.com> Wed, 13 May 2020 02:21 UTC

Message-Id: <6.2.5.6.2.20200512191150.0bafa9a0@elandnews.com>
Date: Tue, 12 May 2020 19:20:47 -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: <4548adba-834c-bfdd-36af-66b367408df8@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> <6.2.5.6.2.20200512162358.0b239160@elandnews.com> <4548adba-834c-bfdd-36af-66b367408df8@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/gXpDa-p66CBRhBa1636mf4aulf0>
Subject: Re: [arch-d] Domain-based Message Authentication, Reporting & Conformance (dmarc) WG Virtual Meeting: 2020-06-11
Precedence: list

Hi Stephen,
At 04:59 PM 12-05-2020, Stephen Farrell wrote:
> > Â  (b) The liaison representatives who speak on behalf of the IETF fall
> > under the IAB.
>
>Well, I'm not sure anyone speaks "on behalf of" the IETF;-)

A definition of "representative" is "a person 
chosen or appointed to act or speak for another 
or others".  RFC 4052 describes the liaison 
manager as "a representative of the IETF".  By my 
reading, that means that the person is speaking on behalf of the IETF.

>In practice, I'd say it's usually better to chat with a WG
>chair or AD as the relevant bits of liaising are more
>likely to be front of their minds and to treat the IAB as a
>fallback if stuff's not happening.

Ok.

>Not sure - you never said which is the other organisation
>nor what may be up between us and them.

The name (M3AAWG) was in the first email which I sent.

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