Re: [trill] Explaining three options for upgrading to FGL (fine-grained-labeling)

Sam Aldrin <aldrin.ietf@gmail.com> Wed, 30 January 2013 19:55 UTC

Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D3C821F88B6 for <trill@ietfa.amsl.com>; Wed, 30 Jan 2013 11:55:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5u+vKxXL+D1M for <trill@ietfa.amsl.com>; Wed, 30 Jan 2013 11:55:36 -0800 (PST)
Received: from mail-pb0-f51.google.com (mail-pb0-f51.google.com [209.85.160.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3524821F88A9 for <trill@ietf.org>; Wed, 30 Jan 2013 11:55:36 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id un15so1153447pbc.24 for <trill@ietf.org>; Wed, 30 Jan 2013 11:55:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=g/3F7QEGvrPqgPLpBdvfFddHZ8VBdnOcW08OWh6yuHU=; b=ZQ2AvZnHe4CEmfzRhu29UwC+Nc1pSZgv+qNk4LDWYLXuqSpaL4CHTX4uuzepsGP+Aj kmF3winsL+IKdnT97aJxd6dITnBliO0A7FowSTS/FDJMC7afix3kZmHB0idTow+XBqwk oOKa9VUcupvkgSzpl835NVB6iy2BzQPclTF6Oqu1vzBKJ6bkwQKNb+wgOE1AOCN7KALF eOttLpLRMwJkLiqscAh69KdALsaUEz4UAk/u3d2FqjI3w4mjVmGBqpAtsV0nN57KKOM1 bvLLKVwPK2ndx+gFqsAaPy0P/MesSawWRjyuYbcYl5z+xn5tKjfkYQ4qwe+cI9YM5+3J Geag==
X-Received: by 10.68.219.36 with SMTP id pl4mr15493703pbc.124.1359575735272; Wed, 30 Jan 2013 11:55:35 -0800 (PST)
Received: from [192.168.255.224] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by mx.google.com with ESMTPS id rk6sm2466477pbc.20.2013.01.30.11.55.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Jan 2013 11:55:34 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Sam Aldrin <aldrin.ietf@gmail.com>
In-Reply-To: <CAF4+nEFLrJL=CgX9e6on-cgz89ugmu93P6u5kmODhUia3H7RLg@mail.gmail.com>
Date: Wed, 30 Jan 2013 11:55:35 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F5A81AE-4B3C-45FD-B431-9BA0011EB085@gmail.com>
References: <CAFOuuo67iBR2JkDtwPFCkrKHs3Fp4U_L1jkmNz5sfht6y05YMw@mail.gmail.com> <CA+-tSzx0E3J4i5Dvfbj4egruCeGi7z1se1Jn5RXtx3RedQLPdg@mail.gmail.com> <CAHD03N89RNX4=XxRZpD+Y2PCktYf-FtVjyYJ5oFS3dui3SsXaA@mail.gmail.com> <CAF4+nEG7YKGzGmObAMaOxackivjJsALymqHX=6PKBd5qU-Z+zQ@mail.gmail.com> <CA+-tSzz0=oh6iB1e-ESyeOx2sCvBFXeVpzuNbKmUVhRNLScDgQ@mail.gmail.com> <CAF4+nEFLrJL=CgX9e6on-cgz89ugmu93P6u5kmODhUia3H7RLg@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: Anoop Ghanwani <anoop@alumni.duke.edu>, Radia Perlman <radiaperlman@gmail.com>, Ayan Banerjee <ayabaner@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Explaining three options for upgrading to FGL (fine-grained-labeling)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 19:55:37 -0000

[still catching up on email, so the delay]

When everyone says, upgrade RBridges, what is the upgrade model they have in mind?
How can one do software upgrade when hardware/silicon cannot support?
Secondly, any actual users, not vendors, commented on how they plan to deploy FGL?

-sam

On Jan 29, 2013, at 4:37 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi Anoop,
> 
> On Tue, Jan 29, 2013 at 7:03 PM, Anoop Ghanwani <anoop@alumni.duke.edu> wrote:
>> On Tue, Jan 29, 2013 at 12:49 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
>> 
>>> The general assumption is that you are migrating from VL to FGL. First
>>> you migrate to FGL-safe. Then you unleash the FGL traffic, by
>>> configuring FGL ports, which isolates any remaining (FGL-unsafe) VL
>>> switches while still being able to handle VL traffic between VL ports
>>> on FGL-safe switches.
>> 
>> Based on what is written so far, it looks like as long as there is even
>> one VL RBridge in it's database, an RBridge would not be able to start
>> sourcing FGL traffic.  It may start doing so only when all RBridges in
> 
> Well, it can start sourcing FGL traffic but their are consequences as
> you note below.
> 
>> its database are FGL-safe.  If we ever get into a condition where
>> an RBridge has started advertising FGL information, at that point,
>> does any other RBridge in the campus simply isolate any VL RBridge
>> (with the assumption that there was some kind of race condition?
> 
> Yes. (This could just be due to some misconfiguration.)
> 
>> The case I'm concerned about is we have 2 FGL RBridges, RB1 and RB2.
>> RB1 is connected to a campus of n RBs that are still VL only.  The VL link
>> Breaks, and RB1 starts advertising FGL information to RB2, but then
>> the link to the VL campus comes back up.  Does this mean RB1 and RB2
>> remain isolated from the campus (and operate as they own mini-campus)
>> until all the other RBridges are converted over to FGL-safe?
> 
> Yes. But I don't think this as much of a problem given that I believe
> existing TRILL switches can be software upgraded to be FGL-safe. I
> view the configuration of FGL ports on RB1/RB2 and the consequent
> routing of actual FGL traffic to be an active network management
> decision, not something that might just happen because there appear to
> be no more VL TRILL switches in the topology.
> 
> Thanks,
> Donald
> =============================
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 155 Beaver Street, Milford, MA 01757 USA
> d3e3e3@gmail.com
> 
>> Anoop
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill