Re: [trill] TRILL deployment

Donald Eastlake <d3e3e3@gmail.com> Fri, 27 May 2016 01:13 UTC

Return-Path: <d3e3e3@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 7F17E12D174 for <trill@ietfa.amsl.com>; Thu, 26 May 2016 18:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 iMz_Tb62qQ9B for <trill@ietfa.amsl.com>; Thu, 26 May 2016 18:13:07 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 E6A4212D111 for <trill@ietf.org>; Thu, 26 May 2016 18:13:06 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id j1so151547647oih.3 for <trill@ietf.org>; Thu, 26 May 2016 18:13:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=436K4iWZVK08SD3TP0F2Pu4NVdp2H6wRc1usPibcjX4=; b=ktZJ0+erPT+NyK3wmkC7Lo3Fw3t26KAWkXrpMzSsWr7a5qt1X9j2qoHU4g3i+UOFdb PgElQnHVxE5HkYFYs+8KH01PNDwhZIsgh3MoN3rH84YZ453xcQ+JDXn7HWK4vfi8TV4I VEFvUQPeB6uqEzTPQsh8eAT/8gfWUIlGzwTz/nS1CeqrIu8K29dJF8u/GltqX15diT7q jnjV7DpJ7c9Vzy/dJ7BK6Qx3H1dHjT8O09U9yA+eSCWJu3zl8PQq38eziicmkIWxvtR1 ELk8Zoa0HNEqVBpyyLmkDuLNMTLIurTv7+b3WCClUa5xH0TxdzjRAtZ7PY4yS1YwA3b6 3ofw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=436K4iWZVK08SD3TP0F2Pu4NVdp2H6wRc1usPibcjX4=; b=AWGEsVh5ZFZHb4i+FDz15uFpOMPcDrpccIgln5dPg+QMRnCj+Le62i/a52o/oLOIU0 Rtf2iah6zPHxqhdGefXeR/G6yBwKv0xVbTdSSWsznLMoCIj03JNIPWWlmWmAdbnHREmp 3R+OgzeZCZjg2PeoiQKirsCPOKsO1pQqLeK2C6r+VjRiB7INjpNrUru+XrIoyHFlTjGo 2E9gFnup0bIYVkXaucZcFjdvDN59gDPUy2PoFkKxvuvVMTs8UZbjv+sBsmY7v3hxZO8M IGGRp6fktPXd8bDOGtz03q3yuG7DXaTZqQ06ZI5ItVv2l9BDgpgHWxcQzrw6ltn0zm/c LiwQ==
X-Gm-Message-State: ALyK8tIya8vPpKx7y/jQL1dZybalT0C+LOxbLvlDgAtYDbVRKl0R4R0TUCzbgwdJe2GpllUchyjfBepr/WVQ3Q==
X-Received: by 10.202.85.73 with SMTP id j70mr7934743oib.114.1464311586241; Thu, 26 May 2016 18:13:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.22.249 with HTTP; Thu, 26 May 2016 18:12:51 -0700 (PDT)
In-Reply-To: <574580D0-D6B3-409C-9697-256C69E8B24C@gmail.com>
References: <CAPN_1CXvk8EYpgtazuVwJK2RxXQLUZXxowd7rC7BxUw0Xkt_Rg@mail.gmail.com> <574580D0-D6B3-409C-9697-256C69E8B24C@gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 26 May 2016 21:12:51 -0400
Message-ID: <CAF4+nEES0b5KyD-YpZ1rGCh3sGWj8drxMF9aC9JtYzzLhCOreA@mail.gmail.com>
To: Jon Hudson <jon.hudson@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/JRD_b9ktWqcmsFICMWuusbv5b2Q>
Cc: devon ietf <devon.ietf@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] TRILL deployment
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 27 May 2016 01:13:08 -0000

On Thu, May 26, 2016 at 3:50 AM, Jon Hudson <jon.hudson@gmail.com> wrote:
>
>
> Main issue that I know from customers is the lack of consistent tools to deep dive debug it.

It seems to me that this is a lack of user tools, not any inherent
problem with TRILL. TRILL has:
TRILL OAM (continuity fault management): RFCs 6905, 7174, 7455, 7784
MIBs: RFCs 6850, 7784
Supports BFD: RFC 7175
Has performance monitoring specified: RFC 7456

In addition, if a management station peers as an RBridge, it would
have direct access to the link state data base.

So I really don't see why there should be a problem with implementing
good TRILL debugging tools.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Jon
>
>
> On May 26, 2016, at 12:01 AM, devon ietf <devon.ietf@gmail.com> wrote:
>
> why is trill not so widely deployed. It's been around for several years and xSTP protocols
> are really bad, then too i don't see customers adopting TRILL as widely. what's wrong ?
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
>
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
>