From exim@www1.ietf.org  Sun Jan  4 04:37:18 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21074
	for <mip6-archive@odin.ietf.org>; Sun, 4 Jan 2004 04:37:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ad4gk-0004DA-1K
	for mip6-archive@odin.ietf.org; Sun, 04 Jan 2004 04:36:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i049anbH016188
	for mip6-archive@odin.ietf.org; Sun, 4 Jan 2004 04:36:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ad4gj-0004D1-Cc
	for mip6-web-archive@optimus.ietf.org; Sun, 04 Jan 2004 04:36:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21061
	for <mip6-web-archive@ietf.org>; Sun, 4 Jan 2004 04:36:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ad4gg-0002WX-00
	for mip6-web-archive@ietf.org; Sun, 04 Jan 2004 04:36:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ad4eq-0002TE-00
	for mip6-web-archive@ietf.org; Sun, 04 Jan 2004 04:34:52 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ad4d4-0002PV-00
	for mip6-web-archive@ietf.org; Sun, 04 Jan 2004 04:33:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ad4d3-00043d-Lr; Sun, 04 Jan 2004 04:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ad4cq-000426-CS
	for mip6@optimus.ietf.org; Sun, 04 Jan 2004 04:32:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20993
	for <mip6@ietf.org>; Sun, 4 Jan 2004 04:32:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ad4cn-0002O1-00
	for mip6@ietf.org; Sun, 04 Jan 2004 04:32:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ad4av-0002L6-00
	for mip6@ietf.org; Sun, 04 Jan 2004 04:30:50 -0500
