Re: [trill] TRILL deployment

sujay gupta <sujay.ietf@gmail.com> Sat, 04 June 2016 16:12 UTC

Return-Path: <sujay.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 36EC012D1A3 for <trill@ietfa.amsl.com>; Sat, 4 Jun 2016 09:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 xRUPm-qpvDjz for <trill@ietfa.amsl.com>; Sat, 4 Jun 2016 09:12:14 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (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 7392C12D135 for <trill@ietf.org>; Sat, 4 Jun 2016 09:12:14 -0700 (PDT)
Received: by mail-pa0-x22c.google.com with SMTP id xk1so22812126pac.2 for <trill@ietf.org>; Sat, 04 Jun 2016 09:12:14 -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=Ilu8ENX4WCz9jeit7uOotTM/0EiZkG8ef5nagjJaIPs=; b=bytUA5g1cBzc7VIqjiLyq3LtIC8PnngxRllKUE48C4UYQg0+YkfH+5Nsb5BNP9FbPT twvWJXxAML3OQUF5UDsDgxKnfLT43m13WDpfd5WptPmVtZ5VBylx7nQ857mHACvGe0Uq QjsqNlStIRsjdprZya4DbdwRNbAa6EN3En7joo6TtuNtQJ596IXDJCvJo56ucoRk3ybR FygsqP4XUeCDNEhtNhRG7w4SFNZX0cPawPBw6UBU5DFxkPDkvaM9RrEbzrTsmT/Twbqt oSZNdXUTpLROpfbS7jNvSHAW3vtVQCAdusvdiOZKWwljQVAzAMMTVuMe27POeKOcPtn9 eKOw==
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=Ilu8ENX4WCz9jeit7uOotTM/0EiZkG8ef5nagjJaIPs=; b=UeQ0dN14VgSKd7EJKS7xFWrO2IvI2acqcbb4GQ38/dVP12Z/JolbbJ2ae4vuU/f1gM oyb0KiaRo1wQYdOirdpgarINhHLwCA+If3TOGWcDKK/6XDV4R6ZdGQbIPX4y7tlBmzL+ Q0ndIJHq6t2GsViuDkxoxnBfNYzH92Sw54tnMlQPs7JxNpg4kjzUX2vP1Youq0I3B7Pj f0W3F/0O18u6r2yuWoX2Fg36hcnt09QKt8ICbGuqyo4mtDTPg1WoeWQmCnSlNvyFfNX8 VVQujerxqpJx62+70+MB0mJKrlfPTZEF8Q1FyZPhlOi5/HqCAIR1elv7wDwUiv0lf0I1 4nWA==
X-Gm-Message-State: ALyK8tIojMT0xm7ADtcwGnio4FbLDpRrIj0nVtQx1XhzcXYjsV/bpTXNe1ed20urPd5n3O+fW3DM0xL3nJghGw==
X-Received: by 10.66.1.99 with SMTP id 3mr12279785pal.26.1465056733910; Sat, 04 Jun 2016 09:12:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.224.4 with HTTP; Sat, 4 Jun 2016 09:12:13 -0700 (PDT)
In-Reply-To: <6DA1B13B-5F4D-4E62-9EF7-F59970AAC7C1@gmail.com>
References: <CAPN_1CXvk8EYpgtazuVwJK2RxXQLUZXxowd7rC7BxUw0Xkt_Rg@mail.gmail.com> <574580D0-D6B3-409C-9697-256C69E8B24C@gmail.com> <CAF4+nEES0b5KyD-YpZ1rGCh3sGWj8drxMF9aC9JtYzzLhCOreA@mail.gmail.com> <6DA1B13B-5F4D-4E62-9EF7-F59970AAC7C1@gmail.com>
From: sujay gupta <sujay.ietf@gmail.com>
Date: Sat, 4 Jun 2016 09:12:13 -0700
Message-ID: <CAMF3MVv3tu42YzLusRPWdZcUy6vmw4XnsjdpR11bxHFeKAmTOg@mail.gmail.com>
To: Jon Hudson <jon.hudson@gmail.com>
Content-Type: multipart/alternative; boundary=20cf305f95d0335b0b0534761a1f
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/XNMK31WKouZqqbfaVLTTSkeaO-k>
Cc: Donald Eastlake <d3e3e3@gmail.com>, 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: Sat, 04 Jun 2016 16:12:16 -0000

Chipset support for OAM offload is another impending problem.
That said we have seen successful deployments of TRILL in large networks
Regards,
-Sujay

On Fri, May 27, 2016 at 4:25 AM, Jon Hudson <jon.hudson@gmail.com> wrote:

>
> 110% agree
>
> It's the vendor implemented tools that are primarily at issue.
>
> Jon
>
> > On May 26, 2016, at 6:12 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> >
> >> 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
> >>
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
>