[secdir] Secdir last call review of draft-ietf-mpls-rfc8287-len-clarification-02

Kyle Rose via Datatracker <noreply@ietf.org> Fri, 02 August 2019 21:04 UTC

Return-Path: <noreply@ietf.org>
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 ED667120147; Fri, 2 Aug 2019 14:04:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kyle Rose via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: mpls@ietf.org, ietf@ietf.org, draft-ietf-mpls-rfc8287-len-clarification.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.99.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Kyle Rose <krose@krose.org>
Message-ID: <156477989693.20922.10639864462240787352@ietfa.amsl.com>
Date: Fri, 02 Aug 2019 14:04:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/s-bf_CnRo00y_39fQVnowhFRj1s>
Subject: [secdir] Secdir last call review of draft-ietf-mpls-rfc8287-len-clarification-02
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: Fri, 02 Aug 2019 21:04:57 -0000

Reviewer: Kyle Rose
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 a straightforward update for implementation clarity and has
neither security nor privacy implications.