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

Hi Sam,

As you can see from the words of the email, it is not a WG adoption polling. I am cautious about this.

According to the decision that the WG had made at the Atlanta meeting, authors were asked to make sure in the TRILL mailing-list whether there is enough number of guys who have read this draft. So, this email actually intends to help chairs to decide whether this draft deserves a call. I wish I have clarified your confusion.

Actually, this draft falls in the scope depicted by the recently updated charter. It is one of those "additional ways to extend and optimize TRILL for the properties of the networks on which it is deployed".

Thanks,
Mingui

________________________________________
From: trill-bounces@ietf.org [trill-bounces@ietf.org] on behalf of Sam Aldrin [aldrin.ietf@gmail.com]
Sent: Thursday, December 06, 2012 2:02
To: Mingui Zhang
Cc: trill@ietf.org
Subject: Re: [trill] TRILL Resilient Distribution Trees, who have read it?

I haven't paid too much attention into the details of the draft. Hence i will defer questions related to draft, for later time. But I do have few questions related to procedure.

1. I do not see this work item chartered for TRILL WG. Until it is done, it is not prudent for WG to focus on non-chartered items, atleast till the updated charter is in place.
2. Is this email a WG adoption call? Not being aware IETF procedures, can individuals call for WG adoption or is it done by chairs? If it is only by WG chairs, what is the purpose of this email.

Cheers
Sam

Sent from my iPad

On 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