Re: [rtcweb] DRAFT Agenda for RTCWEB

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Fri, 01 March 2013 23:09 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 D6CAA11E80BF for <rtcweb@ietfa.amsl.com>; Fri, 1 Mar 2013 15:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level:
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0WeXRfJgI1U for <rtcweb@ietfa.amsl.com>; Fri, 1 Mar 2013 15:09:12 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 30B5611E80BA for <rtcweb@ietf.org>; Fri, 1 Mar 2013 15:09:10 -0800 (PST)
Received: from [192.168.1.101] (p548197B9.dip.t-dialin.net [84.129.151.185]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 389581C0C0BC5; Sat, 2 Mar 2013 00:09:08 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <201303011957.r21JvLZG2849736@shell01.TheWorld.com>
Date: Sat, 2 Mar 2013 00:09:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF476556-87B9-4BD7-82EC-F4BA4F776B4F@lurchi.franken.de>
References: <CA+9kkMALouyyzN4dcGdF92TO2HGcBHbHR6fvHg7QC-x5ndCGjw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B10B717@ESESSMB209.ericsson.se> <03FBA798AC24E3498B74F47FD082A92F36EA7EAB@US70UWXCHMBA04.zam.alcatel-lucent.com> <201303011558.r21FwfGb2830347@shell01.TheWorld.com> <5EB4AF68-2BB3-4243-B759-249065D8815F@lurchi.franken.de> <201303011957.r21JvLZG2849736@shell01.TheWorld.com>
To: worley@ariadne.com (Dale R. Worley)
X-Mailer: Apple Mail (2.1283)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] DRAFT Agenda for RTCWEB
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: Fri, 01 Mar 2013 23:09:13 -0000

On Mar 1, 2013, at 8:57 PM, Dale R. Worley wrote:

>> From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
> 
>> As far as I understand it is easy (based on the first byte) to demux
>> DTLS from STUN and SRTP. SCTP is the only payload for DTLS, so there
>> is no need for demuxing. So no need to control SCTP ports. Or am I
>> missing something?
> 
> Controlling port numbers is needed if SCTP is *not* encapsulated in
> DTLS and yet has to be distinguished from RTP et al.  (That would
> become significant if encryption was applied to the bundle's packet
> stream as a whole, rather than to the constituent streams
> individually.)
Sorry, I don't understand what you are saying. Which document describes
the stack you are referring to? How would encryption be done for SCTP over UDP
over IP?

Best regards
Michael
> 
> Dale
>