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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 21 May 2014 07:56 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 9D57C1A03A6 for <ietf-privacy@ietfa.amsl.com>; Wed, 21 May 2014 00:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 aVqBIen4AfTu for <ietf-privacy@ietfa.amsl.com>; Wed, 21 May 2014 00:56:12 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6076F1A0831 for <ietf-privacy@ietf.org>; Wed, 21 May 2014 00:56:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 2D2B5BE53; Wed, 21 May 2014 08:56:11 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iagujn5nLcev; Wed, 21 May 2014 08:56:09 +0100 (IST)
Received: from [193.1.136.127] (dhcp-c101887f.ucd.ie [193.1.136.127]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CE686BE51; Wed, 21 May 2014 08:56:09 +0100 (IST)
Message-ID: <537C5C19.6060908@cs.tcd.ie>
Date: Wed, 21 May 2014 08:56:09 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Christian Huitema <huitema@huitema.net>, ietf-privacy@ietf.org
References: <01e601cf74bd$bdf51430$39df3c90$@huitema.net>
In-Reply-To: <01e601cf74bd$bdf51430$39df3c90$@huitema.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-privacy/zSLooMhkojgcbjwExvfNSzZbi-c
Cc: 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:56:15 -0000


On 21/05/14 07:27, Christian Huitema wrote:
> 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 recall commenting on RTSP and TLS when we did IESG review of that.
Main comment I had (that I recall;-) was there's no equivalent of
HTTP CONNECT.

S.

> 
>  
> 
> Also, RTSP was widely used in the 90’s. Is that still the case?
> 
>  
> 
> -- Christian Huitema
> 
>  
> 
>  
> 
> 
> 
> 
> _______________________________________________
> ietf-privacy mailing list
> ietf-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-privacy
>