From nobody Wed Dec 8 06:29:17 2021 Return-Path: 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 40E993A096B; Wed, 8 Dec 2021 06:29:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.991 X-Spam-Level: X-Spam-Status: No, score=-0.991 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, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 B4nd3M88MU1Q; Wed, 8 Dec 2021 06:29:10 -0800 (PST) Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 458543A0969; Wed, 8 Dec 2021 06:29:07 -0800 (PST) Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr27.francetelecom.fr (ESMTP service) with ESMTPS id 4J8KKs4zNcz4x0L; Wed, 8 Dec 2021 15:29:05 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1638973745; bh=vAlEpYD1jSCZG5nptMzLqI4CArkBcMgmhnrqvYljs/c=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=f3DRXhVQHSaqkJBc5ja4g2hTGLz2Unz0R8hgPRhHZrakwFE11bc7Gw3hq2PPhCTds uBoreAMN59OqlasfUia5j6jiusBvSXkRHyDTReHgd7wlBY5VEqcCcnOcHO4Cs1v1ea mcgG2118dosMrtBQvKcO3gtzh4Q2m2VuiCk2QvrFKs/AATNe4sA8pbiQKFiVf8SRDi pMM5KOlLRRjjgHtoJYnV/hW6yNIukv+yvj8JrsGhcEn1DMSEIWc21VsJSGOEjAxJsM xyy9tnl+jlSkNd0k7EGkgd3SJvuqQpd9WRs92fGtqUNvGV+65ph5JMVKDN1WJSL0GV VNwRsv6wwmH6Q== From: To: "draft-ietf-spring-nsh-sr@ietf.org" CC: "Joel M. Halpern" , SPRING WG Thread-Topic: draft-ietf-spring-nsh-sr Thread-Index: AdfsPCMdiT18EcMVT4WFxX54OoLQfQ== Content-Class: Date: Wed, 8 Dec 2021 14:29:05 +0000 Message-ID: <25598_1638973745_61B0C131_25598_80_1_282ca6554af94a62b6629764dd94f917@orange.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2021-12-08T14:08:11Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=3ded9430-1b51-4a00-9fd7-abd865a29708; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0 x-originating-ip: [10.115.26.50] Content-Type: multipart/alternative; boundary="_000_282ca6554af94a62b6629764dd94f917orangecom_" MIME-Version: 1.0 Archived-At: Subject: [spring] 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\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2021 14:29:15 -0000 --_000_282ca6554af94a62b6629764dd94f917orangecom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi authors, Following yet another reading, please find below one proposed comment. https://datatracker.ietf.org/doc/html/draft-ietf-spring-nsh-sr#section-5.2 "the processing is the same as that specified by [RFC8754] section 4.3.1.1, up through line S.16. After S.15, if S is a local End.NSH SID, then: S15.1. Remove and store IPv6 and SRH headers in local cache indexed by " May be "up through line S.15" ? (vs S.16)? (but this is an English idiom so= not my area). -- Also could you please check IdNits and - correct the following error" ** There are 3 instances of too long = lines in the document, the longest one being 2 characters in excess of 72." - remove the two un-used references. https://www6.ietf.org/tools/idnits?url=3Dhttps://www.ietf.org/archive/id/dr= aft-ietf-spring-nsh-sr-09.txt Thanks, Regards, --Bruno ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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. --_000_282ca6554af94a62b6629764dd94f917orangecom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi authors,

 

Following yet = another reading, please find below one proposed comment.<= /p>

 

 

ht= tps://datatracker.ietf.org/doc/html/draft-ietf-spring-nsh-sr#section-5.2

“the processing is the same as that specified by [RFC8754] section
   4.3.1.1, up through line S.16.
 
   After S.15, if S is a local End.NSH SID, then:
 
   S15.1.  Remove and store IPv6 and SRH headers in local cache indexe=
d
   by <NSH: service-path-id, service-=
index -1>”
 
 
May be “up through line S.15” ? (vs S=
.16)? (but this is an English idiom so not my area).
--
 
Also could you please check IdNits and 
=
-       correct the following error“  ** There are 3 instances of too long lines in the docum=
ent, the longest one being 2 characters in excess of 72.”<=
/span>
=
-       remove the two un-used references.
 
https:/=
/www6.ietf.org/tools/idnits?url=3Dhttps://www.ietf.org/archive/id/draft-iet=
f-spring-nsh-sr-09.txt
 
Thanks,
Regards,
--Bruno
 

 

