IETF Logo Mail Archive

[trill] TRILL deployment

devon ietf <devon.ietf@gmail.com> Thu, 26 May 2016 07:01 UTC

Return-Path: <devon.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 DA03712D883 for <trill@ietfa.amsl.com>; Thu, 26 May 2016 00:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=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 uYpgzoJUuAUU for <trill@ietfa.amsl.com>; Thu, 26 May 2016 00:01:25 -0700 (PDT)
Received: from mail-vk0-x244.google.com (mail-vk0-x244.google.com [IPv6:2607:f8b0:400c:c05::244]) (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 D63D012D810 for <trill@ietf.org>; Thu, 26 May 2016 00:01:24 -0700 (PDT)
Received: by mail-vk0-x244.google.com with SMTP id e126so1179891vkb.2 for <trill@ietf.org>; Thu, 26 May 2016 00:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=xtFsXVK7pYqfn+xC/quFd+WL0w/GctutwJqeRdmUZlI=; b=qphbnvYYmj2tgSp7ymscIosLCNkrV3AR4QbJVGHUPt3v7xYX0o1pPDOZQqeDyFCFBJ JAzzoyadip5i2X9Y68m1o3/L8m9YBqLpWRVosLPleayEp5GZn6a4xQlgJoFuPwjCiD4n /6O5adVpBk0IMCc273GS2vweM5Qh3+M5Dan6c1PWFbd0UgMP+EBECtUKoyvJke6V76z1 UeHy9DkhOPjP6Rwiy4PSUT0mNaRMTX+j1W3JjvLSzvqlgh2ecgnCQWCcHZIxN1t77crX ReMpWvTdFmKotwcLABFvDrP+J1gzGOm1TeVAAP/ungsxZofv19CEFRPGCOa+lflIffxW vwdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=xtFsXVK7pYqfn+xC/quFd+WL0w/GctutwJqeRdmUZlI=; b=Q4WqVpSyMwZg9z68214qWg1fU+FswCpcXLC74nU5M2eJYkTNuFYtKf59v562yTlRAb OgoZ92IHltxpHNcz7Caz50Vkk1lbyJErMaP2ZGxF8hPjM529Ooc8uRi850bPJrDsn/Jq JTHFriIWchhxXB1VRo1XaDnjY+X1KbuDvSwyHEkRF9+5hKbj9kJ+EIEVjJdXHqyPD/kl fOOdBqFwLRtby2RPWh9IdRMYaLVTKK8JuAkQ3Hp+hZx3cuSL73AmFlDj+TLs1C6/HdnC eew1Z9uyZP7A6QX4Xruf9BwNBEkqHtBgsLXg278QQOBNr438Njb0/LPqkwnl7h2ZtQCj vEjg==
X-Gm-Message-State: ALyK8tJcrBWe1rBSaI4y+PZiYF25QIh1kyQQbHOXpIkT6VbFlrZ5FdPXPzmx1hJKSZ3tvNckqG/23IvBtvJN0w==
MIME-Version: 1.0
X-Received: by 10.31.3.223 with SMTP id f92mr4172856vki.20.1464246083901; Thu, 26 May 2016 00:01:23 -0700 (PDT)
Received: by 10.176.68.133 with HTTP; Thu, 26 May 2016 00:01:23 -0700 (PDT)
Date: Thu, 26 May 2016 12:31:23 +0530
Message-ID: <CAPN_1CXvk8EYpgtazuVwJK2RxXQLUZXxowd7rC7BxUw0Xkt_Rg@mail.gmail.com>
From: devon ietf <devon.ietf@gmail.com>
To: trill@ietf.org
Content-Type: multipart/alternative; boundary="001a11426ad2b1f9d80533b95bfe"
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/_6sw_hKlz39bDmOkcWJejibR8K0>
Subject: [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: Thu, 26 May 2016 07:01:26 -0000

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 ?

v2.23.0 | Report a Bug | By Email