From owner-freebsd-net@FreeBSD.ORG  Wed Dec 22 21:02:56 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3070416A4CE; Wed, 22 Dec 2004 21:02:56 +0000 (GMT)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id F148943D54; Wed, 22 Dec 2004 21:02:55 +0000 (GMT)
	(envelope-from qing.li@bluecoat.com)
Received: from bcs-mail.bluecoat.com (bcs-mail.bluecoat.com [216.52.23.69])
	by whisker.bluecoat.com (8.13.0/8.13.0) with ESMTP id iBML2t7t013354;
	Wed, 22 Dec 2004 13:02:55 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 22 Dec 2004 13:02:54 -0800
Message-ID: <00CDF9AA240E204FA6E923BD35BC643607C4803C@bcs-mail.internal.cacheflow.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: TCP URG point
Thread-Index: AcToaZs4rj1zYtFcRASeS3QwS8Onyg==
From: "Li, Qing" <qing.li@bluecoat.com>
To: <freebsd-net@freebsd.org>, <freebsd-current@freebsd.org>
X-Scanned-By: MIMEDefang 2.49 on 216.52.23.28
Subject: TCP URG point
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Dec 2004 21:02:56 -0000


	It appears the TCP urgent pointer is off by 1.

	In RFC-1122, section 4.2.2.4 on Page 83 describes the
	urgent pointer error in RFC-793.

	The 6.0-CURRENT code has the urgent pointer set
	to (LAST+1).

	Any comments before I sent a PR ?

	-- Qing