Re: [spring] 答复: Questions about the life span of Path Segment

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Thu, 01 August 2019 15:20 UTC

Return-Path: <Alexander.Vainshtein@ecitele.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 BCB6F120103; Thu, 1 Aug 2019 08:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecitele.com header.b=iPyva+zj; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.com header.b=QZjTP6vu
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 RgODiZQvpjfS; Thu, 1 Aug 2019 08:20:51 -0700 (PDT)
Received: from mail1.bemta26.messagelabs.com (mail1.bemta26.messagelabs.com [85.158.142.117]) (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 99250120120; Thu, 1 Aug 2019 08:20:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ecitele.com; s=eciselector10072019; t=1564672848; i=@ecitele.com; bh=TNBe5uT3qjzI9zcqP5wIB4o7L3web6boDz+lMiwXtCE=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=iPyva+zj98jNBd+D3Ebb4S1B1kPEPXL67x3LQhEMxO4+UFoZIZXjbRHBglJFDv8Cb 06gyGXBEIuZDpC1ciPBBfx6p8XSWtzDiJwTrDadbl6teXk5NjiozI6nvJgz0929FiP ilqGEZZqe55sA4hjHi0qvSbU+QtMEt60QQW9HAwI=
Received: from [85.158.142.193] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-6.bemta.az-b.eu-central-1.aws.symcld.net id 18/46-28583-053034D5; Thu, 01 Aug 2019 15:20:48 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WTe0xTdxTH+d1XL0Lx0sJ61uASi07X2UJxGQ3 M6PAfYnSMOBN1K+5SCm0sF/oggz0S1MIQdJgJyAggMFgmDwk4mCjRpYBAneMpQaJ1ig9wsAV1 I+ro1tuLzv1z8jnne37nfH/J70fjknyRnDZk2w1WjjUrqBWEZP5IuyoB36qLLC1XaE/9fU2kH XKPI23pwQJK2z/8DG0h4kuetZHxjt55Mr6+/gn2Pr6XNHHJGdkfk8bR3GaU+c/3WHZX3mWUix wNWCFaQSOmAYeR2VJCSC4RMFR2aTlpRTD8yEnxCcG04NDreuxLJEwxBk/udmNC4kZQcn1CVIj 8aYrZBO1NNyieQ5h98ND9q68JZw5jcK5lnCxENC1lzPCwLljoSYepsTlS4CiorpnCeCaYNVB8 1YHzLGZ0cPFirm++hHkHbh78muDZ37ur4MhR3y7EvAKLrmbfWZyRwdSdkz4GhoH67iFc4FCYn faQQn8y3Lxbi4T6aih3V4oEXgWjJ4uW6ztg8mgrwVsGJhx+mNHxVwFmGsHxgmZK6FFCwdUDyz 1muNX5plBeB46FalLgMCj+dpoQznZS0DNRjQt30cNA5SPiGFJXvGRbYA4GyhZ8LGaCYfCbO0S FdwXOvAGt5yKEltVQUnRLJPB6yKusEr1cr0GiRqRNtprSjPZ01mRWaSIjVRrNRlW0ShOtZj9V JasNWSq9gbNbWa+oZj+xqW056Xpzipoz2NuR97mlWETBZ5Gz9ze1E71KY4pQ8Y7rcTpJUHJGS o6RtRn3WbPMBpsThdG0AsTh2FadJNhqSDNkp5rM3kf7XAY6UBEifpuXxbZMNt1mShMkF0qkj8 1W1eF0fke1Ny4eqvXGhcZ6nn3xyzY+9lY11OESgsvgDHKZWMoPYvhBxizuxZrn32MUrZJLxcj Pz08SmGmwppvs/9cfIBmNFFJxOfJOCTRx9hduHniNYl6jUjKON2pn/5PkuZhMs47zdHfERgZW rhw7/fr+A46+FqKqZnLDFWfvovGG6/yWLGV99+lyTia/QM95PMxkUtFYAJYY0bUzNtulXN94o q3zULFRF6DvSz0l96xxbJp7N2ejquLP76I3DBx3JXQpYyxVqtamiNiRn+PWDhp3/f6UfWzrse Db+0s3h/eHhPV5hqmgoQ/R+dzd1B+fJX5eE7Rtz5miJSV54XJCq3pp5/0B2X1i4qckxSDqmG/ y3MOubU+aPCz7MU+UF+Q/Mq5l11pi7t0+Meveq3sv6ql5RPraTExpkP6ryV2W/R/dDux5a+zM XyvHlmx7vgieSd39S5lqJLR2s4cMoK58EHU2n1IQNiOrUeJWG/svDcumaJkEAAA=
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-5.tower-238.messagelabs.com!1564672844!41522!1
X-Originating-IP: [18.237.140.178]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.43.9; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 31850 invoked from network); 1 Aug 2019 15:20:46 -0000
Received: from p01c.mail.dlp.protect.symantec.com (HELO mail.ds.dlp.protect.symantec.com) (18.237.140.178) by server-5.tower-238.messagelabs.com with ECDHE-RSA-AES256-SHA384 encrypted SMTP; 1 Aug 2019 15:20:46 -0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LrcJsX7Hn/TPuMSEd0RBEo6VXRX3CuXwY9OdWbMGSQlicTyIJOJcR50grNe2WMCqmvoFOPSxzHOGS4KtNjOV6IKpe3DH5S62mryINBSrI+gE6uobtQupoa3ADd0XYzmiyjI9FSICDSZ3YnIOvzueur64mNu2qiFpXn6Im4/BjPWMxA9n4KiPJJ9JMN8K7KVxj1UWkic+0ISHs3Nnoq05+Z9+tF+5AItGOVXDmG5+h7E16x6Xx+OfnDsnIsbGZQ0nnYuMIUrpUs+ErPHVyAGKIAOjRVj969Y07mA8/gqCrF+DpbcAtQKuWNttZSUbDGmh5lFrwSnbIxXQsF3GwCpZXQ==
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=sm0x2udzy/Ufpo4TIamuRLaDOmN+Cse5SiwTKbNgn2o=; b=Z5JeS7e2B31/zzBXybONJqttrtzWReAvvWD9BtqKR/xYJtCiecbC0rWpGoRtAvk88oJUkbwFuGXSml5jk1/BOKU2LO/MKO9xms6s5ftgL+g6kMTFtKU9dsLmFWBSv87x5FGatbkN1c2o6GtA4DuDGx2kwAtgohHve11mjaE8iiEokfpcLPoMvjSytLW39xNG2bsM3FE5LSPvzT+O4bq2LmIA6Afx0cKEHwW2HWK7O8OeE/dPKlg0DZ92HRKGMz+XAbDlByZPZipWwbtYGHuyGTfETLzmiUxj4Lq1cGtXROQ9PVDuLJMZuurtgk4Yt/s2WEKbJ51sQcuAAV0lB3JVHg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=ecitele.com;dmarc=pass action=none header.from=ecitele.com;dkim=pass header.d=ecitele.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector2-ECI365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sm0x2udzy/Ufpo4TIamuRLaDOmN+Cse5SiwTKbNgn2o=; b=QZjTP6vuFo/rPwO15cBjP7e+RCBP4zbzbDOgU8TfBYu+96gFxevdznMnhf7yB8nxobz4iDpOoiZGMYEW5O5sUwaeKpeyj5nqo5HM/5aMQnSw4KFO5ArycOzKX6quL3+ihyWwFYw/BiZKkJM4gjbl/OT2IvarNTZ3XzPVPhUFviU=
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com (52.135.146.159) by AM0PR03MB4196.eurprd03.prod.outlook.com (52.134.89.74) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.15; Thu, 1 Aug 2019 15:20:41 +0000
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com ([fe80::b990:5b8b:e1bf:f977]) by AM0PR03MB3828.eurprd03.prod.outlook.com ([fe80::b990:5b8b:e1bf:f977%7]) with mapi id 15.20.2115.005; Thu, 1 Aug 2019 15:20:41 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com>, "Chengli (Cheng Li)" <chengli13@huawei.com>
CC: "spring@ietf.org" <spring@ietf.org>, "draft-ietf-spring-mpls-path-segment.authors@ietf.org" <draft-ietf-spring-mpls-path-segment.authors@ietf.org>, "draft-ietf-spring-mpls-path-segment.authors@ietf.org" <draft-ietf-spring-mpls-path-segment.authors@ietf.org>
Thread-Topic: 答复: Questions about the life span of Path Segment
Thread-Index: AQHVSGI7V57QNfT8nUODjh+CEYl+M6bmZiZg
Date: Thu, 01 Aug 2019 15:20:41 +0000
Message-ID: <AM0PR03MB3828E60C47BDCE117D3831A29DDE0@AM0PR03MB3828.eurprd03.prod.outlook.com>
References: <A48750D3-3B63-45A3-A593-B81AEC2DFBB4@cisco.com>
In-Reply-To: <A48750D3-3B63-45A3-A593-B81AEC2DFBB4@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.241.1]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ff181731-9137-406a-eabc-08d71693d104
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:AM0PR03MB4196;
x-ms-traffictypediagnostic: AM0PR03MB4196:
x-microsoft-antispam-prvs: <AM0PR03MB41961DBA6BEF31B66EF05E1E9DDE0@AM0PR03MB4196.eurprd03.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01165471DB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(346002)(376002)(39860400002)(136003)(396003)(53234004)(189003)(199004)(51444003)(51874003)(110136005)(316002)(86362001)(9686003)(6306002)(54896002)(66066001)(7736002)(53936002)(54906003)(81156014)(81166006)(236005)(8936002)(2906002)(33656002)(413944005)(229853002)(55016002)(76176011)(102836004)(224303003)(6506007)(7696005)(53546011)(68736007)(790700001)(6436002)(99286004)(66946007)(14444005)(26005)(14454004)(256004)(66446008)(66476007)(64756008)(11346002)(66556008)(76116006)(446003)(186003)(74316002)(52536014)(5660300002)(71200400001)(71190400001)(476003)(6116002)(486006)(478600001)(3846002)(4326008)(6246003)(25786009); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR03MB4196; H:AM0PR03MB3828.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ecitele.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: PNvhvQGFA2ttdW1rKPwPRaHSsUUJullwVNgvLqevbx8ym+1bZIzz38DpG+wm27hgauZqAqLxYJWgRzo70eA6bQOqioHCag1+SDa3BBPqTTRbFC9n8Och5chrl9KIOGpHtM6RQPzGUKLyZKT6bJderWsqyNWsCYzF4RE6UE+ERcRHPlkqvrEYBUYbgc9LnBW/oCqRFhIKqFALhpzySEjkqAbd85804J8hc7wPYa2Cey0ysmkkczD7CwismL1N865734Div6AbSCSoimkGBnCGID1AwTcNu/L755t8/MBElkSs2evqCjSND5vCXciJw4A+yUHT4er/EQ9TvyFYowVPnMgf3LN5nLSecdmF5NA04cVptzKbyr/in9PZQO01d/IVmE/cTgfFfHo8ejcM4xapdWbE6KfsMa9yDNwkzC7SRmA=
Content-Type: multipart/alternative; boundary="_000_AM0PR03MB3828E60C47BDCE117D3831A29DDE0AM0PR03MB3828eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ff181731-9137-406a-eabc-08d71693d104
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Aug 2019 15:20:41.7889 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: alexvain@ecitele.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR03MB4196
X-CFilter-Loop: Reflected
X-DetectorID-Processed: d8d3a2b3-1594-4c39-92fb-b8312fe65a8a
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/vRSI2ufPcuCGbX9JFQjLpOxMww0>
Subject: Re: [spring] 答复: Questions about the life span of Path Segment
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: Thu, 01 Aug 2019 15:20:56 -0000

