From charles.perkins@earthlink.net Tue May 19 09:21:19 2009 Return-Path: X-Original-To: mip6@core3.amsl.com Delivered-To: mip6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00C6A28C0FB; Tue, 19 May 2009 09:21:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.392 X-Spam-Level: X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIDhQSL1M7bs; Tue, 19 May 2009 09:21:17 -0700 (PDT) Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 60EF33A6A93; Tue, 19 May 2009 09:20:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=HE/k0N91TKilEuPsMvkq6mWCCuNan972Ea4evhlmIN08PqO095rNbu6ZkW+GG8Zh; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [38.96.10.141] (helo=[192.168.1.100]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1M6S55-0000yR-Kx; Tue, 19 May 2009 12:22:19 -0400 Message-ID: <4A12DCBA.3010305@earthlink.net> Date: Tue, 19 May 2009 09:22:18 -0700 From: "Charles E. Perkins" Organization: Wichorus Inc. User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: KKloe Kaishoto References: <5819563d0905190616m34ba5111hd435408c3c1f3efb@mail.gmail.com> In-Reply-To: <5819563d0905190616m34ba5111hd435408c3c1f3efb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52f11a20e13c92aeb5f46c40a6a2bb307b350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 38.96.10.141 Cc: mip6@ietf.org, mip4@ietf.org Subject: Re: [Mip6] [Mip4] Initial handshake X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 16:21:19 -0000 Hello Pablo, Mobile IPv* is specifically constructed so that TCP (or any other transport protocol that would normally be carried by IP) will work without any knowledge of Mobile IP. So UDP, SCTP, ICMP, all should just work. Regards, Charlie P. KKloe Kaishoto wrote: > Hallo, my name is Pablo and I am wondering how a mobile establishes a > connection to a correspondent node, I am guessing it uses the ordinary > TCP/IP three way handshake but I am wondering if there is somewhere > more specified how the packages are composed if they are anything > special with them when using Mobile IPv4 or Mobile IPv6? > ------------------------------------------------------------------------ > > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From thiagobemerguy@gmail.com Tue May 19 14:55:22 2009 Return-Path: X-Original-To: mip6@core3.amsl.com Delivered-To: mip6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 668D828C329 for ; Tue, 19 May 2009 14:55:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eoux3F79ps0e for ; Tue, 19 May 2009 14:55:21 -0700 (PDT) Received: from mail-fx0-f158.google.com (mail-fx0-f158.google.com [209.85.220.158]) by core3.amsl.com (Postfix) with ESMTP id EB8D73A70E9 for ; Tue, 19 May 2009 14:55:20 -0700 (PDT) Received: by fxm2 with SMTP id 2so77533fxm.37 for ; Tue, 19 May 2009 14:56:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=shBZN3tVBKuvTq/Sz7cVV8S8ai+CmX9tLCxqdyWjO30=; b=t48DXsRrg1d68ET0mzatOubftIBBNK3sl9jBMEKoisT5MUmWHiIDqADmb2zy189LPm 3wl8SWJ4633E7qQkvQxNOdVcOTMU09XAQIMIkK7kLx1VK3KxvCGz2jlU3w/M4VhTlPms VDlrT5iA11xRrtq9A2mrSBOsHNYLs6+bkYCAg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; b=hzHlH8pAvZ6Od0Ell9d+K+wtbDWq8SZ1ERtv1zJVYdAULfoTREiEWfLz5++GbLNGvn OaSJOb2s3is6vk/y6NcZIZoGwzcDN9wU9/8Fvfv1iQBhpEXIS2CZ/PLpSuYG7Vxab3C2 oPgvSZJXQXoWWdOpRxFMCoB6CfPP5q4RlcpPI= Received: by 10.204.50.212 with SMTP id a20mr504942bkg.35.1242770204547; Tue, 19 May 2009 14:56:44 -0700 (PDT) Received: from servthiago (201008140046.user.veloxzone.com.br [201.8.140.46]) by mx.google.com with ESMTPS id 13sm704421fks.34.2009.05.19.14.56.41 (version=SSLv3 cipher=RC4-MD5); Tue, 19 May 2009 14:56:43 -0700 (PDT) From: "Thiago Bemerguy" To: Date: Tue, 19 May 2009 18:57:04 -0300 Message-ID: <001b01c9d8cc$c22e9310$468bb930$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C9D8B3.9CE15B10" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcnYzL55MwpOfpaiQFS8qd6qiZB9HQ== Content-Language: pt-br Subject: [Mip6] MIPv6 on embedded devices X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 21:55:22 -0000 Esta é uma mensagem em várias partes no formato MIME. ------=_NextPart_000_001C_01C9D8B3.9CE15B10 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Since there is already mipv6 support in linux, and the usage group develops the mipv6 user application. Have someone tested embedded devices working as home agents running (maybe) Openwrt? ------=_NextPart_000_001C_01C9D8B3.9CE15B10 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Since there is already mipv6 = support in linux, and the usage group develops the mipv6 user application. Have = someone tested embedded devices working as home agents running (maybe) = Openwrt?



__________ Information from ESET Smart Security, version of = virus signature database 4084 (20090518) __________

The message = was checked by ESET Smart Security.

http://www.eset.com
------=_NextPart_000_001C_01C9D8B3.9CE15B10-- From henrik.petander@gmail.com Wed May 20 19:57:57 2009 Return-Path: X-Original-To: mip6@core3.amsl.com Delivered-To: mip6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B44243A6EE2 for ; Wed, 20 May 2009 19:57:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4TgqyeOcf3k for ; Wed, 20 May 2009 19:57:56 -0700 (PDT) Received: from mail-gx0-f166.google.com (mail-gx0-f166.google.com [209.85.217.166]) by core3.amsl.com (Postfix) with ESMTP id B08593A698C for ; Wed, 20 May 2009 19:57:56 -0700 (PDT) Received: by gxk10 with SMTP id 10so1558378gxk.13 for ; Wed, 20 May 2009 19:59:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VXN1xARVB4QrprzkVgcuqgA0zdZqoTuwU7bxouC58SA=; b=EX6GniOCY6giDrsH4AttzR0fdFG6b+efMqlc1Vjfqjjv3FT0ZBfMQuAJjPqtTdMkS+ s7YdhnksOVPb6EkhWrzVTNnfp23Huzf60ggOYJVhOcfyYXhUIYk3NOM3ZkM88JwdwqnH 8AiNsH9WCwYZ3MjBq8HheM9uWQ4drnv4sIrYc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=GdJQPcR8koYTay0wy94cHFOyUqZRoksiMBhVGewNThGVTLMxveJZsUDUVyX+w4x/fO /qHjVroglrHErtCjXcCq3PBiJcdHFjsou4khNpZljOAS0SM/MWTXzlBGBrrRQwuorOIg 0CL/cVx1RzLIa8oKo/7Zmqe9/8mfqUNDtDBWc= MIME-Version: 1.0 Received: by 10.90.49.3 with SMTP id w3mr1669650agw.62.1242874771778; Wed, 20 May 2009 19:59:31 -0700 (PDT) In-Reply-To: <001b01c9d8cc$c22e9310$468bb930$@com> References: <001b01c9d8cc$c22e9310$468bb930$@com> Date: Thu, 21 May 2009 12:59:31 +1000 Message-ID: <36cb7a210905201959i2c8dfa20jf3508a53ae3a50c5@mail.gmail.com> From: Henrik Petander To: Thiago Bemerguy Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: mip6@ietf.org Subject: Re: [Mip6] MIPv6 on embedded devices X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: henrik.petander@iki.fi List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2009 02:57:57 -0000 Hi Thiago, I haven't ported MIPv6 for OpenWRT, but we have Dual stack MIPv6 code based on umip-2.02 running on Android (which is ARM based), so you should be able to get the UMIP code working on other embedded Linux systems as well. If openwrt uses a recent 2.6 kernel, getting IPv6 and MIPv6 extension headers working will probably only require cross compiling and installing a kernel configured with the required options for MIPv6. To get the userspace MIPv6 signaling daemon working could be a matter of only running configure and make, if openwrt has a cross compilation environment supporting automake tools. Regards, Henrik Petander On Wed, May 20, 2009 at 7:57 AM, Thiago Bemerguy wrote: > Since there is already mipv6 support in linux, and the usage group develops > the mipv6 user application. Have someone tested embedded devices working as > home agents running (maybe) Openwrt? > > __________ Information from ESET Smart Security, version of virus signature > database 4084 (20090518) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > > From Basavaraj.Patil@nokia.com Thu May 21 07:39:51 2009 Return-Path: X-Original-To: mip6@core3.amsl.com Delivered-To: mip6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1B053A6879 for ; Thu, 21 May 2009 07:39:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.375 X-Spam-Level: X-Spam-Status: No, score=-6.375 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vhmCHBbqwQGP for ; Thu, 21 May 2009 07:39:50 -0700 (PDT) Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 80E043A6C07 for ; Thu, 21 May 2009 07:39:50 -0700 (PDT) Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n4LEfEpq009825; Thu, 21 May 2009 17:41:20 +0300 Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 21 May 2009 17:41:12 +0300 Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 21 May 2009 17:41:11 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 21 May 2009 17:41:06 +0300 Received: from NOK-EUMSG-03.mgdnok.nokia.com ([65.54.30.88]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Thu, 21 May 2009 16:41:06 +0200 From: To: , Date: Thu, 21 May 2009 16:41:17 +0200 Thread-Topic: [Mip6] MIPv6 on embedded devices Thread-Index: AcnZwDX1B8Lns9TCRm+royjK48/wYQAYfyuE Message-ID: In-Reply-To: <36cb7a210905201959i2c8dfa20jf3508a53ae3a50c5@mail.gmail.com> Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 21 May 2009 14:41:06.0750 (UTC) FILETIME=[2C861DE0:01C9DA22] X-Nokia-AV: Clean Cc: mip6@ietf.org Subject: Re: [Mip6] MIPv6 on embedded devices X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2009 14:39:51 -0000 We have a working version of DSMIP6 as well on linux. DSMIP6 works fairly well without the IPsec complexity. It should be fairly straight forward to implement DSMIP6 on openwrt without the IPsec/IKEv2 component. -Basavaraj=20 On 5/20/09 9:59 PM, "ext Henrik Petander" wrote= : > Hi Thiago, >=20 > I haven't ported MIPv6 for OpenWRT, but we have Dual stack MIPv6 code > based on umip-2.02 running on Android (which is ARM based), so you > should be able to get the UMIP code working on other embedded Linux > systems as well. >=20 > If openwrt uses a recent 2.6 kernel, getting IPv6 and MIPv6 extension > headers working will probably only require cross compiling and > installing a kernel configured with the required options for MIPv6. > To get the userspace MIPv6 signaling daemon working could be a matter > of only running configure and make, if openwrt has a cross compilation > environment supporting automake tools. >=20 > Regards, > Henrik Petander >=20 > On Wed, May 20, 2009 at 7:57 AM, Thiago Bemerguy > wrote: >> Since there is already mipv6 support in linux, and the usage group devel= ops >> the mipv6 user application. Have someone tested embedded devices working= as >> home agents running (maybe) Openwrt? >>=20 >> __________ Information from ESET Smart Security, version of virus signat= ure >> database 4084 (20090518) __________ >>=20 >> The message was checked by ESET Smart Security. >>=20 >> http://www.eset.com >>=20 >> _______________________________________________ >> Mip6 mailing list >> Mip6@ietf.org >> https://www.ietf.org/mailman/listinfo/mip6 >>=20 >>=20 > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6