[secdir] Secdir last call review of draft-ietf-regext-rfc7482bis-02

Stefan Santesson via Datatracker <noreply@ietf.org> Mon, 15 February 2021 09:19 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stefan Santesson via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-regext-rfc7482bis.all@ietf.org, last-call@ietf.org, regext@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161338079230.21191.4755037249161520724@ietfa.amsl.com>
Reply-To: Stefan Santesson <stefan@aaa-sec.com>
Date: Mon, 15 Feb 2021 01:19:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/zyA6GbEE7ryfnYhIndUZkP7u2jA>
Subject: [secdir] Secdir last call review of draft-ietf-regext-rfc7482bis-02

Reviewer: Stefan Santesson
Review result: Ready

This document appears to be ready and well written.

>From a security point of view this document does not have much to review as
security services related to this protocol is handled by a separate document
(Security Services for the Registration Data Access Protocol (RDAP) RFC 7481).
At a first glance the security considerations sections seems a bit limited, but
when taking RFC 7481 into account, which has already been approved as a
reasonable set of security functions for this protocol, the security
considerations section seems adequate.

[secdir] Secdir last call review of draft-ietf-re… Stefan Santesson via Datatracker