Dear all,
Lots of thanks for your responses and apologies for my much delayed reaction.

I did not mention it in my original email, but the scenario when a Path Segment is used by the DP to collect some kind of statistics (e.g., packet loss) for the SR policy for which it has been allocated has been the major drive for raising my questions.

In this scenario when the path becomes invalid the Path Segment allocated for it should be detached from whatever statistics have been collected using it to prevent the situation when collected statistics for the now invalidated path and for some new one (e.g., the recomputed one between the same two nodes) are mixed.

I think that this is roughly what Rakesh has said in his response. And I think this should not be left for the implementation to decide but, rather, explicitly required in the draft.

My 2c,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com

From: Rakesh Gandhi (rgandhi) <rgandhi@cisco.com>
Sent: Thursday, August 1, 2019 3:11 PM
To: Chengli (Cheng Li) <chengli13@huawei.com>; Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>; draft-ietf-spring-mpls-path-segment.authors@ietf.org
Cc: spring@ietf.org
Subject: Re: 答复: Questions about the life span of Path Segment

Hi Sasha,
For PM loss measurement use-case, the same path segment ID can be used during the life span of SR Policy.

Thanks,
Rakesh


From: "Chengli (Cheng Li)" <chengli13@huawei.com<mailto:chengli13@huawei.com>>
Date: Friday, July 26, 2019 at 11:43 AM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>, "draft-ietf-spring-mpls-path-segment.authors@ietf.org<mailto:draft-ietf-spring-mpls-path-segment.authors@ietf.org>" <draft-ietf-spring-mpls-path-segment.authors@ietf.org<mailto:draft-ietf-spring-mpls-path-segment.authors@ietf.org>>
Cc: "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>
Subject: 答复: Questions about the life span of Path Segment
Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>
Resent-To: <chengweiqiang@chinamobile.com<mailto:chengweiqiang@chinamobile.com>>, <lihan@chinamobile.com<mailto:lihan@chinamobile.com>>, <mach.chen@huawei.com<mailto:mach.chen@huawei.com>>, "=SMTP:rgandhi@cisco. com" <rgandhi@cisco.com<mailto:rgandhi@cisco.com>>, <royi.zigler@broadcom.com<mailto:royi.zigler@broadcom.com>>
Resent-Date: Friday, July 26, 2019 at 11:43 AM

