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

Ted Hardie <ted.ietf@gmail.com> Wed, 25 May 2016 18:11 UTC

Return-Path: <ted.ietf@gmail.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 9708512D0FE for <ietf@ietfa.amsl.com>; Wed, 25 May 2016 11:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yqzhtnXBpWHh for <ietf@ietfa.amsl.com>; Wed, 25 May 2016 11:11:01 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18E2812D0ED for <ietf@ietf.org>; Wed, 25 May 2016 11:11:01 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id b65so91886847oia.1 for <ietf@ietf.org>; Wed, 25 May 2016 11:11:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TONI8khEtOAy1nI5WHnvpwPLPFbAGrKFu2JgGLA3LVk=; b=k1GBmsNdylJs/7vQGCixcWSVSR+fiM4KE1Zhr4DULNncZAIUuKnNFGyvRCUWZtwBdA 8VQNpWi0IfUkBhwG/vys2yiDfLh4WG+ovJDyJO9ApKO6sNUCFKl0qloIGzjotUcC5g/C XqOcV0JnZ4WZ1QEwDapWbhY540qTmQeJPm/xmr5D5xaU/5fnKO4iWUZmAIczB/I5w8bR nVIiv4VpNRpqjw/f/E8vmugd4avcudvjR09oBjRbSDGx1037vAyLSfN8Sid86V9gLuPO NQVZ24OQjBS3eQ6RdeS9PICV0Skv+e5EhVQYrM1n1QGeyTJ2xcdop5cBM/Y1xkgIgZGb JRVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TONI8khEtOAy1nI5WHnvpwPLPFbAGrKFu2JgGLA3LVk=; b=JwjO+mQ9pSRdlUL2jtNqOjAglMu+SdBKnt5SCFajtj+mtplVLAlc3Xqc5abNT1YU6q hf/4U6MeeJXTy9ZZNTzBzVQVsfjXY7MFu5XcjnrSbgHZgQzblNwrzKOt83ZI5Vgxq1bs mwqKhpARGzrGzehMqVMm68VPQwKwR4XkklkldZJ8OXUTiyab5vwPvP99rlkbxwwltx2k s75evqJyc6wmkKJCB5EmDpBdX8NMabmH0Wycam9hNv48Ewip0c4Tn1lIpznSd4o65+q8 iB++KVJ8AjKSqDnZ81ctbDTFTNXGYDAm/GXVEMGbLixsJ+giWIk5oHbQPlzrK+3psGSx WIGg==
X-Gm-Message-State: ALyK8tLtm/qqqJRecGv8Zn/WVkYEameVE4Qia0uxJNwGtStlgGHvPl8oZvT3Hh/Mfk4ekgo9/mUfN+0H7wve5Q==
X-Received: by 10.157.1.140 with SMTP id e12mr3334996ote.180.1464199860450; Wed, 25 May 2016 11:11:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.195.137 with HTTP; Wed, 25 May 2016 11:10:40 -0700 (PDT)
In-Reply-To: <256739472.426341.1464191336969.JavaMail.yahoo@mail.yahoo.com>
References: <20160524210344.64781.qmail@ary.lan> <bd1f61ef-3be2-1a16-804c-68548df0b789@gmail.com> <alpine.OSX.2.01.1605242300120.194@rabdullah.local> <da508fd5-307c-c61e-5b72-185238414a9c@gmail.com> <1936013436.371962.1464185835726.JavaMail.yahoo@mail.yahoo.com> <439c30dc-3d3c-e6e3-43f2-812a66496379@gmail.com> <270093544.407294.1464189518299.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1605250826150.2005@rabdullah.local> <256739472.426341.1464191336969.JavaMail.yahoo@mail.yahoo.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 25 May 2016 11:10:40 -0700
Message-ID: <CA+9kkMDVX_bpL9FtqSk5u=A_Pt8LWGQ476uh=E9dpB+bAcG8xw@mail.gmail.com>
Subject: Re: IETF 100, Singapore -- proposed path forward and request for input
To: nalini.elkins@insidethestack.com
Content-Type: multipart/alternative; boundary=001a114fd90c8ffdf30533ae98d4
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/y0b9gzwls-gLmyGL5Vv8GkOq1yU>
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
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: Wed, 25 May 2016 18:11:02 -0000

On Wed, May 25, 2016 at 8:48 AM, <nalini.elkins@insidethestack.com> wrote:

>
> I actually prefer the word "unfairness" or "inconvenience" to the word
> "bigotry".  But, I think it FEELS like bigotry to some people so I was
> validating Melinda's feelings.  (Sorry, I am from Northern California and
> processing feelings for hours on end is the local sport.)
>
>
The choice of words here is important.  Inconvenience, for example, has the
connotation that the issue has no great important or long lasting effect.
Unfairness doesn't, and may be a better choice as a result.


A same sex male couple attending the IETF in Singapore will  break the law
to have a normal family life.  Suspending that life for a week may have no
great important or lasting impact to some; for others it may mean they
cannot attend except remotely.  That latter choice may have an impact on
what jobs they can do for the IETF and may have an impact on their
employers' view of their work.

As I said earlier when I suggested we work for principles rather than
anecdote, an individual's willingness to handle risk will be quite variable
depending on their circumstances, but that's not the organizational
question.  That question is either:  are we willing to presume that certain
classes of participants must either skip a meeting or break the law to
attend?

regards,

Ted Hardie