[Idr] Secdir last call review of draft-ietf-idr-capabilities-registry-change-07

Kyle Rose via Datatracker <noreply@ietf.org> Fri, 24 April 2020 14:50 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F4263A0986; Fri, 24 Apr 2020 07:50:00 -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: idr@ietf.org, last-call@ietf.org, draft-ietf-idr-capabilities-registry-change.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.127.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158773980020.30877.3733079568668640715@ietfa.amsl.com>
Reply-To: Kyle Rose <krose@krose.org>
Date: Fri, 24 Apr 2020 07:50:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/G7hp6rEhAQViLO-OlvBUtq8-5ZM>
Subject: [Idr] Secdir last call review of draft-ietf-idr-capabilities-registry-change-07
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2020 14:50:01 -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 ready. It describes a policy change regarding assignment of
BGP capability codes, with no novel security implications.