[Mip4] Initial handshake

To: mip4 at ietf.org, mip6 at ietf.org
Subject: [Mip4] Initial handshake
From: KKloe Kaishoto <kaishos at gmail.com>
Date: Tue, 19 May 2009 15:16:28 +0200
Delivered-to: mip4 at core3.amsl.com
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=P3oBl+3mt2ANVqYARvd3uU2+9arX6sM9ISNsYWsQt3U=; b=F04NerNSjps7n89Dq9gLAEnWVXLw7ZP2uiJltRYkUfs/js+ARcSrZVOUXOXWZ5kfGj AFggb48JesnIzcBB1pDK6MNTfST14DbzaIe8Ws1gshJwqnnct65ywyDoHfFsJ5WZ+S6L hzC5tLyQtUB9skydHmfDjIKgikG7z4dRnjBes=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=lWE8zwI7aIQEZm+iePAyfvyhNO27kJ/OhNRxcwi8OwdhBBH+IJ9+4zZYQlXuVHwqSm 5xlVqg3+ax+xLhJNwLLezq/ZTYbAqvVad8ESy5nHTsNSWCVuH7K4ExCQE2XctOZR44r9 IsS1L3s9WtJ2Pg/AYSiF1TGIdaHj/HSz3J5I0=
List-archive: <http://www.ietf.org/mail-archive/web/mip4>
List-help: <mailto:mip4-request@ietf.org?subject=help>
List-id: Mobility for IPv4 <mip4.ietf.org>
List-post: <mailto:mip4@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>

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?

Follow-Ups:
- Re: [Mip4] Initial handshake
  - From: Charles E. Perkins

Prev by Date: Re: [Mip4] Fw: Recharter: Ethernet Service Support
Next by Date: Re: [Mip4] Initial handshake
Previous by thread: Re: [Mip4] Fw: Recharter: Ethernet Service Support
Next by thread: Re: [Mip4] Initial handshake
Index(es):
- Date
- Thread

[Mip4] Initial handshake

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.