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

Stewart Bryant <stewart@g3ysx.org.uk> Mon, 07 August 2017 09:14 UTC

Return-Path: <stewart@g3ysx.org.uk>
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 94D3E131EC3 for <rtgwg@ietfa.amsl.com>; Mon, 7 Aug 2017 02:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level:
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_KAM_HTML_FONT_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=g3ysx-org-uk.20150623.gappssmtp.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 JQpTPONaQl6X for <rtgwg@ietfa.amsl.com>; Mon, 7 Aug 2017 02:14:02 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67D7F131DAC for <rtgwg@ietf.org>; Mon, 7 Aug 2017 02:14:01 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id m85so2168537wma.0 for <rtgwg@ietf.org>; Mon, 07 Aug 2017 02:14:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=g3ysx-org-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=s8hLD+nAzLNCqGBy/c9efBUT0yKEAYbQoHdleqrB6SE=; b=A6oFx5JCfldvPLWg5tuMfXyPzT2ssGoUaF8BL60fL/f7XlZ/8NnVF04vLIx5tJnHEb rHKpMYQKTDMGqBQklYQ5eO9dndXSUZzgwQCvUP9uQhSvcjFd+7ORARry5kttmbv1b3Gx j296jxQUi35UzjtYw3nvYAmYyQ4CZT2APn2i0FDnMX3w8zTtanmynrFLqYtFQzsD0+QN 5HwyoBreTCq9a8w9aOVCwdSg5/5oZN1e65PpOKSHp8f61nxN7dYhij7+Ft+amMwIbbUs KteEg7Ht6EQeM1Cc+8Ve4lcT+nHQ4LfNC0WRrRFDKmJESTdhCBkFHtE474ANDaxcfBTx 4RHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=s8hLD+nAzLNCqGBy/c9efBUT0yKEAYbQoHdleqrB6SE=; b=Uhua9Z2q9wsKbmEC68/eHA/m7yfKXTdB6puOJskI+C0Jkwkwf+fWC1Q8xI5DODijvK JAwjkKvYQiBCzEGbHfK6F3lAANkS0lCQF5tvezIV/kfAt5FEphV+xCRhiZXLkoTY+c5g TA/wDm97htaA4zqo7irIx07oQHjJYf16M780v/L/39vIPMAFdi77bLFrqpPrAK4oKapF eO/mGmn+CtlDS4fORRai7FmA2g3O0mf8c3Ky1aYgjaXv6/EU3vNcqcAW1T9oopVhxPKc pu6IICL5OcSwVjsA0P6X3Y5fuRrzj/tnkE74DV5neUcORDb9ZMvVGdD9JqB0BbfXLL7M 2TCw==
X-Gm-Message-State: AHYfb5jWLKkG2s99XOw23w3SRPQyLqotdniLo1mxaZ63qHsdp7PIXyeJ ZGdL4LQNnfoy1dzb
X-Received: by 10.28.23.195 with SMTP id 186mr180214wmx.173.1502097240383; Mon, 07 Aug 2017 02:14:00 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 9sm11591600wmo.35.2017.08.07.02.13.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Aug 2017 02:13:59 -0700 (PDT)
Subject: Re: I-D Action: draft-bashandy-rtgwg-segment-routing-ti-lfa-01.txt
To: Sikhivahan Gundu <sikhivahan.gundu@ericsson.com>, "Ahmed Bashandy (bashandy)" <bashandy@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Cc: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "pfrpfr@gmail.com" <pfrpfr@gmail.com>
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>
From: Stewart Bryant <stewart@g3ysx.org.uk>
Message-ID: <b991e0eb-97f0-cd5f-96c8-7ce77d880614@g3ysx.org.uk>
Date: Mon, 07 Aug 2017 10:13:57 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <HE1PR07MB170870985873654D8C0BC340EAB50@HE1PR07MB1708.eurprd07.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------E64E9A60D8F1B961938D1112"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/v280EAv6mEuTDb6ccwZ6KSshdrQ>
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 09:14:05 -0000


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