Re: [arch-d] Liaison reports

Spencer Dawkins at IETF <> Tue, 02 June 2020 15:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 585093A0B37 for <>; Tue, 2 Jun 2020 08:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YvBgo-0AIQbq for <>; Tue, 2 Jun 2020 08:34:51 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6F3AC3A0B42 for <>; Tue, 2 Jun 2020 08:34:40 -0700 (PDT)
Received: by with SMTP id n23so2390912ljh.7 for <>; Tue, 02 Jun 2020 08:34:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N2FAMcX853IskSkXoJXiAYTr/NyvGNopMm7bhn/5ML8=; b=tvZC8wo4TiQ0SXxT2gtVCjkPOq0JP/hC45P2MbNmpYoHSAErU6jwrDjs5vdk80Lg3Q 7qJtZ5rdA8Alnx0az6wXMIow7Mx0pQ4EoV+LyeH4BQqtb1ksPSqy7eceEcEf6rsHUnmr B9kgZpsXSpywt/24kGRTNqA383FX9tnpf2ynMMlVEctnjv0r25CZdy5WQV/P9Gfvmqoi 0GTthBuwtHOORj4BzOWSns69l9rhTM4iR/EoZQljQAnND6rqoUFUwTG/xT2uQ7Ge3E2H iNhw0QXTXJ/i5ytFU5cqTWRxTjgPOB0PQLpHpcnqyYeaNOT+qqxrM2hEM9feBdlaDQWG 6PfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N2FAMcX853IskSkXoJXiAYTr/NyvGNopMm7bhn/5ML8=; b=bKQPmY7vzhHpi96eaOPE72IMgGH1H5e7+dd6QB45ps/VhyOEkJ0hGgLvxtC7mUE2aB CzZ7QfiZkIohrWnnWKk65eBw942AU6fHHHlxvPlzlj5yx0j7yp35L6D6TABnF4ytU46e ywbVMOX9IGR75/zGNLzbgc9yLgyNJzBs8IBckVoGqtNwX15v7maAeEfZH9cbNKxmqzmE RbHa167vlEWBpZpoJPF6EtiLwgbJPP/hCCSA9q/eOSP/cmWLQjXbN+Wf8TUpvv7rV1PT H8t5PV25IxYJ1bxylONcVojy2Hq+E47ikcrIayVW7LkGaqPUROXA/3CYMA2U1KeNP0Dc WB/A==
X-Gm-Message-State: AOAM533W+OgMn+yDE19fArBv1pAPj+YUUIsiKcoBmdQi7ault+jekw6G kQmM9hm/4cCm1MryvWCb7asMLWM+0JAfwu3jvZI=
X-Google-Smtp-Source: ABdhPJxcr+vnc35zejX9ge9/v83uI8E5yiH/VVCmJIgtjlRaIP9GcgwZE71bORGkUlAEO1i4EEzwwopXVO3QkXDPVhg=
X-Received: by 2002:a2e:974e:: with SMTP id f14mr297284ljj.102.1591112078542; Tue, 02 Jun 2020 08:34:38 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Spencer Dawkins at IETF <>
Date: Tue, 2 Jun 2020 10:34:12 -0500
Message-ID: <>
To: Alexandre Petrescu <>
Content-Type: multipart/alternative; boundary="0000000000003d4d1c05a71ba63d"
Archived-At: <>
Subject: Re: [arch-d] Liaison reports
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Jun 2020 15:34:52 -0000

Hi, Alexandre,

On Tue, May 19, 2020 at 9:22 AM Alexandre Petrescu <> wrote:

> Hello,
> Are these liaison reports specific to architecture?

I didn't see an answer to this (did I miss it?), but in, the IAB has six
responsibilities, only one of which is architectural oversight.

"External liaison" is the sixth chartered responsibility.

   (f) External Liaison

   The IAB acts as representative of the interests of the IETF and the
   Internet Society in technical liaison relationships with other
   organizations concerned with standards and other technical and
   organizational issues relevant to the world-wide Internet. Liaisons
   are kept as informal as possible and must be of demonstrable value in
   improving the quality of IETF specifications.  Individual members of
   the IETF are appointed as liaisons to other organizations by the IAB
   or IESG as appropriate.

So liaison manager reports aren't actually an architecture thing
(unless something is going wrong), but they are an IAB thing.

I should let current members of the IAB provide any followup, of
course. Things do change.