[spring] Secdir telechat review of draft-ietf-spring-srv6-network-programming-20

Brian Weis via Datatracker <noreply@ietf.org> Thu, 24 September 2020 16:37 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: spring@ietf.org
Delivered-To: spring@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E7C8F3A10CD; Thu, 24 Sep 2020 09:37:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Weis via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: spring@ietf.org, draft-ietf-spring-srv6-network-programming.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160096545789.2761.7901137068170504935@ietfa.amsl.com>
Reply-To: Brian Weis <bew.stds@gmail.com>
Date: Thu, 24 Sep 2020 09:37:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/2ek65GHH5kPC-S7mTof5moDbHBY>
Subject: [spring] Secdir telechat review of draft-ietf-spring-srv6-network-programming-20
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2020 16:37:38 -0000

Reviewer: Brian Weis
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.

A new sentence was added to Security Considerations in version 20. I believe
it, combined with the previous sentence, will help clueful developers
understand that there may be a need to add HMAC processing even if there is no
SRH header. Thanks. None of the other changes in the update appear to affect
security considerations.