Re: [tcpm] Fwd: New Version Notification fordraft-gont-tcpm-urgent-data-00

Andrew Yourtchenko <ayourtch@cisco.com> Mon, 10 November 2008 05:40 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 742013A69DD; Sun, 9 Nov 2008 21:40:32 -0800 (PST)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C8FA3A69DD for <tcpm@core3.amsl.com>; Sun, 9 Nov 2008 21:40:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level:
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[AWL=0.997, 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 OuHG9lmIFZcz for <tcpm@core3.amsl.com>; Sun, 9 Nov 2008 21:40:30 -0800 (PST)
Received: from av-tac-bru.cisco.com (odd-brew.cisco.com [144.254.15.119]) by core3.amsl.com (Postfix) with ESMTP id A099B3A63EB for <tcpm@ietf.org>; Sun, 9 Nov 2008 21:40:29 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id mAA5dnU19531; Mon, 10 Nov 2008 06:39:49 +0100 (CET)
Received: from kk-son (dhcp-peg3-vl30-144-254-7-191.cisco.com [144.254.7.191]) by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id mAA5dNG19381; Mon, 10 Nov 2008 06:39:23 +0100 (CET)
Date: Mon, 10 Nov 2008 06:39:27 +0100 (CET)
From: Andrew Yourtchenko <ayourtch@cisco.com>
X-X-Sender: ayourtch@zippy.stdio.be
To: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <200811100506.mAA56lfX011855@venus.xmundo.net>
Message-ID: <Pine.LNX.4.64.0811100610550.16978@zippy.stdio.be>
References: <200810280000.m9S00h4E029878@venus.xmundo.net> <A56C813C-B46D-4A02-A905-DD6B7E163156@windriver.com> <200810280203.m9S23foZ023071@venus.xmundo.net> <523175BF-A76B-4A4C-B726-AE4274BE9A44@windriver.com> <200810290227.m9T2RAHQ001594@venus.xmundo.net> <49088156.6020305@isi.edu> <200811030149.mA31n6fe020648@venus.xmundo.net> <4914B521.3090509@isi.edu> <200811080140.mA81eqGx025906@venus.xmundo.net> <4914EFC9.7060906@isi.edu> <200811080157.mA81vYQA032096@venus.xmundo.net> <4915D19A.4070404@isi.edu> <B5A5E01F9387F4409E67604C0257C71E0991E0@NDJSEVS25A.ndc.nasa.gov> <200811100506.mAA56lfX011855@venus.xmundo.net>
MIME-Version: 1.0
Cc: tcpm@ietf.org, ah@tr-sys.de, Joe Touch <touch@ISI.EDU>, David Borman <david.borman@windriver.com>, "Eddy, Wesley M. \(GRC-RCN0\)\[VZ\]" <Wesley.M.Eddy@nasa.gov>
Subject: Re: [tcpm] Fwd: New Version Notification fordraft-gont-tcpm-urgent-data-00
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ayourtch@cisco.com
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


On Mon, 10 Nov 2008, Fernando Gont wrote:

> At 01:47 a.m. 10/11/2008, Eddy, Wesley M. (GRC-RCN0)[VZ] wrote:
>
>> I have a question for the authors.  The survey you did of different OSes
>> and how they handle urgent data is good; did you do any similar study
>> of applications and which ones attempt to use urgent data?
>
> Not yet.
>
> For open source ones I guess we could simply grep lots and lots of source 
> files. For others it might be a little bit more difficult. I recall being 
> told that e.g., MS SQL uses urgent data... and there may be many others...

I think it was oracle SQL*Net:
http://www.stanford.edu/dept/itss/docs/oracle/10g/network.101/b10776/sqlnet.htm

Default is to "use urgent data". I'll try to find an oracle install to see 
what the "urgent data" constitutes there.

One other possible candidate (to be verified) might include Citrix 
terminal server traffic (the anecdotal evidence taken from snort-users 
archive, e.g.: http://archives.neohapsis.com/archives/snort/2001-08/0787.html)

However, both are "closed domain" applications - i.e., usually both 
ends of them are under single administrative domain, so regardless of 
which behaviour they use, standards compliant or not, it can be solved 
with configuration.

The bigger problem is for internet-wide applications, e.g. for FTP, whose 
ABOR command appears to utilise the TCP Urgent as well. Ironically, the 
standard command-line ftp client on linux is BSD, so all the 
"standards-compliant" servers are effectively "broken" by default.

There could be some more proprietary apps as well, since the searchable 
discussion forums on the internet include quite a lot of discussions on 
this topic from the puzzled application programmers.

thanks,
andrew
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm