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

Eliot Lear <lear@cisco.com> Thu, 07 April 2011 10:08 UTC

Return-Path: <lear@cisco.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 90E7B3A69BD for <yaco-liaison-tool@core3.amsl.com>; Thu, 7 Apr 2011 03:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.436
X-Spam-Level:
X-Spam-Status: No, score=-110.436 tagged_above=-999 required=5 tests=[AWL=-0.137, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, 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 zB05c6hv79qE for <yaco-liaison-tool@core3.amsl.com>; Thu, 7 Apr 2011 03:08:27 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 6E5443A68F7 for <yaco-liaison-tool@ietf.org>; Thu, 7 Apr 2011 03:08:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=2454; q=dns/txt; s=iport; t=1302171012; x=1303380612; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=gVMBsetj9xDtvG/lNXDQ1nh+o2HW6AnHloDstqwHNHs=; b=cejwfgDfkh96JWsPQxMZbB3jCp0nRMpACmHfPcsJox360jq0xycj7fC6 7hTsw+ftIlGO0+inEkIKaIqEYPrunax1N6njCJ8tiwG8VxhgLBDddbY9R f7vqZCInXN5Nxp6DvY/zfpBYlRfnyg4Coq694xm7lOgr9TU0ET1hKkvm7 w=;
X-IronPort-AV: E=Sophos;i="4.63,315,1299456000"; d="scan'208";a="82583386"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 07 Apr 2011 10:10:11 +0000
Received: from ams3-vpn-dhcp4906.cisco.com (ams3-vpn-dhcp4906.cisco.com [10.61.83.41]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p37AABnW031330; Thu, 7 Apr 2011 10:10:11 GMT
Message-ID: <4D9D8D5E.6030306@cisco.com>
Date: Thu, 07 Apr 2011 12:09:34 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: =?UTF-8?B?IkVtaWxpbyBBLiBTw6FuY2hleiI=?= <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> <4D9D80D5.50302@levkowetz.com> <4D9D85CF.1030100@yaco.es>
In-Reply-To: <4D9D85CF.1030100@yaco.es>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Thu, 07 Apr 2011 04:23:15 -0700
Cc: yaco-liaison-tool@ietf.org, =?UTF-8?B?csO2bQ==?= <pfaltstr@cisco.com>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Q=?=, 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 10:08:28 -0000

Hi Emilio and all,

I wonder if we could have a call to catch me up on all that is going on
with the tool?  Would that be possible sometime next week?

Eliot

On 4/7/11 11:37 AM, "Emilio A. Sánchez" wrote:
>
>    Hi,
>
>    Right now the field person of the LiaisonDetail model stores the
> PersonOrOrgInfo of the user that creates the liaison. The real one so
> if the secretariat is sending a liaisons the person field has the
> secretariat user person.
>
>    But this info is not used to grant any privilege over the liaisons.
>
>    Best,
>
> El 07/04/11 11:16, Henrik Levkowetz escribió:
>> 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
>>
>
>