[secdir] Secdir early review of draft-ietf-spring-srv6-srh-compression-17

Ned Smith via Datatracker <noreply@ietf.org> Wed, 03 July 2024 23:04 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from [10.244.2.3] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4C2C151993; Wed, 3 Jul 2024 16:04:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ned Smith via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.17.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172004788002.1005451.13608520574234898791@dt-datatracker-5f88556585-g8gwj>
Date: Wed, 03 Jul 2024 16:04:40 -0700
Message-ID-Hash: 2SIYVJ42NS7COMAJUSEAKIPEKFEAN4FV
X-Message-ID-Hash: 2SIYVJ42NS7COMAJUSEAKIPEKFEAN4FV
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-secdir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-spring-srv6-srh-compression.all@ietf.org, spring@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Ned Smith <ned.smith@intel.com>
Subject: [secdir] Secdir early review of draft-ietf-spring-srv6-srh-compression-17
List-Id: Security Area Directorate <secdir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/8dR12_kv-PGF5MxWOVUubOvw5k8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Owner: <mailto:secdir-owner@ietf.org>
List-Post: <mailto:secdir@ietf.org>
List-Subscribe: <mailto:secdir-join@ietf.org>
List-Unsubscribe: <mailto:secdir-leave@ietf.org>

Reviewer: Ned Smith
Review result: Ready

The I-D is ready but the authors may consider making the following changes:
Section 4, 5th paragraph: It would be helpful to describe which operational
issues / challenges are made easier and why to give guidance on when it may/may
not be appropriate to take the recommendation.

Section 5.3, second paragraph: S/Therefore/Therefore,/
third paragraph: S/is able to/can/ and S/Therefore/Therefore,/
fourth paragraph: S/GIB,/GIB;/

Section 6.2, first paragraph: S/in order to/to/

Section 6.3, second paragraph: S/instead/instead,/

Section 9.2, seventh paragraph: S/is able to/can/

Section 9.3, third paragraph: S/in particular is/is/

Section 10, third paragraph: S/Draft, and/Draft and/

Section 10.13, first paragraph: S/open source/open-source/

Section 10.13, second paragraph: S/open source/open-source/

I did not attempt to verify the content of the appendix A was correct / sound.
I assume the reference implementations are there to achieve this goal despite
the stated goal of the reference implementations was for interoperability.
Possibly, the authors could comment on how the I-D describes a correct and
scalable, as well as interoperable solution.