Re: [Mtgvenue] [EXTERNAL] Re: [104attendees] an IETF in India

"Deen, Glenn (NBCUniversal)" <> Thu, 14 March 2019 06:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3E9621277C9; Wed, 13 Mar 2019 23:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=0.85, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8zNiCZEIhgti; Wed, 13 Mar 2019 23:10:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B8B4B12705F; Wed, 13 Mar 2019 23:10:47 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id x2E67vb6031282; Thu, 14 Mar 2019 02:10:46 -0400
Received: from ([]) by with ESMTP id 2r4byw3gk6-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT); Thu, 14 Mar 2019 02:10:46 -0400
Received: from unknown (HELO ([]) by with ESMTP; 13 Mar 2019 23:10:44 -0700
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Thu, 14 Mar 2019 00:10:43 -0600
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Thu, 14 Mar 2019 00:10:42 -0600
Received: from ([]) by ([]) with mapi id 15.01.0669.032; Thu, 14 Mar 2019 00:10:42 -0600
From: "Deen, Glenn (NBCUniversal)" <>
To: "" <>, "" <>, "" <>
CC: "Deen, Glenn (NBCUniversal)" <>
Thread-Topic: [EXTERNAL] Re: [104attendees] an IETF in India
Thread-Index: AQHU2gP6HJ5JYHylBUqdy91IG4W3yKYKlH+A
Date: Thu, 14 Mar 2019 06:10:42 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: []
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: text/plain; charset="utf-8"
Content-ID: <469CAB96B02B0B4E834E11BB04958DAF@NBCUNI.COM>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-14_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903140040
Archived-At: <>
Subject: Re: [Mtgvenue] [EXTERNAL] Re: [104attendees] an IETF in India
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Mar 2019 06:10:49 -0000

While it’s exciting to hear that there is so much enthusiasm for the IETF in India, this approach of people having discussions and site visits of venues totally bypasses the IETF's processes for meeting planning.   We spent a lot of time and effort as a community the last couple of years creating the MTGVENUE criteria and in reworking the planning process and getting community consensus and we all need to follow it.

First, site visits for potential IETF meeting venues can only be done by the meeting planning team from the Secretariat who do it under the IETF LLC's authorization and direction. They have specific expertise in evaluating the city, the venue, and things like the network against IETF requirements as laid out in the MTGVENUE document, and negotiating prices.   No one else should be having discussions in any form with any venues about holding an IETF meeting, or evaluating the MTGVENUE criteria.   It skips our process, it doesn't cover our criteria in the depth we need (especially networking), and it undermines our ability to negotiate with potential future venues on the things we need from them to be chosen to be a meeting location.   

Let me be clear - No one else is authorized to hold any meeting planning discussion or evaluations, and doing so can easily lead to cities or venues being disqualified and removed from consideration.

Want to put forward a new city for consideration?   Send an email to the IETF Executive Director at or the IETF LLC Board  at LLC-BOARD@IETF.ORG.   

The way meeting venues are chosen is laid out here (Forgive the IAOC reference, this is on the list of documents to updated in the IAOC to LLC Transition):

They key parts are:

 1.  Target regions are identified by the IETF LLC (formerly IAOC) and deeper evaluation is done by the IETF Secretariat.    
 2.  Input on venues is solicited from the community by the LLC on specific cities through an email to the IETF.ORG list.    The results are posted at
You'll note that both Hyderabad and Kolkata are on the list of cities which community input has been already requested (March 2018 and September 2018).

  3. The IETF LLC and Secretariat are responsible for any further selection and evaluation, including any discussions with actual cities or venues on the behalf of the IETF.   

Again, having any authorized conversation with a venue on their acceptability for an IETF meeting location can easily undermine our ability to actually negotiate and hold a meeting there, and can remove a location permanently from consideration.

I must absolutely emphasize because of its importance that absolutely no one other than the Secretariat should be doing site visits at any location.  It ignores the actual community process, and it undermines the IETF's ability to properly evaluate and negotiate with venues.

Finally, the right place to have a discussion on meeting process and policy is on the list and not the IETF104attendees list.

-Glenn Deen, as IETF LLC Chair and Venue Review Committee Chair

On 3/13/19, 6:19 PM, "104attendees on behalf of" < on behalf of> wrote:

    <sorry for the double email to some.  I forgot to have 104attendees in the send.> 
    > Agree with Jeff.  Let's clear out on different visa processes and then hopefully
    > decide.  On the separate note, I would love to see an IETF
    > taking place in India.  We would get an enormous number of
    >  local participants who typically don't attend IETF.
    I am in India at the moment.  Yesterday, a couple of us visited a potential venue for the IETF 
    meeting.  It is beautiful.  It is a brand new 5-star hotel.   We will have unbelievable support from
    them as far as food, network, and so on.   There is plenty of capacity for meeting rooms as
    well as hotel rooms.   There is a huge ballroom for the plenary.   They will make sure that
    food allergies / specifications are well taken care of.
    We are visiting a second potential venue on Friday.  In India, we are having an "IETF
    Capacity Building / RFCs We Love" conference this Saturday where engineers and academics 
    from two different Indian states will be participating.
    Thank you to all of you who have been our guests in India at our pre-IETF conferences in the
    last two years for your kind words.  We were very happy to have you.   We will go through the
    MTGVENUE specifications and respond to each of the items.  There is already one presentation
    available which does this.  I will see if we can make that and the pictures that we took
    yesterday of the site publicly available.  We will take pictures of the other site also.
    If I may speak on behalf of the team in India, we will do our best to make the visa process as
    well as food, transportation and any other concerns you may have work as smoothly as 
    I do agree that this is probably not the best place to have this discussion.  Does anyone
    have any suggestions for another list?  
    Lastly, we will be having our 3rd annual pre-IETF Connections conference in India before
    the Singapore meeting.  Anyone who would like to attend, speak, and so on, please talk
    to me, Dhruv Dhody, Vinayak Hegde or Abhijan Bhattacharyya   
    at:, or
    They will also have the pictures of the potential IETF venues available to them.
    I hope to see you in India soon.
    104attendees mailing list