[AVT] syncing sessions

Matthew Romaine <Matthew.Romaine@jp.sony.com> Mon, 27 June 2005 09:25 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmpre-0002qV-0B; Mon, 27 Jun 2005 05:25:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmprc-0002qQ-QE for avt@megatron.ietf.org; Mon, 27 Jun 2005 05:25:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28456 for <avt@ietf.org>; Mon, 27 Jun 2005 05:25:09 -0400 (EDT)
Received: from ns4.sony.co.jp ([137.153.0.44]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DmqGi-0007DF-GL for avt@ietf.org; Mon, 27 Jun 2005 05:51:10 -0400
Received: from mail20.sony.co.jp (mail20.sony.co.jp [43.0.1.220])
Received: from mail20.sony.co.jp (localhost [127.0.0.1]) by mail20.sony.co.jp (R8/Sony) with ESMTP id j5R9OjDs012478 for <avt@ietf.org>; Mon, 27 Jun 2005 18:24:45 +0900 (JST)
Received: from jptkyxim01.jp.sony.com (jptkyxim01.jp.sony.com [43.15.17.87]) by mail20.sony.co.jp (R8/Sony) with ESMTP id j5R9OjAS012472 for <avt@ietf.org>; Mon, 27 Jun 2005 18:24:45 +0900 (JST)
Received: from jptkyxwa03.jp.sony.com ([43.15.31.3]) by jptkyxim01.jp.sony.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 27 Jun 2005 18:24:45 +0900
Received: from [43.13.117.153] ([43.13.117.153]) by jptkyxwa03.jp.sony.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 27 Jun 2005 18:24:44 +0900
Mime-Version: 1.0 (Apple Message framework v721)
Content-Transfer-Encoding: 7bit
Message-Id: <F5DC0AC0-9790-4283-8783-35A002D58A10@jp.sony.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: avt@ietf.org
From: Matthew Romaine <Matthew.Romaine@jp.sony.com>
Date: Mon, 27 Jun 2005 18:23:14 +0900
X-Mailer: Apple Mail (2.721)
X-OriginalArrivalTime: 27 Jun 2005 09:24:44.0852 (UTC) FILETIME=[0E325740:01C57AFA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Subject: [AVT] syncing sessions
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org

fellow avt-ers,

I've got a question about synchronizing multiple sessions related to  
a single payload format.

I am working on a payload format which will support separation of  
data into "required" and "enhancements" categories - aka a variant on  
scalable streaming. In addition to sending all frame-based data over  
one session, I would like to support sending over two sessions  
(necessary data on one session, enhancement data on a second session).

I'm sure this isn't anything new for many of you, but my Google chops  
aren't serving me very well so I thought I would seek some pointers/ 
suggestions on payloads to use as a reference.  (Not to mention using  
an RFC as a reference last time was a mistake :)

My main question is how to specify how one session "belongs" to  
another - i.e., is there an SDP exchange to let a client calculate  
which two receiving-end ports need to be "associated"? Or is this all  
strictly an application-level implementation issue? (there is enough  
data in each payload for a client to realize which session they are  
dealing with (required or enhancement)).

appreciate any comments, pointers, etc.

thanks


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt