[ietf-privacy] Checking an old protocol, RTSP
"Christian Huitema" <huitema@huitema.net> Wed, 21 May 2014 06:27 UTC
Return-Path: <huitema@huitema.net>
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 ECF1E1A027C for <ietf-privacy@ietfa.amsl.com>; Tue, 20 May 2014 23:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level:
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 55f9WA_Dp_la for <ietf-privacy@ietfa.amsl.com>; Tue, 20 May 2014 23:27:33 -0700 (PDT)
Received: from xsmtp02.mail2web.com (xsmtp22.mail2web.com [168.144.250.185]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C71191A0286 for <ietf-privacy@ietf.org>; Tue, 20 May 2014 23:27:33 -0700 (PDT)
Received: from [10.5.2.18] (helo=xmail08.myhosting.com) by xsmtp02.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1Wmzzv-0003Tz-1U for ietf-privacy@ietf.org; Wed, 21 May 2014 02:27:32 -0400
Received: (qmail 31613 invoked from network); 21 May 2014 06:27:30 -0000
Received: from unknown (HELO HUITEMA5) (Authenticated-user:_huitema@huitema.net@[72.235.170.205]) (envelope-sender <huitema@huitema.net>) by xmail08.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf-privacy@ietf.org>; 21 May 2014 06:27:29 -0000
From: Christian Huitema <huitema@huitema.net>
To: ietf-privacy@ietf.org
Date: Tue, 20 May 2014 23:27:27 -0700
Message-ID: <01e601cf74bd$bdf51430$39df3c90$@huitema.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01E7_01CF7483.11963C30"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: Ac90vHqjvVSsFvwpQB6xlAd7yzylIg==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-privacy/0mhp9hOMZts5yhjQ4OQY_tTxi58
Cc: schulzrinne@cs.columbia.edu
Subject: [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 06:27:36 -0000
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? Also, RTSP was widely used in the 90s. Is that still the case? -- Christian Huitema
- [ietf-privacy] Checking an old protocol, RTSP Christian Huitema
- Re: [ietf-privacy] Checking an old protocol, RTSP Fred Baker (fred)
- Re: [ietf-privacy] Checking an old protocol, RTSP Martin Stiemerling
- Re: [ietf-privacy] Checking an old protocol, RTSP Stephen Farrell
- Re: [ietf-privacy] Checking an old protocol, RTSP Magnus Westerlund