Re: [rtcweb] Symmetric RTP and uni-directional media streams

Bernard Aboba <bernard_aboba@hotmail.com> Thu, 01 September 2011 14:34 UTC

Return-Path: <bernard_aboba@hotmail.com>
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 635D021F9B9F for <rtcweb@ietfa.amsl.com>; Thu, 1 Sep 2011 07:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.357
X-Spam-Level:
X-Spam-Status: No, score=-102.357 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 mmTtQpBDx3lG for <rtcweb@ietfa.amsl.com>; Thu, 1 Sep 2011 07:34:01 -0700 (PDT)
Received: from blu0-omc1-s4.blu0.hotmail.com (blu0-omc1-s4.blu0.hotmail.com [65.55.116.15]) by ietfa.amsl.com (Postfix) with ESMTP id 9368D21F9B7E for <rtcweb@ietf.org>; Thu, 1 Sep 2011 07:34:01 -0700 (PDT)
Received: from BLU152-W48 ([65.55.116.8]) by blu0-omc1-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 1 Sep 2011 07:35:30 -0700
Message-ID: <BLU152-W4804B1F5789AF22A6C562593190@phx.gbl>
Content-Type: multipart/alternative; boundary="_54cfd690-8d79-460a-8acd-d5cf65abd6f2_"
X-Originating-IP: [98.203.198.61]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <harald@alvestrand.no>, <christer.holmberg@ericsson.com>
Date: Thu, 1 Sep 2011 07:35:30 -0700
Importance: Normal
In-Reply-To: <4E5F6CEF.6020203@alvestrand.no>
References: <7F2072F1E0DE894DA4B517B93C6A05852233DD0AC8@ESESSCMS0356.eemea.ericsson.se>, <4E5F6CEF.6020203@alvestrand.no>
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Sep 2011 14:35:30.0905 (UTC) FILETIME=[6671FC90:01CC68B4]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Symmetric RTP and uni-directional media streams
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, 01 Sep 2011 14:34:02 -0000

I think Christer's question related to the following text from the W3C WEBRTC editor's draft (http://dev.w3.org/2011/webrtc/editor/webrtc.html) Section 4:

All streams represented by MediaStream objects must be
  marked as "sendonly" by the peer that initially adds the stream to
  the session. The PeerConnection API does not support
  bidirectional ("sendrecv") audio or video media streams. [SDPOFFERANSWER]

  
Date: Thu, 1 Sep 2011 13:30:55 +0200
From: harald@alvestrand.no
To: christer.holmberg@ericsson.com
CC: rtcweb@ietf.org
Subject: Re: [rtcweb] Symmetric RTP and uni-directional media streams



  


    
  
  
    On 09/01/11 13:23, Christer Holmberg wrote:
    
      
      
      
      
      
         
        Hi,
         
        There has been
            much talk about the usage of symmetric RTP. Also,
            draft-perkins-rtcweb-rtp-usage suggests that symmetric RTP
            is required.
         
        However, the
            PeerConnection API currently only supports the establishment
            of uni-directional streams, so for a single two way
            communication one needs to create two separate
            uni-directional streams.
         
        So, I assume
            that one requirement from RTCWEB to W3C will be to add
            support of the establishment of bi-directional streams to
            the PeerConnection API.
      
    To be precise:

    

    I think (and we're implementing) that between two PeerConnections,
    there will be a small number of *RTP sessions*  (ideally one). These
    will be bidirectional.

    

    These will be used for transporting any number of *MediaStreams* (a
    WEBRTC API concept), each of which corresponds to a CNAME (RTP
    protocol concept). These are unidirectional.

    

    So the right answer is "yes" and "no", as far as I can see.

    
         
        Regards,
         
        Christer
         
         
      
      
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

    
    

  


_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb