Re: [nemo] RE: draft-ietf-nemo-home-network-models-05

Alexandru Petrescu <alexandru.petrescu@motorola.com> Fri, 10 February 2006 11:02 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7W2M-00086u-68; Fri, 10 Feb 2006 06:02:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7W2H-00084I-N5 for nemo@megatron.ietf.org; Fri, 10 Feb 2006 06:02:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08579 for <nemo@ietf.org>; Fri, 10 Feb 2006 06:00:03 -0500 (EST)
Received: from motgate4.mot.com ([144.189.100.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7WF4-0004AJ-6R for nemo@ietf.org; Fri, 10 Feb 2006 06:15:13 -0500
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id k1ABCxnp020925; Fri, 10 Feb 2006 04:12:59 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k1ABB3bD016998; Fri, 10 Feb 2006 05:11:04 -0600 (CST)
Message-ID: <43EC727D.6050505@motorola.com>
Date: Fri, 10 Feb 2006 12:01:17 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Pascal Thubert \\(pthubert\\)" <pthubert@cisco.com>
Subject: Re: [nemo] RE: draft-ietf-nemo-home-network-models-05
References: <7892795E1A87F04CADFCCF41FADD00FC01CDC9D4@xmb-ams-337.emea.cisco.com>
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC01CDC9D4@xmb-ams-337.emea.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, tj@kniveton.com, Margaret Wasserman <MRW@devicescape.com>, vijay.devarapalli@nokia.com, ryuji@sfc.wide.ad.jp, ernst@sfc.wide.ad.jp
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Sender: nemo-bounces@ietf.org
Errors-To: nemo-bounces@ietf.org

Pascal Thubert \(pthubert\) wrote:
> Hi Alex
> 
>>> In fact, the text did not appear particularly useful, and would 
>>> have lead to discussion going above and beyond the scope of the 
>>> draft; so the text was simply removed.
>> 
>> If that ICMP Redirect text (between HA and MR) did not appear to be
>>  particularly useful then I wonder how proxy ND by HA for _all_ 
>> addresses in the moving network is of any use at all.  By RFC3963 
>> the HA does proxy ND only for MR's Home Address.
> 
> [Pascal] We removed it because some nodes (including routers) will 
> not react to the redirect, see 
> http://www.mobilenetworks.org/~pthubert/draft-ietf-nemo-home-network-mod
>  els-issue9.txt so we can not see that as an absolute solution, 
> making it hard to recommend. Routing Information will not affect the
>  Hosts/MNs on the Home Links, so it is also a problem. We end up with
>  a pure L2 solution, and since the MR is reachable over a tunnel, it
>  boils down to proxying techniques.

Thanks for documenting that issue.

Pascal:
> ICMP redirect is a router to host thing.

Right, and the Mobile Router acts as a Mobile Host too.

Ryuji:
> some nodes ignore ICMP redirect.

Right and other nodes will never do proxy ND for addresses that are
topologically incorrect on that link.

>> draft-ietf-nemo-home-network-models-xx.txt:
>>> Thus, on the Home Link, the Home Agent must intercept all the 
>>> packets to ALL the Mobile Network Nodes on the registered 
>>> prefixes.  In order to do so, the Home Agent might perform some 
>>> form of ND proxying for all addresses in all registered Mobile 
>>> Network Prefixes.
>> 
>> This above paragraph makes no particular sense at all, since a HA 
>> doing proxy ND for a LFN node which is below MR will intercept 
>> packets from all the neighbours of HA addressed to LFN, even though
>>  it is the MR who should intercept or receive those packets.
>> 
>> There can be no "proxy ND" for an LFN on HA's link as long as the 
>> normal ND of same LFN is not happening on the home link.
> 
> [Pascal] Please read again. The "Nodes on the registered prefixes" 
> means nodes  (eg. LFNs) attached to MRs that are away from home. Thus
>  MRs can not intercept the packets to the LFN over the Home Link.

For some reason "intercept" was perceived by you as something where MR
must do proxy ND in order to receive.  I didn't mean so, sorry.  I meant 
MR should "receive" (or "intercept") packets for LFNs when away from 
home.  This happens by MR receiving packets tunnelled by HA.  The HA has
"intercepted" those packets for LFNs by doing proxy ND for MR's Home
Address exclusively, and not by doing proxy ND for any LFN address.  It
makes no sense for HA to do proxy ND for LFN address.

Again, HA doing proxy ND for LFNs is something topologically invalid.
Proxy ND of a host should be done on a link where the real ND for that
host is topologically valid.

Moreover, there are potentially 2^64 LFNs behind an MR with MNP /64.  HA
has no means to know which of those are active.  So will it send 2^64
periodic NAs as part of its proxy ND for LFNs?

> If MR was at home, then section 6.2.1 or 6.2.2 would apply. 6.2.1 
> describes your point, and yes, in that case the MR does the 
> interception, not the HA.

We agree on this.

Pascal:
> Thus, on the Home Link, the Home Agent must intercept all the packets
>  for ALL the Mobile Network Nodes on the registered prefixes - that 
> is for ALL nodes attached to Mobile Routers that are away from Home. 
> This should be a layer 2 operation, rather than layer 3.  The Home 
> agent might, for example,  perform some form of ND proxying for all 
> addresses in all registered Mobile Network Prefixes.  The Home Agent 
> must also protect the MNP space from autoconfiguration by 
> uncontrolled visitors at Neighbor Discovery level.

Is there a known implementation where the HA intercepts all the packets 
for ALL the Mobile Network Nodes by doing proxy ND for their addresses?

Does anyone plan to write such an implementation?

Alex