Re: Draft Review request - EUDP

David Borman <dab@weston.borman.com> Wed, 01 December 2010 16:09 UTC

Return-Path: <dab@weston.borman.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E8803A6C5C for <tsvwg@core3.amsl.com>; Wed, 1 Dec 2010 08:09:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 2G9hRUoZljH5 for <tsvwg@core3.amsl.com>; Wed, 1 Dec 2010 08:09:34 -0800 (PST)
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by core3.amsl.com (Postfix) with ESMTP id EED923A6C58 for <tsvwg@ietf.org>; Wed, 1 Dec 2010 08:09:33 -0800 (PST)
Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id oB1GAiMW016923; Wed, 1 Dec 2010 08:10:45 -0800 (PST)
Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 1 Dec 2010 08:10:44 -0800
Received: from [172.25.34.36] ([172.25.34.36]) by ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 1 Dec 2010 08:10:43 -0800
Subject: Re: Draft Review request - EUDP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: David Borman <dab@weston.borman.com>
In-Reply-To: <4CF65BD7.20304@gmail.com>
Date: Wed, 1 Dec 2010 10:10:42 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C2B9319-37F5-478C-B2E8-5B4EB0223D47@weston.borman.com>
References: <4CF630B9.2070901@gmail.com> <C23D4465-516D-4150-A3EC-8AF7E21E084B@nokia.com> <4CF65BD7.20304@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-OriginalArrivalTime: 01 Dec 2010 16:10:44.0152 (UTC) FILETIME=[4E9ECB80:01CB9172]
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 16:09:35 -0000

On Dec 1, 2010, at 8:29 AM, Mykyta Yevstifeyev wrote:

> 01.12.2010 13:52, Lars Eggert wrote:
>> Hi,
>> 
>> On 2010-12-1, at 13:25, Mykyta Yevstifeyev wrote:
>>> I have recently made a draft which, IMO, will be interesting
>>> for the WG. You can find it here:
>>> 
>>> http://datatracker.ietf.org/doc/draft-yevstifeyev-eudp/?include_text=1
>>> 
>>> Could you please review it?
>> This is not a useful proposal. Why? UDP is IP plus ports and a checksum. There is no feature negotiation, no state machine to be extended, etc. *at the protocol level*.
> IMO (and this is the main purpose of the EUDP) if some feature concerns any protocol or data which is to be put into payload of the protocol of some layer, the corresponding option should be put in 'this-layer' protocol header. Moreover, UDP provides core service while TCP or DCCP provide many features which can be just not needed. EUDP can provide (or not provide) any features except core ones.
> It is made to provide the choice of features.

I read the document, and adding option space to UDP is not interesting if you don't also have at least one useful option defined at the same time.  There is no motivation to implement this with just the NOP and EOL options.  In addition, as Lars points out, UDP does not have a state machine.  This means that adding any new option will require that the option can either be safely ignored, or negotiation needs to be added to the option itself.  That implies potentially sending UDP packets with just options, and no data.  Or the applications have to do the option negotiation.

So, yes, if you want to add options to UDP, this would be a way to do it, but first you need to have at least one useful option to make use of the new mechanism.

>> (Sure, applications using UDP have these things. But they can *already* put whatever they like into the payload anyway. There is no need for a common spec.)
>> 
>> Plus, by using a different IP protocol number, it is pretty much guaranteed that middleboxes will simply drop this traffic.
> Why do you think that if there is unknown protocol code the traffic will be dropped? Currently there are 142 IP Protocol umbers and near 10 are really used. Will you prove that other 132 are being dropped?

Middle boxes that filter traffic tend to first block everything and then only allow through things that they understand, otherwise if they let through unknown traffic it provides a wide-open door for the middle box to be circumvented.

			-David Borman

>> Lars
>> 
>> PS: Meta comment: You have submitted quite a number of IDs lately (http://tools.ietf.org/id/yevstifeyev). I really do applaud your enthusiasm. But the vast majority of your IDs to me appear to be rather pointless. I encourage you to follow some WGs that interest you most more closely, in order to learn where your contributions would be most useful. I'm being blunt here - please don't be offended. I don't want you to turn away from the IETF in frustration because your contributions don't get traction; I want your contributions to matter.
> Thank you for advice.
> 
> I hope I have explained everything clearly.
> 
> All the best,
> Mykyta Yevstifeyev