Re: [multimob] Summary from multimob session @ IETF71
Hitoshi Asaeda <asaeda@sfc.wide.ad.jp> Mon, 14 April 2008 11:05 UTC
Return-Path: <multimob-bounces@ietf.org>
X-Original-To: multimob-archive@optimus.ietf.org
Delivered-To: ietfarch-multimob-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC3ED3A6E75; Mon, 14 Apr 2008 04:05:26 -0700 (PDT)
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B80893A6E65 for <multimob@core3.amsl.com>; Mon, 14 Apr 2008 04:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 D6AVlSq7Oxu2 for <multimob@core3.amsl.com>; Mon, 14 Apr 2008 04:05:23 -0700 (PDT)
Received: from pione.sfc.wide.ad.jp (unknown [IPv6:2001:200:0:8801:203:47ff:fedf:73cc]) by core3.amsl.com (Postfix) with ESMTP id 646453A6E6F for <multimob@ietf.org>; Mon, 14 Apr 2008 04:05:18 -0700 (PDT)
Received: from localhost (wifi-139-171.sfc.wide.ad.jp [203.178.139.171]) (authenticated bits=0) by pione.sfc.wide.ad.jp (8.13.1/8.13.1) with ESMTP id m3EAnT9w002491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Apr 2008 19:49:56 +0900
Date: Mon, 14 Apr 2008 20:04:04 +0900
Message-Id: <20080414.200404.213470728.asaeda@sfc.wide.ad.jp>
To: schmidt@informatik.haw-hamburg.de
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <47EB81BB.4040801@informatik.haw-hamburg.de>
References: <623942.11346.qm@web84309.mail.re1.yahoo.com> <20080327.122746.11606627.asaeda@sfc.wide.ad.jp> <47EB81BB.4040801@informatik.haw-hamburg.de>
X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Cc: multimob@ietf.org
Subject: Re: [multimob] Summary from multimob session @ IETF71
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: multimob-bounces@ietf.org
Errors-To: multimob-bounces@ietf.org
Hi Thomas, Sorry for the late reply. > This is mechanism is a (subscription-) proxy function used at relays > already today. A multicast relay maintains a group subscription without > forwarding traffic, e.g., down a wireless link to assist a fast > forwarding in case a listener for that group arrives on the link / in > the domain. > > This mechanism is described in the section "5.2.4 MLD Extensions" of the > problem statement > http://tools.ietf.org/html/draft-irtf-mobopts-mmcastv6-ps > > and a protocol realization in the form of an MLD extension is given in > section "4.5 Router attendance control in MLD" of the M-HMIPv6 draft > > http://tools.ietf.org/html/draft-schmidt-waehlisch-mhmipv6 I read this draft. It assumes the use of HMIP6 but this MLD extension would be in general useful with other mobile protocols. I could support this idea. I'm interested in the discussion regarding how this extension would need more improvement as the spec (e.g. how long proxy or mrouter (i.e. MAPs or HA) can keep or maintain "hold" state reported by MN). On the other hand, I'd like to hear other opinions. One may think that it is not necessary to notify MLD hold state to MAPs (or HA in MIP6) as the fast handover would be much faster than the time of membership expiration maintained by MLD. I don't know if this thought is fairly reasonable or not. If we agree to include this extension, I'm happy to discuss the future direction and how we can cooperate in both of our future drafts. Thank you for your input. Regards, -- Hitoshi Asaeda _______________________________________________ multimob mailing list multimob@ietf.org https://www.ietf.org/mailman/listinfo/multimob
- [multimob] Summary from multimob session @ IETF71 Suresh Krishnan
- Re: [multimob] Summary from multimob session @ IE… Thomas C. Schmidt
- Re: [multimob] Summary from multimob session @ IE… Behcet Sarikaya
- Re: [multimob] Summary from multimob session @ IE… Hitoshi Asaeda
- Re: [multimob] Summary from multimob session @ IE… Thomas C. Schmidt
- [multimob] Summary from multimob session @ IETF71 Behcet Sarikaya
- Re: [multimob] Summary from multimob session @ IE… Von-Hugo, Dirk
- Re: [multimob] Summary from multimob session @ IE… Hitoshi Asaeda