IETF Logo Mail Archive

Re: [MMUSIC] Some more thoughts on the simulcast discussion

Jonathan Lennox <jonathan@vidyo.com> Thu, 15 October 2015 22:02 UTC

Return-Path: <prvs=2730449005=jonathan@vidyo.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 3737E1A6FEE for <mmusic@ietfa.amsl.com>; Thu, 15 Oct 2015 15:02:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level:
X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] autolearn=no
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 iLTegYhAdNYd for <mmusic@ietfa.amsl.com>; Thu, 15 Oct 2015 15:02:27 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A8391A6F57 for <mmusic@ietf.org>; Thu, 15 Oct 2015 15:02:26 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id t9FM14mb011067; Thu, 15 Oct 2015 18:02:22 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 1xenmhu7vd-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 15 Oct 2015 18:02:22 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Thu, 15 Oct 2015 17:02:21 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [MMUSIC] Some more thoughts on the simulcast discussion
Thread-Index: AQHRB5P9YYxQKAiotEaBtHoZ+HwElJ5tbvwA
Date: Thu, 15 Oct 2015 22:02:20 +0000
Message-ID: <512C38F4-AD60-419C-9BE8-5B7387B20059@vidyo.com>
References: <561DFFF3.5040703@alvestrand.no> <561E8A27.9000202@alum.mit.edu> <561EBAD5.1020502@alvestrand.no> <562010BF.8060306@nostrum.com> <56201405.4080106@alvestrand.no>
In-Reply-To: <56201405.4080106@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <9EA62E46DE78B54EB630A51A30FAA305@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33, 0.0.0000 definitions=2015-10-15_18:2015-10-15,2015-10-15,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1508030000 definitions=main-1510150272
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ySyb9pkAFuA_vSwVM4nARTFR7Y0>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Some more thoughts on the simulcast discussion
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Oct 2015 22:02:28 -0000

> On Oct 15, 2015, at 5:00 PM, Harald Alvestrand <harald@alvestrand.no> wrote:
> 
> [distraction: can two media streams have the same RID but different
> SSRCs? What does that mean if it's legal? Where do we enforce the
> restriction if it's illegal?]

I think only one encoded (or dependent) stream at a time can have a given RID value, but the mapping between RID and stream will change over time. (For the Selective Forwarding Unit RTP topology, it may change quickly, as in at speaker-switch speeds.)

However, a redundancy stream (FEC or RTX) will share the same RID value as the stream it’s protecting.

v2.23.0 | Report a Bug | By Email