Hi Sasha,

Many thanks for you comments and sorry for my delay. Please see my reply inline.

Cheng

________________________________
发件人: spring [spring-bounces@ietf.org] 代表 Alexander Vainshtein [Alexander.Vainshtein@ecitele.com]
发送时间: 2019年7月24日 23:27
收件人: draft-ietf-spring-mpls-path-segment.authors@ietf.org<mailto:draft-ietf-spring-mpls-path-segment.authors@ietf.org>
抄送: spring@ietf.org<mailto:spring@ietf.org>
主题: [spring] Questions about the life span of Path Segment
Dear colleagues,
I have a couple of questions about the life span of the Path Segment.

Suppose that some entity has computed and instantiated an SR LP that follows a specific path from the ingress node to the  egress node across a single IGP domain. This path is expressed as a sequence of valid IGP Segments (e.g., Node and/or Adjacency segments) .
Suppose also that a Path Segment has been allocated by the egress node for this path, and the ingress node is aware of this and inserts the label acting as the SID for the Path segments immediately after the last SID of the path.

Now my questions:

1.       What happens to the Path Segment when one of the IGP segments defining the original path fails?

a.       To the best of my understanding the path itself becomes invalid

[Cheng] Agree. But IMO, the path segment has the same life circle with the associated LSP. so it MAY not be invalid in FRR since the egress, ingress even the controller does not know that until the Reroute is triggered, then it should be treated as invalid.