Received: from alpha1.its.monash.edu.au ([130.194.1.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ad4aQ-0002Hz-00
	for mip6@ietf.org; Sun, 04 Jan 2004 04:30:18 -0500
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01L50IGL6GDG9KP51Y@vaxc.its.monash.edu.au>
 for mip6@ietf.org; Sun, 04 Jan 2004 20:29:08 +1100
Received: from thwack.its.monash.edu.au
 (localhost.its.monash.edu.au [127.0.0.1])	by localhost (Postfix)
 with ESMTP	id 3E273318002; Sun, 04 Jan 2004 20:29:08 +1100 (EST)
Received: from mail1.monash.edu.au (bigted.its.monash.edu.au [130.194.11.60])
	by thwack.its.monash.edu.au (Postfix) with ESMTP	id 2F3DD2DC007; Sun,
 04 Jan 2004 20:29:08 +1100 (EST)
Date: Sun, 04 Jan 2004 20:29:08 +1100
From: Gregory Daley <Greg.Daley@eng.monash.edu.au>
Subject: Re: [Mip6] I am still puzzled in DAD mechanism in mipv6
To: Jari Arkko <jari.arkko@kolumbus.fi>
Cc: Lee Garth <garthdawn@hotmail.com>, mip6@ietf.org,
        Greg Daley <greg.daley@eng.monash.edu.au>
Message-id: <35992d354f9f.354f9f35992d@mail1.monash.edu.au>
MIME-version: 1.0
X-Mailer: Netscape Webmail
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Content-Transfer-Encoding: 7BIT
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Hi Jari and Lee,

Sorry about the delay in response,
I've been playing with my childrens' toys.

----- Original Message -----
From: Jari Arkko <jari.arkko@kolumbus.fi>
Date: Friday, December 26, 2003 8:35 pm
Subject: Re: [Mip6] I am still puzzled in DAD mechanism in mipv6

> Lee Garth wrote:
> 
> >    In a draft issued in July:draft-park-ipv6-dad-problem-wlan-00.txt
> >    The author says besides the time cost in the procedure that 
> MN proceeds the DAD itself, there is mechanical deficiency in 
> applying DAD in wireless environment.
> > 
> >    In chapter 2, it says:
> >     "In this case, IPv6 DAD will not be able to detect duplicate 
> address>      in 802.11 environment because if am 802.11 end 
> station recevies
> >      a DAD packet from a node which is having same MAC, the 
> 802.11 end      station discards the frame and will not be able to 
> defend the DAD. 
> (snip)
> >         But I don't see any subsequent draft concerning this 
> defect and 
> > thinking over further implementations. All drafts and 
> discussions I have 
> > read are about reducing the time cost in DAD procedure. Have it 
> already 
> > been avoided or amended in draft24? What is the solution then? I 
> would 
> > be very thankful if anyone here illuminates it to me.
> 
> I am not aware of any discussion regarding this, but it is possible
> that DNA BOF/WG has discussed it. Greg?
> 
> Draft 24 certainly does not (and will not) address the defect that
> you mention. The issue is not mobility specific. It might even be
> a non-IETF problem.

I believe that there's been some discussion on this topic, 
but I can't recall if it was on the list or at a meeting.

The DNA archive is at:
http://ecselists.eng.monash.edu.au/~warchive/dna/

I've not found it yet, but Daniel (the draft author)
may know about such discussions.

As Jari said, this may not even be an IETF specific
problem.

I've got the feeling that other types of packet delivery
may fail (apart from DAD) due to duplicate MAC addresses
(and not just in WLAN).  Ethernet switching may go awry 
even when IP layer address collisions don't occur (for
example if distinct CGA addresses or 3041 addresses are in use).

Greg.



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



From exim@www1.ietf.org  Tue Jan  6 02:44:08 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09467
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 02:44:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdlsL-0005lF-6o
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 02:43:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i067hfS0022144
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 02:43:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdlsK-0005l5-Kw
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 02:43:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09460
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 02:43:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdlsG-0006pE-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 02:43:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdlqL-0006jn-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 02:41:38 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adlot-0006gb-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 02:40:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adloo-0005Ll-5H; Tue, 06 Jan 2004 02:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdloI-0005Hs-KO
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 02:39:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09304
	for <mip6@ietf.org>; Tue, 6 Jan 2004 02:39:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdloE-0006dC-00
	for mip6@ietf.org; Tue, 06 Jan 2004 02:39:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdlmJ-0006VD-00
	for mip6@ietf.org; Tue, 06 Jan 2004 02:37:28 -0500
Received: from law9-f80.law9.hotmail.com ([64.4.9.80] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdlkV-0006Ig-00
	for mip6@ietf.org; Tue, 06 Jan 2004 02:35:35 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 5 Jan 2004 23:35:06 -0800
Received: from 218.22.21.27 by lw9fd.law9.hotmail.msn.com with HTTP;
	Tue, 06 Jan 2004 07:35:06 GMT
X-Originating-IP: [218.22.21.27]
X-Originating-Email: [garthdawn@hotmail.com]
X-Sender: garthdawn@hotmail.com
From: "Lee Garth" <garthdawn@hotmail.com>
To: Greg.Daley@eng.monash.edu.au
Cc: mip6@ietf.org
Date: Tue, 06 Jan 2004 07:35:06 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <Law9-F80as2lKn53y3W0000414e@hotmail.com>
X-OriginalArrivalTime: 06 Jan 2004 07:35:06.0312 (UTC) FILETIME=[9AD74C80:01C3D427]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id CAA09305
Subject: [Mip6] About two implementations on DAD in mip6 circumstances
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dear:

    I have read two implementations on DAD in mip6 circumstances in the=20
respected drafts.

    One is called "advanced DAD", implemented in mip6 where fast handover=
=20
is supported. The corresponding draft is:
                  =20
http://www.ietf.org/internet-drafts/draft-han-mobileip-adad-01.txt

    The other is called "optimistic DAD", implemented in all mip6=20
circumstances but with potential hazard to packet transmit confusion if D=
AD=20
fails. The corresponding draft is:
           =20
http://www.watersprings.org/pub/id/draft-moore-ipv6-optimistic-dad-03.txt

    It looks like optimistic DAD doesn't change much from the original DA=
D=20
procedure specified in RFC2462. I can't judge more about the robustness a=
nd=20
effectiveness of either. Would you please tell me more about the=20
implementations of both methods in real network, and which one is more=20
widely used?=20
   =20
    Thanks a lot!

                                                                      You=
rs
      ' spamcontrol '

_________________________________________________________________
=D3=EB=C1=AA=BB=FA=B5=C4=C5=F3=D3=D1=BD=F8=D0=D0=BD=BB=C1=F7=A3=AC=C7=EB=CA=
=B9=D3=C3 MSN Messenger:  http://messenger.msn.com/cn =20


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



From exim@www1.ietf.org  Tue Jan  6 04:42:10 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12490
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 04:42:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdniY-0002jh-PH
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 04:41:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i069fggP010515
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 04:41:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdniX-0002jW-Oo
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 04:41:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12466
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 04:41:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdniU-0003Mv-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 04:41:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adngr-0003IC-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 04:39:58 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adnez-0003D4-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 04:38:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adnez-0002R2-Pz; Tue, 06 Jan 2004 04:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adnem-0002OB-TI
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 04:37:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12292
	for <mip6@ietf.org>; Tue, 6 Jan 2004 04:37:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adnej-0003Ak-00
	for mip6@ietf.org; Tue, 06 Jan 2004 04:37:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adncm-00036j-00
	for mip6@ietf.org; Tue, 06 Jan 2004 04:35:45 -0500
Received: from law9-f69.law9.hotmail.com ([64.4.9.69] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adnb6-000312-00
	for mip6@ietf.org; Tue, 06 Jan 2004 04:34:00 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 6 Jan 2004 01:33:31 -0800
Received: from 218.22.21.27 by lw9fd.law9.hotmail.msn.com with HTTP;
	Tue, 06 Jan 2004 09:33:30 GMT
X-Originating-IP: [218.22.21.27]
X-Originating-Email: [garthdawn@hotmail.com]
X-Sender: garthdawn@hotmail.com
From: "Lee Garth" <garthdawn@hotmail.com>
To: soohong.park@samsung.com
Cc: mip6@ietf.org
Date: Tue, 06 Jan 2004 09:33:30 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <Law9-F6932sqT6WD6cf00004a51@hotmail.com>
X-OriginalArrivalTime: 06 Jan 2004 09:33:31.0163 (UTC) FILETIME=[25A986B0:01C3D438]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA12293
Subject: [Mip6] A question about the DAD protocol prototype
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dear:

    Having read the DAD sections in RFC2462, I have a question below:

    When a node(Node1) receives a NS sent from another node(Node2) who is=
=20
performing DAD procedure, it proves that an address duplication is taking=
=20
place. Then Node1 multicasts a NA with IP destination address set to=20
FF02::1, advertising the duplication to the whole link. And then Node2=20
discards the address it has just generated.
    Will the NA mentioned above affect the Neighbor Cache in all other=20
neighbors on the link? How long after the NA is multicasted can the Node1=
=20
use the address it has always been using? And how to manipulate the packe=
ts=20
being transfered to and fro Node1 that would possibly have been sent awry=
?

    Thanks a million!

                                                                     Your=
s
                                                                         =
=20
Garthdawn
' spamcontrol '

_________________________________________________________________
=D3=EB=C1=AA=BB=FA=B5=C4=C5=F3=D3=D1=BD=F8=D0=D0=BD=BB=C1=F7=A3=AC=C7=EB=CA=
=B9=D3=C3 MSN Messenger:  http://messenger.msn.com/cn =20


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



From exim@www1.ietf.org  Tue Jan  6 04:46:01 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12642
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 04:46:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdnmI-0002t0-BK
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 04:45:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i069jYeE011088
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 04:45:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdnmI-0002sl-0A
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 04:45:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12623
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 04:45:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdnmF-0003Ww-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 04:45:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdnkR-0003TY-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 04:43:39 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adniq-0003P2-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 04:42:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adnir-0002kl-KC; Tue, 06 Jan 2004 04:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdniY-0002jk-Rx
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 04:41:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12472
	for <mip6@ietf.org>; Tue, 6 Jan 2004 04:41:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdniV-0003N5-00
	for mip6@ietf.org; Tue, 06 Jan 2004 04:41:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adngt-0003IS-00
	for mip6@ietf.org; Tue, 06 Jan 2004 04:40:00 -0500
Received: from law9-f111.law9.hotmail.com ([64.4.9.111] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdnfM-0003BW-00
	for mip6@ietf.org; Tue, 06 Jan 2004 04:38:24 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 6 Jan 2004 01:37:55 -0800
Received: from 218.22.21.27 by lw9fd.law9.hotmail.msn.com with HTTP;
	Tue, 06 Jan 2004 09:37:54 GMT
X-Originating-IP: [218.22.21.27]
X-Originating-Email: [garthdawn@hotmail.com]
X-Sender: garthdawn@hotmail.com
From: "Lee Garth" <garthdawn@hotmail.com>
To: mip6@ietf.org
Date: Tue, 06 Jan 2004 09:37:54 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <Law9-F111RtkV1euV8Z0000494c@hotmail.com>
X-OriginalArrivalTime: 06 Jan 2004 09:37:55.0109 (UTC) FILETIME=[C2FC7D50:01C3D438]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA12473
Subject: [Mip6] (no subject)
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dear all:

    Moreover, what is the content of the NA multicasted to indicate that=20
there is an address duplication?
    I haven't find the answer to my questions in the RFC, and in the few=20
drafts I have read. So please do me a favour.

    Thanks.

                                                           Yours Sincerel=
y
                                                                    =20
Garthdawn

' spamcontrol '

_________________________________________________________________
=C3=E2=B7=D1=CF=C2=D4=D8 MSN Explorer:   http://explorer.msn.com/lccn/ =20


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



From exim@www1.ietf.org  Tue Jan  6 14:00:14 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29004
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 14:00:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdwQc-0004k3-A8
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 13:59:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06Ixk3P018226
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 13:59:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdwQc-0004jt-05
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 13:59:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28965
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 13:59:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdwQZ-0003AA-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 13:59:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdwOm-000356-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 13:57:53 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdwN2-000304-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 13:56:04 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AdwN3-0001KU-Fo
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 13:56:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdwMz-0004NE-Qe; Tue, 06 Jan 2004 13:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdwMq-0004MR-QC
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 13:55:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28885
	for <mip6@ietf.org>; Tue, 6 Jan 2004 13:55:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdwMo-0002yT-00
	for mip6@ietf.org; Tue, 06 Jan 2004 13:55:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdwKy-0002tg-00
	for mip6@ietf.org; Tue, 06 Jan 2004 13:53:56 -0500
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdwKG-0002pJ-00
	for mip6@ietf.org; Tue, 06 Jan 2004 13:53:12 -0500
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136])
	by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i06Ir7aA006505
	for <mip6@ietf.org>; Tue, 6 Jan 2004 11:53:09 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i06Ir2NQ016538
	for <mip6@ietf.org>; Tue, 6 Jan 2004 12:53:03 -0600
Received: from nal.motlabs.com (test9.crm.mot.com [10.161.201.219])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 674B085272C
	for <mip6@ietf.org>; Tue,  6 Jan 2004 19:53:02 +0100 (CET)
Message-ID: <3FFB040D.4050001@nal.motlabs.com>
Date: Tue, 06 Jan 2004 19:53:01 +0100
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Mip6] AH ICV covers Home Address of rt hdr 2 of BAck from HA?
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

I'm wondering whether the ICV computation of an AH extension header in
transport mode with Binding Acknowledgement Mobility Header covers the
Type 2 Routing Header too (BAck is sent by HA to MN when in a foreign
network).  I understand that such an ICV does cover a Type 0 routing
header, this being stated explicitely in rfc2402bis.txt, routing header
type 0 being mutable but predictable.  However, I can't find text in
draft-24 saying that Routing Header Type 2 is mutable but predictable.
Is it?

Alex


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



From exim@www1.ietf.org  Tue Jan  6 14:28:37 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29826
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 14:28:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adws6-0005ca-2T
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 14:28:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06JSAZR021607
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 14:28:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adws5-0005cQ-TY
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 14:28:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29776
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 14:28:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adws3-0004gJ-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:28:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdwqA-0004XZ-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:26:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adwp2-0004Qk-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:25:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adwp3-0005Tp-9J; Tue, 06 Jan 2004 14:25:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adwou-0005TF-HZ
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 14:24:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29670
	for <mip6@ietf.org>; Tue, 6 Jan 2004 14:24:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adwor-0004PM-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:24:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adwm4-0004F3-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:21:57 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdwjI-000443-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:19:04 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i06JHvn27016;
	Tue, 6 Jan 2004 11:17:57 -0800
X-mProtect: <200401061917> Nokia Silicon Valley Messaging Protection
Received: from dadhcp-172019060124.americas.nokia.com (172.19.60.124, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdjPeCqk; Tue, 06 Jan 2004 11:17:56 PST
Message-ID: <3FFB09D8.2000501@iprg.nokia.com>
Date: Tue, 06 Jan 2004 11:17:44 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <petrescu@nal.motlabs.com>
CC: mip6@ietf.org
Subject: Re: [Mip6] AH ICV covers Home Address of rt hdr 2 of BAck from HA?
References: <3FFB040D.4050001@nal.motlabs.com>
In-Reply-To: <3FFB040D.4050001@nal.motlabs.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

it should be the same. Routing Header type 2 is also mutable
and predictable.

draft-ietf-mobileip-mipv6-ha-ipsec-03.txt says

    o  IPsec AH [3] authenticator calculation MUST be performed as if a
       packet with a Type 2 Routing header would have the home address in
       the IPv6 destination address field and the care-of address in the
       Routing header.  Type 2 Routing header should be treated by IPsec
       in the same manner as Type 0 Routing header.

the last sentence should answer your question.

Vijay

Alexandru Petrescu wrote:
> Hi,
> 
> I'm wondering whether the ICV computation of an AH extension header in
> transport mode with Binding Acknowledgement Mobility Header covers the
> Type 2 Routing Header too (BAck is sent by HA to MN when in a foreign
> network).  I understand that such an ICV does cover a Type 0 routing
> header, this being stated explicitely in rfc2402bis.txt, routing header
> type 0 being mutable but predictable.  However, I can't find text in
> draft-24 saying that Routing Header Type 2 is mutable but predictable.
> Is it?
> 
> Alex
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www.ietf.org/mailman/listinfo/mip6


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



From exim@www1.ietf.org  Tue Jan  6 14:40:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00365
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 14:40:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adx3a-0006RW-TQ
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 14:40:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06Je1sr024741
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 14:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adx3Z-0006Qh-1C
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 14:40:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00356
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 14:39:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adx3W-0005M7-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:39:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adx1u-0005If-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:38:19 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adx0d-0005D2-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:36:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adx0f-00062S-63; Tue, 06 Jan 2004 14:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adwzh-00061c-AP
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 14:36:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00216
	for <mip6@ietf.org>; Tue, 6 Jan 2004 14:35:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adwze-00059S-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:35:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adwxk-00054S-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:34:01 -0500
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adwx3-00050T-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:33:17 -0500
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i06JXEaA000325;
	Tue, 6 Jan 2004 12:33:16 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id i06JVqQF022558;
	Tue, 6 Jan 2004 13:31:52 -0600
Received: from nal.motlabs.com (test9.crm.mot.com [10.161.201.219])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 3972385272C; Tue,  6 Jan 2004 20:33:10 +0100 (CET)
Message-ID: <3FFB0D76.2010304@nal.motlabs.com>
Date: Tue, 06 Jan 2004 20:33:10 +0100
From: Alexandru Petrescu <petrescu@nal.motlabs.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Cc: mip6@ietf.org
Subject: Re: [Mip6] AH ICV covers Home Address of rt hdr 2 of BAck from HA?
References: <3FFB040D.4050001@nal.motlabs.com> <3FFB09D8.2000501@iprg.nokia.com>
In-Reply-To: <3FFB09D8.2000501@iprg.nokia.com>
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Vijay Devarapalli wrote:
> it should be the same. Routing Header type 2 is also mutable
> and predictable.
> 
> draft-ietf-mobileip-mipv6-ha-ipsec-03.txt says
> 
>    o  IPsec AH [3] authenticator calculation MUST be performed as if a
>       packet with a Type 2 Routing header would have the home address in
>       the IPv6 destination address field and the care-of address in the
>       Routing header.  Type 2 Routing header should be treated by IPsec
>       in the same manner as Type 0 Routing header.
> 
> the last sentence should answer your question.

Stated that way, yes, it does. So an implementer should implement it
that way: routing header Type2 _is_ mutable but predictable, like Type 0.

I'm not looking for text corrections, just wanted to say that I can't
find that text you're citing in draft-ha-ipsec-06 (why do you refer to 03?)

Thanks for the clarification.

Alex


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



From exim@www1.ietf.org  Tue Jan  6 14:58:13 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00787
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 14:58:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdxKk-0006nj-Lu
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 14:57:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06Jvk9u026142
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 14:57:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdxKk-0006nZ-B0
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 14:57:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00769
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 14:57:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdxKh-0005v0-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:57:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdxIn-0005sK-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:55:46 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdxH6-0005q9-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 14:54:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdxH7-0006ff-Lb; Tue, 06 Jan 2004 14:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdxGu-0006et-IK
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 14:53:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00693
	for <mip6@ietf.org>; Tue, 6 Jan 2004 14:53:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdxGr-0005on-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:53:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdxF1-0005l0-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:51:52 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdxDZ-0005i4-00
	for mip6@ietf.org; Tue, 06 Jan 2004 14:50:21 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i06Jnbi17394;
	Tue, 6 Jan 2004 11:49:37 -0800
X-mProtect: <200401061949> Nokia Silicon Valley Messaging Protection
Received: from dadhcp-172019060124.americas.nokia.com (172.19.60.124, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdGIptXR; Tue, 06 Jan 2004 11:49:36 PST
Message-ID: <3FFB1145.5030408@iprg.nokia.com>
Date: Tue, 06 Jan 2004 11:49:25 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <petrescu@nal.motlabs.com>
CC: mip6@ietf.org
Subject: Re: [Mip6] AH ICV covers Home Address of rt hdr 2 of BAck from HA?
References: <3FFB040D.4050001@nal.motlabs.com> <3FFB09D8.2000501@iprg.nokia.com> <3FFB0D76.2010304@nal.motlabs.com>
In-Reply-To: <3FFB0D76.2010304@nal.motlabs.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


>> draft-ietf-mobileip-mipv6-ha-ipsec-03.txt says
>>
>>    o  IPsec AH [3] authenticator calculation MUST be performed as if a
>>       packet with a Type 2 Routing header would have the home address in
>>       the IPv6 destination address field and the care-of address in the
>>       Routing header.  Type 2 Routing header should be treated by IPsec
>>       in the same manner as Type 0 Routing header.
>>
>> the last sentence should answer your question.
> 
> 
> Stated that way, yes, it does. So an implementer should implement it
> that way: routing header Type2 _is_ mutable but predictable, like Type 0.
> 
> I'm not looking for text corrections, just wanted to say that I can't
> find that text you're citing in draft-ha-ipsec-06 (why do you refer to 03?)

that is something I am unhappy with. all references to AH were
removed. I dont remember which issue this was discussed in.

Vijay


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



From exim@www1.ietf.org  Tue Jan  6 16:22:12 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04549
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 16:22:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adye0-0002AK-Vv
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 16:21:44 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06LLiSB008318
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 16:21:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adye0-0002A5-RB
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 16:21:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04493
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 16:21:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adydz-0001Dm-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 16:21:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adyc6-00018m-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 16:19:47 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdyaP-000131-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 16:18:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdyaP-0001yl-5f; Tue, 06 Jan 2004 16:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adya7-0001y3-Bf
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 16:17:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04199
	for <mip6@ietf.org>; Tue, 6 Jan 2004 16:17:40 -0500 (EST)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adya5-0000zq-00
	for mip6@ietf.org; Tue, 06 Jan 2004 16:17:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AdyY9-0000q9-00
	for mip6@ietf.org; Tue, 06 Jan 2004 16:15:41 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdyWL-0000hF-00
	for mip6@ietf.org; Tue, 06 Jan 2004 16:13:49 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i06LDl411220
	for <mip6@ietf.org>; Tue, 6 Jan 2004 23:13:48 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66f9df5724ac158f21081@esvir01nok.ntc.nokia.com> for <mip6@ietf.org>;
 Tue, 6 Jan 2004 23:13:47 +0200
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 6 Jan 2004 13:13:46 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 6 Jan 2004 15:13:45 -0600
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DBC22@daebe007.americas.nokia.com>
Thread-Topic: MIPSHOP Research Group Created
Thread-Index: AcPUmfgjEPZZH9ltRC+tQPwcbIXcxQ==
To: <mip6@ietf.org>
X-OriginalArrivalTime: 06 Jan 2004 21:13:46.0277 (UTC) FILETIME=[F89F2550:01C3D499]
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] MIPSHOP Research Group Created
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


http://www1.ietf.org/mail-archive/ietf-announce/Current/msg27737.html

-Basavaraj

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



From exim@www1.ietf.org  Tue Jan  6 16:40:14 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05149
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 16:40:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdyvS-00031z-PM
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 16:39:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06Ldkx8011645
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 16:39:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdyvS-00031k-Ia
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 16:39:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05118
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 16:39:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdyvQ-0001ry-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 16:39:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adyta-0001nf-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 16:37:51 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adyrp-0001kW-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 16:36:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Adyrp-0002d4-QK; Tue, 06 Jan 2004 16:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AdyrX-0002cD-GR
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 16:35:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05030
	for <mip6@ietf.org>; Tue, 6 Jan 2004 16:35:40 -0500 (EST)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AdyrV-0001i2-00
	for mip6@ietf.org; Tue, 06 Jan 2004 16:35:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Adypa-0001f7-00
	for mip6@ietf.org; Tue, 06 Jan 2004 16:33:42 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Adynh-0001cd-00
	for mip6@ietf.org; Tue, 06 Jan 2004 16:31:45 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i06LVi427997
	for <mip6@ietf.org>; Tue, 6 Jan 2004 23:31:44 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66f9efbe93ac158f2521c@esvir05nok.ntc.nokia.com> for <mip6@ietf.org>;
 Tue, 6 Jan 2004 23:31:42 +0200
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 6 Jan 2004 13:31:27 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] MOBOPTS Research Group Created
Date: Tue, 6 Jan 2004 15:31:26 -0600
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DBC26@daebe007.americas.nokia.com>
Thread-Topic: MIPSHOP Research Group Created
Thread-Index: AcPUmfgjEPZZH9ltRC+tQPwcbIXcxQAAmPNw
To: <mip6@ietf.org>
X-OriginalArrivalTime: 06 Jan 2004 21:31:27.0235 (UTC) FILETIME=[71007D30:01C3D49C]
Content-Transfer-Encoding: quoted-printable
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> Subject: [Mip6] MIPSHOP Research Group Created

I meant to say Mobopts :( instead of MIPSHOP

>=20
>=20
>=20
> http://www1.ietf.org/mail-archive/ietf-announce/Current/msg27737.html
>=20
> -Basavaraj
>=20

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



From exim@www1.ietf.org  Tue Jan  6 18:18:17 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09403
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 18:18:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0SM-00075V-M0
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 18:17:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06NHoEw027239
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 18:17:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0SM-00075F-G5
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 18:17:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09350
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 18:17:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0SI-0005Yh-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:17:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae0QR-0005US-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:15:52 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0Oi-0005RM-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:14:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0Of-0006wP-JZ; Tue, 06 Jan 2004 18:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0OR-0006vm-GJ
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 18:13:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09011
	for <mip6@ietf.org>; Tue, 6 Jan 2004 18:13:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0OO-0005Pd-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:13:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae0MZ-0005Nb-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:11:52 -0500
Received: from alpha2.its.monash.edu.au ([130.194.1.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0Lc-0005Kp-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:10:52 -0500
Received: from localhost ([130.194.13.81]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01L543PBVJGU9KPKNN@vaxc.its.monash.edu.au>
 for mip6@ietf.org; Wed, 07 Jan 2004 10:10:15 +1100
Received: from kapow.its.monash.edu.au
 (localhost.its.monash.edu.au [127.0.0.1])	by localhost (Postfix)
 with ESMTP	id D12031B0002; Wed, 07 Jan 2004 10:10:14 +1100 (EST)
Received: from eng.monash.edu.au (knuth.eng.monash.edu.au [130.194.252.110])
	by kapow.its.monash.edu.au (Postfix) with ESMTP	id B83F0124003; Wed,
 07 Jan 2004 10:10:14 +1100 (EST)
Date: Wed, 07 Jan 2004 10:10:14 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [Mip6] (no subject)
To: Lee Garth <garthdawn@hotmail.com>
Cc: mip6@ietf.org
Reply-to: greg.daley@eng.monash.edu.au
Message-id: <3FFB4056.9060802@eng.monash.edu.au>
Organization: Monash University
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en, en-us
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
References: <Law9-F111RtkV1euV8Z0000494c@hotmail.com>
Content-Transfer-Encoding: 7BIT
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Hi Lee,

Lee Garth wrote:
> Dear all:
> 
>    Moreover, what is the content of the NA multicasted to indicate that 
> there is an address duplication?
>    I haven't find the answer to my questions in the RFC, and in the few 
> drafts I have read. So please do me a favour.
> 
The intent of the multicast NA is to respond to an NS with
the unspecified address (which is used for DAD).

Since there is no source address in the NS to respond to,
the response must go to all nodes.

In optimistic DAD this effect is used to clear any cache entries
created by the optimistic node (since the multicast NA from the
DAD defender goes out with Override flag set).

Greg


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



From exim@www1.ietf.org  Tue Jan  6 18:26:24 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09724
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 18:26:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0aD-0007Pn-NL
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 18:25:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06NPvJN028497
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 18:25:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0aD-0007PY-Hb
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 18:25:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09674
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 18:25:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0aA-0005wQ-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:25:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae0YG-0005qT-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:23:56 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0WN-0005lx-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:21:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0WP-0007EX-Nl; Tue, 06 Jan 2004 18:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0WH-0007DY-LD
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 18:21:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09564
	for <mip6@ietf.org>; Tue, 6 Jan 2004 18:21:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0WE-0005kL-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:21:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae0US-0005ge-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:20:01 -0500
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0TA-0005cF-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:18:41 -0500
Received: from localhost ([130.194.13.81]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01L543R2LWYU8X1SA3@vaxh.its.monash.edu.au> for mip6@ietf.org;
 Wed, 7 Jan 2004 10:11:39 +1100
Received: from kapow.its.monash.edu.au
 (localhost.its.monash.edu.au [127.0.0.1])	by localhost (Postfix)
 with ESMTP	id 244AB1B0002; Wed, 07 Jan 2004 10:11:39 +1100 (EST)
Received: from eng.monash.edu.au (knuth.eng.monash.edu.au [130.194.252.110])
	by kapow.its.monash.edu.au (Postfix) with ESMTP	id 123A0124004; Wed,
 07 Jan 2004 10:11:39 +1100 (EST)
Date: Wed, 07 Jan 2004 10:11:38 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: Re :[Mip6] About two implementations on DAD in mip6 circumstances
To: soohong.park@samsung.com
Cc: Lee Garth <garthdawn@hotmail.com>, "mip6@ietf.org" <mip6@ietf.org>
Reply-to: greg.daley@eng.monash.edu.au
Message-id: <3FFB40AA.2040304@eng.monash.edu.au>
Organization: Monash University
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
X-Accept-Language: en, en-us
References: <664069.1073376180269.JavaMail.weblogic@ep_app25>
Content-Transfer-Encoding: 7BIT
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Hi Daniel,

PARK SOO HONG wrote:

>     It looks like optimistic DAD doesn't change much from the original DAD 
> procedure specified in RFC2462. I can't judge more about the robustness and 
> effectiveness of either. Would you please tell me more about the 
> implementations of both methods in real network, and which one is more 
> widely used? 
>     
> Daniel> I heard optimistic DAD has been already implemented in Monashi Univ. and MS.
> Daniel> In advance DAD case, it is also implemented in SAIT based on Linux OS as well.
> Daniel> Not sure which one is more widely used because it depends on operator's decision IMHO.

I hear that Elmic solutions also have an optimistic DAD/DIID
implementation.

Greg


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



From exim@www1.ietf.org  Tue Jan  6 18:48:34 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10425
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 18:48:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0vg-0008Fq-0U
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 18:48:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06Nm7xr031723
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 18:48:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0vf-0008Fa-Mm
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 18:48:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10412
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 18:48:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0vc-0006z5-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:48:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae0tt-0006tX-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:46:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0sf-0006mg-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:45:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0sh-000876-CG; Tue, 06 Jan 2004 18:45:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0rj-000850-QS
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 18:44:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10241
	for <mip6@ietf.org>; Tue, 6 Jan 2004 18:43:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0rg-0006j2-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:44:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae0ph-0006dC-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:41:58 -0500
Received: from smtp814.mail.sc5.yahoo.com ([66.163.170.84])
	by ietf-mx with smtp (Exim 4.12)
	id 1Ae0oI-0006Z4-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:40:31 -0500
Received: from unknown (HELO eremmell) (elmic@sbcglobal.net@64.170.248.130 with login)
  by smtp814.mail.sc5.yahoo.com with SMTP; 6 Jan 2004 23:40:23 -0000
From: "Ed Remmell" <eremmell@elmic.com>
To: <greg.daley@eng.monash.edu.au>, <soohong.park@samsung.com>
Cc: "'Lee Garth'" <garthdawn@hotmail.com>, <mip6@ietf.org>
Subject: RE: Re :[Mip6] About two implementations on DAD in mip6 circumstances
Date: Tue, 6 Jan 2004 15:40:22 -0800
Message-ID: <000101c3d4ae$74ddb230$0500a8c0@eremmell>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <3FFB40AA.2040304@eng.monash.edu.au>
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Greg -

> I hear that Elmic solutions also have an optimistic DAD/DIID
> implementation.

That is correct. This functionality is also in our Win32 demo of our
dual stack embedded systems protocol products, available for download
here:

http://www.elmic.com/treckDemo.zip


>From an email I sent to this list on 7/23/03, which explained how we
achieved less than 50 millisecond MIPv6 MN handover latency:

"Well, it is fairly straightforward (for those of us who are able to
hack the IPv6 kernel - since our product is a TCP/IP kernel for embedded
systems, this isn't a big problem for us)... basically, I combined your
previous optimistic DAD ideas with the following requirement from
RFC-2462:

"For a set of addresses formed from the same interface identifier, it is
sufficient to check that the link-local address generated from the
identifier is unique on the link. In such cases, after the link-local
address is tested for uniqueness, and if no duplicate address is
detected, an implementation MAY choose to skip Duplicate Address
Detection for additional addresses derived from the same interface
identifier."

After receiving an indication that a L3 handover has occurred (in this
case, the RA from a new router, since I had Eager Cell Switching
enabled), I restart DAD on the auto-configured link-local scope address.
We kind of stretch the above RFC-2462 requirement a little, but when
combined with your optimistic DAD ideas I feel we are still compliant.
Basically, we immediately auto-configure the prefixes in the RA as the
MN's new CoAs on the new link, but note that for the purpose of
optimistic DAD we treat this entire set of addresses (formed from the
same interface ID) as tentative until DAD completes on the
auto-configured link-local scope address. So, that means that we can
immediately use these new CoAs to select a primary CoA, and also
immediately use them as the source address for packets that we send for
MN registration, however while the auto-configured link-local scope
address is tentative, we cannot use any of these CoAs as the source
address of a NS, and if we receive a NS for one of these CoAs, when we
respond with the NA we must clear the Override bit in the NA. Also, note
from the packet trace that since we complete configuration on these CoAs
immediately (even though they are still "tentative" per the status of
the auto-configured link-local scope address), we send an unsolicited NA
for each of these CoA immediately, however the Override bit is cleared.
I think that sums it up.

Also, if DAD were to fail on the auto-configured link-local scope
address, we would immediately unconfigure the entire set of addresses
(i.e. CoAs) formed from that same interface ID, and then the interface
would be disabled for IPv6 until we can set a random interface ID per
RFC-3041 (if that's what the user application wants us to do, it is an
interface option they can specify) and try to reopen the interface again
on the new link.

Also, I ended up modifying our implementation to always send the RS with
the unspecified source address. That seems safer, because the MN can
never tell when it will show up on a new link and it might be soliciting
for a router at the time.

Also, note that we currently don't do any random delays to prohibit
sending messages when we come up on a new link due to link movement."

I have a packet capture of our MIPv6 MN handover processing illustrating
our use of optimistic DAD, I can send it to you if you request it
(rather than spam'ing this list).

Thanks.
- Ed

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.542 / Virus Database: 336 - Release Date: 11/18/2003
 


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



From exim@www1.ietf.org  Tue Jan  6 19:15:24 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09723
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 18:26:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0aD-0007PQ-EP
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 18:25:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i06NPvAQ028481
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 18:25:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0aD-0007PE-4Z
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 18:25:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09671
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 18:25:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0aA-0005wL-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:25:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae0YF-0005qL-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:23:55 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0WN-0005lv-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 18:21:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0WP-0007E4-9U; Tue, 06 Jan 2004 18:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae0WG-0007DT-L8
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 18:21:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09557
	for <mip6@ietf.org>; Tue, 6 Jan 2004 18:21:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0WD-0005k8-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:21:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae0US-0005gU-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:20:00 -0500
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae0T9-0005cF-00
	for mip6@ietf.org; Tue, 06 Jan 2004 18:18:40 -0500
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01L543J630S28X1PI5@vaxh.its.monash.edu.au> for mip6@ietf.org;
 Wed, 7 Jan 2004 10:05:17 +1100
Received: from thwack.its.monash.edu.au
 (localhost.its.monash.edu.au [127.0.0.1])	by localhost (Postfix)
 with ESMTP	id CB794318002; Wed, 07 Jan 2004 10:05:16 +1100 (EST)
Received: from eng.monash.edu.au (knuth.eng.monash.edu.au [130.194.252.110])
	by thwack.its.monash.edu.au (Postfix) with ESMTP	id 9937C2DC005; Wed,
 07 Jan 2004 10:05:16 +1100 (EST)
Date: Wed, 07 Jan 2004 10:05:16 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [Mip6] A question about the DAD protocol prototype
To: Lee Garth <garthdawn@hotmail.com>
Cc: soohong.park@samsung.com, mip6@ietf.org
Reply-to: greg.daley@eng.monash.edu.au
Message-id: <3FFB3F2C.7050500@eng.monash.edu.au>
Organization: Monash University
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
X-Accept-Language: en, en-us
References: <Law9-F6932sqT6WD6cf00004a51@hotmail.com>
Content-Transfer-Encoding: 7BIT
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Hi Lee,

Lee Garth wrote:
> Dear:
> 
>    Having read the DAD sections in RFC2462, I have a question below:
> 
>    When a node(Node1) receives a NS sent from another node(Node2) who is 
> performing DAD procedure, it proves that an address duplication is 
> taking place. Then Node1 multicasts a NA with IP destination address set 
> to FF02::1, advertising the duplication to the whole link. And then 
> Node2 discards the address it has just generated.
>    Will the NA mentioned above affect the Neighbor Cache in all other 
> neighbors on the link? How long after the NA is multicasted can the 
> Node1 use the address it has always been using? And how to manipulate 
> the packets being transfered to and fro Node1 that would possibly have 
> been sent awry?

Yes the Node1 NA overrides existing cache entries where they exist
(it has the override flag set).
In the case no existing cache entry existed, it is unlikely
to create new entries.

Since the DAD NS doesn't contain the Source Link Layer Address Option
(SLLAO), it doesn't make or modify any neighbor
cache entries (with RFC 2462 DAD).

The Owner of the address (Node1) can always use the address
(with no delay).

Only the tentative node must wait in DAD, and these nodes
do not NA while tentative.

Greg


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



From exim@www1.ietf.org  Tue Jan  6 19:48:22 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13116
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 19:48:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae1rW-0002BW-VI
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 19:47:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i070ls89008392
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 19:47:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae1rW-0002BH-Ov
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 19:47:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13092
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 19:47:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae1rV-0002c5-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 19:47:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae1pY-0002Yd-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 19:45:53 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae1om-0002Vc-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 19:45:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae1ok-00021p-SA; Tue, 06 Jan 2004 19:45:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae1ns-00020V-5a
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 19:44:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13000
	for <mip6@ietf.org>; Tue, 6 Jan 2004 19:44:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae1np-0002Tp-00
	for mip6@ietf.org; Tue, 06 Jan 2004 19:44:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae1mB-0002Mo-00
	for mip6@ietf.org; Tue, 06 Jan 2004 19:42:24 -0500
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae1kK-0002Cs-00
	for mip6@ietf.org; Tue, 06 Jan 2004 19:40:28 -0500
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HR300445GILY4@mailout2.samsung.com> for mip6@ietf.org; Wed,
 07 Jan 2004 09:39:57 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HR3002ADGFLHT@mailout2.samsung.com> for mip6@ietf.org; Wed,
 07 Jan 2004 09:38:10 +0900 (KST)
Received: from andy ([168.219.203.230])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HR3003J5GFL7L@mmp2.samsung.com> for mip6@ietf.org;
 Wed, 07 Jan 2004 09:38:09 +0900 (KST)
Date: Wed, 07 Jan 2004 09:38:42 +0900
From: Soohong Daniel Park <soohong.park@samsung.com>
Subject: RE: Re :[Mip6] About two implementations on DAD in mip6 circumstances
In-reply-to: <000101c3d4ae$74ddb230$0500a8c0@eremmell>
To: "'Ed Remmell'" <eremmell@elmic.com>, greg.daley@eng.monash.edu.au
Cc: "'Lee Garth'" <garthdawn@hotmail.com>, mip6@ietf.org,
        soohong.park@samsung.com
Message-id: <002d01c3d4b6$99f6ca90$e6cbdba8@andy>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT


> That is correct. This functionality is also in our Win32 demo of our
> dual stack embedded systems protocol products, available for download
> here:
> 
> http://www.elmic.com/treckDemo.zip

Sounds good.
We also implemented this skill on the linux OS.
I am sure this issue is a mature status in IETF although
related WGs do not have a hard stance at the moment.




Daniel (Soohong Daniel Park)
Mobile Platform Laboratory, SAMSUNG Electronics


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



From exim@www1.ietf.org  Tue Jan  6 19:48:22 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13115
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 19:48:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae1rX-0002Bm-97
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 19:47:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i070lt9O008408
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 19:47:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae1rX-0002BX-55
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 19:47:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13095
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 19:47:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae1rV-0002cA-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 19:47:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae1pZ-0002Yl-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 19:45:54 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae1om-0002Vd-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 19:45:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae1ol-000220-Ao; Tue, 06 Jan 2004 19:45:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae1nu-00020a-Bd
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 19:44:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13021
	for <mip6@ietf.org>; Tue, 6 Jan 2004 19:44:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae1ns-0002UO-00
	for mip6@ietf.org; Tue, 06 Jan 2004 19:44:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae1mI-0002Ni-00
	for mip6@ietf.org; Tue, 06 Jan 2004 19:42:30 -0500
Received: from [211.225.219.76] (helo=nt6.introcom.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1Ae1km-0002Fd-00
	for mip6@ietf.org; Tue, 06 Jan 2004 19:40:56 -0500
Received: from YounHeeHan (202.20.193.254)
	by nt6.introcom.net (211.225.219.76) with [Nmail V3.3 20021108(S)]
	for <mip6@ietf.org> from <yhhan@thinkonweb.com>;
	Wed, 07 Jan 2004 09:39:19 +0900
Message-ID: <009d01c3d4b7$1ccc2370$3d2f024b@YounHeeHan>
From: "Youn-Hee Han" <yhhan@thinkonweb.com>
To: "Lee Garth" <garthdawn@hotmail.com>
Cc: <mip6@ietf.org>
Subject: Re: [Mip6] About two implementations on DAD in mip6 circumstances
Date: Wed, 7 Jan 2004 09:41:53 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: base64
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

SGVsbG8gTGVlLA0KDQpGaXJzdGx5LCBwbGVhc2UgY2FsbCBpdCAnYWR2YW5jZSBEQUQnLCBub3Qg
J2FkdmFuY2VkIERBRCcuDQoNCkl0IGlzIG9idmlvdXMgdGhhdCAnb3B0aW1pc3RpYyBEQUQnIGRv
ZXNuJ3QgcmVxdWlyZSBtdWNoIGNoYW5nZXMgZnJvbSANCm9yaWdpbmFsIGJlaGF2aW9yLiBBbmQs
IGN1cnJlbnQgTUlQdjYgZG9lc24ndCBtb2RpZnkgYWNjZXNzIHJvdXRlcjsgDQonYWR2YW5jZSBE
QUQnLCBob3dldmVyLCBuZWVkcyBzdXBwb3J0cyBvZiBhY2Nlc3Mgcm91dGVycy4NClNvLCBpbiB0
ZXJtcyBvZiBmYXN0IGRlcGxveWVtZW50LCBNSVB2NiArIG9EQUQgd2lsbCBiZSBtb3JlIGhlbHBm
dWwgDQppbiBvcmRlciB0byBhY2hpZXZlIGxvdyBsYXRlbmN5IElQdjYgaGFuZG92ZXIuDQoNCkJ1
dCwgaW4gb3JkZXIgdG8gc3VwcG9ydCBzZWFtbGVzcyAoZS5nLiwgSVAtbGV2ZWwgc29mdCBvciBz
ZW1pLXNvZnQpIGhhbmRvdmVyLA0KdGhlcmUgaGF2ZSBiZWVuIHNvbWUgZWZmb3J0cyB0byBtb2Rp
ZnkgYWNjZXNzIHJvdXRlcnMgKGUuZy4sIGZhc3QgYmluZGluZyB1cGRhdGUgDQphbmQgdHVubmVs
IHNldHVwIGluIEZNSVB2NikuIFNvLCBJTU8sICdhZHZhbmNlIERBRCcgY2FuIGJlIGEgc3VwcGxl
bWVudGFyeSANCmZ1bmN0aW9uYWxpdHkgZm9yIHByb3RvY29scyB3aGljaCBhbGxvd3Mgbm9kZXMg
YW5kIGFjY2VzcyByb3V0ZXJzIHRvIHRpZ2h0bHkgDQpjb29wZXJhdGUgZm9yIHN1Y2ggYSBzZWFt
bGVzcyBtb2JpbGl0eSBzdXBwb3J0LiANCg0KSW4gYSBzaG9ydCB0aW1lLCB5b3Ugd2lsbCBzZWUg
YW4gdXBkYXRlZCB2ZXJzaW9uIG9mICdhZHZhbmNlIERBRCcgd2hpY2ggDQphY2NlbnR1YXRlcyB0
aGUgYWJvdmUgcG9pbnQgb2YgYXJndW1lbnQuIFRoaXMgd2lsbCBiZSByZWdpc3RlcmVkIGF0ICdk
bmEgYm9mJyANCm1haWxpbmcgbGlzdC4gQWxzbywgeW91IHdpbGwgc2VlIGEgbmV3IGRyYWZ0IHdo
aWNoIGFjY291bnRzIGZvciAnQSBzdXBwbGVtZW50YXJ5DQpzY2hlbWUgb2YgbmV3IENvQSBjb25m
aWd1cmF0aW9uIGFuZCBjb25maXJtYXRpb24gaW4gRk1JUHY2Jy4gVGhpcyB3aWxsIGJlIA0KcmVn
aXN0ZXJlZCBhdCAnbWlwc2hvcCBib2YnLg0KDQotIFkuSC4gSGFuDQoNCj4gRGVhcjoNCj4gDQo+
ICAgSSBoYXZlIHJlYWQgdHdvIGltcGxlbWVudGF0aW9ucyBvbiBEQUQgaW4gbWlwNiBjaXJjdW1z
dGFuY2VzIGluIHRoZSANCj4gIHJlc3BlY3RlZCBkcmFmdHMuDQo+IA0KPiAgT25lIGlzIGNhbGxl
ZCAiYWR2YW5jZWQgREFEIiwgaW1wbGVtZW50ZWQgaW4gbWlwNiB3aGVyZSBmYXN0IGhhbmRvdmVy
IA0KPiAgaXMgc3VwcG9ydGVkLiBUaGUgY29ycmVzcG9uZGluZyBkcmFmdCBpczoNCj4gICAgICAg
ICAgICAgICAgICAgIA0KPiAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtaGFuLW1vYmlsZWlwLWFkYWQtMDEudHh0DQo+IA0KPiAgICAgVGhlIG90aGVyIGlzIGNhbGxl
ZCAib3B0aW1pc3RpYyBEQUQiLCBpbXBsZW1lbnRlZCBpbiBhbGwgbWlwNiANCj4gY2lyY3Vtc3Rh
bmNlcyBidXQgd2l0aCBwb3RlbnRpYWwgaGF6YXJkIHRvIHBhY2tldCB0cmFuc21pdCBjb25mdXNp
b24gaWYgREFEIA0KPiBmYWlscy4gVGhlIGNvcnJlc3BvbmRpbmcgZHJhZnQgaXM6DQo+ICAgICAg
ICAgICAgIA0KPiBodHRwOi8vd3d3LndhdGVyc3ByaW5ncy5vcmcvcHViL2lkL2RyYWZ0LW1vb3Jl
LWlwdjYtb3B0aW1pc3RpYy1kYWQtMDMudHh0DQo+DQo+ICAgIEl0IGxvb2tzIGxpa2Ugb3B0aW1p
c3RpYyBEQUQgZG9lc24ndCBjaGFuZ2UgbXVjaCBmcm9tIHRoZSBvcmlnaW5hbCBEQUQgDQo+IHBy
b2NlZHVyZSBzcGVjaWZpZWQgaW4gUkZDMjQ2Mi4gSSBjYW4ndCBqdWRnZSBtb3JlIGFib3V0IHRo
ZSByb2J1c3RuZXNzIGFuZCANCj4gZWZmZWN0aXZlbmVzcyBvZiBlaXRoZXIuIFdvdWxkIHlvdSBw
bGVhc2UgdGVsbCBtZSBtb3JlIGFib3V0IHRoZSANCj4gaW1wbGVtZW50YXRpb25zIG9mIGJvdGgg
bWV0aG9kcyBpbiByZWFsIG5ldHdvcmssIGFuZCB3aGljaCBvbmUgaXMgbW9yZSANCj4gd2lkZWx5
IHVzZWQ/IA0K


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



From exim@www1.ietf.org  Tue Jan  6 23:54:19 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20973
	for <mip6-archive@odin.ietf.org>; Tue, 6 Jan 2004 23:54:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae5hY-0002zr-4B
	for mip6-archive@odin.ietf.org; Tue, 06 Jan 2004 23:53:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i074rqu7011518
	for mip6-archive@odin.ietf.org; Tue, 6 Jan 2004 23:53:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae5hX-0002zh-Vc
	for mip6-web-archive@optimus.ietf.org; Tue, 06 Jan 2004 23:53:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20863
	for <mip6-web-archive@ietf.org>; Tue, 6 Jan 2004 23:53:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae5hV-0005jA-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 23:53:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae5ff-0005c8-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 23:51:56 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae5ds-0005WZ-00
	for mip6-web-archive@ietf.org; Tue, 06 Jan 2004 23:50:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae5dq-0002nz-SK; Tue, 06 Jan 2004 23:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ae5df-0002mr-N0
	for mip6@optimus.ietf.org; Tue, 06 Jan 2004 23:49:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20743
	for <mip6@ietf.org>; Tue, 6 Jan 2004 23:49:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ae5dd-0005Tx-00
	for mip6@ietf.org; Tue, 06 Jan 2004 23:49:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ae5bk-0005Lo-00
	for mip6@ietf.org; Tue, 06 Jan 2004 23:47:52 -0500
Received: from [211.225.219.76] (helo=nt6.introcom.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1Ae5Zu-0005GU-00
	for mip6@ietf.org; Tue, 06 Jan 2004 23:45:58 -0500
Received: from YounHeeHan (202.20.190.19)
	by nt6.introcom.net (211.225.219.76) with [Nmail V3.3 20021108(S)]
	for <mip6@ietf.org> from <yhhan@thinkonweb.com>;
	Wed, 07 Jan 2004 13:44:32 +0900
Message-ID: <00cf01c3d4d9$5e287f90$3d2f024b@YounHeeHan>
From: "Youn-Hee Han" <yhhan@thinkonweb.com>
To: "Youn-Hee Han" <yhhan@thinkonweb.com>, "Lee Garth" <garthdawn@hotmail.com>
Cc: <mip6@ietf.org>
References: <009d01c3d4b7$1ccc2370$3d2f024b@YounHeeHan>
Subject: Re: [Mip6] About two implementations on DAD in mip6 circumstances
Date: Wed, 7 Jan 2004 13:47:34 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: base64
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

PiBJbiBhIHNob3J0IHRpbWUsIHlvdSB3aWxsIHNlZSBhbiB1cGRhdGVkIHZlcnNpb24gb2YgJ2Fk
dmFuY2UgREFEJyB3aGljaCANCj4gYWNjZW50dWF0ZXMgdGhlIGFib3ZlIHBvaW50IG9mIGFyZ3Vt
ZW50LiBUaGlzIHdpbGwgYmUgcmVnaXN0ZXJlZCBhdCAnZG5hIGJvZicgDQo+IG1haWxpbmcgbGlz
dC4gQWxzbywgeW91IHdpbGwgc2VlIGEgbmV3IGRyYWZ0IHdoaWNoIGFjY291bnRzIGZvciAnQSBz
dXBwbGVtZW50YXJ5DQo+IHNjaGVtZSBvZiBuZXcgQ29BIGNvbmZpZ3VyYXRpb24gYW5kIGNvbmZp
cm1hdGlvbiBpbiBGTUlQdjYnLiBUaGlzIHdpbGwgYmUgDQo+IHJlZ2lzdGVyZWQgYXQgJ21pcHNo
b3AgYm9mJy4NCg0Kb29wcy4gJ21pcHNob3Agd2cnIGlzIGNvcnJlY3QuLi4u


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



From exim@www1.ietf.org  Wed Jan  7 23:39:01 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23452
	for <mip6-archive@odin.ietf.org>; Wed, 7 Jan 2004 23:39:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeRwH-0006OI-KY
	for mip6-archive@odin.ietf.org; Wed, 07 Jan 2004 23:38:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i084cX3I024560
	for mip6-archive@odin.ietf.org; Wed, 7 Jan 2004 23:38:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeRwH-0006O3-EU
	for mip6-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 23:38:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23406
	for <mip6-web-archive@ietf.org>; Wed, 7 Jan 2004 23:38:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeRwF-0007RF-00
	for mip6-web-archive@ietf.org; Wed, 07 Jan 2004 23:38:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeRuS-0007L3-00
	for mip6-web-archive@ietf.org; Wed, 07 Jan 2004 23:36:40 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeRst-0007EI-00
	for mip6-web-archive@ietf.org; Wed, 07 Jan 2004 23:35:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeRss-0005nx-Dz; Wed, 07 Jan 2004 23:35:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeRsJ-0005m5-Vr
	for mip6@optimus.ietf.org; Wed, 07 Jan 2004 23:34:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23205
	for <mip6@ietf.org>; Wed, 7 Jan 2004 23:34:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeRsH-0007AY-00
	for mip6@ietf.org; Wed, 07 Jan 2004 23:34:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeRqM-00073c-00
	for mip6@ietf.org; Wed, 07 Jan 2004 23:32:27 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeRmz-0006x2-00
	for mip6@ietf.org; Wed, 07 Jan 2004 23:28:57 -0500
Received: from pvdbergen.caia.swin.edu.au (pvdbergen.caia.swin.edu.au [136.186.229.26])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id PAA542955
	for <mip6@ietf.org>; Thu, 8 Jan 2004 15:28:16 +1100 (EST)
From: paul van den bergen <pvandenbergen@swin.edu.au>
To: mip6@ietf.org
Date: Thu, 8 Jan 2004 15:28:16 +1100
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200401081528.16738.pvandenbergen@swin.edu.au>
Content-Transfer-Encoding: 7bit
Subject: [Mip6] which implementations.
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all.

I am wondering what mobile IP implementations there are out there.

Specifically I am most interested in Open Source - *BSD and linux 
implementations for IPv4 and/or IPv6.

I am aware of KAME for *BSD/ IPv6.

If you know of a mobile IP implementation, could you drop me an email with;

Mobile IP implementation name
Operating system(s) - e.g. windows, MacOS, *BSD, linux distro
IPv4 or IPv6.
state... e.g. Commercial or Open Source; Experimental, Beta or 
Stable/Mature...

thanks.

-- 
Dr Paul van den Bergen
Centre for Advanced Internet Architectures
caia.swin.edu.au
pvandenbergen@swin.edu.au
IM:bulwynkl2002
"And some run up hill and down dale, knapping the chucky stones 
to pieces wi' hammers, like so many road makers run daft. 
They say it is to see how the world was made."
Sir Walter Scott, St. Ronan's Well 1824 


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



From exim@www1.ietf.org  Thu Jan  8 13:07:21 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04722
	for <mip6-archive@odin.ietf.org>; Thu, 8 Jan 2004 13:07:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeeYX-0005kV-Ur
	for mip6-archive@odin.ietf.org; Thu, 08 Jan 2004 13:06:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i08I6r7E022095
	for mip6-archive@odin.ietf.org; Thu, 8 Jan 2004 13:06:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeeYX-0005kI-R5
	for mip6-web-archive@optimus.ietf.org; Thu, 08 Jan 2004 13:06:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04704
	for <mip6-web-archive@ietf.org>; Thu, 8 Jan 2004 13:06:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeeYW-00041g-00
	for mip6-web-archive@ietf.org; Thu, 08 Jan 2004 13:06:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeeWb-0003vQ-00
	for mip6-web-archive@ietf.org; Thu, 08 Jan 2004 13:04:53 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeeUo-0003ox-00
	for mip6-web-archive@ietf.org; Thu, 08 Jan 2004 13:03:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeeUn-0005Yh-9o; Thu, 08 Jan 2004 13:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeeUN-0005Ww-OG
	for mip6@optimus.ietf.org; Thu, 08 Jan 2004 13:02:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04532
	for <mip6@ietf.org>; Thu, 8 Jan 2004 13:02:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeeUL-0003kj-00
	for mip6@ietf.org; Thu, 08 Jan 2004 13:02:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeeSO-0003eT-00
	for mip6@ietf.org; Thu, 08 Jan 2004 13:00:32 -0500
Received: from smtp813.mail.sc5.yahoo.com ([66.163.170.83])
	by ietf-mx with smtp (Exim 4.12)
	id 1AeeQc-0003YB-00
	for mip6@ietf.org; Thu, 08 Jan 2004 12:58:42 -0500
Received: from unknown (HELO eremmell) (elmic@sbcglobal.net@64.170.248.130 with login)
  by smtp813.mail.sc5.yahoo.com with SMTP; 8 Jan 2004 17:58:14 -0000
From: "Ed Remmell" <eremmell@elmic.com>
To: "'paul van den bergen'" <pvandenbergen@swin.edu.au>
Cc: <mip6@ietf.org>
Subject: RE: [Mip6] which implementations.
Date: Thu, 8 Jan 2004 09:58:16 -0800
Message-ID: <000401c3d610$fdd56f70$0500a8c0@eremmell>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
In-Reply-To: <200401081528.16738.pvandenbergen@swin.edu.au>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Paul -

Elmic Systems has a commercial source code implementation of Mobile
IPv4, as well as Mobile IPv6 compliant with the latest IETF drafts
(including the MIPv6 IPsec/IKE requirements). Our products are source
code implementations of Internet protocols, specifically
designed/optimized for embedded systems, and can work with or without an
RTOS. Typically, our products are either used without any RTOS (all
calls are non-blocking, and the stack runs as a single task called by a
main program "super loop"), or are fully integrated with a customer's
proprietary preemptive or non-preemptive RTOS, or are fully integrated
with a commercial off-the-shelf RTOS such as uC/OS, VxWorks, etc.

Our product datasheet for our Mobile IPv6 product is available here:
http://www.elmic.com/pdf/MobileIPv6_data.pdf

A Win32 port (binary demo) of our dual stack + applications + Mobile
IPv6 + IPsec/IKE is available for download here:
http://www.elmic.com/TreckDemo.zip

Please note that Elmic Systems is soon to be changing its name to Treck
Inc.

Thanks.
- Ed Remmell
Treck, Inc. (formerly Elmic Systems, USA)

Best of Show Winner, ESC 2003
Click on the link and take a look!
http://cmp.iconvention.com/escshowdaily/v33/index.cvn?ID=10183

> -----Original Message-----
> From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On 
> Behalf Of paul van den bergen
> Sent: Wednesday, January 07, 2004 8:28 PM
> To: mip6@ietf.org
> Subject: [Mip6] which implementations.
> 
> 
> Hi all.
> 
> I am wondering what mobile IP implementations there are out there.
> 
> Specifically I am most interested in Open Source - *BSD and linux 
> implementations for IPv4 and/or IPv6.
> 
> I am aware of KAME for *BSD/ IPv6.
> 
> If you know of a mobile IP implementation, could you drop me 
> an email with;
> 
> Mobile IP implementation name
> Operating system(s) - e.g. windows, MacOS, *BSD, linux distro
> IPv4 or IPv6.
> state... e.g. Commercial or Open Source; Experimental, Beta or 
> Stable/Mature...
> 
> thanks.
> 
> -- 
> Dr Paul van den Bergen
> Centre for Advanced Internet Architectures
> caia.swin.edu.au
> pvandenbergen@swin.edu.au
> IM:bulwynkl2002
> "And some run up hill and down dale, knapping the chucky stones 
> to pieces wi' hammers, like so many road makers run daft. 
> They say it is to see how the world was made."
> Sir Walter Scott, St. Ronan's Well 1824 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www.ietf.org/mailman/listinfo/mip6
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.542 / Virus Database: 336 - Release Date: 11/18/2003
>  
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.542 / Virus Database: 336 - Release Date: 11/18/2003
 
  


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



From exim@www1.ietf.org  Mon Jan 12 21:50:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08702
	for <mip6-archive@odin.ietf.org>; Mon, 12 Jan 2004 21:50:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgEd0-0000RG-9H
	for mip6-archive@odin.ietf.org; Mon, 12 Jan 2004 21:50:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0D2o2gS001677
	for mip6-archive@odin.ietf.org; Mon, 12 Jan 2004 21:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgEcz-0000Qm-5y
	for mip6-web-archive@optimus.ietf.org; Mon, 12 Jan 2004 21:50:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08616
	for <mip6-web-archive@ietf.org>; Mon, 12 Jan 2004 21:49:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgEcw-0005NL-00
	for mip6-web-archive@ietf.org; Mon, 12 Jan 2004 21:49:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgEb5-0005Dr-00
	for mip6-web-archive@ietf.org; Mon, 12 Jan 2004 21:48:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgEZD-00052j-00
	for mip6-web-archive@ietf.org; Mon, 12 Jan 2004 21:46:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgEZ7-0000EN-8O; Mon, 12 Jan 2004 21:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag2GM-0003NA-SK
	for mip6@optimus.ietf.org; Mon, 12 Jan 2004 08:37:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26050
	for <mip6@ietf.org>; Mon, 12 Jan 2004 08:37:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag2GG-0001Tq-00
	for mip6@ietf.org; Mon, 12 Jan 2004 08:37:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag29e-0001KF-00
	for mip6@ietf.org; Mon, 12 Jan 2004 08:30:55 -0500
Received: from myra.cc.metu.edu.tr ([144.122.199.93])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag27g-0001C4-00; Mon, 12 Jan 2004 08:28:55 -0500
Received: from kerpeten (ee-167-166.eee.metu.edu.tr [144.122.167.166])
	by myra.cc.metu.edu.tr (8.11.7/8.11.7) with SMTP id i0CDRko20637;
	Mon, 12 Jan 2004 15:27:46 +0200 (EET)
Message-ID: <05f401c3d90f$daf45b90$a6a77a90@kerpeten>
From: "Buyurman Baykal" <buyurman@metu.edu.tr>
To: <mip4@ietf.org>, <mip6@ietf.org>, <mipshop@ietf.org>
Date: Mon, 12 Jan 2004 15:27:36 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [Mip6] MedHocNet'04 Call For Papers
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.1 required=5.0 tests=MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Apologies if you receive multiple copies of this message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


                        Med-Hoc-Net 2004
                        ================
   The Third Annual Mediterranean Ad Hoc Networking Workshop

                June 27-30, 2004, Bodrum, Turkey

               http://www.medhoc04.diit.unict.it/

                        Call for Papers
                        ---------------

Ad hoc network applications are emerging continuously imposing their own
stringent constraints which cannot be fulfilled by generic approaches and
thus spur new research efforts. The aim of Med-Hoc-Net 2004 is to serve as
a platform for researchers and visionaries from academia, research labs,
and industry from all over the globe to share their ideas, views, results,
and experiences in the field of ad-hoc networking and communications.
Med-Hoc-Net 2004 will include presentations of theoretical and
experimental achievements, innovative ad-hoc systems, prototyping efforts,
case studies, and advancements in technology directly affecting ad-hoc
networking and communications infrastructures.

After Sardinia (Italy) and Mahdia (Tunisia), this year the workshop will
take place in another beautiful spot on the Mediterranean Sea: Bodrum
(Turkey) where you will find wonderful nature and amazing historical sites
close to hand. Bodrum is easy to reach via frequent flight connections
from Istanbul.

Topics of Interest:
-------------------
The papers solicited in Med-Hoc-Net 2004 cover a variety of topics
including but not limited to:

- Novel ad-hoc network architectures and applications,
- Sensor network applications and protocols,
- Implementations, testbeds, and prototypes,
- Interfacing ad-hoc systems with different networks,
- Resource discovery and management,
- Power management and control,
- Call admission and traffic shaping policies for ad-hoc networks,
- Multimedia location services,
- Self organization and network reconfiguration,
- Protocols for QoS support in ad-hoc networks,
- QoS support in Bluetooth, HomeRF, HIPERLAN, IEEE 802.11 etc.,
- MAC protocols, scheduling, and radio resource sharing in ad hoc
  networks,
- Unicast and multicast routing algorithms and protocols,
- Transport layer protocols for multi-hop networks,
- Congestion control,
- Performance evaluation of ad-hoc network protocols through
  simulations,
  analysis, and measurements,
- Security in ad-hoc networks,
- Fault tolerance and error recovery
- Signal processing algorithms (coding, compression) for ad-hoc networks

The program committee will referee all papers, and accepted papers will be
published in the conference proceedings. PAPERS OF PARTICULAR MERIT WILL
BE PUBLISHED IN AD HOC NETWORKS (ELSEVIER) JOURNAL.

Submission and Important Dates:
-------------------------------

Manuscripts must be formatted according to the IEEE double-column standard
format, except the font size, which must be 11pt. Authors should use only
standard fonts, i.e., Times Roman, Courier, Symbol, and Helvetica, or their
equivalent. The maximum length of the manuscript is 12 pages.

Papers should be submitted in pdf or ps format via email to
medhoc04@diit.unict.it according to the following timetable:

Full Paper Electronic Submission:                   March 2, 2004
Notification of Acceptance/Rejection:            May 3, 2004
Camera ready submission of full papers:        May 17, 2004
Tutorial date:                                                June 27, 2004
Conference dates:                                        June 28-30, 2004

Keynote Speakers:
-----------------

Leonard Kleinrock (UCLA, USA), and Imrich Chlamtac (UTDallas, USA).

Steering Committee:
-------------------

Khaldoun Al Agha (LRI, France), Mario Gerla (UCLA, USA), Farouk Kamoun
(ENSI, Tunisia), Giovanni Pau (UCLA, USA), and Guy Pujolle (LIP6, France).


Organization Committee:
-----------------------

General Chair:
   Ian F. Akyildiz, Georgia Institute of Technology, USA

General Vice Chair:
  Erdal Cayirci, Istanbul Technical University, TURKEY

Technical Program Chairs:
   Giacomo Morabito, University of Catania, ITALY
   Eylem Ekici, Ohio State University, USA

Tutorial Chairs:
   Francesca Cuomo, University of Rome - La Sapienza, ITALY
   Christos Douligeris, University of Piraeus, GREECE

Publicity  Chairs:
   Buyurman Baykal, Middle East Technical University, TURKEY
   Jaudelice Cavalcante de Oliveira, Drexel University, USA

Registration Chair:
   Sebnem Baydere, Yeditepe University, TURKEY

Technical Program Committee:
----------------------------

Khaldoun Al Agha, Laboratoire de Recherche en Informatique, FRANCE
Hamid Aghvami, King's College London, UK
Eitan Altman, INRIA, FRANCE
Roberto Battiti, University of Trento, ITALY
Raouf Boutaba, University of Waterloo, CANADA
Walid Dabbous, INRIA, FRANCE
Magda El Zarki, University of California at Irvine, USA
Luigi Fratta, Politecnico di Milano, ITALY
Mario Gerla, UCLA, USA
Paul J. M. Havinga, University of Twente, NETHERLANDS
Farouk Kamoun, ENSI, TUNISIA
Holger Karl, Technical University of Berlin, GERMANY
Ulf  Korner, Lund Institute of Technology, SWEDEN
Bhaskar Krishnamachari, University of Southern California, USA
Marwan Krunz, University of Arizona, USA
Albert Levi, Sabanci University, TURKEY
Janise McNair, University of Florida, USA
Lazaros Merakos, University of Athens, GREECE
Ioanis Nikolaidis, University of Alberta, CANADA
Ariel Orda, Technion, ISRAEL
Sergio Palazzo, University of Catania, ITALY
Giovanni Pau, UCLA, USA
Chiara Petrioli, University of Rome "La Sapienza", ITALY
Andreas Pitsillides, University of Cyprus, CYPRUS
Guy Pujolle, LIP6, FRANCE
Paolo Santi, CNR, ITALY
Adrian Segall, Technion, ISRAEL
Ness Shroff, Purdue University, USA
Moshe Sidi, Technion, ISRAEL
Raghupathy Sivakumar, Georgia Institute of Technology, USA
Ioannis Stavrakakis, University of Athens, GREECE
Ivan Stojmenovic, University of Ottawa, CANADA
Violet R. Syrotiuk, Arizona State University, USA
Leandros Tassiulas, University of Thessaly, GREECE
Bernhard H. Walke, Aachen University of Technology, GERMANY
Wenye Wang, North Carolina State University, USA
Michele Zorzi, University of Ferrara, ITALY

--------------------------------------------------
For more information on the workshop, please check
http://www.medhoc04.diit.unict.it/




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



From exim@www1.ietf.org  Thu Jan 15 05:41:58 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26150
	for <mip6-archive@odin.ietf.org>; Thu, 15 Jan 2004 05:41:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah4wM-0003su-VJ
	for mip6-archive@odin.ietf.org; Thu, 15 Jan 2004 05:41:31 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0FAfUeF014928
	for mip6-archive@odin.ietf.org; Thu, 15 Jan 2004 05:41:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah4wM-0003sh-QU
	for mip6-web-archive@optimus.ietf.org; Thu, 15 Jan 2004 05:41:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26138
	for <mip6-web-archive@ietf.org>; Thu, 15 Jan 2004 05:41:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah4wJ-0004lo-00
	for mip6-web-archive@ietf.org; Thu, 15 Jan 2004 05:41:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah4vd-0004jP-00
	for mip6-web-archive@ietf.org; Thu, 15 Jan 2004 05:40:45 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah4uy-0004eu-00
	for mip6-web-archive@ietf.org; Thu, 15 Jan 2004 05:40:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah4uy-0003id-CQ; Thu, 15 Jan 2004 05:40:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ah4uN-0003gn-2B
	for mip6@optimus.ietf.org; Thu, 15 Jan 2004 05:39:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25958
	for <mip6@ietf.org>; Thu, 15 Jan 2004 05:39:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah4uI-0004Zz-00
	for mip6@ietf.org; Thu, 15 Jan 2004 05:39:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ah4tQ-0004Ww-00
	for mip6@ietf.org; Thu, 15 Jan 2004 05:38:28 -0500
Received: from 94.180.32.202.ts.2iij.net ([202.32.180.94] helo=mail.64translator.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ah4sn-0004Nx-00
	for mip6@ietf.org; Thu, 15 Jan 2004 05:37:49 -0500
Received: from bahamas.64translator.com ([10.21.32.3])
	by mail.64translator.com (8.12.6p3/8.12.6) with ESMTP id i0FAbD40012702
	for <mip6@ietf.org>; Thu, 15 Jan 2004 19:37:14 +0900 (JST)
	(envelope-from h.miyata@jp.yokogawa.com)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by bahamas.64translator.com (8.12.9p2/8.12.9) with ESMTP id i0FAb8Av067446
	for <mip6@ietf.org>; Thu, 15 Jan 2004 19:37:08 +0900 (JST)
	(envelope-from h.miyata@jp.yokogawa.com)
Mime-Version: 1.0 (Apple Message framework v609)
Content-Transfer-Encoding: 7bit
Message-Id: <C547D38B-4746-11D8-BA44-000A9599E546@jp.yokogawa.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: mip6@ietf.org
From: Hiroshi MIYATA <h.miyata@jp.yokogawa.com>
Date: Thu, 15 Jan 2004 19:37:09 +0900
X-Mailer: Apple Mail (2.609)
Content-Transfer-Encoding: 7bit
Subject: [Mip6] MIPv6 Testing at Connectathon 2004
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

This is Hiroshi miyata@tahi project.
As Samita Chakrabarti announced at the 58th IETF and Mailing list,
Connectathon is scheduled on February, 2004.
MIPv6 testing will start from around 22rd.
We, TAHI/v6pc team, will coordinate interoperability test, and
will provide very powerful conformance test.

If you have not registered yet, please don't miss it.
Connectathon is comming.
http://www.connectathon.org/

I'm looking forward to seeing you at Connectathon 2004.

Best Regards,

...miyata@tahi


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



From exim@www1.ietf.org  Mon Jan 19 22:50:28 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26783
	for <mip6-archive@odin.ietf.org>; Mon, 19 Jan 2004 22:50:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aimto-00077m-D5
	for mip6-archive@odin.ietf.org; Mon, 19 Jan 2004 22:49:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K3nuMg027382
	for mip6-archive@odin.ietf.org; Mon, 19 Jan 2004 22:49:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aimtj-00077D-37
	for mip6-web-archive@optimus.ietf.org; Mon, 19 Jan 2004 22:49:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26762
	for <mip6-web-archive@ietf.org>; Mon, 19 Jan 2004 22:49:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aimta-0000YX-00
	for mip6-web-archive@ietf.org; Mon, 19 Jan 2004 22:49:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AimqI-0000Jm-00
	for mip6-web-archive@ietf.org; Mon, 19 Jan 2004 22:46:19 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AimmR-00006s-00
	for mip6-web-archive@ietf.org; Mon, 19 Jan 2004 22:42:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aimm9-0006eK-Ms; Mon, 19 Jan 2004 22:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AimlR-0006dA-4A
	for mip6@optimus.ietf.org; Mon, 19 Jan 2004 22:41:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26503
	for <mip6@ietf.org>; Mon, 19 Jan 2004 22:41:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AimlG-00000K-00
	for mip6@ietf.org; Mon, 19 Jan 2004 22:41:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AimiC-0007hQ-00
	for mip6@ietf.org; Mon, 19 Jan 2004 22:37:56 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AimgU-0007aw-00; Mon, 19 Jan 2004 22:36:10 -0500
Received: from pvdbergen.caia.swin.edu.au (pvdbergen.caia.swin.edu.au [136.186.229.26])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id OAA864336;
	Tue, 20 Jan 2004 14:35:18 +1100 (EST)
From: paul van den bergen <pvandenbergen@swin.edu.au>
To: mip6@ietf.org, <mip4@ietf.org>, <users@ipv6.org>, snap-users@kame.net,
        users@freenet6.net
Date: Tue, 20 Jan 2004 14:35:17 +1100
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200401201435.17642.pvandenbergen@swin.edu.au>
Content-Transfer-Encoding: 7bit
Subject: [Mip6] for your information - Mobile IP v4 and v6 implementations.
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all,
a few weeks ago I asked for mobile IP implementations...

just thought you'd all be interested to see what I found...


IP	Operating Systems	Name			Source and Comments
6	FreeBSD 4.9		KAME			http://www.kame.net/
	NetBSD 1.6.1						Stable, MIP code experimental, actively updated
	OpenBSD 3.3

4	NetBSD 1.1		Monarch			http://www.monarch.cs.cmu.edu/software.html
	FreeBSD 2.2.2						Rich University, old
6	INRIA's IPv6 code
	and FreeBSD 2.2.2

4	linux				Secure Mobile Net	http://www.cs.pdx.edu/research/SMN/
	FreeBSD 2.2.8, 4.6					actively updated
	4.8, 4.9, 5.2

4	Linux				Dynamics			Helsinki University of Technology
	Windows client						http://dynamics.sourceforge.net/
6	Linux				MIPL				http://www.mipl.mediapoli.com/
									GPL, stable

4	Linux				UoB-NOMAD		http://www.mobileip.org/
									SPL, based on NOMADv4

6	Linux				HMIPv6			http://www.ctie.monash.edu.au/ipv6/hmipv6.htm

4	Windows			SEGCO			http://www.secgo.com/
	Linux								commercial

4	Linux kernel 2.2.16	MosquitoNet		http://mosquitonet.stanford.edu/mip/

4	Windows			IPunplugged		http://www.ipunplugged.com/
									commercial
4	Windows			Birdstep			http://www.birdstep.com/
	embedded systems					commercial

4 & 6 embedded			Elmic Systems		http://www.elmic.com/
	OS independant						commercial, now Treck Inc.

4	Userland			MobileIP
	(platform independent)
	(linux 2.0.3)
									http://www.hpl.hp.com/personal/Jean_Tourrilhes/MobileIP/index.html
	

-- 
Dr Paul van den Bergen
Centre for Advanced Internet Architectures
caia.swin.edu.au
pvandenbergen@swin.edu.au
IM:bulwynkl2002
"And some run up hill and down dale, knapping the chucky stones 
to pieces wi' hammers, like so many road makers run daft. 
They say it is to see how the world was made."
Sir Walter Scott, St. Ronan's Well 1824 


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



From exim@www1.ietf.org  Tue Jan 20 00:56:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02607
	for <mip6-archive@odin.ietf.org>; Tue, 20 Jan 2004 00:56:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aiorr-0004ux-9q
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 00:56:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K5u3rP018897
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 00:56:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aiorr-0004ui-4N
	for mip6-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 00:56:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02577
	for <mip6-web-archive@ietf.org>; Tue, 20 Jan 2004 00:55:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aioro-0000at-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 00:56:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aioqp-0000Xp-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 00:55:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aiops-0000Vf-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 00:54:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aiops-0004oa-UV; Tue, 20 Jan 2004 00:54:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aioox-0004j3-7x
	for mip6@optimus.ietf.org; Tue, 20 Jan 2004 00:53:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02524
	for <mip6@ietf.org>; Tue, 20 Jan 2004 00:52:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aioou-0000T5-00
	for mip6@ietf.org; Tue, 20 Jan 2004 00:53:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aionv-0000PU-00
	for mip6@ietf.org; Tue, 20 Jan 2004 00:52:00 -0500
Received: from 203.141.155.85.user.ca.il24.net ([203.141.155.85] helo=doller.momose.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AionF-0000It-00; Tue, 20 Jan 2004 00:51:17 -0500
Received: from [IPv6:2001:200:182:2000:20a:95ff:fef1:1836] ([IPv6:2001:200:182:2000:20a:95ff:fef1:1836])
	(authenticated (0 bits))
	by doller.momose.org (8.12.10/8.11.4) with ESMTP id i0K5oW4N092360;
	Tue, 20 Jan 2004 14:50:35 +0900 (JST)
	(envelope-from t-momose@kame.net)
In-Reply-To: <200401201435.17642.pvandenbergen@swin.edu.au>
References: <200401201435.17642.pvandenbergen@swin.edu.au>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <8D867402-4B0C-11D8-8C16-000A959836B2@kame.net>
Content-Transfer-Encoding: 7bit
Cc: "<mip4@ietf.org>" <mip4@ietf.org>, mip6@ietf.org, users@freenet6.net,
        "<users@ipv6.org>" <users@ipv6.org>
From: Tsuyoshi MOMOSE <t-momose@kame.net>
Date: Tue, 20 Jan 2004 14:50:29 +0900
To: snap-users@kame.net
X-Mailer: Apple Mail (2.609)
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Re: (KAME-snap 8240) for your information - Mobile IP v4 and v6 implementations.
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

On 2004/01/20, at 12:35, paul van den bergen wrote:

> IP	Operating Systems	Name			Source and Comments
> 6	FreeBSD 4.9		KAME			http://www.kame.net/
> 	NetBSD 1.6.1						Stable, MIP code experimental, actively updated
> 	OpenBSD 3.3

Current KAME MIP6 doesn't support OpenBSD yet.
I'm now working to port it.


---
MOMOSE Tsuyoshi
NEC Corporation
KAME Project		http://www.kame.net/
Nautilus Project	http://www.nautilus6.org/


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



From exim@www1.ietf.org  Tue Jan 20 05:07:38 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21700
	for <mip6-archive@odin.ietf.org>; Tue, 20 Jan 2004 05:07:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aisms-00016d-L6
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 05:07:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KA7A9t004238
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 05:07:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aismq-000163-Fk
	for mip6-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 05:07:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21585
	for <mip6-web-archive@ietf.org>; Tue, 20 Jan 2004 05:07:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aismn-0003ps-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 05:07:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aisld-0003gR-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 05:05:54 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aisks-0003X5-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 05:05:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aiskp-0000pq-4t; Tue, 20 Jan 2004 05:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiskC-0000pG-9A
	for mip6@optimus.ietf.org; Tue, 20 Jan 2004 05:04:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21281
	for <mip6@ietf.org>; Tue, 20 Jan 2004 05:04:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aisk9-0003WA-00
	for mip6@ietf.org; Tue, 20 Jan 2004 05:04:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aisj8-0003Sc-00
	for mip6@ietf.org; Tue, 20 Jan 2004 05:03:19 -0500
Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aisis-0003Pd-00; Tue, 20 Jan 2004 05:03:02 -0500
Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com)
	by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian))
	id 1Aisio-00024j-00; Tue, 20 Jan 2004 11:02:58 +0100
Date: Tue, 20 Jan 2004 11:02:49 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
To: paul van den bergen <pvandenbergen@swin.edu.au>
Cc: mip6@ietf.org, <mip4@ietf.org>, <users@ipv6.org>, snap-users@kame.net,
        users@freenet6.net
Message-Id: <20040120110249.461dfeea.henrik@levkowetz.com>
In-Reply-To: <200401201435.17642.pvandenbergen@swin.edu.au>
References: <200401201435.17642.pvandenbergen@swin.edu.au>
X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6
 implementations.
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello Paul,

Tuesday 20 January 2004, paul van den bergen wrote:
> Hi all,
> a few weeks ago I asked for mobile IP implementations...
> 
> just thought you'd all be interested to see what I found...

<snip table of implementations>

Useful and interesting indeed.  I've taken the liberty of duplicating
the information here:

 <http://www.mip4.org/2004/mip-implementations.html>


	Thanks,
		Henrik

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



From exim@www1.ietf.org  Tue Jan 20 16:40:08 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26664
	for <mip6-archive@odin.ietf.org>; Tue, 20 Jan 2004 16:40:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj3b1-0003OR-VN
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 16:39:40 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KLddl9013039
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 16:39:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj3b1-0003OE-Mg
	for mip6-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 16:39:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26584
	for <mip6-web-archive@ietf.org>; Tue, 20 Jan 2004 16:39:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj3az-0006yu-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 16:39:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aj3a4-0006ph-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 16:38:41 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj3ZV-0006mf-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 16:38:05 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Aj3Uf-0005X8-LH
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 16:33:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj3Ub-0002m8-V4; Tue, 20 Jan 2004 16:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj3UG-0002fw-FJ
	for mip6@optimus.ietf.org; Tue, 20 Jan 2004 16:32:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26395
	for <mip6@ietf.org>; Tue, 20 Jan 2004 16:32:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj3UE-0006c7-00
	for mip6@ietf.org; Tue, 20 Jan 2004 16:32:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aj3TL-0006ZZ-00
	for mip6@ietf.org; Tue, 20 Jan 2004 16:31:43 -0500
Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj3Ss-0006W5-00; Tue, 20 Jan 2004 16:31:15 -0500
Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com)
	by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian))
	id 1Aj3Sk-0002Jy-00; Tue, 20 Jan 2004 22:31:06 +0100
Date: Tue, 20 Jan 2004 22:31:01 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
To: qiangieee@yahoo.com
Cc: mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net,
        users@freenet6.net
Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6
 implementations.
Message-Id: <20040120223101.1634dc64.henrik@levkowetz.com>
In-Reply-To: <20040120182737.20338.qmail@web12823.mail.yahoo.com>
References: <20040120110249.461dfeea.henrik@levkowetz.com>
	<20040120182737.20338.qmail@web12823.mail.yahoo.com>
X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Qiang

Tuesday 20 January 2004, Qiang Zhang wrote:
> I know there are several other commercials, such as
> ecutel.com

As more implementations are mentioned on the mailing list, I'll put them
into the table at <http://www.mip4.org/2004/mip-implementations.html>.

I would need a bit more information to do so, though.  Would you be kind
enough to provide / IP version / OS / Name / URL / status /  for the
implementations you know of?

	Henrik

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



From exim@www1.ietf.org  Tue Jan 20 19:57:23 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04631
	for <mip6-archive@odin.ietf.org>; Tue, 20 Jan 2004 19:57:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj6fq-0003zF-TJ
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 19:56:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0L0uoEB015324
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 19:56:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj6fq-0003z5-O8
	for mip6-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 19:56:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04615
	for <mip6-web-archive@ietf.org>; Tue, 20 Jan 2004 19:56:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj6fo-00036P-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 19:56:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aj6ex-00032I-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 19:55:56 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj6e8-0002wi-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 19:55:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj6e7-0003kw-FN; Tue, 20 Jan 2004 19:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj6dp-0003jz-Eq
	for mip6@optimus.ietf.org; Tue, 20 Jan 2004 19:54:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04385
	for <mip6@ietf.org>; Tue, 20 Jan 2004 19:54:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj6dn-0002tc-00
	for mip6@ietf.org; Tue, 20 Jan 2004 19:54:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aj6co-0002kK-00
	for mip6@ietf.org; Tue, 20 Jan 2004 19:53:43 -0500
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj6bn-0002Yl-00; Tue, 20 Jan 2004 19:52:39 -0500
Received: from pvdbergen.caia.swin.edu.au (pvdbergen.caia.swin.edu.au [136.186.229.26])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id LAA985290;
	Wed, 21 Jan 2004 11:51:23 +1100 (EST)
From: paul van den bergen <pvandenbergen@swin.edu.au>
To: Henrik Levkowetz <henrik@levkowetz.com>, qiangieee@yahoo.com
Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6 implementations.
Date: Wed, 21 Jan 2004 11:51:22 +1100
User-Agent: KMail/1.5
Cc: mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net,
        users@freenet6.net
References: <20040120110249.461dfeea.henrik@levkowetz.com> <20040120182737.20338.qmail@web12823.mail.yahoo.com> <20040120223101.1634dc64.henrik@levkowetz.com>
In-Reply-To: <20040120223101.1634dc64.henrik@levkowetz.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200401211151.23317.pvandenbergen@swin.edu.au>
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hey Henrik,

thanks for that! I'm glad this information has a home! (I might steal your 
page and duplicate it at wikipedia too, if I get a moment.)

FYI, I am winding up here this week, so this email address will disappear. but 
anyone who wants to talk to the people who will no doubt follow after me (I 
speak of the researcher who is greater than me, whos very operational 
parameters I am unworthy to even calculate) can go to www.caia.swin.edu.au 
and have a look around there... :-)




On Wed, 21 Jan 2004 08:31 am, Henrik Levkowetz wrote:
> Hi Qiang
>
> Tuesday 20 January 2004, Qiang Zhang wrote:
> > I know there are several other commercials, such as
> > ecutel.com
>
> As more implementations are mentioned on the mailing list, I'll put them
> into the table at <http://www.mip4.org/2004/mip-implementations.html>.
>
> I would need a bit more information to do so, though.  Would you be kind
> enough to provide / IP version / OS / Name / URL / status /  for the
> implementations you know of?
>
> 	Henrik
IP	OS				Name	URL				Comments
4	Windows client/server	Viatores	www.ecutel.com/		commercial
	Linux server




-- 
Dr Paul van den Bergen
Centre for Advanced Internet Architectures
caia.swin.edu.au
pvandenbergen@swin.edu.au
IM:bulwynkl2002
"And some run up hill and down dale, knapping the chucky stones 
to pieces wi' hammers, like so many road makers run daft. 
They say it is to see how the world was made."
Sir Walter Scott, St. Ronan's Well 1824 


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



From exim@www1.ietf.org  Tue Jan 20 23:43:20 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10046
	for <mip6-archive@odin.ietf.org>; Tue, 20 Jan 2004 23:43:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjACZ-0007qQ-Bh
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 23:42:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0L4gpPA030148
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 23:42:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjACY-0007pw-Ne
	for mip6-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 23:42:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10040
	for <mip6-web-archive@ietf.org>; Tue, 20 Jan 2004 23:42:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjACW-0005OB-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 23:42:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjABZ-0005MY-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 23:41:50 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjAAr-0005Kd-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 23:41:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjAAp-0007fo-KF; Tue, 20 Jan 2004 23:41:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aj0dv-0007GO-Mi
	for mip6@optimus.ietf.org; Tue, 20 Jan 2004 13:30:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15245
	for <mip6@ietf.org>; Tue, 20 Jan 2004 13:30:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aj0dt-0002MD-00
	for mip6@ietf.org; Tue, 20 Jan 2004 13:30:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aj0cw-0002Ka-00
	for mip6@ietf.org; Tue, 20 Jan 2004 13:29:26 -0500
Received: from web12823.mail.yahoo.com ([216.136.174.204])
	by ietf-mx with smtp (Exim 4.12)
	id 1Aj0cA-0002JH-00
	for mip6@ietf.org; Tue, 20 Jan 2004 13:28:38 -0500
Message-ID: <20040120182737.20338.qmail@web12823.mail.yahoo.com>
Received: from [66.208.42.117] by web12823.mail.yahoo.com via HTTP; Tue, 20 Jan 2004 10:27:37 PST
Date: Tue, 20 Jan 2004 10:27:37 -0800 (PST)
From: Qiang zhang <qiangieee@yahoo.com>
Reply-To: qiangieee@yahoo.com
Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6 implementations.
To: paul van den bergen <pvandenbergen@swin.edu.au>
Cc: mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net,
        users@freenet6.net
In-Reply-To: <20040120110249.461dfeea.henrik@levkowetz.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Dr. Paul Bergen,

I know there are several other commercials, such as
ecutel.com

Qiang
--- Henrik Levkowetz <henrik@levkowetz.com> wrote:
> Hello Paul,
> 
> Tuesday 20 January 2004, paul van den bergen wrote:
> > Hi all,
> > a few weeks ago I asked for mobile IP
> implementations...
> > 
> > just thought you'd all be interested to see what I
> found...
> 
> <snip table of implementations>
> 
> Useful and interesting indeed.  I've taken the
> liberty of duplicating
> the information here:
> 
>  <http://www.mip4.org/2004/mip-implementations.html>
> 
> 
> 	Thanks,
> 		Henrik
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www.ietf.org/mailman/listinfo/mip6
> 


__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

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



From exim@www1.ietf.org  Tue Jan 20 23:43:20 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10048
	for <mip6-archive@odin.ietf.org>; Tue, 20 Jan 2004 23:43:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjACZ-0007q9-8m
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 23:42:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0L4gpGu030133
	for mip6-archive@odin.ietf.org; Tue, 20 Jan 2004 23:42:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjACY-0007pv-0X
	for mip6-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 23:42:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10037
	for <mip6-web-archive@ietf.org>; Tue, 20 Jan 2004 23:42:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjACV-0005O5-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 23:42:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjABY-0005MQ-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 23:41:49 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjAAr-0005Kc-00
	for mip6-web-archive@ietf.org; Tue, 20 Jan 2004 23:41:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjAAp-0007fe-6F; Tue, 20 Jan 2004 23:41:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aiuuf-0000bh-Qk
	for mip6@optimus.ietf.org; Tue, 20 Jan 2004 07:23:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26288
	for <mip6@ietf.org>; Tue, 20 Jan 2004 07:23:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aiuuf-0003RB-00
	for mip6@ietf.org; Tue, 20 Jan 2004 07:23:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aiutm-0003OC-00
	for mip6@ietf.org; Tue, 20 Jan 2004 07:22:27 -0500
Received: from gaia.cs.uoi.gr ([195.130.121.201])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aiusp-0003IL-00; Tue, 20 Jan 2004 07:21:27 -0500
Received: from zeus.cs.uoi.gr (zeus.cs.uoi.gr [195.130.121.11])
	by gaia.cs.uoi.gr (8.12.10/8.12.10) with ESMTP id i0KCKrAe009307;
	Tue, 20 Jan 2004 14:20:53 +0200 (EET)
	(envelope-from faturu@zeus.cs.uoi.gr)
Received: from io.cs.uoi.gr (io [195.251.195.19])
	by zeus.cs.uoi.gr (8.12.9+Sun/8.12.5) with ESMTP id i0KCKqVN022487;
	Tue, 20 Jan 2004 14:20:52 +0200 (EET)
Received: from localhost (faturu@localhost)
	by io.cs.uoi.gr (8.11.6+Sun/8.10.2) with SMTP id i0KCKqk01599;
	Tue, 20 Jan 2004 14:20:52 +0200 (EET)
Date: Tue, 20 Jan 2004 14:20:52 +0200 (EET)
From: Panagiota Fatourou <faturu@zeus.cs.uoi.gr>
To: mip6@ietf.org, mip4@ietf.org, mipshop@ietf.org
cc: kutten@ie.technion.ac.il, victor.luchangco@sun.com,
        Fatourou Panagiota <faturu@io.cs.uoi.gr>
Message-ID: <Pine.GSO.3.96.1040120142023.1345A-100000@io>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: ClamAV version 'clamd / ClamAV version devel-20031127', clamav-milter version '0.60n'
Subject: [Mip6] PODC 2004: Call for Papers
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Please accept our apologies if you receive multiple copies.
We would appreciate it if you distribute the cfp to your collegues
and post it on the bulletin boards of your Department.

==============================================================================

                            CALL FOR PAPERS

          Twenty-third Annual ACM SIGACT-SIGOPS Symposium on
                  PRINCIPLES OF DISTRIBUTED COMPUTING
                              (PODC 2004)

                            July 25-28, 2004
                    St. John's, Newfoundland, Canada

                     http://www.podc.org/podc2004/

Submission deadline:       February 15, 2004
Acceptance notification:         May 9, 2004
Camera-ready copy due:          May 29, 2004

PODC 2004 is colocated with the Workshop on Concurrency and
Synchronization in Java Programs; joint submission is encouraged.


How to submit
=============

Electronic submissions are strongly encouraged; information on how
to submit electronically will be available at

    http://www.podc.org/podc2004/.

Authors unable to submit electronically should contact the program
chair, Shay Kutten (kutten@ie.technion.ac.il), to receive
instructions.

PODC does not allow anonymous submissions. Submissions are considered
confidential, and are only distributed for the purposes of evaluating
whether they are appropriate for presentation at PODC. It is expected
that at least one of the authors of each accepted paper attends the
conference and presents the paper.


SCOPE
=====

PODC continues to broaden the conference, and solicits papers on all
areas of distributed systems.  We encourage submissions dealing with
any aspect of distributed computing, including theory and practice,
systems, design, specification, verification, implementation,
application, and properties of distributed systems.  The common goal
is to shed light on the principles of distributed computing.

This year, we have a special track to emphasize the area of Algorithms
and Data Structures for the Internet.  We also continue to actively
seek papers in areas emphasized in recent PODCs, such as the
implementation, analysis, evaluation, and deployment of real systems
(from PODC 2002), and the intersection of security and distributed
computing (from PODC 2003).  We generally favor work that explores new
territory or reflects on experience with practical applications of the
community's knowledge.

Topics of interest include, but are not limited to, the following
subjects in networks and distributed systems:
 - Internet algorithms and data structures
 - Distributed computing issues in the Internet and the Web
 - Distributed algorithms, correctness, complexity, application
 - Synchronization: hardware, software, algorithms, architecture, practice
 - Cryptographic and security protocols, security of distributed systems
 - Distributed middleware platforms, operating systems, databases
 - Mobile computing, ad hoc and sensor networks
 - P2P computing, overlay networks
 - High-performance distributed computing and the computational grid
 - Multiprocessor/cluster architectures, algorithms, experience
 - Agents' cooperation, mobile agents
 - Location-aware distributed computing, distributed robots' cooperation
 - Networking: architecture, design, control, services, applications
 - Communication network protocols
 - Transport and application layer protocols, routing, scheduling,
   resource allocation
 - Shared memory
 - Algorithmic mechanism design
 - Fault tolerance, availability, self stabilization
 - Specification, semantics, and verification
 - Distributed data management and search

Conference presentations will have three formats:

REGULAR PRESENTATIONS (about 20-25 minutes, depending on the time
constraints of the conference), accompanied by papers of up to 10
pages in the proceedings, are intended for contributions reporting on
original research, submitted exclusively to this conference (or
jointly to this conference and to the Workshop on Concurrency and
Synchronization in Java Programs). Submission to a journal is allowed
(but papers already published in a journal should not be submitted).

BRIEF ANNOUNCEMENTS (up to 10 minutes, depending on the time
constraints of the conference), accompanied by one-page abstracts in
the proceedings (each marked as brief announcement), are encouraged
as an opportunity for conference participants to be exposed to work in
progress or published in other conferences.  Links to longer versions
expanding the brief announcements will be collected at a web site.

POSTERS AND DEMONSTRATIONS include graphic material and demo prepared
by authors for exhibitions.  Time during the conference will be
allotted for participants to inspect the posters, and for authors to
be available to answer questions.


PROGRAM COMMITTEE
=================

James Aspnes                    Yale
Gregory Chockler                MIT
Edith Cohen                     AT&T Labs
Panagiota Fatourou              U. Ioannina
Joan Feigenbaum                 Yale
Christof Fetzer                 AT&T Labs
Jaap-Henk Hoepman               U. Nijmegen
David Karger                    MIT
Idit Keidar                     Technion
Shay Kutten, Chair              Technion
Victor Luchangco                Sun Labs
Keith Marzullo                  UCSD
Toshimitsu Masuzawa             Osaka U.
Michael Mitzenmacher,           Harvard U.
      Special Track Chair
Rafail Ostrovsky                UCLA
Boaz Patt-Shamir                HP Labs, Tel-Aviv U.
Michel Raynal                   U. Rennes
Alex Shvartsman                 U. Connecticut
Gadi Taubenfeld                 IDC
Mark Tuttle                     HP Labs
Roger Wattenhofer               ETHZ

SUBMISSIONS FORMAT
==================

All electronic submissions must be in Postscript or PDF format, and
capable of being previewed by Ghostview.  Please include the following
information on the cover page (1) contact person's name, phone, fax,
email and complete postal mail address, (2) title of paper, (3) names
and affliations of all authors, (4) a brief abstract, (5) keywords,
and (6) the number of pages.  In addition, please indicate in boldface
below the brief abstract whether the paper is also submitted to the
Workshop on Concurrency and Synchronization in Java Programs, whether
any author is a member of the program committee, and, for a regular
presentation, whether it is eligible for the best student paper award
(see details below), and whether it should be considered a brief
announcement (if not accepted as a regular presentation).

It is recommended that each submission begins with a succinct statement
of the problem, summary of the main results, and a brief explanation
of their significance, all suitable for a nonspecialist.  Technical
development of the work, directed to the specialist, should follow.

A submission for REGULAR PRESENTATION must be no longer than 10 pages
on letter-size paper using at least 11-point font (4,500 words).
Additional necessary details may be included in a clearly marked
appendix, which will be read at the discretion of the program
committee.

A submission for BRIEF ANNOUNCEMENT must be no longer than 3 pages on
letter-size paper using at least 11-point font.  If requested by the
authors (by indicating on the cover page), a submission that is not
selected for regular presentation will also be considered for the
brief announcement format.  Such a request will not affect
consideration of the paper for regular presentation.

More details about submissions for POSTERS AND DEMONSTATIONS will
appear on the PODC web site.

Submissions deviating significantly from these guidelines will be
rejected without consideration of their merits.  Late submissions will
not be read or considered.


BEST STUDENT PAPER AWARD
========================

A prize will be given to the best student paper.  A paper is eligible
if at least one author is a full-time student at the time of
submission, and the contribution of the student is significant.  This
must be noted on the cover page.  The program committee may decline to
make the award or split it.









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



From exim@www1.ietf.org  Thu Jan 22 12:44:26 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01015
	for <mip6-archive@odin.ietf.org>; Thu, 22 Jan 2004 12:44:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajis2-0001fQ-F7
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 12:43:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0MHhw7f006402
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 12:43:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajis2-0001fA-7Q
	for mip6-web-archive@optimus.ietf.org; Thu, 22 Jan 2004 12:43:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00961
	for <mip6-web-archive@ietf.org>; Thu, 22 Jan 2004 12:43:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajis0-0000GS-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 12:43:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajiox-00005U-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 12:40:48 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajild-0007gl-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 12:37:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjilI-0000qM-Tz; Thu, 22 Jan 2004 12:37:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjikE-0000oB-UB
	for mip6@optimus.ietf.org; Thu, 22 Jan 2004 12:36:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00597
	for <mip6@ietf.org>; Thu, 22 Jan 2004 12:35:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajik8-0007bD-00
	for mip6@ietf.org; Thu, 22 Jan 2004 12:35:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajig6-0007O5-00
	for mip6@ietf.org; Thu, 22 Jan 2004 12:31:39 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajicw-0007AE-00; Thu, 22 Jan 2004 12:28:22 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 22 Jan 2004 09:31:53 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0MHRVff007001;
	Thu, 22 Jan 2004 09:27:31 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn3-722.cisco.com [10.21.66.210])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id APN31133;
	Thu, 22 Jan 2004 09:27:30 -0800 (PST)
Message-Id: <4.3.2.7.2.20040122092132.0256a9b8@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 22 Jan 2004 09:27:29 -0800
To: Henrik Levkowetz <henrik@levkowetz.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and
  v6 implementations.
Cc: qiangieee@yahoo.com, mip6@ietf.org, mip4@ietf.org, users@ipv6.org,
        snap-users@kame.net, users@freenet6.net
In-Reply-To: <20040120223101.1634dc64.henrik@levkowetz.com>
References: <20040120182737.20338.qmail@web12823.mail.yahoo.com>
 <20040120110249.461dfeea.henrik@levkowetz.com>
 <20040120182737.20338.qmail@web12823.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi Henrik.

Here's Cisco's info:

IP: 4 & 6
OS: Cisco IOS
Name: Cisco Systems (URL: http://www.cisco.com/go/mobile_ip)
Comments: MIPv4 commercial, MIPv6 technology preview

Kent

At 10:31 PM 1/20/2004 +0100, Henrik Levkowetz wrote:

>As more implementations are mentioned on the mailing list, I'll put them
>into the table at <http://www.mip4.org/2004/mip-implementations.html>.
>
>I would need a bit more information to do so, though.  Would you be kind
>enough to provide / IP version / OS / Name / URL / status /  for the
>implementations you know of?
>
>         Henrik
>
>--
>Mip4 mailing list
>Mip4@ietf.org
>https://www.ietf.org/mailman/listinfo/mip4


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



From exim@www1.ietf.org  Thu Jan 22 19:29:23 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21450
	for <mip6-archive@odin.ietf.org>; Thu, 22 Jan 2004 19:29:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjpBw-0006m8-6y
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 19:28:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0N0SuHV026040
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 19:28:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjpBw-0006lv-3U
	for mip6-web-archive@optimus.ietf.org; Thu, 22 Jan 2004 19:28:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21445
	for <mip6-web-archive@ietf.org>; Thu, 22 Jan 2004 19:28:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjpBp-0000MQ-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 19:28:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajp9u-0000Ia-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 19:26:50 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajp6a-0000Dg-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 19:23:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajp6D-0006EW-QF; Thu, 22 Jan 2004 19:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajp5A-0006Bw-9Z
	for mip6@optimus.ietf.org; Thu, 22 Jan 2004 19:22:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21309
	for <mip6@ietf.org>; Thu, 22 Jan 2004 19:21:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajp53-0000A8-00
	for mip6@ietf.org; Thu, 22 Jan 2004 19:21:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajp2S-00006q-00
	for mip6@ietf.org; Thu, 22 Jan 2004 19:19:10 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajp0E-00000B-00
	for mip6@ietf.org; Thu, 22 Jan 2004 19:16:50 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id i0N0FqEq014389
	for <mip6@ietf.org>; Thu, 22 Jan 2004 18:15:52 -0600 (CST)
Received: by eamrcnt750.exu.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <CR56425Y>; Thu, 22 Jan 2004 18:15:20 -0600
Received: from [142.133.72.18] (142.133.72.18 [142.133.72.18]) by EAMMLEX034.lmc.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XHG6X59B; Thu, 22 Jan 2004 19:15:33 -0500
Date: Thu, 22 Jan 2004 19:12:34 -0500 (EST)
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
X-X-Sender: lmcsukr@localhost.localdomain
Reply-To: Suresh Krishnan <suresh.krishnan@ericsson.ca>
To: mip6@ietf.org
Message-ID: <Pine.LNX.4.44.0401221857060.20261-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Mip6] Vulnerability of MIPv6 in RO mode
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi folks,
	I was thinking of possible attacks on MIPv6 RO mode and I found 
one, which I think may be interesting. I have read the ro security 
design document and this has not been covered. 

Let's say there is a mobile node MN1 which has a session with a server CN. 
The mobile node wants to kill another mobile node MN2 by flooding it with 
data. In my scenario MN1 has the capability to sniff packets going to 
MN2 (say by virtue of being on the same broadcast network as MN2, or by 
being on the direct path from MN2 to CN). The MN1 sends a HOTI and COTI to 
the CN that its new Care of address is CoA(MN2). The MN1 gets the HOT 
through its home agent and gets the CoT by sniffing the packet sent to 
MN2. It can now make the BU and succesfully complete the handover. It can 
initiate a high rate data stream from the server before it does this so 
that MN2 is flooded with data it does not need. Am I missing something 
here or is this a legitimate threat? 

Regards
Suresh
 

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



From exim@www1.ietf.org  Thu Jan 22 19:57:00 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22272
	for <mip6-archive@odin.ietf.org>; Thu, 22 Jan 2004 19:56:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajpcc-0000Hq-OC
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 19:56:31 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0N0uU5l001096
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 19:56:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajpcc-0000Hb-J6
	for mip6-web-archive@optimus.ietf.org; Thu, 22 Jan 2004 19:56:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22267
	for <mip6-web-archive@ietf.org>; Thu, 22 Jan 2004 19:56:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajpca-0001QK-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 19:56:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajpbg-0001Nm-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 19:55:32 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjpbH-0001K7-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 19:55:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjpbB-00007M-MR; Thu, 22 Jan 2004 19:55:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjpaN-0008Vu-A5
	for mip6@optimus.ietf.org; Thu, 22 Jan 2004 19:54:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22176
	for <mip6@ietf.org>; Thu, 22 Jan 2004 19:54:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjpaL-0001Ho-00
	for mip6@ietf.org; Thu, 22 Jan 2004 19:54:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjpZN-0001FI-00
	for mip6@ietf.org; Thu, 22 Jan 2004 19:53:10 -0500
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjpYQ-0001DC-00
	for mip6@ietf.org; Thu, 22 Jan 2004 19:52:12 -0500
Received: from localhost ([130.194.13.85]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01L5QJMZI9O4902RDL@vaxh.its.monash.edu.au> for mip6@ietf.org;
 Fri, 23 Jan 2004 11:43:55 +1100
Received: from broink.its.monash.edu.au
 (localhost.its.monash.edu.au [127.0.0.1])	by localhost (Postfix)
 with ESMTP	id DC838158002; Fri, 23 Jan 2004 11:43:54 +1100 (EST)
Received: from eng.monash.edu.au (knuth.eng.monash.edu.au [130.194.252.110])
	by broink.its.monash.edu.au (Postfix) with ESMTP	id C1E43120002; Fri,
 23 Jan 2004 11:43:54 +1100 (EST)
Date: Fri, 23 Jan 2004 11:43:54 +1100
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [Mip6] Vulnerability of MIPv6 in RO mode
To: Suresh Krishnan <suresh.krishnan@ericsson.ca>
Cc: mip6@ietf.org
Reply-to: greg.daley@eng.monash.edu.au
Message-id: <40106E4A.2040809@eng.monash.edu.au>
Organization: Monash University
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
X-Accept-Language: en, en-us
References: <Pine.LNX.4.44.0401221857060.20261-100000@localhost.localdomain>
Content-Transfer-Encoding: 7BIT
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Hi Suresh,

Suresh Krishnan wrote:
> Hi folks,
> 	I was thinking of possible attacks on MIPv6 RO mode and I found 
> one, which I think may be interesting. I have read the ro security 
> design document and this has not been covered. 
> 
> Let's say there is a mobile node MN1 which has a session with a server CN. 
> The mobile node wants to kill another mobile node MN2 by flooding it with 
> data. In my scenario MN1 has the capability to sniff packets going to 
> MN2 (say by virtue of being on the same broadcast network as MN2, or by 
> being on the direct path from MN2 to CN). The MN1 sends a HOTI and COTI to 
> the CN that its new Care of address is CoA(MN2). The MN1 gets the HOT 
> through its home agent and gets the CoT by sniffing the packet sent to 
> MN2. It can now make the BU and succesfully complete the handover. It can 
> initiate a high rate data stream from the server before it does this so 
> that MN2 is flooded with data it does not need. Am I missing something 
> here or is this a legitimate threat? 

I'm not sure if this specific attack has been defined,
but it is well known that return-routability tests in MIPv6
are not well protected from devices which are on the path to the
MN(2).

I hope this helps,

Greg


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



From exim@www1.ietf.org  Thu Jan 22 20:18:02 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22778
	for <mip6-archive@odin.ietf.org>; Thu, 22 Jan 2004 20:18:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajpx0-0001ru-BC
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 20:17:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0N1HYOC007176
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 20:17:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajpx0-0001rf-71
	for mip6-web-archive@optimus.ietf.org; Thu, 22 Jan 2004 20:17:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22764
	for <mip6-web-archive@ietf.org>; Thu, 22 Jan 2004 20:17:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajpwt-00028n-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 20:17:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajpu2-00022T-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 20:14:32 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajpqz-0001uu-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 20:11:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajpqf-0001HS-VX; Thu, 22 Jan 2004 20:11:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ajpph-0001GA-B5
	for mip6@optimus.ietf.org; Thu, 22 Jan 2004 20:10:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22543
	for <mip6@ietf.org>; Thu, 22 Jan 2004 20:09:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajppa-0001ru-00
	for mip6@ietf.org; Thu, 22 Jan 2004 20:09:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajpmd-0001l0-00
	for mip6@ietf.org; Thu, 22 Jan 2004 20:06:52 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjpkQ-0001ew-00
	for mip6@ietf.org; Thu, 22 Jan 2004 20:04:34 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id i0N13nEq024553;
	Thu, 22 Jan 2004 19:03:49 -0600 (CST)
Received: by eamrcnt750.exu.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <CR564MQJ>; Thu, 22 Jan 2004 19:03:34 -0600
Received: from [142.133.72.18] (142.133.72.18 [142.133.72.18]) by EAMMLEX034.lmc.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XHG6X6G4; Thu, 22 Jan 2004 20:03:48 -0500
Date: Thu, 22 Jan 2004 20:00:50 -0500 (EST)
From: Suresh Krishnan <suresh.krishnan@ericsson.ca>
X-X-Sender: lmcsukr@localhost.localdomain
Reply-To: Suresh Krishnan <suresh.krishnan@ericsson.ca>
To: Greg Daley <greg.daley@eng.monash.edu.au>
cc: mip6@ietf.org
Subject: Re: [Mip6] Vulnerability of MIPv6 in RO mode
In-Reply-To: <40106E4A.2040809@eng.monash.edu.au>
Message-ID: <Pine.LNX.4.44.0401221956200.28828-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60

On Fri, 23 Jan 2004, Greg Daley wrote:
>I'm not sure if this specific attack has been defined,
>but it is well known that return-routability tests in MIPv6
>are not well protected from devices which are on the path to the
>MN(2).

Hi Greg,
  Thanks for the quick reply. I would have thought so except for the 
following statement in the RO security design

+   The binding update authorization mechanism used in the MIPv6 security
+   design is primarily intended to mitigate this threat, and to limit
+   the location of attackers to the path between a correspondent node
+   and the home agent.

which implies the insecurity is the the path between the CN and the 
<B>HA</B> rather than the path between the CN and MN.

Regards
Suresh

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



From exim@www1.ietf.org  Thu Jan 22 20:53:43 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24491
	for <mip6-archive@odin.ietf.org>; Thu, 22 Jan 2004 20:53:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjqVX-0004gi-9N
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 20:53:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0N1rF5h018014
	for mip6-archive@odin.ietf.org; Thu, 22 Jan 2004 20:53:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjqVX-0004gT-3x
	for mip6-web-archive@optimus.ietf.org; Thu, 22 Jan 2004 20:53:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24485
	for <mip6-web-archive@ietf.org>; Thu, 22 Jan 2004 20:53:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjqVU-0004Oa-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 20:53:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjqUZ-0004Nt-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 20:52:16 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjqUJ-0004N4-00
	for mip6-web-archive@ietf.org; Thu, 22 Jan 2004 20:51:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjqUK-0004Xp-R4; Thu, 22 Jan 2004 20:52:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjqTa-0004XP-3q
	for mip6@optimus.ietf.org; Thu, 22 Jan 2004 20:51:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24463
	for <mip6@ietf.org>; Thu, 22 Jan 2004 20:51:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjqTX-0004Lu-00
	for mip6@ietf.org; Thu, 22 Jan 2004 20:51:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjqSe-0004LO-00
	for mip6@ietf.org; Thu, 22 Jan 2004 20:50:16 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjqS9-0004KU-00
	for mip6@ietf.org; Thu, 22 Jan 2004 20:49:45 -0500
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id i0N1neqV018170;
	Thu, 22 Jan 2004 18:49:41 -0700 (MST)
Received: from sun.com (vpn-129-156-96-16.EMEA.Sun.COM [129.156.96.16])
	by bebop.France.Sun.COM (8.11.7p1+Sun/8.10.2/ENSMAIL,v2.2) with ESMTP id i0N1ncQ21196;
	Fri, 23 Jan 2004 02:49:39 +0100 (MET)
Message-ID: <40107D21.9080209@sun.com>
Date: Fri, 23 Jan 2004 02:47:13 +0100
From: gabriel montenegro <gab@sun.com>
Reply-To: gab@sun.com
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.6a) Gecko/20031029
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.ca>
CC: Greg Daley <greg.daley@eng.monash.edu.au>, mip6@ietf.org
Subject: Re: [Mip6] Vulnerability of MIPv6 in RO mode
References: <Pine.LNX.4.44.0401221956200.28828-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.44.0401221956200.28828-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Suresh Krishnan wrote:
> On Fri, 23 Jan 2004, Greg Daley wrote:
> 
>>I'm not sure if this specific attack has been defined,
>>but it is well known that return-routability tests in MIPv6
>>are not well protected from devices which are on the path to the
>>MN(2).

Yes. This is mentioned in 4.1.2 (Care-of-Address check):

    The Care-of Test traverses only one leg, directly from the
    correspondent node to the mobile node. It remains unprotected all
    along the way, making it vulnerable to eavesdroppers near the
    correspondent node, on the path from the correspondent node to the
    mobile node, or near the mobile node.

> Hi Greg,
>   Thanks for the quick reply. I would have thought so except for the 
> following statement in the RO security design
> 
> +   The binding update authorization mechanism used in the MIPv6 security
> +   design is primarily intended to mitigate this threat, and to limit
> +   the location of attackers to the path between a correspondent node
> +   and the home agent.
> 
> which implies the insecurity is the the path between the CN and the 
> <B>HA</B> rather than the path between the CN and MN.

The above is not conclusive. It only mentions those attacks deemed
to be more serious. The attack you mention is already described,
however. Please look at section 5.3 (Pretending to be your neighbor).

-gabriel

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



From exim@www1.ietf.org  Sat Jan 24 04:27:48 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01545
	for <mip6-archive@odin.ietf.org>; Sat, 24 Jan 2004 04:27:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkK4V-0000DM-Nk
	for mip6-archive@odin.ietf.org; Sat, 24 Jan 2004 04:27:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0O9RJhf000823
	for mip6-archive@odin.ietf.org; Sat, 24 Jan 2004 04:27:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkK4U-0000DB-JH
	for mip6-web-archive@optimus.ietf.org; Sat, 24 Jan 2004 04:27:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01511
	for <mip6-web-archive@ietf.org>; Sat, 24 Jan 2004 04:27:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkK4R-00032Q-00
	for mip6-web-archive@ietf.org; Sat, 24 Jan 2004 04:27:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkK3V-0002yh-00
	for mip6-web-archive@ietf.org; Sat, 24 Jan 2004 04:26:18 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkK2c-0002v5-00
	for mip6-web-archive@ietf.org; Sat, 24 Jan 2004 04:25:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkK2I-0008WJ-Ef; Sat, 24 Jan 2004 04:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjneE-0002SJ-82
	for mip6@optimus.ietf.org; Thu, 22 Jan 2004 17:50:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17721
	for <mip6@ietf.org>; Thu, 22 Jan 2004 17:49:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ajne6-0004gW-00
	for mip6@ietf.org; Thu, 22 Jan 2004 17:49:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ajnbf-00047X-00
	for mip6@ietf.org; Thu, 22 Jan 2004 17:47:26 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjnXw-0003GN-00
	for mip6@ietf.org; Thu, 22 Jan 2004 17:43:32 -0500
Received: from phys-bur1-1 ([129.148.13.15])
	by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id i0MMhVqX023047
	for <mip6@ietf.org>; Thu, 22 Jan 2004 15:43:31 -0700 (MST)
Received: from Sun.COM (sunlabs-sr1.East.Sun.COM [129.148.75.32])
 by bur-mail2.east.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPA id <0HRW00DJ1XSJFW@bur-mail2.east.sun.com> for mip6@ietf.org; Thu,
 22 Jan 2004 17:43:31 -0500 (EST)
Date: Thu, 22 Jan 2004 17:43:31 -0500
From: Victor Luchangco <Victor.Luchangco@Sun.COM>
To: mip6@ietf.org, mipshop@ietf.org
Cc: Panagiota Fatourou <faturu@zeus.cs.uoi.gr>,
        Shay Kutten <kutten@ie.technion.ac.il>
Reply-to: Victor.Luchangco@Sun.COM
Message-id: <40105213.60206@Sun.COM>
Organization: Sun Microsystems Laboratories
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6) Gecko/20040109
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Call for Papers: Algorithms and Data Structures for the Internet
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Please accept our apologies if you receive multiple copies.

==============================================================================

                       Call for Papers

       Algorithms and Data Structures for the Internet

                    Special Track for the

       Twenty-third Annual ACM SIGACT-SIGOPS Symposium on
         Principles of Distributed Computing (PODC 2004)
      (http://www.podc.org/podc2004/special-track-cfp.html)

The Internet is the modern platform for distributed computing.  PODC
has historically focused more on a higher level, abstracting away the
platform on which the computation takes place.  But PODC was covering
and contributing algorithms for distributing computing before the
Internet platform arrived.  The special track on Internet Algorithms
will attempt to expand the focus and the community, and bring modern
trends on Internet research closer to the PODC community, seeding
future areas of research for the years to come.

We are soliciting research contributions on the design, specification,
and implementation of algorithms for current and future Internet
applications.  Both theoretical work and practical work that
demonstrates fundamental principles of distributed computing in this
setting are desired.

Topics of interest include, but are not limited to,

+   Peer-to-peer, overlay, and content distribution networks

+   Analysis of small world networks

+   Algorithmic mechanism design for distributed systems

+   Distributed caching protocols

+   GRID computing

+   Multicast protocols

+   Network coding

+   Compression and coding in distributed systems

+   Models of fault-tolerance and reliability for Internet networks

+   Search engines and the Web:  crawling and indexing

+   Data stream algorithms for distributed systems:  stream algorithms
     for network monitoring, handling network traffic, and manipulating
     network-generated data.

The special track is an integral part of PODC.  The papers for the
special track are to be submitted to PODC, as described in the PODC
call for papers.  The PODC program committee reflects expertise in the
subjects of the special track, as well as in other PODC subjects.  For
the dates, formats, submission instructions, etc., please see the PODC
call for papers (http://www.podc.org/podc2004/cfp.html).



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



From exim@www1.ietf.org  Sat Jan 24 10:50:02 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12546
	for <mip6-archive@odin.ietf.org>; Sat, 24 Jan 2004 10:50:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkQ2R-00054c-8A
	for mip6-archive@odin.ietf.org; Sat, 24 Jan 2004 10:49:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0OFnZvi019498
	for mip6-archive@odin.ietf.org; Sat, 24 Jan 2004 10:49:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkQ2R-00054P-3H
	for mip6-web-archive@optimus.ietf.org; Sat, 24 Jan 2004 10:49:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12535
	for <mip6-web-archive@ietf.org>; Sat, 24 Jan 2004 10:49:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkQ2O-0003u4-00
	for mip6-web-archive@ietf.org; Sat, 24 Jan 2004 10:49:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkQ1R-0003sK-00
	for mip6-web-archive@ietf.org; Sat, 24 Jan 2004 10:48:34 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkQ0w-0003qY-00
	for mip6-web-archive@ietf.org; Sat, 24 Jan 2004 10:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkQ0v-0004xZ-Fq; Sat, 24 Jan 2004 10:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkQ0U-0004wd-Kg
	for mip6@optimus.ietf.org; Sat, 24 Jan 2004 10:47:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12509
	for <mip6@ietf.org>; Sat, 24 Jan 2004 10:47:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkQ0R-0003qF-00
	for mip6@ietf.org; Sat, 24 Jan 2004 10:47:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkPzZ-0003ok-00
	for mip6@ietf.org; Sat, 24 Jan 2004 10:46:37 -0500
Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkPzI-0003mK-00; Sat, 24 Jan 2004 10:46:20 -0500
Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com)
	by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian))
	id 1AkPz7-0000gl-00; Sat, 24 Jan 2004 16:46:09 +0100
