Re: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

"Wang, Weibin (NSB - CN/Shanghai)" <weibin.wang@nokia-sbell.com> Fri, 18 October 2019 03:56 UTC

Return-Path: <weibin.wang@nokia-sbell.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 8CA271201CE for <spring@ietfa.amsl.com>; Thu, 17 Oct 2019 20:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.005
X-Spam-Level:
X-Spam-Status: No, score=-1.005 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 6UQFGjXWJtsS for <spring@ietfa.amsl.com>; Thu, 17 Oct 2019 20:56:32 -0700 (PDT)
Received: from cnshjsmin03.nokia-sbell.com (unknown [116.246.26.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A22F120052 for <spring@ietf.org>; Thu, 17 Oct 2019 20:56:30 -0700 (PDT)
X-AuditID: ac189297-d29ff70000006f83-c1-5da937cf4ec4
Received: from CNSHPPEXCH1601.nsn-intra.net (Unknown_Domain [135.251.51.101]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by cnshjsmin03.nokia-sbell.com (Symantec Messaging Gateway) with SMTP id 77.DD.28547.FC739AD5; Fri, 18 Oct 2019 11:55:59 +0800 (HKT)
Received: from CNSHPPEXCH1605.nsn-intra.net (135.251.51.105) by CNSHPPEXCH1601.nsn-intra.net (135.251.51.101) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 18 Oct 2019 11:55:59 +0800
Received: from CNSHPPEXCH1605.nsn-intra.net ([135.251.51.105]) by CNSHPPEXCH1605.nsn-intra.net ([135.251.51.105]) with mapi id 15.01.1713.007; Fri, 18 Oct 2019 11:55:59 +0800
From: "Wang, Weibin (NSB - CN/Shanghai)" <weibin.wang@nokia-sbell.com>
To: Rajesh M <mrajesh=40juniper.net@dmarc.ietf.org>, "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>, SPRING WG List <spring@ietf.org>
CC: Srihari Sangli <ssangli@juniper.net>, Shraddha Hegde <shraddha@juniper.net>
Thread-Topic: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24
Thread-Index: AQHVg3ellwgh7tiPSkiKObnXdT1kiade6fwAgADZTOA=
Date: Fri, 18 Oct 2019 03:55:58 +0000
Message-ID: <02b54f9299ce4820b83e9344e8a5f049@nokia-sbell.com>
References: <19C3F806-B455-4D0A-A56B-9BF5C6A36DE8@cisco.com> <MN2PR05MB6080AF7CB8230A9F403F7C89BE6D0@MN2PR05MB6080.namprd05.prod.outlook.com>
In-Reply-To: <MN2PR05MB6080AF7CB8230A9F403F7C89BE6D0@MN2PR05MB6080.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=mrajesh@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2019-10-11T01:46:23.5028871Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=da749b5a-3079-47d3-b15d-13c6e8f83efc; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
x-originating-ip: [135.251.51.115]
Content-Type: multipart/alternative; boundary="_000_02b54f9299ce4820b83e9344e8a5f049nokiasbellcom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPIsWRmVeSWpSXmKPExsXS/ts4Vfe8+cpYg5ajIhbbT25ls/h1fBeL xY1He5ktjl/4zWhx+/8WVgdWjym/N7J6nFh2hdVjyZKfTB7Xm66yB7BEcdmkpOZklqUW6dsl cGU8ereOreDKUsaKsz8vMTYwLprJ2MXIwSEhYCKxaaVPFyMXh5DAISaJg1svMEE4fxkl1t1e wA7hbGKUWLb0IWsXIycHm4CbxKRtu9hAEiICXYwS69/sZQEZxSwQKHF6YQRIjbBApsT7OYvY QGwRgSyJ6/8OskDYVhIHO94xgdgsAqoSd/9vYwaxeQXsJP68uMIGsayfUWLezMOMIAlOgViJ Ca+bwGxGATGJ76fWgDUzC4hL3HoyH8yWEBCQWLLnPDOELSrx8vE/VpBBvAK7WCWaGt6xQfyp JNG3Aao3VWJaVxMTxGJBiZMzn7BMYBSbhWTsLCRls5CUQcS1JOY1/IaqUZSY0v2QHcLWlLgy +RCUrS2xbOFr5gWM7KsYpZPzijOyinMz8wyM9fLyszMTdYuTUnNy9JLzczcxAqN5jcSk6TsY jx3wPsQowMGoxMN7IHxFrBBrYllxZe4hRgkOZiURXuYqoBBvSmJlVWpRfnxRaU5q8SFGaQ4W JXHelskLY4UE0hNLUrNTUwtSi2CyTBycUg2MXB+/Z7Acm1MR8Hvrp9ymbRwf2e89Fln6Vq5r 26lzbY6HBVu7NYPPy9ks4NJq8/lRoeXLqlL2I7eHaan6gztFEz1CdD6la2pV7Hwb8lmQwSxQ 3Zh3VWMG/yEfdbNjuwXllqtcCcpct/ZWl2+W8kq73iZmk4ketrKHH/zukz0h7aq1NWVJ0Tkl luKMREMt5qLiRAD4XnLo4gIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/w8SBURTwOjCw6jNrkWdn5CjDh2g>
Subject: Re: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24
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: Fri, 18 Oct 2019 03:56:36 -0000

The value of Segment Left field in SRH begin with 0, so [SL]=0 represent the last SID. in this case, when [SL] decrease 1, and the penultimate SRv6 node copy IPv6 SID corresponding to [SL]=0 to DA field of IP packet, when enable PSP flavor at same time, the penultimate SRv6 node will check the [SL] value, if it is 0, then pop SRH, these extra action is pseudocode of PSP. This logic has no problem.


--------------------------------------
Cheers !


WANG Weibin

From: spring <spring-bounces@ietf.org> On Behalf Of Rajesh M
Sent: 2019年10月18日 6:38
To: Pablo Camarillo (pcamaril) <pcamaril@cisco.com>; SPRING WG List <spring@ietf.org>
Cc: Srihari Sangli <ssangli@juniper.net>; Shraddha Hegde <shraddha@juniper.net>
Subject: Re: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

WANG had given below use case : But using existing PSP logic this will not work.
In below at PSP router updated SL will be 1 (since END.DT4 is still there) ,so SRH pop won’t happen.



   S14.1.   If (updated SL == 0) {

   S14.2.      Pop the SRH

   S14.3.   }

WANG use case:
“For example in SRv6-based L3VPN service scenario, The ingress PE within SRv6-enabled domain can utilize SR-TE policy to enable TE-path function when encapsulating and transiting L3VPN traffic, The Ingress PE push on customer packets with SID list representing SR-TE policy plus END.DT4 as last SRv6 SID in SRH; So I think, each flavor of PSP/USP/USD can be designed to perform in related SRv6 endpoint. Imaging the PSP, the penultimate Endpoint can perform PSP, e.g. copy the last SID (END.DT4) of SRH to destination field of IPv6 header and POP the SRH, then forwarding it toward egress PE identified by DA”







Juniper Business Use Only
From: Pablo Camarillo (pcamaril) <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>
Sent: Tuesday, October 15, 2019 10:13 PM
To: Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>; SPRING WG List <spring@ietf.org<mailto:spring@ietf.org>>
Cc: Srihari Sangli <ssangli@juniper.net<mailto:ssangli@juniper.net>>; Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>
Subject: Re: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

Rajesh,

This has already been replied less than one week ago.. Please see:
https://mailarchive.ietf.org/arch/msg/spring/V0ZpjVLSVZxHaBwecXFxqJjlg_c<https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/spring/V0ZpjVLSVZxHaBwecXFxqJjlg_c__;!8WoA6RjC81c!W8zXtokq31cYlPoLJ6Ip-BlyXApb7JIhuJzRXW3khd_OAByxCvaxs9Jw7HGIr9o9$>
https://mailarchive.ietf.org/arch/msg/spring/WrYzRZC0HKVgBYaYMCQVcTWrfak<https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/spring/WrYzRZC0HKVgBYaYMCQVcTWrfak__;!8WoA6RjC81c!W8zXtokq31cYlPoLJ6Ip-BlyXApb7JIhuJzRXW3khd_OAByxCvaxs9Jw7P8QaU_7$>

Thanks,
Pablo.


From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> on behalf of Rajesh M <mrajesh=40juniper.net@dmarc.ietf.org<mailto:mrajesh=40juniper.net@dmarc.ietf.org>>
Date: Friday, 11 October 2019 at 03:47
To: SPRING WG List <spring@ietf.org<mailto:spring@ietf.org>>
Cc: Srihari Sangli <ssangli@juniper.net<mailto:ssangli@juniper.net>>, Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>
Subject: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24


Wanted to know the use case where we only POP the SRH ?

4.16.1<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04*section-4.16.1__;Iw!8WoA6RjC81c!W8zXtokq31cYlPoLJ6Ip-BlyXApb7JIhuJzRXW3khd_OAByxCvaxs9Jw7DAv5v98$>.  PSP: Penultimate Segment Pop of the SRH

   The SRH processing of the End, End.X and End.T behaviors are

   modified: after the instruction "S14.  Update IPv6 DA with Segment

   List[Segments Left]" is executed, the following instructions must be

   executed as well:



   S14.1.   If (updated SL == 0) {

   S14.2.      Pop the SRH

   S14.3.   }



Juniper Business Use Only