Re: WGLC for draft-rtgwg-mrt-frr-architecture
Stewart Bryant <stewart.bryant@gmail.com> Fri, 04 December 2015 15:54 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 3B6A41A88C0 for <rtgwg@ietfa.amsl.com>; Fri, 4 Dec 2015 07:54:46 -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 mINvLvp1gvhm for <rtgwg@ietfa.amsl.com>; Fri, 4 Dec 2015 07:54:45 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 094A21A88BD for <rtgwg@ietf.org>; Fri, 4 Dec 2015 07:54:41 -0800 (PST)
Received: by wmww144 with SMTP id w144so67331352wmw.1; Fri, 04 Dec 2015 07:54:39 -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=kuD5vi8qGHSxyc9rLxfuyIIzK422IwC6sEI6OVKsX0g=; b=qdq0eHHUQcwuOsLW1m9tZY9eiB+JMlyhoseW2JdUSy6ewLQ4MgSC20/8ruqh9ujNr9 PGzF8sDzJjaGAGPoOxgBtPIjwOTQbel9V4xtsFOIoWRjRueqCx/kf1R/ZSJ0vvOxQiB+ Nrxrkye0WceXtvlL56rcl3QInNDw00qen6PktwazVt+tsCI6Ka3OQHQRnjtamYzWPOyo PhAYrQ4KQ9fCMXhLyhqV1ixk6qApYvIiQC3mKd2BX/11S5D6tmOxQ5N8s5HTmfVCR/Au ZuI5fflZpzh53tECCo8G8wf1uCuH7V6HrDf8oB2yGQqOGPYx27NwxVi3R9PMsN6MwDLo PpuQ==
X-Received: by 10.28.187.4 with SMTP id l4mr5914672wmf.33.1449244479633; Fri, 04 Dec 2015 07:54:39 -0800 (PST)
Received: from [192.168.2.132] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id bg10sm12636568wjb.46.2015.12.04.07.54.38 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Dec 2015 07:54:38 -0800 (PST)
Subject: Re: WGLC for draft-rtgwg-mrt-frr-architecture
To: draft-rtgwg-mrt-frr-architecture@ietf.org, "rtgwg@ietf.org" <rtgwg@ietf.org>, Alvaro Retana <aretana@cisco.com>
References: <56608847.9040505@gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <5661B73D.2030802@gmail.com>
Date: Fri, 04 Dec 2015 15:54:37 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <56608847.9040505@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/gQCTpZpxoYTTIS5Xh1ZjgMMRzmc>
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: Fri, 04 Dec 2015 15:54:46 -0000
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
- WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Anil Kumar S N (VRP Network BL)
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Anil Kumar S N (VRP Network BL)
- RE: WGLC for draft-rtgwg-mrt-frr-architecture bruno.decraene
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Anil Kumar S N (VRP Network BL)
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Alvaro Retana (aretana)
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- RE: WGLC for draft-rtgwg-mrt-frr-architecture bruno.decraene
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Alvaro Retana (aretana)
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Rob Shakir
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Chris Bowers
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Chris Bowers
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Chris Bowers
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Rob Shakir
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Chris Bowers
- Re: WGLC for draft-rtgwg-mrt-frr-architecture Stewart Bryant
- RE: WGLC for draft-rtgwg-mrt-frr-architecture Chris Bowers