From owner-freebsd-hackers  Wed Jun 18 21:22:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA04295
          for hackers-outgoing; Wed, 18 Jun 1997 21:22:37 -0700 (PDT)
Received: from caipfs.rutgers.edu (root@caipfs.rutgers.edu [128.6.155.100])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04290
          for <freebsd-hackers@FreeBSD.ORG>; Wed, 18 Jun 1997 21:22:34 -0700 (PDT)
Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5])
	by caipfs.rutgers.edu (8.8.5/8.8.5) with SMTP id AAA21282;
	Thu, 19 Jun 1997 00:22:07 -0400 (EDT)
Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4)
	id AAA07058; Thu, 19 Jun 1997 00:20:01 -0400
Date: Thu, 19 Jun 1997 00:20:01 -0400
Message-Id: <199706190420.AAA07058@jenolan.caipgeneral>
From: "David S. Miller" <davem@jenolan.rutgers.edu>
To: louie@TransSys.COM
CC: flash@hway.ru, freebsd-hackers@FreeBSD.ORG, Eric.Schenk@dna.lth.se
In-reply-to: <199706190331.XAA00910@whizzo.TransSys.COM> (louie@TransSys.COM)
Subject: Re: RFCs and Urgent pointers
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

   From: "Louis A. Mamakos" <louie@TransSys.COM>
   Date: Wed, 18 Jun 1997 23:31:09 -0400

   > >    Anybody thought of adding the RFC style Urgent pointers to the TCP,
   > >    say, as TCP level socket option ?

   TCP urgent data is how the socket out-of-band-data abstraction is realized.  I
   don't understand what else you might "add" to TCP to do "Urgent Pointers". 
   There ought to already be a option for "inline" out-of-band data, which I
   think is the default in most modern BSD-based TCPs.

The issue is not to add anything, but rather to allow, on a
configurable basis, one to choose between the RFC sanctioned
interpretation of where the urgent pointer "points" and the
traditional one.

Read the RFC for details 8-)

Later,
David "Sparc" Miller
davem@caip.rutgers.edu