Date: Sat, 24 Jan 2004 16:45:50 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Kent Leung <kleung@cisco.com>
Cc: mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net,
        users@freenet6.net
Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6
 implementations.
Message-Id: <20040124164550.422cb64e.henrik@levkowetz.com>
In-Reply-To: <4.3.2.7.2.20040122092132.0256a9b8@mira-sjcm-2.cisco.com>
References: <20040120182737.20338.qmail@web12823.mail.yahoo.com>
	<20040120110249.461dfeea.henrik@levkowetz.com>
	<20040120182737.20338.qmail@web12823.mail.yahoo.com>
	<4.3.2.7.2.20040122092132.0256a9b8@mira-sjcm-2.cisco.com>
X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg="pgp-sha1";
 boundary="Signature=_Sat__24_Jan_2004_16_45_50_+0100_CnA_7QrvTfWN_aHw"
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

--Signature=_Sat__24_Jan_2004_16_45_50_+0100_CnA_7QrvTfWN_aHw
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Thursday 22 January 2004, Kent Leung wrote:
> Here's Cisco's info:
> 
> IP: 4 & 6
> OS: Cisco IOS
> Name: Cisco Systems (URL: http://www.cisco.com/go/mobile_ip)
> Comments: MIPv4 commercial, MIPv6 technology preview
> 
> Kent

Thanks, Kent. 

I've added this to the page at <http://www.mip4.org/2004/implementations/>.
If there are any updates, let me know.

	Regards,

		Henrik



--Signature=_Sat__24_Jan_2004_16_45_50_+0100_CnA_7QrvTfWN_aHw
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAEpM3eVhrtTJkXCMRAkHlAJ0Z11lIp82HGb/EUKv9v8EO5NqvowCg528T
NhdqfohqmHAL3JNnQI8RzCo=
=OixS
-----END PGP SIGNATURE-----

--Signature=_Sat__24_Jan_2004_16_45_50_+0100_CnA_7QrvTfWN_aHw--

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



From exim@www1.ietf.org  Tue Jan 27 19:39:50 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06141
	for <mip6-archive@odin.ietf.org>; Tue, 27 Jan 2004 19:39:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aldjn-0007UY-S7
	for mip6-archive@odin.ietf.org; Tue, 27 Jan 2004 19:39:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0S0dNS1028792
	for mip6-archive@odin.ietf.org; Tue, 27 Jan 2004 19:39:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aldjn-0007UH-Lr
	for mip6-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 19:39:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05952
	for <mip6-web-archive@ietf.org>; Tue, 27 Jan 2004 19:39:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aldjl-0002pD-00
	for mip6-web-archive@ietf.org; Tue, 27 Jan 2004 19:39:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aldh8-00029G-00
	for mip6-web-archive@ietf.org; Tue, 27 Jan 2004 19:36:40 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AldeG-0001Se-00
	for mip6-web-archive@ietf.org; Tue, 27 Jan 2004 19:33:41 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AldRe-00065H-NM
	for mip6-web-archive@ietf.org; Tue, 27 Jan 2004 19:20:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AldGp-0001CW-8C; Tue, 27 Jan 2004 19:09:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlCNh-00039W-1A
	for mip6@optimus.ietf.org; Mon, 26 Jan 2004 14:27:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16645
	for <mip6@ietf.org>; Mon, 26 Jan 2004 14:26:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlCNU-0007GE-00
	for mip6@ietf.org; Mon, 26 Jan 2004 14:26:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlCL7-00079d-00
	for mip6@ietf.org; Mon, 26 Jan 2004 14:24:05 -0500
Received: from palrel11.hp.com ([156.153.255.246])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlCJg-00073E-00; Mon, 26 Jan 2004 14:22:36 -0500
Received: from strtio1.cup.hp.com (strtio1.cup.hp.com [15.13.129.245])
	by palrel11.hp.com (Postfix) with ESMTP
	id 5A48D1C012E5; Mon, 26 Jan 2004 21:28:05 -0800 (PST)
Received: (from jlau@localhost)
	by strtio1.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) id LAA13756;
	Mon, 26 Jan 2004 11:20:15 -0800 (PST)
