Re: Follow-up on the issue of IETF members being unable to attend.

Pat Thaler <pat.thaler@broadcom.com> Thu, 02 February 2017 00:09 UTC

Return-Path: <pat.thaler@broadcom.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 662351294F0 for <ietf@ietfa.amsl.com>; Wed, 1 Feb 2017 16:09:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.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 TlMEUix_fgZ1 for <ietf@ietfa.amsl.com>; Wed, 1 Feb 2017 16:09:48 -0800 (PST)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (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 1F02812959A for <ietf@ietf.org>; Wed, 1 Feb 2017 16:09:48 -0800 (PST)
Received: by mail-vk0-x231.google.com with SMTP id t8so171578vke.3 for <ietf@ietf.org>; Wed, 01 Feb 2017 16:09:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=efCC3bfjpCaGjrw60cmYUtd66rXNrw5y9oxEc1YhUbw=; b=buQrJ818SiRM6oG+YamaBr8j7ehB/r3bKXlnpzsR1nzaq3Ai6GFPcTd23p+7SydhxG z4dMRYWUdbKT/4DdefV4rgAcS4fgRDIwfk4iNrCBSjQuUHq7Saqro7GQDKCqrSdgxJ2M MjLl+GTd/xK7u2VFiNrmknKkspgPuy9QzfjhA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=efCC3bfjpCaGjrw60cmYUtd66rXNrw5y9oxEc1YhUbw=; b=e8kHMDxczdLTjUkxMMlIL5uWr0IZ9be/LKHdYXtb1Z2zZLxvMt5YjZbpYTPHivKBbO fVLH7HuZEflhpS6dnXZp4SGf9VG+4RUNArHgvfUzrsP5UBaLWNfy3OM7v32efP43QGCc X7PT4Drb67vK5uqoi5d2l7SuxtAqH/xMMTS6w6YbkMLZH0NK60JQL1G31IECQ/HMmn3b KNDDZy5fh2vikU/1lIbO8BEhDAAAuQr/6MLWVq5A/Gkw79AuOrYLTZWCSFyGzjWTnNIV rM2WzfXAxspcF6UiossVgZ9HndZVSLGZNCtczfi65r8eS0QmpicXVW7ejJW5Jae3UvSg S9kQ==
X-Gm-Message-State: AIkVDXLegeMWIV1mwKYr4mxD3jQ+CtMYNau0hPus3ffAvPUznk3+6NQDGrG1hmiGXAux/9L7MhX0ncMb122KR2DS
X-Received: by 10.31.48.75 with SMTP id w72mr2808812vkw.69.1485994186917; Wed, 01 Feb 2017 16:09:46 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.69.226 with HTTP; Wed, 1 Feb 2017 16:09:46 -0800 (PST)
From: Pat Thaler <pat.thaler@broadcom.com>
Date: Wed, 01 Feb 2017 16:09:46 -0800
Message-ID: <CAJt_5EiSDWaT+SVJ7TMk4gDkV5uRXX5D8eby=gA3xz3KymyyQw@mail.gmail.com>
Subject: Re: Follow-up on the issue of IETF members being unable to attend.
To: Dave Burstein <daveb@dslprime.com>
Content-Type: multipart/alternative; boundary="001a11430ea6a6a947054780fb68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YlLIf_B475yv2cm_9sTHw41l4BM>
Cc: IETF Discussion <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: Thu, 02 Feb 2017 00:09:50 -0000

Just to clarify, there is IEEE (the whole organization) and many different
subgroups of IEEE of which IEEE 802 is one. IEEE in Dave's first bullet is,
I expect, referring to IEEE as a whole. The third bullet applies for IEEE
802. I've no idea what the refund policy will be applied by other IEEE
subgroups who are holding meetings, conferences and such.

IEEE at the top level has said, in an email to the subgroups, that a
statement from IEEE is forthcoming. They have asked the subgroups to
refrain from issuing independent statements until that happens.

The IEEE 802 Executive Committee has it's regular teleconference on Feb 7.
There is an agenda item to discuss impact of the immigration policy on us.
It has already been IEEE 802's practice to refund plenary meeting fees when
someone can't attend due to a visa issue. There may be discussion on
whether to confirm that policy with a motion.

Regards,
Pat



On Tue, Jan 31, 2017 at 11:53 PM, Dave Burstein <daveb@dslprime.com> wrote:

> Folks
>
> I want to thank Jari, Leslie, and Andrew for speaking rapidly and clearly.
> I believe they are wise to address the issues directly affecting IETF
> rather than discussing the merits of U.S. policy. I believe just about
> everyone following this knows the issues and nothing would be gained by
> political discussion.
>
> A few follow-up suggestions, carefully chosen to be procedural. I'm mostly
> a lurker here.:
>
>
>    - That the IETF liaisons courteously forward our blog to the
>    organizations we connect with. I just got a note in IEEE that they are
>    considering a policy and believe what we've decided could help their
>    discussion. I particularly would like to hear from Gonzalo with any
>    response we get from 3GPP, a European-based group that might have a
>    different perspective.
>    - That we take up the offer of support from ISOC that Kathy Brown
>    posted on the ISOC list. They have a communications staff of about a dozen
>    full-time people. I've heard from two ISOC Board members as well as Kathy
>    that they are deeply committed to doing what's right here. They might help
>    if we reach out and reiterate that IETF is open to all. That could be as
>    simple as a letter to the editor of leading publications in the countries
>    most directly involved. I assume that whoever signs the note will carefully
>    not present personal opinions as IETF policy. We could also send out the
>    blog we have.
>    - That we consider providing refunds to those blocked from attending.
>    I'm told that IEEE will almost definitely offer refunds. I'd suspect the
>    total would not be that large. It will be discussed at a teleconference
>    February 7 http://www.ieee802.org/minutes/Conference-calls/
>    Conference-calls.shtml . I believe there are many IEEE members here
>    and the call is open to all.
>
> I have been reporting on this at http://bit.ly/2kKIjY3, which I'm posting
> as a bit.ly link rather than with a title some might think subjective.
>
> Dave Burstein
>
>
>
> --
> Editor, Fast Net News, 5GW News, Net Policy News and DSL Prime
> Author with Jennie Bourne  DSL (Wiley) and Web Video: Making It Great,
> Getting It Noticed (Peachpit)
>