Re: [Hipsec] Sending data on HIP packets
Robert Moskowitz <rgm@htt-consult.com> Wed, 21 April 2010 17:41 UTC
Return-Path: <rgm@htt-consult.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3E233A6C2E for <hipsec@core3.amsl.com>; Wed, 21 Apr 2010 10:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.97
X-Spam-Level:
X-Spam-Status: No, score=-1.97 tagged_above=-999 required=5 tests=[AWL=0.629, 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 AjEjqm5948Kd for <hipsec@core3.amsl.com>; Wed, 21 Apr 2010 10:41:06 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id DA6A73A6CA3 for <hipsec@ietf.org>; Wed, 21 Apr 2010 10:30:04 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 01F0D6912C; Wed, 21 Apr 2010 17:24:14 +0000 (UTC)
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yCjlfN4Yhu4o; Wed, 21 Apr 2010 13:24:04 -0400 (EDT)
Received: from nc2400.htt-consult.com (h155.home.htt [208.83.67.155]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 8900E6912B; Wed, 21 Apr 2010 13:24:04 -0400 (EDT)
Message-ID: <4BCF3608.7030108@htt-consult.com>
Date: Wed, 21 Apr 2010 13:29:44 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Laganier, Julien" <julienl@qualcomm.com>
References: <4BCF16EC.6080806@htt-consult.com> <BF345F63074F8040B58C00A186FCA57F1EFEFD6FDE@NALASEXMB04.na.qualcomm.com>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1EFEFD6FDE@NALASEXMB04.na.qualcomm.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "hipsec@ietf.org" <hipsec@ietf.org>
Subject: Re: [Hipsec] Sending data on HIP packets
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2010 17:41:07 -0000
On 04/21/2010 12:14 PM, Laganier, Julien wrote: > Robert Moskowitz wrote: > >> Is there any experience in sending data along with I2 and R2? >> > I don't. > > >> Is this easy to do or very hard even with HIP aware apps? >> > Hmmm. Isn't this going to create problem with PMTUD because the PMTU on the data sent over I2 and R2 will be lower than can be expected after the HIP handshake concludes? On the other hand if the first sent is TCP SYN on I2 and TCP SYN ACK on R2 then there's no problem with PMTUD... The Initiator would have to 'know' that the data would fit within the allowed frame size. The Responder (after validating I2 and setting up the HIP Association state) might just pass the data up the stack and immediate send R2 without any data, the data response following later in its own datagram. Or if the Responder 'knows' there should be a response, it holds off on sending R2 until it gets the data (typically a TCP SYN/ACK). In fact if the higher layer rejects the connection with a quite drop, the Responder could not even send R2 and quitely drop the Association as well. Lots of room for smart behaviour. Or bad programming :)
- [Hipsec] Sending data on HIP packets Robert Moskowitz
- Re: [Hipsec] Sending data on HIP packets Laganier, Julien
- Re: [Hipsec] Sending data on HIP packets Robert Moskowitz