[secdir] Secdir last call review of draft-ietf-iasa2-trust-rationale-00

Tero Kivinen <kivinen@iki.fi> Thu, 04 October 2018 13:12 UTC

Return-Path: <kivinen@iki.fi>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CEC3B130E3C; Thu, 4 Oct 2018 06:12:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tero Kivinen <kivinen@iki.fi>
To: <secdir@ietf.org>
Cc: iasa20@ietf.org, draft-ietf-iasa2-trust-rationale.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.85.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153865873277.4558.6110980379756897850@ietfa.amsl.com>
Date: Thu, 04 Oct 2018 06:12:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/4mRXPo0eWRutlLfIRZ3wqVQGbKA>
Subject: [secdir] Secdir last call review of draft-ietf-iasa2-trust-rationale-00
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2018 13:12:13 -0000

Reviewer: Tero Kivinen
Review result: Ready

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

This document is discussion document that does not even plan to be
published as RFC, as the document says:

   This memo is provided only for discussion.  There is no intention to
   publish this memo as an RFC.

Thus this document actually misses security considerations section, 
but I agree that even when there could be some security issues in this 
document they do not affect any protocols directly.