Re: [AVTCORE] Fwd: I-D Action: draft-lennox-avtcore-rtp-topo-offer-answer-00.txt

"Roni Even" <ron.even.tlv@gmail.com> Sun, 11 March 2012 23:07 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 522C221F85D2 for <avt@ietfa.amsl.com>; Sun, 11 Mar 2012 16:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.445
X-Spam-Level:
X-Spam-Status: No, score=-1.445 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_BELOW2=2.154, RCVD_IN_DNSWL_LOW=-1]
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 fosRYrqRg7Zb for <avt@ietfa.amsl.com>; Sun, 11 Mar 2012 16:07:14 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 4DFCB21F85A4 for <avt@ietf.org>; Sun, 11 Mar 2012 16:06:54 -0700 (PDT)
Received: by wibhq7 with SMTP id hq7so2324849wib.13 for <avt@ietf.org>; Sun, 11 Mar 2012 16:06:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=he8TBZ975LVyuVc/qx+FaKVPeYipOo1zRxb3sp9Bug4=; b=jdYIl8h8WnTzaX49J+vvNUwCk6aUIYJZ0tG37X5JylaDeBkQsbkzirT/pFANqebqF8 JZ2x/y9HvVHJQS6gFNKRnkpQg9x9r5YaymscaCVdA9UCBklUXAl+UvNxx19+/gyUtA87 HKyDqV4Sa5eyXZTyxvDEVC2/RpZp3xfHojbyRWMROZW1rD5h+z8ujYdkM4bDQPeZwewr dlACGC+aAt6yLpCQ8JQRNrCf7wEqQ5kgjjfY9H6jGw803aiF9rPP2QPolnKWAvDfHQd9 e5VAysyj8jzUnNfcI7FQkPPbBQehsicV3nvyt9C649Fs5hRCw1ZYbmv1l8VgPGMle6Sc rWJg==
Received: by 10.180.99.65 with SMTP id eo1mr22400969wib.13.1331507213380; Sun, 11 Mar 2012 16:06:53 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-219-130.red.bezeqint.net. [79.179.219.130]) by mx.google.com with ESMTPS id d7sm49132325wiz.6.2012.03.11.16.06.51 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 11 Mar 2012 16:06:52 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Jonathan Lennox'" <jonathan@vidyo.com>, "'IETF AVTCore WG'" <avt@ietf.org>
References: <20120305215535.22939.91509.idtracker@ietfa.amsl.com> <3A00EA94-E3D3-404A-8283-599D156481D8@vidyo.com>
In-Reply-To: <3A00EA94-E3D3-404A-8283-599D156481D8@vidyo.com>
Date: Mon, 12 Mar 2012 01:06:03 +0200
Message-ID: <4f5d300c.0755b40a.44ab.ffffc16a@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acz+UKR6NWmv24w7TpinCrioOF59zABh5Nzw
Content-Language: en-us
Subject: Re: [AVTCORE] Fwd: I-D Action: draft-lennox-avtcore-rtp-topo-offer-answer-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Mar 2012 23:07:15 -0000

Hi Jonathan,
I read the draft and I assume you are talking about a relay architecture
without signaling, is this the case, is it only for point to point?
If the Topo-Transport-Translator need also to relay to multiple parties you
need also for SRTP to discuss the key distribution and synchronization since
not all parties join at the same time. This is discussed in
drafty-ietf-avt-srtp-ekt.

As for the offer answer discussion in section 4 the central box can enforce
a single view which it calls the common mode. The participants who cannot
support this common mode are second class participants. The assumption is
that there will be at least a common audio mode (used to be G.711) or in
RTCWeb the mandatory audio codec so second class participants will have the
audio connection. The assumption is that most of the parameters you
specified in section 4 are not fixed values but maximum values and any value
bellow it is also supported.

I think that another issue that should be discussed in the topo-offer-answer
is how the offer size scales if there are multiple streams and if the SSRC
attribute is used to distribute the list of all participants for source
selection. You have some information in
draft-lennox-mmusic-sdp-source-selection but it does not discuss the issue
of the offer size. 

Roni Even 

> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Jonathan Lennox
> Sent: Saturday, March 10, 2012 1:59 AM
> To: IETF AVTCore WG
> Subject: [AVTCORE] Fwd: I-D Action: draft-lennox-avtcore-rtp-topo-
> offer-answer-00.txt
> 
> Hi, all -- I've submitted this draft discussing the interaction of SDP
> Offer/Answer with RTP topologies -- specifically, why the RTP topology
> Topo-Transport-Translator can't be created with offer/answer, and why
> this is actually a good thing.
> 
> This is a generalization of a some issues that came up in the
> discussion of BUNDLE in Taipei.
> 
> Comments are welcome.
> 
> Begin forwarded message:
> 
> > From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> > Date: March 5, 2012 4:55:35 PM EST
> > To: "i-d-announce@ietf.org" <i-d-announce@ietf.org>
> > Subject: I-D Action: draft-lennox-avtcore-rtp-topo-offer-answer-
> 00.txt
> > Reply-To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >
> > 	Title           : Real-Time Transport Protocol (RTP) Topology
> Considerations for Offer/ Answer-Initiated Sessions.
> > 	Author(s)       : Jonathan Lennox
> > 	Filename        : draft-lennox-avtcore-rtp-topo-offer-answer-
> 00.txt
> > 	Pages           : 11
> > 	Date            : 2012-03-05
> >
> >   This document discusses a number of considerations related to the
> >   topologies of Real-Time Transport Protocol (RTP) sessions initated
> >   using the Session Description (SDP) unicast Offer/Answer Model,
> >   especially as applied to source-multiplexed sessions.
> >
> >   The primary observation is that certain topologies cannot be
> created
> >   by unicast SDP Offer/Answer.  Notably, the it is not possible to
> >   negotiate the topology that RFC 5117 calls Topo-Transport-
> Translator
> >   (or "relay").
> >
> >   As a consequence of this limitation, certain topological
> assumptions
> >   can safely be made for RTP sessions initiated using unicast SDP
> >   Offer/Answer; and therefore, certain optimizations to RTP are
> >   possible in such sessions.  This document also describes the
> >   optimizations that these assumptions make possible.
> >
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-lennox-avtcore-rtp-topo-
> offe
> > r-answer-00.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> > ftp://ftp.ietf.org/internet-drafts/draft-lennox-avtcore-rtp-topo-
> offer
> > -answer-00.txt
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> 
> --
> Jonathan Lennox
> jonathan@vidyo.com
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt