Re: [dispatch] "profile datasets" and the SIP UA configuration system

"Dale Worley" <dworley@nortel.com> Wed, 13 May 2009 21:43 UTC

Return-Path: <dworley@nortel.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D7983A6B14 for <dispatch@core3.amsl.com>; Wed, 13 May 2009 14:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.512
X-Spam-Level:
X-Spam-Status: No, score=-6.512 tagged_above=-999 required=5 tests=[AWL=0.087, 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 LNf0mD4jgH8n for <dispatch@core3.amsl.com>; Wed, 13 May 2009 14:43:04 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 4A5D43A683B for <dispatch@ietf.org>; Wed, 13 May 2009 14:43:04 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n4DLhVE23170 for <dispatch@ietf.org>; Wed, 13 May 2009 21:43:32 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 13 May 2009 17:44:30 -0400
From: Dale Worley <dworley@nortel.com>
To: Mary Barnes <mary.barnes@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1DEDB2F8@zrc2hxm0.corp.nortel.com>
References: <1242079371.3757.46.camel@victoria-pingtel-com.us.nortel.com> <1ECE0EB50388174790F9694F77522CCF1DEDB2F8@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 13 May 2009 17:44:29 -0400
Message-Id: <1242251069.26396.2.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 May 2009 21:44:30.0148 (UTC) FILETIME=[FED30840:01C9D413]
Cc: DISPATCH <dispatch@ietf.org>
Subject: Re: [dispatch] "profile datasets" and the SIP UA configuration system
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2009 21:43:05 -0000

On Mon, 2009-05-11 at 20:16 -0400, Barnes, Mary (RICH2:AR00) wrote:
> I also think that draft-ietf-sipping-policy-package might fit into the
> more general topic - it depends upon the media-policy-dataset.  

Currently, I don't classify draft-ietf-sipping-policy-package as being
involved in this discussion because it does not depend on the config
schema, it only specifies that the event package carry such XML
documents.  Of course, that distinction breaks down because
policy-package users are interested that the schema carry the
information that they need, but that's more of a semantic
interest/constraint than a syntactic one.

> There have been several other individual documents in this area in the
> past as well - I'll let those folks speak up if they still have an
> interest in this work.

Given the ambiguities involved, it looks like Dispatch is a good place
to get the discussion started.

Dale