Re: Interim step on meetings site feedback for sites currently under active consideration (off-topic)

Corinne Cath <corinnecath@gmail.com> Fri, 22 April 2016 11:30 UTC

Return-Path: <cattekwaad@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B17E12E3D8 for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 04:30:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IUIHhs8rDTCu for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 04:29:59 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44C8112D903 for <ietf@ietf.org>; Fri, 22 Apr 2016 04:29:59 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id v200so1896987wmv.1 for <ietf@ietf.org>; Fri, 22 Apr 2016 04:29:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=VQAqcOuulXPxkpZDjy2caQRlgvSw/NCCWQYeRd1fP3c=; b=nVCSbrhtt2szOnrtYE6C2/jCwmzCeistzfyWGCzNq8OKM2jhn3mS2JJOMVO8SrkplR DOpyAuV9hTFpFfVNoFJMaSZp+ksy7a+x1VjJxVQxihna4/MU3rV+PiwQSs8ihYIQxNxr DI+y8HCKlYXsziMHvinE+6K07166AEZX+BXBDzKByyM49BnqW0chG15f53N9eT8NAu4V Ftbm+ynoZyYQabnI/TxRuznmtVNZEgt6psVkvdA/KJBSEH9vel4+TPxgSijaMyGFKRMV fLXWvI9tOVXXnR5IF/Na4py/jNZTCuhYpUs9S3D7lJqhjPsVO310pz2pidWbf4nLnIT0 4DBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=VQAqcOuulXPxkpZDjy2caQRlgvSw/NCCWQYeRd1fP3c=; b=i0nQtTk17+nehB2KQvUFApQNRzpvVf+YjIqBPkZu+9XnvmI5FAadIbdEoQX9gXwA+j lDYONFWyWCLg0F1x4wmhBtRm0j+/xlamStmYKSvDw48oNYsR3KuIQ41+kh91bF0MhRdq m/cPT3UjjhzkZSRinGsb2YtWH7B6MsEo9ZK0K/KBWgIrSF1ZQITvkJVhXyaG//vx/pzq f/zdqPLlOK8CfUcdSvLCTMSRoWU+3RkJngJVLK3Pmyhls8rS17QcaoYqafghhcGc0oS4 tdZrn1lmUplT9eskHtsoDI+rbvrUIr5Gzz1l3uk11Zc/uvyadQcWYWMAU6n5ZG4iwwp1 MCHA==
X-Gm-Message-State: AOPr4FUsdQj5KNu3JT1vnEuuVCKKtf0zwOeMIkYdKBvrCtS/TOQo68ji/vF3i6DVuVr1+PmkmOSsVNVBFRaB2w==
MIME-Version: 1.0
X-Received: by 10.194.61.19 with SMTP id l19mr19435724wjr.4.1461324597885; Fri, 22 Apr 2016 04:29:57 -0700 (PDT)
Sender: cattekwaad@gmail.com
Received: by 10.194.190.71 with HTTP; Fri, 22 Apr 2016 04:29:57 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20160422005428.110b3f28@resistor.net>
References: <57151C55.30206@gmail.com> <746128222.2295531.1461009032633.JavaMail.yahoo@mail.yahoo.com> <CAD499eLvW0KFToSHLb4faMHk2c5ad+HAPEwumaq48QaUbh2n2A@mail.gmail.com> <6.2.5.6.2.20160422005428.110b3f28@resistor.net>
Date: Fri, 22 Apr 2016 12:29:57 +0100
X-Google-Sender-Auth: NHYTlsgjEj2qxYe9qxk3RBW5SBg
Message-ID: <CAD499eJWX8DU7iyvSxDtFWm+srpJWRMyLe+PZ7sL3+=hb6pibQ@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration (off-topic)
From: Corinne Cath <corinnecath@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary="047d7ba97bfe8f0c2d05311125ae"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SIxnIcsa75bque01CiqPmjL_G7M>
Cc: ietf@ietf.org, Juliao Braga <juliao@braga.net.br>, "Carlos M. Martinez" <carlos@lacnic.net>, Christian O'Flaherty <oflaherty@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Apr 2016 11:30:01 -0000

excellent. thank you, best, corinne

On Fri, Apr 22, 2016 at 10:44 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Corinne, Ted,
> At 01:48 19-04-2016, Corinne Cath wrote:
>
>> Just a quick question: are you intending on providing feedback to the
>> IAOC? If so, maybe it makes sense to coordinate a bit in order to prevent a
>> duplication of entries? Or will it be useful if multiple people point out
>> the same themes?
>>
>
> The IAOC Chair requested comments about a future IETF meeting in Paris
> (France),
> Montreal (Canada) or Copenhagen (Denmark) as the IAOC is considering
> whether the IETF can have a meeting in any of those countries.  It probably
> doesn't make much of a difference whether there is duplication of entries
> except to the person(s) who will be reading the messages to
> venue-selection@ietf.org to extract the points of concern.
>
> At 05:02 19-04-2016, Ted Lemon wrote:
>
>> The IETF has a very strong tradition of commenting at length on the topic
>> at hand and hoping either that IETF leadership will spend the time to
>> review the whole thread and extract the salient points from it, or give up
>> in despair.   So what you are seeing here is very much the IETF tradition.
>>  Asking people to do better probably won't work, although it never hurts to
>> try.
>>
>
> I read the 36 messages in this thread.  Although some of the content is
> interesting, it does not look like the messages are directly related to the
> subject line.  Even though two Area Directors read some of the messages,
> the discussion is on an unmanaged thread.  It is more of an effort instead
> of a problem to extract the arguments made on this thread.  The problem is
> what to suggest given that they may be related to multiple IETF policies.
>
> Regards,
> S. Moonesamy
>