Re: [AVTCORE] RTP Topology addition (was: Design choice comments..._

"David Benham (dbenham)" <dbenham@cisco.com> Mon, 23 March 2015 17:55 UTC

Return-Path: <dbenham@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EF1E1AD060 for <avt@ietfa.amsl.com>; Mon, 23 Mar 2015 10:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 OfVHKYlUErQ0 for <avt@ietfa.amsl.com>; Mon, 23 Mar 2015 10:55:03 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C41E21AD05B for <avt@ietf.org>; Mon, 23 Mar 2015 10:55:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2620; q=dns/txt; s=iport; t=1427133302; x=1428342902; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=R9ONJlsCpdGZndVHOS4NUJXhGGkikuj4G9fEwlweJf4=; b=E2Lt4fhFJXe6LC/xvoNfL3YOQrsPu558JhwNACFliW3eWtc16dGzk9gE NbpyYk2LBcd4g4BHCue/XcL5VsgtUxh87xKz/v28bYeQoL9ojMFv42dfY W3QWWT3tnF8zo/zsaPn9nkSJJyem/C58B1LYO1u9PC36lzTBKe557oDPT 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ASBQANUxBV/5BdJa1cgwaBLASCRkbJNQIcgRFMAQEBAQEBfYQUAQEBAwEMFxFFBQkCAgEGAhUFAgYdAwICAhkXFAEQAQEEDgUIiB8IkWCcdpl0AQEBAQEBAQEBAQEBAQEBAQEBAQEBFwSBHYoAhEQWGweCaC+BFgEEhhiKN4sJgzCGaoICgyyDRyKCAhyBUG+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,453,1422921600"; d="scan'208";a="406343922"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-2.cisco.com with ESMTP; 23 Mar 2015 17:55:02 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t2NHt2hi022947 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 23 Mar 2015 17:55:02 GMT
Received: from xmb-aln-x10.cisco.com ([169.254.5.197]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Mon, 23 Mar 2015 12:55:01 -0500
From: "David Benham (dbenham)" <dbenham@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: RTP Topology addition (was: Design choice comments..._
Thread-Index: AdBk6YxRU3CTbOLcSASxJ1/yjwhcPwAWugkAABIV0dA=
Date: Mon, 23 Mar 2015 17:55:00 +0000
Message-ID: <0683D6CB32AC424D8AF52C0F660E5DC56B94BDEF@xmb-aln-x10.cisco.com>
References: <0683D6CB32AC424D8AF52C0F660E5DC56B9497A2@xmb-aln-x10.cisco.com> <550F8A3C.4060900@ericsson.com>
In-Reply-To: <550F8A3C.4060900@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.24.222.174]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/7HKgr5O29CQTDC6fzibo1eMCNeA>
Cc: 'IETF AVTCore WG' <avt@ietf.org>
Subject: Re: [AVTCORE] RTP Topology addition (was: Design choice comments..._
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2015 17:55:09 -0000

> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > That said, and to your RTP translator observation, wish to explore
> > adding another RTP topology called "RTP Translator Forwarding Switch
> > (RTFS)."   Channeling Steve Wenger's post shortly before IETF 91,  '
> > ..topologies document is never really done' or something like that.
> > Can I get this started and in to the topologies doc update?
> 
> As one of the authors of the document. Currently passed working group
> last call and updated and ready for publication request, I say maybe.
> But, please understand that we thought we was currently done.

Understood.   

> I think you need to start by actually describing in which way this RTFS
> is different from the RTP mixer or the SFM. Is this really different
> from what is already described, or simply a variant?

From the doc, the SFM appears to require, like the media switching mixer referenced, a collection of its own SSRCs (ie, terminating SSRCs on all legs), sending only a finite set of SSRC values downstream to any given recipient or a 'cascade link' to another box.   

Is an SFM allowed per the definition to reuse the senders/upstream SSRCs, sending a potentially unlimited set of SSRCs downstream/to any given recipient?  Is allowing that a variant or?


> Thus, please provide text to describe this thing you want to add.
> 
> Cheers
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Färögatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------