Re: Microloop protection as discussed in today's meeting

"Ahmed Bashandy (bashandy)" <bashandy@cisco.com> Wed, 20 July 2016 09: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 87D9D12B040 for <rtgwg@ietfa.amsl.com>; Wed, 20 Jul 2016 02:04:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level:
X-Spam-Status: No, score=-15.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, 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 TGXaHNc7RXXp for <rtgwg@ietfa.amsl.com>; Wed, 20 Jul 2016 02:04:22 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA4F112B037 for <rtgwg@ietf.org>; Wed, 20 Jul 2016 02:04:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2956; q=dns/txt; s=iport; t=1469005461; x=1470215061; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=C+Gs5hkqgvrAQUoJPjYNz6uz3N4giKYM/AYfmaIumZ8=; b=j6cWbGpR+BsEE5SJtC/nVEi8lHlR6tkh3+rcJ3nHyAqHR9b/bkkyzNAa xeaBZqt73He1x/7fM0SAhTZ4i6ZRvSRzT0LmBXcMbZdIY+JRumzl8lA8v KBQX9r+YBwhmir2CsFwjp4tymSIRM9JB4Jl5XtR50NYHjVZ11LUZbhxq6 o=;
X-IronPort-AV: E=Sophos;i="5.28,393,1464652800"; d="scan'208";a="299921463"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jul 2016 09:04:21 +0000
Received: from [10.61.239.84] ([10.61.239.84]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u6K94Kta025841; Wed, 20 Jul 2016 09:04:20 GMT
Message-ID: <578F3E93.3020403@cisco.com>
Date: Wed, 20 Jul 2016 02:04:19 -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.bryant@gmail.com>, rtgwg@ietf.org
Subject: Re: Microloop protection as discussed in today's meeting
References: <578E3DBD.9030702@gmail.com>
In-Reply-To: <578E3DBD.9030702@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/-DJ-nnSUabSkA6VY_2qDagP3gPQ>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 20 Jul 2016 09:04:24 -0000

Stewart,

You are stating the most obvious:)
For a feature to work, e.g. encapsulating into an RSVP tunnel, the entry 
point of the packet must be able to support that feature. That is not a 
problem. That how the entire world works:)

SR-based ti-uloop avoidance is no different. So if a packet arrives at 
node "D" for example, then node "D" must be able to steer the packet 
such that it guarantees loop-freeness.
Once "D" source-routes the packet into the loop-free path towards the 
destination "Z" , downstream routers from "D" towards "Z" need NOT have 
the ability to do uloop avoidance or even know that packets was 
source-routed by node "D"

As for the need for using "strict" vs "loose" source routing, that is 
topology dependent. The same applies for ti-lfa, rLFA, or even directly 
connected LFA.

One last thing, if you think that source routing can reduced to a 
"tunnel" we might as well shutdown SPRING WG:)

Ahmed




On 7/19/2016 7:48 AM, Stewart Bryant wrote:
> Appologies if this is a duplicate.
>
> The RFC that had all of the generic methods that were known at the 
> time of publication is RFC5715.
>
> The two phase methods were in section 6.2 (near-side) and section 6.3 
> (far-side). The first describing tunnelling the traffic towards the 
> repair (and continue to use the repair), the second describing 
> tunnelling traffic towards the destination. For the purposes of this 
> discussion source routing of all flavours can be considered a type of 
> tunnel.
>
> If this approach is a new  genetric  two phase method, it would be 
> useful to articulate it in general terms.
>
> The type of topology that I was trying to explain in the meeting is as 
> follows
>
> A-B-C-D-E-F-H-I-J.....W
> |                     |
> |                     |
> +------X-Y-Z----------+
>
> All costs are 1 and Y has failed.
>
> Traffic to Z can enter enywhere, and is protected by X.
>
> When the network starts to converge ALL the routers A..J will need to 
> update their fib to forward towards Z via W rather than towards X via A.
>
> If they do this in a random order as would be the case without LF 
> convergence then you may precipitate microlooping.
>
> What you need to do is to force the packets toward either X or Z using 
> a tunnel, or a source routed path, and as far as I can see you need to 
> do that at every point of potential entry into the network, in the 
> above case A..J, else you risk a microloop.
>
> Now I suppose that if ALL packets were source routed, then you could 
> consider that the network was constantly in the first phase, but I 
> think that you would need to use strict source routing, rather than 
> loose source routing else it reduces the the problem I describe above.
>
>
> - Stewart
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg