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

Sam Aldrin <aldrin.ietf@gmail.com> Wed, 05 December 2012 18:02 UTC

Return-Path: <aldrin.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 37C7121F8B9A for <trill@ietfa.amsl.com>; Wed, 5 Dec 2012 10:02:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.901
X-Spam-Level:
X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 z62c0EbPHh5M for <trill@ietfa.amsl.com>; Wed, 5 Dec 2012 10:02:48 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id DD42021F8716 for <trill@ietf.org>; Wed, 5 Dec 2012 10:02:47 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so3618152pad.31 for <trill@ietf.org>; Wed, 05 Dec 2012 10:02:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=nuCbDEqgfP18S97K61f7xKyC+5YvvAhrUvRVHnHEJmM=; b=BtW00pIR6EvWpRRd+VdYwENcZ1sYs6mCBOCD706Xikff/WIFq4ATJDyqRs5E3bJ6Bf 8zmGtB/LtWEe4NYXxO3tmbendKTGEgrEnovNc5zNL3jRx0wDG68ML4WzLCJBB7e234VK frbblqfRIyRXBl06x01q77GaPluBkjQeJp7TvI/f6ZL9faqWMuXsuFgf6SriHahxQSVV jgqdd8riUK39Pr7wJHYco558M6Bl7TimvVPgjP57ZonweqgFaCkGdeelmQwkhwizvlDD Nt2k0RH6RQKx8tmDK6s0zRywvK97/sfvs/Loi/IGpAKEEeLYMGux7m7jpT9phmTm8Qt3 uPug==
Received: by 10.66.88.102 with SMTP id bf6mr46841957pab.10.1354730567042; Wed, 05 Dec 2012 10:02:47 -0800 (PST)
Received: from [192.168.1.3] (c-98-248-237-85.hsd1.ca.comcast.net. [98.248.237.85]) by mx.google.com with ESMTPS id sy1sm3238329pbc.66.2012.12.05.10.02.44 (version=SSLv3 cipher=OTHER); Wed, 05 Dec 2012 10:02:45 -0800 (PST)
References: <4552F0907735844E9204A62BBDD325E732132977@SZXEML507-MBS.china.huawei.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <4552F0907735844E9204A62BBDD325E732132977@SZXEML507-MBS.china.huawei.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1260C20-4A5D-4F74-A283-0B9385D3B4B2@gmail.com>
X-Mailer: iPad Mail (10A523)
From: Sam Aldrin <aldrin.ietf@gmail.com>
Date: Wed, 05 Dec 2012 10:02:44 -0800
To: Mingui Zhang <zhangmingui@huawei.com>
Cc: "trill@ietf.org" <trill@ietf.org>
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: Wed, 05 Dec 2012 18:02:49 -0000

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