[AVTCORE] Fwd: I-D Action: draft-lennox-avtcore-rtp-topo-offer-answer-00.txt
Jonathan Lennox <jonathan@vidyo.com> Fri, 09 March 2012 23:59 UTC
Return-Path: <jonathan@vidyo.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 A456221F84D2 for <avt@ietfa.amsl.com>; Fri, 9 Mar 2012 15:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 tnpjnCohFWOI for <avt@ietfa.amsl.com>; Fri, 9 Mar 2012 15:59:22 -0800 (PST)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id 0E40B21F84BF for <avt@ietf.org>; Fri, 9 Mar 2012 15:59:22 -0800 (PST)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 60725553B25 for <avt@ietf.org>; Fri, 9 Mar 2012 18:59:21 -0500 (EST)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB023.mail.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id F2C3B553B5F for <avt@ietf.org>; Fri, 9 Mar 2012 18:59:20 -0500 (EST)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB023.mail.lan ([10.110.17.23]) with mapi; Fri, 9 Mar 2012 18:59:14 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: IETF AVTCore WG <avt@ietf.org>
Date: Fri, 09 Mar 2012 18:59:19 -0500
Thread-Topic: I-D Action: draft-lennox-avtcore-rtp-topo-offer-answer-00.txt
Thread-Index: Acz+UKR6NWmv24w7TpinCrioOF59zA==
Message-ID: <3A00EA94-E3D3-404A-8283-599D156481D8@vidyo.com>
References: <20120305215535.22939.91509.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [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: Fri, 09 Mar 2012 23:59:22 -0000
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-offer-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
- [AVTCORE] Fwd: I-D Action: draft-lennox-avtcore-r… Jonathan Lennox
- Re: [AVTCORE] Fwd: I-D Action: draft-lennox-avtco… Roni Even
- [AVTCORE] RTPTOPO & H.248; RE: Fwd: I-D Action: d… Schwarz, Albrecht (Albrecht)