______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
--_000_282ca6554af94a62b6629764dd94f917orangecom_-- From nobody Wed Dec 8 06:32:19 2021 Return-Path: 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 B0C263A096C; Wed, 8 Dec 2021 06:32:17 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Bruno Decraene via Datatracker To: X-Test-IDTracker: no X-IETF-IDTracker: 7.40.0 Auto-Submitted: auto-generated Precedence: bulk Cc: bruno.decraene@orange.com, iesg-secretary@ietf.org, spring-chairs@ietf.org, spring@ietf.org Message-ID: <163897393770.27053.11590232900560025708@ietfa.amsl.com> Date: Wed, 08 Dec 2021 06:32:17 -0800 Archived-At: Subject: [spring] Publication has been requested for draft-ietf-spring-nsh-sr-09 X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2021 14:32:18 -0000 Bruno Decraene has requested publication of draft-ietf-spring-nsh-sr-09 as Proposed Standard on behalf of the SPRING working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-spring-nsh-sr/ From nobody Mon Dec 13 11:23:29 2021 Return-Path: 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 266BC3A0A84; Mon, 13 Dec 2021 11:23:23 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: spring@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.41.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: spring@ietf.org Message-ID: <163942340306.17202.4064255459658075186@ietfa.amsl.com> Date: Mon, 13 Dec 2021 11:23:23 -0800 Archived-At: Subject: [spring] I-D Action: draft-ietf-spring-nsh-sr-10.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Dec 2021 19:23:23 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Packet Routing in Networking WG of the IETF. Title : Integration of Network Service Header (NSH) and Segment Routing for Service Function Chaining (SFC) Authors : James N Guichard Jeff Tantsura Filename : draft-ietf-spring-nsh-sr-10.txt Pages : 18 Date : 2021-12-13 Abstract: This document describes the integration of the Network Service Header (NSH) and Segment Routing (SR), as well as encapsulation details, to support Service Function Chaining (SFC) in an efficient manner while maintaining separation of the service and transport planes as originally intended by the SFC architecture. Combining these technologies allows SR to be used for steering packets between Service Function Forwarders (SFF) along a given Service Function Path (SFP) while NSH has the responsibility for maintaining the integrity of the service plane, the SFC instance context, and any associated metadata. This integration demonstrates that NSH and SR can work cooperatively and provide a network operator with the flexibility to use whichever transport technology makes sense in specific areas of their network infrastructure while still maintaining an end-to-end service plane using NSH. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-spring-nsh-sr/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-spring-nsh-sr-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-nsh-sr-10 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts From nobody Mon Dec 13 18:53:26 2021 Return-Path: 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 8EF913A0DFB; Mon, 13 Dec 2021 18:53:11 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: spring@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.41.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: spring@ietf.org Message-ID: <163945039151.26392.5134640938985340492@ietfa.amsl.com> Date: Mon, 13 Dec 2021 18:53:11 -0800 Archived-At: Subject: [spring] I-D Action: draft-ietf-spring-mpls-path-segment-06.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2021 02:53:12 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Packet Routing in Networking WG of the IETF. Title : Path Segment in MPLS Based Segment Routing Network Authors : Weiqiang Cheng Han Li Mach(Guoyi) Chen Rakesh Gandhi Royi Zigler Filename : draft-ietf-spring-mpls-path-segment-06.txt Pages : 14 Date : 2021-12-13 Abstract: A Segment Routing (SR) path is identified by an SR segment list. Only the complete segment list can identify the end-to-end SR path, and a sub-set of segments from the segment list cannot distinguish one SR path from another as they may be partially congruent. SR path identification is a pre-requisite for various use-cases such as Performance Measurement (PM), bidirectional paths correlation, and end-to-end 1+1 path protection. In SR for MPLS data plane (SR-MPLS), the segment identifiers are stripped from the packet through label popping as the packet transits the network. This means that when a packet reaches the egress of the SR path, it is not possible to determine on which SR path it traversed the network. This document defines a new type of segment that is referred to as Path Segment, which is used to identify an SR path in an SR-MPLS network. When used, it is inserted by the ingress node of the SR path and immediately follows the last segment identifier in the segment list of the SR path. The Path Segment is preserved until it reaches the egress node for SR path identification and correlation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-spring-mpls-path-segment/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-spring-mpls-path-segment-06 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-mpls-path-segment-06 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts From nobody Mon Dec 20 20:20:40 2021 Return-Path: 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 464483A1135; Mon, 20 Dec 2021 20:20:30 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: spring@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.41.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: spring@ietf.org Message-ID: <164006043021.27508.5698346155123214161@ietfa.amsl.com> Date: Mon, 20 Dec 2021 20:20:30 -0800 Archived-At: Subject: [spring] I-D Action: draft-ietf-spring-mpls-path-segment-07.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2021 04:20:30 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Packet Routing in Networking WG of the IETF. Title : Path Segment in MPLS Based Segment Routing Network Authors : Weiqiang Cheng Han Li Mach(Guoyi) Chen Rakesh Gandhi Royi Zigler Filename : draft-ietf-spring-mpls-path-segment-07.txt Pages : 14 Date : 2021-12-20 Abstract: A Segment Routing (SR) path is identified by an SR segment list. Only the complete segment list can identify the end-to-end SR path, and a sub-set of segments from the segment list cannot distinguish one SR path from another as they may be partially congruent. SR path identification is a pre-requisite for various use-cases such as Performance Measurement (PM), bidirectional paths correlation, and end-to-end 1+1 path protection. In SR for MPLS data plane (SR-MPLS), the segment identifiers are stripped from the packet through label popping as the packet transits the network. This means that when a packet reaches the egress of the SR path, it is not possible to determine on which SR path it traversed the network. This document defines a new type of segment that is referred to as Path Segment, which is used to identify an SR path in an SR-MPLS network. When used, it is inserted by the ingress node of the SR path and immediately follows the last segment identifier in the segment list of the SR path. The Path Segment is preserved until it reaches the egress node for SR path identification and correlation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-spring-mpls-path-segment/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-spring-mpls-path-segment-07 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-mpls-path-segment-07 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts From nobody Thu Dec 23 09:37:55 2021 Return-Path: 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 870583A07AA; Thu, 23 Dec 2021 09:37:43 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Jim Guichard via Datatracker To: X-Test-IDTracker: no X-IETF-IDTracker: 7.41.0 Auto-Submitted: auto-generated Precedence: bulk Cc: iesg-secretary@ietf.org, james.n.guichard@futurewei.com, spring-chairs@ietf.org, spring@ietf.org Message-ID: <164028106352.12919.11945513389637817691@ietfa.amsl.com> Date: Thu, 23 Dec 2021 09:37:43 -0800 Archived-At: Subject: [spring] Publication has been requested for draft-ietf-spring-mpls-path-segment-07 X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2021 17:37:53 -0000 Jim Guichard has requested publication of draft-ietf-spring-mpls-path-segment-07 as Proposed Standard on behalf of the SPRING working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-spring-mpls-path-segment/