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

"Fred Baker (fred)" <fred@cisco.com> Wed, 21 May 2014 06:40 UTC

Return-Path: <fred@cisco.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 6B1A01A040A for <ietf-privacy@ietfa.amsl.com>; Tue, 20 May 2014 23:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.151
X-Spam-Level:
X-Spam-Status: No, score=-115.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 Z-D_62zRgbSq for <ietf-privacy@ietfa.amsl.com>; Tue, 20 May 2014 23:40:16 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B31381A0246 for <ietf-privacy@ietf.org>; Tue, 20 May 2014 23:40:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3537; q=dns/txt; s=iport; t=1400654416; x=1401864016; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=u70bmPizi0rkCsB40xISnPtRYlsytcGYIsVbdWuw04c=; b=LZZMGwHI/q5l8/qyX+lLUbhJb99oaflKqvhR4w/YpmAY01kaVNxJYGCi KL464CLm9Lpl9ItMuvHabSNYZ1g5vNCAoenEQ31hs8nbfrJv1XFVJF4Un m5OYYsaXyglhUc/U6UyhZvV1FXJ2KsWqV7sh5vuUIT5zJ7qePe8n6hJK7 g=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAMNJfFOtJV2d/2dsb2JhbABZgkJEUVjEIgGBFxZ0giUBAQEDAXkFCwIBCARCMiUBAQQOBQ6IKwjVIheOTgeDK4EVAQORSYE6hmqTJIM4gjA
X-IronPort-AV: E=Sophos;i="4.98,878,1392163200"; d="asc'?scan'208,217";a="326689380"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 21 May 2014 06:39:48 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s4L6dmss002675 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 21 May 2014 06:39:48 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.239]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Wed, 21 May 2014 01:39:48 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Christian Huitema <huitema@huitema.net>
Thread-Topic: [ietf-privacy] Checking an old protocol, RTSP
Thread-Index: Ac90vHqjvVSsFvwpQB6xlAd7yzylIgALNpkA
Date: Wed, 21 May 2014 06:39:48 +0000
Message-ID: <D4192F6C-3B06-461F-8608-DC602BDE468A@cisco.com>
References: <01e601cf74bd$bdf51430$39df3c90$@huitema.net>
In-Reply-To: <01e601cf74bd$bdf51430$39df3c90$@huitema.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.123]
Content-Type: multipart/signed; boundary="Apple-Mail=_55DECD3C-9382-4BC0-B215-B3FC90E2B37B"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-privacy/Gj-vgvxZJBwmC-GNjK52cruLios
Cc: "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>, "schulzrinne@cs.columbia.edu" <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 06:40:18 -0000

On May 20, 2014, at 11:27 PM, Christian Huitema <huitema@huitema.net> 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?
>  
> Also, RTSP was widely used in the 90’s. Is that still the case?

You could take a look at RFC 4567. It does not specify TLS or SSL; it defines a key exchange for SDP and RTSP.