Re: [arch-d] Liaison reports (was: Domain-based Message Authentication, Reporting & Conformance (dmarc) WG Virtual Meeting: 2020-06-11)
Mirja Kuehlewind <ietf@kuehlewind.net> Thu, 14 May 2020 21:08 UTC
Return-Path: <ietf@kuehlewind.net>
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 D19243A0DC0; Thu, 14 May 2020 14:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 4TEeqM7F9-Ho; Thu, 14 May 2020 14:08:37 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F1253A0DD1; Thu, 14 May 2020 14:08:31 -0700 (PDT)
Received: from p200300dee7007a00184ff4f5f7fc0bb9.dip0.t-ipconnect.de ([2003:de:e700:7a00:184f:f4f5:f7fc:bb9]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1jZL5W-0005yZ-57; Thu, 14 May 2020 23:08:18 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <6.2.5.6.2.20200513140922.0aebf148@elandnews.com>
Date: Thu, 14 May 2020 23:08:17 +0200
Cc: architecture-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3AE398D-7BBF-4187-BEB4-9F3B55463662@kuehlewind.net>
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> <6.2.5.6.2.20200512191150.0bafa9a0@elandnews.com> <9161f68e-f51b-f97b-fc2b-372d24404209@cs.tcd.ie> <CAL0qLwZQxM+eDeZ+zFw3Gny7sy=jXi-1aUvE1B2RuO=M5CP_Sw@mail.gmail.com> <6.2.5.6.2.20200512232644.0d9328c8@elandnews.com> <CALaySJKs9oLXBN_UVq=Mn5ZefvrSgPyrV1J=1NMA0=YVDRnJVA@mail.gmail.com> <6.2.5.6.2.20200513081326.0ababe28@elandnews.com> <CALaySJKG7+g7u4p92axbZx4AxhwZgNfgfeHhE708EVpLs+iJjQ@mail.gmail.com> <6.2.5.6.2.20200513101502.0b0c7c90@elandnews.com> <CALaySJ++dWefRF5rbc0Fxp6wAFWJJH0rMt9u_5gv9BxN2adKbw@mail.gmail.com> <6.2.5.6.2.20200513140922.0aebf148@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1589490511;3c6c896b;
X-HE-SMSGID: 1jZL5W-0005yZ-57
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/suR690b4kIsdM752z7j6370fu9I>
Subject: Re: [arch-d] Liaison reports (was: 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: Thu, 14 May 2020 21:08:46 -0000
Hello S. Moonesamy, Thanks for pointing this out. It seems that the page was not correctly taken over when the IAB webpage was moved to a new system in 2011. The pages are restored now. However, as you can see and as noticed on the IAB liaison page itself, we don’t have the practice of collecting periodic report anymore, for a while already. As noted by Wes already, if reports are sent to the IAB or if liaison managers directly report in an IAB meeting, these are noted and published in the minutes instead. Mirja > On 13. May 2020, at 23:31, S Moonesamy <sm+ietf@elandsys.com> wrote: > > Dear IAB Chair, > > I was searching for liaison reports. Unfortunately, the link on the IAB web site ( https://www.iab.org/liaisons/liaison-mgr-reports/ ) is not working correctly. I assume that the openness (Section 3.6 of RFC 2850) allows for those reports to be published. Such reports could be useful information to people responding to IAB requests for comments on the IAB appointments. > > I would appreciate if the IAB could consider my request to publish all the liaison reports. > > Regards, > S. Moonesamy > > _______________________________________________ > Architecture-discuss mailing list > Architecture-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/architecture-discuss >
- 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