Re: [MMUSIC] BUNDLE: RTP only?

Eric Rescorla <ekr@rtfm.com> Sun, 17 February 2013 00:08 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD30921F8A71 for <mmusic@ietfa.amsl.com>; Sat, 16 Feb 2013 16:08:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.791
X-Spam-Level:
X-Spam-Status: No, score=-102.791 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 0aS+w3qD3-c9 for <mmusic@ietfa.amsl.com>; Sat, 16 Feb 2013 16:08:11 -0800 (PST)
Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by ietfa.amsl.com (Postfix) with ESMTP id 1954221F8A6F for <mmusic@ietf.org>; Sat, 16 Feb 2013 16:08:11 -0800 (PST)
Received: by mail-qe0-f46.google.com with SMTP id 1so1949642qec.5 for <mmusic@ietf.org>; Sat, 16 Feb 2013 16:08:08 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-originating-ip:in-reply-to:references :from:date:message-id:subject:to:cc:content-type:x-gm-message-state; bh=6/5qyYUCFzGajqB7/T8+tbeuzM3G7z10g6x1QsxvfcY=; b=PHq0rGSCzL1tkgut7j6GLRDjCnxpL7UJ1DL/vQrvpjcqhogkoYSpoGI22MCFStug/s yf3a2+5BNTuhPln+QzwWpz/FzFCqgeMzuAMWw880ruKNlrYZnEbbAYWNmLKtuHXz95/T sXAZtBEEd+GXZfu5yRN7mtarL5jktxbRH8wQp8dktozPZ1yc1fu/mXx6TuPCh72gEy0V 8MqO4K+Q/RcQ8JVr3zXAgdIP0ENTGZYXNJzy94rFr7qyhACHKlRozZsP9SfE+NObWZl/ ec+k6dhM2h0Mvz+BsASssfdAtGMFZH1iFTy4//3GlubxEPRvrIUAGouYqhZK9+M3tDSH honA==
X-Received: by 10.49.127.101 with SMTP id nf5mr3050285qeb.20.1361059688543; Sat, 16 Feb 2013 16:08:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.49.28.230 with HTTP; Sat, 16 Feb 2013 16:07:28 -0800 (PST)
X-Originating-IP: [74.95.2.173]
In-Reply-To: <201302152222.r1FMMUpo1903639@shell01.TheWorld.com>
References: <7594FB04B1934943A5C02806D1A2204B0D8131@ESESSMB209.ericsson.se> <511BF229.1090702@alum.mit.edu> <201302141953.r1EJrMT01840535@shell01.TheWorld.com> <7594FB04B1934943A5C02806D1A2204B0D8A67@ESESSMB209.ericsson.se> <511D6A75.2030507@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B0D8CE4@ESESSMB209.ericsson.se> <CAL02cgR-=UbKPB8jQLGBapN3T8sWEFZ_4hWduofpuAu=Go50mA@mail.gmail.com> <511E8401.7010907@alum.mit.edu> <201302152222.r1FMMUpo1903639@shell01.TheWorld.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 16 Feb 2013 16:07:28 -0800
Message-ID: <CABcZeBMTwe5oWxMrAkg+nDoB6iQfxpM=u8Jr4PLH+T0eWxbboA@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="047d7b6dc0bc40f6d204d5e067d1"
X-Gm-Message-State: ALoCoQl5tkkHm5HvNkDxVbe6zE1MtQRDeJIl/RY2zPDyhY4ggiFfwcwmt+ZHgdrq1qxtSqH7iSz1
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] BUNDLE: RTP only?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 17 Feb 2013 00:08:12 -0000

Dale,

I had assumed that the layering diagram looked as follows:

     SCTP
     DTLS    SRT(C)P       STUN
               UDP


This means that the demux problem becomes something like

- If packet is STUN, forward to ICE stack.
- If packet is SRT(C)P:
  + Primary demux on payload type
  + Secondary demux on SSRC
- If packet is DTLS
  + Demux SCTP associations by port number
    . SCTP streams are demuxed by stream ID

1. The first level of demux is described in RFC 5764 S 5.1.2.
2. The SRT(C)P demux appears to be specified in:
   http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-01
3. SCTP over DTLS encapsulation (and the elevant muxing) appears to
   be specified in:
   http://tools.ietf.org/id/draft-tuexen-tsvwg-sctp-dtls-encaps-01.txt
   and since the port is part of SCTP, this seems straightforward
   if we wish to allow it.


Obviously, one could, as you suggest, tunnel everything over SCTP,
but this seems like it would be less efficient in terms of bandwidth
(since you would add a bunch of headers to the RTP) and would also
be less compatible with existing SRTP endpoints.

Best,
-Ekr










On Fri, Feb 15, 2013 at 2:22 PM, Dale R. Worley <worley@ariadne.com> wrote:

> The problem is divisible into two parts.  One part is just clarifying
> what needs to be supported.  The second, harder part is specifying all
> the mechanisms.
>
> When multiplexing, we have to establish:
>
> 1. What is the nature of the constituent data streams that can be
>    multiplexed?
>
> 2. What method is used to multiplex the constituents?  Does there need
>    to be an encapsulation protocol?
>
> 3. What method is used to demultiplex the incoming PDUs of the
>    multiplexed data?
>
> 4. What carrier protocol is used to carry the multiplexed data?
>
> 5. How will we signal whatever information is needed to control the
>    demultiplexing process?  (This is affected by any need to
>    interoperate with existing systems.)
>
> 6. Where in the stack of protocols do we apply encryption, and what is
>    its nature?
>
> Items 1 and 3 are the ones that are most constrained by the
> requirements of the situation.
>
> As far as I can tell from what I've seen, the nature of the
> constituent data streams is:
>
> - the RTP or SRTP traffic arising from zero or more SDP media
>   descriptions (Here we assume that it is important when
>   demultiplexing RTP that it is important to identify the correct
>   constituent media description for each incoming RTP packet; that RTP
>   cannot be interpreted except in the context of the correct media
>   description.)
>
> - the corresponding RTCP or Secure RTCP traffic (assuming we want to
>   have RTP/RTCP multiplexing)
>
> - the data carried over a single SCTP connection (which includes a
>   number of SCTP streams), or possibly more than one SCTP connection
>   if that is to be supported (It is not clear if the multiplexing
>   process has access to the data in the individual SCTP streams, or
>   whether the constituent data stream is the packets generated by
>   SCTP's multiplexing process, or whether it must handle the packets
>   generated by DTLS encrypting the SCTP packets.)
>
> The carrier protocol seems to be assumed to be UDP supplemented by the
> STUN and ICE traffic needed to support a UDP association with the
> far-end.  However there may be value in using SCTP-over-DTLS-over-UDP
> as the carrier protocol.
>
> In regard to encryption, it would be more efficient to apply
> encryption only to the multiplexed data.  That suggests that the
> constituent data is unencrypted: RTP instead of SRTP, SCTP instead of
> DTLS/SCTP.
>
> There tends to be an assumption that the demultiplexing process is
> trivial, that all incoming PDUs can be identified and routed to their
> correct destinations without any additional encapsulation
> information.  We might be lucky enough that that is true, but it is
> not the common case.
>
> Dale
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>