IETF Logo Mail Archive

[MEXT] Some questions on draft-sarikaya-mext-multicastdmm

Romain KUNTZ <rkuntz@us.toyota-itc.com> Fri, 22 July 2011 23:02 UTC

Return-Path: <rkuntz@us.toyota-itc.com>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3882821F874C for <mext@ietfa.amsl.com>; Fri, 22 Jul 2011 16:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.289
X-Spam-Level:
X-Spam-Status: No, score=-6.289 tagged_above=-999 required=5 tests=[AWL=-0.190, BAYES_00=-2.599, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_MED=-4]
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 CA9uOTKnfYt7 for <mext@ietfa.amsl.com>; Fri, 22 Jul 2011 16:02:14 -0700 (PDT)
Received: from na3sys009aog117.obsmtp.com (na3sys009aog117.obsmtp.com [74.125.149.242]) by ietfa.amsl.com (Postfix) with SMTP id 1876121F86DF for <mext@ietf.org>; Fri, 22 Jul 2011 16:02:13 -0700 (PDT)
Received: from mail-pz0-f47.google.com ([209.85.210.47]) (using TLSv1) by na3sys009aob117.postini.com ([74.125.148.12]) with SMTP ID DSNKTioBdOF/kVDHlcSml7i5iKofthA0cRnL@postini.com; Fri, 22 Jul 2011 16:02:14 PDT
Received: by mail-pz0-f47.google.com with SMTP id 36so5341191pzk.6 for <mext@ietf.org>; Fri, 22 Jul 2011 16:02:12 -0700 (PDT)
Received: by 10.68.37.68 with SMTP id w4mr3129080pbj.179.1311375732786; Fri, 22 Jul 2011 16:02:12 -0700 (PDT)
Received: from saby-lt.paloalto.toyota-itc.com ([206.132.173.18]) by mx.google.com with ESMTPS id k8sm2096277pbk.47.2011.07.22.16.02.11 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 22 Jul 2011 16:02:12 -0700 (PDT)
From: Romain KUNTZ <rkuntz@us.toyota-itc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Jul 2011 16:02:09 -0700
Message-Id: <5ABC57DC-9BF5-4626-B51F-DD50222BA5CB@us.toyota-itc.com>
To: mext@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [MEXT] Some questions on draft-sarikaya-mext-multicastdmm
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 23:02:15 -0000

Hello Behcet,

I'm currently updating draft-kuntz-dmm-summary and was considering including draft-sarikaya-mext-multicastdmm. However I have a few questions about your draft.

To me it seems that your proposal is not a DMM solution by itself but is built upon draft-kassi-mobileip-dmi. Am I right? Is the exact motivation of your proposal to support multicast on the mobile node when DMI is used?

About the solution itself:

* Section 3: 

  "MN starts to receive the packets over HA-MN link from
   CN and MN starts to send packets with a destination option containing
   the previous Care-of Address as MN's Home Address (HoA) to the CN."

I'm not sure why you are doing this? This sounds like route optimization to me.

* Section 6: 
 
  "Multicast state for the mobile node is usually established when
   mobile node was on the link and the state in Multicast State mobility
   option normally must match this state and the multicast state sent by
   the mobile node becomes the multicast state of the mobile node when
   communicating over MN-HA tunnel."

This sentence is quite hard to understand. Can you explain?


Thank you,
Romain

v2.8.7 | Report a Bug | By Email