Re: [yaco-liaison-tool] The liaison tool: Status Update

Henrik Levkowetz <henrik@levkowetz.com> Thu, 07 April 2011 09:14 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: yaco-liaison-tool@core3.amsl.com
Delivered-To: yaco-liaison-tool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD9B33A68DF for <yaco-liaison-tool@core3.amsl.com>; Thu, 7 Apr 2011 02:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.313
X-Spam-Level:
X-Spam-Status: No, score=-102.313 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 IzmAeh82a9HU for <yaco-liaison-tool@core3.amsl.com>; Thu, 7 Apr 2011 02:14:53 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id EBA2E3A68D6 for <yaco-liaison-tool@ietf.org>; Thu, 7 Apr 2011 02:14:52 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:53419 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.74) (envelope-from <henrik@levkowetz.com>) id 1Q7lJv-0002Ml-1d; Thu, 07 Apr 2011 11:16:08 +0200
Message-ID: <4D9D80D5.50302@levkowetz.com>
Date: Thu, 07 Apr 2011 11:16:05 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
References: <4D483171.7090508@levkowetz.com> <A9723AE7-F5B8-4722-BBB6-80F71C6AED31@amsl.com> <4D485061.3090204@levkowetz.com> <1FD00AF1-C1C6-4D33-9E70-E2B3D3ED11A6@cisco.com> <4D494292.1000809@levkowetz.com> <D4C88766-1C27-4212-B833-EF9F3B06452C@cisco.com> <4D49D50A.9000408@levkowetz.com> <18D7B1E6-2A70-4C5A-8C0E-9D43AD489599@cisco.com> <4D4B0946.7070302@levkowetz.com> <AF68B07C-FB34-4B7D-B710-848C710E20E1@cisco.com> <4D4BB18F.8020808@yaco.es> <09D40B0B-3058-4416-AC88-49C072EE93E0@cisco.com> <1EA3B690-E6A3-4988-8D2A-8A73147117EA@amsl.com> <C09F0708-AD85-4B96-BB63-537DE1936373@cisco.com> <4D9C5C79.40904@levkowetz.com> <4D9C72BB.8020605@yaco.es> <4D9D74E6.3080808@levkowetz.com> <4D9D7BBC.4030708@yaco.es>
In-Reply-To: <4D9D7BBC.4030708@yaco.es>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2E1605611804D989EEB3D4FE"
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: esanchez@yaco.es, pfaltstr@cisco.com, smccammon@amsl.com, amorris@amsl.com, housley@vigilsec.com, lear@cisco.com, rpelletier@isoc.org, glen@amsl.com, yaco-liaison-tool@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: yaco-liaison-tool@ietf.org, Eliot Lear <lear@cisco.com>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <pfaltstr@cisco.com>, Ray Pelletier <rpelletier@isoc.org>
Subject: Re: [yaco-liaison-tool] The liaison tool: Status Update
X-BeenThere: yaco-liaison-tool@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of the Yaco / Liaison Statement Management Tool Project details <yaco-liaison-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yaco-liaison-tool>, <mailto:yaco-liaison-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-liaison-tool>
List-Post: <mailto:yaco-liaison-tool@ietf.org>
List-Help: <mailto:yaco-liaison-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-liaison-tool>, <mailto:yaco-liaison-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2011 09:14:54 -0000

Hi Emilio,

I'm not sure you, Patrik and myself are talking about the same thing
here.  See more below.

On 2011-04-07 10:54 "Emilio A. Sánchez" said:
>     Hi.
> 
> El 07/04/11 10:25, Henrik Levkowetz escribió:
>> Hi Emilio,
>>
>> On 2011-04-06 16:03 "Emilio A. Sánchez" said:
>> ...
>>
>>>      I don't understand what data want's to edit Patrik when he say 'who
>>> holds the action item'. If he refers to the person who can 'take care'
>>> of a liaison, this person is selected automatically.
>>
>> But if the SDO Liaison Manager is changing, then liaisons which still
>> need to be taken care of will need to be updated, no?
> 
>     I'm revising the code. The persons who are allowed to 'take care' of 
> a liaison are:
> 
>     * The secretariat (always)
>     * Any person whose email is listed under 'cc', 'reply_to', 'poc', 
> 'response_contact', 'technical_contact' and the submitter. Of course 
> only if this person has an user in the datatracker.
> 
>     One option is edit one of this field (but this is so ugly).
> 
>     I think that the best option is allow to the 'take care' a if the 
> current user is allowed to edit the liaison (This check is done on the 
> fly and checks if the user is currently an sdo manager of the liaison).


There's an entry in the LiaisonDetails class which is 'person'.
This would be the person who holds the token to handle a liaison,
maybe?  If so, I think that's the entry Patrik would like to update.

But if this entry isn't used anywhere, then we need to figure out
the distinction between the set of people who 'can take care of' a
liaison, and the person who has the token.


Best,

	Henrik