IETF Logo Mail Archive

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

"David Benham (dbenham)" <dbenham@cisco.com> Sun, 22 March 2015 21:45 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 1968D1A1C05 for <avt@ietfa.amsl.com>; Sun, 22 Mar 2015 14:45:55 -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 15xNel2M2lYS for <avt@ietfa.amsl.com>; Sun, 22 Mar 2015 14:45:53 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E3B11A1C03 for <avt@ietf.org>; Sun, 22 Mar 2015 14:45:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1766; q=dns/txt; s=iport; t=1427060753; x=1428270353; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=4M/dPRBzKsrGCrY6f3LVeDjn5aJ0dMXc0iKUaEYkEFg=; b=gDHEGyAr+imB+DOEAFiKif01KOPue9CKm2S1TLOEmDRWRcNUufwxJhoA tVavr2KTM7l6IyXQ6mG88UNpcCG8978tkLB0VPIuzE71axARoVay1MwaB dzk7qk1Ik+9kBIqVqFruP6dRSnMsxc9XtaSbdHxs3/ybSdxB4R/w5DE9f k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANBQCiNw9V/5FdJa1cgwaBLASDDMlbAhyBAkwBAQEBAQF9hBQBAQEDASMRNBYNAQgOBAMFAgYdAwIEHxEUAQIPAQQBEgiIEwMJCK8ik2wNhUABAQEBAQEEAQEBAQEBHIEhigCCRoFYJoMgL4EWBZBPiCKCZ4oaggJMgmCDRyKCAhyBUG8BgQJBfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,447,1422921600"; d="scan'208";a="134390707"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-2.cisco.com with ESMTP; 22 Mar 2015 21:45:52 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t2MLjqkK024951 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 22 Mar 2015 21:45:52 GMT
Received: from xmb-aln-x10.cisco.com ([169.254.5.197]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Sun, 22 Mar 2015 16:45:51 -0500
From: "David Benham (dbenham)" <dbenham@cisco.com>
To: Roni Even <ron.even.tlv@gmail.com>, 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, 'IETF AVTCore WG' <avt@ietf.org>
Thread-Topic: RTP Topology addition (was: Design choice comments..._
Thread-Index: AdBk6YxRU3CTbOLcSASxJ1/yjwhcPw==
Date: Sun, 22 Mar 2015 21:45:51 +0000
Message-ID: <0683D6CB32AC424D8AF52C0F660E5DC56B9497A2@xmb-aln-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.24.224.163]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/cD6neQVgcZRAKetUcDO-sKjIwKs>
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: Sun, 22 Mar 2015 21:45:55 -0000

> 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.

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?

> So to summarize I would think that you describe an
> decomposed conference bridge and we can look at the work done in mediactrl
> WG for the architecture. 
> 
> Roni Even as individual
>

v2.23.0 | Report a Bug | By Email