Re: [Mip6] [Mip4] Initial handshake
"Charles E. Perkins" <charles.perkins@earthlink.net> Tue, 19 May 2009 16:21 UTC
Return-Path: <charles.perkins@earthlink.net>
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 <charles.perkins@earthlink.net>) 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" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: KKloe Kaishoto <kaishos@gmail.com>
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: <mip6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mip6>
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-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/ >
- Re: [Mip6] [Mip4] Initial handshake Charles E. Perkins