Date: Mon, 26 Jan 2004 11:20:15 -0800 (PST)
From: Joe Lau <jlau@strtio1.cup.hp.com>
Message-Id: <200401261920.LAA13756@strtio1.cup.hp.com>
To: mip4@ietf.org, mip6@ietf.org
Cc: clemenj@cup.hp.com, henrik@levkowetz.com, jlau@cup.hp.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Re: Mobile IP v4 and v6 implementations.
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Subject: Re: Mobile IP v4 and v6 implementations.

Hello,

Please add the following Mobile IP implementation from HP to your
Mobile-IP Implementions List.

IP = 4
Operating Systems =  HP-UX 11.11
Name = HP-UX Mobile IPv4
License = commercial
Comments = Mobile IPv4 HA/CN, Reverse Tunneling, Route Optimization and AAA support 
URL = www.software.hp.com
-----------------

IP = 6
Operating Systems =  HP-UX 11.11 and HP-UX 11.23
Name = HP-UX Mobile IPv6
License = commercial
Comments = Mobile IPv6 HA/CN, draft-24
URL = www.software.hp.com

Thank you.

Regards,

Joe Lau
Mobile IP Project
SNSL, HP

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



From exim@www1.ietf.org  Wed Jan 28 21:10:30 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11918
	for <mip6-archive@odin.ietf.org>; Wed, 28 Jan 2004 21:10:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Am1d2-0005SJ-TB
	for mip6-archive@odin.ietf.org; Wed, 28 Jan 2004 21:10:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0T2A0Qi020967
	for mip6-archive@odin.ietf.org; Wed, 28 Jan 2004 21:10:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Am1d2-0005S6-O0
	for mip6-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 21:10:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11904
	for <mip6-web-archive@ietf.org>; Wed, 28 Jan 2004 21:09:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am1d0-00032R-00
	for mip6-web-archive@ietf.org; Wed, 28 Jan 2004 21:09:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Am1c3-0002x8-00
	for mip6-web-archive@ietf.org; Wed, 28 Jan 2004 21:08:59 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am1b8-0002rg-00
	for mip6-web-archive@ietf.org; Wed, 28 Jan 2004 21:08:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Am1b7-0004zb-OG; Wed, 28 Jan 2004 21:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Am1b2-0004xC-FG
	for mip6@optimus.ietf.org; Wed, 28 Jan 2004 21:07:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11809
	for <mip6@ietf.org>; Wed, 28 Jan 2004 21:07:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Am1az-0002q7-00
	for mip6@ietf.org; Wed, 28 Jan 2004 21:07:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Am1a1-0002kN-00
	for mip6@ietf.org; Wed, 28 Jan 2004 21:06:54 -0500
