IETF Returning to Berlin for IETF 96

IETF Administrative Director <> Tue, 04 February 2014 18:10 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 041211A0135 for <>; Tue, 4 Feb 2014 10:10:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fnF-i4RTXZTc for <>; Tue, 4 Feb 2014 10:10:27 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 9B2F71A0035 for <>; Tue, 4 Feb 2014 10:10:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <>
To: IETF Announcement List <>
Subject: IETF Returning to Berlin for IETF 96
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 04 Feb 2014 10:10:27 -0800
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Feb 2014 18:10:31 -0000

The IAOC is pleased to announce the IETF will be returning to Berlin for IETF 96, 
July 17 - 22, 2016.  If you attended IETF 87 in Berlin you were asked in the 
meeting survey whether you would like to return to the Berlin InterContinental for 
an IETF meeting.  96% of the respondents said Yes!  We are happy to oblige! 

We are looking for a Host and some sponsors for this meeting.  Contact Drew 
Dvorshak, dvorshak at, if you have any interest.

Other News - IETFs 95, 96 & 97 in 2016

The IAOC adopted a policy that we would select the IETF meeting venues three years 
in advance.  So, ordinarily we would have made announcements for the first 2 of the
3 meetings for 2016 in 2013, but 2013 turned out to be a challenging year for 
contracting.  The target regions for 2016 were Europe, the Americas, and Asia in that
order, and work began early in the year to identify and qualify venues for those 
regions.  Typically, arrangements for the third meeting carry over into the first 
quarter of the next year.  

There was interest in having an IETF meeting in Latin America. Due diligence 
included a site visit there in late February, followed by a Meetings Committee and 
IAOC review of the feasibility, and a decision to discuss the possibility with the 
community was made by the IAOC.  

The IAOC authorized negotiations in Buenos Aires to began in earnest on 20 June for
IETF 95 in April 2016 after receiving feedback from the community from a survey and 
comments on the list.  I wish I could tell you that we have a contract.  However, 
economic uncertainty in the country, among other things, has made it difficult to 
close on a deal.  But we are still at it, including looking at other options in Buenos 

Moving the Americas to April meant we needed to move Europe to July 2016.  The 
successful meeting in Berlin and the attendees strong desire to return greatly 
influenced the decision to return.  However, we could not close on a contract with the
 hotel until all the VAT administrative work was completed and that didn’t happen 
until 19 December.

As for Asia I expect we will have something to announce at or before IETF 90 in 

Only 26 days until IETF 89 in London!  Register here: 

See you there!

Ray Pelletier
IETF Administrative Director


IETF 89  London  Hilton Metropole  March 2 - 7  Host:  ICANN
IETF 90  Toronto  Fairmont Royal York Hotel  July 20 - 25  Host:  In 
IETF 91  Honolulu  Hilton Hawaiian Village  Nov 9 - 14  Host: Cisco


IETF 92  Dallas  March 22 - 27  Host:  Your Name Here
IETF 93  Prague	  July 19 - 24  Host:  Your Name Here
IETF 94  Yokohama  Nov 1 - 6  Host:  WIDE