Re: I-D Action: draft-bashandy-rtgwg-segment-routing-ti-lfa-01.txt

"Ahmed Bashandy (bashandy)" <bashandy@cisco.com> Mon, 07 August 2017 18:23 UTC

Return-Path: <bashandy@cisco.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 C6DB5132373; Mon, 7 Aug 2017 11:23:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 UKQ4LF4D2Ggo; Mon, 7 Aug 2017 11:23:48 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DE4113240F; Mon, 7 Aug 2017 11:23:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8722; q=dns/txt; s=iport; t=1502130225; x=1503339825; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=8ta5T/vr9jU9iOrOdxfRSVyI1KYxCzv2+ZtwLg5qGxs=; b=b/qDxzKSZdmLKBVRM157ezJC/ynqTPDAh/PATPUlWx34fmZXyQZNrf/w 5ZtjLooavjvnHHsYdYgRYKrnQlYcB1EPaX3ypKqWlqACPOnRPOvkmkSTt mBCSIyrC2+OtHlZcK83fFaOhbSCDvL+9fxzOqZEMtFq0Gp5l5UAg6WjrK c=;
X-IronPort-AV: E=Sophos;i="5.41,339,1498521600"; d="scan'208,217";a="282746873"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Aug 2017 18:23:44 +0000
Received: from [10.154.131.17] ([10.154.131.17]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v77INiKo012687; Mon, 7 Aug 2017 18:23:44 GMT
Message-ID: <5988B030.8080001@cisco.com>
Date: Mon, 07 Aug 2017 11:23:44 -0700
From: "Ahmed Bashandy (bashandy)" <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Stewart Bryant <stewart@g3ysx.org.uk>, Sikhivahan Gundu <sikhivahan.gundu@ericsson.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
CC: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "pfrpfr@gmail.com" <pfrpfr@gmail.com>
Subject: Re: I-D Action: draft-bashandy-rtgwg-segment-routing-ti-lfa-01.txt
References: <150027597752.32726.7270829130613224040@ietfa.amsl.com> <596C668E.9050106@cisco.com> <HE1PR07MB1708E945640F865CA32D85F7EAB30@HE1PR07MB1708.eurprd07.prod.outlook.com> <5984CFB0.3070908@cisco.com> <HE1PR07MB170870985873654D8C0BC340EAB50@HE1PR07MB1708.eurprd07.prod.outlook.com> <b991e0eb-97f0-cd5f-96c8-7ce77d880614@g3ysx.org.uk>
In-Reply-To: <b991e0eb-97f0-cd5f-96c8-7ce77d880614@g3ysx.org.uk>
Content-Type: multipart/alternative; boundary="------------000701020008060802000902"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/VZBwAB6maW_dVFSeUxYDOkyZyZQ>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 07 Aug 2017 18:23:50 -0000

See my reply to Sikhi

Thanks

Ahmed


On 8/7/2017 2:13 AM, Stewart Bryant wrote:
>
>
>
> On 07/08/2017 06:45, Sikhivahan Gundu wrote:
>>
>> By “ambiguity”, I meant that backup calculation taking SRLG into
>>
>> account is  based on speculated topology,  whereas computation of
>>
>> post-convergence path, ie, SPF, is based on actual topology.  This
>>
>> seems needs reconciling since in  TI-LFA the backup is by definition
>>
>> the post-convergence path, with a single path-transition after
>>
>> link-failure as the intended outcome. Do I understand correctly that
>>
>> the draft prefers to relax that expectation for SRLG?
>>
>>
>
> Yes, that is a good point, in the event of an incomplete failure
> of an SRLG, there may not be congruence between the
> FRR path and the post convergence path. This certainly
> needs further study.
>
>   *
> A--------//---------B
> |                   |
> |  *                | cost 2
> C-------------------D
> |                   |
> |                   | cost 100
> E-------------------F
>
>
> AB + CD in same SRLG
>
> TiLFA path is ACEFDB
>
> Post convergence path is ACDB
>
> In this case I think that the impact is just more SR hops in the
> repair path than might be needed without the SRLG, but we do need to
> be sure  that there are no pathological  cases in
> topologies that lack the proposed congruence, and as
> Sikhivahan notes this effect does need to be clarified in the
> text.
>
> - Stewart
>
>
>
>