IETF Logo Mail Archive

Re: [maitai] Roles of Sender and Receiver

"Duckworth, Mark" <Mark.Duckworth@polycom.com> Thu, 02 December 2010 18:32 UTC

Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: maitai@core3.amsl.com
Delivered-To: maitai@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB8F43A69A8 for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 10:32:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NqbPXuP5Nqfj for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 10:32:56 -0800 (PST)
Received: from Crpehubprd01.polycom.com (crpehubprd01.polycom.com [140.242.64.158]) by core3.amsl.com (Postfix) with ESMTP id 100DD3A6972 for <maitai@ietf.org>; Thu, 2 Dec 2010 10:32:53 -0800 (PST)
Received: from Crpmboxprd01.polycom.com ([fe80::e001:c7b0:91a1:9443]) by Crpehubprd01.polycom.com ([fe80::27:216a:613a:350c%13]) with mapi; Thu, 2 Dec 2010 10:34:09 -0800
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "maitai@ietf.org" <maitai@ietf.org>
Date: Thu, 02 Dec 2010 10:34:07 -0800
Thread-Topic: [maitai] Roles of Sender and Receiver
Thread-Index: AcuSMcHUji2QcuNKQQ+pGZLX/kNAwgAHX54w
Message-ID: <44C6B6B2D0CF424AA90B6055548D7A61A76B365B@CRPMBOXPRD01.polycom.com>
References: <928969B1-F60B-47B8-A526-676E86BA7061@magorcorp.com> <44C6B6B2D0CF424AA90B6055548D7A61A7612FD9@CRPMBOXPRD01.polycom.com> <D840EB23-8E8E-481C-9410-F36FD963BF97@magorcorp.com>
In-Reply-To: <D840EB23-8E8E-481C-9410-F36FD963BF97@magorcorp.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: Re: [maitai] Roles of Sender and Receiver
X-BeenThere: maitai@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-stream Attributes for Improving Telepresence Application Interoperability <maitai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/maitai>, <mailto:maitai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/maitai>
List-Post: <mailto:maitai@ietf.org>
List-Help: <mailto:maitai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/maitai>, <mailto:maitai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Dec 2010 18:32:56 -0000

Peter,

H.281 controls video on an existing stream, not selecting a new stream from a new IP/port.

Mark

-----Original Message-----
From: Peter Musgrave [mailto:peter.musgrave@magorcorp.com] 
Sent: Thursday, December 02, 2010 10:01 AM

On 2010-12-02, at 9:35 AM, Duckworth, Mark wrote:
> 
> That is certainly a good possibility.  If B can choose dynamically, changing the choice during the session, it is similar to the current standard ability for B to select a video source from A using the H.281 SELECT VIDEO SOURCE message.  But the list of possible sources supported in H.281 isn't good enough for this application.
> Peter,
> 
Oh, dear. Another H.xxx protocol I don't know...

Are the semantics in H.281 controlling which video is placed on an existing media stream (i.e. stream still appears to come from same port/IP but the content within the stream changes) - or does the sender send from a new IP/port to the same destination? 


I agree with your comments that receiver selection is a powerful thing. It seems to me inevitable that this is something which will need effort - but IIUC this is out of scope for the Maitai work (it is concerned with knowing what the choices are...and not issues which touch on 'continuous presence/floor control')

Thanks, 

Peter

v2.23.0 | Report a Bug | By Email