RE: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Thu, 12 July 2018 11:26 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B7B1310D1; Thu, 12 Jul 2018 04:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.78
X-Spam-Level:
X-Spam-Status: No, score=-1.78 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.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 jsb8b2wsOufi; Thu, 12 Jul 2018 04:26:22 -0700 (PDT)
Received: from mail1.bemta25.messagelabs.com (mail1.bemta25.messagelabs.com [195.245.230.129]) (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 725B0130DFA; Thu, 12 Jul 2018 04:26:21 -0700 (PDT)
Received: from [46.226.53.55] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-1.bemta.az-c.eu-west-1.aws.symcld.net id ED/36-02793-BDA374B5; Thu, 12 Jul 2018 11:26:19 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1VTbUxTVxjeuef29kq4y6WgvOuKxE7nR3a7Vsi 8Y7L5R22CLP7xh7K5XeBCO0shvWXAsh+FjS2DuMzRMm0BQUj8gnWSGZk0ujA1a6MDu2xsnXwI uChTtxk/UIzbvT3q3P3x5jnv87zv85zkXBYbDuqNrFzrlT1uyWVmUujclXNLhUTexiJrZDRb7 O4FcW6gDYtz4fXiV9czxKnwp0j8ZbiFEhu6GrB4sq8biyNX57EYm5TWpdh7716n7N8Ex/T2np 67lH204Se9/cPfo4x98EgntZnZpnO6iytr39Y5fgif01UdnaBqf/soQvvQZIJqQiksze/DkAj dY7SDgfdTEDv1MSaHaQSR4+f0TWgBy/D50H94jNFwBv8KTO4KJycwfwJD34EjlEak82WwP+hD RFQOoakZiuA82L2nT9eEWNVvGfTHjVqb4yXoDIzSxOxHHZwO/5N0XsB/guDql35aUyF+EdyJ9 SYXYT4TEjN7kxh4Hnoiw5jghXBl+oGO6Ith4lIXIv0lsHu8TU9wFsT3NiPNAPhjFHzfGHtICP BXIIC1dMA/B19ffpPAQrh55nkin0Rw8O92Pem/AAPXXieTVXD/5zgmmg4Eft89HSEWw6GdF2l CfIuhfiLKEMIEl6eDDydGGZi+EaA+Q0LwicsR7IbBlvkk5vg0iO6ZoYOqOeZXQvj4i0SyBPzN F/UEr4DGtnb9k/1OpD+ExGKPs9zhrZCcLsFmtQo222phtTVHsOXkWqT3hBKLXC3UyIpXsFmkG sWi1FWUuEotbtnbj9SH+ZT6DaDE7ZIh9AxLmRdyxrz1RYaniytL6xyS4njLU+2SlSFkYlkzcB te3lhkSPPI5XJtmdOlvu5HNLCp5gwuW6M5pUqqUJzlhIqhAvbUuP9zzI4ka8fpgFrv/6nVE82 tar2gVQPtrnTLxkzutraC11Y4qt2PDR79QXGUZUznkBrZkFoleyqc3v/zsyiTReZ0bo22JdXp 9j7OMatGpNSI20s3aBG90n+U0Yfqv2jZeaN1E85ZJlz4bvHa9BWh+Zb8YOhZRXo3/9bY2Ygj6 ro5PhOvOzvxRsGu/duuDWTPNrpGtn9QM5R7vtB5ntuihDo6r5je2dr6a2vW1jXRHZbuqfaCwV VdL+1r2lFWn1b/amGfz2py/NH12to7w6nMuksPlp45WTd/a5F/+dGS901mWnFItlXYo0j/Alg 8kHQ8BAAA
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-10.tower-307.messagelabs.com!1531394774!4677828!1
X-Originating-IP: [52.41.248.36]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.9.15; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 2996 invoked from network); 12 Jul 2018 11:26:17 -0000
Received: from us-west-2a.mta.dlp.protect.symantec.com (HELO EUR01-HE1-obe.outbound.protection.outlook.com) (52.41.248.36) by server-10.tower-307.messagelabs.com with AES256-SHA256 encrypted SMTP; 12 Jul 2018 11:26:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ecitele-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3a5kgopWuUTnR+wubi1iqA1GpUZVxpG+8a4YlAskWFM=; b=Nzd8naCtHOgIqu3lNX9p+53PDm90AlFuoiBf4mf1WbKY2+NEw9sq1w3eaJA9mTUoDr0OT3SZt8DMYskUG02oFYU3tHy7MEOUki9eS/HwqGz98AgKIUuK3U5o5qpsHiW+yKsEV3/yFG66QS1uXhgRyZEBsheNTiUJhaAcSqDZtqw=
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com (10.167.226.155) by DB5PR0301MB2104.eurprd03.prod.outlook.com (10.167.228.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.952.17; Thu, 12 Jul 2018 11:26:12 +0000
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com ([fe80::6c62:c2c0:1d05:4e77]) by DB5PR0301MB1909.eurprd03.prod.outlook.com ([fe80::6c62:c2c0:1d05:4e77%2]) with mapi id 15.20.0952.017; Thu, 12 Jul 2018 11:26:12 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
CC: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "pfrpfr@gmail.com" <pfrpfr@gmail.com>, "draft-bashandy-rtgwg-segment-routing-ti-lfa@ietf.org" <draft-bashandy-rtgwg-segment-routing-ti-lfa@ietf.org>, "daniel.voyer@bell.ca" <daniel.voyer@bell.ca>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Ahmed Bashandy <abashandy.ietf@gmail.com>, Robert Raszuk <robert@raszuk.net>, Chris Bowers <cbowers@juniper.net>, Stewart Bryant <stewart.bryant@gmail.com>
Subject: RE: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa
Thread-Topic: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa
Thread-Index: AQHT9sbRZr09Sx5RRE2SlwYEgLprKaSLVK0wgABYMmA=
Date: Thu, 12 Jul 2018 11:26:12 +0000
Message-ID: <DB5PR0301MB19097AB7FA7181464B765B779D590@DB5PR0301MB1909.eurprd03.prod.outlook.com>
References: <1e42030f-3d68-fca3-500c-95ab7303e7cd@gmail.com> <F0098308-4F1E-4596-B3F9-B6740BA88F9A@gmail.com> <bfbe9775-ee81-b1fe-bb1f-a02392bc6fb5@gmail.com> <43389eec-6d63-ee35-54ed-19562b24562b@gmail.com> <12E9EB99-2970-49B6-9407-FE6AEAB3A0BB@gmail.com> <SN6PR05MB44305802FF3330DC2AE27F9CA96E0@SN6PR05MB4430.namprd05.prod.outlook.com> <CA+b+ERm=Jczivo0sJGuHWyP7UJbJFY=+N-vyQK7H_Es2anLGmQ@mail.gmail.com> <DB5PR0301MB1909BF5C925473CB3BC97BE79D6D0@DB5PR0301MB1909.eurprd03.prod.outlook.com> <27db8d16-6120-17e9-55fa-30d35be97b32@gmail.com> <98d610d9-1dd4-3025-3b5c-070b6120cda7@gmail.com> <30046_1531388953_5B472419_30046_355_1_53C29892C857584299CBF5D05346208A47AEA48D@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <30046_1531388953_5B472419_30046_355_1_53C29892C857584299CBF5D05346208A47AEA48D@OPEXCLILM21.corporate.adroot.infra.ftgroup>
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-microsoft-exchange-diagnostics: 1; DB5PR0301MB2104; 7:tU+0rXuwm5dXCBFXJg/FI8nJ1MYs6pa/YYDnsLoFaY2+cZ57Eor+hL/DRKof5wnKjK+lTcaV7MVaKQlwuJj6CZGqeyWa+PjCqNXEtL1IcKnJuTYsV4EYok0c/xsASISmp+JUu+Adq/wwXHAWVf7xLi47j7dxk0aGMNoOvEFJoZk4z70V3idQmVBKHgEJGu3BenXKO3bz69XeK+C9BS4YgBySksqcPk4zwsuuyJrYYVZn2+tKVkC/e2haMh/8ER3G
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 1569e739-01f7-4fd1-3b29-08d5e7ea4602
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(48565401081)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:DB5PR0301MB2104;
x-ms-traffictypediagnostic: DB5PR0301MB2104:
x-microsoft-antispam-prvs: <DB5PR0301MB21045B186C93776032A792349D590@DB5PR0301MB2104.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(226690903318834)(138986009662008)(85827821059158)(18271650672692)(21748063052155)(279101305709854);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3002001)(3231311)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123560045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:DB5PR0301MB2104; BCL:0; PCL:0; RULEID:; SRVR:DB5PR0301MB2104;
x-forefront-prvs: 0731AA2DE6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(366004)(346002)(39860400002)(376002)(252514010)(189003)(199004)(51444003)(81156014)(478600001)(72206003)(6916009)(8676002)(790700001)(39060400002)(25786009)(81166006)(8936002)(7416002)(66066001)(256004)(68736007)(93886005)(486006)(5630700001)(3846002)(4326008)(6116002)(2906002)(5660300001)(54906003)(11346002)(316002)(476003)(105586002)(2900100001)(14444005)(6506007)(55016002)(5024004)(6306002)(53546011)(446003)(54896002)(236005)(99286004)(53936002)(6436002)(9686003)(97736004)(5640700003)(86362001)(106356001)(102836004)(186003)(2351001)(26005)(2501003)(229853002)(6246003)(74316002)(76176011)(7696005)(7736002)(5250100002)(14454004)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR0301MB2104; H:DB5PR0301MB1909.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-microsoft-antispam-message-info: 5eSjGwSOD6UrpZGs2ffwcwXOHJMHUlqXSz6XkMvB3C75GsVNgXF23ut8djcbP4l79PeMe8AQVR3ilZ07zkRrbSa/nmWqGGfj7SogfbRkeKWNGbyAKHNR/kaSf0izdrYS6xtiLD/Qsezec8K1KvOAFTqFZntMzQ02wGi8hCneff185OOiuw6TdXfI9e7IvdCHSUxgckn19xJJYUGZVC46UWboDC1gzOHvZNIg8nLjATlBt+/vXiiI4Ugrka1BA0KFLdUAVhcnIHyp6DrGFFudt8Xi0HuMAtwLGzmZcb9vfDTojfst0UTrojjOywpcTz4KdJLJoYeuCj6iT7SYkHEPtSc/No0sADG19yeR6e2Ju9w=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR0301MB19097AB7FA7181464B765B779D590DB5PR0301MB1909_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1569e739-01f7-4fd1-3b29-08d5e7ea4602
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jul 2018 11:26:12.4276 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR0301MB2104
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/5tDv2ZDX99FTAGUm7ptxmXNQPic>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 11:26:26 -0000

