Re: Tricky cross-area topics

Russ Housley <housley@vigilsec.com> Thu, 03 October 2019 22:16 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 855E812002F for <wgchairs@ietfa.amsl.com>; Thu, 3 Oct 2019 15:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 UUhSQQFMCojY for <wgchairs@ietfa.amsl.com>; Thu, 3 Oct 2019 15:16:54 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D85612001E for <wgchairs@ietf.org>; Thu, 3 Oct 2019 15:16:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BBC9D300AEF for <wgchairs@ietf.org>; Thu, 3 Oct 2019 18:16:52 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id bhtr0ZHIpXHA for <wgchairs@ietf.org>; Thu, 3 Oct 2019 18:16:51 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id 77508300460; Thu, 3 Oct 2019 18:16:51 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Tricky cross-area topics
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <77b22339-6a8e-8eaa-a695-724deb963dec@nostrum.com>
Date: Thu, 03 Oct 2019 18:16:52 -0400
Cc: IETF WG Chairs <wgchairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0959298-AF06-4CBE-80A6-988A93B04C30@vigilsec.com>
References: <77b22339-6a8e-8eaa-a695-724deb963dec@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/emaJiHY_cXQbg1d9CwhVrDUAib0>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Oct 2019 22:16:55 -0000

In security, you probably want to ask whether manual key management is proposed.  See RFC 4107.

Russ


> On Oct 3, 2019, at 3:29 PM, Adam Roach <adam@nostrum.com> wrote:
> 
> Working group chairs --
> 
> In an attempt to reduce the number of "late surprises" with documents found during IESG review -- that is, showstopping issues with uses of technology that can sometimes require non-trivial reworking of protocol mechanisms -- the IESG has gathered together a list of topics that frequently trip up document authors and occasionally entire working groups.
> 
> The hope is that Working Group Chairs can keep an eye on these topics as new work starts up in their working groups, so that appropriate experts can be looped in early in the process, thereby avoiding late surprises during IETF last call and IESG evaluation.
> 
> The high-level list lives at <https://trac.ietf.org/trac/iesg/wiki/ExpertTopics>. The intent is that this should be fairly easy to scan to see whether a document under consideration for adoption touches on any of the related technologies. Each area also has its own slightly more detailed page, linked from this list, that goes into the technology areas in a bit more depth; but the intention here is that anyone using a listed technology should reach out to a directorate, expert, or area director in the related area for guidance.
> 
> Please feel free to share this list with your respective working groups however you see most fit.
> 
> Thanks!
> 
> /a
>