Re: [MEXT] Some questions on draft-sarikaya-mext-multicastdmm
Romain KUNTZ <rkuntz@us.toyota-itc.com> Tue, 16 August 2011 01:17 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 8691A21F863E for <mext@ietfa.amsl.com>;
Mon, 15 Aug 2011 18:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.538
X-Spam-Level:
X-Spam-Status: No, score=-6.538 tagged_above=-999 required=5 tests=[AWL=0.061,
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 IYQhoXUI5+up for
<mext@ietfa.amsl.com>; Mon, 15 Aug 2011 18:17:05 -0700 (PDT)
Received: from na3sys009aog108.obsmtp.com (na3sys009aog108.obsmtp.com
[74.125.149.199]) by ietfa.amsl.com (Postfix) with SMTP id 21E0921F8CFE for
<mext@ietf.org>; Mon, 15 Aug 2011 18:16:57 -0700 (PDT)
Received: from mail-yx0-f174.google.com ([209.85.213.174]) (using TLSv1) by
na3sys009aob108.postini.com ([74.125.148.12]) with SMTP ID
DSNKTknFL6orKYzkVunTfEhtTb1KwQbEEFUo@postini.com;
Mon, 15 Aug 2011 18:17:45 PDT
Received: by mail-yx0-f174.google.com with SMTP id 19so3478269yxj.19 for
<mext@ietf.org>; Mon, 15 Aug 2011 18:17:35 -0700 (PDT)
Received: by 10.101.84.12 with SMTP id m12mr4497626anl.62.1313457454865;
Mon, 15 Aug 2011 18:17:34 -0700 (PDT)
Received: from hong-lt.paloalto.toyota-itc.com ([206.132.173.18]) by
mx.google.com with ESMTPS id b5sm2311591anm.47.2011.08.15.18.17.33
(version=TLSv1/SSLv3 cipher=OTHER); Mon, 15 Aug 2011 18:17: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: <1313421077.34816.YahooMailNeo@web111401.mail.gq1.yahoo.com>
Date: Mon, 15 Aug 2011 18:17:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3235EB6-0AED-4E1F-B094-77F641676C8E@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>
<94FEB967-CECD-440A-81DE-7D29C7F77251@us.toyota-itc.com>
<1313421077.34816.YahooMailNeo@web111401.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: Tue, 16 Aug 2011 01:17:05 -0000
Hi Behcet, On Aug 15, 2011, at 8:11, Behcet Sarikaya wrote: >>> 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. >> > > As it says in RFC 6275 the destination option is needed to inform the recipient > of the mobile node's home address > > > This is the functionality that is needed for dmm. There is no need for return routability procedure. > That means dmm can not work with an unmodified CN, which is the most important impact. I'm not sure you get my point: it is a security breach to use the destination option with a CN without having a proper binding registration & return routability procedure. Regards, Romain
- [MEXT] Some questions on draft-sarikaya-mext-mult… Romain KUNTZ
- Re: [MEXT] Some questions on draft-sarikaya-mext-… Behcet Sarikaya
- Re: [MEXT] Some questions on draft-sarikaya-mext-… Romain KUNTZ
- Re: [MEXT] Some questions on draft-sarikaya-mext-… Behcet Sarikaya
- Re: [MEXT] Some questions on draft-sarikaya-mext-… Behcet Sarikaya
- Re: [MEXT] Some questions on draft-sarikaya-mext-… Romain KUNTZ
- Re: [MEXT] Some questions on draft-sarikaya-mext-… Behcet Sarikaya
- Re: [MEXT] Some questions on draft-sarikaya-mext-… Romain KUNTZ
- Re: [MEXT] Some questions on draft-sarikaya-mext-… Behcet Sarikaya