Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input

"Peterson, Jon" <jon.peterson@neustar.biz> Sat, 21 May 2016 21:38 UTC

Return-Path: <jon.peterson@neustar.biz>
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 12B3312B076 for <ietf@ietfa.amsl.com>; Sat, 21 May 2016 14:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 wXKVTrJDwMaM for <ietf@ietfa.amsl.com>; Sat, 21 May 2016 14:38:32 -0700 (PDT)
Received: from mx0b-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7F5B128B44 for <ietf@ietf.org>; Sat, 21 May 2016 14:38:32 -0700 (PDT)
Received: from pps.filterd (m0078664.ppops.net [127.0.0.1]) by mx0a-0018ba01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4LLXA5V015872 for <ietf@ietf.org>; Sat, 21 May 2016 17:38:32 -0400
Received: from stntexhc11.cis.neustar.com ([156.154.17.216]) by mx0a-0018ba01.pphosted.com with ESMTP id 232jatu61y-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 21 May 2016 17:38:32 -0400
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.94]) by stntexhc11.cis.neustar.com ([::1]) with mapi id 14.03.0279.002; Sat, 21 May 2016 17:38:31 -0400
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
Thread-Topic: [Recentattendees] IETF 100, Singapore -- proposed path forward and request for input
Thread-Index: AQHRs6kdf19IPbKzWU6x0/t4EZ7rVg==
Date: Sat, 21 May 2016 21:38:30 +0000
Message-ID: <D3662363.190A96%jon.peterson@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [10.96.12.51]
Content-Type: multipart/alternative; boundary="_000_D3662363190A96jonpetersonneustarbiz_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-21_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605210281
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/iIh2rDZTbpjFERrUaBw3Z4Bevgc>
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: Sat, 21 May 2016 21:38:34 -0000

On 5/21/16 1:00 PM, Brian E Carpenter wrote:

> I agree, but I also agree with Jordi. The main reason for having
> a diversity policy is ethical and moral, but there's also a 'business'
> reason - making use of everybody's talents to the maximum - and that
> surely is the fundamental reason for the whole site selection policy
> anyway. It certainly isn't providing tourist and vacation opportunities
> for family members. So...


There's a reason this discussion has come up around IETF 100, though. While I'm sure IETF participants would be tempted to view this as just another meeting, there's a sense in which it has to be more than that. A lot of us have spent much of our careers working in this organization, and developing professional and personal relationships here. IETF 100 will be a work meeting and not a vacation opportunity, but I think attached to that work meeting should also be a celebration, and one where the personal relationships may matter more than usual.


When I hear that long-time participants, people that have been around longer than me, feel like they need to sit this one out because of where it is happening, or worry about bringing their families to a meeting where we expect that these enduring relationships will be celebrated, that makes me think we as a community need to arrive at a consensus about whether or not this is okay, and if not, what we should do about it.


We do need to set better general policies for venue selection, and it sounds like the IAOC is starting to look into that. But I think there's a further question about this specific meeting location that we should resolve with some urgency.


Jon Peterson

Neustar, Inc.