AW: [Sipping] draft-tschofenig-sipping-spit-policy-00

"Tschofenig, Hannes" <hannes.tschofenig@siemens.com> Sat, 10 March 2007 21:34 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQ9Cr-0000RC-WA; Sat, 10 Mar 2007 16:34:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQ9Cq-0000R2-ID for sipping@ietf.org; Sat, 10 Mar 2007 16:34:24 -0500
Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQ9Cl-0006Ss-78 for sipping@ietf.org; Sat, 10 Mar 2007 16:34:24 -0500
Received: from mail2.siemens.de (localhost [127.0.0.1]) by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id l2ALYGoU029844; Sat, 10 Mar 2007 22:34:17 +0100
Received: from mchp771a.ww002.siemens.net (mchp771a.ww002.siemens.net [139.25.131.189]) by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id l2ALYFgF031576; Sat, 10 Mar 2007 22:34:16 +0100
Received: from MCHP7R6A.ww002.siemens.net ([139.25.131.164]) by mchp771a.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Sat, 10 Mar 2007 22:34:16 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: AW: [Sipping] draft-tschofenig-sipping-spit-policy-00
Date: Sat, 10 Mar 2007 22:25:36 +0100
Message-ID: <8F6CBC7005099442AECDB784C9E9D7E7018CABEB@MCHP7R6A.ww002.siemens.net>
In-Reply-To: <33127495-8FDD-42B3-A12E-432944166E74@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] draft-tschofenig-sipping-spit-policy-00
Thread-Index: AcdjWjf65KrrQ5ZaS7ezN5z8MRtQCgAABnZA
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: Cullen Jennings <fluffy@cisco.com>, sipping <sipping@ietf.org>
X-OriginalArrivalTime: 10 Mar 2007 21:34:16.0012 (UTC) FILETIME=[DA5E10C0:01C7635B]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc:
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi Cullen, 

 
> I'd rather have a better idea bout what the overall system looked  
> like and what the required policy is before dealing with the details  
> of how to represent it.

We started with a requirements document and nobody gave us comments.
Hence, we thought that we would get more comments when to submit a
strawman proposal. 

> 
> For example, I'D like to be able to do rules like "not in my buddy  
> list" or "not a FOAF".
You can do things like "not in my buddy list" quite easily with these
type of policies. How you represent these policies to the user (as a
user interface) is another story. 

Ciao
Hannes

> 
> 
> Cullen <with my individual hat on>
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP