From owner-soc-status@FreeBSD.ORG  Tue Jun 14 16:39:35 2011
Return-Path: <owner-soc-status@FreeBSD.ORG>
Delivered-To: soc-status@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E6CA1106566C
	for <soc-status@freebsd.org>; Tue, 14 Jun 2011 16:39:35 +0000 (UTC)
	(envelope-from nc3bhconc@gmail.com)
Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com
	[209.85.216.175])
	by mx1.freebsd.org (Postfix) with ESMTP id A38DF8FC27
	for <soc-status@freebsd.org>; Tue, 14 Jun 2011 16:39:35 +0000 (UTC)
Received: by qyk35 with SMTP id 35so1876969qyk.13
	for <soc-status@freebsd.org>; Tue, 14 Jun 2011 09:39:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:sender:from:date
	:x-google-sender-auth:message-id:subject:to:content-type;
	bh=rAYZIK3WOEfQJ5cYiQmymQprkfxYS8AVvsDmpratkqo=;
	b=Jf7jga2KgPQ1bd+nQEOrZLMweXQkAaUPcNAa9NoLW1y3t9qJSb/Ju0XOmmaEFRzc72
	q5aEYTmWXCqunXJa1NVJ1SbAf6xX5sjTrRcKqMlca2uZR59et1lu0IpE7dlDop+6B1Ri
	OXu6aFJvigc3Ea8jOFv+7uhUyzETDKMaCFAZM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:sender:from:date:x-google-sender-auth:message-id
	:subject:to:content-type;
	b=RxKLBtuXKv+hUYD+ybS300egGuqD+BBpKxEt7j+tv4NsHV40h3plT8tENpE/FOUybu
	mdyGg6hXHh/TNhciGWlYUu0gNe5GtKQXUUfFVf0qUAO0obs8wxToUVVqRhBaxV8Gg6Gt
	Lfx2CqkM++UbQx7U8b1Oddu2mfzw7d5c3ojEc=
Received: by 10.224.202.72 with SMTP id fd8mr4986406qab.295.1308069575126;
	Tue, 14 Jun 2011 09:39:35 -0700 (PDT)
MIME-Version: 1.0
Sender: nc3bhconc@gmail.com
Received: by 10.224.28.212 with HTTP; Tue, 14 Jun 2011 09:39:15 -0700 (PDT)
From: Catalin Nicutar <catalin.nicutar@gmail.com>
Date: Tue, 14 Jun 2011 19:39:15 +0300
X-Google-Sender-Auth: 4MMjEQpgLyWrvgR2xjTo1lJrGFo
Message-ID: <BANLkTimrF65oU14anh5WPw6=8Gz4quO57g@mail.gmail.com>
To: soc-status@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: TCP UTO - Weekly Report 3
X-BeenThere: soc-status@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Summer of Code Status Reports and Discussion <soc-status.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/soc-status>,
	<mailto:soc-status-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/soc-status>
List-Post: <mailto:soc-status@freebsd.org>
List-Help: <mailto:soc-status-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/soc-status>,
	<mailto:soc-status-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 16:39:36 -0000

Hello!

This is the third report for TCP UTO.

* Short TCP UTO description

UTO stands for User Timeout Option (it is described in RFC5482). TCP UTO
specifies a peer should be allowed to advertise its chosen `User Timeout'
for a connection.
The wiki page for this project: http://wiki.freebsd.org/CatalinNicutar/TCPUTO


* Work completed last week
       * The option is now correctly sent on first SYN sent
       * I have tested using Wireshark and it seems to be correct (or pcap is
       making the same mistakes as I am)

The TCP_SNDUTO_TIMEOUT setsockopt option controls the way the user timeout
is sent. If it's set to 0 no user timeout is sent. If it's > 0 the specified
timeout is sent on first SYN.

* My goals for for this week
       * Correctly set the granularity for the timeout (seconds / minutes)
       * Test the option for SYN-ACK
       * Receive the option and store it (the value can be retrieved using
       TCP_RCVUTO_TIMEOUT)

This is all for report 3. If you have questions, suggestions or advices
drop me an email to cnicutar@FreeBSD.org.

Catalin Nicutar