Re: IETF 92 in Dallas!

"Fred Baker (fred)" <fred@cisco.com> Thu, 16 August 2012 18:59 UTC

Return-Path: <fred@cisco.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 8E9AC21F853F; Thu, 16 Aug 2012 11:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.504
X-Spam-Level:
X-Spam-Status: No, score=-110.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y4Pi3fzjT4i9; Thu, 16 Aug 2012 11:59:32 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id EAF0421F85DA; Thu, 16 Aug 2012 11:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=723; q=dns/txt; s=iport; t=1345143572; x=1346353172; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=UAxes00Spk1NWUMxX1rCyFpp56U9jJaKaJ8PtA5Rw3s=; b=Gi49we5RecGmdmNH3ayzItZGq5tRmuAmbof4ZxZohp7/zXGTAkqg8o3B yV+mkNG8fQjZKne+ztDoM0QHuZEkaIUyk2G/NDU8X6KGVldxrThJCrcww nKE7utOITJY5v/tSmJesrcnFSCXJ/mPktSCfVozsk4VWvMksZuOcjWYM9 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAM9CLVCtJV2c/2dsb2JhbABFui2BB4IgAQEBBBIBJz8QAgEIDgoeEDIlAgQOJ4drmk6gQIsKhXdgA5VPjiyBZoJf
X-IronPort-AV: E=Sophos;i="4.77,780,1336348800"; d="scan'208";a="112369495"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP; 16 Aug 2012 18:59:31 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id q7GIxVgk018549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Aug 2012 18:59:31 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.97]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0298.004; Thu, 16 Aug 2012 13:59:30 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: IETF 92 in Dallas!
Thread-Topic: IETF 92 in Dallas!
Thread-Index: AQHNexjl8crCkcCVmkiACyxTrfHTzZdcHm4AgAEBs4A=
Date: Thu, 16 Aug 2012 18:59:29 +0000
Message-ID: <E4C5EA9B-9F60-4A8F-98F9-AC86E1407F5A@cisco.com>
References: <20120815190455.14702.74089.idtracker@ietfa.amsl.com> <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
In-Reply-To: <618FF5D7-5351-468C-A08E-4C104B063D16@lacnic.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.89.130]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19120.001
x-tm-as-result: No--36.741000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DE65182C30DBC546BF1BAEB4F5845B75@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org Group" <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, IAB IAB <iab@iab.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 16 Aug 2012 18:59:32 -0000

On Aug 15, 2012, at 8:37 PM, Arturo Servin wrote:
> 	So "Americas" was actually "North America".
> 
> 	Well, it went the possibility to have one in central or south america, what at shame. At least until IETF 98 in March 2017 no IETF down the south of Rio Grande.
> 
> 	May I ask the IAOC, what are the impediments to have one IETF in Latin America?
> 
> Regards,
> as

It was investigated and dropped, having gotten hotel pricing and found it unusually high. I'm told that there is further discussion targeting finding ways to reduce that. We have had similar investigations and decisions in other places. You'll note that the IAOC is routinely tarred and feathered over prices...