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

In any case the issues go beyond switching - any MANE that modifies the sequence number or SSRC field will have a problem, regardless of whether supports switching or not.

> On Mar 23, 2015, at 6:41 AM, Roni Even <ron.even.tlv@gmail.com> wrote:
> 
> Hi,
> My concerns were not about the term translator but like Magnus is saying lack of  a description of this entity you defining.
> I also think that the name "switched conferencing environment" is not correct you are only talking about switched media and not conference. Conference has more aspects than just media switching (e.g. conference control,..) which are as you say out of scope. 
> 
> Roni
> 
>> -----Original Message-----
>> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
>> Sent: 23 March, 2015 5:36 AM
>> To: David Benham (dbenham); Roni Even; 'IETF AVTCore WG'
>> Subject: Re: RTP Topology addition (was: Design choice comments..._
>> 
>> On 2015-03-22 16:45, David Benham (dbenham) wrote:
>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com] To me when looking at
>>>> what is called switching conference server it seems that this is not
>>>> a conference server but maybe just an some sort of RTP translator or
>>>> maybe what we called a media server (RFC5576 section
>>>> 6)
>>> 
>>> First and foremost, we've been wanting to work on the security-centric
>>> requirements and not prematurely limit the RTP
>>> topologies.   To that end, and at the risk of pre-empting the
>>> discussion during agenda, we'll propose a design team meet to discuss
>>> ways to convey elements of cryptographic context that is as friendly
>>> to as many RTP topologies as possible.    Not unlike the design team
>>> focused on 'congestion management' issues and which meet back in Dec
>>> after IETF91.
>> 
>> Good.
>> 
>>> 
>>> 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.
>> 
>> 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?
>> 
>> 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
>> ----------------------------------------------------------------------
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt