[secdir] Secdir last call review of draft-ietf-sfc-hierarchical-08

Sean Turner <sean@sn3rd.com> Tue, 29 May 2018 14:19 UTC

Return-Path: <sean@sn3rd.com>
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 6231512E050; Tue, 29 May 2018 07:19:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Sean Turner <sean@sn3rd.com>
To: <secdir@ietf.org>
Cc: draft-ietf-sfc-hierarchical.all@ietf.org, ietf@ietf.org, sfc@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.81.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152760355124.12572.4328281075629737814@ietfa.amsl.com>
Date: Tue, 29 May 2018 07:19:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/s9mtOhfuW1bfB3Jxt-pmJ7zfqCE>
Subject: [secdir] Secdir last call review of draft-ietf-sfc-hierarchical-08
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 29 May 2018 14:19:12 -0000

Reviewer: Sean Turner
Review result: Ready

Hi! I’m no expert on SFC so I spent some time reviewing RFC7665 and Simon
Josefsson’s secdir review [0] as well as RFC 8300 and 8393.  It looks like all
the things I was going to pick on are addressed by the references.

I’ll let somebody else on the IESG debate whether Figure 4 is trying to be a
little different than the rest of this architectural document by specify some
protocols bits; informational still?