Bruno,
It seems there is some misunderstanding, and I will try to clarify it.

To the best of my understanding, the following text in Section 1 of the draft presents the benefits of using post-convergence path for FRR:

   As the capacity of the post-convergence path is typically planned by
   the operator to support the post-convergence routing of the traffic
   for any expected failure, there is much less need for the operator
   to tune the decision among which protection path to choose.  The
   protection path will automatically follow the natural backup path
   that would be used after local convergence.  This also helps to
   reduce the amount of path changes and hence service transients: one
   transition (pre-convergence to post-convergence) instead of two
   (pre-convergence to FRR and then post-convergence).

I see two different claims of benefits from using post-convergence path in this test fragment

1.       One path change and therefore one service transient instead of two

2.       Post-convergence path is taken into account in the operator’s panning (e.g., by allocating sufficient resources for traffic flows on both pre-convergence and post-convergence paths).


Speaking just for myself, I think that neither of these claims is justified for traffic flows that do not originate at the PLR.

E.g., consider Stewart’s example and the traffic flow from A to E

1.       This flow will experience two path changes (pre-convergence--> FRR and FRR --> post-convergence

2.       The network operator will not take links C-F, F-G and G-D for consideration in its planning of pre-convergence and post-convergence paths for this flow.

Did I miss something substantial?
Regards,
Sasha

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

From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
Sent: Thursday, July 12, 2018 12:49 PM
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: rtgwg-chairs@ietf.org; pfrpfr@gmail.com; draft-bashandy-rtgwg-segment-routing-ti-lfa@ietf.org; daniel.voyer@bell.ca; rtgwg@ietf.org; Ahmed Bashandy <abashandy.ietf@gmail.com>om>; Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>om>; Robert Raszuk <robert@raszuk.net>et>; Chris Bowers <cbowers@juniper.net>
Subject: RE: Request for RTGWG Working Group adoption for draft-bashandy-rtgwg-segment-routing-ti-lfa

Stewart,

Please see 1 comment inline [Bruno]
Trimming the text to ease the focus on this point

From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
Sent: Tuesday, July 10, 2018 2:40 PM



On 09/07/2018 20:53, Ahmed Bashandy wrote:
[…]



b.       Selecting the post-convergence path (inheritance from draft-francois) does not provide for any benefits for traffic that will not pass via the PLR after convergence.

                                                               i.      The authors claim to have addressed this issue by stating that “Protection applies to traffic which traverses the Point of Local Repair (PLR). Traffic which does NOT traverse the PLR remains unaffected.”

SB> It is not as simple as that, and I think that the draft needs to provide greater clarity.

I think there will be better examples, but consider

              12
      +--------------+
      |              |
A-----B-----C---//---D----E
        10  |        |
            F--------G

Traffic injected at C will initially go C-D-E at cost 2, will be repaired C-F-G-D-E at cost 4 and will remain on that path post convergence. This congruence of path is what TI-LFA claims.

However, a long standing concern about traffic starting further back in the network needs to be more clearly addressed in the draft to clearly demonstrate the scope of applicability.

For traffic starting at A, before failure the path is A-B-C-D-E cost 13

TI-LFA will repair to make the path A-B-C-F-G-D-E cost 15 because TI-LFA optimises based on local repairs computed at C.

After repair the path will be A-B-D-E cost 14.

[Bruno] The draft is about IP Fast ReRoute (FRR).
FRR is a local reaction to failure, so by hypothesis, all nodes but the PLR are not aware about the failure. This includes all upstream nodes which do keep forwarding traffic through the same path, i.e. via the PLR.
The argument that the path would have been shorter if upstream node were aware of the failure to reroute before (or that the PLR should send the packet back in time) is not relevant.
The only question which matter is: from the PLR to the destination, which is the best path to use?
I, and the draft, argue that the best path in IP routing, is the IGP shortest path. Whichever type of metric you choose (e.g. bandwidth, latency, cost…). Do you disagree on this?


Now, eventually we can narrow down the discussion to the choice of terms. We can discuss about the term “post-convergence paths from the point of local repair », which you don’t think to like. Although, the term seems technically true to me, I would also be fine with changing from  “post-convergence path” to “optimal IGP shortest path”



So the draft needs to make it clear to the reader that TI-LFA only provides benefit to traffic which traverses the PLR before and after failure.

[Bruno] No, that is not true. cf above.
--Bruno



Traffic which does not pass through the PLR after the failure will need to be traffic engineered separately from traffic that passes though the PLR in both cases.






_________________________________________________________________________________________________________________________



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.

___________________________________________________________________________

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.
___________________________________________________________________________