Re: [ftpext] Discouraging use of TCP "urgent data"

"William F. Maton" <wmaton@ottix.net> Tue, 21 September 2010 16:57 UTC

Return-Path: <wmaton@ottix.net>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46C263A6988 for <ftpext@core3.amsl.com>; Tue, 21 Sep 2010 09:57:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level:
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 yEteUq18ttB3 for <ftpext@core3.amsl.com>; Tue, 21 Sep 2010 09:57:13 -0700 (PDT)
Received: from iskra.ottix.net (iskra.ottix.net [IPv6:2001:410:90ff::2]) by core3.amsl.com (Postfix) with ESMTP id 0B3C13A692A for <ftpext@ietf.org>; Tue, 21 Sep 2010 09:57:11 -0700 (PDT)
Received: from iskra.ottix.net (localhost [127.0.0.1]) by iskra.ottix.net (8.14.4/8.14.4) with ESMTP id o8LGvVKX015313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Sep 2010 12:57:32 -0400
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 iskra.ottix.net o8LGvVKX015313
Received: from localhost (wmaton@localhost) by iskra.ottix.net (8.14.4/8.14.3/Submit) with ESMTP id o8LGvVRh015310; Tue, 21 Sep 2010 12:57:31 -0400
Date: Tue, 21 Sep 2010 12:57:31 -0400 (EDT)
From: "William F. Maton" <wmaton@ottix.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <4C98B731.2030802@isode.com>
Message-ID: <Pine.LNX.4.64.1009211253500.29844@iskra.ottix.net>
References: <4C98B731.2030802@isode.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ftpext@ietf.org
Subject: Re: [ftpext] Discouraging use of TCP "urgent data"
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 16:57:14 -0000

On Tue, 21 Sep 2010, Alexey Melnikov wrote:

> This is somewhat related to FTP: there is currently a document in IESG review 
> talking about deprecation (or strong discouragement) of use of TCP urgent 
> data:
>
> <https://datatracker.ietf.org/doc/draft-ietf-tcpm-urgent-data/>
>
> I would like to ask people to review this and tell me how this affect FTP.

Just taking a quick peek, looks like it isn't relevant to RFC 4217 at 
least, but as section 14 points out, 'FTP uses the Telnet Interrupt 
Process and Data Mark commands in conjunction with Urgent data to preface 
two commands: ABOR (Abort Transfer) and STAT (Status request).'

If 'urgent data' isn't recommended for new apps, then FTP is ...... ?

wfms