RE: Tricky cross-area topics

Jim Schaad <ietf@augustcellars.com> Fri, 04 October 2019 17:28 UTC

Return-Path: <ietf@augustcellars.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 EA4751208F1 for <wgchairs@ietfa.amsl.com>; Fri, 4 Oct 2019 10:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 t5deg2DdK_ev for <wgchairs@ietfa.amsl.com>; Fri, 4 Oct 2019 10:28:08 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E44841208D9 for <wgchairs@ietf.org>; Fri, 4 Oct 2019 10:28:07 -0700 (PDT)
Received: from Jude (192.168.1.159) by mail2.augustcellars.com (192.168.1.201) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 4 Oct 2019 10:28:01 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Adam Roach' <adam@nostrum.com>, 'IETF WG Chairs' <wgchairs@ietf.org>
References: <77b22339-6a8e-8eaa-a695-724deb963dec@nostrum.com>
In-Reply-To: <77b22339-6a8e-8eaa-a695-724deb963dec@nostrum.com>
Subject: RE: Tricky cross-area topics
Date: Fri, 04 Oct 2019 10:27:57 -0700
Message-ID: <024801d57ad9$11f553c0$35dffb40$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQH4MOOSgN3PaQKlif/4S2AdjMXzz6cFTWVQ
Content-Language: en-us
X-Originating-IP: [192.168.1.159]
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/4A1Lo2EKQSu7PUtlmTYdzV2UcnM>
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: Fri, 04 Oct 2019 17:28:10 -0000

Things that are missing in my opinion:

ART:

Application Layer Security: Is missing COSE, and CMS 

Expanded:  When application layer security is specified for a protocol, issues that must be addressed include:
 1) Matching of entities and keys:  Who is doing the matching?  What needs to be done for naming?  How is matching revoked or timed out?
 2) Supported algorithms and what the migration path should be.
 3) Algorithm and capability negotiation:  What do we both support and how do we find out?  The issues are different between online and store and forward.
4) What security properties are needed, two common ones are confidentiality and data origination.  (Note data origination is not the same as integrity.)

Security area does not discuss any store and forward issues.  Examples are CMS, X509, and so forth.

-----Original Message-----
From: WGChairs <wgchairs-bounces@ietf.org> On Behalf Of Adam Roach
Sent: Thursday, October 3, 2019 12:29 PM
To: IETF WG Chairs <wgchairs@ietf.org>
Subject: Tricky cross-area topics

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