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

Romain KUNTZ <rkuntz@us.toyota-itc.com> Sat, 13 August 2011 00:28 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 2664421F863A for <mext@ietfa.amsl.com>; Fri, 12 Aug 2011 17:28:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.474
X-Spam-Level:
X-Spam-Status: No, score=-6.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 PatAPrFT3r+3 for <mext@ietfa.amsl.com>; Fri, 12 Aug 2011 17:28:01 -0700 (PDT)
Received: from na3sys009aog124.obsmtp.com (na3sys009aog124.obsmtp.com [74.125.149.151]) by ietfa.amsl.com (Postfix) with SMTP id E5CDF21F861A for <mext@ietf.org>; Fri, 12 Aug 2011 17:28:00 -0700 (PDT)
Received: from mail-yx0-f182.google.com ([209.85.213.182]) (using TLSv1) by na3sys009aob124.postini.com ([74.125.148.12]) with SMTP ID DSNKTkXFMwpa/vHr/5Oon9Qi3GKwFwLPA5A/@postini.com; Fri, 12 Aug 2011 17:28:39 PDT
Received: by mail-yx0-f182.google.com with SMTP id 31so2935481yxl.41 for <mext@ietf.org>; Fri, 12 Aug 2011 17:28:35 -0700 (PDT)
Received: by 10.150.159.1 with SMTP id h1mr2692890ybe.233.1313195315563; Fri, 12 Aug 2011 17:28:35 -0700 (PDT)
Received: from [192.168.18.145] (adsl-99-49-9-53.dsl.pltn13.sbcglobal.net [99.49.9.53]) by mx.google.com with ESMTPS id p1sm109694yba.17.2011.08.12.17.28.33 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 12 Aug 2011 17:28:34 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Romain KUNTZ <rkuntz@us.toyota-itc.com>
In-Reply-To: <1313186725.90692.YahooMailNeo@web111402.mail.gq1.yahoo.com>
Date: Fri, 12 Aug 2011 17:28:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <94FEB967-CECD-440A-81DE-7D29C7F77251@us.toyota-itc.com>
References: <5ABC57DC-9BF5-4626-B51F-DD50222BA5CB@us.toyota-itc.com> <1311438985.9673.YahooMailRC@web111416.mail.gq1.yahoo.com> <B70CF283-B5F4-4F14-9FF3-9F7CF1575D37@us.toyota-itc.com> <1313186725.90692.YahooMailNeo@web111402.mail.gq1.yahoo.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
X-Mailer: Apple Mail (2.1244.3)
Cc: "mext@ietf.org" <mext@ietf.org>
Subject: Re: [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: Sat, 13 Aug 2011 00:28:02 -0000

Hello Behcet,

On Aug 12, 2011, at 15:05, Behcet Sarikaya wrote:
>> In section 5 you are stating "This protocol removes the need for route 
>> optimization.  Correspondent nodes do not need to maintain a binding cache of 
>> bindings for other  nodes.", so this does not sound coherent with the MN 
>> behavior exposed above. 
>> 
> 
> 
> RFC 6275 says destination option is used in a packet
>    sent by a mobile node while away from home, to inform the recipient
>    of the mobile node's home address.
> So we need it. I will clarify no route optimization statement, which means that there is no need 
> 
>  1 Home Test Init
> 
>       2  Care-of Test Init
> 
>       3  Home Test
> 
>       4  Care-of Test
> message exchanges.

If I remember correctly, RFC6275 requires the CN to have a binding cache entry to process destination options from the MN, which requires the return routability procedure. 

romain