Re: [arch-d] Liaison reports

S Moonesamy <sm+ietf@elandsys.com> Wed, 20 May 2020 22:56 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 4D5913A08CD; Wed, 20 May 2020 15:56:52 -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 4FAxc4luwUzA; Wed, 20 May 2020 15:56:48 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id DE8733A08C7; Wed, 20 May 2020 15:56:32 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.33.18]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 04KMuBib023518 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 May 2020 15:56:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1590015383; x=1590101783; i=@elandsys.com; bh=92Ec2dkN6kucXQq/r4P974S25VJ4/DSJwo7XyaFPMQo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=U8D1QqOttcEXqoaCMiwoaX1GJTdeVbwNN/gyvq983g4gQGfUI2/ec8hPdnmNapTj6 ovzc/OL6d6daeMGu9ygxy2w0vJSwk9X/rZv1LzwNSB+5D43pR9p/H16ioMWNZb363Q Pb6AtIraQxM3jKy+QgjLuW7Xbk1oGfUAW4yY8Xxg=
Message-Id: <6.2.5.6.2.20200520152717.0b1464e0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 20 May 2020 15:54:05 -0700
To: Wes Hardaker <wjhns1@hardakers.net>, architecture-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: iab-chair@iab.org
In-Reply-To: <yblh7wafnd5.fsf@w7.hardakers.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> <ybld077uw6f.fsf@w7.hardakers.net> <6.2.5.6.2.20200513212345.0afe2f10@elandnews.com> <yblh7wafnd5.fsf@w7.hardakers.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/EbVztf5RULNgNMVB_KFZd8hWZAw>
Subject: Re: [arch-d] Liaison reports
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, 20 May 2020 22:56:52 -0000

Hi Wes,
At 11:54 AM 20-05-2020, Wes Hardaker wrote:
>I think someone already answered you, but I don't see it in the response
>thread, so just to be absolutely certain your question doesn't go
>unanswered: the iab website did indeed have a bug wrt liason statements
>being listed in the menu and is now fixed.
>
>https://www.iab.org/liaisons/liaison-mgr-reports/

Thanks for making those liaison notes available.

Regards,
S. Moonesamy