Re: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00

Henrik Levkowetz <henrik@levkowetz.com> Fri, 28 October 2005 19:24 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 1EVZpo-0004hE-Kw; Fri, 28 Oct 2005 15:24:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVZpm-0004h8-Ot for mip6@megatron.ietf.org; Fri, 28 Oct 2005 15:24:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04141 for <mip6@ietf.org>; Fri, 28 Oct 2005 15:23:56 -0400 (EDT)
Received: from av9-2-sn2.hy.skanova.net ([81.228.8.180]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVa3N-00070T-IX for mip6@ietf.org; Fri, 28 Oct 2005 15:38:19 -0400
Received: by av9-2-sn2.hy.skanova.net (Postfix, from userid 502) id 2D8B9381A0; Fri, 28 Oct 2005 21:23:58 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av9-2-sn2.hy.skanova.net (Postfix) with ESMTP id 558593817C; Fri, 28 Oct 2005 21:23:57 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com [81.224.201.50]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id F36E537E43; Fri, 28 Oct 2005 21:23:56 +0200 (CEST)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.54) id 1EVZpT-0007HD-NK; Fri, 28 Oct 2005 21:23:55 +0200
Message-ID: <43627ACB.9050806@levkowetz.com>
Date: Fri, 28 Oct 2005 21:23:55 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDD3@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDD3@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


on 2005-10-28 20:16 Soliman, Hesham said the following:

>> > => No. Movement detection is done based on Router 
>> Discovery. That's 
>> > what MIPv4 assumes...It only extends RFC 1256. You don't need that 
>> > extension if you're not using MIPv4, you detect movement 
>> based on RFC
>> >  1256. That's something we can detail in the draft.
>> 
>> Ok, so DSMIPv6 would be extended with Router Discovery.
> 
> => No, router discovery is an IPv4 feature. DSMIPv6 could monitor
> changes in RAs to detect movement.

Right.

The most appropriate current reference for detecting changes in
attachment to IPv4 only networks would probably be the IPv4 DNA
document, currently draft-ietf-dhc-dna-ipv4-17.txt.

	Henrik

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6