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

Rajesh M <mrajesh@juniper.net> Fri, 18 October 2019 12:18 UTC

Return-Path: <mrajesh@juniper.net>
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 8375C1200B4 for <spring@ietfa.amsl.com>; Fri, 18 Oct 2019 05:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-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=juniper.net
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 QGYib9nDWOdf for <spring@ietfa.amsl.com>; Fri, 18 Oct 2019 05:18:08 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 9595E120098 for <spring@ietf.org>; Fri, 18 Oct 2019 05:18:08 -0700 (PDT)
Received: from pps.filterd (m0108158.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x9ICGcrK016196; Fri, 18 Oct 2019 05:18:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=kDnEyOpy5crAGng+yUX92PFNkB7jo0DuoPTJC750LZw=; b=s5zYN83OWZ6g5/9iXeUMTn5nbTJxtOMOI5EC+/FMVbswsV36reUcHDERJLbCbBLDH7wj 50XGH/omCtCB8BoS9xYwMNS6C9dtFHbxjhK+CT/798bgjFxO/sW9Pq1dRNehURq8IVu5 ecZSf3A5xaHHou4fcKhbtO+U0yB6kVGEN0ggSEP9yUug4Yu0v8Op6OT0cSuCkPRqLVx+ totWjDf/UwqaWH17yWuUQzKUIIps7a1q2aBhWNIDYqRT2P5LIY6WxX65D8bfKoj0GmiF XqnPmG5OIWZZe5FYUuV+lZZL8eOMAJJt7pDtssCGJ1nXmQokyQTMMcIJRZDftcQHUVh3 eQ==
Received: from nam05-dm3-obe.outbound.protection.outlook.com (mail-dm3nam05lp2050.outbound.protection.outlook.com [104.47.49.50]) by mx0a-00273201.pphosted.com with ESMTP id 2vpmydjk9a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 18 Oct 2019 05:18:06 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F8WTTtyU10DANUTYEs5455tmxoU9RWDRmP5UTt3wm///o6Fgsa0rWEUqzDRGkU9hqlHvQ1+/of9TC2ZuneI8do1Ld42exUQ3PuWgVo0KGcH04c0JUOuIADEnuCF2684ao8Rgj6QfU3TA9i2Tm31Z7G5J1/HqKn6TnQbIw1gZG7idzp9J+BkTUop3cvC9DLDwDKr1eASF1MM6Y7KV5ip/iuxXABqkgMvShWBfdyy/0/9EqE/yzJ3InuK93jcOc9mxb7aXtyp9Y28/CF48Y8ZK1Wf24NdANtdOSMvnnrxwbx6Ltm57v8yobbmXy6T3FnTgeKi7WwXagOnsGeIdK5CFCA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kDnEyOpy5crAGng+yUX92PFNkB7jo0DuoPTJC750LZw=; b=kxFslAn8K7yB5lZmkAVE/uZSWNAmGZppJTssa9RUwIKnpEJc03T2CnzRcwJOceczM3hng/ENVDfuydV4k9IsIyGFa2ksNyGbjsEc0iLP2T+cUBfAQSdGpY7ZCbcI4fvNIAKK+s3HN1mzd3PV98tBtwaWvObYbFlO2IhLIchbNKNJ8A0JLvNAGzBvaWXACYFbQP9AfpLtgeUoRqvYLXTsBcAgDChNCB4KuwJKD/QTHAYqOMbPtcmFVmY0jYM4z7O5xPUQdElOMyI7gy69yxxIAuINNOx2derwVh1BMuTgJgQiYTp0EnZHMilb1wKwTikN/BdrJQ0j4mSnthtyaGhpHQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
Received: from MN2PR05MB6080.namprd05.prod.outlook.com (20.178.241.21) by MN2PR05MB6176.namprd05.prod.outlook.com (20.178.242.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2367.14; Fri, 18 Oct 2019 12:18:04 +0000
Received: from MN2PR05MB6080.namprd05.prod.outlook.com ([fe80::75f9:ea2d:bb47:8292]) by MN2PR05MB6080.namprd05.prod.outlook.com ([fe80::75f9:ea2d:bb47:8292%4]) with mapi id 15.20.2367.019; Fri, 18 Oct 2019 12:18:04 +0000
From: Rajesh M <mrajesh@juniper.net>
To: "Wang, Weibin (NSB - CN/Shanghai)" <weibin.wang@nokia-sbell.com>, 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: AQHVg3el/QTSxmKUH02g4wcuLniNTadfbEpggABcrACAAIiUIA==
Date: Fri, 18 Oct 2019 12:18:04 +0000
Message-ID: <MN2PR05MB60806B43DBD4D38910CBB1E3BE6C0@MN2PR05MB6080.namprd05.prod.outlook.com>
References: <19C3F806-B455-4D0A-A56B-9BF5C6A36DE8@cisco.com> <MN2PR05MB6080AF7CB8230A9F403F7C89BE6D0@MN2PR05MB6080.namprd05.prod.outlook.com> <02b54f9299ce4820b83e9344e8a5f049@nokia-sbell.com>
In-Reply-To: <02b54f9299ce4820b83e9344e8a5f049@nokia-sbell.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
dlp-product: dlpe-windows
dlp-version: 11.2.0.14
dlp-reaction: no-action
x-originating-ip: [116.197.184.16]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f7fef8e3-3d81-4d01-b069-08d753c53a1f
x-ms-office365-filtering-ht: Tenant
x-ms-traffictypediagnostic: MN2PR05MB6176:
x-ms-exchange-purlcount: 6
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <MN2PR05MB61762725028E95F44F8EB589BE6C0@MN2PR05MB6176.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01949FE337
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(376002)(396003)(39860400002)(346002)(189003)(199004)(71190400001)(74316002)(186003)(2906002)(66476007)(6506007)(102836004)(54896002)(66574012)(53546011)(5660300002)(66556008)(6306002)(99286004)(66446008)(64756008)(33656002)(478600001)(4326008)(236005)(110136005)(9686003)(71200400001)(54906003)(52536014)(76176011)(6436002)(7696005)(107886003)(316002)(55016002)(81166006)(6246003)(81156014)(8676002)(66946007)(8936002)(14454004)(256004)(26005)(14444005)(486006)(76116006)(966005)(66066001)(86362001)(7736002)(446003)(229853002)(11346002)(6116002)(790700001)(3846002)(606006)(25786009)(476003); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR05MB6176; H:MN2PR05MB6080.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: WsPALrUNZU669+0dCVrTTBHL4QbKi7x1oRGBhyEvSQH5AKKKRNAG35ztoEPLRIgW15QPA9ShLTBhI47h01d4UhgugytZ7qxx/t3ROAjHkTfEaidbeDDK8zb5ZL9fPk5A46W/KNb/l4U/06JHX+w5oPg+uDVR0A0RKBx1D32HLsqzdcIos2P2UUVVP1OdUhD0BXsKBDa21VF2XdtgaN5BMUSWLk27JTLcT14EqzEgEFF5I3MgiOJVlw+i2HhBEhWp7ERy1n+kAtCkLg/rLQVoryqpGj2oeGOFtzeY7StCkXZa16sNW4DseeBSa/5lnwXy/oB1zv0hQtlpoHdl3BQwt2yrPgn8MgjGbEHEJf65ZIoytonPRUSW9eDofSwCMHqthkBHfaV1Rx4dssnLm4or6bT0rDMMr0J7HJ7lVH/qshvJHIZeoKVcIBj891CCykzz5uorfJTfknB8038bIjX9Lw==
Content-Type: multipart/alternative; boundary="_000_MN2PR05MB60806B43DBD4D38910CBB1E3BE6C0MN2PR05MB6080namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: f7fef8e3-3d81-4d01-b069-08d753c53a1f
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Oct 2019 12:18:04.3403 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: yGArIdESDxzWpaN/Tb/GudC5ul5CHTz+hEGESt0cbjWrNbaAFUw5EZOpaQbUuGfninLE0gEM5Z8gl4g+QRmhMA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR05MB6176
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-18_03:2019-10-18,2019-10-18 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 mlxscore=0 malwarescore=0 phishscore=0 suspectscore=0 adultscore=0 spamscore=0 clxscore=1011 bulkscore=0 priorityscore=1501 mlxlogscore=999 lowpriorityscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1910180117
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/T8XTds6tO98vHo8h_PREvI1D2N0>
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 12:18:12 -0000

I was more focused towards END.DT4 SID where behavior you mentioned is possible only if we do below optimization in https://tools.ietf.org/html/draft-dawra-bess-srv6-services-02<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-dawra-bess-srv6-services-02__;!8WoA6RjC81c!VLXDHwQhv3Ai4Cky1wjCRKLg4MMbWlArh2rC0Srmtc6uKxdGYoSjuGxkKh-cx1pT$>  section 3.

when the received route is colored with an extended color community 'C' and Next-Hop 'N', and the ingress PE has a valid SRv6 Policy (C, N) associated with SID list <S1,S2, S3>, then the effective SR Policy is <S1, S2, SRv6-Service-SID>.Here if you see
S3 and SRv6-Service-SID both belong to Egress so s3 has been removed.


For you my query is removing only SRH header on PHP router will give what kind of advantage ?

Thanks
Rajesh





Juniper Business Use Only
From: spring <spring-bounces@ietf.org> On Behalf Of Wang, Weibin (NSB - CN/Shanghai)
Sent: Friday, October 18, 2019 9:26 AM
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>
Subject: Re: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

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<mailto:spring-bounces@ietf.org>> On Behalf Of Rajesh M
Sent: 2019年10月18日 6:38
To: Pablo Camarillo (pcamaril) <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>; 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

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<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04*page-24__;Iw!8WoA6RjC81c!Wogoc-HBxWprNFIMxDGoprcCPpEqeSUK6WmLst9CNbljhrh-Ur4yOghFj3kDJQnV$>

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<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04*page-24__;Iw!8WoA6RjC81c!Wogoc-HBxWprNFIMxDGoprcCPpEqeSUK6WmLst9CNbljhrh-Ur4yOghFj3kDJQnV$>


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