[sfc] Éric Vyncke's No Objection on draft-ietf-sfc-serviceid-header-12: (with COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Wed, 04 November 2020 07:06 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: sfc@ietf.org
Delivered-To: sfc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BD5F13A0B3B; Tue, 3 Nov 2020 23:06:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sfc-serviceid-header@ietf.org, sfc-chairs@ietf.org, sfc@ietf.org, Greg Mirsky <gregimirsky@gmail.com>, gregimirsky@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <160447360974.14778.1078740998266370203@ietfa.amsl.com>
Date: Tue, 03 Nov 2020 23:06:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/FK2q9AGGEtTQ3mIec46bcwXw41Y>
Subject: [sfc] Éric Vyncke's No Objection on draft-ietf-sfc-serviceid-header-12: (with COMMENT)
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2020 07:06:50 -0000
Éric Vyncke has entered the following ballot position for draft-ietf-sfc-serviceid-header-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/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-sfc-serviceid-header/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for the work put into this document. Please find below a couple of non-blocking COMMENT points and I would appreciate it if the authors answered to my points that were closed to be a DISCUSS. I hope that this helps to improve the document, Regards, -éric -- Section 1 -- Please clarify the following text as NAT only applies to IPv4 and as there is no private addresses in IPv6 " Typically, because of the widespread use of private addressing in those networks, if SFs to be invoked are located after a NAT function, the identification based on the internal IP address is not possible once the NAT has been crossed. " -- Section 3 -- While I am not familiar with NSH RFC 8300 and the concept of updating the NSH context, the following text makes me wonder: " The classifier and NSH-aware SFs MAY inject or strip a Subscriber Identifier Context Header as a function of a local policy." It appears to me that a SF would actually increase/decrease the size of NSH which could lead to two issues: 1) the actual MTU is decreased on the path *after* encapsulation 2) if ICMP is generated back to the source of the NSH header, then will the source recognize the NSH packet inside the ICMP message as it is different ?
- [sfc] Éric Vyncke's No Objection on draft-ietf-sf… Éric Vyncke via Datatracker
- Re: [sfc] Éric Vyncke's No Objection on draft-iet… mohamed.boucadair
- Re: [sfc] Éric Vyncke's No Objection on draft-iet… Eric Vyncke (evyncke)