Re: [Taps] A proposal to throw out RTP

Joe Touch <touch@isi.edu> Thu, 04 June 2015 19:12 UTC

Return-Path: <touch@isi.edu>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3776F1A8906 for <taps@ietfa.amsl.com>; Thu, 4 Jun 2015 12:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level:
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EWhcF0YRIZ7b for <taps@ietfa.amsl.com>; Thu, 4 Jun 2015 12:12:19 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E2161A88F7 for <taps@ietf.org>; Thu, 4 Jun 2015 12:12:19 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id t54JBHS0010439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 4 Jun 2015 12:11:17 -0700 (PDT)
Message-ID: <5570A2D4.4040005@isi.edu>
Date: Thu, 04 Jun 2015 12:11:16 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>, Marie-Jose Montpetit <mariejo@mit.edu>
References: <E3DC5BD4-8D0C-46FE-996D-36E32F3C1DAF@ifi.uio.no> <c7e606a2040be5b0142f7ca52005a533.squirrel@erg.abdn.ac.uk> <4600A299-E820-4D67-8ADF-BB9783931E49@trammell.ch> <556F2413.5040308@tik.ee.ethz.ch> <DM2PR0301MB06559237988EFFEF557312DAA8B40@DM2PR0301MB0655.namprd03.prod.outlook.com> <36C995D9-261C-4AAD-A86D-681F58CACF9A@mit.edu> <ED9159AB-BCA3-4347-9130-C9123283BAA2@ifi.uio.no> <FDC85C9E-F488-429A-BE7D-5390798B4E52@mit.edu> <557029B4.9030001@tik.ee.ethz.ch>
In-Reply-To: <557029B4.9030001@tik.ee.ethz.ch>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MailScanner-ID: t54JBHS0010439
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/5iPyi1TU7EJSkdjekldHdZ0ZGRg>
Cc: "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] A proposal to throw out RTP
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2015 19:12:20 -0000


On 6/4/2015 3:34 AM, Mirja Kühlewind wrote:
> It's in the doc:
> 
> "Application:  an entity that uses the transport layer for end-to-end
>       delivery data across the network (this may also be an upper layer
>       protocol or tunnel encapsulation)."

"End to end" is *defined* as the endpoints of the transport association.

So, basically:

"Application:  an entity that uses the transport layer for delivery of
data between the transport endpoints."

However, *every* protocol is trivially defined as:

	A mechanism between two or more parties to exchange data
	(information) between those parties.

I.e., as a result, an app is defined EXACTLY and ONLY by the following:

	Application: an entity that *uses* a transport layer.

Every other part of the definition is irrelevant, IMO.

Joe