Re: [trill] TRILL Resilient Distribution Trees, who have read it?

Ayan Banerjee <ayabaner@gmail.com> Tue, 04 December 2012 18:23 UTC

Return-Path: <ayabaner@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 6053021F8CA1 for <trill@ietfa.amsl.com>; Tue, 4 Dec 2012 10:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 kJO9So6EXX7U for <trill@ietfa.amsl.com>; Tue, 4 Dec 2012 10:23:39 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id 75BF821F8BFD for <trill@ietf.org>; Tue, 4 Dec 2012 10:23:38 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hj13so805928wib.13 for <trill@ietf.org>; Tue, 04 Dec 2012 10:23:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pwRSYiQJ9EQ7DAFkfSNs3dolEfNiMah0SUxwh6zpy70=; b=OtwbOZ/AYXwNvjRf+fvSM4glEQcpqOiYIuofdC/Q/tneWezhiSF03fHwwC6MeOUr7B qXuNpI2AinwQLBfqn3Z4u0z/SP+h/6mXV5y3CZeWgqsGzO/Tc0OIt5DDsVzcfSuK+9BM IQNgQV4ReBoOQ6LRwhNDcEClshoYtHrwyligV6NjEg6IsZfn9eoYHi5p2yzAQ3sH0sjH tlXKeuHBBmHDAQZSh6RlXbbEzKp/STPi+jgFODFEj39td9jWkS8nZh6ffYxQ3EZ9GyPa uEh5i6H+p4bldpkfatKsjg0MJnpozLY+xFynxuHjhi56yUVTmCrHEQaOo6NedOM7IUIW PkcA==
MIME-Version: 1.0
Received: by 10.216.80.130 with SMTP id k2mr5332708wee.118.1354645413848; Tue, 04 Dec 2012 10:23:33 -0800 (PST)
Received: by 10.194.14.200 with HTTP; Tue, 4 Dec 2012 10:23:33 -0800 (PST)
In-Reply-To: <CA+-tSzzp08kcd31qZtz0Kf73tnktuTv-spxfdfheuztED51wcQ@mail.gmail.com>
References: <4552F0907735844E9204A62BBDD325E732132977@SZXEML507-MBS.china.huawei.com> <CA+-tSzzp08kcd31qZtz0Kf73tnktuTv-spxfdfheuztED51wcQ@mail.gmail.com>
Date: Tue, 04 Dec 2012 10:23:33 -0800
Message-ID: <CAHD03N_vTBCtbrEPY5+POvPN81_OCPX156F_0FCWtGU019HS8w@mail.gmail.com>
From: Ayan Banerjee <ayabaner@gmail.com>
To: "trill@ietf.org" <trill@ietf.org>
Content-Type: multipart/alternative; boundary="0016e6deea62b0658d04d00af60c"
Subject: Re: [trill] TRILL Resilient Distribution Trees, who have read it?
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: Tue, 04 Dec 2012 18:23:41 -0000

I would like to voice support for this work (as a co-author).

It is important to have some determinism to the manner in which
multi-destination trees are computed for operational purposes and
this draft is a step in that direction.

Thanks,
Ayan



On Mon, Dec 3, 2012 at 7:05 PM, Anoop Ghanwani <anoop@alumni.duke.edu>wrote:

> Just wanted to say that I support this work (as a co-author).
>
> I think this will make provisioning simpler and would allow an
> operator to create multiple trees that are maximally disjoint.
> In the case of fat trees, this is fairly trivial to do in a manual
> way (just use different "core" RBridges as roots), but in any
> other topology, this will help avoid overlapping links.
>
> Anoop
>
> On Fri, Nov 30, 2012 at 12:18 AM, Mingui Zhang <zhangmingui@huawei.com>wrote:
>
>> Hi all,
>>
>> When customers deploy TRILL in their networks, they concern much about
>> minimizing the disruption of their multicast service. So failure protection
>> mechanisms are desired. Protection solutions for IP Multicast service have
>> been developed and standardized. However, unlike unicast, multicast
>> protection solutions cannot be reused by TRILL because TRILL-multicast is
>> customized for TRILL. Therefore we composed the draft to provide the
>> multicast protection suitable for TRILL.
>>
>> As we know, TRILL can intrinsically calculate multiple distribution
>> trees. In the draft, this ability is leveraged to achieve multicast
>> protection in a way that the pay is insignificant.
>>
>> We believe this work deserves our exploration. So, we would like to know,
>> who have read this draft?
>>
>> The draft
>> TRILL Resilient Distribution Trees
>> http://datatracker.ietf.org/doc/draft-zhang-trill-resilient-trees/
>>
>> Thanks,
>> Mingui
>> _______________________________________________
>> 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
>
>