[Sipping] Re: Consent framework comments

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Mon, 07 November 2005 00:36 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYuzp-0002la-9c; Sun, 06 Nov 2005 19:36:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYuzo-0002lV-9T for sipping@megatron.ietf.org; Sun, 06 Nov 2005 19:36:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29872 for <sipping@ietf.org>; Sun, 6 Nov 2005 19:35:58 -0500 (EST)
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EYvFE-0001F6-BC for sipping@ietf.org; Sun, 06 Nov 2005 19:52:25 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 496207A6; Mon, 7 Nov 2005 01:36:10 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 7 Nov 2005 01:36:08 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 7 Nov 2005 01:33:53 +0100
Received: from [131.160.126.74] (rvi2-126-74.lmf.ericsson.se [131.160.126.74]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 959412819; Mon, 7 Nov 2005 02:33:41 +0200 (EET)
Message-ID: <436EA0DB.8000601@ericsson.com>
Date: Mon, 07 Nov 2005 02:33:31 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Markus.Isomaki@nokia.com
References: <C84E0A4ABA6DD74DA5221E0833A35DF303816D06@esebe101.NOE.Nokia.com>
In-Reply-To: <C84E0A4ABA6DD74DA5221E0833A35DF303816D06@esebe101.NOE.Nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Nov 2005 00:33:53.0235 (UTC) FILETIME=[EE180A30:01C5E332]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, dean.willis@softarmor.com
Subject: [Sipping] Re: Consent framework comments
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Hi Markus,

thanks for the comments. Answers inline:

 > So, would it be possible to have consent policies
> like this: - Any translation created by User X, using factory URI Y;
> or even - Any translation created by User X in domain Y

Yes, we need to discuss the format of the permission documents. We want 
something simple but with enough expresiveness to cover the main 
scenarios where consent is useful.

> Perhaps even things like SAML should be
> investigated for giving permissions.

In principle, we were thinking of a simple XML schema explicitly 
designed for consent, but it may be worthwhile exploring other 
alternatives as well, as you suggest.

The initial proposal was something like this:

    <target>
       <identity>
              <id>A@example.com</id>
       </identity>
     </target>
     <sender>
       <identity>
         <any-identity/>
       </identity>
     </sender>
     <recipient>
       <identity>
         <id>a@ws123.example.com</id>
       </identity>
     </recipient>
     <operations>
         <any-method/>
     </operations>

> what can be done about domains that do not
> enforce this type of policies?

I think this is indeed an interesting discussion to have... not so 
relevant to this draft at this point, though.

> While this is not required for the draft, it would be good to list
> for SIPPING WG what kind of Standards Track RFCs should be generated
> to actually build a working consent system out of the framework, so
> that these pieces can be chartered and work started/distributed.

Yes, we will coordinate these efforts with the SIP/SIPPING chairs and 
the AD.

Thanks,

Gonzalo

_______________________________________________
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