Re: [MEDIACTRL] AD review:draft-ietf-mediactrl-mixer-controlpackage-09

"Spencer Dawkins" <spencer@wonderhamster.org> Thu, 28 January 2010 21:43 UTC

Return-Path: <spencer@wonderhamster.org>
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FF3E3A67E1 for <mediactrl@core3.amsl.com>; Thu, 28 Jan 2010 13:43:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 h8mUO03itiEm for <mediactrl@core3.amsl.com>; Thu, 28 Jan 2010 13:43:20 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 4AC413A677C for <mediactrl@ietf.org>; Thu, 28 Jan 2010 13:43:20 -0800 (PST)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MBEth-1NTDkO35TZ-00AMnZ; Thu, 28 Jan 2010 16:43:28 -0500
Message-ID: <117A6662C69545969EDBEF9BDEE0BD39@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: "MUNSON, GARY A, ATTLABS" <gm3472@att.com>, mediactrl@ietf.org
References: <4b50ee20.b7.1d08.420790473@webmaildh2.ad.aruba.it><878F581E-1BE0-4418-B583-1BEEC87FF22F@hp.com><8302FCDB11E340D5BC7233306C4336E9@china.huawei.com> <2F41EF28ED42A5489E41742244C9117C01E4849D@gaalpa1msgusr7b.ugd.att.com>
Date: Thu, 28 Jan 2010 15:43:16 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/yBi3JOY7hVRacLleXxLUKNLPGcQ2OI+3Vl7q SBI5yUWfh0cGFNwicVJ8R9fscvTqGoM/E94M/ytFHUUz6TkkWa I8CyPmQaXLTdL+Q483uOUVZps/U+OSuXL7Y8xKmWHg=
Subject: Re: [MEDIACTRL] AD review:draft-ietf-mediactrl-mixer-controlpackage-09
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2010 21:43:21 -0000

Gary,

This is exactly the kind of feedback I'm looking for - I'm not saying 
there's a problem, I'm just saying that we forwarded two specs to Robert 
that deal with partial failures differently, and I want to make sure that we 
did that on purpose!

Do others see it the same way?

Thanks,

Spencer


> That feels right to me.
>
> I can imagine with IVR a prompt & collect routine of some length going
> on where there's a problem part way through (MS software or subsystem
> hiccup or whatever) and MS can't complete. Can't expect the MS to know
> that ahead of time, and it can't undo.
>
> With MIXER, I can't imagine a scenario, practically, where there would
> be a problem in the middle of doing something. (Not sure there really is
> much of a middle with MIXER operations.)
>
> cheers,
>
> Gary
>
> -----Original Message-----
> From: mediactrl-bounces@ietf.org [mailto:mediactrl-bounces@ietf.org] On
> Behalf Of Spencer Dawkins
> Sent: Thursday, January 28, 2010 3:07 PM
> To: Scott McGlashan; Lorenzo Miniero
> Cc: draft-ietf-mediactrl-mixer-control-package@tools.ietf.org;
> mediactrl@ietf.org
> Subject: Re: [MEDIACTRL] AD review:
> draft-ietf-mediactrl-mixer-controlpackage-09
>
> Hi, Scott,
>
> Thanks for taking care of this - Robert has just launched the control
> framework, the IVR package, and the MIXER package for IETF Last Call.
>
> This is a big step forward (and I look forward to the next big step,
> when
> the documents are approved for publication as Proposed Standards ;-)
>
> To the group,
>
> Scott has made a one-sentence change in the draft that I agree with (and
> I
> also agree with Robert that we had to say SOMETHING about whether
> requests
> can "partially fail", whether the answer was "yes" or "no"), but I need
> to
> make sure the working group agrees with it. The diff pops out for you at
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-mediactrl-mixer-control-pa
> ckage-10.
>
> So, what we have is a statement in one control package, but we do not
> require atomicity for control packages in general - right?
>
> For ease of reference in this thread, here's what MIXER-10 says:
>
>   If the
>   MS is not able to process the request and carry out the mixer
>   operation (in whole or in part), then the request has failed: the MS
>   MUST ensure that no part of the requested mixer operaton is carried
>   out, and the MS MUST indicate the class of failure using an
>   appropriate 4xx response code.
>
> And here's what IVR-07 says, in roughly the same place:
>
>   If the
>   MS is not able to process the request and carry out the dialog
>   operation, the request has failed and the MS MUST indicate the class
>   of failure using an appropriate 4xx response code.
>
> Do we have this right? Please let us know on-list!
>
> Thanks,
>
> Spencer
>
> ----- Original Message ----- 
> From: "Scott McGlashan" <Scott.McGlashan@hp.com>
> To: "Lorenzo Miniero" <lorenzo@meetecho.com>
> Cc: "Spencer Dawkins" <spencer@wonderhamster.org>; "Robert Sparks"
> <rjsparks@nostrum.com>; <mediactrl@ietf.org>;
> <draft-ietf-mediactrl-mixer-control-package@tools.ietf.org>
> Sent: Thursday, January 28, 2010 12:16 PM
> Subject: Re: [MEDIACTRL] AD review: draft-ietf-mediactrl-mixer-control
> package-09
>
>
> I've updated the mixer draft with a clarification along the lines
> Lorenzo
> suggested. Hopefully it is clearer now - if a operation fails in part,
> then
> the MS ensures that no part of the operation is carried out.
>
> thanks
>
> Scott
>
> _______________________________________________
> MEDIACTRL mailing list
> MEDIACTRL@ietf.org
> https://www.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl
> _______________________________________________
> MEDIACTRL mailing list
> MEDIACTRL@ietf.org
> https://www.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl