From owner-freebsd-hackers Wed Jun 18 06:15:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA15654 for hackers-outgoing; Wed, 18 Jun 1997 06:15:51 -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 GAA15647 for ; Wed, 18 Jun 1997 06:15:48 -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 JAA01980; Wed, 18 Jun 1997 09:15:46 -0400 (EDT) Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4) id JAA06467; Wed, 18 Jun 1997 09:13:40 -0400 Date: Wed, 18 Jun 1997 09:13:40 -0400 Message-Id: <199706181313.JAA06467@jenolan.caipgeneral> From: "David S. Miller" To: flash@hway.ru CC: freebsd-hackers@FreeBSD.ORG, Eric.Schenk@dna.lth.se In-reply-to: (flash@hway.ru) Subject: Re: RFCs and Urgent pointers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Date: Wed, 18 Jun 1997 16:50:13 +0400 (MSD) From: "Alexander V. Tischenko" Anybody thought of adding the RFC style Urgent pointers to the TCP, say, as TCP level socket option ? We've made this a sysctl() tunable under Linux, I don't think we considered the benefits of making it a socket option, that may in fact be a better approach. Comments?