Re: WGLC for draft-rtgwg-mrt-frr-architecture

Stewart Bryant <stewart.bryant@gmail.com> Wed, 23 December 2015 12:33 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2041ACEF1 for <rtgwg@ietfa.amsl.com>; Wed, 23 Dec 2015 04:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 DqhzZED1H7bX for <rtgwg@ietfa.amsl.com>; Wed, 23 Dec 2015 04:33:18 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 B6CCA1ACEED for <rtgwg@ietf.org>; Wed, 23 Dec 2015 04:33:18 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id p187so146864927wmp.0 for <rtgwg@ietf.org>; Wed, 23 Dec 2015 04:33:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=ytZZM5Y0R0h5Pa5q9faB4F6UgedTbMbbpK3tcUAIur0=; b=J4qSA9NZXzkIyG3s1sx/t2ZRa5ng9s8AShhs6j6a1lknsR+/giAmg3nZFLekyGXumt 0R5EUNfBN42RHhBtSnfD6stIxmaxqWsBXOLyCqHJhWZR07H0XWG7T0wClD/2oj/4eDD3 ehhPY9m5P18botWabK21wkbiEZbD14LB/JfYB2xu3v6VVlsXpzyLxn1XEb+DH+oHtniH Lcdx4Nt2fb2iREyctpdI+nBqXo/tb//QG0bFYdV8zFO1UzfVFIJDjktrZw42ZWs7zGP9 dUSZfWSRBj0e/oiqlC+xUMDjBG3SetJZTOl7kSydPg2ntZy5ISiZXYSHyMWzOEmnTEkn GPVQ==
X-Received: by 10.28.172.129 with SMTP id v123mr33140097wme.47.1450873997116; Wed, 23 Dec 2015 04:33:17 -0800 (PST)
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 i63sm3314687wmf.24.2015.12.23.04.33.15 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Dec 2015 04:33:16 -0800 (PST)
Subject: Re: WGLC for draft-rtgwg-mrt-frr-architecture
To: Chris Bowers <cbowers@juniper.net>, "draft-rtgwg-mrt-frr-architecture@tools.ietf.org" <draft-rtgwg-mrt-frr-architecture@tools.ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Alvaro Retana <aretana@cisco.com>
References: <56608847.9040505@gmail.com> <5661B73D.2030802@gmail.com> <CO2PR05MB619C358B509AE4030EB40EFA9E40@CO2PR05MB619.namprd05.prod.outlook.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <567A948B.9080706@gmail.com>
Date: Wed, 23 Dec 2015 12:33:15 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CO2PR05MB619C358B509AE4030EB40EFA9E40@CO2PR05MB619.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/V_qXrP7qQVMACndcK-wtexLrNO0>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Dec 2015 12:33:20 -0000


On 21/12/2015 14:47, Chris Bowers wrote:
> Steward,
>
> I don't agree with the initial statement that the technique forms two trees rooted at a single node.  The designation of the GADAG root plays an important role in computing the red and blue MRT trees.  However,  red and blue MRT trees are computed using forward SPFs rooted at each source, which follow the directed links on the GADAG and do not propagate past the GADAG root.  The net result of these computations can be viewed as producing red and blue MRT trees rooted at each destination.  In any case, these trees are not rooted at the GADAG root.
Ah, OK.

However the GADAG root can move, does that not have an impact on the 
repair topology? It sounds from the above as if it might since you say 
you say that the root sets a propagation limit.

- Stewart
>
> Anil pointed out that the pseudo-code in draft-ietf-rtgwg-mrt-frr-algorithm didn't always make a clear distinction between the root of the forward SPF computation and the GADAG root, so we tried to clarify that in this set of changes.
>
> https://github.com/cbowers/draft-ietf-rtgwg-mrt-frr-algorithm/commit/ada619050ec9d773b7919a1c622f068d5a5a5e88
>
> Are there places in the architecture document where similar clarifications should be made?
>
> Chris
>
> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Friday, December 04, 2015 9:55 AM
> To: draft-rtgwg-mrt-frr-architecture@ietf.org; rtgwg@ietf.org; Alvaro Retana <aretana@cisco.com>
> Subject: Re: WGLC for draft-rtgwg-mrt-frr-architecture
>
> Another couple of comments on this draft.
>
> The technique you use of selecting a single node and forming two trees rooted at that node should really be noted up front in the summary.
>
> A consequence of this is that when you add a node or when the root node fails the trees and hence the FRR paths may change. To some extent this happens in LFA and RLFA, although the changes will tend to be confined to a local region, whereas with MTR I think that the  node may move to a completely different region. If that is the case then that has an impact on the FRR traffic management. By way of comparison, NV is the least impacted by this approach and the SR approach is impacted as much as LFA, but has the option of correcting this will a little effort.
>
> I think that there really needs to be some text on the matter in the architecture spec.
>
> - Stewart
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg