Re: [Recentattendees] Background on Singapore go/no go for IETF 100

Margaret Cullen <> Thu, 26 May 2016 18:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 785D212D84F; Thu, 26 May 2016 11:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FSL_HELO_HOME=1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id F-nGHWpQLDug; Thu, 26 May 2016 11:44:07 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3010612D85D; Thu, 26 May 2016 11:44:06 -0700 (PDT)
Received: by with SMTP id x189so85002182ywe.3; Thu, 26 May 2016 11:44:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ChZ28vVjBln6dh3pYJ4WMin7GpV56/dZruaspCgKH/Y=; b=jlPgQUso/NKi5m6P8k7mM+DTdB/ovUXzSEVTZt/hr6djByQecy5e1htxS/ZBnJvS9b 38vbomuTAq+aS9ZoQ8gRazhnYldc6vFUPmetbBky5XqVkAgOVdflzkkLnJ5n+1OxJswu DbYnYalpzms0uWbehLR3+AfOVUOfm349LWzmOyJ1qTEgH5iJW/wxFHBmLlBczffjI4VJ /CQMCnq/3H5M7uJTN6yflEzGa+fFpFxVP559cfkIJcpLg8FhG8Uu2bkuKCuzIZRA+TJz kFBOLA4r1mFP9lbC28eT/+hi7DdWD1eQSHkKud6KOooz3lawXubbnBReSTS835zK0ijw zOrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=ChZ28vVjBln6dh3pYJ4WMin7GpV56/dZruaspCgKH/Y=; b=d1OublHoJIGMQ5Vofk/AKt2YNLh0rm0kfQvNWiu3tFFW8ybc7eVqveOagwmdl7YVFG nMF6z8rg4LCuHe27wxqjpQutnZlvCDe7pe62bdfDdZynY/f/9ROQV+xYpwikVe6yDaAi rdMqxGnzahyWLISSXHQ6ZbV7lp5SLFWIMrR5L94SQ9dkrtOh4X23YDscBpa/Th7y7UX1 F71mHqIXi0xHqwIgExKLfaUVMHbTr7+M94bgx0oQ05koyI1t8Ecpb8ft9Vh897Ik722R C7q+RPigRvRSWVMam+cSoke9LlR93o+YvnVp5bysGdt5KBHO3LmFY9wmuOAFki5Qipu2 J/gw==
X-Gm-Message-State: ALyK8tIyKGSrVzscrX5GX8Zxg5KgI5/ADyezKfkoJvRHnp0S4WbEIPF1nTLB7SYfDJrK7g==
X-Received: by with SMTP id r123mr7484264ywd.274.1464288245234; Thu, 26 May 2016 11:44:05 -0700 (PDT)
Received: from margarets-air-3.home ( []) by with ESMTPSA id j7sm3116130ywg.31.2016. (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 26 May 2016 11:44:04 -0700 (PDT)
Sender: Margaret Cullen <>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
From: Margaret Cullen <>
In-Reply-To: <>
Date: Thu, 26 May 2016 14:44:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: "Fred Baker (fred)" <>
X-Mailer: Apple Mail (2.3124)
Archived-At: <>
Cc: "" <>, "Ietf@Ietf. Org" <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 May 2016 18:44:09 -0000

Hi Fred,

> On May 26, 2016, at 1:15 PM, Fred Baker (fred) <> wrote:
> indicates that 12 states have anti-sodomy laws on the books, including Louisiana, Alabama, Florida, Idaho, Kansas, Michigan, Mississippi, North Carolina, Oklahoma, South Carolina, Texas and Utah.

The U.S. Supreme Court ruled that those laws are unconstitutional.  The fact that states have not cleared them off the books is annoying, but does not mean that they are currently enforced or enforceable.

As far as I know, the law in Singapore is still in force.  According to videos sent by one of the posters here, their Parliament considered rescinding the law bout 10 years ago, and decided not to rescind it.  

> We have met three times in Texas, three times in Florida, and once in Utah. We have had no incident that I became aware of.

Did any IETF participant claim, in advance or since, that it wouldn’t be safe for them to travel to those locations?
> Which doesn't say that Ted is wrong, but it says that his information is dated.

I have known Ted Hardie for almost two decades, and while we don’t always agree, I have never known him to be careless, alarmist or paranoid.  Ted cares deeply about the IETF and the Internet, and I don’t believe he would raise an issue like this to gain attention or obstruct our work.  So, when Ted says that it might be unsafe for him to travel to Singapore with his family, I believe that there are rational reasons for him to think so.

> If we can't go to Singapore, I don't see how we go back to Texas, Utah, Florida, important parts of Africa, or the Arab world. And, oh yes, much of Eastern Asia. To me, that's the crux of the issue. I respect Ted, Melinda, and the many others that are LGBT and working in the IETF. However, the issue has, in my opinion, become far more political/emotional than fact-based. I'd like us to make sure we have the right guidelines in venue selection that focus on having successful meetings, and remote participation capabilities that will enable someone that chooses to attend that way to do so productively.

I hope we would not go to most of the Arab world, anyway, because of the status of women in those countries.  I would not be willing to travel to a country where women cannot vote, cannot own property, cannot drive, etc.  So, if the IETF were to go to one of those countries, I would not attend.  I would also think less of the IETF and it’s commitment to gender diversity. (BTW, I think it is fine for women to _choose_ to abide by religious or cultural restrictions — I object to laws that require them to do so.)

You seem to be advocating for an IETF that meets all over the world, while people who are unwilling to travel to those places for reasons of safety or ethics would stay home and participate remotely.  While there might be some (as yet unquantified, see below) advantage to that approach, it would have the _hugely unfortunate effect_ that the most privileged people in the world (rich, white, U.S./European, straight men) might be the only ones who are willing/able to attend every meeting in person.  Given that our leadership selection process depends on in-person attendance, both as a way to select nomcom members and as a requirement for leadership positions, that would run counter to our efforts to make the IETF a more diverse organization across many lines.

Also, while I enjoy our World Tour as much as the next girl, the meeting in Buenos Aires had very poor attendance from regular attendees, and this made it harder to get work done, IMO.  Attendance numbers (and therefore registration fees) were also down.  What are the benefits that offset those costs?  Does having one meeting in a country actually result in an increase in meaningful, ongoing participation from people in that country?  Has anyone checked how many first-time attendees from a given location send mail to our mailing lists more than six months later, attend future meetings (in person or remotely) and/or author documents?  If so, could someone publish the results of these studies?

This is obviously a very complicated issue.  The IETF has a choice to make about what sort of organization it wants to be, and there are rational viewpoints on both sides of this issue.  I don’t think we will resolve this issue, though, if we keep throwing up strawmen (like being unable to meet in Texas), instead of trying to understand the more subtle effects of the choices we are making in these situations.

No one person can have a diverse perspective, and I can’t claim to speak for everyone in the IETF about these sorts of issues any more than you can.  Probably the best way for the IETF to make good, carefully researched and highly responsive decisions in this area would be to have an IAOC that is as diverse as possible, along as many different lines as possible.  I will send that suggestion as input to the new nomcom when it has formed.