b.       Will the Path Segment that identifies the now invalid path be retained indefinitely, or would it be invalidated as well and the label acting as its SID released?

[Cheng] Honestly, I think it depends on implementation. The the LSP fails, then the related Path Segment is invalid. But when the Rerouted LSP is installed, the path segment should be allocated, and we don't make any assumption of the value of the path segment. It CAN be the same value as the previous one.



2.       Suppose that the entity that has computed and instantiated the original path re-computes it and instantiate a new valid path.

a.       Should the new path (that replaces the invalidated original one) be allocated with the same Path Segment as the original path, or should a new Path Segment be allocated for it?

[Cheng] Same as above. As long as the information is synchronized between the controller and the data plane, any value is OK. But the same path segment should be recommended.



b.       If the Path Segment allocated for the invalidated path is released (see (1b) above), can the label that identified it be re-used as the Path Segment ID immediately, or only after some delay?

[Cheng] It depends on the implementation. Just to make sure that the path segment can be available.



From my POV the answers to these questions do not depend on the actual method by which the Path Segments are allocated and propagated from the egress node to the ingress one.
And while my questions explicitly mention IGP Segments that define the SR LSP for which the Path Segment is allocated, the desired behavior should not depend on the type of segments used in the definition of the path.
[Cheng] Sure.

Your feedback would be highly appreciated.

Regards, and lots of thanks in advance,
[Cheng] Thank you as well for valuable comments.
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>


___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this
transmission in error, please inform us by e-mail, phone or fax, and then delete the original
and all copies thereof.
___________________________________________________________________________

___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is 
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this 
transmission in error, please inform us by e-mail, phone or fax, and then delete the original 
and all copies thereof.
___________________________________________________________________________