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

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

Message-Id: <6.2.5.6.2.20200513140922.0aebf148@elandnews.com>
Date: Wed, 13 May 2020 14:31:28 -0700
To: iab-chair@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: architecture-discuss@ietf.org
In-Reply-To: <CALaySJ++dWefRF5rbc0Fxp6wAFWJJH0rMt9u_5gv9BxN2adKbw@mail.g mail.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/shz8nmDJyK_J3GDm0P4gnsXOQ4o>
Subject: [arch-d] Liaison reports (was: Domain-based Message Authentication, Reporting & Conformance (dmarc) WG Virtual Meeting: 2020-06-11)
Precedence: list

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

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