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

"Ahmed Bashandy (bashandy)" <bashandy@cisco.com> Mon, 07 August 2017 20:04 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 69E02132758; Mon, 7 Aug 2017 13:04:38 -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 bPyEQY_FPYPQ; Mon, 7 Aug 2017 13:04:36 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46FB413277B; Mon, 7 Aug 2017 13:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13715; q=dns/txt; s=iport; t=1502136275; x=1503345875; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=HuGdGw6MdV/3DumfnyL7iLVPb91s7ipPd6fcqmeRRoE=; b=SSg5rxMcibfTm/WlAlRO4EaBuaJKDmxn1Rmj09t0iQUCF18x49affjgx PACp8ChHCr6+ssbCejg2myTMXmAowUw3aRbdQpyC4BhHENyOO+ORF/XGj NH5fWxJ+KVHzQl7BEUsoartvn0Du8oaqNOwpmskY3qsX8t5+4vywsvJVI 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DlAACMx4hZ/5FdJa1cGQEBAQEBAQEBAQEBBwEBAQEBgm9rZIEUB44IkAWBbog2iCyFMw6CBCEBCoUbAoRbPxgBAgEBAQEBAQFrKIUYAQEBAQMBAStBCxACAQgRBAEBFhIHIQYLFAkIAgQBDQUIiUNMAxUQrkUnhwwNhA4BAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYMoggKDL4MngleBWQF4CYU1BYlvlWQ8Ao8+hGqSVYwtiVoBHziBCncVSYUXHIFndohdgQ8BAQE
X-IronPort-AV: E=Sophos;i="5.41,339,1498521600"; d="scan'208,217";a="277900837"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Aug 2017 20:04:34 +0000
Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v77K4Xiu012734 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 7 Aug 2017 20:04:33 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 7 Aug 2017 16:04:32 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Mon, 7 Aug 2017 16:04:32 -0400
From: "Ahmed Bashandy (bashandy)" <bashandy@cisco.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, 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
Thread-Topic: I-D Action: draft-bashandy-rtgwg-segment-routing-ti-lfa-01.txt
Thread-Index: AQHS/s0UOH2rEJV8wEWTuDjp0BV0SaJXbAIAgBgMyACABQzEAIAEQIMAgAA6YoCAACRCAIAAjPmA//+9EvA=
Date: Mon, 07 Aug 2017 20:04:32 +0000
Message-ID: <849700d9f030475a852096bfa51766fb@XCH-RTP-020.cisco.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> <b991e0eb-97f0-cd5f-96c8-7ce77d880614@g3ysx.org.uk> <5988B030.8080001@cisco.com> <9ecd1975-e34e-6d6a-6d6f-0e62dc4c48b5@gmail.com>
In-Reply-To: <9ecd1975-e34e-6d6a-6d6f-0e62dc4c48b5@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.160.78]
Content-Type: multipart/alternative; boundary="_000_849700d9f030475a852096bfa51766fbXCHRTP020ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/kxDmIIzvG8jA8a42-thrGKJgNog>
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 20:04:38 -0000

Stewart

I already replied to Sikhi explaining the concept of the SRLG used in this draft and the intent to make it even clearer.

IMO the scope of the draft is very clear from the draft itself as well as the numerous responses during the previous IETF and the mailing list.

The issue below is *out of scope* of the draft and hence I have no plans on addressing it.

I hope you don't insist on pushing out-of-scope topics down the throat of this draft :)

Ahmed

From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
Sent: Monday, August 07, 2017 12:48 PM
To: Ahmed Bashandy (bashandy); Stewart Bryant; Sikhivahan Gundu; rtgwg@ietf.org
Cc: rtgwg-chairs@ietf.org; pfrpfr@gmail.com
Subject: Re: I-D Action: draft-bashandy-rtgwg-segment-routing-ti-lfa-01.txt


Your answer did not address the issue below, which is one of a class of issues related to SRLG.

- Stewart

On 07/08/2017 19:23, Ahmed Bashandy (bashandy) wrote:
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









_______________________________________________

rtgwg mailing list

rtgwg@ietf.org<mailto:rtgwg@ietf.org>

https://www.ietf.org/mailman/listinfo/rtgwg