IETF Logo Mail Archive

Re: [MEDIACTRL] gen-art review of draft-ietf-mediactrl-architecture-04.txt

Scott Brim <swb@employees.org> Wed, 21 January 2009 15:43 UTC

Return-Path: <mediactrl-bounces@ietf.org>
X-Original-To: mediactrl-archive@optimus.ietf.org
Delivered-To: ietfarch-mediactrl-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8E8C3A6AEE; Wed, 21 Jan 2009 07:43:43 -0800 (PST)
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 74C393A6922; Wed, 21 Jan 2009 07:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.525
X-Spam-Level:
X-Spam-Status: No, score=-6.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, 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 GQpuMp0mJtmU; Wed, 21 Jan 2009 07:43:41 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 95BCC3A68C0; Wed, 21 Jan 2009 07:43:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,301,1231113600"; d="scan'208";a="130061927"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 21 Jan 2009 15:43:25 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0LFhP11003698; Wed, 21 Jan 2009 07:43:25 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id n0LFhCko020377; Wed, 21 Jan 2009 15:43:25 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jan 2009 10:43:20 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jan 2009 10:43:19 -0500
Date: Wed, 21 Jan 2009 10:43:19 -0500
From: Scott Brim <swb@employees.org>
To: Tim Melanchuk <tim.melanchuk@gmail.com>
Message-ID: <20090121154319.GA71937@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Tim Melanchuk <tim.melanchuk@gmail.com>, gen-art@ietf.org, Spencer Dawkins <spencer@wonderhamster.org>, Jon Peterson <jon.peterson@neustar.biz>, mediactrl@ietf.org
References: <20090119211110.GA33692@cisco.com> <b9d5d6d70901210737w4ec22a6doa147b85fef3b4cf2@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <b9d5d6d70901210737w4ec22a6doa147b85fef3b4cf2@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 21 Jan 2009 15:43:20.0037 (UTC) FILETIME=[FC2A8150:01C97BDE]
Authentication-Results: sj-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: gen-art@ietf.org, Jon Peterson <jon.peterson@neustar.biz>, mediactrl@ietf.org
Subject: Re: [MEDIACTRL] gen-art review of draft-ietf-mediactrl-architecture-04.txt
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mediactrl-bounces@ietf.org
Errors-To: mediactrl-bounces@ietf.org Excerpts from Tim Melanchuk on Wed, Jan 21, 2009 07:37:28AM -0800:

> hi scott,
> my feeling is that sourcing and sinking media streams is implicit in
> all of the overt functions covered by the definition and that the act
> of "only" sourcing or sinking media, divorced from the functions
> listed in the definition, is not really a primary MS function.
> 
> also, the text and diagram in section 3 "architecture overview" clearly
> note that the MS is sourcing and sinking media streams to/from
> SIP UAs so i don't think there is any chance of confusion.
> 
> cheers,
> timm

OK.  

Scott

> 
> On Mon, Jan 19, 2009 at 1:11 PM, Scott Brim <swb@employees.org> wrote:
> 
> > I have been selected as the General Area Review Team (Gen-ART)
> > reviewer for this draft (for background on Gen-ART, please see
> > http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).  Please
> > resolve these comments along with any other Last Call comments you may
> > receive.
> >
> > Document: draft-ietf-mediactrl-architecture-04.txt
> > Reviewer: Scott  Brim
> > Review Date: 2009-01-19
> > IETF LC End Date: 2009-01-26
> > IESG Telechat date: (not known)
> >
> > Summary: This document is ready for publication as an Informational
> > RFC with one nit.
> >
> > Details:
> >
> > It's good.  I have a minor issue.  I note that in the definition of
> > media server ...
> >
> >   Media Server (MS): The media server includes the mixer as defined
> >   in [RFC4353].  The media server plays announcements, it processes
> >   media streams for functions like Dual Tone Multi-Frequency (DTMF)
> >   detection and transcoding.  The media server may also record media
> >   streams for supporting IVR functions like announcing conference
> >   participants. ...
> >
> > ... you don't include what seems to me to be its most essential
> > function, to deliver media streams to SIP user agents (via RTP/SRTP).
> > I just want to be sure that you didn't leave out fundamental functions
> > because you were figuring out the more complex ones.
> >
> > swb
> >
> >
_______________________________________________
MEDIACTRL mailing list
MEDIACTRL@ietf.org
https://www.ietf.org/mailman/listinfo/mediactrl
Supplemental Web Site:
http://www.standardstrack.com/ietf/mediactrl

v2.23.0 | Report a Bug | By Email