Re: [yaco-liaison-tool] Acceptance?

Patrik Fältström <paf@cisco.com> Mon, 11 October 2010 15:01 UTC

Return-Path: <paf@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 9676D3A6A64 for <yaco-liaison-tool@core3.amsl.com>; Mon, 11 Oct 2010 08:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.249
X-Spam-Level:
X-Spam-Status: No, score=-4.249 tagged_above=-999 required=5 tests=[AWL=-1.950, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 z9asLvex+T12 for <yaco-liaison-tool@core3.amsl.com>; Mon, 11 Oct 2010 08:01:56 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 787213A6AB4 for <yaco-liaison-tool@ietf.org>; Mon, 11 Oct 2010 08:01:56 -0700 (PDT)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmcEAAPEskyQ/khLgWdsb2JhbACiDRUBARYiIqRynDaFSASKQQ
X-IronPort-AV: E=Sophos;i="4.57,314,1283731200"; d="scan'208";a="11097458"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 11 Oct 2010 15:03:07 +0000
Received: from ams3-vpn-dhcp5444.cisco.com (ams3-vpn-dhcp5444.cisco.com [10.61.85.67]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o9BF37is022981; Mon, 11 Oct 2010 15:03:07 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
In-Reply-To: <4CB3248D.50102@levkowetz.com>
Date: Mon, 11 Oct 2010 17:03:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <04B4A66E-0041-427C-9375-ECD05FC416A7@cisco.com>
References: <4CAF4639.7020608@levkowetz.com> <2497A646-8C1D-444D-9B28-567E4E2B4FEE@cisco.com> <4CB2AE09.30302@yaco.es> <22B82BE6-7915-447A-BA37-B1CE9FD927C7@cisco.com> <4CB2B398.2090308@yaco.es> <4CB31117.6010304@levkowetz.com> <0F1DB687-97DD-4320-8313-9F737C1752F0@cisco.com> <4CB3248D.50102@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.1081)
Cc: yaco-liaison-tool@ietf.org
Subject: Re: [yaco-liaison-tool] Acceptance?
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: Mon, 11 Oct 2010 15:01:57 -0000

On 11 okt 2010, at 16.51, Henrik Levkowetz wrote:

>> Is it sorted out who is doing all the work with assigning the roles at time of launch?
> 
> No.  What would you suggest as the optimal approach?


Have whoever handle the statements@ietf.org do the following:

1. Add the IAB and IETF chairs, wg chairs, area directors etc as apropriate (as described in the document).

2. Add the liaisons in the IETF assigned and named on the IAB list of liaisons.

[done]

Later: Have those liaisons be able to report (or possibly add) the external liaisons that should be able to file incoming liaisons.

   Patrik