[Sidrops] Opsdir last call review of draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04

Mehmet Ersue via Datatracker <noreply@ietf.org> Mon, 18 March 2019 10:07 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E190130E16; Mon, 18 Mar 2019 03:07:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Mehmet Ersue via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: sidrops@ietf.org, ietf@ietf.org, draft-ietf-sidrops-bgpsec-algs-rfc8208-bis.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Mehmet Ersue <mersue@gmail.com>
Message-ID: <155290366133.26147.15826331095937544086@ietfa.amsl.com>
Date: Mon, 18 Mar 2019 03:07:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/IqO0NuzDNkDZD_eKu-T4iVoKvbI>
X-Mailman-Approved-At: Mon, 18 Mar 2019 03:19:29 -0700
Subject: [Sidrops] Opsdir last call review of draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2019 10:07:42 -0000

Reviewer: Mehmet Ersue
Review result: Has Nits

I reviewed the document "BGPsec Algorithms, Key Formats, and Signature Formats"
(draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04.txt) as part of the Operational
directorate's ongoing effort to review all IETF documents being processed by
the IESG. These comments were written primarily for the benefit of the
operational area directors.  Document editors and WG chairs should treat these
comments just like any other last call comments.

Intended status: Standards Track
Current IESG state: Waiting for Writeup
IANA State: IANA - Review Needed

The document specifies the algorithms, algorithm parameters, asymmetric key
formats, asymmetric key sizes, and signature formats used in BGPsec.  The
document updates RFC 8208 ("BGPsec Algorithms, Key Formats, and Signature
Formats") by adding Special-Use Algorithm IDs and correcting the range of
unassigned algorithms IDs to fill the complete range.

There are some nits in the document like
- Normative reference to an Informational RFCs and
- Non-RFC (?) normative references

As far as I can tell the document does not cause any issues related to
operations and management.