Re: [rtcweb] SRTP/AVPF/TCP in draft-ietf-rtcweb-transports-01

Harald Alvestrand <harald@alvestrand.no> Thu, 03 October 2013 15:27 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA7821F8E85 for <rtcweb@ietfa.amsl.com>; Thu, 3 Oct 2013 08:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y3kPZS5bW2kj for <rtcweb@ietfa.amsl.com>; Thu, 3 Oct 2013 08:27:32 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 18EFD21F8EEA for <rtcweb@ietf.org>; Thu, 3 Oct 2013 08:20:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7A94E39E4AB; Thu, 3 Oct 2013 17:20:16 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pE70AVUlf7vw; Thu, 3 Oct 2013 17:20:15 +0200 (CEST)
Received: from [10.0.0.100] (unknown [205.164.11.246]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id DB38739E27D; Thu, 3 Oct 2013 17:20:14 +0200 (CEST)
Message-ID: <524D8B2C.7050606@alvestrand.no>
Date: Thu, 03 Oct 2013 17:20:12 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <006401cebf96$7db7a4f0$7926eed0$@co.in>, <524C7FD8.1050801@alvestrand.no> <ro3xdjcv7wkbl37rttggv2qu.1380777749933@email.android.com>
In-Reply-To: <ro3xdjcv7wkbl37rttggv2qu.1380777749933@email.android.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------070606000408090102030006"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] SRTP/AVPF/TCP in draft-ietf-rtcweb-transports-01
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Oct 2013 15:27:51 -0000

On 10/03/2013 07:22 AM, Magnus Westerlund wrote:
> Harald, 
>
> Yes you are missing something. The registry you pointed at are the one for RTP profiles. The one containing the combinations with transport are SDP specific. 
>
> http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xhtml#sdp-parameters-2

Thanks!

For consistency's sake, shouldn't all the SDP parameters that contain
"RTP" also be listed in the RTP registry?

I'm thinking that -transport- may have to grow an IANA section that
registers TCP/RTP/SAVPF, and it needs to decide whether to register it
in one or both.

(Of course, the TCP/ prefix is only used in some of the examples in the
RFC defining RTP over TCP - as a matter of taste, I don't like having
protocol in the profile name, so would be happy not doing so if the SDP
experts say this is OK by the rules, but then I need to adjust the
language to not use the word "profile" in this place.)