Re: [ietf-privacy] Checking an old protocol, RTSP

Martin Stiemerling <mls.ietf@gmail.com> Wed, 21 May 2014 07:24 UTC

Return-Path: <mls.ietf@gmail.com>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4395B1A0484 for <ietf-privacy@ietfa.amsl.com>; Wed, 21 May 2014 00:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 wZDOVlMEarI0 for <ietf-privacy@ietfa.amsl.com>; Wed, 21 May 2014 00:24:46 -0700 (PDT)
Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com [IPv6:2a00:1450:4013:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 882651A0469 for <ietf-privacy@ietf.org>; Wed, 21 May 2014 00:24:46 -0700 (PDT)
Received: by mail-ee0-f52.google.com with SMTP id e53so1247297eek.39 for <ietf-privacy@ietf.org>; Wed, 21 May 2014 00:24:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6vIBvNAzJ0ZBIJV66EmXkPYaHuOqP/+DaI+Lo5ueJRQ=; b=ttuVCZ/89rvtcWw9lhHOUrxBP1deqJkhRtGaANEG0DINyyBTTDNHkCaxGiYy5mMfKQ ZC5TiBSreJ0bGf4k0aNrr+ka/OLIE/f/XXlDmtfOEm0zXGbE8VsIqpKogvCpXBAnisUV KHfuk+6Ly2eyaw9mThxzZRLn7cjTjfF2I0IGqR/Owuxn46HYOBDIzjrjEJ9d99mtEIKU m5j8lo25zTdVGJIZvT27V3+6jquixjIWDNGLx6Z2U8szSC+L/m3lMA1XsisgQf5+aigz bxw4FbH0m3p6WvAlmtTv8fGP7k8J3ewARFzUsl546IHK8cMnxX5+rAd5kozpY/ztpb1s LDSQ==
X-Received: by 10.14.114.69 with SMTP id b45mr1234958eeh.69.1400657084444; Wed, 21 May 2014 00:24:44 -0700 (PDT)
Received: from ?IPv6:2001:1a80:2804:a00:b59f:cdde:81c6:fca6? ([2001:1a80:2804:a00:b59f:cdde:81c6:fca6]) by mx.google.com with ESMTPSA id g8sm9692709eep.0.2014.05.21.00.24.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 21 May 2014 00:24:43 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Martin Stiemerling <mls.ietf@gmail.com>
In-Reply-To: <01e601cf74bd$bdf51430$39df3c90$@huitema.net>
Date: Wed, 21 May 2014 09:24:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB17078D-76BD-4EC6-AB33-2ACF5B6ACF07@gmail.com>
References: <01e601cf74bd$bdf51430$39df3c90$@huitema.net>
To: Christian Huitema <huitema@huitema.net>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-privacy/AvZuJjAlX2Wf6-vJ_heVb-FsaYQ
Cc: ietf-privacy@ietf.org, schulzrinne@cs.columbia.edu
Subject: Re: [ietf-privacy] Checking an old protocol, RTSP
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 May 2014 07:24:48 -0000

Hi Christian, 

Am 21.05.2014 um 08:27 schrieb Christian Huitema <huitema@huitema.net>et>:

> I am currently taking a look at RFC 2326: Real Time Streaming Protocol. The design of RTSP/1.0 is pretty close to that of HTTP/1.0, with very similar security and privacy considerations, but RTSP did not evolve as quickly as HTTP. In particular, I cannot find a profile for running RTSP over SSL or TLS in the RFC series. Is that defined elsewhere?

I don’t think so, but there is an updated version of RTSP 1.0 which is RTSP 2.0 and this is in the RFC editor’s queue (https://ietf.org/doc/draft-ietf-mmusic-rfc2326bis/). RTSP 2.0 has support for TLS, actually it is MTI.

>  
> Also, RTSP was widely used in the 90’s. Is that still the case?

It is still in closed environments, such as cable networks, but much less on the public Internet.

Pure HTTP and Dynamic Adaptive Streaming over HTTP (DASH) is what is used across  the public Internet for video streaming by today. 

  Martin

>  
> -- Christian Huitema
>  
>  
> _______________________________________________
> ietf-privacy mailing list
> ietf-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-privacy