Re: [MEDIACTRL] I-D ACTION:draft-ietf-mediactrl-architecture-01.txt

Lorenzo Miniero <lorenzo.miniero@unina.it> Wed, 21 November 2007 09:58 UTC

Return-path: <mediactrl-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IumM2-0008Kd-Qf; Wed, 21 Nov 2007 04:58:46 -0500
Received: from mediactrl by megatron.ietf.org with local (Exim 4.43) id 1IumM1-0008IL-Rs for mediactrl-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 04:58:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IumLv-0008G1-Qv for mediactrl@ietf.org; Wed, 21 Nov 2007 04:58:39 -0500
Received: from mail.unina.it ([192.132.34.73]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IumLr-00071K-RG for mediactrl@ietf.org; Wed, 21 Nov 2007 04:58:39 -0500
Received: from localhost.localdomain ([143.225.229.170]) by mail.unina.it (8.13.7/8.13.7) with ESMTP id lALAAp9T013163 for <mediactrl@ietf.org>; Wed, 21 Nov 2007 11:10:51 +0100
Message-ID: <47440111.6010303@unina.it>
Date: Wed, 21 Nov 2007 10:57:37 +0100
From: Lorenzo Miniero <lorenzo.miniero@unina.it>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: mediactrl@ietf.org
Subject: Re: [MEDIACTRL] I-D ACTION:draft-ietf-mediactrl-architecture-01.txt
References: <E1IubN0-0003j8-5p@stiedprstage1.ietf.org>
In-Reply-To: <E1IubN0-0003j8-5p@stiedprstage1.ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-unina-it-MailScanner-Information: Please contact www.csi.unina.it for information
X-unina-it-MailScanner: Found to be clean
X-unina-it-MailScanner-SpamCheck: non spam, SpamAssassin (punteggio=0.035, necessario 6, autolearn=disabled, AWL 0.04)
X-unina-it-MailScanner-From: lorenzo.miniero@unina.it
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Control BOF Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
Errors-To: mediactrl-bounces@ietf.org

Reading it again, I think I have a comment upon the conferencing section 
I contributed to. The 6.2 paragraph is probably incorrect by stating 
that the 3PCC mechanism alone is always used to add participants to a 
conference. While it may be right in other cases, in MediaCtrl the 
proper way to do such is probably doing the following:

	1. the AS uses 3PCC to attach a UAC to the MS, as always;
	2. the AS uses other means (e.g. the conferencing package) to actually 
join the newly created UAC media leg(s) to a conference when it 
needs/wants to.

This also allows subsequent and/or previous manipulation of the leg in 
other contexts, without explicitely binding it to a conferencing 
scenario as the paragraph suggests. By saying 'other contexts' I'm 
thinking for instance to IVR menus that take place before the join of a 
conference, as prompting for a PIN and so on, or having the join to a 
conference only as one of the possible branches of an IVR menu, and so 
on. Of course, this also means that between the AS and the MS it is not 
important which SIP URI is used (as it is instead between the UAC and 
the AS, since it selects the service to provide), considering that the 
join to a specific conference is accomplished through the control 
channel and not using the URI itself.

I think this may need to be reflected in the draft. About the rest, my 
opinion is that the draft is fine the way it is.

Lorenzo
	

Internet-Drafts@ietf.org ha scritto:
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Media Server Control Working Group of the IETF.
> 
> 	Title		: An Architectural Framework for Media  Server Control
> 	Author(s)	: T. Melanchuk
> 	Filename	: draft-ietf-mediactrl-architecture-01.txt
> 	Pages		: 29
> 	Date		: 2007-11-20
> 	
> This document describes an Architectural Framework for Media Server
>    Control.  The primary focus will be to define logical entities that
>    exist within the context of Media Server control, and define the
>    appropriate naming conventions and interactions between them.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mediactrl-architecture-01.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> i-d-announce-request@ietf.org with the word unsubscribe in the body of 
> the message. 
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
> to change your subscription settings.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the 
> username "anonymous" and a password of your e-mail address. After 
> logging in, type "cd internet-drafts" and then 
> "get draft-ietf-mediactrl-architecture-01.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-mediactrl-architecture-01.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> MEDIACTRL mailing list
> MEDIACTRL@ietf.org
> https://www1.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl



_______________________________________________
MEDIACTRL mailing list
MEDIACTRL@ietf.org
https://www1.ietf.org/mailman/listinfo/mediactrl
Supplemental Web Site:
http://www.standardstrack.com/ietf/mediactrl