[secdir] Secdir last call review of draft-ietf-lamps-rfc7299-update-00
Steve Hanna via Datatracker <noreply@ietf.org> Wed, 15 September 2021 09:38 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 CD1333A0A9D; Wed, 15 Sep 2021 02:38:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Steve Hanna via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-lamps-rfc7299-update.all@ietf.org, last-call@ietf.org, spasm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163169870178.28115.9749565789693881234@ietfa.amsl.com>
Reply-To: Steve Hanna <steve@hannas.com>
Date: Wed, 15 Sep 2021 02:38:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/qKXYbwwxwvXkMMyobi__sMc_pbA>
Subject: [secdir] Secdir last call review of draft-ietf-lamps-rfc7299-update-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: Wed, 15 Sep 2021 09:38:22 -0000
Reviewer: Steve Hanna 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. The summary of the review is Ready. This short document adds a small number of object identifiers to the IANA registry for PKIX. These OIDs were assigned in RFC 4212 but accidentally not included in RFC 7299. This RFC will rectify that error. I see no problems from a security standpoint. In fact, there will be some slight improvement because readers will be able to find the OIDs in the registry. Nothing substantive here but it should be approved.
- [secdir] Secdir last call review of draft-ietf-la… Steve Hanna via Datatracker