IETF Logo Mail Archive

Re: [MMUSIC] Bundling data channel and RTP? - Text proposal

Martin Thomson <martin.thomson@gmail.com> Thu, 28 May 2015 23:06 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85CDA1ACDD3 for <mmusic@ietfa.amsl.com>; Thu, 28 May 2015 16:06:37 -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 U64UoqZy6ryE for <mmusic@ietfa.amsl.com>; Thu, 28 May 2015 16:06:36 -0700 (PDT)
Received: from mail-yh0-x22e.google.com (mail-yh0-x22e.google.com [IPv6:2607:f8b0:4002:c01::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 567E81ACD93 for <mmusic@ietf.org>; Thu, 28 May 2015 16:06:36 -0700 (PDT)
Received: by yhda23 with SMTP id a23so15281920yhd.2 for <mmusic@ietf.org>; Thu, 28 May 2015 16:06:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=x2dt6Zvf3gQJNnJW+x1LqAx8QQe9LrEOA/u3X5OnlJ4=; b=dyX6xJ3EljCDymxI+r6Pp/4l59xz8mS0N5c9almsTuJVIW9zCR0tg7fh2CWyCuOl5q gWV1fS7BpTa1isViusoZyDV8N0pUpM8jBNZfDRS6UMbpPC3d2ZKvv3u+493wqSs+ahbn BnOAa3uNqCG28G86bT16syNEJqcJevCxQC0gE5/nMePz4p6jEJ6sZiqlHQV48mGCfzDC HUD+w3fvaX5TIiRBHrjM5t47S+F4kqGcB7Fb0x4Lv3lDv9ReNaUZYSMYsS29UpXtBFht 92+J2V+KVTf8UoOU7nYBkNDYvmsd8GJldfwpYfDrHiwS31J3myMzyz23vz1y9MoIaaHc iHjQ==
MIME-Version: 1.0
X-Received: by 10.236.41.169 with SMTP id h29mr5266232yhb.100.1432854395764; Thu, 28 May 2015 16:06:35 -0700 (PDT)
Received: by 10.129.110.138 with HTTP; Thu, 28 May 2015 16:06:35 -0700 (PDT)
In-Reply-To: <CAD5OKxsu=uYqpFQ2Rko9gViCxRdiOudF6wbd618jy6CEFnjV_w@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B1D852384@ESESSMB209.ericsson.se> <55634C34.4080304@alum.mit.edu> <5565838D.2020005@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D866141@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E7D3EEB@US70UWXCHMBA02.zam.alcatel-lucent.com> <CAD5OKxuEpmMVfScf62bs=y+9PyYbejfa2OmsHYq=dStTZmjdVg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D8689E9@ESESSMB209.ericsson.se> <55665BFA.4020600@nteczone.com> <CAD5OKxsukfKG=bW-5QWu35AQQX_Eve8YM0cQ=xc=B=obnzKQdQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D86C915@ESESSMB209.ericsson.se> <547EE95EB794FD4DB8062F7A4C86D0BC4A36371A@FR712WXCHMBA13.zeu.alcatel-lucent.com> <CAD5OKxsu=uYqpFQ2Rko9gViCxRdiOudF6wbd618jy6CEFnjV_w@mail.gmail.com>
Date: Thu, 28 May 2015 16:06:35 -0700
Message-ID: <CABkgnnVonJPedgOdAPkia0D+W4HrUSLnHqjhm3ov6KCk0LiLfw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/fA7aLOexPDbCPzNTDjrF_xiHUSE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "pkyzivat@alum.mit.edu" <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Bundling data channel and RTP? - Text proposal
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2015 23:06:37 -0000

On 28 May 2015 at 16:01, Roman Shpount <roman@telurix.com> wrote:
> I am not the member of TLS working group and TLS 1.3 is still fairly early
> to completely specify how it operates. In particular, it does not include
> any mechanism for key material update. I am not 100% sure what is going to
> be supported there and if extensions can be added and removed for an
> existing DTLS session.

I expect that TLS 1.3 will specify a rekeying mechanism, but only for
its own records (in this context, that means SCTP).  Things that
depend on exporters (like DTLS-SRTP) will likely get a single, stable
value.

I agree with your analysis regarding use_srtp.  We certainly behave that way.

v2.23.0 | Report a Bug | By Email