Re: [MMUSIC] Bundle offer with different ports - where to expect media?

Emil Ivov <emcho@jitsi.org> Mon, 20 May 2013 12:12 UTC

Return-Path: <emil@sip-communicator.org>
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 332D821F9298 for <mmusic@ietfa.amsl.com>; Mon, 20 May 2013 05:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ad0RL5fOcJ-o for <mmusic@ietfa.amsl.com>; Mon, 20 May 2013 05:12:46 -0700 (PDT)
Received: from mail-bk0-x230.google.com (mail-bk0-x230.google.com [IPv6:2a00:1450:4008:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 18E5021F925A for <mmusic@ietf.org>; Mon, 20 May 2013 05:12:45 -0700 (PDT)
Received: by mail-bk0-f48.google.com with SMTP id jf3so3455044bkc.21 for <mmusic@ietf.org>; Mon, 20 May 2013 05:12:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=g+kZ1TevMpzVUkF9Id1zAtYRwMO3KLNYkPOEiCVJsY8=; b=ZLCnFVeuesv9Xekj5wN7hzET8tcOl+NGH5+2oS8XxK69b1HcJ18ZT20bhb3ow0f0Ce GAlEssOvKzyFtANcb4VldwxkmTMeqg08vCmiJhTIMs2gmZYzbA3dgtNy9qHWzk9s2e5Z 3Hmzxi6o7wDPb5XMrmOIOJdtnH43ZsQGjpRHFi7JOVAi0wx+lnZ78EJRhFeTtVWsJhNM DUCQ0JIACho0FgG6aRQYbPYLGVPmVfGrvnqNX/XWq0NK47n6aWpsBVbG6hkZSNjJk9z5 Tx0lxS8cNkm3BYug55WtyFc5xVSTb+Evs7YVs5rDxKunHgwBG2gMt6rNVDiLV9CGrQPP 0i3w==
X-Received: by 10.205.44.129 with SMTP id ug1mr19267452bkb.29.1369051964762; Mon, 20 May 2013 05:12:44 -0700 (PDT)
Received: from [192.168.43.3] ([212.5.158.160]) by mx.google.com with ESMTPSA id b12sm130673bkz.0.2013.05.20.05.12.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 05:12:43 -0700 (PDT)
Message-ID: <519A1336.9010001@jitsi.org>
Date: Mon, 20 May 2013 15:12:38 +0300
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1C374357@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C374357@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnflvv69r/u98L9vEK2tUIjBD5dgAEb7qORV+8SAP/8BSAsPCDWzp9sQ92Dx+VgdcnM0xYv
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Bundle offer with different ports - where to expect media?
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: Mon, 20 May 2013 12:12:47 -0000

Hey Christer,

On 20.05.13, 14:43, Christer Holmberg wrote:
> Hi, 
> 
> Currently BUNDLE defines that the first offer is sent with separate port
> numbers (later, if the answerer has indicated support of BUNDLE, the
> offerer will send a second offer, with identical port numbers).
> 
> Some people have indicated that the offerer shall be able to receive
> data already when the first offer has been sent. The question is on
> which port(s) it needs to be able to receive media.

Do we really have a choice here? We send the offer with different port
numbers so that it would work with endpoints that have no knowledge of
bundle. Such endpoints can start streaming media to any port. Bundled
devices can, on the other hand, start streaming media on the bundle port.

So in other words, the offerer need to expect media arriving on any port
just as it needs to expect any stream arriving on the bundle port.

This would be consistent with what we do for rtcp-mux.

Emil


> 
>  
> 
> -          Some have suggested the port of the first non-zero m- line
> within the offered bundle group.
> 
> -          Some have suggested ANY port
> 
>  
> 
>  
> 
> The issue with assuming the first non-zero m- line is that the answerer
> in the answer may reject it (put the port to zero), or remove it from
> the bundle group (which people seem to want to allow). In both cases it
> would be strange to assume the first m- line.
> 
>  
> 
> Now, in case e.g. ICE is used, the offerer will be able to send the
> second offer before any media is received to begin with. But, the
> offerer could still receive STUN connectivity checks on any of the
> ports, until the second offer has been sent.
> 
>  
> 
> We need text in BUNDLE about this, so comments/inputs are welcome :)
> 
>  
> 
> Regards,
> 
>  
> 
> Christer
> 
>  
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> 

-- 
https://jitsi.org