[spring] Erik Kline's No Objection on draft-ietf-spring-nsh-sr-12: (with COMMENT)

Erik Kline via Datatracker <noreply@ietf.org> Wed, 26 April 2023 20:15 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 38E92C14F6EC; Wed, 26 Apr 2023 13:15:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-spring-nsh-sr@ietf.org, spring-chairs@ietf.org, spring@ietf.org, bruno.decraene@orange.com, bruno.decraene@orange.com
X-Test-IDTracker: no
X-IETF-IDTracker: 10.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <168254015822.29658.13271459537716537906@ietfa.amsl.com>
Date: Wed, 26 Apr 2023 13:15:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/2EIbDElqJMP_RwpQQmpgGKgjxaA>
Subject: [spring] Erik Kline's No Objection on draft-ietf-spring-nsh-sr-12: (with COMMENT)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 26 Apr 2023 20:15:58 -0000

Erik Kline has entered the following ballot position for
draft-ietf-spring-nsh-sr-12: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


# Internet AD comments for draft-ietf-spring-nsh-sr-12
CC @ekline

## Comments

### S5.1, S5.2

* I am not very familiar with the SFC paradigm, so please do correct me or
  ignore me.

  Does this "service-index - 1" cache end up imposing too tight a restriction
  on the SF handling of the NSH, limiting processing to only a single
  function (decrementing the service index by only 1)?

  I naively expected that the SR segment list could move a packet through
  a network of endpoints, but that each endpoint could perhaps trigger
  multiple functions acting on the packet without incurring extra,
  duplicative segments to indicate additional processing on the same node.

### S11.1

* Should the document reference actually RFC 8300 (NSH)?  "This document"
  defines where the IANA allocation comes from but that doesn't really help
  a possible implementer get directly to the required spec.