Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc

Hitoshi Asaeda <asaeda@sfc.wide.ad.jp> Tue, 14 May 2013 05:40 UTC

Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B5A21F8528 for <pim@ietfa.amsl.com>; Mon, 13 May 2013 22:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQVI+trcZbJH for <pim@ietfa.amsl.com>; Mon, 13 May 2013 22:40:05 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 455CF21F851C for <pim@ietf.org>; Mon, 13 May 2013 22:40:03 -0700 (PDT)
Received: from localhost (unknown [133.69.32.86]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 2DFB627807D; Tue, 14 May 2013 14:40:01 +0900 (JST)
Date: Tue, 14 May 2013 14:40:03 +0900
Message-Id: <20130514.144003.46061186.asaeda@sfc.wide.ad.jp>
To: stig@venaas.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <518D2F0C.8030805@venaas.com>
References: <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp> <518D2F0C.8030805@venaas.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 05:40:06 -0000

>    Specific or Group-and-Source Specific Query messages transmitted from
>    a router, and reduce the number of Current-State Report messages
>    transmitted from member hosts.  If a router enables the explicit
>    tracking function with "specific query suppression", it suppresses
>    specific query transmission and transmits specific query messages
>    only when the router expects that the State-Change Report sender is
>    the sole member of the channel, based on its membership state
>    information (expressed in Section 3.1).
> 
> I believe it is fairly common to also suppress specific query when the
> last member is leaving, in order to do "fast-leave". Basically
> stopping
> forwarding without having to wait for responses to specific queries.
> 
> I vaguely remember we discussed this a couple of years ago...
> 
> I was thinking of this when I wrote "fast-leave" above. If you can
> expect the robustness to be tuned appropriately, this should be
> fairly safe. See what I wrote regarding tradeoff above.

Ok, so how about the following text added at the last part of the
section titled "Lowering the Risk of Wrong Membership State"?
(Do you have any suggestion of "may", "will", etc. in this para, too?)

  In order to reduce the possibility of the incorrect membership
  expectation and keep the up-to-date membership state information,
  operators may configure the LMQC/LLQC value to 2 (the default value
  of the [Robustness Variable] value) or bigger value for their
  routers enabling the explicit tracking function with specific query
  suppression. However, if operators believe that their link is fairly
  robust or that they can configure the [Robustness Variable] value
  appropriately so that the chances of unsolicited messages being lost
  are sufficiently low, they will enable specific query suppression
  and configure both or either of the LMQC/LLQC value and the
  [Robustness Variable] value to 1 for their routers.

Regards,
--
Hitoshi Asaeda