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

Return-Path: <sm@elandsys.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCDC53A0D0F; Tue, 12 May 2020 19:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GIgmtfFwLUQB; Tue, 12 May 2020 19:21:27 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id BFD033A0D18; Tue, 12 May 2020 19:21:27 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.46.37]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 04D2L7MR001837 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 May 2020 19:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1589336480; x=1589422880; i=@elandsys.com; bh=LHCh54uz1qZfikSAcPGhQD3IzK5sIrfQDOLoZF/IcQs=; h=Date:To:From:Subject:In-Reply-To:References; b=CMa2xOvoRUUqAQ/qH7QYoH4O8lJmGepd7Sja+RNr2mS/8O0en/XjLDe3fhM+9wlmp gcTCanaXgqJdXG64O+rGMV/lxmefjd+/U1k47EZt8YX6d4OzC8wQf1i6k2ZogFa9ty XuM2VWdCH6efw+PA3+LVDJzC3kfHiMKDM/8nCtEs=
Message-Id: <6.2.5.6.2.20200512191150.0bafa9a0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
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
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2020 02:21:34 -0000

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