Re: [spring] WG Last Call draft-ietf-spring-nsh-sr

bruno.decraene@orange.com Mon, 15 March 2021 15:44 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF803A143D; Mon, 15 Mar 2021 08:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.817
X-Spam-Level:
X-Spam-Status: No, score=-2.817 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8XL_jGp86qg; Mon, 15 Mar 2021 08:44:13 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 152773A143B; Mon, 15 Mar 2021 08:44:13 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 4DzghC1Nn2zCqvf; Mon, 15 Mar 2021 16:44:11 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1615823051; bh=f88YA9DTCks1fpbDWXzBcPZ5d0PcN/OimgGQc6fB274=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=xB7dMtvAQUbtbIJgLQfyFApev+E0xgFvrvNNdpHNKD7L6yjDwZCG+CGlRl8Dw+keg c5nlZvyQ3tu7ebA9g/iClq98m6UJ7opQtYKGIpuixEOssdcesUNIrjrWVqjmh/auTX USlCNEfe5uJHMklxWpdUWfH1b6urJWR394zycdZFSVzy7gs8kGxAu6CMvjYP7hBN6j nKBa661cfRRt26zWCQdm79IGovXPqfM9Q2QL42xc2vztyHYSKYbCddZv70ARl0kUHl uoFy4h6PLgNfAjBjMxsVoTPxQ4VzMhui1i02CUSoBJXpeC8NimqLhbcLJQMNDI7xip MuM12hvuxbrWA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.73]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 4DzghC0S76zFpXP; Mon, 15 Mar 2021 16:44:11 +0100 (CET)
From: <bruno.decraene@orange.com>
To: "spring@ietf.org" <spring@ietf.org>, "draft-ietf-spring-nsh-sr@ietf.org" <draft-ietf-spring-nsh-sr@ietf.org>
Thread-Topic: WG Last Call draft-ietf-spring-nsh-sr
Thread-Index: Adb/EbzdQyDXcLfTRQ6v+vtwpmiyOganoO9g
Date: Mon, 15 Mar 2021 15:44:10 +0000
Message-ID: <26005_1615823051_604F80CB_26005_428_14_53C29892C857584299CBF5D05346208A4CD131C0@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <25012_1612895472_6022D4F0_25012_72_1_53C29892C857584299CBF5D05346208A490C4A3A@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
In-Reply-To: <25012_1612895472_6022D4F0_25012_72_1_53C29892C857584299CBF5D05346208A490C4A3A@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A4CD131C0OPEXCAUBM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/4aNL87DOV8u-1sScqvlcPtfE29E>
Subject: Re: [spring] WG Last Call draft-ietf-spring-nsh-sr
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 15 Mar 2021 15:44:16 -0000

Hi authors, SPRING,

Speaking as shepherd.

Encapsulation of NSH following SRv6 may be indicated either by
   encapsulating NSH in UDP (UDP port TBA1) and indicating UDP in the
   Next Header field of the SRH, or by indicating an IP protocol number
   for NSH in the Next Header of the SRH."


Yes, NSH may be encapsulated using a variety of ways. But did we had a discussion about why we need to specify both?
A priori, having N ways increase the cost and decrease the interoperability.

More specifically, why do we need to add the UDP layer?
- This increases the packet overhead
- In IPv4, UDP may be a solution to cross NAT-PT, but for IPv6 this looks less likely. Plus the use case would likely have NAT as a Service Function, not between Service Functions
- In IPv4, UDP may be a solution to provide entropy for ECMP. But in IPv6 & SRv6, we already have the flow label.
- The use of UDP is likely to require an additional section and discussion (from Transport Area) regarding congestion.

Thanks,
Regards,
--Bruno


From: spring [mailto:spring-bounces@ietf.org] On Behalf Of bruno.decraene@orange.com
Sent: Tuesday, February 9, 2021 7:31 PM
To: spring@ietf.org
Cc: draft-ietf-spring-nsh-sr@ietf.org
Subject: [spring] WG Last Call draft-ietf-spring-nsh-sr

Dear WG,

This message starts a 2 weeks WG last call for draft-ietf-spring-nsh-sr [1].

After review of the document please indicate whether you believe this document should be progressed to the IESG.

In addition to yes/no, please consider providing a technical review of this document; in particular if you care for this document.
Indeed, since WG adoption, this document had benefited from little reviews from the WG, so we need more review from the SPRING WG.

If you are aware of an implementation of this document, please report the implementation either on the list or to the chairs so that the shepherd can report implementations in the writeup.

Note that I'll forward that call to the SFC WG.

Thanks!

[1] https://tools.ietf.org/html/draft-ietf-spring-nsh-sr

--Bruno


_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.