Received: from [202.106.187.158] (helo=sina.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1Am1Z8-0002ei-00
	for mip6@ietf.org; Wed, 28 Jan 2004 21:05:58 -0500
Received: (qmail 71807 invoked from network); 29 Jan 2004 02:05:51 -0000
Received: from unknown (HELO wym-pc) (210.42.103.237)
  by 202.106.187.158 with SMTP; 29 Jan 2004 02:05:51 -0000
Date: Thu, 29 Jan 2004 10:07:15 +0800
From: "Yuming Wang" <acer_wym@sina.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>,
        "pvandenbergen" <pvandenbergen@swin.edu.au>
Cc: "Mip6" <Mip6@ietf.org>, "mip4" <mip4@ietf.org>, "users" <users@ipv6.org>,
        "snap-users" <snap-users@kame.net>, "users" <users@freenet6.net>
Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6implementations.
X-mailer: Foxmail 5.0 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <E1Am1Z8-0002ei-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Henrik and Paul,

That's a good summary, a useful list.
Thanks!

>Hello Paul,
>
>Tuesday 20 January 2004, paul van den bergen wrote:
>> Hi all,
>> a few weeks ago I asked for mobile IP implementations...
>> 
>> just thought you'd all be interested to see what I found...
>
><snip table of implementations>
>
>Useful and interesting indeed.  I've taken the liberty of duplicating
>the information here:
>
> <http://www.mip4.org/2004/mip-implementations.html>
>
>
>	Thanks,
>		Henrik
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www.ietf.org/mailman/listinfo/mip6
>
>
>.

Yuming
2004-01-29
---------------- Yuming Wang -----------------
NGIT Research Group, ITEC R&D Center, EI Dpt.,
HuaZhong University of Science and Technology.
Email:     acer_wym@sina.com
Home Page: http://itec.hust.edu.cn/wym.htm
TEL: +86-27-87453207  FAX: +86-27-87456436
----



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



From exim@www1.ietf.org  Thu Jan 29 18:35:17 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00345
	for <mip6-archive@odin.ietf.org>; Thu, 29 Jan 2004 18:35:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmLgQ-0002Is-Ec
	for mip6-archive@odin.ietf.org; Thu, 29 Jan 2004 18:34:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0TNYoen008853
	for mip6-archive@odin.ietf.org; Thu, 29 Jan 2004 18:34:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmLgQ-0002Ii-8h
	for mip6-web-archive@optimus.ietf.org; Thu, 29 Jan 2004 18:34:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00233
	for <mip6-web-archive@ietf.org>; Thu, 29 Jan 2004 18:34:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmLgN-0002RY-00
	for mip6-web-archive@ietf.org; Thu, 29 Jan 2004 18:34:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmLe8-0001uI-00
	for mip6-web-archive@ietf.org; Thu, 29 Jan 2004 18:32:28 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmLcm-0001am-00
	for mip6-web-archive@ietf.org; Thu, 29 Jan 2004 18:31:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AmLcn-0002if-2v
	for mip6-web-archive@ietf.org; Thu, 29 Jan 2004 18:31:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmLck-00020E-FR; Thu, 29 Jan 2004 18:31:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmAsE-0001ZE-5D
	for mip6@optimus.ietf.org; Thu, 29 Jan 2004 07:02:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14195
	for <mip6@ietf.org>; Thu, 29 Jan 2004 07:02:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmAs9-0002CO-00
	for mip6@ietf.org; Thu, 29 Jan 2004 07:02:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmArI-000277-00
	for mip6@ietf.org; Thu, 29 Jan 2004 07:01:21 -0500
Received: from orion.lrg.ufsc.br ([150.162.63.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmAqs-00021R-00; Thu, 29 Jan 2004 07:00:55 -0500
Received: by orion.lrg.ufsc.br (Postfix, from userid 3002)
	id 898C2153B4; Thu, 29 Jan 2004 10:01:49 -0400 (WST)
Received: from localhost (localhost [127.0.0.1])
	by orion.lrg.ufsc.br (Postfix) with ESMTP
	id 5DCBE1712E; Thu, 29 Jan 2004 10:01:49 -0400 (WST)
Date: Thu, 29 Jan 2004 10:01:48 -0400 (WST)
From: Carlos Becker Westphall <westphal@lrg.ufsc.br>
To: neuman@ufc.br
Cc: mip6@ietf.org, mip4@ietf.org, mipshop@ietf.org
Message-ID: <Pine.GSO.4.10.10401290959530.15055-100000@orion.lrg.ufsc.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Mip6] ICT2004 - deadline extension (fwd)
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Taking into account several requests for postponing the submission
deadline for ICT2004, the organising committee has decided to
extend it to February 14 so that the participation could be as large
as possible. So take your time and visit the ICT2004 web site
at www.ict2004.com.br.


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



From exim@www1.ietf.org  Thu Jan 29 23:48:25 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11665
	for <mip6-archive@odin.ietf.org>; Thu, 29 Jan 2004 23:48:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmQZR-0007NQ-F8
	for mip6-archive@odin.ietf.org; Thu, 29 Jan 2004 23:47:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0U4lvrb028352
	for mip6-archive@odin.ietf.org; Thu, 29 Jan 2004 23:47:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmQZR-0007ND-9x
	for mip6-web-archive@optimus.ietf.org; Thu, 29 Jan 2004 23:47:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11651
	for <mip6-web-archive@ietf.org>; Thu, 29 Jan 2004 23:47:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmQZP-0000mt-00
	for mip6-web-archive@ietf.org; Thu, 29 Jan 2004 23:47:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmQYc-0000fH-00
	for mip6-web-archive@ietf.org; Thu, 29 Jan 2004 23:47:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmQXq-0000YU-00
	for mip6-web-archive@ietf.org; Thu, 29 Jan 2004 23:46:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmQXa-0007Dr-8s; Thu, 29 Jan 2004 23:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmQXR-0007Cx-KM
	for mip6@optimus.ietf.org; Thu, 29 Jan 2004 23:45:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11597
	for <mip6@ietf.org>; Thu, 29 Jan 2004 23:45:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmQXP-0000XV-00
	for mip6@ietf.org; Thu, 29 Jan 2004 23:45:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmQWW-0000RW-00
	for mip6@ietf.org; Thu, 29 Jan 2004 23:44:57 -0500
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmQWJ-0000Kk-00
	for mip6@ietf.org; Thu, 29 Jan 2004 23:44:43 -0500
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HSA00K01D52QJ@mailout1.samsung.com> for mip6@ietf.org; Fri,
 30 Jan 2004 13:43:50 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HSA00HGPD52W4@mailout1.samsung.com> for mip6@ietf.org; Fri,
 30 Jan 2004 13:43:50 +0900 (KST)
Received: from OLNRAO ([107.108.71.122])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HSA002VED501Z@mmp1.samsung.com> for mip6@ietf.org;
 Fri, 30 Jan 2004 13:43:50 +0900 (KST)
Date: Fri, 30 Jan 2004 10:10:59 +0530
From: "O.L.N.Rao" <olnrao@samsung.com>
To: mip6@ietf.org
Message-id: <011501c3e6eb$43721980$7a476c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: multipart/alternative;
 boundary="Boundary_(ID_UyqFTiEtHezjOnht/PrMpQ)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [Mip6] Re: I am still puzzled in DAD mechanism in mipv6
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

--Boundary_(ID_UyqFTiEtHezjOnht/PrMpQ)
Content-type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: 7BIT

Hi,

    ASAP we are going to update this draft to bringout the possible solutions (although vague).
    draft-park-ipv6-dad-problem-wlan-00.txt.  

    Also to note, the next draft mostly follows the name draft-<OneOfAuthor>-ipv6-over-wifi-01.txt.

    This is FYI plz.

Regards,
O.L.N.Rao

===================================


Hello to all:
In a draft issued in July:draft-park-ipv6-dad-problem-wlan-00.txt
The author says besides the time cost in the procedure that MN proceeds the DAD itself, there is mechanical deficiency in applying DAD in wireless environment.

In chapter 2, it says:
"In this case, IPv6 DAD will not be able to detect duplicate address
in 802.11 environment because if am 802.11 end station recevies
a DAD packet from a node which is having same MAC, the 802.11 end station discards the frame and will not be able to defend the DAD.
So the DAD always succeeds even though there are two end stations with the same MAC address.
Consequently, IPv6 node generates its address without any duplication,
but this address is not unique address but duplicated address. This concludes that "Multicast Packet Filtering based on Source Address" makes "Duplicate Address Detection" procedure trivial."

This draft provides in Chapter 3.2 two possible solutions:
* Enhanced Multicast Filtering at Layer 2
* Selective Filtering at Layer 2
But I don't see any subsequent draft concerning this defect and thinking over further implementations. All drafts and discussions I have read are about reducing the time cost in DAD procedure. Have it already been avoided or amended in draft24? What is the solution then? I would be very thankful if anyone here illuminates it to me.

Happy Christmas to all....

Yours Garthdawn
'spamcontrol '

--Boundary_(ID_UyqFTiEtHezjOnht/PrMpQ)
Content-type: text/html; charset=Windows-1252
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1276" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#c0c0c0>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; ASAP we are going to update this 
draft to bringout the possible solutions (although vague).</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; 
draft-park-ipv6-dad-problem-wlan-00.txt.&nbsp; </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; Also to note, the&nbsp;next 
draft&nbsp;mostly follows the name </FONT><FONT face=Arial 
size=2>draft-&lt;OneOfAuthor&gt;-ipv6-over-wifi-01.txt.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; This is FYI plz.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV><FONT face=Arial size=2>O.L.N.Rao</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>===================================</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Hello to all:<BR>In a draft issued in 
July:draft-park-ipv6-dad-problem-wlan-00.txt<BR>The author says besides the time 
cost in the procedure that MN proceeds the DAD itself, there is mechanical 
deficiency in applying DAD in wireless environment.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>In chapter 2, it says:<BR>"In this case, IPv6 DAD 
will not be able to detect duplicate address<BR>in 802.11 environment because if 
am 802.11 end station recevies<BR>a DAD packet from a node which is having same 
MAC, the 802.11 end station discards the frame and will not be able to defend 
the DAD.<BR>So the DAD always succeeds even though there are two end stations 
with the same MAC address.<BR>Consequently, IPv6 node generates its address 
without any duplication,<BR>but this address is not unique address but 
duplicated address. This concludes that "Multicast Packet Filtering based on 
Source Address" makes "Duplicate Address Detection" procedure 
trivial."</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>This draft provides in Chapter 3.2 two possible 
solutions:<BR>* Enhanced Multicast Filtering at Layer 2<BR>* Selective Filtering 
at Layer 2<BR>But I don't see any subsequent draft concerning this defect and 
thinking over further implementations. All drafts and discussions I have read 
are about reducing the time cost in DAD procedure. Have it already been avoided 
or amended in draft24? What is the solution then? I would be very thankful if 
anyone here illuminates it to me.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Happy Christmas to all....</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Yours Garthdawn<BR>'spamcontrol 
'</FONT></DIV></BODY></HTML>

--Boundary_(ID_UyqFTiEtHezjOnht/PrMpQ)--

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



From exim@www1.ietf.org  Fri Jan 30 00:39:25 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13835
	for <mip6-archive@odin.ietf.org>; Fri, 30 Jan 2004 00:39:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmRMn-0002bf-QX
	for mip6-archive@odin.ietf.org; Fri, 30 Jan 2004 00:38:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0U5cvc6010013
	for mip6-archive@odin.ietf.org; Fri, 30 Jan 2004 00:38:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmRMn-0002bQ-L6
	for mip6-web-archive@optimus.ietf.org; Fri, 30 Jan 2004 00:38:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13789
	for <mip6-web-archive@ietf.org>; Fri, 30 Jan 2004 00:38:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmRMk-00074X-00
	for mip6-web-archive@ietf.org; Fri, 30 Jan 2004 00:38:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmRLr-0006xh-00
	for mip6-web-archive@ietf.org; Fri, 30 Jan 2004 00:38:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmRKu-0006pz-00
	for mip6-web-archive@ietf.org; Fri, 30 Jan 2004 00:37:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmRKv-0002Eq-Jo; Fri, 30 Jan 2004 00:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmRKp-0002EE-AB
	for mip6@optimus.ietf.org; Fri, 30 Jan 2004 00:36:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13731
	for <mip6@ietf.org>; Fri, 30 Jan 2004 00:36:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmRKm-0006ow-00
	for mip6@ietf.org; Fri, 30 Jan 2004 00:36:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmRJp-0006im-00
	for mip6@ietf.org; Fri, 30 Jan 2004 00:35:54 -0500
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmRJX-0006cl-00
	for mip6@ietf.org; Fri, 30 Jan 2004 00:35:35 -0500
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0HSA00001FIH6T@mailout1.samsung.com> for mip6@ietf.org; Fri,
 30 Jan 2004 14:35:05 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0HSA00JEEFIG4J@mailout1.samsung.com> for mip6@ietf.org; Fri,
 30 Jan 2004 14:35:05 +0900 (KST)
Received: from OLNRAO ([107.108.71.122])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0HSA00EVBFICTD@mmp1.samsung.com> for mip6@ietf.org;
 Fri, 30 Jan 2004 14:35:04 +0900 (KST)
Date: Fri, 30 Jan 2004 11:02:12 +0530
From: "O.L.N.Rao" <olnrao@samsung.com>
To: mip6@ietf.org
Message-id: <015e01c3e6f2$6bd3c2a0$7a476c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: multipart/alternative;
 boundary="Boundary_(ID_ZBgGPJ1Ry0yqrbsZyhdBcw)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [Mip6] Reg. IPsec configuration for Payloads in TAHI testsuite
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

--Boundary_(ID_ZBgGPJ1Ry0yqrbsZyhdBcw)
Content-type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: 7BIT


Hello,

    Your TAHI MIPv6 CT suit is really very much helpful
    to carefully understand each and every line (even word)
    of Draft-24.

    I am currently working with 2.0.5 release.  In which
    there is a IPsec configuration for Payload packets to & from MN.

    When enabled IPSEC_* to YES:

    TN sends Echo Request with ESP applied twice once in each mode.
    First in Transport Mode with SPI 2009.  Then with Tunnel Mode with
    SPI 2007.  

    When NUT receives this packet, it could find 2007 SPI in its Policy DB
    and could decrypt and decapsulate.  However, when trying to find
    the policy for SPI 2009, it fails.  Because, currently our IPsec
    can not be applied differently for each ICMPv6 message type.  We can
    only apply per protocol basis.  So, what ever is configured for Prefix Discovery    
    automatically covers all the ICMPv6 packets.  Becuase SPDs 
    are ordered, the Payload polilcy configuration is applicable only to 
    non-MIPv6 and non-ICMPv6 packets.  Also, in the configuration for MN
    is with spi_e is not clear to me.  It has two values ??


    Let me know whether my understanding is correct, (that is Policy given is per
    ICMPv6 message type.  And, MPS & MPA need one policy and all others need
    another policy).


   Following snip is from the draft : draft-ietf-mobileip-mipv6-ha-ipsec-06.txt 
   5.2.3 Prefix Discovery
   In the following we describe some additional SPD and SAD entries to
   protect prefix discovery.  Note that the SPDs described above protect
   all ICMPv6 traffic between the mobile node and the home agent, as
   IPsec may not have the ability to distinguish between different
   ICMPv6 types. 


    This is true with our IPsec implementaion.  Also to note, payload protection is
    MAY in the draft.  Where as all others are MUST + SHOULD combination.
    I tried to make IPSEC_PAYLOAD* NO and run the script.  Then, TN sends
    Echo Request in plain text (not applied with any IPsec policy).  But as per
    the order of poicies, it SHOULD have been applied with Prefix Discovery policy
    as it covers all ICMPv6 packets (Again this statement is only applicable if
    your TAHI ipsec scripts work per protocol basis, and not per icmp message type).


    Your clarification in this regard is very much helpful for us to proceed.

    Thanks in advance.



Regards,
O.L.N.Rao

--Boundary_(ID_ZBgGPJ1Ry0yqrbsZyhdBcw)
Content-type: text/html; charset=Windows-1252
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1276" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#c0c0c0>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Hello,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; Your TAHI MIPv6 CT suit is 
really very much helpful</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; to carefully understand each and 
every line (even word)</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; of Draft-24.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; I am currently working with 
2.0.5 release.&nbsp; In which</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; there is a IPsec configuration 
for Payload packets to &amp; from MN.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp;&nbsp;When enabled IPSEC_* to 
YES:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; TN sends Echo Request with ESP 
applied twice once in each mode.</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; First in Transport Mode with SPI 
2009.&nbsp; Then with Tunnel Mode with</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; SPI 2007.&nbsp; </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; When NUT receives this packet, 
it could find 2007 SPI in its Policy DB</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; and could decrypt and 
decapsulate.&nbsp; However, when trying to find</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; the policy for SPI 2009, it 
fails.&nbsp; Because, currently our IPsec</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; can not be applied differently 
for each ICMPv6 message type.&nbsp; We can</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; only apply per protocol 
basis.&nbsp; So, what ever is configured for Prefix Discovery&nbsp;&nbsp;&nbsp; 
</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; automatically covers all the 
ICMPv6 packets.&nbsp; Becuase SPDs 
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; are ordered, </FONT>the Payload 
polilcy configuration </FONT><FONT face=Arial size=2>is applicable only to 
</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; non-MIPv6 and non-ICMPv6 
packets.&nbsp; Also, in the configuration for MN</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; is with spi_e is not&nbsp;clear 
to me.&nbsp; It has two values ??</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; Let me know whether my 
understanding is correct, (that is Policy given is per</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; ICMPv6 message type.&nbsp; 
And,&nbsp;MPS &amp; MPA need one policy and all others need</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; another policy).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp; Following snip is from the draft : 
<STRONG>draft-ietf-mobileip-mipv6-ha-ipsec-06.txt</STRONG> 
<P><FONT face=Arial size=2>&nbsp;&nbsp; 5.2.3 Prefix Discovery<BR>&nbsp;&nbsp; 
In the following we describe some additional SPD and SAD entries 
to<BR>&nbsp;&nbsp; protect prefix discovery.&nbsp; Note that the SPDs described 
above protect<BR>&nbsp;&nbsp; all ICMPv6 traffic between the mobile node and the 
home agent, as<BR>&nbsp;&nbsp; IPsec may not have the ability to distinguish 
between different<BR>&nbsp;&nbsp; ICMPv6 types.</FONT> 
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp;&nbsp;This is true with our IPsec 
implementaion.&nbsp;&nbsp;Also to note, payload protection is</FONT></DIV>
<DIV>&nbsp;&nbsp;&nbsp; MAY in the draft.&nbsp; Where as all others are MUST + 
SHOULD combination.</DIV>
<DIV>&nbsp;&nbsp;&nbsp; I tried to make IPSEC_PAYLOAD* NO and run the 
script.&nbsp; Then, TN sends</DIV>
<DIV>&nbsp;&nbsp;&nbsp; Echo Request in plain text (not applied with any IPsec 
policy).&nbsp; But as per</DIV>
<DIV>&nbsp;&nbsp;&nbsp; the order of poicies, it SHOULD have been applied with 
Prefix Discovery policy</DIV>
<DIV>&nbsp;&nbsp;&nbsp; as it covers all ICMPv6 packets (Again this statement is 
only applicable if</DIV>
<DIV>&nbsp;&nbsp;&nbsp; your TAHI ipsec scripts work per protocol basis, and not 
per icmp message type).</DIV>
<P>&nbsp;</P>
<P>&nbsp;&nbsp;&nbsp; Your clarification in this regard is very much helpful for 
us to proceed.</P>
<P>&nbsp;&nbsp;&nbsp; Thanks in advance.</P>
<P></FONT><FONT face=Arial size=2></FONT>&nbsp;</P></DIV></DIV>
<DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV><FONT face=Arial size=2>O.L.N.Rao</FONT></DIV></BODY></HTML>

--Boundary_(ID_ZBgGPJ1Ry0yqrbsZyhdBcw)--

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



From exim@www1.ietf.org  Sat Jan 31 23:27:59 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22870
	for <mip6-archive@odin.ietf.org>; Sat, 31 Jan 2004 23:27:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1An9Cl-0004l4-1G
	for mip6-archive@odin.ietf.org; Sat, 31 Jan 2004 23:27:31 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i114RULj018287
	for mip6-archive@odin.ietf.org; Sat, 31 Jan 2004 23:27:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1An9Ck-0004ks-NG
	for mip6-web-archive@optimus.ietf.org; Sat, 31 Jan 2004 23:27:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22856
	for <mip6-web-archive@ietf.org>; Sat, 31 Jan 2004 23:27:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1An9Ci-00026m-00
	for mip6-web-archive@ietf.org; Sat, 31 Jan 2004 23:27:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1An9Bp-00020y-00
	for mip6-web-archive@ietf.org; Sat, 31 Jan 2004 23:26:33 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1An9BM-0001vF-00
	for mip6-web-archive@ietf.org; Sat, 31 Jan 2004 23:26:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1An9BK-0004dh-OC; Sat, 31 Jan 2004 23:26:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmhhY-00042b-Ch
	for mip6@optimus.ietf.org; Fri, 30 Jan 2004 18:05:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24632
	for <mip6@ietf.org>; Fri, 30 Jan 2004 18:05:23 -0500 (EST)
From: sensorsystems_meeting@enl.usc.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmhhV-00006l-00
	for mip6@ietf.org; Fri, 30 Jan 2004 18:05:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmhgZ-0007nY-00
	for mip6@ietf.org; Fri, 30 Jan 2004 18:04:27 -0500
Received: from enl.usc.edu ([128.125.4.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amhff-0007hW-00
	for mip6@ietf.org; Fri, 30 Jan 2004 18:03:31 -0500
Received: from localhost.localdomain (enl.usc.edu [128.125.4.10])
	by enl.usc.edu (8.12.8/8.12.5) with ESMTP id i0UN3TLL014044
	for <mip6@ietf.org>; Fri, 30 Jan 2004 15:03:30 -0800
Date: Fri, 30 Jan 2004 15:03:29 -0800
Message-Id: <200401302303.i0UN3TLL014044@enl.usc.edu>
To: mip6@ietf.org
Subject: [Mip6] NSF Informational Meeting: Networking of Sensor Systems
Sender: mip6-admin@ietf.org
Errors-To: mip6-admin@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60


(Apologies if you receive multiple copies of this CfP).

			   Call for Participation
			   -----------------------

		 NSF Informational Meeting for the NeTS Program 
		  Focus Area: Networking of Sensor Systems
            ---------------------------------------------------------

  	   Meeting Website: http://enl.usc.edu/sensorsystems_meeting
          Relevant NSF Solicitation: 
          http://www.nsf.gov/pubs/2004/nsf04540/nsf04540.htm

The NSF recently issued a new solicitation 04-540 on Research in
Networking Technology and Systems.  One of the focus areas in this
solicitation is the Networking of Sensor Systems.  This focus area is
concerned with the design and development of protocols, operating
systems, and network architectures and with building systems that
facilitate constructing networks of sensor systems. The overall goal
is to make it as easy to assemble a network of sensor systems in the
next few years as it became in the 1980s to assemble a LAN of
workstations using the BSD Unix protocol stack and socket interface
and Ethernet line cards.

This is a call for participation in a one-day informational meeting
that will help potential proposers to get background information on
the focus area and on the state of sensor systems research. The
meeting has limited seating so please RSVP early.

Logistical Details
------------------
Date:  February 20, 2004

Venue: Marina Del Rey Hotel, CA
       Hotel Information:
          Marina Del Rey Hotel
          13534 Bali Way
          Marina del Rey, CA 90292
       Hotel Reservations:
          Call 1-800-882-4000
          Special Rate: $99.00
          Ask for: USC-NSF Networking of Sensor Systems Workshop
          Cutoff date: February 6, 2004
       Hotel Shuttle:
          Hotel has free shuttle from LAX, call 310-745-5181 for pickup.

Web site: http://enl.usc.edu/sensorsystems_meeting
Registration: http://enl.usc.edu/sensorsystems_meeting
Registration Fee: $50, payable on-site.

Contact: sensorsystems_meeting@enl.usc.edu for questions about the 
         workshop.

Goals of the Informational Meeting
----------------------------------

The purpose of the informational meeting is to share with the
community the goals and scope of the focus area.  By including
presentations from researchers, vendors, and applications experts,
this meeting will enable attendees to get a sense of the state of the
art in sensor networks, and the key challenges facing the focus area
and sub-areas thereof. It will help the community better target
proposals; PIs will be able to conserve efforts by understanding which
proposals would be completely out of scope.  Finally, it will start to
build a community for the focus area, perhaps encouraging early
collaboration and potentially strengthening the pool of submissions.

Format
------

The meeting will start with the cognizant NSF program officer(s)
presenting an overview of the focus area, and providing some context
for the focus area within the broader networking program at NSF.  This
presentation will include the technical and logistical details of the
focus area, and will be followed by an open question and answer
session from the attendees.

This break will then be followed by five panels of approximately one
hour each. Each panel will consist of speakers drawn from the
community who will cover different aspects of sensor network systems.
Each panel will have three panelists who will summarize lessons
learned from the first generation of sensor systems, and discuss the
challenges in each of the sub-areas.

Tentative Agenda
----------------

7:45am - 8am: Continental Breakfast

8am-10am: Overview and details of Focus Area
	  Guru Parulkar, NSF

10am-10:30am: Break

10:30am-11:30am: Network and protocol architecture for sensor systems

11:30am-12:30pm: Network programming and querying

12:30pm-1:30pm: Lunch

1:30pm-2:30pm: Algorithms for networks of sensor systems

2:30pm-3:00pm: Break and vendor demonstrations

3:00pm-4:00pm: Experiences with testbeds and applications

4:00pm-5:00pm: Integration of research and education

5:00pm-5:15pm: Closing remarks

A more detailed agenda will be posted on the website closer
to the meeting date.


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



