Re: [magma] Question about fast-leave implementation

Hitoshi Asaeda <asaeda@sfc.wide.ad.jp> Sat, 30 October 2010 05:43 UTC

Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: magma@core3.amsl.com
Delivered-To: magma@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8413C3A682E for <magma@core3.amsl.com>; Fri, 29 Oct 2010 22:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.848
X-Spam-Level:
X-Spam-Status: No, score=-96.848 tagged_above=-999 required=5 tests=[AWL=0.740, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, SARE_RECV_IP_222000=1.508, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYTBQNNC9KVp for <magma@core3.amsl.com>; Fri, 29 Oct 2010 22:42:56 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id 80C613A6844 for <magma@ietf.org>; Fri, 29 Oct 2010 22:41:26 -0700 (PDT)
Received: from localhost (KHP222006121211.ppp-bb.dion.ne.jp [222.6.121.211]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 26C692780B5; Sat, 30 Oct 2010 14:41:45 +0900 (JST)
Date: Sat, 30 Oct 2010 14:41:44 +0900 (JST)
Message-Id: <20101030.144144.39171384.asaeda@sfc.wide.ad.jp>
To: kunal.shah@ericsson.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <4FD1E7CD248BF84F86BD4814EDDDBCC150E72D5C2E@EUSAACMS0703.eamcs.ericsson.se>
References: <4FD1E7CD248BF84F86BD4814EDDDBCC150E72D5C2E@EUSAACMS0703.eamcs.ericsson.se>
X-Mailer: Mew version 6.2.51 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: magma@ietf.org
Subject: Re: [magma] Question about fast-leave implementation
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/magma>
List-Post: <mailto:magma@ietf.org>
List-Help: <mailto:magma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Oct 2010 05:44:30 -0000

Hi Kunal,

> Is there any reason to send out a query in fast-leave is enabled on
> the interface?? Enabling fast-leave allows deleting the cache
> immediately on receiving a leave. If the cache is deleted
> immediately, hosts on the interface will see traffic loss, which
> makes me think that fast-leave is enabled when the interface is
> gauranteed to receive a leave when the last host goes away or there
> is only one host on the interface. So does it make any sense in
> sending out a query on receiving a leave if fast-leave is enabled??

Good question.

In fact, I've been working the function that supports fast leave.
You may want to read the following draft;
http://tools.ietf.org/html/draft-asaeda-mboned-explicit-tracking-01

This draft is currently submitted to MBONED.

Any commnet is welcome.

Regards,
--
Hitoshi Asaeda