Re: IAOC requesting input on (potential) meeting cities

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Wed, 12 April 2017 14:01 UTC

Return-Path: <prvs=127550c264=jordi.palet@consulintel.es>
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 E5DBD1294B5 for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 07:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 UnAiPgp5WHZZ for <ietf@ietfa.amsl.com>; Wed, 12 Apr 2017 07:01:35 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 054AE126BF0 for <ietf@ietf.org>; Wed, 12 Apr 2017 07:01:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1492005687; x=1492610487; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=rysYTIWVNEFO35kmXKrYHV8Pa zcM08w3bA184T0h5qE=; b=E7dmFp6+o+adomv6JwkL7ZWHtFh6tuv2qt8BeQONR DnRrRlfnoZft3T7WohfffGXulxexfBIEUiv3sLY1xRzxjrh5jlo68IK1t0NQu6ch NIsR2o5qSt/8lu90nmEbZ+gItm1RtEvWQ2gs2q7+TzwC67FiVXdrZi64o4S5TKFM zI=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=KSGY/RgSr/1LnAqv/BtYDrCyiCcACTwbuaju8KAfY2EcSa1/EapsqeMjGYC3 8daHQqo0k6jaRACd+jOhlBhOb6kl1AByU6Yc/R4EDWDa7Ux63Ji92Ft83 v2zwwh0iuW7DyRP85SinAlaXFgnmBZIgAa6tTEF/6Y79OrZ1aSVpNc=;
X-MDAV-Processed: mail.consulintel.es, Wed, 12 Apr 2017 16:01:26 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 12 Apr 2017 16:01:25 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005407089.msg for <ietf@ietf.org>; Wed, 12 Apr 2017 16:01:25 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170412:md50005407089::lcXDAYyjNbm37Ut0:00001/D3
X-Return-Path: prvs=127550c264=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Wed, 12 Apr 2017 16:01:23 +0200
Subject: Re: IAOC requesting input on (potential) meeting cities
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <iaoc@ietf.org>, IETF Discussion <ietf@ietf.org>
Message-ID: <AC7E6A0F-923B-4DF9-81E2-3575EA156F86@consulintel.es>
Thread-Topic: IAOC requesting input on (potential) meeting cities
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es> <102DED0B-F1CD-4C65-8AA2-5270227EECCC@consulintel.es> <697AB8AC-BD17-47D6-94C7-B80186500699@consulintel.es> <AD2AF7CA-ACAB-4642-BA6A-FB77423CD74F@fugue.com>
In-Reply-To: <AD2AF7CA-ACAB-4642-BA6A-FB77423CD74F@fugue.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mThBjp-gBKTE1xOQVWuqczHzCnw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 12 Apr 2017 14:01:37 -0000

So, you mean they don’t use email?

Sounds surprising to me, despite for sure they had some time in Chicago to decide about what can be said to the community about the SF meeting. If they haven’t considered that, I guess we need an IAOC with more focus on what is the most relevant and important topic right now for the community.

By the way, it seems that they haven’t met anyway since August 2015, as they promised me to respond to one of my emails regarding some spam/email bouncing issues and the way we are managing so, and I’ve been waiting since them. Really nice and respectful way to support the community.

Regards,
Jordi
 

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Ted Lemon <mellon@fugue.com>
Responder a: <mellon@fugue.com>
Fecha: miércoles, 12 de abril de 2017, 15:26
Para: <jordi.palet@consulintel.es>
CC: <iaoc@ietf.org>rg>, IETF Discussion <ietf@ietf.org>
Asunto: Re: IAOC requesting input on (potential) meeting cities

    On Apr 12, 2017, at 4:53 AM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
    Do we need to ask again and again every day?
    
    
    
    
    
    Has the IAOC met since the first time you asked?
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.